High-Level Protocol Support

DapTechnology offers a series of highly integrated protocol decoding add-ons which greatly enhance the standard analysis and testing capabilities of the FireSpy data analyzers. Once the basic 1394 protocol has been mastered, typical analysis, debugging and testing requirements transition quickly into the protocol layer. Without proper tools this can be a painful and very time consuming task.

As an added benefit, a separate application (Format Editor) allows for the modification and extension of the factory default decoding and identification definitions. This extremely powerful and versatile tool enables experienced users to build on top of the standard definitions, engage in early prototyping and benchmarking of protocols still in the specification development process, as well as add proprietary extensions.

The different protocols require very different implementation details and are therefore very unique in their implementation. However, some key characteristics can be identified and are listed below:

Key Features

  • Nested protocol header decoding
  • Protocol payload separation
  • Handshake verification
  • Logical grouping of related transactions
  • Separate protocol view
  • Protocol layer CRC and Parity Check verification
  • Handshake timing analysis (in combination with Time View)
  • Customization of display details

Screenshots

AS5643 / Mil1394 Protocol Suport

The AS5643 protocol has been developed by the SAE in order to address the unique requirements of the usage of IEEE-1394 in aerospace and avionics. The AS5643 standard has become the main focus of FireSpy protocol layer support and is present in most of the FireSpy functional modules. In certain instances DapTechnology also uses the trademarked term "Mil1394". Mil1394 refers to a feature and functional set that goes beyond the current definitions within AS5643. Mil1394 is compatible with AS5643 yet targets to make the usage within A&D even easier.

The Mil1394 protocol add-on adds the following functional modules to the FireDiagnostics Suite software:

In addition to the above added functional modules, the Mil1394 Protocol add-on also extends the other FireSpy modules with AS5643-specific functionality. For example, the Recorder is extended with the following features and similar extensions are available within the other components as well.

The Mil1394 Recorder includes a 12.5 ms time slot visualization in the Recorder Time View, the grouping of asynchronous stream packets by channel numbers, time slot analysis referencing STOF timing, remote node name assignment based on transmit/receive offset specification, etc...

Recorder extended packet verification includes:

  • Heartbeat check
  • Vertical Parity Check
  • Payload Length Check

Other Protocols Supported

SBP2 Protocol

The SBP (serial bus) protocol is predominantly used for IEEE-1394 storage applications which utilize this protocol for the encapsulation of other command-based protocols and require the movement of large blocks of data. Examples of such encapsulated commands are the SCSI command sets. The following specification is supported by the FireSpys: ANSI NCITS 325 1998

AV/C Protocol

The AV/C (Audio Video Command Set) specifications have been developed within the 1394 Trade Association. The General Specification defines a framework for control and status commands targeted at audio/video devices using IEEE 1394. It is based on the Function Control Protocol (FCP) defined in IEC 61883-1. Beside the General Specification numerous specifications for AV/C sub-units have been developed.

IIDC Protocol

The IIDC (Industrial and Instrumentation Digital Camera) specification was developed within the 1394 Trade Association in order to standardize the control command set for industrial cameras. It is important to understand that this specification is not used for commercial camcorders.

IP4 Protocol

The IP1394 specification was developed within the IETF (Internet Engineering Task Force) in order to define how to use IEEE 1394 for the transport of Internet Protocol Version 4 (IPv4) datagrams; it defines the necessary methods, data structures and codes for that purpose. These include not only packet formats and encapsulation methods for datagrams, but also an address resolution protocol (1394 ARP) and a multicast channel allocation protocol (MCAP). Both 1394 ARP and MCAP are specific to Serial Bus; the latter permits management of Serial Bus resources when used by IP multicast groups.

AMI-C Protocol

AMI-C 1394 specifies requirements for implementing a vehicle interface that enables devices (i.e. mini disk players, compact disc players, audio processors, DVD players, digital video camcorders, etc.) to access and communicate with an automaker’s proprietary vehicle network. The AMI-C specifications allow for flexible application design and support expandability and upgradeability options.