Rs232, Event generation/text insertion protocol, 1 message structure – GE TRIPLEX 0150-0193C User Manual
Page 69: 2 message type, 3 event field
0150-0193C
69
Calibur DVMR
e
Triplex
7
RS232
Event Generation/Text Insertion Protocol
7.1 Message Structure
Delimiter
Class
Command
Data Length
Data
The Delimiter byte signals the start of a new message, and has a value of 0xFF.
The Class and Command fields identify the type of message.
The Data Length is a 16-bit value indicating the number of bytes in the Data portion of
the message. Data Length is sent using Intel byte ordering (Little Endian).
The Check Sum byte is the result of ORing all the bytes in the message.
Check Sum
7.2 Message Type
0xFF
0x14
0x40
Data Length[0]
Data Length[1]
Camera
Event
String[0]
String[1]
:
String[n-1]
One message is currently supported to store text along with recorded video.
CMD_ADD_TEXT
Class byte is 0x14.
Command byte is 0x40.
Data Length is the number of data bytes in the message (from 2 to 502).
Camera byte indicates the camera associated with the text. The valid range is from
0 to 15.
Event byte usage is described in the following section.
String field contains text characters. The string can be from 0 to 500 characters in
length.
Check Sum
7.3 Event Field
MSB 7
LSB 0
The two least significant bits are currently used. All
other bits should be zero.
0
0
0
0
0
0
End
Start
A – Event 0x00
If both the start and end bits are clear, the associated text will be stored with the next recorded field for
that camera. That cameras record rate will not be changed.
B – Event 0x01
If only the start bit is set, the associated text will be stored with the next recorded field for that camera.
This will cause the selected camera, as well as any pre-event fields to be recorded at the Event
Record Rate*.
C – Event 0x02
If only the end bit is set, the associated text will be stored with the next recorded field for that camera.
This will start the post-event timer** after which, the selected camera will resume recording at the
normal record rate*.