DAP Technology 1394 Operation Manual

Hardware and software guide

page of 458

/ 458
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

1394 Analyzer Operation Manual

Hardware and Software Guide

Doc #: DT-PRO134MAN700E

Table of Contents

Need help?

Do you have a question about the 1394 and is the answer not in the manual?

Questions and answers

Summary of Contents for DAP Technology 1394

Page 1 1394 Analyzer Operation Manual Hardware and Software Guide Doc #: DT-PRO134MAN700E...
Page 2: Table Of Contents
1394 Analyzer Operation Manual Table of Contents Chapter 1. Introduction Chapter 2. Installation 2.1 Windows ........................... Installing the Software ....................................13 Installing the Driver ....................................17 Windows Driver installer ................................. 17 Older Windows versions ............................20 Manual driver (un)installation ................................. 24 Ethernet Configuration ....................................
Page 3 1394 Analyzer Operation Manual Triggering ................................. 65 Marking packets ................................. 66 Details ....................................66 Menus ................................. 66 Toolbar ................................. 72 Scriptable Export ................................. 73 Standalone Recorder ....................................75 Multi-FireSpy Synchronized Recorder ................................. 76 7.2 Time View ........................... How to use it ....................................
Page 4 1394 Analyzer Operation Manual Export Recorder Data ....................................122 Play Regeneration File ....................................123 8.2 Details ........................... Toolbar ....................................123 Bus settings ....................................124 Chapter 9. Symbol Recorder 9.1 Main Window ........................... How to use it ....................................126 Display Symbol Recorder Files .................................
Page 5 1394 Analyzer Operation Manual 11.1 Main Window ........................... 11.2 Script Editor ........................... Toolbar ....................................157 Context menu ....................................157 Status Bar ....................................158 Property Editor ....................................158 Statement ................................. 159 Declaration ................................. 159 Loop Statement ................................. 159 Conditional Statement ................................. 159 Function Declaration .................................
Page 6 1394 Analyzer Operation Manual Chapter 12. Filter/Trigger 12.1 How to use it ........................... Trigger ....................................204 General Trigger ....................................206 Filter ....................................207 Packet Sets ....................................208 12.2 Details ........................... Menus ....................................210 Trigger ....................................211 General Trigger ....................................224 Filter ....................................
Page 7 1394 Analyzer Operation Manual Toolbar ....................................271 Relations Pane ....................................272 Details Pane ....................................273 Transactions and packets pane ....................................276 IIDC Protocol Settings ....................................276 Chapter 15. Audio Video / Control protocol (AV/C) 15.1 Recorder Protocol View ........................... How to use it ....................................
Page 8 1394 Analyzer Operation Manual transactions and packets pane ................................. 323 AMI-C-Protocol Settings ................................. 324 18.2 Editing AMI-C Formats ........................... Example ....................................326 Chapter 19. Custom Protocols 19.1 What is it ........................... 19.2 How to use it ........................... 19.3 Details ...........................
Page 9 1394 Analyzer Operation Manual Chapter 22. Protocol Editor 22.1 How to use it ........................... 22.2 Details ........................... Caption Bar ....................................365 File Menu ....................................365 Protocol name & identity ....................................365 Address ranges ....................................366 Fixed channels ....................................367 Chapter 23. File Formats 23.1 Hex Data file...
Page 10 Main Feature Summary ....................................442 Specifications ....................................444 FireSpy 1600,3200 ....................................444 FireSpy Front ................................. 444 FireSpy Rear ................................. 445 24.6 Basic 1394 Analyzer Series ........................... Main Feature Summary ....................................446 Specifications ....................................448 FireSpy 400b ....................................449 FireSpy Front ................................. 449 FireSpy Rear .................................
Page 11 1394 Analyzer Operation Manual The SCSI2 Connector ....................................456 The SUBD connector ....................................457...
Page 12: Chapter 1. Introduction
Introduction Chapter 1. Introduction Welcome to the 1394 Analyzer Operation Manual . For a quick start, please read the Getting Started chapter. If you need help installing the software, please refer to the Installation chapter. The analyzer software contains the following functionality, which is explained in the corresponding chapters of the FireDiagnostics Suite Manual.
Page 13: Chapter 2. Installation
Installation Chapter 2. Installation DapTechnology analyzers are not packaged with any software-installation media. This is because we would like our customers to use the very latest software available and not an old version that happened to be the latest when we packaged the product. You will be able to download the latest software version from our website: http://www.daptechnology.com Click on the support button at the top of the web page and after inserting the serial number of your...
Page 14 Installation After clicking on "Next", the following window will be showed. It contains the License Information for the software you are about to install. Please read it carefully and check the checkbox to agree to the license agreement before proceeding to the next step. If you are installing a beta software version, an additional license agreement needs to be agreed with before continueing the installation process.
Page 15 Installation The installer options dialog as shown below allows the user to select which components to install. We recommend installing all components, however it is also possible to leave some components out. If another FireDiagnostics Suite installed version with the same main version number is found it needs to be reinstalled before the installer is able to continue.
Page 16 Installation The following dialog will show uninstallation progress. Please wait until it finishes. The following dialog will show installation progress. Please wait until it finishes. After the installation is complete, the following dialog will appear. We recommend to always restart your computer after installing the FireDiagnostics software.
Page 17: Installing The Driver
Installation 2.1.2. Installing the Driver The driver installation will automatically start following the FireDiagnostics Suite installation, after the machine is rebooted. This installer will install the drivers for Windows 7 and Windows 10. Older Windows versions still work with the supplied drivers, but some additional steps may be required during installation. These steps are described in chapter Older Windows versions.
Page 18 Installation After clicking "Next", the drivers will be installed. Please wait until it finishes. After the drivers are installed the following window will be showed. Click "Finish" to close the installation. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 19 Installation After your are booted to the desktop, you may check the device manager if the install has succeeded. The device manager will show a FireSpy under "Multifunction adapters". Here you find a several functions the device has. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 20: Older Windows Versions
Installation 2.1.2.1.1 Older Windows versions For Windows versions older than Windows 7 some additional steps during the Driver installation may be required. After the FireDiagnostics Suite installation, and after rebooting the machine, the Driver installer will start. During the installation the Windows Driver Wizard may appear, as shown in the following image. Please click "Cancel"...
Page 21 Installation At the start of the installation the following message may be displayed, saying the software has not passed Windows Logo testing. The FireSpy Logo testing is not supported for Windows versions older than Windows 7, but function on these Windows version regardless. Click "Continue Anyway" to continue with the installation.
Page 22 Installation After the drivers are installed the following window will appear. Click "Finish" to continue starting Windows. Any devices that were connected to the machine during the installation should work now. If there were any unplugged devices, please connect them to the machine now. The Windows Driver Wizard mentioned earlier should appear now.
Page 23 Installation After clicking "Next" the Wizard will install the driver for the FireSpy device. Repeat this process for any additional FireSpy device that was not yet correctly installed during the installation. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 24: Manual Driver (Un)Installation
Installation 2.1.2.2. Manual driver (un)installation Drivers will be uninstalled when uninstalling the FireDiagnostics Suite. The uninstaller can be found in the Windows Start menu, under FireDiagnostics Suite x.x -> Uninstall FireDiagnostics Suite (for Windows 10), or FireDiagnostics Suite x.x -> Administration -> Uninstall FireDiagnostics Suite (for older Windows versions).
Page 25: Configuration Steps Firespy Application
Installation Step 5 Wait until the firmware is written. Switch off the power and disconnect USB. Switch on the power and verify that led ‘init’ is on and turns off in about 8 seconds. If so the FireSpy x810 is configured successfully. Otherwise please repeat the above steps. The FireSpy x810 is now able to start-up autonomously from flash.
Page 26 Installation Step 2 From the "Tools" menu open ‘Settings’ and click on item ‘LAN Devices. Step 3 See figure below. Click ‘Add Host address...’ and fill in either the IP number or the DNS host address that is routed to the FireSpy. Make sure the address is valid and click ‘Ok’ when finished. Step 4 Now press the apply button and close the dialog.
Page 27: Chapter 3. Getting Started
Getting Started Chapter 3. Getting Started This section of the manual provides a quick-start guide for your analyzer and software. If you need help installing the application, please take a look at the Installation. 3.1. Starting the Application If you haven't already done so, install the software as described in Installation. Make sure the devices are properly installed in or connected to the computer, have a matching power source and are turned on (where applicable).
Page 28 Getting Started No Devices Shown - IMPORTANT NOTICE In case you are sure a FireSpy is properly connected but it is not shown in the Device Selection dialog, it may be needed to manually install the drivers. This could also be needed when multiple versions of the FireDiagnostics Suite are installed and you want to switch between them.
Page 29 Getting Started License Management You can enter the license configuration mode by clicking the toolbutton with the key icon, and go back to the device information mode by clicking it once again (or by clicking the 'Done' button). The license configuration mode shows the main license validation number and the licensed modules and their respective keys.
Page 30 Getting Started After Device Selection If you installed the drivers correctly, the application will recognize the connected analyzer and start configuring it. After configuration, the analyzer is ready for use, the Main Window will be displayed. Multiple Applications Using the Same Analyzer It is possible to open the same analyzer from within different applications, however, all main functions like the monitor, recorder, e.o.
Page 31: Main Window
Getting Started You may now connect the power supply and/or switch the power on, and try again. Or you may choose to run the application without an analyzer. 3.2. Main Window The main window consists of the menus and the control area. Below is a screenshot of the main window without a FireSpy connected.
Page 32 Getting Started Selecting 'Analyzer Info' from the Help menu opens a window with information about the analyzer(s) currently in use: Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 33: Connecting To An Ieee1394 Bus
Getting Started Controls The windows for the main functions (Monitor, Recorder, Generator, Commander and Scriptor) can also be opened by clicking on the corresponding button. The button will be highlighted when the mouse is positioned above it. The led in the left-bottom corner will display the current configuration status. It can be: ·...
Page 34: Command Line Options
Getting Started packets, but it does not know at which speed the packet has been sent or how many bytes it consists of. If you see the Monitor Recorder detecting these packets, you can take a look at the topology view in Commander to find the problem.
Page 35 Getting Started Multiple standalone FireSpy tools can be started at the same time, but each module can only be started once per FireSpy. The following standalone FireSpy tools allow controlling multiple FireSpy devices from within a single application: · Recorder ·...
Page 36: Chapter 4. License Manager
Any existing keys for the same serial number and module will be permanently overwritten. Please contact DAP Technology to obtain additional license keys. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 37: Chapter 5. Monitor
Monitor Chapter 5. Monitor The Monitor gives a quick indication of bus activity. The Monitor displays the number of packets passed on the bus and some additional events. The packets are differentiated to speed and type, including all isochronous, asynchronous, phy packets and acknowledge packets types. Also the number of packets with different kinds of errors and the IEEE1394 bus voltage are monitored and displayed.
Page 38 Monitor File Menu Export... The export menu allows for saving current counter values to an external file. The file will be stored as a comma seperated spreadsheet (csv) including column headers. Tools menu License Manager The license manager can be opened when running the monitor in the standalone version. The Monitor that is integrated within the application will not have this option.
Page 39 Monitor This option will open the settings dialog. The Monitor can use alternate device and/or bus names, they can be changed on the alias tab. (See screenshot) Window Configuration The Monitor can use quite some desktop space, to reduce this space you can make a selection of the monitor groups you want to monitor.
Page 40 Monitor Bus Configuration The Bus Configuration dialog has two functions; reorder the busses and most important, select how to display incoming and/or outgoing packets. For stealth analyzers it indicates packets going from 'pipe A to B' or from 'pipe B to A'. As a user you have four options: -Receive.
Page 41: Details
Monitor Buttons Pause/Resume display Pressing this button will hold the updates to the monitor. When pressed again the updates will resume. Note that only the display is paused, not the monitoring itself. Clear When this button is clicked all packet and event counters described above will be cleared and start counting from 0 (zero) again.
Page 42: Multi-Bus Version
Monitor Errors The Errors box gives the user a quick indication of the existence of erroneous packets. It handles the following kind of errors: Data CRC error All packets that have a data block and with an error detected in the data CRC are counted here. Note that only packets that have a valid header (correct header CRC and valid tcode) can have a data block, and thus packets with data CRC error are not counted as 'error' packets in the Packets section.
Page 43 Monitor Node Selection If the Monitor is used in multi-bus setup, it is possible to show the counters for just one node or several nodes at once. The toolbar contains the following control to select which nodes to display. By clicking on the "a", "b" or "c" button, the corresponding node can be hidden or shown. A red background color means it is visible, a white background color means it is hidden.
Page 44: Chapter 6. Commander
Commander Chapter 6. Commander The Commander has four separate functions: The 'Topology' is used to display the current bus topology with, optionally, more-detailed information about the nodes. Depending on node capabilities, one can suspend, resume, disable and enable a node. One can also generate bus resets here and display the new bus topology.
Page 45: Topology
Commander 6.1.1. Topology Select the topology page if you want to display the current bus topology. When connecting or disconnecting nodes, you will see the topology picture change, reflecting the changed bus topology. See above for an example of the Topology page. With the 'Detailed view mode' button you can toggle between detailed and compact view mode.
Page 46: Memory Read/Write
Commander If the software encounters violations of the CSR specification while parsing the Configuration ROM, these entries will be displayed in orange. Note: The 'Root Directory' will not be displayed if there is no license key available for the version 2 software (see License Manager).
Page 47: Packets Send/Receive
Commander To perform a lock operation, check the 'Lock Oper.' check box. Because lock operations can only be performed on one-quadlet or two-quadlet data, the length changes to 1 or 2 quadlets. The data table now has a data and an argument column, because some lock operations need data and arguments. You can specify the kind of lock operation to be performed using the popup box with the possible lock operations.
Page 48: Phy Register Read/Write
Commander The send packet will be sent when you press the 'Send' button. If an acknowledge has been received for the packet, it will be displayed left at the bottom of the page. If retry is enabled, the packet will be retried up to 15 times if needed. The packet is retried if the target node did not respond with an acknowledge, or if it is acknowledged with an ack_busy or ack_tardy code.
Page 49: Details
Commander If you want to change a value, change it in the field list and press the 'Write Changes' button. As soon as a value has been changed by the user, but has not been written yet, the changed field will be displayed in red and the 'Write Changes' button will be enabled (see example above).
Page 50: Topology
Commander The following sections describe the details per tab page of the Commander. 6.2.1. Topology The 'Topology' page consists of a toolbar, the topology picture and optionally extra bus and node information. Toolbar The toolbar has the following buttons: Detailed view mode This is a toggle button.
Page 51 4), one port has been disabled, recognizable by it's yellow color, and a tooltip is show for another port. The ports of the harddisk are black: it's PHY registers cannot be read because it is a 1394-1995 device. Note: The 'Root Directory' will not be displayed if there is no license key available for the version 2 software (see License Manager).
Page 52: Memory R/W
Commander Active Configuration Rom and Bus_Manager_ID reads If Configuration-Rom information of some node or the Bus_Manager_ID register value is needed, the Analyzer will read it actively. It will only use quadlet read transactions. If the ‘node display options’ that are retrieved from the Bus_Info_Block are all disabled and if the ‘Bus and node information’...
Page 53 Commander In the case of broadcasts, only write actions will be possible. Node If 'broadcast' is not checked, you can select a node from this popup list. The nodes in this list will consist of all nodes connected to the bus if the local bus is specified (local checked), otherwise it will be a list of all possible node Ids (0 to 62).
Page 54 Commander Because lock operations can only be performed on a data size of 1 or 2 quadlets, the length will automatically change to 1 or 2 quadlets. The data table will get an extra 'Lock Argument' column, because some lock operations need a data value and an argument value for each address location. Finally, when checking this box the popup list to specify a lock operation will be enabled.
Page 55: Packets S/R
Commander 6.2.3. Packets S/R The 'Packets S/R' page consists of the following parts: · send packet (everything left from the middle) · receive packet (everything right from the middle) send packet This part consists of the 'Send' button, 'Retry enable' check box, the 'Packet to Send' box that defines the packet to be sent, and the 'Acknowledge after Send' box.
Page 56 Commander the ack_tardy code, the packet will be retransmitted, up to 15 times. If the send fails a message is displayed with information about the failure. Send Multi If this button is pressed, a dialog pops up prompting the user to enter the number of times the packet will be sent: If the user enters a number equal to, or bigger than 1, and presses 'OK', the application proceeds to send the packet the selected number of times in rapid succession.
Page 57 Commander Layout The same fields displayed in the 'Fields' page are displayed in the 'Layout' page. But now the layout of the packet is shown. Each line shows 32 bits, or one quadlet. The exact bit position of each field is shown, including the field name (mostly some abbreviation because of space limitation) and the value.
Page 58 Commander Acknowledge after Send If the transmitted packet is acknowledged, the acknowledge code is displayed here. If the packet is retransmitted, and acknowledged again, the last acknowledge code will be displayed. receive packet This part consists of the 'Wait for response (if pending)' checkbox and the 'Received Packet' box that displays the received packet.
Page 59: Phy Register R/W
Commander Layout The same fields displayed in the 'Fields' page are displayed in the 'Layout' page. But now the layout of the packet is shown. Each line shows 32 bits or one quadlet. The exact bit position of each field is shown, including the field name (mostly some abbreviation because of space limitation) and the value.
Page 60 Commander register layout This part (most left) displays the layout of the selected register set. All phy registers are arranged in bytes. One byte can hold several fields and one field may occupy several bytes. The field names and values are included in the layout picture.
Page 61 Commander The Analyzer can only read the local phy registers or the phy registers from remote nodes that comply with the IEEE1394a standard. If the read could not be performed, an error message will be displayed, and no data will be displayed. Write box The write box has only one button: Write Changes...
Page 62: Chapter 7. Recorder
Recorder Chapter 7. Recorder Packets and events can be stored in the internal memory and viewed later, using a number of possible Views, using the Recorder. All Views can be switched on or off individually. 'Time View' enables the user to view the timing of events and packets (including acknowledge packets and the packet prefix) at a resolution of about 20nS for a FireSpy400 and 10nS for a FireSpy800.
Page 63: How To Use It
Recorder The window is filled with different kinds of views for the recorded data. You can switch them on and off or dock/undock them. The Time View is always displayed (if enabled) at the top. If a protocol view is switched on, it is showed at the bottom of the window.
Page 64 Recorder Now you see the 'Time View' and 'Packet View' both display the data. In the example window below, the Packet View is disabled and the 'Time View', 'Topology View' and 'Transaction View' are enabled. You can use the 'Recorder' menu or toolbar buttons to record packets into internal memory of the Analyzer, and download them to the host.
Page 65: Record Packets
Recorder which can be used to save a selection of packets as a text file or as Packet file. A Packet file can be used in the (isochronous) Generator. 7.1.1.2. Record Packets If the internal recorder memory of the Analyzer is empty, you can start recording by selecting the 'Start' command from the 'Recorder' menu, or clicking the 'Start Recording' button in the toolbar.
Page 66: Marking Packets
Recorder The hardware-trigger logic will be described in full detail in 'Filter/Trigger'. Each time you start the Recorder, a check is made if the user changed some settings in the Filter/Trigger Settings window. If so, the user will be asked if these changes need to be activated or ignored before starting the recording.
Page 67 Recorder It has the following parts: · Script Generator: All export functions, regardless of the pre-defined (the options described in the Save As pane) or customized, work based on scripts running behind this dialog. If you need to modify a pre-defined or customized script, you will need click on the "Edit Script" button in this pane.
Page 68 Recorder attached as the last column title and one column of hex data represents one quadlet data in the data payload. · Hex file (*.hex): A file in this format can be imported by the Generator. The format is described Hex Data file.
Page 69 Recorder The dialog consists of the following parts: · Unmark others: If this box is checked (default) only the packets selected by the dialog will be marked and all others will be unmarked. If this box is not checked the packets selected by the dialog will be marked additionally to the already marked packets and events.
Page 70 Recorder This dialog looks almost the same as the mark dialog above. The only difference is that the 'unmark others' checkbox is missing and there is an 'Unmark" button instead of the 'Mark' button. The initial values are different in the example above because apparently an asynchronous packet with source local:0 and destination local:1 was selected when this command was invoked.
Page 71 Recorder When one or more packets are marked, you can use these commands to select the indicated packet. For the 'Go to previous Mark' and 'Go to next Mark' there are also corresponding buttons in the Packet View toolbar (see below). Go to packet number ...
Page 72: Toolbar
Recorder checked, otherwise there is no limit and process has to be stopped manually using 'Stop' button. First recording will start when you press 'Start' button and the rest will be done automatically. Each recording ends after a trigger, which you can configure using 'Trigger Settings...'. View With this menu you can enable and disable the different kind of Recorder views: ·...
Page 73: Scriptable Export
7.1.2.3. Scriptable Export The Export functionalities have been greatly enhanced by adopting Dap Technology's proven technology: the scripting features that have been utilized in the Scriptor. The scripting engine for the Export functions runs on a host computer along with other Analyzer application components while the engine for the Scriptor runs on a RISC processor embedded on an Analyzer analyzer.
Page 74 Recorder code will be generated, compiled and executed. You can browse and modify actual script source code by either selecting one of the pre-defined file format or opening an external export script file (*.fes extension), and then click on the "Edit Script" button at the upper-right hand corner of the dialog.
Page 75: Standalone Recorder
Recorder The above picture shows the actual script source code for the Binary file option. This script is the least complex one among all pre-defined options. In this example, the script performs: 1. Sets the filter mode for traversing packets in the Recorder memory. (Marked is selected in the default dialog above.) 2.
Page 76: Multi-Firespy Synchronized Recorder
Recorder The standalone recorder can be started with the following command line options: USAGE RecorderApp [-h] or [/?] Shows command line usage RecorderApp [options] [file] [commands] Recorder is run is a specific mode, on a specific device to start a recording or to open a recording. OPTIONS -d --device serialnumber Opens the device which is identified by serialnumber.
Page 77 Recorder The picture below shows the option to select multiple FireSpys. Please ensure to only select multiple FireSpys that are actually time-synchronized. Otherwise, the application will exit with an error. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 78: Time View
Recorder When multiple analyzers are properly synchronized then they can be controlled as one large FireSpy with many buses just as normally is done controlling a single FireSpy. The following picture shows the Recorder when 3 triple analyzers are open and a Recording was made with only 6 out of 9 buses selected. 7.2.
Page 79: Details
Recorder At the top of the view you see a toolbar with some buttons and controls like zoom in and zoom out buttons, the cursor time indicator and buttons to quickly find other packets of the same type as the current selected one or packets with errors.
Page 80 Recorder When the cursor is moved now, the position of the old cursor (the reference) is indicated with a dotted line and a horizontal line with arrows is drawn between this reference and the new cursor position. See the time view above for an example. The time in the 'Cursor time' box indicates the length of the horizontal line, or the time between the old and the new cursor position.
Page 81: Packet / Event Display
Recorder It contains the following additional control: View This control van be used to select the Analyzer nodes to view information for. By clicking on the "a", "b" or "c", the corresponding nodes can be hidden or shown. A red background indicates a node is shown. A white background indicates a node is hidden.
Page 82: Topology View
Recorder recorder filter logic can be instructed to store these events. See Filter/Trigger for more details. The example below shows the events described above. The Phy-Interrupt events are displayed at the position where the link interface signals a phy interrupt. By default this events is not stored when recording, but the recorder filter logic can be instructed to store the events.
Page 83: How To Use It
Recorder An optional pane can be switched on to display additional bus and node information. This information will be derived from recorded CSR register reads. For each node all Configuration-ROM reads will be collected and the contents of the Configuration ROM will be reconstructed if possible. 7.3.1.
Page 84 Recorder Using the 'Bus and node information' button (right button in Topology Toolbar) you can display additional bus and node information. In the example below this option is swithed on. The extra node information corresponds to node 5, the selected node. Copyright ©...
Page 85: Details
Recorder The extra node information consists of information from the selfIDs from this node and information from the Configuration Rom of this node. For values that could not be found (no read of the corresponding Configuration ROM address recorded) a '?' will be displayed. 7.3.2.
Page 86 Recorder The information for the upper options is retrieved from the selfID(s) of the corresponding node. The information for the lower options are retrieved from the Bus_Info_Block of the CSR Rom. This information will only be displayed if it can be found. See below for more information about this. Below is an example of the topology view with the options enabled as shown in the 'Topology Options' dialog above.
Page 87 Recorder Bus and node information This is a toggle button. When this button is pressed, extra bus information and node information of a selected node will be displayed. Below is an example of the topology view, with the 'Bus and node information' button pressed, and with node 0 selected.
Page 88 Recorder Note: The 'Root Directory' will not be displayed if there is no license key available for the version 2 software or higher. See License Manager. Triple Analyzers For triple Analyzers, the toolbar looks as in the following picture: It contains the following additional control: View This control van be used to select the Analyzer node to view information for.
Page 89: Topology Picture
Recorder 7.3.2.2. Topology picture The topology can only be drawn if valid topology information can be found for the cursor position. Valid information can be found if the cursor is positioned at or after a bus reset that is followed by all the PhySelfID packets that are needed to create the topology.
Page 90: Packet View
Recorder more topology changes. The recorder will search for recorded bus transactions that will give more information about the Configuration ROM and Bus_Manager_ID register. It searches for read transactions of the Configuration ROM and for lock transactions on the Bus_Manager_ID register. It will search, starting with the last reset event before the current cursor position until the next reset event or until the end of recorded packets.
Page 91: Details
Recorder details on the right. Those optional details can be enabled and disabled with the right-most button on the toolbar. Selecting a packet in the table will display the details of that packet in the (optional) details part and will also select the corresponding packet or item in all other views of the Recorder.
Page 92: Packets/Events Table
Recorder a packet is present. Go to next packet of same type When clicking this button, the next packet of the same type will be selected. It will be enabled if such a packet is present. Go to previous packet with error(s) When clicking this button, the previous packet that has one or more errors will be selected.
Page 93: Packet Details
Recorder The size column displays the total packet size expressed in bytes. If the packet size is not a whole number of bytes, which is an error condition, the number of whole bytes is displayed plus the '+' sign. Thus a packet of 27 bits has a size of '3+'. The exact number of bits can be found in the details area, using the 'Layout' page.
Page 94 Recorder Packet speed These selection buttons will indicate the speed of the selected packet. They are not selectable by the user, they just function as an indicator. Fields For primary packets the 'Fields' page shows all the fields the header of the packet is made of plus the quadlet data fields if they are present.
Page 95: Triple Version
Recorder Acknowledge code If the selected packet has a corresponding acknowledge, the acknowledge code will be displayed here. If it has no acknowledge, it will say '(none)'. If the acknowledge is invalid (disallowed code) the code will be displayed too and in case of an acknowledge error (inverse-check error), the complete acknowledge byte will be displayed.
Page 96: Transaction View
Recorder 7.5. Transaction View The Transactions View is one of the possible views in the Recorder which you can use to investigate the recorded packets and events. It displays all completed and not completed transactions in a table Optionally additional information of a selected transaction can be displayed, including an overview of the involved request and response packets, a flow diagram, the transferred data and possible warnings and errors that are detected for the transaction.
Page 97: Details
Recorder The currently shown transactions table columns are checked in the menu. A column is shown or hidden by clicking the corresponding menu item. The transaction number column shows the corresponding transaction number. It is initially hidden and can be made visible in the transaction table through the transaction column menu. Selecting a transaction in the table will display the details of that transaction in the (optional) details part and will also select the corresponding item in all other views of the Recorder.
Page 98: Transactions Table
Recorder It contains the following additional Toolbar control: View This control van be used to select the Analyzer nodes to view information for. By clicking on the "a", "b" or "c", the corresponding nodes can be hidden or shown. A red background indicates a node is shown. A white background indicates a node is hidden.
Page 99: Transactions Details
Recorder Bus resets are also included in this list for the convenience of the user.Transactions are displayed in orange if one or more warnings are found within the transactions and red when one or more errors are found within the transaction. Details of the warnings and/or errors can be found on the optional right part of the view (see below).
Page 100 Recorder Flow Selecting this page will show the same packets but now as a flow diagram. The requester is drawn left (vertical dark gray line) and the responder right (also vertical dark gray line). The packets transmitted between these two nodes, for the selected transaction, are drawn as arrows. The arrows point into the direction of transmission (from source to destination).
Page 101 Recorder Data Layout The same data as displayed in the ‘Data’ page, is also displayed in the ‘Data Layout’ page, but now shown as a packet layout. An example of the ReadBlock transaction of above is shown below. For Lock transactions the tree data values (argument, data and old data ) are now displayed underneath each other.
Page 102: Protocol View
Recorder answered with an acknowledge. So the request is not completed. Because there was no response, there is also a warning that the transaction is not completed. 7.6. Protocol View The Protocol View is part of the Recorder and will display the result of the protocol analysis. Currently the protocol analyzer supports the following protocols: ·...
Page 103 Recorder The left pane of the Protocol View is the 'relations' pane. It displays the results of the protocol analyzer in the terminology of the supported protocols. Each supported protocol has a tab page in the 'relations' pane. The tab page shows the results found for the protocol it supports. A tab page comprises a tree, which displays the hierarchy of the found results.
Page 104: How To Use It
Recorder The red bar indicates the highlighted transaction in the 'transactions and packets' pane, which is in this case the second corresponding transaction of the highlighted item in the 'relations' pane. Another example is protocol AV/C, see figure below. Protocol AV/C shows only the fields and their values of the highlighted transaction in the 'transactions and packets' pane and offers navigation buttons to walk through the corresponding transactions of the highlighted item.
Page 105: Details
Recorder Configuration ROM of a node. The Configuration ROM of a node is often read after a bus reset. If this information can't be retrieved from the recorded data it is to be provided manually. The Protocol Settings dialog shows all information needed by each protocol. It is filled initially with the information that could be found automatically.
Page 106: Details Pane
Recorder the same order as displayed in this tree. However, all items inside the same item of the tree (at the same level) are listed in the same order as the order of recording the first corresponding packet of each item. To find out the order of corresponding transactions and packets, see the 'transactions and packets' pane or take a look at one of the other views of the Recorder (e.g.
Page 107: Transactions And Packets Pane
Recorder For more informattion about the 'details' pane, see the corresponding protocol chapters. 7.6.2.4. Transactions and packets pane The 'transactions and packets' pane shows the involved transactions and packets of the results found by the protocol analyzer. It also shows all bus resets, see figure below. The 'transactions and packets' pane lists the transactions, packets and bus resets in a chronological order.
Page 108 Recorder button. To get original protocol settings use 'Revert' button. Below is an example of the Protocol-Settings dialog. In this example you can see the settings for the protocol. Mostly the protocol analyzer will need information about the Units inside the nodes that comply to the protocol.
Page 109: How To Use It
Recorder 7.6.3.1. How to use it If you need to specify Units for some protocol manually, then you first have to make a Node Specification that specifies the node in which the Unit resides. Then you can specify the Unit and the information that is needed for the Unit.
Page 110: Details
Recorder Another way to specify a node across reset boundaries is to use the EUI64 of that node. This value will (normally) be present in the Configuration ROM of the device. All EUI64 values for which one or more reads have been recorded are listed in the 'Found EUI64 values' box somewhere at the top of the dialog. When selecting such a value and clicking the 'Select/Add' button to the right of it, the Node Specification for that device will be added if it is not already present.
Page 111: Packet Marking
Recorder General Options At this moment, one general option exists: Mark unhandled packets This checkbox can be used to have all packets marked that aren't part of any protocol. It works like this: before the protocol analysis starts, all packets are marked that might be part of a protocol (request, response and stream packets).
Page 112: Packet Searching
Recorder · Using the Advance Search function. Marked packets can be exported to a Analyzer Packet file (*.fsp) or to a text file using the 'Export' function in the 'File' menu of the Recorder. Mark / Unmark with mouse clicks To mark/unmark a packet with a mouse click, click left to the colored packet rectangles in the Packet View (completely left in the table).
Page 113: Details
Recorder 7.8.2. Details Below, the different parts of the Search dialog are described in more detail. 7.8.2.1. Mark / Unmark options At the top of the dialog you can choose if you want to mark or unmark packets and set some other options.
Page 114: Search Result
Recorder 7.8.2.2. Search result At the top-right of the dialog you will find an indication of the number of currently marked packets and the number of currently unmarked packets. When the search is performed (Search button clicked), new packets may be marked or marked packets may be unmarked (depending on the chosen options).
Page 115 Recorder · Data Values box to specify optional data field conditions Primary Packets or Phy Packets Here you can select whether this set specifies primary packets or phy packets. Primary packets are Request packets, Response packets, Cycle Start packets or Stream (isochronous or asynchronous) packets.
Page 116 Recorder types, then the Destination-Offset field will be enabled. you can put a condition on this field. But if you also select a Response, this field will be disabled because it is not present in a Response packet. There are also some buttons to quickly select multiple types at once: Clicking this button will select all types.
Page 117 Recorder condition may be entered. A condition can be set by specifying a condition and a value. In the example above for instance, a condition is set on the Source field. A packet only fits the Set if all specified conditions (and that are not disabled) are true for the packet. In the example above for instance, a packet does not fit the Set if the Source field is not equal to 0xFFC1.
Page 118 Recorder Depending on the license keys that are installed, you can select all kinds of formats and optionally sub formats where needed. There are formats for the SBP protocol, IIDC protocol, IP4 protocol and AV/C protocol. You can also select the format 'unformatted' to be able to set any kind of condition on any bits. Now we will describe the different parts of the Data Values box: payload size (bytes): Here you can enter the payload size of the packet expressed in number of bytes.
Page 119 Recorder right of it. For some parameters, the value can be entered by selecting a symbolic value from a list of symbolic values in a combo box. · Fields. The formatted payload or field can be shown as a table or a layout picture. The Fields tab shows the table.
Page 120 Recorder Decimal and hexadecimal numbers can be entered decimal or hexadecimal. For fields with symbolic values, a combo box will be displayed when clicking on the value so that a value can be chosen. You can change this behaviour by selecting another display form (overruling the automatic form) using the right mouse button as described below.
Page 121: Others Page
Recorder 7.8.2.5. Others page As well as specifying packets using the packet sets, we can also quickly include packets and events using the 'Others' tab page. On this page you will find a number of packet types and events that can be included by checking those check boxes.
Page 122: Chapter 8. Mil1394 Player
Mil1394 Player Chapter 8. Mil1394 Player The Mil1394 Player is a FireSpy application which is able to transmit AS5643 stream packets as recorded by the Recorder. This allows the user to recreate a previously recorded situation on demand, including dropped packets, timing faults and missing data. The Mil1394 Player can help reproduce specific use cases, which can be used in developing the system around it.
Page 123: Play Regeneration File
Mil1394 Player Export packets Click on Export to create the Regeneration file (*.rgn). This is the file that will be used by the Mil1394 Player. 8.1.2. Play Regeneration File You can open the Mil1394 Player by clicking on the Player button in the main window. When opening the Mil1394 Player, an empty user interface will appear.
Page 124: Bus Settings
Mil1394 Player toggle button. The second counter shows the total number of packets to be sent. Time indicators The first ‘time indicator’ shows either the remaining or elapsed time, which can be switched with the toggle button. The second time indicator shows the total time needed for the Regeneration file to be played completely.
Page 125: Chapter 9. Symbol Recorder
Symbol Recorder Chapter 9. Symbol Recorder NOTE: The Symbol Recorder module is only available on FireStealth analyzers with a Symbol Recorder Module license. 'Time View' enables the user to view the timing of symbols, packets and toning as they occur on the connection.
Page 126: How To Use It
Symbol Recorder 9.1.1. How to use it 9.1.1.1. Display Symbol Recorder Files Initially, there is no recorded data and the views are empty. You can load a symbol recorder file into the Symbol Recorder using the 'Open' command of the 'File' menu. You can select a file (extension .sym) and it will be loaded.
Page 127: Download And Process Symbols
Symbol Recorder progress bar' in the toolbar will indicate the part of recorder memory that is filled with data. Note that when the Recorder is not triggered yet, only the part before the trigger indicator in the progress bar (the little vertical line) will be filled. If this part becomes full, recording continues and old data will be removed from the memory while the new data is stored (cyclic buffer).
Page 128: Using Multiple Analyzers
Symbol Recorder 9.1.1.5. Using multiple analyzers When multiple FireStealth devices are connected to the same topology it is important that they are synchronized to an IRIG-B122 time source. It is also possible to control multiple devices without time synchronization but then then Recorder simply assumes all analyzer recordings started at exactly the same time.
Page 129 Symbol Recorder It has the same status as the 'trigger led' on the Analyzer front panel (see Hardware). Ready indicator This green indicator will light when the Recorder has been stopped and has recorded data in its memory ready for download. It has the same status as the 'record ready led' on the FireSpy front panel (see Hardware).
Page 130: Time View
Symbol Recorder 9.2. Time View The Time View is one of the possible views in the Recorder which you can use to investigate the recorded data. It displays all packets and symbols on a time line. The relative positions of the packets and symbols correspond to the time the packet or symbol was recorded and the length of symbols and packets in the view correspond to the actual duration of the items.
Page 131: Data Display
Symbol Recorder Zoom reset With this button you can reset the zoom amount to its original value. Goto Next Trigger With this button you can move the cursor to the next trigger location. Goto Next Bus Reset With this button you can move the cursor to the next Bus Reset symbol. Goto Next Error With this button you can move the cursor to the Error or Raw symbol.
Page 132 Symbol Recorder Configuration Request Symbols Packet Data Comma Symbol Erroneous Toning Raw (undecodable) Packets have their own color codes. The used packet colors are: cycle start packets stream packets read/write/lock request packets read/write/lock response packets phy packets packets with error(s) acknowledge packets The cursor is a vertical line with little triangles on the top and bottom.
Page 133: Packet View
Symbol Recorder T = Trigger R = Bus Reset The Trigger event will be displayed at the position where the trigger occurred. The Bus Reset event will be displayed at the position where the link interface signals a bus-reset status. selecting packets Packets can be selected by clicking with the mouse in the packet rectangle.
Page 134: Packet Detail View
Symbol Recorder When clicking this button, the previous packet will be selected. It will be enabled if a previous packet is present. Go to next packet When clicking this button, the next packet will be selected. It will be enabled if another packet is present. 9.3.2.2.
Page 135: Symbol View
Symbol Recorder Packet' type does not correspond to the real packet type, an error page is added to the 'Fields' and 'Layout' pages. Selecting this page will list all detected errors. Below, an example of the 'Errors' page is shown. In this example, the packet above is shown as a stream packet, which of course will result in errors.
Page 136: Details
The type of the item as summarized below. Scrambler The value of the scrambler of the sending 1394 port at the current location. Sync Offset The offset from the position where the software could find bit synchronization and determine the scrambler value.
Page 137 Symbol Recorder This item can be found when the decoding algorithms can not decode the data in any way. This means the pickup logic can detect data on the line but it cannot decode it into toning or tokens. 10B Count is the number of supposed symbols data[x] shows the raw data of 30 bits a row.
Page 138: Examples
Symbol Recorder Toning is a square wave with a frequency of 50MHz and a duty cycle of 50%. If the software detects this, it is marked as a toning item. Token Tokens are descrambled/ decoded symbols. If a token is found repeatedly, only the first occurrence is saved and a counter is increased.
Page 139 Symbol Recorder Total Overview of StartRecordingS800toS400.sym First Part: Toning In the IEEE1394-2008 specification this state is named the "Disconnected" State (P0). Toning and speed negotiation takes place here. Speed negotiation In the picture above we see the S400 capable node sending toning on the upper part of the screenshot and the S800 capable node on the lower part.
Page 140 Symbol Recorder (For details about training please refer to 13.3.2.1 of the IEEE1394-2008 specification) TRAINING/OPERATION symbols are used to synchronize bits/character and the scrambler. When a node is ready (in sync) it starts sending OPERATION symbols. After both ports receive OPERATION symbols, they are synchronized and can start testing for a possible loop.
Page 141: Chapter 10. Generator
Generator Chapter 10. Generator The Generator can generate large amounts of stream packets. It includes a powerful graphical editor to specify the sequences of stream packets that should be sent; up to 64 channels simultaneously. You can do this by defining so-called slots. Each slot represents a number of cycles; a packet will be sent once per cycle.
Page 142: Details
Generator data can be specified in the "Streams" generator page, where you can define isochronous sequences. Sequences are indicated by blue rectangles on the time line of a slot. This can be seen in the picture above. An isochronous sequence is specified by a a start cycle number, the length in number of cycles, the speed and contents of the isochronous packets to be sent during these cycles.
Page 143: Toolbar
Generator Clear Clear the uploaded Generator definition from the Analyzer. Slot Definitions With this command, the slot definition editor can be opened. For a description of how it works, please refer to the Slot Definitions section. Frame Settings With this command, the frame settings dialog can be opened. For a description of how it works, please refer to the Frame Settings section.
Page 144 Generator Buttons The slot definitions window contains the following buttons Insert This button can be used to insert a new slot definition. Delete This button can be used to delete the currently selected slot. Move up This button can be used to move the currently selected slot one line up. This means that the priority will be increased by one.
Page 145 Generator Channel The channel to use for all packets for this slot. Length The number of cycles represented in the slot. Priority If the check-box "Use column priority for sending order" is checked, this determines sending order. Otherwise, the channel numbers. Looped If set to true, the generator will continuously repeat sending the packets for this slot when the end of the slot is reached.
Page 146: Settings
Generator 10.1.2.4. Settings The Cycle Settings dialog can be used to change the following settings: Cycle master when root If the Analyzer is the root node and this setting is enabled, it will also act as Cycle Master Force Root at Start If this setting is enabled, the Analyzer will try to become the root node when the Generator is started Cycle Time If the Analyzer is cycle master, this setting determines the cycle time in nano seconds.
Page 147 Generator At the top of this window you can find the toolbar with buttons for starting, uploading and stopping the Generator. Before starting the Generator, you first have to upload the generator data to the Analyzer. This data can be specified in the "Mil1394 Streams" generator page, where you can define isochronous sequences.
Page 148: Details
Generator 10.2.2. Details 10.2.2.1. Menu File Open With this command you can open an existing Analyzer generator file. By default these files have an extension of .fsg. Save With this command you can save the current generator data as a Analyzer generator file. By default these files have an extension of .fsg.
Page 149: Slot Definitions
Generator generated for the defined cycle, where cycle 0 corresponds to the current isochronous cycle at the moment the Generator is started. If the isochronous generator data has been changed since the last upload, the user will first be asked if the changed data must be uploaded again. Stop isochronous generator Clicking this button will stop (deactivate) the isochronous Generator.
Page 150 Generator Delete This button can be used to delete the currently selected slot. Move up This button can be used to move the currently selected slot one line up. This means that the priority will be increased by one. Move down This button can be used to move the currently selected slot one line down.
Page 151: Settings
Generator nodes are used when starting the generator. 10.2.2.4. Settings The Frame Settings dialog can be used to change the following settings: Set frame length/sync start If this option is enabled, the generator will synchronize its frame timing when started. The following options determine how synchronization will take place.
Page 152: Mil1394 Example
Generator 10.2.3. Mil1394 Example We will explain the Generator and Recorder function with regard to the Mil1394-protocol using an example file. To run the examples, connect the FireSpy800 and make sure the Mil1394-protocol key is installed. Load example file Open the Generator window and select File->Open. Browse to the Mil1394GenExample.fgs file in the examples folder and open it.
Page 153: Chapter 11. Scriptor
Scriptor Chapter 11. Scriptor Using the Analyzer Scriptor feature, it is possible to send/receive packets, extract fields from a packet and display the results on a Control Panel by using different kinds of indicators. The Scriptor window is divided in four parts, each represented by a tab page. Script Editor ·...
Page 154 Scriptor Getting help When editing a script, one may press the F1 key to get help about the word at the current cursor position. Additionally, when moving the mouse to an identifier and leaving it there for approximately one second, a tooltip pops up that contains the declaration information for that identifier if known.
Page 155: Script Editor
Scriptor This command enables exporting the text part of a script to an external file. Two formats are currently support: (*.txt) and (*.html). Scripts exported to a text file can be imported again with the import command. However, when doing so, the Data and Control Panel are lost. The other format exports the text part of a script to a web page.
Page 156 Scriptor Property Editor, an Object Browser and a Debugger. Property Editor is used to edit the properties of the script source-code line that is currently selected. Object Browser contains an hierarchical overview of the processes, functions and variables that are defined in the script source code.
Page 157: Toolbar
Scriptor line shows its selection by using a blue highlight bar for the selected part and a gray highlight bar for the remainder of the line. Collapsing and expanding Whenever a line contains child lines, as indicated by the branches in the plotted tree, the childs may be hidden by collapsing the tree node corresponding to this line.
Page 158: Status Bar
Scriptor 11.2.3. Status Bar The status bar at the bottom possibly contains an error message. While editing a script, error messages will be shown in red. During the edit phase, error messages should be considered as hints about the current statement. If, during compilation, errors still exist, the line corresponding to the error will be highlighted right after the compiler finishes and the script part that contains the error will be underlined.
Page 159: Statement
Scriptor the script. An overview of currently supported statements will be presented in the next sections. 11.2.4.1. Statement When entering a statement, a simple edit box is shown on the properties page for entering an expression. The property editor is shown in the picture below. 11.2.4.2.
Page 160: Define Statement
Scriptor This property editor contains the following items: Type The return type of the function. Name A user-defined name. Main entry When the script is being executed on the Analyzer, all functions that have this option checked will be started. Function priorities are determined by the order of function definitions, the first one having the highest priority.
Page 161: Macros
Scriptor 11.2.4.7. Macros In addition to the statements described in the previous section, the Script Editor also supports the use of macros. Macros can be used by providing their name on an empty line in the script editor. After such a name is entered, a property editor corresponding to that type of macro will show up.
Page 162: Setpacketheaderfields And Getpacketheaderfields
Scriptor field. To create a packet that is larger than the size that is automatically determined by the packet layout, enable the "Fixed size" checkbox set the size to an arbitrary value. While filling in the property editor, the script on the left side is updated and child nodes are generated. In de example below, the offset field has been given a value in the property editor and the script carries this out by calling two API functions.
Page 163: Object Browser
Scriptor "set" column to set a header field and provide the value to set in the "Param Value" column. Use the tCode edit box to set the tCode of the packet. When no value is provided, nothing is done. Just like the other macros, when filling in the property editor, subnodes are generated containing the required API calls to set or get the header fields.
Page 164: Debugger
Scriptor Functions The list of functions contains all the functions that are defined in the source code of the script. This does not necessarily mean that a function in this list is actually executed. Regular functions themselves are not started as a process, but can only be called by other functions or processes. The order of this list only reflects the order the functions are defined in the script.
Page 165: Debug Icons
Scriptor 11.2.6.1. Debug Icons Currently the following icons exist for display in the debugger: A process is currently executing this line The selected process is currently executing this line This line is currently being executed by multiple processes This line is currently being executed by multiple processes, including the selected one If for the currently selected process, in the call stack view, a different call depth is selected, this icon is shown at the line where the selected function call took place.
Page 166: Breakpoint View
Scriptor 11.2.6.3. Breakpoint View The Breakpoint view displays a list of all the breakpoints that are currently set in the script. For each breakpoint listed, the following information is shown: · If a process is broken at this breakpoint, an arrow is shown. See row 4 in the picture above ·...
Page 167 Scriptor · waiting (sleep), The process is waiting for a sleep statement (not yet implemented) · waiting (breakpoint), The process is broken at a breakpoint or the user is stepping with the debuggger · waiting (stream write), The process is writing to a stream buffer, or waiting until space is available to write ·...
Page 168: Call Stack View
Scriptor 11.2.6.5. Call Stack view The Call Stack View displays symbol and function-call information for the process that is currently selected in the Process View. If the Process View has no selection, this view will be empty. The upper part of the Call Stack View displays a list of function calls made by the selected process. The top one is the line that the process is currently executing.
Page 169: Control Panel
Scriptor Whenever the debugger receives a negative return value it is appended to the error view. The picture above shows an example of a negative value (-6) returned by the recvStreamPacket function. In this case a bus reset was detected before a packet was received. The error view will always get focus when it received the first error during script execution.
Page 170: Control Properties
Scriptor control. The Gauge is the most complex control with many properties to customize it. The Led has just two specific properties (color and threshold). All Controls share a few settings, these are also the most important settings. An added control is positioned below the cursor, the position and size might not be what you want. To position it just drag and drop the control to its place.
Page 171 Scriptor This section explains the most common properties. Every Control should get its own unique ID. When the script is being executed, the function setControlValue(ID,Value) sets all the controls with that ID to "Value". It is possible to assign the same ID to multiple controls.
Page 172 Scriptor The controls always display the calculated value. The history graph however has an option to "recover" the value as it was set by setValue() and grabValues(). Range Min/Max These settings are mainly used for adjusting the scale of the history graph. However, this setting is also used to change the scale of the "Gauge"...
Page 173: Output Controls
Scriptor Origin Defines the starting position of the first line of the scale in degrees counter clockwise. So "-90" starts at the top. "0" starts on the right, "90" on the bottom etc. ScaleArcMin In degrees, counter clockwise, starting from the "Origin" (mostly 0). ScaleArcMax In degrees, counter clockwise, starting from origin.
Page 174: Input Controls
Scriptor An LCD Control can be used to display numeric values. Note that this control is slower than the Number control. A Led is a control that is either "on" or "off". To turn it off, send a value of '0' to it. All other values turn it on.
Page 175 When the user clicks in a region the corresponding value is sent to the control ID of the image control. An example of a car with some clickable IDB 1394 nodes is shown in the folling picture. File Browser The File browser control makes it possible to open a file dialog and select a file for input or output from a running script.
Page 176: Layout Controls
Scriptor script opens the specified file, the green LED will turn on. When this LED is on, it is not possible to change the filename. 11.3.4. Layout Controls Layout controls donot have any form of dynamic behavior. They can be used to beautify or clarify the control panel.
Page 177: Client
Scriptor control. The Graph also contains a cursor, which can be used to retrieve the value at the selected time. Move the cursor to position it exactly where you want it, this way it is easy to retrieve a maximum or minimum value.
Page 178 Scriptor attached. You can place the same controls on it as with the application. There is only one control that is not supported in this client and that is the FileBrowser. If you created a control panel in the Analyzer application than you can export this control panel to file in the file menu if the scriptor.
Page 179: Data Editor
Scriptor Next to this icon the application shows the number of clients connected. The port number of the application and the client can be freely chosen so that it is possible to have multiple applications running a server. When the client is connected all control values that are send from the script are also send to the connected remote clients.
Page 180: Toolbar
Scriptor Using data objects in the script In the picture below, a script is shown that contains some data blocks. The script only uses the first file data object as input for a packet. The packet header is also set from a data object. After the packet is filled with a header and some data, it is send once.
Page 181: Packet Data Editor
Scriptor 11.4.3. Packet Data Editor When the data type is set to "Packet data", a data editor will appear as shown in the picture below. The "format" combo can be used to set the packet format. Selecting a format will update the number of bits to the default value for the selected format and display the corresponding field lay out.
Page 182: Packet Header Editor
Scriptor 11.4.4. Packet Header Editor When the data type is set to "Packet Header", a data editor will appear as shown in the picture below. For this type of data editor, the number of bits is determined by the selected packet type. Also, the available header fields are determined by the selected packet type.
Page 183: File Data Editor
Scriptor 11.4.5. File Data Editor When the data type is set to "File", a data editor will appear as shown in the picture below. To select the file, click on the "Browse" button on the right. It is possible to load from Quadlet files "*.qdl" and from Hex data files "*.hex".
Page 184: Script Properties
Scriptor 11.5. Script Properties The Script Properties tab provides information about the current script. All values defined here are saved both in the script source and the generated executable for later use. These values could for example be used to verify if an executable and source file match and which features are required to run the compiled script.
Page 185: Script Executable
Scriptor 11.5.1. Script Executable The Script Executable group of controls on the Script Properties tab page contains different kinds of version numbers. Some of the values will be generated at compile time while others are user defined. Whenever the script is compiled, all values will be stored in the executable file. By using the API it is possible to extract these values from the executable file to verify them.
Page 186: Examples
Scriptor · Enabled: This field indicates whether the feature is currently enabled or not · Requirements: This field describes the (license/validation) requirements for this feature. 11.6. Examples 11.6.1. Simple Sending This example shows how to define a packet using the build-in data editor and how to send a multiple of this packet each time a bus reset is detected.
Page 188: Simconfrom
Scriptor 11.6.2. SimConfRom When running this script, all reads of the Analyzer configuration Rom will be catched and a corresponding value from a quadlet file will be returned. This quadlet file was created by using the Memory R/W function of the Commander of the Analyzer. The configuration Rom of a desktop computer (with FireWire card) was read and stored to a quadlet file.
Page 189: Details
Scriptor tcode == TCODE_READREQ q1 = getPacketHeaderField ( req, q2 = getPacketHeaderQuadlet ( req, q1 == 0xFFFF && ( q2 & 0xFFFFFC00 0xF0000400 addr = ( q2 & 0x3FF )>> setPacketHeaderFields ( resp, RESPCODE_COMPLETE ) setPacketHeaderField resp, RESPCODE_COMPLETE writePacketHeader ( resp, ,DATA_ID_1_FIRST ,addr, sendPacket ( resp ) cnt = cnt +...
Page 190 Scriptor Now that all has been initialized, the script enters an indefinite loop. (while 1) A loop iteration starts by waiting for an asynchronous packet. When a packet is received, a macro is encountered with the name "getPacketHeaderFields". See the picture below. Copyright ©...
Page 191 Scriptor This macro is filled in to get the values of "Source", "Destination" and "Transaction label" for a "ReadReq" packet. The values should respectively be set to "requestor", "node" and "label". As can be seen in the script, the macro accomplishes this by generating three calls to API functions. These calls to "getPacketHeaderFields"...
Page 192: Erroneous Sending
Scriptor Note that the data is read from file during script upload from the specified file. When the script is running on the Analyzer, the file data is already in Analyzer memory. After reading the data from file, the packet is sent and the controls on the control panel are updated. 11.6.3.
Page 193 Scriptor Channel This is the channel the packets will be sent on. Frame offset This field is only used if the packets are sent in synchronous mode and sets the time offset within a frame each packet is sent. Packet speed Sets the speed of the packets that are sent.
Page 194: Details
Scriptor Enable the buttons "Node A" and "Node B" Enable the button "Data CRC Error" Set "Number of packets" to 5 (press set) Set "Channel" to 5 Set "Frame Offset" to 5000ms Set "Packet Speed" to 800 10. Start sending by pressing the button: "Send synchronous" 11.
Page 195 Scriptor updateButtonStates On the control panel, a couple of buttons are used as so-called state buttons. This means that a button should stay down when it is enabled and up when it is disabled. Normally, buttons on the control panel will come back up as soon as they are released after pressing them.
Page 196 Scriptor setControlValue ( i + , getControlValue ( i + i = i + speed != && speed != && speed != && speed != setControlValue ( packets < setControlValue ( //-------------------------------------------------------------------- void startButtonHandlers () entry packet = createPacket () stofPacket = createSTOFPacket () while true...
Page 197 Scriptor selectFireSpyNode ( sendPacket ( packet ) sendC selectFireSpyNode ( sendPacket ( packet ) i = i + //-------------------------------------------------------------------- void sendSync ( stofPacket, packet ) num = getControlValue ( frameOffset = getControlValue ( bool sendA = getControlValue ( bool sendB = getControlValue ( bool sendC = getControlValue ( ! sendA &&...
Page 198 Scriptor createSTOFPacket () p = newPacket ( fillPacket ( p, DATA_ID_3 ) fillPacketHeader p, DATA_ID_3 return //-------------------------------------------------------------------- void setPacketErrors ( channel = getControlValue ( speed = getControlValue ( bool dataCRC = getControlValue ( bool sizeError = getControlValue ( dataBytes = getPacketDataSize ( p ) * // Check if we have to set an incorrect data size in the header sizeError dataBytes = dataBytes +...
Page 200: Cable Test
Scriptor 11.6.4. Cable Test If you only have one triple FireSpy analyzer (FS3810 or FS3850) for the test, you can test one cable at a time. If you have more than one FireSpy® analyzer for the test, you can configure two non-triple FireSpy analyzers as a pair, or configure...
Page 201: Two Non-Triple Firespy Analyzers
Scriptor 11.6.4.2. Two non-triple FireSpy analyzers You will need to dedicate one analyzer as a server and the other as a client. Start the FireSpy application on both analyzers and load CableTestServer.fss and CableTestClient.fss in the Scriptor accordingly. The client-side script has no controls: you will simply need to start the script. On the server side script, however, you will need to setup the controls according to the analyzer type and cable settings you have.
Page 202 Scriptor All settings are very similar to step 3 except that you need to enable Node B and/or Node C cable speed depending on the configuration you have. You will also need to load the CableTestClient.fss script file to each client FireSpy® analyzer and CableTestServer.fss to the triple analyzer. Copyright ©...
Page 203: Chapter 12. Filter/Trigger
Filter/Trigger Chapter 12. Filter/Trigger This section describes the Filter / Trigger functionality. Please take note that not all features described are available on all analyzer models. With the Recorder Filter one can skip packets or events. Skipped packet or events are not stored in memory by the Recorder.
Page 204: Trigger
Filter/Trigger If you want to change the trigger settings, select the Trigger page (like above) or General Trigger page. To change the Filter settings, select the Filter page. If you use one of the four basic packet sets and you want to change one of them, select the corresponding SetA, SetB, SetC or SetD pages.
Page 205 Filter/Trigger The most important part for the trigger settings is the Trigger Sequencer, see left pane in example above. Here you can graphically define a trigger program by adding items to the flow and change theire properties. By executing the program you can generate a Recorder trigger when a particular sequence of packets or events has been detected.
Page 206: General Trigger
Filter/Trigger buffer full option is selected (default), the Recorder will also stop when the complete Recorder buffer has been filled with data. In this mode you will never overwrite recorded data. When you however select the Cyclic pre-trigger buffer option, the Recorder will use a cyclic buffer for the recorded data before a trigger occurs.
Page 207: Filter
Filter/Trigger 12.1.3. Filter The Filter Tab is not available on · Stealth Series in Symbol Recorder mode Actual available options for filtering depend on the analyzer model used. An example of the Filter page is shown below. You can select on this page which packets and events should be skipped. In the Skip by packet type box you can select packet types to be skipped.
Page 208: Packet Sets
Filter/Trigger In the Skip events box you can select which events should be skipped by checking the corresponding checkboxes. By default all the 'Bus Reset' events will be skipped. Note that Bus-Reset events can not be skipped. 12.1.4. Packet Sets The Packet Sets tab is not available on ·...
Page 209 The table in this box shows all possible fields that can be present in a 1394 packet header. Only those fields that are present in the selected packet types will be enabled. You can only specify conditions for those enabled fields. If more packet types are selected, only those fields will be enalbed that are present in all the selected types.
Page 210: Details
Filter/Trigger The selected format describes the commands for a 'Simplified direct-access (RBC)' unit. By choosing a value for the 'operation code' field, the format will automatically adjust to the format of the selected command. In the example conditions are set on some fields such that the packet will only fit the set if the 'operation code' equals the 'READ(10)' command with a 'transfer length' or 256 or more.
Page 211: Trigger
Filter/Trigger This commands does the same as the 'Save' command, except that it will always display the file dialog, so that you can specify a file name and path. Windows From the 'Windows' menu you can open one of the other windows of the Analyzer. 12.2.2.
Page 212 Filter/Trigger button: Start or restart trigger sequencer Clicking this button will activate the sequencer (if it wasn't already active) and the sequencer will start executing the first item in the trigger sequencer program flow. When the filter/trigger settings need to be uploaded (Apply button enabled), the user will be asked if the settings must be uploaded before (re)starting the sequencer.
Page 213 Filter/Trigger button: Add a Jump item When clicking this button, a new Jump item will be inserted in the flow below the selected item. Initially the Jump item looks as follow: When this Jump item is executed, the sequencer will jump if the last Wait was ended by the reception of a packet and the received packet fits the description of setA.
Page 214 Filter/Trigger The result is that the Jump item is enclosed in a Repeat-start and a Repeat-end item. Executing this flow would repeat the Jump item 2 times, which does not make any sense. You can expand the repeat block by using the Move item up button when the Repeat-start item is selected, or using the Move item down button when the Repeat-end item is selected.
Page 215 Filter/Trigger changed and the text in the item will indicate the new properties of the item. The properties of all items are described in more details below. Now we will discuss the different types of items and describe what happens when they are executed. ·...
Page 216 Filter/Trigger Note that an Acknowledge will not end the Wait execution and thus is not detected. Note also that the flow on the right does not do the same thing! This is because the first Jump item after the Wait item will jump if the Wait was not ended because of a BusReset event.
Page 217 Filter/Trigger the Max pre-trigger size slider. As soon as the Recorder is triggered, the data in the pre-trigger buffer will not be overwritten anymore and the remaining Recorder memory will be filled. The Recorder will stop when the complete Recorder memory has been filled or when the data after the trigger reached the the amount indicated by the Max post-trigger size slider.
Page 218 Filter/Trigger You can select to wait for a Packet, an Acknowledge, an Event, or any combination of them. See flow diagram area above for a description of what happens when a Wait item is executed. The text inside the Wait item will indicate the selected properties. ·...
Page 219 Filter/Trigger The following sub-selections are possible: · Any Packet (incl. erroneous packets): If this option is selected, the jump-condition will be true for every packet that is detected, including packets with an error or invalid packets. · Packet from Set(s)...: If this option is selected, you can specify a packet Set or a boolean combination of packet Sets.
Page 220 Filter/Trigger In the example above, the jump-condition is only true for CycleStart packets. · other Packets ...: If this option is selected, additional check boxes appear where you can specify some special packet types or some packet errors. If a packet was detected with a type for which the corresponding checkbox is checked or with an error for which the corresponding checkbox is checked, the jump-condition is true.
Page 221 Filter/Trigger The following sub-selections are possible: · Any Ack (incl. erroneous Ack): If this option is selected, the jump-condition will be true for every acknowledge that is detected, including erroneous acknowledges or invalid acknowledges. Erroneous acknowledges are 8 bits long (which identifies an acknowledge), for which the first 4 bits are not the inverse of the last 4 bits.
Page 222 Filter/Trigger ended because of the detection of Packet or Acknowledge, then the result of the jump-condition is always false. The three elipses indicate that additional sub-selections are possible. When selecting this option, the additional sub-selection options appear at the right top of the Jump Properties box.
Page 223 Filter/Trigger for an Action item. The page is shown below. The second action, Trigger Recorder will trigger the Recorder. The third action, Set Output Port will set the specified port to the specified state. The text inside the Action item will indicate the selected properties. ·...
Page 224: General Trigger
Filter/Trigger 12.2.3. General Trigger Cyclic buffer mode is not available on · Third Generation Analyzers An example of the General Trigger page is shown below. Trigger events from external Port signals In this box you can specify the external ports input which will cause the trigger. For detailed pins/ports settings, please refer to External Port Settings.
Page 225: Filter
Filter/Trigger Trigger Position In this box you can specify the trigger position in the Recorder memory and you can enable a cyclic buffer for the data before the trigger. Stop recording when buffer full Selecting this option (default) will cause the Recorder to stop when the Recorder buffer is completely filled.
Page 226 Filter/Trigger Skip by packet type Using this box, you can select which packet types need to be skipped by the Recorder. You can select some packet types (like Cycle packet or Stream packet), you can select some packet type combinations (like Write Request and Response packets) and you can select packet with some kind of error (like packets with invalid tcode in header).
Page 227: Packet Sets
Filter/Trigger Here you can select packet speeds. All packets with a speed of one of the selected speeds will be skipped. Note that when the S100 speed is selected, the Phy SelfID packets will be skipped too. This means that the topology can not be drawn in the Topology View of the Recorder, because the Phy SelfID packets are needed for that.
Page 228 Filter/Trigger Primary Packets or Phy Packets Here you can select if this set specifies primary packets or a phy packets. Primary packets are Request packets, Response packets, Cycle Start packets or Stream (isochronous or asynchronous) packets. If you select Phy Packets, then you can specify optional phy packet field value conditions using the Data Values box.
Page 229 Filter/Trigger None Clicking this button will deselect all types. Requests Clicking this button will select all request types. Responses Clicking this button will select all response types. with Data quadlet Clicking this button will select all packet types, for which a data quadlet is present in the header. with Data block Clicking this button will select all packet types, for which a data block may follow the header.
Page 230 Filter/Trigger greater than or equal to 1024. Note that some values can be selected by selecting a symbolic value from a combo box, so you do not have to look up these values. If you want to know the values of these symbolic names, you can look inside the 'Layout' tab, or you can use a right-mouse click and select the 'Decimal' values option for instance.
Page 231 Filter/Trigger the example below for instance the selected format is one of the command sets for the command data for the SBP2 protocol. Command data is returned as a reaction on a command. In this case, the command has an operation code that determines the format of the command data. Thus to be able to format a command data packet, you will need to enter an operation code.
Page 232 Filter/Trigger Decimal and hexadecimal numbers can be entered decimal or hexadecimal. For fields with symbolic values, a combo box will be displayed when clicking on the value so that a value can be chosen. You can change this behaviour by selecting an other display form (overruling the automatic form) using the right mouse button as described below.
Page 233: Chapter 13. Mil1394 Protocol Support
The AS5643 specification defines so called Asynchronous Subscriber Messages (ASM). Remote nodes will listen on (subscribe to) a specific 1394 channel and look at the MessageID field in each packet received on that channel to determine the format of the message data and decode for example sensor values.
Page 234: How To Use It
Mil1394 Protocol support 13.1.1. How to use it The Mil1394 Signal Monitor can be started through the Windows Start menu as a standalone application or from the Main Window of the FireSpy application. After starting the Mil1394 Signal Monitor, an empty view will be shown as can be seen in the picture below.
Page 235: Details
Mil1394 Protocol support Using the cursor line in the plot view at the bottom you can navigate through all the frames and show the signal values captured in a specific frame number. The next step would be to actually capture some data. This could easily be done in either of two ways: ·...
Page 236: Toolbar
Mil1394 Protocol support These files could be created with the Control Panel of the Mil1394 Signal Monitor itself or with another tool with Control Panel like the Scriptor. · Signal Definitions: Allows loading a set of signals from a .csv file, overwriting the current signal set. This function was added to support loading signal definition files as used in previous versions of the application.
Page 237: Signals View
Mil1394 Protocol support Start This button can be used to start monitoring the currently defined signals. The button will be disabled (grayed out) whenever the Mil1394 Signal Monitor is already active. Stop This button can be used to stop monitoring currently defined signals. The button will be disabled (grayed out) when the Mil1394 Signal Monitor is not active.
Page 238 Mil1394 Protocol support Toolbar The top of the view contains a toolbar which is labeled "Signals View". It contains respectively the following items: Add predefined This button can be used to select signals from a predefined set of signals. The pre-defined set either originates from an XML file that defines several AS5643 slash sheet defined configuration items or it originates from a .csv file with signal definitions.
Page 239 Mil1394 Protocol support The dialog contains a similar representation of signals as the Signals View itself, however, no values column and the details pane can not be hidden. You can now simply check the checkbox in front of signals you are interested in and after pressing "OK" these will be added to the active set. Pressing "Cancel"...
Page 240 Mil1394 Protocol support You can now manually define all signal details and after pressing "OK" the signal will be added to the active set. Pressing "Cancel" will ignore the contents of the dialog and the active set will remain the same as just before opening this dialog.
Page 241 Message Id The Mil1394 Message ID this signal is defined in. Quadlet offset The offset in quadlets relative to the 1394 data section of the packet. Offset zero points to the Message ID field. Bit offset The offset in bits relative to the the quadlet offset defined above.
Page 242: Controls View
Mil1394 Protocol support · Int8: 8 bits signed integer · Int16: 16 bits signed integer · Int32: 32 bits signed integer · Float32: 32 bits floating point value · Enumeration: associate texts with numeric values. When this data type is chosen, a button will be shown to open the value-text definitions dialog.
Page 243 Mil1394 Protocol support Toolbar Clear This button can be used to clear the complete contents of the current Control Panel. This button will be disabled (grayed out) when the Control Panel is in Locked state. Delete This button can be used to delete all controls that are currently selected.This button will be disabled (grayed out) when the Control Panel is in Locked state or when no controls are currently selected.
Page 244: Plot View
Mil1394 Protocol support Grid This button can be used to show or hide the grid. Close This button can be used to close the view. Control Panel The remaining area below the Toolbar is taken up by the Control Panel. In this area the user can place several kinds of controls as documented in the Control Panel section.
Page 245: Recorder Protocol View
Mil1394 Protocol support 13.2. Recorder Protocol View This chapter describes the Mil1394 Protocol of the Protocol View. When a Recorder file is opened or when a new recording is downloaded from the Analyzer, or when the Protocol View is opened, the Mil1394 Protocol analyzer scans through the recorded data in the Recorder and displays the found result in the Protocol View.
Page 246: How To Use It
Mil1394 Protocol support tab page. The 'Field' tab page shows the fields and their values in a tree and the 'Layout' tab page shows the fields and their values in the layout of the highlighted Mil1394 packet. 13.2.2. How to use it To show the Protocol View click menu item 'View | Protocol View' of the Recorder.
Page 247: Relation Tree Pane
Mil1394 Protocol support Triple Analyzers For triple Analyzers the toolbar looks as follows: It contains the following additional control: Analyzer node select control With this control you are able to select the protocol analysis result of each supported Analyzer node. 13.2.3.2.
Page 248: Details Pane
Mil1394 Protocol support 13.2.3.3. Details Pane The 'detail' pane of the Protocol View shows the details of the highlighted Mil1394 packet in the 'transactions / packets' pane. An example that shows the details of a STOF packet is depicted below. The different parts of the 'detail' pane are described below.
Page 249 Mil1394 Protocol support Offset in frame The 'Offset in frame' box shows the offset time of the highlighted Mil1394 packet relative to the frame, to which the highlighted Mil1394 packet belongs. Each STOF packet starts a new frame. This also means that the offset time of a STOF packet is always 0 microseconds.
Page 250 Mil1394 Protocol support Like the 'Fields' tab page it shows the fields and their values of the highlighted Mil1394 packet. But now the fields and their values are displayed graphically inside a data block, which represents the highlighted Mil1394 packet. 'transactions / packets' pane The 'transaction / packets' pane of the Protocol View shows all bus resets and Mil1394 packets found by the Mil1394 Protocol analyzer, see the figure below.
Page 251: Mil1394 Protocol Settings
Mil1394 Protocol support The 'transactions / packets' pane lists the bus resets and Mil1394 packets in a chronological order. A red cross in front of a Mil1394 packet in the 'transactions / packets' pane indicates the Mil1394 packet contains one or more errors. If you click a Mil1394 packet in the 'transactions / packets' pane, it will highlight.
Page 252: Scriptor
Mil1394 Protocol support table Mil1394 Channels Each row in table 'Mil1394 Channels' represents a node. The table shows in the columns the specific information of a node. This specific information of a node is: its name, the channel number, the heartbeat and the time slots to transmit an asynchronous stream packet, to receive an asynchronous stream packet and to transmit a datapump packet.
Page 253: Timed Sending
Mil1394 Protocol support 13.3.1. Timed Sending This example shows some of the timed sending capabilities of the Scriptor. Each frame, two packets are sent. One is a STOF packet that is transmitted at frame offset time 0 and the other packet is a data packet using the Mil1394 Protocol.
Page 254 Mil1394 Protocol support Running the script To run this example, please proceed with the following steps: Open the recorder and start recording Go back to the scriptor and select the Control Panel Start the script Press the button "Generate Data CRC Errors" Move the slider back and forth such that it shows a curve similar to the picture above Stop the script Open the recorder window and download the recording...
Page 255: Details
Mil1394 Protocol support below, the packet was found and the picture shows that the "Offset in Frame" was 12039 us, which corresponds to the value indicated by the Control Panel. So, the frame offset was indeed user controllable by the slider on the Control Panel. The "Time View"...
Page 256 Mil1394 Protocol support explained below: main Main is the only process in the script. It sets up the Mil1394 Stream packet and the STOF packet and sends them every frame according to the settings on the Control Panel. createSTOFPacket This function creates a STOF packet and returns the ID of the packet buffer the packet is written to. Two data objects from the Data Editor are used.
Page 257 Mil1394 Protocol support // Select Node selectFireSpyNode ( // Main loop while true // Wait for the beginning of a frame and send the STOF packet waitStartOfFrame () sendPacketNextFrame ( STOFPacket, // Set a data CRC error to the packet if the control panel button is down getControlValue ( CONTROL_ERROR ) setControlValue ( CONTROL_ERROR, setSendDataCRCError ( customOffsetPacket,...
Page 258 Mil1394 Protocol support return //------------------------------------------------------------------------------- int32 createMil1394Packet ( int32 channel ) // Create a packet buffer int32 p = newPacket ( // Set the packet data from the Data Editor fillPacket ( p, HEADER_EMPTY_STREAM, Mil1394_PACKETDATA ) fillPacketHeader p, HEADER_EMPTY_STREAM fillPacketData p, Mil1394_PACKETDATA // Set the channel setPacketHeaderFields...
Page 260: Mil1394 Signal Monitor
Mil1394 Protocol support The only field that is non-zero is the "Message Payload Length". This field is set to 12 because the script sets the ID of the packet to the "Decimal Value 1" field. 13.3.2. Mil1394 Signal Monitor This script can be used to monitor signal values for Mil1394 messages. It uses a channel number and messageID to filter the received messages.
Page 261 Mil1394 Protocol support This counter counts the number of times an API function returned a negative number quadlet index The quadlet offset in the message payload data the signal is located. For Mil1394 Messages, the MessageID is quadlet 0. Data type The data type of the signal.
Page 262: Editing Mil1394 Formats
Mil1394 Protocol support 13.4. Editing Mil1394 Formats When defining your own packet formats for the Mil1394 Protocol, you will be able to display the message payload of your Mil1394 stream packets in any format. You can use these custom formats in the Scriptor, Generator, Mil1394 Protocol analyzer of the Recorder and in the Filter Sets for the Filter/Trigger logic to define field conditions.
Page 263: Example
Mil1394 Protocol support needs. 13.4.1. Example The Mil1394FormatExample.dff file is an example file that shows an example of how to define formats for the Mil1394 Protocol. It can be found in the examples folder of your Analyzer install and it contains two format definitions as shown below.
Page 264: Format 2
Mil1394 Protocol support Fields 'value1a-hex' and 'value1b-hex' are both 16 bits size and are displayed as hexadecimal numbers. The remaining message payload fields are all 32 bits size. The 'converted temp' and 'converted voltage' fields are of the 'Convert' type. This means that a conversion is done on the raw bits values before it is displayed.
Page 265: Set Options
Mil1394 Protocol support channel number (plus a default 'case'). Below the 'Mil1394Format2' is shown in more detail. The 'switch' item is selected and we can see in the properties for this switch that it tests the input parameter 'channel'. If the channel number is 22, two (hexa)decimal fields are added. If the channel number is 23, four floating point values are added to the message payload.
Page 266: Xml Settings
Mil1394 Protocol support The 'Set type' should be 'Mil1394'. The 'Set key' must be set to 0. The 'Set name' must be unique for all Mil1394 type files. So you should fill in some other name here. When the Analyzer application finds two Mil1394 format sets with the same 'Set name' then the second one will be ignored.
Page 267: Packet Formats
Mil1394 Protocol support Each signal is in fact a field within a packet, the ASM packet. Each signal is therefore to be interpreted from a certain number of bits, at a certain offset from the start of the packet; in number of 32 bit blocks called quadlets and possibly a number of additional, individual bits.
Page 268: Channel Lists And Frame Timing
Mil1394 Protocol support </DecimalParts> </MessageID> <Field Name="Reserved" QuadOffset="1" FirstBit="0" NumBits="32" DataType="hex"/> <NodeID QuadOffset="2" FirstBit="0" NumBits="32" DataType="udec"/> <Priority QuadOffset="3" FirstBit="24" NumBits="8" DataType="udec"/> <MessagePayloadDataLength QuadOffset="3" FirstBit="0" NumBits="24" DataType="udec"/> </ASMHeader> <PayloadData> <HealthStatus QuadOffset="0" FirstBit="0" NumBits="32" DataType="hex"> <Port Name="Port 2"> <Speed FirstBit="2" NumBits="3" DataType="udec" EnumName="SPEED"/> <BetaMode FirstBit="5"...
Page 269 Mil1394 Protocol support  <ChannelList> <Channel ID="4" Heartbeat="80" DeviceName="Remote I/O 1"> <Transmit Offset="2000" Length="100"/> <Receive Offset="2200" Length="100"/> <DataPump Offset="2400" Length="100"/> </Channel> <Channel ID="5" Heartbeat="80" DeviceName="Remote I/O 2"> <Transmit Offset="2000" Length="100"/> <Receive Offset="2200" Length="100"/> <DataPump Offset="2400" Length="100"/> </Channel> <Channel ID="22"...
Page 270: Chapter 14. Industrial / Instrumentation Digital Camera Protocol (Iidc)
Industrial / Instrumentation Digital Camera protocol (IIDC) Chapter 14. Industrial / Instrumentation Digital Camera protocol (IIDC) One of the protocols supported by the Protocol View of the Recorder is the Industrial / Instrumentation Digital Camera protocol (IIDC) protocol. The IIDC-protocol analyzer software will scan through all transactions and packets to find IIDC-compliant Units and it will fill the 'relations' pane in the IIDC tab page with IIDC-related items, as described in Protocol View...
Page 271: Details
Industrial / Instrumentation Digital Camera protocol (IIDC) To make sure the IIDC analyzer finds the IIDC information automatically, you should make sure that the reading of Configuration ROM for the node id of the unit is recorded. The Configuration-ROM information is normally read after a bus reset.
Page 272: Relations Pane
The type of items that can be displayed are: · Node: displays a 1394 node with IIDC units inside that node below it. Each node gets a logical node id, which is fixed for the entire recording. This logical node id is called a NodeSpec and is displayed in the tree.
Page 273: Details Pane
Industrial / Instrumentation Digital Camera protocol (IIDC) write of status and control register · read of status and control · · read of inquiry · video frame channel allocation and de-allocation · Bandwidth allocation and de-allocation · 14.2.3. Details Pane The middle part of the Protocol View shows the details of the item that is selected in the 'relations' pane.
Page 274 Industrial / Instrumentation Digital Camera protocol (IIDC) Layout The 'Layout' shows the layout of the selected item. Like the 'Fields' table it shows the fields that are defined for the selected item and the corresponding values of these fields. But now the fields are displayed graphically inside the data item.
Page 275 Industrial / Instrumentation Digital Camera protocol (IIDC) The tab displays information about the selected video frame and contains control buttons to select other video frames and to play back a sequence of video frames. The selected video frame is also displayed in a separate popup window shown below.
Page 276: Transactions And Packets Pane
Industrial / Instrumentation Digital Camera protocol (IIDC) Previous frame Clicking this button will select the first packet of the video frame before the selected frame. Playback video Clicking this button will play back the video frames starting at the selected frame. It tries to play the video back at the recorded rate, but depending on the format and speed the actual playback rate might be lower.
Page 277 Industrial / Instrumentation Digital Camera protocol (IIDC) protocol-specific settings. The dialog will be initialized with all information that can be found automatically. If this is not enough for a correct analysis (e.g. the IIDC unit's base command address was not recorded), you can add this information manually.
Page 278 · Video frame size: This displays the frame size (1394 bus packet size excluding header) for the video frame-data transmitted. It is fully determined by the choices made for the values of 'Video mode', 'Video format' and 'Video frame rate' described above.
Page 279: Chapter 15. Audio Video / Control Protocol (Av/C)
Audio Video / Control protocol (AV/C) Chapter 15. Audio Video / Control protocol (AV/C) 15.1. Recorder Protocol View One of the protocols supported by the Protocol View of the Recorder is the Audio Video / Control (AV/C) protocol. The AV/C protocol-analyzer software will scan through all transactions and packets to find AV/C-compliant Units and it will fill the 'relations' pane in the AV/C tab-page with AV/C-related items (including streams according to IEC 61883), as described in Protocol View and Protocol...
Page 280: How To Use It
Audio Video / Control protocol (AV/C) · AV/C Tuner Subunit Model and Command Set version 2.0, including: · AV/C Tuner Broadcast System Specification - Analog Video - version 1.0 · AV/C Tuner Broadcast System Specification - Analog Audio version 1.1 ·...
Page 281: Details
Audio Video / Control protocol (AV/C) In the example above, an isochronous packet was selected and its details are displayed in the middle part as described above. The extra display, the 'Isochronous source packet' part, will display the isochronous source packet corresponding to the selected isochronous. As defined in the IEC61883 standard, isochronous streams are build from isochronous source packets.
Page 282: Relations Pane
Audio Video / Control protocol (AV/C) 15.1.2.2. Relations Pane This pane shows all transactions and packets found, grouped into items and displayed in a tree. The items are not necessarily recorded in the same order as displayed in this tree. However, all items inside the same item of the tree (at the same level) are listed in the same order as the first corresponding packet of each item was recorded.
Page 283: Details Pane
Audio Video / Control protocol (AV/C) 15.1.2.3. Details Pane When selecting a transaction or stream packet in the 'Transactions and packets' pane, the details of that transaction or stream packet are listed this pane. You can choose between a Field view or a Layout view. We will describe the different parts below: Offset This box displays the address (offset) of the start of the selected item.
Page 284 Audio Video / Control protocol (AV/C) Bandwidth, Channel, Plug register If a Bandwidth allocation/de-allocation transaction or Channel allocation/de-allocation transaction or Plug register transaction was selected in the 'details' pane, the 'details' pane will show the corresponding lock-transaction details. The displayed data consists of 3 parts: Argument, Data and Old data. In the Fields view these 3 data parts are displayed in 3 columns.
Page 285: Transactions And Packets Pane
Audio Video / Control protocol (AV/C) Additionally, the previous and/or next isochronous packet buttons (at the top-right corner) may be enabled. Using these buttons you can easily find the previous or next isochronous packet of a continuous isochronous stream. Previous isochronous packet same stream Clicking this button will select the previous isochronous packet of the same isochronous stream.
Page 286: Isochronous Source Packets Pane
Audio Video / Control protocol (AV/C) Note that the colors identify the type of access and are the same as used in the 'relations' pane (see above). All transactions and packets in this list that are not part of the protocol currently selected in the 'relation' pane are colored gray.
Page 287 Audio Video / Control protocol (AV/C) video). If the 'Isochronous source packets pane' is enabled, the Time View will indicate the source packet shown in the 'Isochronous source packets pane' by displaying a dark brown bar beneath those isochronous packets (or parts of isochronous packets) that are part of the source packet. In the example below, which is a DV video example, one source packet corresponds to one isochronous packet.
Page 288: Bt601 Support
As a part of the AV/C protocol support for BT601 is available. BT601 Message Set Message set is defined in the specification “BT.601 Transport Over IEEE-1394” (document number 2006020). Specification defines two basic packet formats. One is related to the stream information and metadata –...
Page 289: Av/C-Protocol Settings
Audio Video / Control protocol (AV/C) Using BT601 protocol audio and video data can be transferred uncompressed or compressed. Depend on the data format packet has different size, but header remains the same. Figure below shows BT.601 video source header. 15.1.2.6.
Page 290 Audio Video / Control protocol (AV/C) In the dialog you see an upper part to specify one or more 'Node Specifications', and a lower part to specify protocol specific information. In between these two parts, general options can be selected. For a correct analysis, the Unit information of the AV/C device to be analyzed must be present.
Page 291: Editing Av/C Formats
Fixed channels Some applications use 1394 channels for isochronous communication without previous resource allocation. Those channels are predefined, so the same has to be done in the FireWire Protocol Analyzer. In unit description, column “Fixed channel” can be used to assign per unit any channel between 0 and 63, and in case of more channels an array can be defined (e.g.
Page 292: Example
Audio Video / Control protocol (AV/C) You could create a new format set with the FormatEditor and start building your format defintions from scratch. But probably the easiest way is to open an existing format file for the AVC protocol and adapt it to your needs.
Page 293 Audio Video / Control protocol (AV/C) As you can see above, the 'fcp frame' format definition starts with the 'cts', 'ctype', 'subunit type' and 'subunit ID' fields. Then there are some 'if' items for the optional extensions for the 'subunit type' and 'subunit ID' fields.
Page 294 Audio Video / Control protocol (AV/C) Input parameter name value prevCommandCType This is the value of the ctype field of the corresponding AVC command. It can be usefull if the ctype for the command and response blocks are not the same. Set options To be able to use the format definitions in this format set for the AV/C protocol you need to set the correct 'Set options'.
Page 295: Chapter 16. Internet Protocol Version 4 (Ip4)
Internet Protocol version 4 (IP4) Chapter 16. Internet Protocol version 4 (IP4) One of the protocols supported by the Protocol View of the Recorder is the Internet Protocol version 4 (IP4) protocol. The IP4-protocol analyzer software will scan through all transactions and packets to find IP4-compliant Units and it will fill the 'relations' pane in the IP4 tab page with IP4-related items, as described in Protocol View and Protocol...
Page 296: Recorder Protocol View
The Configuration-ROM information is normally read after a bus reset. ARP packets are sent if an IP4 unit wants to communicate with another IP4 unit, but doesn't know the 1394 node id of that unit yet. One way to do this is to (re)connect the IP4 device while the Recorder is recording data.
Page 297: Toolbar
Since there's no option currently in this file format for 1394 packets, the Ethernet format is abused: the source and destination mac address in the dump are used to hold the specification id's of the 1394 nodes. An Ethernet mac address is 6 bytes wide, so the first 2 bytes are set to all zeros. The timing information for each packet is added to a start date of 15 January 1970.
Page 298 The type of items that can be displayed are: · Node: displays a 1394 node with IP4 units inside that node below it. Each node gets a logical node id, which is fixed for the entire recording. This logical node id is called a NodeSpec and is displayed in the tree.
Page 299: Details Pane
Internet Protocol version 4 (IP4) item received by the unit that is part of a group · ungrouped ICMP packet · · un-handled IP packet · broadcast packet For each item in the tree two extra columns indicate the source and destination IP address. Where relevant, the port number is appended to the IP address (e.g.
Page 300: Transactions And Packets Pane
Internet Protocol version 4 (IP4) Fields The 'Fields' table shows the fields that are defined for the selected item and the corresponding values of these fields. See example above. Layout The 'Layout' shows the layout of the selected item. Like the 'Fields' table it shows the fields that are defined for the selected item and the corresponding values of these fields.
Page 301: Ip4 Protocol Settings
Internet Protocol version 4 (IP4) Note that the colors identify the type of access and are the same as used in the 'relations' pane (see above). All transactions and packets in this list that are not part of the protocol currently selected in the 'relation' pane are colored gray.
Page 302 Internet Protocol version 4 (IP4) automatically find IP4 Units. Adding such a Unit will create a Node Specification and Unit. The created Node Specification will be filled automatically when possible. You probably will have to select correct nodes for some reset segments. Make sure you have selected the IP4 node corrrectly for those reset segments for which transaction and packets are recorded that you want to analyze.
Page 303: Chapter 17. Serial Bus Protocol (Sbp)
Serial Bus Protocol (SBP) Chapter 17. Serial Bus Protocol (SBP) 17.1. Recorder Protocol View One of the protocols supported by the Protocol View of the Recorder is the Serial-Bus Protocol (SBP). The SBP-protocol analyzer software will scan through all transactions and packets to find SBP-compliant Units and it will fill the 'relations' pane in the SBP tab page with SBP-related items, as described in Protocol View and Protocol...
Page 304: How To Use It
Serial Bus Protocol (SBP) · Management accesses · Command-agent accesses · Orb reads and next orb-pointer re-read · Data transfers including data tables · Orb status and unsolicited status · Bus resets The details of the item selected in the relations tree, are displayed in the middle part of the Protocol View. It displays the fields defined for the selected item and the values of those fields.
Page 305: Details
Serial Bus Protocol (SBP) information that was send during the login command and is not resend for a reconnect command. This missing information can be added manually, or you should make sure the SBP unit was disconnected for a period longer than 20 seconds, so that a login command will be recorded. Manually inputting SBP information If no Configuration-ROM reads login-command is recorded, you will need to input this information manually.
Page 306: Relations Pane
Serial Bus Protocol (SBP) 17.1.2.2. relations pane This pane shows all transactions and packets found, grouped into items and displayed in a tree. The tree structure indicates the relation between the items. The items are not necessarily recorded in the same order as displayed in this tree.
Page 307 Serial Bus Protocol (SBP) We will describe the different parts below: Offset This box displays the address (offset) of the start of the selected item. Length The 'Length' box shows the size of the selected item in bytes. Num. Trans. This box shows the number of transactions that corresponds to the selected item.
Page 308 Serial Bus Protocol (SBP) Without the option checked (example above), all the fields of the item are listed, including the command-set-specific part ('command block' in the example above). Note however, that the command-set-specific part is not formatted in this case. It is just the SBP definition of the ORB block. When the 'show command-set-specific format' option is selected, only the command-set-specific part is displayed.
Page 309: Transactions And Packets Pane
Serial Bus Protocol (SBP) defined for the selected item and the corresponding values of these fields. But now the fields are displayed graphically. When a part of the item contains command-set-specific information, the user has the option to show all the item fields (including the unformatted command data) or only the command data formatted corresponding to the defined command set.
Page 310: Protocol Settings
Serial Bus Protocol (SBP) in the 'transactions and packets' pane list with a gray bar (the selected item, which is also part of the item will still be highlighted with the usual selection color). The example below corresponds to the examples in the 'Fields' and 'Layout' descriptions above. Thus the selected item consists of 8 transactions and the third transaction is selected.
Page 311 Serial Bus Protocol (SBP) In the dialog you see an upper part to specify one or more 'Node Specifications', and a lower part to specify protocol-specific information. In between these two parts, general options can be selected. In the protocol-specific part one or more 'Units' can be specified for each protocol. For a correct analysis the Unit information of the SBP device to be analyzed must be present.
Page 312 Serial Bus Protocol (SBP) skipped. · Node Spec.: A Unit is part of a node. As explained before, nodes are specified using Node Specifications. The number in this column corresponds to the Node-Specification numbers of the table in the upper part of the dialog. ·...
Page 313: Editing Sbp2 Formats
Serial Bus Protocol (SBP) this could be the status fifo address. Fill it in, try it and if status formatting errors occur, you probably have the wrong one. · ORB pointer: This field is needed if the first write to the 'ORB pointer write' register was not recorded. If your login was not recorded, this one is probably not recorded either.
Page 314: Data
Serial Bus Protocol (SBP) The command always starts with an operation code field. The format of the remaining bytes depend on the value of this operation code. A 'switch' item is used to implement the different commands. The implementation of the 'INQUIRE' command is shown ('case INQUIRE' item expanded) in more detail. One of its field is the 'cmddt' field.
Page 315 Serial Bus Protocol (SBP) As for the 'command' format, the 'data' format depends on the 'operation code'. A 'switch' item is used to implement the formats for the different operation codes. The value of the operation code is however not included in the packet (as it was for the 'command' format).
Page 316: Status
Serial Bus Protocol (SBP) 17.2.1.3. Status The format definition 'status' defines the format of the command set dependent part of the status block. This is the part of the status block after the first two quadlets. It only need to be present when it differs from the standard format for a SBP2 status packet.
Page 317: Set Options
Serial Bus Protocol (SBP) 17.2.2. Set Options To be able to use the format definitions in this format set for the SBP2 protocol you need to set the correct 'Set options. Below the 'Set options' of the example file are shown. The 'Set type' should be 'SBP'.
Page 318 Serial Bus Protocol (SBP) recognized automatically, then you must expand the list above. This list is part of the format set with file name 'sbp_scsi_general.dff'. If you open this file, you will see a format definition named 'device type'. See below.
Page 319: Chapter 18. Automotive Multimedia Interface - Collaboration Protocol (Ami-C)
Automotive Multimedia Interface - Collaboration protocol (AMI-C) Chapter 18. Automotive Multimedia Interface - Collaboration protocol (AMI-C) 18.1. Recorder Protocol View One of the protocols supported by the Protocol View of the Recorder is the Automotive Multimedia Interface - Collaboration (AMI-C) protocol. The AMI-C protocol-analyzer software will scan through all transactions and packets to find AMI-C-compliant Units and it will fill the 'relations' pane in the AMI-C tab-page with AMI-C-related items.
Page 320: Details
Automotive Multimedia Interface - Collaboration protocol (AMI-C) The AMI-C-protocol analyzer needs some information from the Configuration ROM of a AMI-C device, to be able to analyze the AMI-C transactions and packets corresponding to this device. There are two ways the analyzer can get this information: automatically or manually. Automatically finding AMI-C information To make sure the AMI-C analyzer finds the AMI-C information automatically, you should make sure that the reading of Configuration ROM for the node id of the unit is recorded.
Page 321: Relations Pane
Automotive Multimedia Interface - Collaboration protocol (AMI-C) It contains the following additional control: Analyzer node select control With this control you are able to select the protocol analysis result of each supported Analyzer node. 18.1.2.2. Relations Pane This pane shows all transactions and packets found, grouped into items and displayed in a tree. The tree structure indicates the relation between the items.
Page 322 Automotive Multimedia Interface - Collaboration protocol (AMI-C) Offset This box displays the address (offset) of the start of the selected item. Length The 'Length' box shows the size of the selected item in bytes. Num. Trans. This box shows the number of transactions that corresponds to the selected item. For AMI-C this will always be 1.
Page 323 Automotive Multimedia Interface - Collaboration protocol (AMI-C) 18.1.2.4. transactions and packets pane The right-most part of the Protocol View shows the sequence of all found protocol packets and transactions (including those for AMI-C). The order of items in this list corresponds to the order of recording.
Page 324 Automotive Multimedia Interface - Collaboration protocol (AMI-C) When an item is selected that consists of more than one packet or transaction, the items are highlighted in the 'transactions and packets' pane list with a gray bar (the selected item, which is also part of the item will still be highlighted with the usual selection color).
Page 325 Automotive Multimedia Interface - Collaboration protocol (AMI-C) In the dialog you see an upper part to specify one or more 'Node Specifications', and a lower part to specify protocol specific information. In between these two parts, general options can be selected. For a correct analysis, the Unit information of the AMI-C device to be analyzed must be present.
Page 326 Automotive Multimedia Interface - Collaboration protocol (AMI-C) Check this box to enable the AMI-C analyzer. All protocol tabs in this dialog have such a checkbox, which can be useful if a recording contains data from several protocols, and you are not interested in some of these.
Page 327 Automotive Multimedia Interface - Collaboration protocol (AMI-C) As you can see above, the 'VIP Frame' format definition starts with fields 'CTS' and 'ACC'. To identify 'VIP Frame' these values have to be 'CTS'=4 and 'ACC'=0. 'AMI-C Frame' is encapsulated in 'VIP Frame' and has two possible transactions: - Application transaction, 'System Bit'=0, - System transaction,...
Page 328 Automotive Multimedia Interface - Collaboration protocol (AMI-C) The 'Set type' should be 'AMI-C'. The 'Set key' must be set to the subunit type corresponding to the command set you have implemented by this format set. The 'Set name' must be unique for all AMI-C type files.
Page 329 Custom Protocols Chapter 19. Custom Protocols Custom-made protocols are supported by the Protocol View of the Recorder. The protocol analyzer takes into account the custom-made protocols for which protocol definitions are available. A protocol definition lay down the behavior of a custom-made protocol. Protocol definitions are created with the Protocol editor.
Page 330 Custom Protocols this part is filled completely (see the Recorder for more information). Manually inputting custom-made protocol information If no Configuration-ROM reads are recorded, you will need to input this information manually. Also if only part of this information can be found automatically, you will need to add information manually. You can do this in the 'Protocol Settings' dialog.
Page 331 Custom Protocols For each found or manually specified NodeSpec there will be a root item in the tree (NodeSpec 0 above). For information about NodeSpec's, see 'Custom-made Protocol Settings' below. For each found or manually specified Unit, there will be a Unit item inside the corresponding NodeSpec (Unit 0 in NodeSpec 0 above).
Page 332 Custom Protocols The 'Fields' table shows the fields that are defined for the selected item and the corresponding values of these fields. See example above. Layout The 'Layout' shows the layout of the selected item. Like the 'Fields' table it shows the fields that are defined for the selected item and the corresponding values of these fields.
Page 333 Custom Protocols 'relation' pane are colored gray. 19.3.5. Custom Protocol Settings When clicking the 'Protocol Settings' button in the toolbar of the Protocol View, the 'Protocol Settings' dialog will be displayed. This dialog shows information used by the protocol analyzer to find and correctly analyze the transactions.
Page 334 Custom Protocols Mark unhandled packets For information about this checkbox, please see Protocol Settings. Protocol-specific information Enable analysis Check this box to enable the analysis of this custom-made protocol. All protocol tabs in this dialog have such a checkbox, which can be useful if a recording contains data from several protocols, and you are not interested in some of these.
Page 335: Global Settings
Settings Chapter 20. Settings With the settings dialog you can control all kinds of Analyzer settings. There are general settings like which windows should open when the application is started, and there are settings for individual windows. The settings are persistent. So, when starting the Analyzer application the next time, the last settings will be applied automatically.Since the redesign of the settingsdialog in version 4.1, device dependent settings are saved per analyzer.
Page 336 Settings If the 'Use Analyzer appearance' box is checked, the Analyzer-type colors will be used for all windows. If this box is not checked, the standard system colors will be used. All examples in this manual use the Analyzer-type colors. After changing the checkbox, you can use the 'Apply' or 'OK' button to activate it.
Page 337 Settings 20.2.1.3. LAN Devices The FireDiagnosticsSuite can use Analyzers connected via ethernet after they are configured with the EthernetConfig tool. To have the application look for an ethernet device, add its IP Address in the box above. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 338 Settings 20.2.1.4. Mil1394 Mil1394 Protocol The picture above shows the Mil1394 protocol settings page. As of software version 5 it is recommended to use an XML file to define all important aspects of the AS5643 protocol according to the specifications of the program. An example file named "Mil1394Settings.xml"...
Page 339 Settings 20.2.1.5. Protocol Custom Protocol Directories The picture above shows the custom protocols. It can be used to define all locations the application should search for custom protocol definitions. For more information about custom protocols, please read Protocol Editor section. Depending on your license, this setting might be disabled.
Page 340 Settings 20.2.2. FireSuiteApplication 20.2.2.1. Startup Open at Application start In this box you can specify which windows should open at application start. In the example above, none of the windows will open. The little main window will always open at startup. If you want to change these settings, you need to apply the new settings.
Page 341 Settings 20.2.2.2. Topology Custom Icons Directories This list box can be used to define all locations the software should search for custom icons used by the Topology view of the Commander. For more details, please read the Commander Topology section. Copyright ©...
Page 342 Settings 20.2.3. Recorder 20.2.3.1. Recordings Temporary Recorder Data This setting only applies to Third Generation Analyzers. In this box you can choose a folder location where to store temporary recording files that are created during recording and the maximum file size. Please choose a folder on a fast hard drive or SSD to keep up with the data that is received on the bus.
Page 343 Settings 20.2.4. Scriptor 20.2.4.1. Editor Highlight colors This section contains several color settings that can be changed to let the Scriptor tree editor use different colors for syntax highlighting. It contains the following items: · Default: All text that is not covered by one of the other highlight items ·...
Page 344 Settings 20.2.4.2. Misc Default Scripts Folder Specify a folder here that will be used as the default folder for scripts. This folder will be the starting point of a file open or file save dialog is displayed. Send initial values before starting the Scriptor on every start. When input control are used on the Control Panel, they only send their values to the scriptor when they are changed.
Page 345 Settings 20.2.5.1. Preferences Control Label Colors When Controls are added to the Mil1394 Signal Monitor Controls View the label color can automatically be chosen from a predefined set of colors. To enable this functionality the check box "Enable auto label color selection"...
Page 346 Settings 20.2.6. Device 20.2.6.1. Alias Aliases The Aliases setting allows an user to enter a nickname to a device and/or its busses. The device name can be used to change the window name. The bus names are currently only used by the monitor. Copyright ©...
Page 347 It will be visible to the user by showing a progress dialog. Mil1394 Mode If enabled, the generator can be used for generating Mil1394 Streams instead of standard 1394 isochronous streams. Furthermore, the Scriptor will also contain some additional Mil1394 Functions for Frame timing.
Page 348 Settings 20.2.6.3. Connection Data-Pickup Logic Connection-Settings As the FireStealth does not have auto detection of the bus speed, the user must supply it by means of these configuration settings. Setting the line speed can be done by making a selection in the Speed box between S800, S400, S200 and S100.
Page 349 Settings 20.2.6.4. External Timing The FireSpy385X is capable of synchronization between multiple analyzers by setting one as a time master and the others as time slave. Time on the master can be configured either using an internal clock running in free running mode or using an IRIG timing source (in combination with a DapTechnology IRIG Demodulator) to synchronize the internal clock.
Page 350 Settings 20.2.6.5. FilterTrigger Initial Filter/Trigger file This box specifies the file that should be opened in the Filter/Trigger Settings dialog and that should be uploaded to the Analyzer (if connected) at application start. You can change the file by using the 'Browse' button, which will start a file dialog to choose a file.
Page 351 Settings 20.2.6.6. IDC Connector /OutA, B, C, D, E, F and /InA, B ,C These ports can be used as a part of the Trigger Sequencer and the General Trigger. The ports can also be controlled by Port I/O in the Scriptor. /TriggerOut This port can be associated with a trigger event.
Page 352 Settings 20.2.6.7. Memory The total memory is shown as the last item in the list. Part of the internal memory is allocated by the Analyzer itself. This allocation is fixed and cannot be changed. The following fixed memory allocations exist: Internal Use This part of the memory is used by the Analyzer itself for internal housekeeping.
Page 353 Bus Power This section is only available for the advanced series of analyzers.It contains a check box for each Analyzer node. By enabling the check box for a specific node, this node will provide power to the 1394 bus. Analyzers with only a single node will only show "Enable Bus Power".
Page 354 Settings 20.2.6.9. SUBD Connector /OutA, B, C, D, E, F and /InA, B ,C These ports can be used as a part of the Trigger Sequencer and the General Trigger. The ports can also be controlled by Port I/O in the Scriptor. /TriggerOut This port can be associated with a trigger event.
Page 355 Settings 20.2.6.10. VHDCI Connector /OutA, B, C, D, E, F and /InA, B ,C These ports can be used as a part of the Trigger Sequencer and the General Trigger. The ports can also be controlled by Port I/O in the Scriptor. /TriggerOut This port can be associated with a trigger event.
Page 356 Settings 20.2.6.11. Inter Board Connector /OutA, B, C, D, E, F and /InA, B ,C These ports can be used as a part of the Trigger Sequencer and the General Trigger. The ports can also be controlled by Port I/O in the Scriptor. /TriggerOut This port can be associated with a trigger event.
Page 357 Format Editor Chapter 21. Format Editor Using the FormatEditor you can define format sets. A format set is stored in a file with .dff extension. Each format set consists of one or more format definitions which the Analyzer application can use to display formatted data in a table form or layout form.
Page 358 Format Editor In the following image, the format definition file of a SBP2 format set has been opened. In the 'Definition' pane you see the format definitions tree. The name of the first definition is 'command'. It starts with a field with name 'operation code'. This item is selected, so the properties of this 'Field' item are displayed below.
Page 359 Format Editor It defines an SBP (SBP2) Set type for a Direct-access (SBC) device. The Set type and Set name and sometimes the Set key are used by the Analyzer to find the correct format definitions. How these fields need to be filled in depends on the protocol the format set is used for. For details on this, see the corresponding document file (e.g.
Page 360 Format Editor parameters are not really needed for the selected format definition). 21.1.3. Built-in variables and functions The following built-in variables and functions can be used in expressions: Name Description databits This variable reflects the number of bits in the data block to be formatted.
Page 361 Format Editor The "Set Options" tab for this example looks as follows: A set should always be of one of the known "Set Types". This enables automatic loading by the Analyzer application. Furthermore, the field "Set name" should not be set to "general" as this name is used by all Copyright ©...
Page 362 Format Editor built-in format sets. Please use something else. To use your own format sets, you have to tell the Analyzer application where to find them. This can be done in the Settings dialog of the Analyzer application. The picture below shows the relevant section of the Settings dialog for the above example.
Page 364 Protocol Editor Chapter 22. Protocol Editor The Protocol editor is a tool to create a protocol definition for a specific high-level protocol. This high-level protocol could be one of the standard high-level protocols for example: AV/C, SBP-2, IIDC, etc. or your own custom-made high-level protocol.
Page 365: File Menu
Protocol Editor 22.2. Details 22.2.1. Caption Bar In the caption bar you see the filename between brackets of the displayed protocol definition. If a new created protocol definition is displayed as shown above and it hasn't been saved to file yet 'untitled' is displayed between the brackets.
Page 366 Protocol Editor 22.2.4. Address ranges Below the text fields Protocol name and Protocol identity you see the Address ranges table and its buttons Remove and New. Table Address ranges displays the created address ranges. Each row of the table displays an address range.
Page 367 Protocol Editor 22.2.5. Fixed channels Already defined custom protocol you can extend with fixed channels. It means that you can assign custom isochronous protocol to one channel of your choice. Image below illustrates five fixed channels within SBP-2 protocol. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 368 File Formats Chapter 23. File Formats This chapter describes all file formats supported by the Analyzer software that were intended for use by the customer. 23.1. Hex Data file Hex data files have the extension .hex and contain one or more data blocks in hexadecimal format. The file is an ascii file and the new lines may be indicated with a cariage-return or line-feed, or both.
Page 369 File Formats The following example defines 5 quadlets of data: FFFF008Fh FFC5FFFFh F0000200h BAB27024h 78AE439Fh The same 5 quadlets could also be written as: 4294901903 4291166207 4026532352 3132256292 2024686495 If more than one blocks of data are present, the blocks are separated by one or more lines containing no data.
Page 370 File Formats The block header is one 32-bit value. The upper 12 bits define a block id and the lower 20 bits define the length of the block data in bytes. If the length is not a multiple of 4 bytes, the block data is padded with zero-value bytes. The only block type defined at this moment is a packet block it has a block id of 0, the specified length in the header equals the number of packet bytes and the block data consists of the packet quadlets.
Page 371 File Formats Filed Contents - Type 1 - Time Resolution Frequency 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0x01 0x01 Time Resolution Frequency...
Page 372 Data Size in Quadlets: Number of Data Quadlets (including CRCs) (18 bits) Time Field: 0, 32 or 64 bits depending on Time Format Header: 1394 Header Contents (Quadlet aligned) Header CRC: 1394 Header CRC (Quadlet aligned) Data: 1394 Data Contents Data CRC: 1394 Data CRC 23.5.
Page 373 File Formats value. Units ascii text Used to decorate the Control Panel psi, V/m uint32, int32, DataType ascii text The data type of the signal. See below for float32, float64, the special data type 'enum'. enum Note : if a signal is of data type 'enum', additional columns with label, value pairs must follow. The number of pairs is user-defined.
Page 374 File Formats Channel Definitions node contains a list of nodes, each of which define a channel's properties. The ChannelList Channel can be defined, as well as the properties of the Heartbeat DeviceName Offset Length Transmit frames (within the respective childnodes). These nodes can be omitted or their Receive Datapump attributes set to zero to invalidate those kinds of messages for the respective channel.
Page 375 File Formats specified field. For the sake of clarity it is recommended to explicitly define the offsets. Please note that the fields still have to be in bitwise order. (default 32) NumBits The number of bits that mark the value of the field. This may span accross quadlet alignments. (optional) Name The name of the field.
Page 376 File Formats <Reserved QuadOffset="1" FirstBit="0" NumBits="32" DataType="hex"/> <NodeID QuadOffset="2" FirstBit="0" NumBits="32" DataType="udec"/> <MessagePayloadDataLength QuadOffset="3" FirstBit="0" NumBits="24" DataType="udec"/> <Priority QuadOffset="3" FirstBit="24" NumBits="8" DataType="udec"/> </ASMHeader> <PayloadData> <HealthStatus QuadOffset="0" FirstBit="0" NumBits="32" DataType="hex"> <Port Name="Port 2"> <Struct Name="Port Struct"/> </Port> <Port Name="Port 1"> <Struct Name="Port Struct"/>...
Page 377 File Formats FirstBit="16" NumBits="16"/> </MessageDefinition> <MessageDefinition Channel="5" MessageID="0"> <SignalGroup> <Signal Name="sensors_heartbeat" DataType="udec" QuadOffset="0"/> <Signal Name="sensors_sensor1" DataType="dec" QuadOffset="2" EnumName="switch"/> </SignalGroup> </MessageDefinition> </MessageDefinitions> Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 378 The FireSpy9x32bT has nine 1394 nodes connected to nine synchronized analysis engines. They are controlled by three dual core ARM processors running at 667MHz. Each node is connected to two 1394 ports. Both ports of each node are connected to a separate LEMO connector which was chosen over standard 1394 connectors for improved ruggedness.
Page 379 Hardware · Connects to host using USB3.0 interface · 15GByte memory for embedded OS and packet and data storage · Firmware field upgradeable to enable future expansions · AUX connector for: o Trigger input and output functions o Recording external events ·...
Page 380 Power Requirements: FCC Class A Compliance: Connections: · USB 3.0 connector for host-computer · 18x LEMO connectors (EYG.0B.304) for 1394 Beta connections · Auxiliary connector · Power connector Indicators: · Multi-colored LEDs for: Unit status, Recorder, Generator, Trigger, Active (per node) ·...
Page 381 Hardware 24.1.1.3. FireSpy Front Generator LED This LED will light up green while the FireSpy Generator is active. See Generator. Recorder LED This LED will light up red while recording is in progress. After the recording stops it will be orange during the post-processing phase.
Page 382 Hardware The Power LED will light up red when power is supplied to the power connector on the back. Please be aware that this LED also lights up when the Power Switch on the back is in the Off position. USB LED The USB LED will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy Rear' below) and the computer is switched on.
Page 383 The FireSpy6x32bT has six 1394 nodes connected to six synchronized analysis engines. They are controlled by two dual core ARM processors running at 667MHz. Each node is connected to two 1394 ports. Both ports of each node are connected to a separate LEMO connector which was chosen over standard 1394 connectors for improved ruggedness.
Page 384 Hardware · Counts number of bus resets RECORDER · Time stamping of all packets and status events with 10ns resolution · Packets hidden by slower connections are visible as ‘prefix only’ packets · Extensive packet/event filtering/trigger/search capabilities o Packet type o Transmission speed o Boolean combination of 4 programmable packet sets o Data payload patterns...
Page 385 Power Requirements: FCC Class A Compliance: Connections: · USB 3.0 connector for host-computer · 12x LEMO connectors (EYG.0B.304) for 1394 Beta connections · Auxiliary connector · Power connector Indicators: · Multi-colored LEDs for: Unit status, Recorder, Generator, Trigger, Active (per node) ·...
Page 386 Hardware 24.1.2.3. FireSpy Front Generator LED This LED will light up green while the FireSpy Generator is active. See Generator. Recorder LED This LED will light up red while recording is in progress. After the recording stops it will be orange during the post-processing phase.
Page 387 Hardware The Power LED will light up red when power is supplied to the power connector on the back. Please be aware that this LED also lights up when the Power Switch on the back is in the Off position. USB LED The USB LED will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy Rear' below) and the computer is switched on.
Page 388 The FireSpy3x30xx has three 1394 nodes connected to three synchronized analysis engines. They are controlled by a dual core ARM processor running at 667MHz. Each node is connected to three 1394 ports. All ports of each node are connected to a separate IEEE-1394 connector with screw mount holes which was chosen over standard 1394 connectors for improved ruggedness.
Page 389 Hardware · Counts number of bus resets RECORDER · Time stamping of all packets and status events with 10ns resolution · Packets hidden by slower connections are visible as ‘prefix only’ packets · Extensive packet/event filtering/trigger/search capabilities o Packet type o Transmission speed o Boolean combination of 4 programmable packet sets o Data payload patterns...
Page 390 12 V, 40Watt max. Power Requirements: FCC Class A Compliance: Connections: · USB 3.0 connector for host-computer · 9x IEEE-1394 connectors with screw holes · Auxiliary connector · Power connector Indicators: · Multi-colored LEDs for: Unit status, Recorder, Generator, Trigger, Active (per node) ·...
Page 391 The USB LED will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy Rear' below) and the computer is switched on. It indicates the availability of USB bus power. IEEE-1394 Connectors Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 392 Hardware With these connectors the FireSpy can be connected to the IEEE1394 bus to be analyzed. Each connector may be connected to the bus. The IEEE1394b ports are (top-down, left-right) A0, A1, A2, B0, B1, B2, C0, C1, C2. Depending on the exact model, each connector is transformer coupled. 24.1.3.4.
Page 393 The FireSpy3x22bT have three 1394 nodes connected to three synchronized analysis engines. They are controlled by a dual core ARM processor running at 667MHz. Each node is connected to two 1394 ports. Two ports of each 1394 node are connected to a LEMO connector.
Page 394 Hardware · Measurement of bus power voltages (bilingual ports) RECORDER · Time stamping of all packets and status events with 10ns resolution · Packets hidden by slower connections are visible as ‘prefix only’ packets · Extensive packet/event filtering/trigger/search capabilities o Packet type o Transmission speed o Boolean combination of 4 programmable packet sets o Data payload patterns...
Page 395 Hardware 24.1.4.2. Specifications 4-lane PCIe: card length approx. 205 mm Dimensions: Weight: 0 – 70 C Operating Range: 25Watt max. Power Requirements: FCC Class A Compliance: Connections: · PCIe connector · 6x LEMO connectors · Auxiliary connector Indicators: Switches: Package Content: FireSpy3x22bT 3x LEMO to Bilingual cables 36 months limited warranty...
Page 396 24.1.5. FireSpy 4430b, 4430bT, 4830, 4830bT The FireSpy4x30xx bus analyzer is world’s only four-node IEEE-1394 bus analyzer. Based on the 4th generation FireSpy analyzer architecture the FireSpy4x30xx is the most advanced 1394 test equipment in the market. The FireSpy4x30xx in fact combines four FireSpy analyzers in one single instrument. It comprises a significantly more powerful on-board processor and improved connectivity to the host.
Page 397 The FireSpy4x30xx has four 1394 nodes connected to four synchronized analysis engines. They are controlled by two dual core ARM processors running at 667MHz. Each node is connected to three 1394 ports. All ports of each node are connected to a separate IEEE-1394 connector with screw mount holes which was chosen over standard 1394 connectors for improved ruggedness.
Page 398 Hardware · Extensive packet/event filtering/trigger/search capabilities o Packet type o Transmission speed o Boolean combination of 4 programmable packet sets o Data payload patterns o Error conditions o Various status events o Graphical Trigger Sequencer · Adjustable trigger position within programmable record buffer size ·...
Page 399 12 V, 40Watt max. Power Requirements: FCC Class A Compliance: Connections: · USB 3.0 connector for host-computer · 12x IEEE-1394 connectors with screw holes · Auxiliary connector · Power connector Indicators: · Multi-colored LEDs for: Unit status, Recorder, Generator, Trigger, Active (per node) ·...
Page 400 Hardware 24.1.5.3. FireSpy Front Generator LED This LED will light up green while the FireSpy Generator is active. See Generator. Recorder LED This LED will light up red while recording is in progress. After the recording stops it will be orange during the post-processing phase.
Page 401 The USB LED will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy Rear' below) and the computer is switched on. It indicates the availability of USB bus power. IEEE-1394 Connectors With these connectors the FireSpy can be connected to the IEEE1394 bus to be analyzed. Each connector may be connected to the bus.
Page 402 24.2. Advanced Series The “Advanced Series” of FireSpys redefines 1394 data analysis! Built on top of the proven “Basic Series” this brand-new line features better performance due to a more powerful on-board processor, bus power provider capability, new connectivity interfaces (USB 2.0 and Ethernet, PCI), enhanced Scriptor...
Page 403 Hardware · several types of Errors · Counts packets according to type, speed, ack and error condition · Counts number of bus resets · Measurement of bus power voltages Recorder · Time stamping of all packets and status events with 10ns resolution ·...
Page 404 Hardware 24.2.1.2. Specifications 125 mm x 48 mm x 224 mm Dimensions: 760 g Weight: 12 V, 10 Watt maximum (without providing 1394 bus power) Power Requirements: FCC Class A Compliance: USB2.0-connector for host-computer Connections: RJ45 Ethernet connector 2 IEEE 1394-connectors (bilingual/Beta)
Page 405 Hardware 24.2.1.3. FireSpy Front USB led This green led will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy 400 Rear' below) and the computer is switched on. It indicates the availability of USB bus power. power led This green led will light up when the power supply is connected to FireSpy (see 'FireSpy 400 Rear' below) and the FireSpy is switched on.
Page 406 Hardware The FireSpy is triggered when it detects a positive pulse of minimal 3 Volt (resulting in a current of about 1.6 mA) and a duration of typical 10 uS. 24.2.1.4. FireSpy Rear power switch Using this switch the FireSpy can be switched on (powered) and off. When switched on the 'power led' on the front will light up.
Page 407 DapTechnology. Based on the industry leading FireSpy800 the all new and enhanced architecture of the FireSpy810 has raised the bar in IEEE 1394 test equipment! It comprises a significantly more powerful on-board processor, more memory and improved connectivity to the host.
Page 408 Hardware · External Trigger Input, positive edge · AUX connector for: · Trigger input and output functions · Recording external events · Software runs on Windows™ XP and Windows™ 7 Monitor · Displays bus activity: · Counts packets according to type, speed, ack and error condition ·...
Page 409 24.2.2.2. Specifications Dimensions: 125 mm x 48 mm x 224 mm Weight: 760 g Power Requirements: 12 V, 10 Watt maximum (without providing 1394 bus power) Compliance: FCC Class A Connections: USB2.0-connector for host-computer RJ45 Ethernet connector 2 IEEE 1394-connectors (bilingual/Beta)
Page 410 Hardware 24.2.2.3. FireSpy Front power led This green led will light up when the power supply is connected to the FireSpy (see 'FireSpy 810 Rear' below) and the FireSpy is switched on. It indicates the availability of power from the power supply USB led This green led will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy 810 Rear' below) and the computer is switched on.
Page 411 Hardware This red led will light when recording is in progress. See Recorder. trigger led This green led will light up when the FireSpy Recorder has been triggered. See Recorder. manual trigger Pressing this button will trigger the Recorder when recording is in progress and the Recorder is not yet triggered.
Page 412 They support up to 800Mb (400Mb for the FS450b(T), 200Mb for the FS450bT1) transfer rate and are fully IEEE 1394b compliant. Three bilingual or Beta 1394 ports (depending on model) allow for convenient connection to the system under test. As an added feature the FS450b uses dip-switches to conveniently allow the changing of PHY port speed/mode settings.
Page 413 Hardware · Measurement of bus power voltages (except FS450bT(1) ) Recorder · Time stamping of all packets and status events with 10ns resolution · Packets hidden by slower connections are visible as ‘prefix only’ packets · Extensive packet/event filtering/trigger/search capabilities ·...
Page 414 210 x 20 x 129 mm CPCI: 150 g / TBD Weight: Operating Range: 0 – 70 C 12V, 10 Watt maximum (without providing 1394 bus power) Power Requirements: FCC Class A Compliance: 32bit/33MHz PCI connector, universal keyed (for 3.3V and 5V slots)
Page 415 Hardware 24.2.3.3. The PCI board This FireSpy is a PCI card. It must be build into a PC. IDC connector The IDC connector is an auxiliary port.The auxiliary port will be discussed in a separate chapter. See Auxiliary connector ports. . IEEE1394b connectors (3x) With these connectors the FireSpy can be connected to the IEEE1394 bus to be analyzed.
Page 416 Based on the industry leading FireSpy800 and the new FireSpy3810 architecture the FireSpy3810 is the most advanced IEEE 1394 test equipment in the market. The FireSpy3810 in fact combines three FireSpy analyzers in one single instrument. It comprises a significantly more powerful on-board processor and improved connectivity to the host.
Page 417 · FS3410bT(1): Supports 100(B) and 200(B) Mbps connection speeds · Connects to host using USB2.0 interface or to LAN via 10/100 BaseT · Electrical isolation between IEEE 1394 and host (USB) · Optional Bus Power: 2.8 Watts at 12 Volt (for each bilingual port) ·...
Page 418 Hardware · Graphically programming of stream transmit block · Data payload import from file · Generator and Scriptor run simultaneous for stream and asynchronous packet generation · Special AS5643 stream generator package (optional) Scriptor · Script Editor · C-like scripting language ·...
Page 419 125 mm x 48 mm x 209 mm Dimensions: 800 g Weight: 0 – 45 C Operating Range: 12 V, 10 Watt maximum (without providing 1394 bus power) Power Requirements: FCC Class A Compliance: USB2.0-connector for host-computer Connections: RJ45 Ethernet connector For FS3810, FS3410bT(1): ·...
Page 420 Hardware 24.3.1.3. FS3810 and FS3410bT(1) Front VHDCI connector This connector is a 68 pins connector. It encompasses the transformer coupled IEEE1394b ports A0, A1, B0, B1, C0, C1 and a 6 aux port signals. The auxiliary port will be discussed in a separate chapter. See Auxiliary connector ports.
Page 421 Hardware This red led will light up when the Scriptor is active. See Scriptor. generator led This red led will light up when the FireSpy Generator is active. See Generator. record led This red led will light when recording is in progress. See Recorder. trigger led This green led will light up when the FireSpy Recorder has been triggered.
Page 422 Hardware Each connector is bilingual. This means that they can be connected to a 1394b (beta) port or to a 1394a (legacy) port, by using the correct cables. buzzer opening Behind this hole a buzzer is installed. active led This red led will light up when the Scriptor is active. See Scriptor. generator led This red led will light up when the FireSpy Generator is active.
Page 423 24.3.2. FireSpy 3850, 3851 The FireSpy385x bus analyzer is world’s only PCI –based multichannel FireWire bus analyzer. Based on the industry leading FireSpy810 architecture the FireSpy385x is the most advanced IEEE 1394 test equipment in the market. The FireSpy385x in fact combines three FireSpy analyzers in one single instrument.
Page 424 Hardware · several types of Errors · Counts packets according to type, speed, ack and error condition · Counts number of bus resets · Measurement of bus power voltages (bilingual ports) Recorder · Time stamping of all packets and status events with 10ns resolution ·...
Page 425 Dimensions: 150 g Weight: 0 – 70 C Operating Range: Power Requirements: 12 V, 10 Watt maximum (without providing 1394 bus power) FCC Class A Compliance: Connections: · 32bit/33MHz PCI connector, universal keyed (for 3.3V and 5V slots) · 3 IEEE 1394-connectors (bilingual) ·...
Page 426 Hardware 24.3.2.3. The FS3850, FS3851 PCI board This FireSpy is a PCI card. It must be build into a PC. IDC connector The IDC connector is an auxiliary port.The auxiliary port will be discussed in a separate chapter. See Auxiliary connector ports.
Page 427 24.3.3. FireSpy 3852 The FireSpy385x bus analyzer is world’s only PCI –based multichannel FireWire bus analyzer. Based on the industry leading FireSpy810 architecture the FireSpy385x is the most advanced IEEE 1394 test equipment in the market. The FireSpy385x in fact combines three FireSpy analyzers in one single instrument.
Page 428 Hardware · Error conditions · Various status events · Graphical Trigger Sequencer · Adjustable trigger position within programmable record buffer size · Cyclic pre-trigger buffer management option · Different kinds of packet display views, including: · Time View, displays all packets on a time line, including the prefix ·...
Page 429 Dimensions: 150 g Weight: 0 – 70 C Operating Range: Power Requirements: 12 V, 10 Watt maximum (without providing 1394 bus power) FCC Class A Compliance: Connections: · 32bit/33MHz PCI connector, universal keyed (for 3.3V and 5V slots) · 6x Circular LEMO connector type FGG.0B.304.CLAD42...
Page 430 Hardware 24.3.3.3. The FS3852 PCI board This FireSpy is a PCI card. It must be build into a PC. IDC connector The IDC connector is an auxiliary port.The auxiliary port will be discussed in a separate chapter. See Auxiliary connector ports.
Page 431 Hardware 24.3.4. FireSpy 3470 24.3.4.1. Main Feature Summary General · IEEE 1394-19000595, 1394a-2000 and 1394b-2002 compliant · Supports 400(B) Mbps transfer rates · Compact PCI PICMG 2.0 R3.0 compliant · PXI 2.2 compliant* · 992 MByte memory for packet and data storage ·...
Page 432 Hardware · Script Editor · C-like scripting language · Function Library · Macros to automatically generate blocks of code · Syntax coloring · Integrated Debugger · Floating point data types · Data Editor · Control Panel · Graphical display elements for data value representation ·...
Page 433 Hardware 24.3.4.3. The PXI Board This FireSpy is a CompactPCI / PXI card, it must be fitted in a CompactPCI / PXI chassis. SCSI2 Connector This connector is a 68 pins connector. It encompasses the transformer coupled IEEE1394b ports A0, A1, A2, B0, B1, B2, C0, C1 and C2 Compact PCI connector The PCI connector is the connection between this FireSpy and the computer it is to work with.
Page 434 · Supports 100(B), 200(B), 400(B) and 800(B) Mbps transfer rates · Connects to host using USB2.0 interface or to LAN via 10/100 BaseT · Electrical isolation between IEEE 1394 and host (USB) · 992 MByte memory for packet and data storage ·...
Page 435 Compliance: Connections: · USB2.0-connector for host-computer · RJ45 Ethernet connector · 2 IEEE 1394-connectors (Beta) Indicators: · Green LEDs for: Sync, Speed , USB, Power, Ethernet, Trigger · Red LEDs for: Record, Scriptor Active, Ready · Bicolor LEDs for: Port Polarity, Port Signal ·...
Page 436 Hardware 24.4.1.3. FireStealth Front Polarity led This dual colored (green/red) led will light up green whenever the FireStealth has participated in the connection setup of the IEEE 1394b bus and has detected that the polarity of the cable is normal. This dual colored (green/red) led will light up red whenever the FireStealth has participated in the connection setup of the IEEE 1394b bus and has detected that the polarity of the cable is inverted.
Page 437 Hardware Logic Connection Settings dialog window. S400 led This green led will light up when the line speed of the FireStealth has been set to S400 in the Data Pickup Logic Connection Settings dialog window. S800 led This green led will light up when the line speed of the FireStealth has been set to S800 in the Data Pickup Logic Connection Settings dialog window.
Page 438: General Operation
Hardware 24.4.1.4. FireStealth Rear power switch Using this switch the FireStealth can be switched on (powered) and off. When switched on the 'power led' on the front will light up. Note that the power supply needs to be connected to the FireStealth (see below) to be able to switch the FireStealth on.
Page 439 Hardware thus, no topology reconfiguration and node ID reassignments are performed. The FireStealth’s passive personality and non-intrusive behavior renders it invisible to all other devices on the IEEE 1394b bus. Also, it does not participate in any bus management activities such as root contention, cycle start generation &...
Page 440 Hardware 24.4.2.3. Configuration of the FireStealth 24.4.2.3.1 Bus Topology information Whenever configuration of the FireStealth is done before configuration of the IEEE 1394b bus, the FireStealth will be able to analyze the IEEE 1394b bus configuration and will gather the bus topology information.
Page 441 Hardware Whenever configuration of the FireStealth is done after configuration of the 1394b bus, the FireStealth will have missed the IEEE 1394b bus configuration and will not be able to gather the bus topology information. Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019...
Page 442 24.5. Third Generation Analyzers In order to support the higher speeds this new generation of 1394 bus analyzer has been completely redesigned. And the 1394 interface is entirely based on DapTechnology's Firewire IP solution FireCore™...
Page 443 · AUX connector for: · Trigger input and output functions · Recording external event (not implemented yet) · Software runs on Windows™ XP and Windows™ 7 · Configurable 1394 Behaviour like: · Configuration Rom · Cycle master Capable · IRM Capable Monitor ·...
Page 444 12 V, 10 Watt maximum (Bus Power not included) Compliance: FCC Class A Connections: PCIe External interface to host-computer 3 IEEE 1394-connectors (Beta Only) BNC-connector for external trigger-input Indicators: Green/Red LEDs for: Active, Generating, Recording, Trigger Ready Switches: Tumble switch for Power On/Off...
Page 445 Hardware IEEE1394b Connectors (3x) With these connectors the FireSpy 1600 can be connected to the IEEE1394b buses to be analyzed. All connectors are beta ports. This means that they only can be connected to a 1394b (beta) port S800 or S1600.
Page 446 With their initial releases in 2000 and 2003 the FireSpy400 and FireSpy800 have defined new standards for 1394 data analysis. Their unmatched feature set and the outstanding price/performance ratio of the FireSpys have made them the most commonly used 1394 data analyzers in the marketplace.
Page 447 Hardware · Connects to host using USB 1.1 interface · Electrical isolation between IEEE 1394 and host (USB) · 248 MByte memory for packet and data storage · Firmware field upgradeable to enable future expansions · External Trigger Input: 3V, positive edge, opto-coupled ·...
Page 448 5 V, 5 Watt maximum Compliance: FCC Class A Connections: USB1.1-connector for host-computer 2 IEEE 1394-connectors (bilingual) BNC-connector for external trigger-input Indicators: Green LEDs for: USB, Power, Ready Trigger Red LEDs for: Record, Scriptor Active Tumble switch for Power On/Off...
Page 449 Hardware 24.6.3. FireSpy 400b 24.6.3.1. FireSpy Front USB led This green led will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy 400b Rear' below) and the computer is switched on. It indicates the availability of USB bus power. power led This green led will light up when the power supply is connected to FireSpy (see 'FireSpy 400b Rear' below) and the FireSpy is switched on.
Page 450 Hardware external trigger Using this connector, the FireSpy can be triggered with an external electrical signal when recording is in progress and the Recorder is not yet triggered. The FireSpy is triggered when it detects a positive pulse of minimal 3 Volt (resulting in a current of about 1.6 mA) and a duration of typical 10 uS.
Page 451 Hardware 24.6.4. FireSpy 800 24.6.4.1. FireSpy Front USB led This green led will light up when the FireSpy is connected to the USB port of your computer (see 'FireSpy 800 Rear' below) and the computer is switched on. It indicates the availability of USB bus power. power led This green led will light up when the power supply is connected to FireSpy (see 'FireSpy 800 Rear' below) and the FireSpy is switched on.
Page 452 Hardware external trigger Using this connector, the FireSpy can be triggered with an external electrical signal when recording is in progress and the Recorder is not yet triggered. The FireSpy is triggered when it detects a positive pulse of minimal 3 Volt (resulting in a current of about 1.6 mA) and a duration of typical 10 uS.
Page 453 Hardware 24.7. Auxiliary connector ports All FireSpy devices have one or more auxiliary connector ports. The signals on these ports are: · A number of aux signals · Ground (for aux signals and Power if available) · Power (not on IDC connector) The aux signals are all open drain CMOS output with a pullup resister to 3.3 Volts.
Page 454 Hardware Pin 3 aux1 Pin 4 Ground Pin 5 aux2 Pin 6 Ground Pin 7 aux3 Pin 8 Ground Pin 9 aux4 Pin 10 Ground Pin 11 aux5 Pin 12 Ground Pin 13 aux6 Pin 14 Ground Pin 15 aux7 Pin 16 Ground Pin 17...
Page 455 Hardware 24.7.3. The VHDCI Connector The VHDCI connector is available for the FireSpy Triple Series. This connector has 6 transformer coupled IEEE1394b ports. Two for each node in the FireSpy. These Ports are A0 and A1 for the first node, B0 and B1 for the second node and C0 and C1 for the third node. This connector also holds 6 aux signals and optional power.
Page 456 Hardware Pin 44 Cable shield Pin 45 B1-TPA- Port B1 Pin 46 Not used Pin 47 B1-TPB- Port B1 Pin 48 Cable shield Pin 49 Ground Pin 50 Ground Pin 51 Aux5 CONTROL Pin 52 Aux3 CONTROL Pin 53 Aux1 CONTROL Pin 54 Cable shield...
Page 457 Hardware Pin 16 Cable shield Pin 17 TPA+ Port B1 Pin 18 TPA- Port B1 Pin 19 Cable shield Pin 20 TPA+ Port B0 Pin 21 TPA- Port B0 Pin 22 Cable shield Pin 23 VCC12 Pin 24 VCC12 Pin 25 Cable shield Pin 26 TPA+...
Page 458 Hardware This 15 pin SUBD connector has the following signals: Name (Basic & Advanced) Name (Gen 4) aux0 aux0 aux2 aux2 aux4 aux4 (IRIG1) aux5 aux5 (IRIG2) aux7 aux7 (TIM2) aux9 RS232 Receive aux10 aux10 (VS-Sync) aux11 RS232 Transmit aux1 aux1 aux3 aux3 (TIM1)

DAP Technology 1394 Operation Manual

Chapter 1. Introduction

Chapter 2. Installation

Chapter 3. Getting Started

Chapter 4. License Manager

Chapter 5. Monitor

Chapter 6. Commander

Chapter 7. Recorder

Chapter 8. Mil1394 Player

Chapter 9. Symbol Recorder

Chapter 10. Generator

Chapter 11. Scriptor

Chapter 12. Filter/Trigger

Chapter 13. Mil1394 Protocol Support

Chapter 14. Industrial / Instrumentation Digital Camera Protocol (IIDC)

Chapter 15. Audio Video / Control Protocol (AV/C)

Chapter 16. Internet Protocol Version 4 (IP4)

Chapter 17. Serial Bus Protocol (SBP)

Chapter 18. Automotive Multimedia Interface - Collaboration Protocol (AMI-C)

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for DAP Technology 1394

Summary of Contents for DAP Technology 1394