Device Profile Counters report long term, low frequency counters for performance monitoring and prediction.
This is commonly used on battery powered devices.
What do the counters tell us?
Counters will allow you to monitor the performance of each device, such as voltage, GPS fix time, upload time, etc. If certain trends are seen, such as an increased Failed GPS Fixes, this allows the user to determine if certain parameters, such as GPS Settings, will need to be modified.
It can also be used for battery usage trends. For example, a failed upload uses up to 20 times the power of a successful upload. This is because a failed upload scans the bands for 3 minutes (registration timeout), while a successful upload is typically done within 5 – 10 seconds. This can be seen in photo of the counters below. The device had over 18,000 uploads with a successful upload time of slightly over 2 days while the roughly 2,700 failed uploads had the device on, attempting an upload for over 13 days.
Where are the counters found?
Device Counters can be found via:
- Device Details in OEM
- Device Logs
- Battery Management page in Telematics Guru
To view within OEM, click on details for the device you are interested in:
This will open a new window. The device counters can be found at the bottom of the details section.
Historical counter values will appear in the Device Logs
However the format is not as readable as in the Device Details Section:
DeviceProfiling[0:4694 1:9094 2:280 9:0 3:3719 4:4561 128:460 129:7087 130:5 131:2103 132:761 133:3743 134:16 135:952 136:76 137:2669 138:435 139:6 140:0 141:0 142:12893526 145:0 146:0 147:0]
HTTP Connector Settings
Device counters are sent to third party endpoints but OEM filters them out by default via HTTP connections. To send the device counters through the HTTP connector the below will need to be added to the XML of your connector.
<add key="removeCounters" value="false"/>
|0||Internal Battery Voltage||1 mV|
|1||Internal Battery||0.01 %|
|2||Estimated Battery Capacity Used||10 mAh|
|3||Maximum Temperature||0.01 C|
|4||Initial Internal Battery Voltage||1 mV|
|5||Average Successful GPS Fix Time||1 second per fix|
|6||Average Failed GPS Fix Time||1 second per failed fix|
|7||Average GPS Freshen Time||1 second per freshen attempt|
|8||Average Wakeups Per Trip||1 wakeup per trip|
|128||Successful Uploads||1 upload|
|129||Successful Upload Time||1 second|
|130||Failed Uploads||1 upload|
|131||Failed Upload Time||1 second|
|132||Successful GPS Fixes||1 fix|
|133||Successful GPS Fix Time||1 second|
|134||Failed GPS Fixes||1 fix|
|135||Failed GPS Fix Time||1 second|
|136||GPS Freshen Attempts||1 attempt|
|137||GPS Freshen Time||1 second|
|138||Accelerometer Wakeups||1 wakeup|
|140||GPS Fixes Due to 'Upload on Jostle'||1 fix|
|141||Uploads Due to 'Upload on Jostle'||1 upload|
|143||Tx Count||1 tx|
|144||Rx Count||1 rx|
|145||Successful Wi-Fi Scans||1|
|146||Failed Wi-Fi Scans||1|
|148||BLE Module Uptime||1 second|
|149||BLE Module Failures||1|