DAP Technology 1394, Operation Manual

Page: 255 / 458

Mil1394 Protocol support
255 Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019
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" of the recorder is also interesting to look at. The first think that you will probably notice is
that some of the packets are painted red. This is due to the fact that when running this example, the
"Generate Data CRC errors" button was pressed. As the STOF packets are painted green, it is easy to
distinguish them. In the picture below, the Packet with ID 661 is selected and the frame it belongs to is
also marked below it with a red horizontal bar.
The frames left of the selected packet donot contain a red packet. This is because the selected packet
was the first packet in a while with a frame offset smaller than the frame length. The packets before this
packet had a frame offset exceeding the frame length and could therefore not be sent.
The selected packet has a frame offset of 12.04 ms and is therefore painted almost at the right side of the
frame. When looking at the Time View from the left to the right, starting at the selected packet, it can be
seen that the frame offsets are decreasing. This is exactly what we've alread seen in the History Graph of
the Control Panel.
13.3.1.2. Details
The script source code
The picture below shows the Object Browser contents for the current example. The picture shows that the
script contains one main entry function and two regular functions. The purpose of the functions will be