Difference between revisions of "OBD Device Debugging"
From Wiki Knowledge Base | Teltonika GPS
BaronenasT (talk | contribs) |
BaronenasT (talk | contribs) |
||
(50 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | <span style="color:red">''Note: This page is in works!''</span> | ||
__TOC__ | __TOC__ | ||
'''Solution applies for these devices''' | '''Solution applies for these devices''' | ||
− | '''[[FMB001]]''' '''[[FMC001]]''' '''[[FMM001]]''' '''[[FMB003]]''' '''[[FMC003]]''' '''[[FMM003]]''' | + | '''[[FMB001]]''' '''[[FMC001]]''' '''[[FMM001]]''' '''[[FMB003]]''' '''[[FMC003]]''' '''[[FMM003]]''' |
+ | |||
== '''OBD Data Debugging''' == | == '''OBD Data Debugging''' == | ||
=== Device does not read listed OBD OEM parameters === | === Device does not read listed OBD OEM parameters === | ||
− | |||
==== Capturing OBD logs from FMX00X via OEM Reset ==== | ==== Capturing OBD logs from FMX00X via OEM Reset ==== | ||
− | + | === Device does not work with OBD Data in General === | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==== Capturing OBD logs from FMX00X with Filters ==== | ==== Capturing OBD logs from FMX00X with Filters ==== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== '''Basic OBD OEM Configuration''' == | == '''Basic OBD OEM Configuration''' == | ||
Line 55: | Line 19: | ||
For '''Internal Combustion Engine & HV''' ''OBD (Auto)'' must be Checked. <span style="color:blue">If it is an '''EV''', ''use Non-OBD compliant and enter VIN Source Manually</span>''. | For '''Internal Combustion Engine & HV''' ''OBD (Auto)'' must be Checked. <span style="color:blue">If it is an '''EV''', ''use Non-OBD compliant and enter VIN Source Manually</span>''. | ||
* Now it is necessary to enable OBD OEM parameters according to the vehicle list | * Now it is necessary to enable OBD OEM parameters according to the vehicle list | ||
− | [[Image: | + | [[Image:OEM_example.png|750px]] |
Let's say we have a VW Polo 2016. The list tells that '''Mileage''' (AVL ID 389), '''Fuel Level in Liters''' (AVL ID 390) and '''Fuel Level in %''' (AVL ID 48) is supported. | Let's say we have a VW Polo 2016. The list tells that '''Mileage''' (AVL ID 389), '''Fuel Level in Liters''' (AVL ID 390) and '''Fuel Level in %''' (AVL ID 48) is supported. | ||
* Enable the listed parameters | * Enable the listed parameters | ||
Line 65: | Line 29: | ||
Once the device is installed, turn on the Ignition and send SMS command '''web_connect'''. This will force the device to acquire OBD OEM File from FOTA WEB. | Once the device is installed, turn on the Ignition and send SMS command '''web_connect'''. This will force the device to acquire OBD OEM File from FOTA WEB. | ||
===Verify the Status on FOTA WEB === | ===Verify the Status on FOTA WEB === | ||
− | * Open your FOTA WEB account | + | * Open your FOTA WEB account, |
* Find device by IMEI | * Find device by IMEI | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 83: | Line 47: | ||
=== OBD Feature for EVs === | === OBD Feature for EVs === | ||
[[Image:OBD_EV_ManualVIN.png|650px]] | [[Image:OBD_EV_ManualVIN.png|650px]] | ||
− | Configuration for EVs. '''OBD Feature''' Non-OBD compliant, '''Vin Source''' (Manual) | + | Configuration for EVs. '''OBD Feature''' Non-OBD compliant, '''Vin Source''' (Manual). |
== '''Renault''' & '''Peugeot''' Specific FMB003 Information == | == '''Renault''' & '''Peugeot''' Specific FMB003 Information == | ||
If you have Renault or Peugeot vehicle and OBD OEM does not work, check if you have the latest FMB003 Hardware. | If you have Renault or Peugeot vehicle and OBD OEM does not work, check if you have the latest FMB003 Hardware. | ||
===Verify FMB003 Hardware Status on FOTA WEB === | ===Verify FMB003 Hardware Status on FOTA WEB === | ||
− | * Open your FOTA WEB account | + | * Open your FOTA WEB account, |
* Find device by IMEI | * Find device by IMEI | ||
{| class="wikitable" | {| class="wikitable" | ||
− | |||
|- | |- | ||
|[[Image:FMB003_OLDHW.png|500px]] || [[Image:FMB003_77HW.png|500px]] | |[[Image:FMB003_OLDHW.png|500px]] || [[Image:FMB003_77HW.png|500px]] | ||
|- | |- | ||
|} | |} | ||
− | With this example ''' | + | With this example '''FMB003OENJ01''' is an old hardware and '''FMB00377NJ01''' being a newer one. If Product Code contains - FMB003'''OE'' consider new Hardware. Contact your Sales Manager for more information. |
Revision as of 13:19, 20 July 2023
Note: This page is in works!
Solution applies for these devices FMB001 FMC001 FMM001 FMB003 FMC003 FMM003
OBD Data Debugging
Device does not read listed OBD OEM parameters
Capturing OBD logs from FMX00X via OEM Reset
Device does not work with OBD Data in General
Capturing OBD logs from FMX00X with Filters
Basic OBD OEM Configuration
- You need to make sure that your vehicle is supported with OBD OEM parameters. Compatibility can be checked here: OBD OEM Supported Vehicle List
- Enable Codec 8 Extended Protocol
- Configure Ignition Settings according to your vehicle.
If the vehicle is equipped with Internal Combustion Engine, it is recommended to keep Ignition Source settings with Power Voltage. Otherwise, if it is an EV/HV, set Ignition Source settings as Accelerometer.
- Check if OBD Feature is Enabled
For Internal Combustion Engine & HV OBD (Auto) must be Checked. If it is an EV, use Non-OBD compliant and enter VIN Source Manually.
- Now it is necessary to enable OBD OEM parameters according to the vehicle list
Let's say we have a VW Polo 2016. The list tells that Mileage (AVL ID 389), Fuel Level in Liters (AVL ID 390) and Fuel Level in % (AVL ID 48) is supported.
- Enable the listed parameters
Enabled Fuel Level in % (AVL ID 48) Parameter.
Enabled Mileage (AVL ID 389) and Fuel Level in Liters (AVL ID 390) Parameter.
- After enabling the parameters proceed with installation of FMX00X device into the OBDII port.
Once the device is installed, turn on the Ignition and send SMS command web_connect. This will force the device to acquire OBD OEM File from FOTA WEB.
Verify the Status on FOTA WEB
- Open your FOTA WEB account,
- Find device by IMEI
Under Details, OBD section, you should see the VIN Number of your vehicle: | Under Tasks, you can verify if the file is delivered to the device or not: |
---|---|
Lastly, check your server for the availability of OBD OEM Data.
OBD Feature
OBD Feature for Vehicles with Internal Combustion Engine
Regular configuration for vehicles with Internal Combustion engines. OBD Feature OBD (Auto), Vin Source (Auto).
If Auto VIN reading does not work, enter VIN Number manually.
OBD Feature for EVs
Configuration for EVs. OBD Feature Non-OBD compliant, Vin Source (Manual).
Renault & Peugeot Specific FMB003 Information
If you have Renault or Peugeot vehicle and OBD OEM does not work, check if you have the latest FMB003 Hardware.
Verify FMB003 Hardware Status on FOTA WEB
- Open your FOTA WEB account,
- Find device by IMEI
With this example FMB003OENJ01' is an old hardware and FMB00377NJ01 being a newer one. If Product Code contains - FMB003OE consider new Hardware. Contact your Sales Manager for more information.