Burst message logger

The Burst message logger DataMode™ is used to store message data for transient events in an efficient manner. It can capture message data before and after user-defined triggering events occur. It is particularly useful in minimizing data storage consumption when video channels are used.

NOTE
When a large number of channels are selected for a DataMode, the GUI responsiveness can become sluggish. Typically with 500 channels or less, this is not overly intrusive to usability. However, if more than 500 channels are required for any given DataMode, it is recommended that users consider splitting the channels across multiple DataModes when possible; otherwise, users will need to be patient in regard to the GUI response when assigning or editing any of the DataMode parameters.

ClosedGeneric parameters

Navigate in a dialog using a mouse pointer, keyboard Tab, up-arrow or down-arrow key (not a 10-key pad up- and down-arrow key). Mouse point or Tab between insertion points or options. Use the mouse or up-arrow or down-arrow keys to scroll among options. Click the mouse, Tab or Enter to select an option.

  • Name: Each DataMode must have a unique name and contain only valid characters (invalid characters are single and double quotes, '\', '@', '#', '&', '<' and '>'). Invalid channel names are 'true' and 'false' (case sensitive).
  • Description: Optional detailed description of the DataMode.
  • Trigger mode: Select one of the following triggering options.
    •  When true: A burst record will be stored whenever the trigger channel is TRUE.
    •  On false – true edge: A burst record will be stored when the trigger channel transitions from FALSE to TRUE.
  • Trigger channel: Select the desired logical input channel for burst triggering.

Trigger time

  • Pre (secs): Specify the time period in seconds of data storage before the trigger.
  • Post (secs): Specify the time period in seconds of data storage after the trigger.

NOTE
Typically, some messages or video frames will be stored before the defined pre-trigger time and after the defined post-trigger time. The reason for this is a bit complex, but in brief, it’s much more efficient to process the message data in blocks compared to processing one message (or one video frame) at a time. The storage overhead will typically be very minimal.

  • Channel select: From the channels list, select the desired input channels for the DataMode and click the appropriate arrow. Alternatively, drag and drop the desired channels to the appropriate list.