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.
- Monitors up to a single IEEE 1394b compatible bus at a signal rate of 200Mbps (S200b) using a transformer-coupled interface
- Coherently parses isochronous and asynchronous stream packets and tags for up to 65 messages using the Channel ID/Message ID
- Maximum payload size of 2KB per packet
- Discards other asynchronous, bus configuration and PHY packets (except traffic with transaction code 0xA)
- FireWire beta mode bus monitoring
KAD/FBM/103 1 channel Firewire Bus Monitor
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 deactivated. The KAD/FBM/103 parses isochronous or asynchronous stream packets. All other traffic is ignored (configuration traffic, PHY packets, and asynchronous transactions). Selected packets and associated tag information are stored in one of 65 triple-buffered parser slots. Each parser slot contains up to 1036 16-bit words: 1030 words of packet content; three words of timestamp information; one word containing the transaction number; one word containing the packet size; and one word containing buffer information.
FireWire packets are parsed in two stages. First, packets are filtered to accept only isochronous and asynchronous stream packets (traffic with transaction code A16). Then the channel ID and message ID (third quadlet in the FireWire packet) are used to classify the packet and determine which of the 65 parser slots the packet is written to. Unique channel ID and message ID combinations can be targeted to any of the 64 available parser slots. Parser slot 0 may be configured to operate as a "catch all" slot where any channel and message IDs not mapped to specific parser slots will be routed.
Aerospace Instrumentation Brochure
Modern aerospace instrumentation systems can be highly complex, and it can be difficult to know how to meet program needs. It’s not unusual for requirements to change during a campaign and cause significant delays, and data must be captured reliably no matter what – otherwise expensive additional flights will be needed or months of program data could be lost. Read our brochure to learn how you can reduce your risk with commercial off-the-shelf (COTS) solutions.