OBD Manual OEM Request Validation Instruction

Overview

This guide outlines the procedure for manual OEM request validation using the obdoemdatasource: command. This process is used to manage and verify data sources when a Teltonika device retrieves multiple or incorrect diagnostic values from a vehicle's Electronic Control Units (ECUs).

When to Use

• Incorrect Values: When the parsed values received on the server do not match the actual values displayed on the vehicle's dashboard/instrument cluster.
• No Value: When a specific OEM parameter value is supported by the vehicle but is not being received or captured by the device.

---

Command Syntax

The command can be executed remotely through SMS or GPRS communication channels using the structures below:

Syntax Structure

Method	Syntax
SMS (With Login)	<login><space><password><space>obdoemdatasource:<operation>:<arg1>:[<arg2>]
SMS (No Login)	<space><space>obdoemdatasource:<operation>:<arg1>:[<arg2>]
GPRS	obdoemdatasource:<operation>:<arg1>:[<arg2>]

---

Parameter Reference

Available Operations (<operation>)

Operation	Description
get	Retrieves all available detected OEM sources for a specific data identifier.
set	Sets and locks the selected source, ignoring or clearing all other conflicting sources for that identifier.

Data Identifier Mapping (<arg1>)

<arg1>	OEM Data Identifier (DID)	<arg1>	OEM Data Identifier (DID)
1	OEM Total Mileage	10	OEM HVBattery Max Energy
2	OEM Fuel level1 (l)	11	OEM HVBattery Available Energy
3	OEM Distance Till Next Service	12	OEM HVBattery Lifetime Charge
4	OEM Remaining Distance	13	OEM HVBattery Lifetime Energy
5	OEM Fuel level2 (l)	14	OEM Ambient Temperature
6	OEM HVBattery Charge Level	15	OEM Remaining Oil Life
7	OEM HVBattery Voltage	16	OEM HVBattery State of Charge
8	OEM HVBattery Health	17	OEM HVBattery Current
9	OEM HVBattery Temperature	18	OEM Ignition

Note: <arg2> is the numerical index value representing the specific source for a particular identifier. You must always use the get command first to find which source indexes are active and available.

---

Step-by-Step Validation Example

Example: Locking Total Mileage to a Correct Source

Scenario: The received telemetry values do not match the actual mileage shown on the vehicle's dashboard.

Example Context: The device is currently reporting an incorrect OEM mileage of 168,4300 km, while the actual physical vehicle dashboard reads 65,799 km.

1. Identify Available Sources: Send the get command for the Total Mileage parameter (DID 1).
   • Command: obdoemdatasource:get:1
   • Device Response: Sources: 1. val:0 2. val:0 3. val:65799 4. val:1684300
2. Compare with Vehicle Dashboard: Match the values from the response to the physical dashboard. Since the dashboard shows 65,799 km, the 3rd source index (3) is the correct source.
3. Set and Lock the Source: Send the set command specifying DID 1 and Source Index 3.
4. * Command: obdoemdatasource:set:1:3
5. Confirm Application: Verify that the device replies with the success confirmation payload.
   • Device Response: Manual OEM source setting performed successfully