Reporting
43
© 2021 Cypress Solutions
Complete Manual: CTM-200 R2 (Revision 1.4)
For example to send a “hard acceleration” event or “hard brake” event an “accelcond” would be set to define
the “trigger” points. The CTM-200 monitors the acceleration in real time and when the condition is met a
report is generated that sends the message, in this case a message containing relevant acceleration data
11.3
Infrequent Interval Reports
An Infrequent interval report is typically a report generated by an event that is infrequent. In many cases
“ignition” is considered infrequent as there can be long periods between ignition events. The idea behind
the Infrequent Interval report is that these reports typically contain information is useful but not required in
a real time environment
Examples of Infrequent reports are:
•
Odometer
•
Fuel
•
Idle
•
Engine Hours
•
Wireless Data consumed
An ignition condition “igncond” is typically used to trigger an infrequent report. The ignition condition
triggers based on the state of the ignition, OFF/ON etc.
11.4
Triggers or event conditions
•
Acceleration trigger condition
•
Data event trigger
•
Geo-route violation conditions
•
GPS trigger condition (Speed, Distance travelled, heading change, time)
•
Idle trigger condition
•
Ignition trigger condition
•
GPIO trigger condition
•
MODBUS exception condition
•
Engine diagnostics trigger condition
•
Power up trigger condition
•
Supply voltage trigger condition
