Troubleshoot your OBD Dongle
When you experience a problem with your OBD dongle you must follow those steps :
make sure that your device is correctly plugged on the car.
check if the device found any car protocols to communicate.
check that the OBD data are correctly read and decoded.
Check that the device is correctly plugged
When you plug your device on the car, the led must turn on with constant red light.
If the device have no reaction when you plug the device on your car :
please check your installation, the OBD connector can be sometimes difficult to insert, you need to be sure that the connector is firmly plugged into its base.
In case of usage of relocation cable, please proceed as the first point and if it's not successful please try to plug the device directly on the connector (if possible) or try another relocation cable.
If the device switch on its led, you can check the following table to see if the led behavior correspond to a known behavior :
Please note that device has a two-coloured LED, green and red, when both are switched on the led appear as orange.
The orange LED provides you on the GPS and Cellular status.
Device LED pictures
https://store.munic.io/documen...
If you see a led behavior that is different from the one described in the table, please send us a ticket with following informations :
IMEI of the device
description of the led behavior with estimated timing for on and off phase or a video.
Check that device communicate with car protocols
For this part we assume that the device is correctly plugged and is able to connect and send information to Cloud Connect.
If it's not the case please check the first part of this guide and the following link : What to do when my device is not communicating
In the notification that you receive on your server, you will see a field called "OBD_CONNECTED_PROTOCOL".
https://store.munic.io/documen...
Please note that it can take up to 5 minutes after the start of the car to get this value. We recommend to make a real trip of 5 to 10 minutes to check protocol availability and get some real trip data.
If this variable remains at 0, that means that the Dongle is not able to find a protocol to talk on the car. In this case please send us a ticket with the following informations :
IMEI of the device
Make, Model and Year of the car
UTC Timestamp of a recent trip
How the device is installed on the car (location, use of relocation cable, type of connector...)
Photo and schemes from your installation.
Details about the behavior of the device, specificity of the car, occurrence and reproducibility.
Recent action done on the device
Any other information that seems pertinent about the case
If you see a value different from 0 on the field that means that the device find one or several protocols to communicate with your car.
Check the presence of OBD Data
When the device start communicating with one of the protocol, some integrated OBD stack try to get default value and fill some field with them.
We have also some State Machine that make calculation based on those OBD data.
Those values are :
MDI_OBD_SPEED
MDI_OBD_RPM
MDI_OBD_VIN
MDI_OBD_FUEL_LEVEL
MDI_OBD_MILEAGE
DIO_IGNITION
...
If you don't see some change on this value or if you see some instability/reset of OBD_CONNECTED_PROTOCOL during trip, please send us a ticket with the following informations :
IMEI of the device
Make, Model and Year of the car
value of "OBD_CONNECTED_PROTOCOL"
UTC Timestamp of a recent trip
How the device is installed on the car (location, use of relocation cable, type of connector...)
Photo and schemes from your installation.
Details about the behavior of the device, specificity of the car, occurrence and reproducibility.
Recent action done on the device
OBD Data missing and available
Any other information that seems pertinent about the case
If at least some of those value change that means that all works fine, but keep in mind that depending on the car some value can be available and some other not.