AS5643 Advanced Interface Card - FireTrac3460bT

FireTrac® 3460bT

Advanced AS5643 I/O adapter

The FireTrac 3460bT features the FireTrac® family functionality in the widely used PMC mezzanine card form factor. It uses the latest versions off-the-shelf PHY layer silicon (TSB41BA3) together with Dap's FireLink® Extended IP Core.

The HW also provides IRIG time-stamping of monitored events and accepts IRIG-B122 (IEEE1344) inputs.

Key features

  • AS5643 compliant
  • IEEE 1394b-2008 compliant
  • Supported Speeds*: S100B, S200B, S400B,
  • 3 independent 1394 nodes
  • Link Layer: FireLink Extended with Mil1394 Extensions
  • PHY Layer
    • FT4424bT: Texas Instruments TSB41BA3DIPFP (or newer)
  • 9 active transformer-coupled 1394 ports
  • SCSI2 connector for port A0-A2, B0-B2, C-C2 as well as IRIG and Sync
  • Field-upgradable
  • PMC form factor
  • Sustained multi-bus IEEE-1394 traffic at S400
  • IRIG Time Synchronization
    • IRIG-B122 (IEEE1344) modulated
  • C/C++ and Python Application Programming Interface (API)
  • Support for:
    • MS Windows
    • Linux
    • VxWorks
    • LabVIEW (RT)
    • QNX

*) Depending on exact model

Offboard SCSI2 bus connectivity

For this version of FireTrac® DapTechnology uses a rather traditional SCSI2 connector. Main reason is the form factor and high pin count together with a good signal quality which is so essential for high-speed low-voltage differential data transmissions.

The connector allows to route all bus connections (A0-A2, B0-B2, C0-C2) together with 3 trigger signals as well as the IRIG sync input.

 

 

FireTrac® 3460bT specifications

Dimensions: PMC form factor, 15 x 74 x 154 mm
Weight: 130 g
Power Requirements: 7 Watts (max.), +3.3V and +5V
Regulatory Compliance: FCC Class A, CE
Connections:

64-bit PMC connector configuration

Off-board connector (high density) for transformer coupled 1394b ports, Off-board connector for 9 bus connections, connects to optional offboard cables (see accessories)

Indicators: -
Switches: dip switches for PHY port mode programming
Part Number: FT3460bT-OPT1-OPT2-OPT3-OPT4
FT3460bT1-OPT1-OPT2-OPT3-OPT4
Options:

OPT1: Form factor
PCI:     PCI (carrier)
PCIe:   PCIe (carrier)
CPCI:   CPCI (carrier)
CPCIe: CPCIer (carrier)
PXIe:    PXIe (carrier)

OPT2: Operating System

WIN  – MS WindowsTM
VXW  – VxWorksTM
LIN    – Linux
LABV  – LabVIEW
QNX   – QNX

OPT3: Personality Profile
FFP – Full Personality Profile
LLP – Low Level Profile
SSP – SW Stack Profile
SSBMP – SW Stack & Bus Mgmt. Profile
AS5643P – AS5643 Profile

OPT4: Extended Warranty
SS - SW extended Warranty

Codes:

ECCN:3A992.a

HST: 8471.90.0000

Blockdiagram

FireTrac® Software

FireTrac and FireStack - an ideal combination

In order to get the best out of the unique feature set of the FireTrac card DapTechnology recommends using the hardware in combination with FireStack, i.e. DapTechnology's home grown software stack.

FireStack optimally supports the hardware and firmware layers embedded into FireTrac. As FireTrac's host interface uses FireLink Extended (and not a standard OHCI Link Layer chip) functionality that has been tailored and optimized for the support of the AS5643 standard brings the combination of FireTrac and FireStack to an entirely new level.

Optimized IEEE-1394 Software Layers

The objective of FireStack’s® 1394 packet handler is to reduce resource burden when receiving and transmitting 1394 packets. The consistent utilization of zero-copy operations greatly enhances the overall system performance. FireStack® provides memory buffers accessible by both the user application and the 1394 Link Layer DMA engine.

For example, when transmitting an asynchronous packet and the user application has filled the memory buffer with the needed packet data, FireStack® will hand the buffer directly to the Link Layer for reading the packet into the packet transmission FIFO without having the CPU copy memory to memory.

Likewise, displaying a video stream from an IIDC camera only requires creation of DMA-capable reception buffers for the video frame data and registration of notification upon filling of a complete frame. Once notified the buffers holding the received data can be accessed directly by the video rendering engine in order to move the data to video card memory. 

Inbound Transactions:

Inbound Transactions (handling of incoming requests) are defined in two separate methods:

