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 high proportion of 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 much more energy than a successful upload. This is because a failed upload will result in the device scanning for the network for longer periods of time. ( see Upload Timeouts) while a successful upload is typically done within 5 – 10 seconds. This can be seen in photo of the counters below. If there are many failed uploads, we may need to review device placement or parameters.
- The device had over 800 uploads with a successful upload time of slightly over 3 hours
- While the roughly 90 failed uploads had the device on, attempting an upload for over 5 hours!
- So the 90 failures use 5/3 more power than the other 800 combined!
- We can limit this by reviewing these settings - Upload Timeouts - Network Registration Strategy [Yabby3], and ensuring the device is placed well to get good signal. Mounting and Installation [Yabby3]
Where are the counters found?
Device Counters can be found via:
- Device Details in OEM
- Device Logs
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:
DeviceCounters. DeviceProfiling[0:5429 3:2300 4:5425 128:0 129:0 130:1 131:599 132:0 133:0 134:1 135:300 138:0 139:0 140:0 141:0 142:904]
Counters are only sent when the devices are able to commit. Counters and Device Logs are not available when devices are set to 3rd party direct mode.
HTTP Connector Settings
Device counters are sent to third party endpoints but OEM filters them out by default for 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|
|3||Maximum Temperature||0.01 C|
|4||Initial Internal Battery Voltage||1 mV|
|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|
|138||Accelerometer Wakeups||1 wakeup|
|140||GPS Fixes Due to 'Upload on Jostle'||1 fix|
|141||Uploads Due to 'Upload on Jostle'||1 upload|