• Summary

    FireTrac® 4x24bT

    Advanced AS5643 I/O adapter

    The FireTrac®product familycomplements DapTechnology’s successful FireSpy®and AS5643 OHCI host adapter product lines. It clearly is the next generation SAE AS5643 data processing, simulation and testing solution.

    DapTechnology has seen an increasing demand for more streamlined hardware systems for the processing of AS5643 (and generic 1394) data streams. More and more customers get involved in monitoring the actual data content rather than the 1394 layer. And for simulation purposes, they require advanced error insertion capabilities that can only be accomplished with non-off-the-shelf Link Layer implementations. IRIG time-stamping of monitored events on the bus is a typical requirement.

    FireTrac®is the answer for this market need. It is designed to natively (not just as an add-on protocol) support AS5643. Besides the standard IEEE1394 features, FireTrac® has been architected to provide hardware level support for SAE AS5643 which reduces host processor burden, specifically for packet encapsulation, data extraction, receive/transmit STOF offsets, etc. As a key example, FireTrac® handles AS5643 transmission timing entirely in hardware therefore making it a lot more accurate. It is important to understand that FireTrac® is a dedicated and optimized solution for the processing of AS5643 type traffic. Support for this protocol is embedded in the hardware and not just in a software layer (as typically provided with other solutions that rely on COTS OHCI chipsets).

    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.

    Key features

    • AS5643 compliant
    • IEEE 1394b-2008 compliant
    • Supported Speeds*: S100B, S200B, S400B, S800B
    • 4 independent 1394 nodes
    • Link Layer: FireLink Extended with Mil1394 Extensions
    • PHY Layer:
      • FT4424bT: Texas Instruments TSB41BA3DIPFP (or newer)
      • FT4824bT: Texas Instruments TSB81BA3EPFP (or newer)
    • 12 active transformer-coupled 1394 ports
    • 3x SFF-8614 connectors
      • ports A0, B0, C0, D0
      • ports A1, B1, C1, D1
      • ports A2, B2, C2, D2
    • Field-upgradable
    • PCI Express 2.0 x4
    • Sustained multi-bus IEEE-1394 traffic at S400/S800
    • IRIG Time Synchronization
      • IRIG-B122 (IEEE1344)
      • IRIG-B002 (IEEE1344) TTL
      • IRIG-B002 (IEEE1344) RS422
    • C/C++ Application Programming Interface (API)
    • Support for:
      • MS Windows
      • Linux
      • VxWorks
      • QNX
      • LabVIEW (RT)
      • SGI IRIX

    *) Depending on exact model

    An “Enabling” AS5643 Solution

    FireTrac® provides a very universal approach to dealing with AS5643 type of traffic. It is uniquely suited for SAE AS5643 level Data

    Extraction and Analysis (RX) but also Data Generation and Device Simulation (TX).

    With the FireTrac® platform DapTechnology has enabled dedicated implementations needed in the A&D environment. Such application-centric solutions are focused on very specific tasks and, due to their very clearly defined requirements, DapTechnology is able to even further optimize the firmware and software architecture.

    Examples for such “customized” solutions are:

    • Data Recorders (single/multi-channel, with/without Stealth, …)
    • System Simulators (multi-streams generator, error injection, …)
    • System Monitors (Health, Data Extraction, …)


    FireTrac® uses a combination of 1394 and AS5643 support in hardware, as well as a robust, well-designed 1394 software stack (FireStack®) running on a host computer. Interfacing to this stack can be done via an API that offers C/C++ interfaces on multiple platforms and a LabVIEW interface on Windows. Currently, DapTechnology supports Windows, VxWorks, Linux, QNX, IRIX and LabVIEW(RT) platforms

    An essential feature of FireTrac® is its adaptable software and firmware layers. In order to be usable in embedded designs having limited resources, great emphasis was given to keep the footprint and host system resource utilization fairly small. 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.

     

     

    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

    Offboard SFF-8614 bus connectivity

    For this version of FireTrac® DapTechnology has opted to implement an innovative off-board connectivity, rather than the SCSI2 connector (used on the FT3460bT) the FT4x24bT uses SFF-8614 connectors. SFF-8614 originates from the miniSAS HD interconnectivity technology which has proven its benefits with regards to signal integrity, data throughput, durability and usability. Customers will benefit for the selected port-to-connector routing (A0-D0, A1-D1, A2-D2) as the need for cables can be adjusted to the specific usage scenario, therefore simplifying harnesses and reducing costs for unneeded cables.

    For example, with just one (1) harness the ‘0”-ports on all 4 nodes (A-D) can be connected as leave nodes. Additional harnesses would only have to be added for daisy-chain or star connectivity.

     

     

  • Specification

    FireTrac® 4x24bT specifications

    Dimensions:

    Half-length, full-height x4 PCIe, 111mm x 167mm

    Weight: 230 g
    Power Requirements: 10 Watts (max.)
    Regulatory Compliance: FCC Class A, CE
    Connections:

    PCI Express 2.0 x4

    3x SFF-8614 connectors for transformer-coupled 1394b ports

    D-SUB connector for IRIG and Sync

    Indicators: -
    Switches: -
    Part Number:

    FT4424bT-OPT1-OPT2-[OPT3]

    or

    FT4824bT-OPT1-OPT2-[OPT3]

    Options: OPT1: Operating System

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


     

    OPT2: Personality Profile

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

    OPT3: Extended Warranty

    SS - SW extended Warranty

    Blockdiagram

  • Software

    FireTrac® 4x24bT 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.

  • AS5643 & MIL1394

    FireTrac® 4x24bT AS5643 & MIL1394

    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 FireTrachardware. 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.

  • Usage

    FireTrac® Usage

    Simulating AS5643 CCs and RNs

    SAE AS5643 describes two types of device categories Control Computers (CC) and Remote Nodes (RN) whose functional definitions depend on the assigned tasks with respect to network communication and integrity verifications. Supporting both device types is an integral objective for FireTrac®and  FireStack®  and the  FireStack API provides feature rich function calls for both categories in parallel. This way the implementer can focus on the AS5643 functional requirements for either CC and RNs. FireStack® doesn’t put the device in a specific operational mode (either CC or RN) but all related functions and functionalities exist in parallel and – for a multi-node device can used independently per node. Example applications are (or will be made) available to demonstrate both scenarios.

    However, it is also important to understand that FireTrac®  is not just a dedicated “AS5643 device”. It is also a fully compliant IEEE-1394 device. In particular this is important because next to the Async Streams (which are used for the Asynchronous Subscriber Model (ASM)) FireStack® also supports Asynchronous as well as Isochronous Messaging. Both are optional for the usage in AS5643. But due to its guaranteed quality-of-service the Asynchronous messaging seems to be the logical choice for Cross-Channel-Data-Link (CCDL) implementations. And video/audio streaming in conjunctions with ASM traffic is seen as a future growth path for future variants of AS5643.

    Network Simulation with FireTrac®

    The FireTrac®  product familyoffers a large variety of options how these I/O cards can be used to start, expand, and grow a simulation environment for  AS5643 devices. While architecturally identical, the different channel numbers allow for a vast variety of configurations. The image to the reight presents a few varants hwo a network can be built by using just a few FireTrac cards. The multi-node card archtiecture allows to easily configure the branch structure of nodfes connected to a single CC. Equally, the FireTracs can be used to simulate the aspects of a redundant network.

    Please note that the configuration scenarios presented below predominantly address triple redundant network systems, yet can relatively simply be adapted for system redundancies lower or higher than three (3).    

    4-node FireTrac®:

    The 4-node version(s) of FireTrac®is perfectly suited for use as a CC. As the picture below demonstrates the 4-node architecture is ideal to simulate a 3-branch CC including the interface for the CCDL. Using three FireTrac® cards (blue) a full and triple-redundant arrangement for control computers can be realized.

    Paired with a triple redundant RN implementation using 3-node FireTrac® (displayed in green) one can easily build a minimal yet expandable instantiation of an AS5643 network consisting of CCs with CCDL and RNs.

    However, the above is only an implementation variant. A 4-node FireTrac® can also be used to simulate single branch bus behavior (left and middle) or mixed CC/RN situation in double redundancy (right).

    3-node FireTrac®:

    The 3-node version(s) of FireTrac®is best suited to address triple-redundant and triple-branch architectures when no CCDL is needed. The picture below demonstrates how such a system can be arranged in different RN configurations by using just a few 3-node FireTrac® cards (green).

    Other variants of how a single 3-node FireTrac® card can be used are depicted below. The left shows a CC devices simulating the triple bus interface (3 CC) whereas the right pictures demonstrates a possible single-branch usages model (CC + 2 RNs).

    Scalability of the AS5643 Network

    A single FireTrac can be used to simulate four different AS5643 devices and the separate nodes can be easily interconnected via small Connectivity Dongles which are sold as optional accessories.

    In the depicted example, one Dongle (AB-CD, top) connects ports A0 with B0 as well as C0 with D0. Furthermore, an additional Dongle (AD-BC, bottom) can be used to connect B1 with C1. The resulting loop on A1-D1 is automatically resolved with the PHY-level loop healing mechanism.

    When enlarging the network, two or more FireTracs can be easily interconnected with SFF-SFF harnesses. Such harnesses are available in various lengths. 
    For optimized installations (labs, test systems, …) these SFF-SFF harnesses can also be configured in single, dual or triple channel variants. Please consult our sales specialists for assistance.

  • Media

    FireTrac® 4x24bT media files

    Product Image(s)

  • Documents

    FireTrac® 4x24bT documentation

    Manual

    Manual available on request

  • Accessories

    FireTrac® 4x24bT accessories

    The following accessories are available for this product:

    In order provide a wide variety of connectivity options – either to additional FireTracs or to other AS5643 equipment, DapTechnology is developing a set of harnesses / interconnectivity options.

    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.

    Beside the 19”-panels DapTechnology will offer also a series of “patch-cables”. For examples, the SFF-to-SFF cable shown below can be used to effectively daisy-chain several FireTracs (ports A0-D0 to A1-D1) with just one single harness. Other variants include fan-out cables with Bilingual or 38999 connectivity. No termination variants are also available.

    Mil1394 SFF Spider Cable with 19" panel

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: Gore Quadrax

    Part number:
    SFF5F419PBLF

    Termination 1:
    3x FSS-8614

    Termination 2:
    12x 1394 Bilingual (female) 9-pin,
    permanently attached to 19"-Panel

    Length:
    5 feet

    SFF5F419PBLF-IS

    3x FSS-8614

    12x 1394 Bilingual (female) 9-pin,
    permanently attached to 19"-Panel,
    1x IRIG and 3xSYNC

    5 feet

    The harnesses above are also availbale in 10ft, 15ft, 20ft and 50ft variants.
    The harnesses above can also be built with termination sockets of the following type(s): Mil38999 m/f, LEMO m/f

    Mil1394 SFF Connection Dongle

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: -

    Part number:
    SFFDongleAB&CD

    Termination 1:
    FSS-8614

    Connections:
    Port Ax conencted to Port Bx
    Port Cx conencted to Port Dx

    Length:
    -

    SFFDongleAD&BC

     FSS-8614 Port Ax conencted to Port Dx
    Port Bx conencted to Port Cx

    -

    Mil1394 SFF-SFF cable

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: Gore Quadrax

    Part number:
    SFF1F4SFF

    Termination 1:
    FSS-8614

    Termination 2:
    FSS-8614

    Length
    1 foot

    SFF5F4SFF as above as above 5 feet
    The harnesses above are also availbale in 3ft, 7ft,10ft, 15ft, 20ft and 50ft variants.
    Additional to the default configuration (i.e. 4 bus connections) the harnesses above can also be built lower number (1/2/3) of connections per SFF connector. Please talk to our sales specialists for such variants.

     

    Mil1394 SFF-NT cable

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: Gore Quadrax

    Part number:
    SFF5F4NT

    Termination 1:
    FSS-8614

    Termination 2:
    4x unterminated cable

    Length
    5 foot

    The harnesses above are also availbale in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants.
    Additional to the default configuration (i.e. 4 bus connections) the harnesses above can also be built lower number (1/2/3) of connections per SFF connector. Please talk to our sales specialists for such variants.

     

    Mil1394 SFF-LEMO (m/f) cable

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: Gore Quadrax

    Part number:
    SFF5F4LEM

    Termination 1:
    FSS-8614

    Termination 2:
    4x LEMO male

    Length
    5 foot

    SFF5F4LEF FSS-8614 4x LEMO female 5 foot
    The harnesses above are also availbale in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants.
    Additional to the default configuration (i.e. 4 bus connections) the harnesses above can also be built lower number (1/2/3) of connections per SFF connector. Please talk to our sales specialists for such variants.

     

    Mil1394 SFF-1394b (m/f) cable

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: standard 1394

    Part number:
    SFF5F4BEM

    Termination 1:
    FSS-8614

    Termination 2:
    4x 1394b Beta male

    Length
    5 foot

    SFF5F4BLF FSS-8614 4x 1394b Bilingual female 5 foot
    The harnesses above are also availbale in a 10ft variant.
    Additional to the default configuration (i.e. 4 bus connections) the harnesses above can also be built lower number (1/2/3) of connections per SFF connector. Please talk to our sales specialists for such variants.

     

    Mil1394 SFF-Mil38999 (m/f) cable

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: Gore Quadrax

    Part number:
    SFF5F4MIM-...

    Termination 1:
    FSS-8614

    Termination 2:
    4x 38999* male

    Length
    5 foot

    SFF5F4MIF-... FSS-8614 4x 38999* female 5 foot

    * Due to numerous options for 38999 connectors (material, size, pinning, keying, lanyard, ...) a detailed connector requirement has to be delveloped as part of the sales process.

    The harnesses above are also availbale in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants.
    Besides the default configuration (i.e. 4 bus conenctions) the harnesses above can also be built lower number (1/2/3) of connections per SFF connector. Please talk to our sales specialists for such variants.

     

    Mil1394 Dsub to BNC/Dsub for IRIG and Sync

    For Product(s): FireTrac4x24bT
    Documents: -
    Cable Type: Gore Quadrax

    Part number:
    DSU5F5BNC-IS

    Termination 1:
    Dsub

    Termination 2:
    4x BNC male
    Dsub

    Length
    5 foot

    The harnesses above are also availbale in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants.

     

  • Sales

    FireTrac® 4x24bT 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!