KAD/FBM/105 - 1 channel Multi-rate FireWire Bus Monitor
- REQUEST A QUOTE
- Monitors an IEEE 1394b S100b, S200b, S400b bus
- Coherently parses traffic and tags
- Supports 511 (1k), 256 (2k) or 128 (4k) messages (including one catchall slot)
- Parser discards bus configuration, PHY packets and other synchronous packets (except traffic with transaction code 0xA)
- Provides transaction counters and error detection
- FireWire beta mode bus monitoring
Setting up data acquisition systems can take a lot of time and effort, particularly as many systems today are growing larger and larger. Managing thousands of channels of data over dozens of data...
The KAD/CBM/103 extracts valid CCDL/MCDL messages from incoming serial streams. It coherently extracts certain words from these messages and saves them to specified locations in the telemetry...
The KAD/FBM/102 is designed to monitor IEEE 1394 (FireWire) traffic, parse and tag packets, and distribute the monitored packet contents to other KAM-500 modules. The KAD/FBM/102 acts as a leaf in...
The KAD/FBM/103 monitors FireWire (IEEE 1394b) traffic. It acts as a leaf in the FireWire bus topology and to all other nodes on the bus, the link layer and transaction layer appear to be...
1 channel Multi-rate FireWire Bus Monitor Parser
The KAD/FBM/105 acts as a leaf in the FireWire bus topology. To all other nodes on the bus, the link layer and transaction layer appear deactivated.
The KAD/FBM/105 parses isochronous or asynchronous stream packets; all other traffic (configuration traffic, PHY packets, and asynchronous transactions) is ignored. Selected packets and associated tag information are stored in triple buffered parser slots. The size of the parser buffer, and consequently the number of parser buffers, can be adapted to each application, depending on the rate and the maximum size of the data payload. If the maximum data payload is up to 1,024 bytes, 511 parser slots are available; if it is 2,048 bytes, 256 parser slots are available; and if it is 4,096 bytes, up to 128 parser slots are available.
FireWire packets are parsed in two stages. First, packets are filtered to accept only isochronous and asynchronous stream packets (traffic with transaction code 0xA). Then the isochronous packet header quadlet, and five quadlets of the FireWire packet data payload, are used to classify the packet and determine which of the parser slots the packet is written to. At S100b, the packet must be at least 13 quadlets (52 bytes) long. At S200b, the packet must be at least 21 quadlets (84 bytes) long. At S400b, the packet must be at least 41 quadlets (164 bytes) long. Packets smaller than these are dropped. Packets received within 2.2 μs (S200b) or 3.2 μs (S400b) after an STOF packet are dropped. (An STOF packet is 13 quadlets long and has a 0X00281FA0 header.)
Contact our sales team today to learn more about our products and services.
Our support team can help answer your questions - contact us today.