• Summary

    FireAdapter 3465bT

    Mil1394 Standard OHCI Host I/O cards

    In order to offer long-term availability of a triple OHCI card in PMC form factor, the FireAdapter3465bT was designed as a 1-to-1 replacement of the PMC341bT using a modern PCI Express based approach. Three XIO2213B 1394b LLC chips are connected to a PCI Express switch which is connected to a PCIe to PCI-X bridge in reverse mode in order to connect to PCI-X or PCI based Single Board Computers. This concept allows using the latest PCIe based OHCI LLC technology even on legacy PMC-based systems.

    The internal PHY of the XIO2213B is disabled and an external TSB41BA3 is used in order to benefit from all the latest updates to IEEE-1394 PHY technology.

     

    Key features

    • AS5643 compliant
    • IEEE 1394b-2008 compliant
    • Supported Speeds*: S100B, S200B, S400B
    • 3 independent 1394 nodes
    • PHY Layers: TSB41BA3 (latest commercially available revision)
    • 9 active transformer-coupled Mil1394 ports
    • SCSI2 off-board connector for 1394 ports A0-A2, B0-B2, C0-C2
    • PCI-X 1.0 host connectivity, 64-bit x 133MHz
    • Link Layers: XIO2213B (1394b LLC)
      • OHCI 1.1 compliant
    • Sustained multi-bus IEEE-1394 traffic at S400
    • C/C++ Application Programming Interface (API)
    • Support for:
      • MS Windows
      • Linux
      • VxWorks

    *) Depending on exact model

  • Specification

    FireAdapter 3465bT specifications

    Dimensions: PMC form factor, 15 x 74 x 154 mm
    Weight: 100 g
    Power Requirements: PMC: 3.3 V
    Regulatory Compliance: FCC Class A, CE
    Connections:

    64-bit PMC connector configuration

    off-board SCSI2 connector for 9 bus connections, fan-out cable is optional

    Indicators: -
    Switches: dip switches for PHY port mode programming
    Part Number: FA3465bT(1)-OPT1-OPT2-OPT3-OPT4
    Options: OPT1: Form Factor

    PCI:     PCI form factor (carrier)
    PCIe:   PCIe form factor (carrier)
    CPCI:   CPCI form factor (carrier)
    CPCIe: CPCIe form factor (carrier)
    PXIe:    PXIe form factor (carrier)

    OPT2: Operating System

    WIN  – MS WindowsTM
    VXW  – VxWorksTM
    LIN    – Linux

    OPT3: Personality Profile

    LLP – Low Level Profile
    SSP – SW Stack Profile
    SSBMP – SW Stack & Bus Mgmt. Profile

    OPT4: Extended Warranty

    SS - SW extended Warranty

    Codes:

    ECCN:3A992.a

    HST: 9030.40.00

  • Software

    FireAdapter 3465bT Software

    FireAdapter and FireStack - a complementing combination

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

    This very robust and well-designed 1394 software stack runs on a host computer and very effectively supports the OHCI descriptor model for packet assembly and disassembly. Interfacing to this stack can be done via an API which offers C/C++ interfaces and runs on multiple Windows versions. An essential feature of FireAdapter is its standardized HW layer. For FireStack® the individual features and functions of FireAdapter 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 Profiles

    An essential feature of FireStack® is its thin software  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 FireStack® 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.

    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

    FireAdapter 3465bT AS5643 & MIL1394

    An “Enabling” AS5643 Solution

    It is important to understand that FireAdapter is a “Mil1394 enabling” but not a dedicated and optimized solution for the specific processing of AS5643 type of data transmissions. Usage of OHCI compliant LLC components provides the necessary ability to transmit and receive Asynchronous Stream packets as required by the AS5643 specification for Asynchronous Subscriber Model (ASM) related data traffic.

    Furthermore, the Mil1394 compliant versions of FireAdapter provide the specified active transformer coupling essential for support of longer cable length and electrical isolation. These versions also feature hardware supporting multi-bus requirements which is critical for the support of Mil1394 redundancy and fault tolerance.

    For a proper system design as well as integration optimization it is important to understand that due to its OCHI compliance FireAdapter will utilize host processor resource for handling all Mil1394 – and specifically ASM - related packet handling tasks. Standard OHCI 1.1 is “Mil1394 unaware” and related functions will have to be implemented in a product-specific application or middleware layer. Such functions include packet encapsulation, data extraction, receive/transmit STOF offsets, etc. As a key example, FireAdapter handles ASM transmission timing entirely in software. The application has full control and responsibility of handling offset relative to the STOF during packet transmission as well as receive offset validations as well as many other verification functions.

    While this can be seen as an advantage, implementers have to pay attention to system resource utilization and latency concerns in order to meet the stringent Mil1394 timing requirements. Please also evaluate Dap’s approach to mitigate related challenges and check out FireTrac® and its innovative, resource-saving and industry approved take on embedded and HW assisted support for packet receive/transmit and timing related Mil1394 requirements.

  • Media

    FireAdapter 3465bT media files

    Product Image(s)

    FA3465bT with CarrierCards

  • Documents

    FireAdapter 3465bT documentation

  • Accessories

    FireAdapter 3465bT accessories

    In order provide a wide variety of connectivity options – either to additional FireAdapter 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.

    Mil1394 SCSI2 Spider Cable

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

    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 availbale 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

    Mil1394 SCSI2 Spider Cable with 19" panel

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

    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 availbale 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:
    -

     

  • Sales

    FireAdapter 3465bT 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!