TIMEDEVENTPULSE
Add a new camera event
|
Platform: |
OEM719, OEM729, OEM7500, OEM7600, OEM7700, OEM7720, PwrPak7, CPT7, CPT7700 |
Use this command to add a new camera event to the system. TIMEDEVENTPULSE sends a pulse on the sensor MARK output at the selected GPS time and sets the trigger on the sensor MARK input to be tagged with an event ID (see the TAGGEDMARK1PVA, TAGGEDMARK2PVA, TAGGEDMARK3PVA and TAGGEDMARK4PVA log). The lines connected to each sensor are configured using the SETUPSENSOR command.
A maximum of 10 unprocessed events can be buffered into the system. A TIMEDEVENTPULSE command must be entered at least 1 second prior to the requested event time.
The receiver will accept the TIMEDEVENTPULSE command only if the receiver time status is FINESTEERING.
Message ID: 1337
Abbreviated ASCII Syntax:
TIMEDEVENTPULSE SensorID GPSWeek GPSSeconds [Event ID]
Abbreviated ASCII Example:
TIMEDEVENTPULSE -1 1617 418838 100
|
Field |
Field Type |
ASCII Value |
Binary Value |
Description |
Binary Format |
Binary Bytes |
Binary Offset |
|
1 |
Command header |
- |
- |
TIMEDEVENTPULSE header This field contains the command name for abbreviated ASCII or the message header for ASCII (see page 1) or Binary (see page 1). |
- |
H |
0 |
|
2 |
SensorID |
ALL |
-1 |
The sensor(s) affected by the trigger command. The decimal representation of the combination of bits 0-2 can be used to select a combination of active sensors (e.g. 5 [101] will select sensors 1 and 3). |
Long |
4 |
H |
|
SENSOR1 |
0x01 |
||||||
|
SENSOR2 |
0x02 |
||||||
|
SENSOR3 |
0x04 |
||||||
|
3 |
GPSWeek |
0 - MAX Ulong |
The GPS week that triggers the event. |
Ulong |
4 |
H+4 |
|
|
4 |
GPSSeconds |
0 - 604800 |
The GPS week seconds that triggers the event. |
Double |
8 |
H+8 |
|
|
5 |
Event ID |
0- MAX Ulong |
The event's identifier, used to tag the TAGGEDMARKxPVA logs if a sensor input is enabled. Default = 0 |
Ulong |
4 |
H+16 |
|