4,745
edits
Changes
mLine 1:
Line 1: − '''HOW TO CONFIGURE OEM PARAMETERS FOR FMX001/FMB003 '''+ − − + − + + − + − + − + − + − + − + − + − + − + + + + + Line 23:
Line 27: − + − + + − + Line 44:
Line 49: − + + Line 52:
Line 58: − + − + − + + + Line 66:
Line 74: − +
Text replacement - "Bluetooth(?!®)" to "Bluetooth®"
[[Category: Frequently Asked Questions - FAQ]]
==OEM Parameters==
==OEM Parameters==
Are available in the OBD devices,
Are available in the OBD devices,
*For FMB003 03.27.07.Rev.562 Firmware must be installed in order to receive OEM data.
*For FMB003 03.27.07.Rev.562 Firmware must be installed in order to receive OEM data.
*For FMC003 03.28.03.Rev.94 Firmware must be installed in order to receive OEM data.
*For FMX001 03.27.12.Rev.143 Firmware must be installed in order to receive OEM data.
*For FMX001 03.27.12.Rev.143 Firmware must be installed in order to receive OEM data.
Before starting, kindly check if your vehicle is in the supported list, you can find the supported lists for OBD devices [[OBD_supported_vehicle_list|here]] </br>
Before starting, kindly check if your vehicle is in the supported list, you can find the supported lists for OBD devices [[OBD_supported_vehicle_list|here]] </br>
''Note: If your vehicle is not in the supported lists, it does not mean that you can not install the device - Regular OBD data will still be available.''
''Note: If your vehicle is not in the supported lists, it does not mean that you can not install the device - Regular OBD data will still be available.''
==Configuration on the Device Side ==
==Configuration on the Device Side ==
*Move to the ''system'', and enable the '''''codec 8E'''''
*Move to the ''system'', and enable the '''''codec 8E''''' :[[File:Codec.png|right]]
::[[File:Codec.png|left]]
</br></br></br>
</br></br></br>
*[[File:OBDII.png|right]] Move to ''OBDII'':
*[[File:OBDII.png|right]] Move to ''OBDII'': </br>
*# On OBD feature select '''''OBD'''''
*# On OBD feature select '''''OBD'''''
*# On OBD VIN setting: Select '''''Auto''''', this will automatically fetch the VIN number from the vehicle.
*# On OBD VIN setting: Select '''''Auto''''', this will automatically fetch the VIN number from the vehicle. </br></br>
Note: If Auto was not able to fetch the VIN number automatically from the vehicle, select '''''Manual''''', and insert the VIN number of the Vehicle.
''Note: If '''''Auto''''' was not able to fetch the VIN number automatically from the vehicle, select '''''Manual''''', and insert the VIN number of the vehicle. VIN should be 17 characters, uppercase letters, and doesn't include letters I(i), Q(q), and O(o) (to avoid confusion with numerals 1 & 0).''
*Enable the required IO by selecting the '''''low''''' priority
*Enable the required '''''IO''''' parameters from the ''IO'' section by choosing the needed priority
</br>
</br>
</br>
</br>
We can speed up the process by sending a command to the device,
We can speed up the process by sending a command to the device,
<code><login<space><password><space>web_connect</code> </br>
<code><login><space><password><space>web_connect</code> </br>
This will push the device to connect to the FOTA WEB immediately.
This will push the device to connect to the FOTA WEB immediately.
Note: The device will request 1 or 2 files from the FOTA WEB.
''Note: The device will request 1 or 2 files from the FOTA WEB.''
==Configuration via GPRS/SMS Command ==
==Configuration via GPRS/SMS Command ==
=====An example of how an OEM can enable fuel and mileage via SMS=====
Send the following command to the device via SMS </br>
Send the following command to the device via SMS </br>
<code><login><space><password><space>setparam 40000:1;40005:1;40430:1;40440:1</code>
<code><login><space><password><space>setparam 40000:1;40005:1;40430:1;40440:1</code>
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
ID:
ID:
</div>
</div>
'''Note''': If no login & password for SMS, two spaces should be inserted before the command.<br/><br/>
'''''Note''': If no login & password for SMS, two spaces should be inserted before the command.''
Find all parameters list of OEM in this [[FMB003_Parameter_list#OBD_II_.28Bluetooth®.29|link]]
==Verify the Status on FOTA ==
==Verify the Status on FOTA ==
! 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:
! 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:
|-
|-
|</br> [[File:Details 1.png]] || [[File:Task 2.png]]
|[[File:Task 5.png|500px]] || [[File:Task 4.png|500px]]
|-
|-
|}
|}
==Server Side==
==Server Side==
The AVL ID for OEM parameters are:
The following example displays only two AVL IDs for OEM parameters:
*'''389''' OBD OEM total mileage
*'''389''' OBD OEM total mileage
*'''390''' OBD OEM fuel level
*'''390''' OBD OEM fuel level
[[File:Server data.png]]
[[File:Data serve.png]]
</br>
Find all AVL ID list for OEM parameters [[FMB003_Teltonika_Data_Sending_Parameters_ID#OBD_OEM_elements|here]]
==Troubleshooting==
==Troubleshooting==
If you were not able to get OEM parameters using this method, you may have to check the following:
If you were not able to get OEM parameters using this method, you may have to check the following:
* Device Firmware.
* Device Firmware.
* Check the device power and OBD cables in the vehicle.
* Check the device power and OBD cables in the vehicle.
* Try to drive the vehicle for some time.
* Try to drive the vehicle for some time.
If the previous steps were not beneficial, then the vehicle is currently not supporting the OEM parameters and needs to perform reverse engineering.
If the previous steps were not beneficial, then the vehicle is currently not supporting the OEM parameters and needs to perform reverse engineering.
