© 2021 Cypress Solutions
Complete Manual: CTM-200 R2 (Revision 1.3)
39
Reporting
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
Irregular and Infrequent reports are triggered by the below conditions, the GPS condition will typically trigger a
regular AVL type report.
Triggers or events
Description
Event Label
GPS
8 available conditions can be triggered on time, speed (low
speed, high speed), distance travelled, heading change.
GPSx
Input Condition
8 available conditions, time based, alarm based on input states
of 6 inputs, up to 2 inputs can be compared in each condition.
IP change trigger
GPIOx
Ignition
8 available conditions, triggers on ignition going off, on or
transition.
IGNx
OBDII or J1939
8 available conditions. Time based, or based on a valid OBDII or
J1939 parameter being =,>,< the reported value from the
vehicle ECU
OBDx