Map Local Memory: The user can "map" a memory buffer to a specific address space. The contents of the memory buffer can be accessed by the user application at any point in time. At the same time when the stack receives a request packet from a remote device it will automatically perform the response operation (read, write or lock) and will send a response packet back to the requester. The user has the option to be notified by the notification callback function when the transaction completes.

Transaction Handler: Similar to the Map Local Memory above the user can "register for" a specific address space instead of "mapping" local memory. When the stack receives a request packet it will call the user-specified handler callback function. The user can then perform any operation within the callback function. Upon returning from the handler callback, the FireStack® may transmit a response packet. The notification callback function will be called after completion of the response process.

Outbound Transactions:

This module can be used to perform memory transactions (read, write, lock) on remote nodes. When a memory transaction is initiated FireStack® will automatically determine the maximum speed to the destination node by performing the needed PHY remote accesses.

Outbound Transactions can be used in the following ways with respect to result indication: In Blocking mode the TX functions will not return until the response packet is received and thus making the code sequential. In contrast to that the Non-Blocking mode can be used to initiate a series of “split” transactions i.e. a series of requests that are then followed by the corresponding - but not necessarily sequential - responses.

Isochronous Messaging:

The Isochronous Streaming modules build on the mechanisms for efficient data processing defined by OHCI and provide a flexible and user-friendly API around it. Linked lists of buffers can be setup by the user application and will be automatically processed by the Link Layer DMA engine. Notification mechanisms are available for buffer and/or packet completion.

FireTrac® Personality Profiles

An essential feature of FireTrac® is its thin software and firmware layer. In order to be usable in embedded designs having limited resources, great emphasis was given to keep the footprint and host system resource utilization as small as possible. And, in order to optimize and streamline performance, the individual features and functions of FireTrac® are grouped into so-called Personality Profiles. These profiles may be purchased separately so that the user may configure their system based on individual requirements.

Personality Profile Comparison

The Personality Profiles allow the solution to be adapted for use in embedded systems which typically have limited resources, and/or with powerful host processors that can utilize even the fully featured profile.

The following profiles are available:

  • Low-Level API Profile
  • 1394 Software Stack Profile
  • 1394 Software Stack + Bus Mgmt. Profile
  • AS5643 Bus Interface Profile

AS5643 Personality Profile

The SAE-AS5643 protocol differs from other 1394 protocols because of its stringent timing requirements. Because of potential inaccuracies and unpredictable latencies possible with software implementations, DapTechnology strongly believes that the AS5643 protocol timing is best implemented via a HW extension in the 1394b Link Layer. Therefore, DapTechnology has added the AS5643 protocol timing into FireLink® Extended as an integral module. With this HW support FireLink® Extended is easily capable of meeting the AS5643 frame timing requirements and eliminates the need for complicated interrupt schemes or real-time operating systems typically needed to efficiently use the AS5643 protocol.

The FireStack® software library contains an AS5643 protocol module that can be used to control the AS5643 hardware of FireLink Extended enabled products (e.g. the FireTrac I/O card). Optimized frame timing can be configured and used for both timed transmission and reception.

Frame Timing: FireStack® is very flexible in the way it handles the timing of Start of Frames. Frame synchronization for AS5643 reception and transmission may be configured as either:

  • Free Running based on an internal clock with a 1us resolution,
    • based on STOF packets on the bus (just any stream packet on a configurable channel),
    • based on an External Sync Input Signal
  • or synchronized to one of the other buses on the same FireTrac.

In addition to acting as a synchronization “slave”, it is also possible for each bus to act as STOF master and output a sync pulse on an External Sync Pin.

Reception: AS5643 reception provides a filtering mechanism and all incoming packets will be run against a comprehensive verification system. Messages can be filtered on channel number, AS5643 message ID or a combination of both.

Transmission: AS5643 Transmission module can be used to control devices that support AS5643 timed transmission in. FireTrac® offers very accurate transmission timing. The following transmission modes are available:

Streaming messages: Allows writing large or small sets of messages to FireStack® and having them transmitted automatically at specified frame offset times. The provided data needs to contain so called frame separator elements to indicate that the following message needs to be transmitted in the next frame.

Repeating messages: Allows setting up a message that will automatically be transmitted each frame by FireTrac hardware. The user will have a pointer to the actual data of the message and is allowed to manipulate the data at any point in time without having to worry about its timed transmission. This is very useful for AS5643 status messages.

Single messages: Allows simply transmitting a message as soon as possible but exactly at the specified frame offset time. Several messages may be handed to the FireStack® for immediate transmission and the FireStack® will then take care of the actual moment of transmission.

STOF Messages: Allows controlling transmission of STOF messages.

