DAP Technology 1394, Operation Manual

Page: 82 / 458

Recorder
82 Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019
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. See Filter/Trigger for more details.
In this example a Bus Reset occurred, followed by two Phy-SelfID packets. After the second SelfID packet
there is for some time no packet, resulting in the Subaction Gap and Arbitration-Reset Gap events. Then
a cycle-start packet is transmitted and again a while nothing, resulting in the Subaction Gap and
Arbitration-Reset Gap again, etc.
Note that the Subaction Gap and Arbitration-Reset Gap are only displayed when zooming in far enough,
to avoid messing up the picture too much.
For the FireSpy800 the Arbitration-Reset Gap and Cycle Start can be of type 'odd' or 'even'. The example
below displays the same situation recorded by a FireSpy800. The 'odd' and 'even' Arbitration-Reset Gaps
are indicated with the letter 'o' respectively 'e' after the 'A'.
External events can also be recorded, external events are transitions from high to low on external IO
connectors see: External Port Settings. If you want to record these events you need to check some
settings in the software; In the settings menu you need to tick the /InA, /InB and/or /InC if you have
connected hardware to any or all of these ports. Then in the FilterTrigger Settings go to the Filter Tab,
there you can see that the default action is to skip External Events. To record them they should not be
skipped and so we must uncheck the appropriate check boxes.
selecting packets
Packets can be selected by clicking with the mouse in the packet rectangle. The cursor will move to the
selected packet and the selected packet will also be selected in the other views, so that the details can be
seen. If a packet has an associated acknowledge rectangle, you also can click in the rectangle of this
acknowledge packet or in the space between the packet and the acknowledge to select the packet.
Packets and their associated acknowledges are handled as a unity in the Recorder, but not for the trigger
logic as you can see in Filter/Trigger Settings. As a result, acknowledge packets cannot be selected
separately if they belong to some packet. If an acknowledge has no associated packet (dangling
acknowledge), which is an error condition, the acknowledge packet can be selected.
If you click with the mouse on an empty space above the base line, the first packet to the right of the
clicked position will be selected and displayed.
moving cursor to specific position
If you click on the other hand below the base line, then the cursor will be moved to exactly that position.
This can be used to measure the duration of, for example, the prefix of the packet itself or the time
between a packet and its acknowledge.
7.3. Topology View
The Topology View is one of the possible views in the Recorder which you can use to investigate the
recorded data. It displays the topology corresponding to the current cursor position. For a given cursor
position, the last recorded selfIDs will be searched and the topology will be derived from these selfIDs.