This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
event_filter [2016/03/16 15:31] pereira |
event_filter [2016/03/16 15:36] pereira [S800 data format from Event Filter (S800 Filter)] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== S800 data format from Event Filter (S800 Filter) ====== | ====== S800 data format from Event Filter (S800 Filter) ====== | ||
+ | This page describes the data format assembled by the S800 filter. The data is written in a series of 16-bit unsigned integers, subsequently referred to as '' | ||
+ | |||
+ | ===== General packet structure ===== | ||
+ | All data is written using the concept of " | ||
+ | |||
+ | ^ Length ^ Packet Tag ^ Packet Data | | ||
+ | |||
+ | Length: a count of the number of words in the packet, inclusive of the length word itself | ||
+ | |||
+ | Packet Tag: a predefined integer indicating the type of data found in the Packet Data | ||
+ | |||
+ | Packet Data: the data themselves. These can be data read from the modules or a sub packet. Sub packets have identical structure to main packets. Using this format all data can be placed in nested packets, and coding decisions on how to unpack the Packet Data can be made by examination of the preceding Packet Tag. Packets (including sub packets) can also be skipped by jumping ahead Length words in the buffer. | ||
+ | |||
- | The trigger bits words indicates which bits were set during the event. The encoding of the bits is the following: | ||
In this section, each 16-bit word sent by the Filter is described by a 16x3-table diagram. The first row includes the value, either in decimal or hexadecimal format, or a descriptive note. The second row shows the value in binary (" | In this section, each 16-bit word sent by the Filter is described by a 16x3-table diagram. The first row includes the value, either in decimal or hexadecimal format, or a descriptive note. The second row shows the value in binary (" | ||
+ | |||