FireTrac® 3460bT media files

Product Image(s)

FT3460bT with CarrierCards

FireTrac® 3460bT documentation

Manual

Manual available on request

FireTrac® 3460bT accessories

In order provide a wide variety of connectivity options – either to additional FireTracs or to other AS5643 equipment, DapTechnology is offering a series of harnesses / interconnectivity options. The versions below highlight the most commonly used variants.

However, it needs to be pointed out that other variations (e.g. different connector type) can be very easily built as well and therefore to not fall under the category "custom designed". For example, the 19”-breakout panel as depicted below offers an extremely flexible way to connecting bus devices via 1394b bilingual sockets. Such a “patch”-panel can also be configured with LEMO or 38999 sockets depending on the customer’s interconnectivity preferences. Or the "Spider"-cable can be easily built with bilingual or 38999 sockets or plugs.

1394 SCSI2 Spider Cable

For Product(s): PMC cards with SCSI2 connector: FireTrac, FireAdapter
Documents: -
Cable Type: standard 1394
Codes: ECCN EAR99, HST: 8544.49.1000

Part number:
PMC3CH3FBM

Termination 1:
1x SCSCI2 connector,
68-pin

Termination 2:
9x 1394 Beta (male),
9-pin

Length:
3 feet

PMC3CH5FBM

as above

as above

5 feet

PMC3CH3FLM

as above

9x 1394 Legacy (male),
9-pin

3 feet

PMC3CH5FLM

as above

as above

5 feet

PMC3CH7FLM

as above

as above

7 feet

1394b Coupler

Part number:

Termination 1:

Termination 2:

Dimensions:

BLFCouplerBLF 1394b, Bilingual (female), 9-pin 1394b, Bilingual (female), 9-pin 33x18.5x15 mm

 

Mil1394 SCSI2 Spider Cable

For Product(s): PMC cards with SCSI2 connector: FireTrac, FireAdapater
Documents: -
Cable Type: Gore Quadrax 26AWG
Codes: ECCN EAR99, HST: 8544.49.1000

Part number:
PMC3CH3FNT

Termination 1:
1x SCSCI2 connector,
68-pin

Termination 2:
9x unterminated cable

Length:
3 feet

PMC3CH3FNT-IS

as above

9x unterminated cable
1x IRIG and 3x SYNC

3 feet

The harnesses above are also available in 5ft, 10ft, 15ft, 20ft and 50ft variants.
The harnesses above can also be built with termination connectors (sockets and/or plugs) of the following type(s): 38999, LEMO
The harnesses can also be built with 24AWG or 22AWG with less conenctions. Details depend on the cable gauge used.

Mil1394 SCSI2 Spider Cable with 19" panel

For Product(s): PMC cards with SCSI2 connector: FireTrac, FireAdapter
Documents: -
Cable Type: Gore Quadrax
Codes: ECCN EAR99, HST: 8544.49.100

Part number:
PMC3CH5F19FP

Termination 1:
1x SCSCI2 connector,
68-pin

Termination 2:
9x 1394 Bilingual (female),
9-pin

Length:
5 feet

PMC3CH5F19FP-IS

as above

9x 1394 Bilingual (female),
9-pin
1x IRIG and 3xSYNC

5 feet

The harnesses above are also available in 5ft, 10ft, 15ft, 20ft and 50ft variants.
The harnesses above can also be built with termination sockets of the following type(s): 38999, LEMO

 

PCIe - single lane Carrier Card

for Product(s): all PMC Mezzanine cards
Documents: Datasheet
Codes: ECCN EAR99, HST: 8544.49.1000

Partnumber:
CC_PCIeG1x1_to_PMC

Host Interface:
PCI Express 1.1, single lane

Form Factor:
standard height, half length

other:
-

 

PCIe - four lane Carrier Card

for Product(s): all PMC Mezzanine cards
Documents: Datasheet
Codes: ECCN EAR99, HST: 8544.49.1000

Partnumber:
CC_PCIeG1x4_TO_PMC

Host Interface:
PCI Express 1.1, 4 lane

Form Factor:
standard height, half length

other:
-

 

PMC Carrier Card
4-Lane PXIe

for Product(s): all PMC Mezzanine cards
Documents: Datasheet
Codes: ECCN EAR99, HST: 8544.49.1000

Partnumber:
CC_PXIeG1x4_TO_PMC

Host Interface:
PXI Express 1.2, 4 lane

Form Factor:
standard height, half length

other:
-

 

FireTrac® 3460bT sales info

Package Contents

Please contact DapTechnology or DapUSA directly by sending an email to sales(at)daptechnology.com for additional information about pricing and availability!