OBD Manual OEM Request Validation Instruction
Revision as of 14:16, 4 June 2026 by Maynard.castro (talk | contribs)
Manual OEM Request Validation Guide
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 the device retrieves multiple or incorrect diagnostic values from the vehicles.
When to Use
- Incorrect Values: When the received values do not match the actual values displayed on the vehicle's dashboard
- No Value: When no OEM parameter value is received by the device.
Command Syntax
The command can be executed through various communication channels:
Parameter Reference
Available Operations (<operation>)
Parameter Reference
Available Operations (<operation>)
| 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>]
|
| Operation | Description |
|---|---|
get
|
Retrieves OEM sources for a specific data identifier. |
set
|
Sets the selected source and deletes all other 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 Charge State | 16 | OEM HVBattery Voltage |
| 8 | OEM HVBattery Health | 17 | OEM HVBattery Current |
| 9 | OEM HVBattery Temperature | 18 | OEM Ignition |
Note: <arg2> is the numerical value representing the source for a particular identifier. You must use the get command first to find the available sources.
|
Step-by-Step Validation Example
Example 1: Locking Total Mileage to a Correct Source
Scenario: The received values do not match the actual values shown on the vehicle's dashboard.
Example: The device is currently reporting an OEM mileage of 86,666 km, while the actual dashboard reads 56,566 km.
- Identify Available Sources: Use the
getcommand for Mileage.- Command:
obdoemdatasource:get:1 - Response:
Sources: 1. val:0 2. val:0 3. val:65799 4. val:1684300
- Command:
- Compare with Vehicle Dashboard: If the dashboard shows 65,799, the 3rd source is correct.
- Set the Source:
@smsrun:obdoemdatasource:set:1:3 - Confirm: "Manual OEM source setting performed successfully" will be displayed.