Description:
This article will list all possible causes that could lead to the device consuming a high amount of data, this can result in SIMCARD blocking (by Carrier) or overcharging.
Check first
If the device is sending data to Trust Track:
Download the coordinate analysis report and check the number of records generated by each Input Trigger
If the device is sending data only to a third-party server
Create a coordinates report containing all the records received from the last few days, check the number of records generated by each IO ID.
Possible causes:
Data collection:
Low number on either of these 3 coefficients (CHECK ALL PROFILES IF PROF SWITCHING IS ENABLED)
Distance < 500m
Time with Engine < 60s
Radial < 45º
Time without Engine < 600s (CHECK ALL PROFILES IF PROF SWITCHING IS ENABLED)
Data sending:
Constant Link enabled
The device will ignore the link timeout and retain a connection to the server always open
Heartbeat enabled
The device will send a "handshake" to the server every X seconds
TCP keep-alive enabled
The device will send a new keep-alive packet periodically even if there is no data to be sent to the server.
IO events:
An IO configured with Event On: Change that is changing frequently. It does not matter if the priority is high or not. It will generate a new record every time it changes
For example, Movement Sensor configured with Event On: Change, can cause several new records to be generated and it will consume data to send all these new "unnecessary" records.
An IO configured with Hysteresis
Its Delta value is set to a normal operating voltage
Its Level value set to a low value
Its Average value set to < 1000ms
Either one of these cases can cause high number of record generation, for example. Power Supply Voltage configured like this:
Delta = 12600
Level = 1
Average = 10ms
On Both or On Rising or On Falling
If the vehicle power supply voltage when powered ON ranges between 12500 and 12700 it will generate a LOT of records
Custom Ignition configured using Power Supply Voltage with the range set to values that oscillate during normal vehicle operation.
The vehicle will be "turning ON and OFF" several times and this can cause several records to be generated
Custom Ignition configured using Movement Sensor on a device that is poorly fixed on the vehicle
A poorly fixed device will cause several false indications of movements and stoppages, therefore, generating several records.
CAN interface:
CAN mode J1939 + DTC is used with TT2 server
DTC are not supported in TT2, but device sends the data anyway, causing huge data consumption.
Recommended to switch to FMS mode.
DMP settings:
DMP connection frequency set to every 5 min or lower
This is only for 5 Gen devices.
Possible Solutions:
If none of these possible causes match and DMP connection frequency is set to 5 min or lower
You could change the connection frequency to twice a day (every 12hours), once a week (every 7 days)
In order to set a custom connection frequency you can calculate:
( qty days) * ( 24 hours) * (60 min) * (60 sec)
For example, to get the number of seconds in 7 days, the calculation would be:
7 * 24 * 60 * 60 = 604,800
You can send the SMS:
setcfg 23101 604800
Or you can create a DIFF file by changing only this parameter inside DMP settings in Advanced Configurator.