Data Capturing on OEM
Table of Contents
OEM is normally a conduit for device data to front end systems such as Telematics Guru. You can set up a data capture by activating the function on OEM Server before the data sent through to TG or a Third Party platform. Remember that this setting is applied to new connections. So if a device is currently connected and data capture is turned on, nothing will change. To close the connection, navigate to the Details page; and click on the Close Connection button (or restart the asset)
Data capture is useful for a few purposes:
- Digital Matter support staff can view device data to assist in debugging without needing access to an end platform
- Checking data parsing/decoding when integrating. Data being sent from the device as captured via OEM can be compared to what is received on the end platform. The actual raw data will be identical but this is useful to spot any errors with payload decoding.
3rd Party Direct Users
Helpjuice Danger Callout BodyPlease note that device logs can not be viewed on OEM server if the devices are using the third party direct/option 4 integration method.
Viewing Logs
Please see this article for details on how to view data records
To Turn on Data Capturing:
Search for your device and select the check box to the left (1):
Go to Device Operations (1); Set Data Capture Expiry (2)

Set the Data Capture Expiry Date(1) and Click on the OK button(2). The expiry date is when OEM will stop capturing data for the device.