- Home
- Products
- Summary & Overview
- Bus Analyzer
- Interface Cards
- Connectivity
- FireRepeater
- Cables and Harnesses
- IP Cores
- Software
- Accessories
- Solutions
- Support
- News
- Contact
- Company
- Mil1394
- Sitemap
- Search
The FireAdapter3424bT and 4424bT were designed as an upgrade of the PCI341bT using a modern PCI Express based host connectivity approach. Three (four) XIO2213B 1394b LLC chips are connected to a PCI Express switch. This concept allows using the latest PCIe based OHCI LLC technology.
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.
*) Depending on exact model
| Dimensions: | Half-length, full-height x4 PCIe | |||
| Weight: | 200g | |||
| Power Requirements: | PMC: 3.3 V, 6.6 W max | |||
| Regulatory Compliance: | FCC Class A, CE | |||
| Connections: |
PCI Express 2.0 x4 3x SFF-8614 connectors for transformer-coupled 1394b ports |
|||
| Indicators: | - | |||
| Switches: | dip switches for PHY port mode programming | |||
| Part Number: |
FA3424bT-OPT1-OPT2-OPT3 FA4424bT-OPT1-OPT2-OPT3 |
|||
| Options: | OPT1: Operating System
WIN – MS WindowsTM |
OPT2: Personality Profile LLP – Low Level Profile |
OPT3: Extended Warranty SS - SW extended Warranty |
|
| Codes: |
ECCN:3A992.a HTS: 8471.90.0000 |
|||
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.
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.
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 (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.
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.
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.
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.
The following accessories are available for this product:
In order provide a wide variety of connectivity options – either to additional FireAdapters 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.
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Termination 2: |
Length: |
|
The harnesses above are also available in 10ft, 15ft, 20ft and 50ft variants. Warning: The usage of the SFF connectivity in this harness is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac. |
|||
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Connections: |
Length: |
|
SFFDongleAD&BC |
SFF-8614 | Port Ax connected to Port Dx Port Bx connected to Port Cx |
- |
|
SFFDongleAB |
SFF-8614 | Port Ax connected to Port Bx |
- |
|
SFFDongleAC |
SFF-8614 | Port Ax connected to Port Cx |
- |
|
SFFDongleBC |
SFF-8614 | Port Bx connected to Port Cx |
- |
| Warning: The usage of the SFF connectivity in this device is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac or FireAdapter. | |||
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Termination 2: |
Length |
| SFF5F4SFF SFF5F3SFF |
as above | as above | 5 feet |
|
The harnesses above are also available in 3ft, 7ft,10ft, 15ft, 20ft and 50ft variants. Warning: The usage of the SFF connectivity in this harness is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac. |
|||
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Termination 2: |
Length |
|
The harnesses above are also available in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants. Warning: The usage of the SFF connectivity in this harness is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac. |
|||
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Termination 2: |
Length |
| SFF5F4LEF SFF5F3LEF |
SFF-8614 | 4x LEMO female 3x LEMO female |
5 foot |
|
The harnesses above are also available in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants. Warning: The usage of the SFF connectivity in this harness is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac. |
|||
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Termination 2: |
Length |
|
The harnesses above are also available in a 10ft variant. Warning: The usage of the SFF connectivity in this harness is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac. |
|||
|
For Product(s): FireTrac4x24bT, FireTrac3x24bT, FireAdapter4424bT, FireAdapter3424bT |
|||
|
Part number: |
Termination 1: |
Termination 2: |
Length |
| SFF5F4MIF-... SFF5F3MIF-... |
SFF-8614 | 4x 38999* female 3x 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 available in 1ft, 3ft, 7ft, 10ft, 15ft, 20ft and 50ft variants. Warning: The usage of the SFF connectivity in this harness is tailored for IEEE1394 and has a non-standard pinning. It shall only be used in combination with FireTrac. |
|||
Please note that cables for this product need to be purchased separately.
Typically 4 weeks. Please contact sales(at)daptechnology.com for more detailed information.
Standard: 48 months, limited.
Options: Additional 1-year SW/FW Support packages may be purchased.
All products will be supported on a 24 hours response basis and free of charge during the warranty period. For support questions please contact: sales(at)daptechnology.com
Of course you can also call us during our office hours from 9:00 until 17:00 hours (GMT +1:00). Contact Info
For those educational institutions that would like to use our high-specification IEEE-1394 analyzer for educational purposes only, we have a special discount offer. Our FireSpy® software which runs automatically in demo-mode without the use of a FireSpy® has great educational properties. This software can be used for free by everyone and is of great value for learning IEEE-1394. In order to obtain more details about this offer, please contact: sales(at)daptechnology.com
Please contact sales(at)daptechnology.com for current pricing.
| Country | Distributor | Phone | URL |
|---|---|---|---|
| China | BEIJING CESITEK CO., LTD. | +86 10 84177715 | www.cesitek.com |
| Japan | Nacelle Co. Ltd. | +81-3-5921-5099 | www.nacelle.co.jp |
| United States of America | DapUSA, Inc | +1 480 422 1551 | www.dapusa.com |
| South Korea | Realtimewave Co. Ltd. | +82-31-698-2980/2 | www.realtimewave.com |
| all other countries | Dap Technology B.V. | +1-514-453-4111 | www.daptechnology.com |
Click here for a more detailed listing of our Sales Representations.
For the U.S.A., we have as representatives:
| Representative | Territory | Phone | URL |
|---|---|---|---|
| Dap USA Office Arizona | Entire United States of America | +1 480 422 1551 | www.dapusa.com |
To place an order for DapTechnology products, please print one of the following order forms and email it to the corresponding email address:
USA:
Dap USA, Inc.
sales(at)dapusa.com
Download order form
Or contact us by phone: +1 480 422 1551
Rest of the world:
Dap Technology B.V.
sales(at)daptechnology.com
Download order form
Or contact us by phone: +1 480 422 1551
