Difference between revisions of "OEM Parameters"

From Wiki Knowledge Base | Teltonika GPS
(Created page with "'''HOW TO CONFIGURE OEM PARAMETERS FOR FMX001/FMB003 ''' ==OEM parameters== Are available in the OBD Devices, *for FMB003 03.27.07.Rev.562 Firmware must be installed in orde...")
 
m (Text replacement - "Bluetooth(?!®)" to "Bluetooth®")
Tags: Mobile edit Mobile web edit
 
(17 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
'''HOW TO CONFIGURE OEM PARAMETERS FOR FMX001/FMB003 '''
+
[[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 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.
 +
 
 +
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.''
 +
 
 +
==Configuration on the Device Side ==
 +
*Move to the ''system'', and enable the '''''codec 8E''''' 
 +
::[[File:Codec.png|left]]
 +
‎</br>‎</br></br>
 +
*[[File:OBDII.png|right]] Move to ''OBDII'': </br>
 +
*# On OBD feature select '''''OBD'''''
 +
*# 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. 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''''' parameters from the ''IO'' section by choosing the needed priority
  
−
*for FMB003 03.27.07.Rev.562 Firmware must be installed in order to receive EV OEM data
 
−
*FOR FMC001 03.27.12.Rev.143 Firmware must be installed in order to receive OEM data.
 
  
−
==Configuration On the device side ==
 
−
* Move to the ''system'', and enable the '''''codec 8E''''' : [[File:System.png|right]] ‎</br>‎</br>‎</br>
 
−
* [[File:OBDII.png|right]] Move to OBDII :
 
−
*# On OBD feature select ''OBD''
 
−
*# On OBD VIN setting: Select '''''Auto''''', this will gather the VIN number from the vehicle automatically
 
−
Note: If Auto didn't work Select '''''Manual''''', and put the VIN of the Vehicle Manuale.
 
−
*Enable the required IO by selecting the low priority
 
  
 
</br>
 
</br>
−
After the device configuration, keep the device connected to the vehicle, after the FOTA configured time, the device will automatically request to download the needed file from FOTAWEB to enable the OEM parameters.
+
After configuring the device, keep the device connected to the vehicle after the FOTA configured time, the device will automatically request to download the needed files from FOTA WEB to enable the OEM parameters.
−
  Note: The device will request 1 or 2 files from the FOTAWEB
+
</br>
 +
We can speed up the process by sending a command to the device,
 +
<code><login><space><password><space>web_connect</code> </br>
 +
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.''
  
−
==Configuration via GPRES/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><username><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:
Line 35: Line 49:
 
</div>
 
</div>
  
−
'''Note''': If no username & password for SMS, two space symbols 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 ==
−
* Open your FOTA account,
+
* Open your FOTA WEB account,
−
* Search about the device IMEI
+
* Search about the device's IMEI
−
* Under ''Details'', ''OBD'' section, you should see the ''VIN number'' of your vehicle:
+
{| class="wikitable"
−
[[File:Vin num.png|Defualt]]
+
! 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 ''Tasks'', you can verify if the file is delivered to the device or not
+
|-
−
:::: [[File:Obd config file fota.png|Defualt]]
+
|[[File:Task 5.png|500px]]  || [[File:Task 4.png|500px]]
−
 
+
|-
−
If the file download is successful, kindly check your server data to confirm.
+
|}
  
 
==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==
−
Before testing, the car's ignition should be On
+
Before starting the test, the car's ignition should be On,
 
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
+
* 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.

Latest revision as of 15:27, 28 December 2023

Main Page > Frequently Asked Questions - FAQ > OEM Parameters

OEM Parameters

Are available in the OBD devices,

  • 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.

Before starting, kindly check if your vehicle is in the supported list, you can find the supported lists for OBD devices here 

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

  • Move to the system, and enable the codec 8E 
Codec.png

‎
‎

  • OBDII.png
    Move to OBDII:
    1. On OBD feature select OBD
    2. On OBD VIN setting: Select Auto, this will automatically fetch the VIN number from 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 parameters from the IO section by choosing the needed priority



After configuring the device, keep the device connected to the vehicle after the FOTA configured time, the device will automatically request to download the needed files from FOTA WEB to enable the OEM parameters.
We can speed up the process by sending a command to the device, <login><space><password><space>web_connect
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.

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
<login><space><password><space>setparam 40000:1;40005:1;40430:1;40440:1

ID:

  • 40000 – OBD Feature
  • 40005 – VIN Source
  • 40430 – OEM Total Mielge
  • 40440 – OEM Fuel

Value:

  • 1 – Enable
  • 1 – Auto
  • 1 – Enable (low)
  • 1 – Enable (low)
Note: If no login & password for SMS, two spaces should be inserted before the command.

Find all parameters list of OEM in this link

Verify the Status on FOTA

  • Open your FOTA WEB account,
  • Search about the device's 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:
Task 5.png  Task 4.png

Server Side

The following example displays only two AVL IDs for OEM parameters:

  • 389 OBD OEM total mileage
  • 390 OBD OEM fuel level

Data serve.png
Find all AVL ID list for OEM parameters here

Troubleshooting

Before starting the test, the car's ignition should be On, If you were not able to get OEM parameters using this method, you may have to check the following:

  • Device Firmware.
  • Check the device power and OBD cables in the vehicle. 
  • 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.

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=OEM_Parameters&oldid=94371"