OBD Manual OEM Request Validation Instruction - Revision history

Maynard.castro at 11:38, 4 June 2026

2026-06-04T11:38:12Z

← Older revision		Revision as of 14:38, 4 June 2026
Line 97:		Line 97:
	[[File:OEM Validation.png\|left\|frameless\|478x478px]]		[[File:OEM Validation.png\|left\|frameless\|478x478px]]
	#*		#*

	~~[[Category:Manual]]~~
	~~[[Category:Commands]]~~

Maynard.castro: /* Example: Locking Total Mileage to a Correct Source */

2026-06-04T11:32:57Z

Example: Locking Total Mileage to a Correct Source

← Older revision		Revision as of 14:32, 4 June 2026
Line 94:		Line 94:
	# '''Confirm Application:''' Verify that the device replies with the success confirmation payload.		# '''Confirm Application:''' Verify that the device replies with the success confirmation payload.
	#* '''Device Response:''' <code>Manual OEM source setting performed successfully</code>		#* '''Device Response:''' <code>Manual OEM source setting performed successfully</code>
	#* '''Verify the data:''' Check from the configurator or via AVL after successful operation.[[File:OEM Validation.png\|left\|frameless\|478x478px]]		#* '''Verify the data:''' Check from the configurator or via AVL after successful operation.
			[[File:OEM Validation.png\|left\|frameless\|478x478px]]
	#*		#*

	[[Category:Manual]]		[[Category:Manual]]
	[[Category:Commands]]		[[Category:Commands]]

Maynard.castro: /* Step-by-Step Validation Example */

2026-06-04T11:32:10Z

Step-by-Step Validation Example

← Older revision		Revision as of 14:32, 4 June 2026
Line 91:		Line 91:
	# '''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 (<code>3</code>) is the correct source.		# '''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 (<code>3</code>) is the correct source.
	# '''Set and Lock the Source:''' Send the <code>set</code> command specifying DID <code>1</code> and Source Index <code>3</code>.		# '''Set and Lock the Source:''' Send the <code>set</code> command specifying DID <code>1</code> and Source Index <code>3</code>.
	# * '''Command:''' <code>obdoemdatasource:set:1:3</code>		# '''Command:''' <code>obdoemdatasource:set:1:3</code>
	# '''Confirm Application:''' Verify that the device replies with the success confirmation payload.		# '''Confirm Application:''' Verify that the device replies with the success confirmation payload.
	#* '''Device Response:''' <code>Manual OEM source setting performed successfully</code>		#* '''Device Response:''' <code>Manual OEM source setting performed successfully</code>
			#* '''Verify the data:''' Check from the configurator or via AVL after successful operation.[[File:OEM Validation.png\|left\|frameless\|478x478px]]
			#*

	[[Category:Manual]]		[[Category:Manual]]
	[[Category:Commands]]		[[Category:Commands]]

Maynard.castro: /* Step-by-Step Validation Example */

2026-06-04T11:28:51Z

Step-by-Step Validation Example

← Older revision		Revision as of 14:28, 4 June 2026
Line 84:		Line 84:
	'''Scenario:''' The received telemetry values do not match the actual mileage shown on the vehicle's dashboard.		'''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 '''86,~~666~~ km''', while the actual physical vehicle dashboard reads '''65,799 km'''.		'''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'''.

	# '''Identify Available Sources:''' Send the <code>get</code> command for the Total Mileage parameter (DID <code>1</code>).		# '''Identify Available Sources:''' Send the <code>get</code> command for the Total Mileage parameter (DID <code>1</code>).

Maynard.castro: /* Overview */ added recommended firmware version

2026-06-04T11:27:27Z

Overview: added recommended firmware version

← Older revision		Revision as of 14:27, 4 June 2026
Line 3:		Line 3:
	== Overview ==		== Overview ==
	This guide outlines the procedure for manual OEM request validation using the <code>obdoemdatasource:</code> 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).		This guide outlines the procedure for manual OEM request validation using the <code>obdoemdatasource:</code> 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).

			===== Recommended firmware version: 04.02.00.rev.602+ =====

	== When to Use ==		== When to Use ==

Maynard.castro at 11:25, 4 June 2026

2026-06-04T11:25:02Z

← Older revision		Revision as of 14:25, 4 June 2026
Line 1:		Line 1:
	__TOC__		__TOC__

	== ~~Manual OEM Request Validation Guide~~ ==		== Overview ==
			This guide outlines the procedure for manual OEM request validation using the <code>obdoemdatasource:</code> 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).
	This guide outlines the procedure for manual OEM request validation using the <code>obdoemdatasource:</code> 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 ==		== When to Use ==
	* '''Incorrect Values:''' When the received ~~values~~ do not match the actual values displayed on the vehicle's dashboard		* '''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 no OEM parameter value is received by the device.		* '''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 ==		== Command Syntax ==
	The command can be executed through ~~various~~ communication channels		The command can be executed remotely through SMS or GPRS communication channels using the structures below:

	===~~= Parameter Reference ====~~		=== Syntax Structure ===

	~~==== Available Operations (<operation>) =~~===
	{\| class="wikitable"		{\| class="wikitable"
	! Method		! Method
Line 29:		Line 26:
	\| '''GPRS'''		\| '''GPRS'''
	\| <code>obdoemdatasource:<operation>:<arg1>:[<arg2>]</code>		\| <code>obdoemdatasource:<operation>:<arg1>:[<arg2>]</code>
	\|-		\|}


	----		----
Line 36:		Line 32:
	== Parameter Reference ==		== Parameter Reference ==

	=== Available Operations (<operation>) ===		=== Available Operations (<code><operation></code>) ===
	{\| class="wikitable"		{\| class="wikitable"
	! Operation		! Operation
Line 42:		Line 38:
	\|-		\|-
	\| <code>get</code>		\| <code>get</code>
	\| Retrieves OEM sources for a specific data identifier.		\| Retrieves all available detected OEM sources for a specific data identifier.
	\|-		\|-
	\| <code>set</code>		\| <code>set</code>
	\| Sets the selected source ~~and deletes~~ all other sources for that identifier.		\| Sets and locks the selected source, ignoring or clearing all other conflicting sources for that identifier.
	\|-

	\|}		\|}

	==== Data Identifier Mapping (<arg1>) ====		=== Data Identifier Mapping (<code><arg1></code>) ===
	{\| class="wikitable"		{\| class="wikitable"
	! <code><arg1></code>		! <code><arg1></code>
Line 69:		Line 63:
	\| '''6''' \|\| OEM HVBattery Charge Level \|\| '''15''' \|\| OEM Remaining Oil Life		\| '''6''' \|\| OEM HVBattery Charge Level \|\| '''15''' \|\| OEM Remaining Oil Life
	\|-		\|-
	\| '''7''' \|\| OEM HVBattery ~~Charge State~~ \|\| '''16''' \|\| OEM HVBattery ~~Voltage~~		\| '''7''' \|\| OEM HVBattery Voltage \|\| '''16''' \|\| OEM HVBattery State of Charge
	\|-		\|-
	\| '''8''' \|\| OEM HVBattery Health \|\| '''17''' \|\| OEM HVBattery Current		\| '''8''' \|\| OEM HVBattery Health \|\| '''17''' \|\| OEM HVBattery Current
Line 78:		Line 72:
	{\| class="wikitable" style="border-left: 5px solid #00549A; background-color: #F8F9FA;"		{\| class="wikitable" style="border-left: 5px solid #00549A; background-color: #F8F9FA;"
	\|-		\|-
	\| '''Note:''' <code><arg2></code> is the numerical value representing the source for a particular identifier. You must use the <code>get</code> command first to find ~~the~~ available ~~sources~~.		\| '''Note:''' <code><arg2></code> is the numerical index value representing the specific source for a particular identifier. You must always use the <code>get</code> command first to find which source indexes are active and available.
	\|}		\|}

Line 85:		Line 79:
	== Step-by-Step Validation Example ==		== Step-by-Step Validation Example ==

	=== Example 1: Locking Total Mileage to a Correct Source ===		=== Example: Locking Total Mileage to a Correct Source ===
	'''Scenario:''' The received values do not match the actual ~~values~~ shown on the vehicle's dashboard.		'''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 '''86,666 km''', while the actual physical vehicle dashboard reads '''65,799 km'''.

	~~'''Example:''' The device is currently reporting an OEM mileage of 86,666 km, while the actual dashboard reads 56,566 km.~~		# '''Identify Available Sources:''' Send the <code>get</code> command for the Total Mileage parameter (DID <code>1</code>).
	# '''Identify Available Sources:''' ~~Use~~ the <code>get</code> command for Mileage.
	#* '''Command:''' <code>obdoemdatasource:get:1</code>		#* '''Command:''' <code>obdoemdatasource:get:1</code>
	#* '''Response:''' <code>Sources: 1. val:0 2. val:0 3. val:65799 4. val:1684300</code>		#* '''Device Response:''' <code>Sources: 1. val:0 2. val:0 3. val:65799 4. val:1684300</code>
	# '''Compare with Vehicle Dashboard:''' If the dashboard shows 65,799, the 3rd source is correct.		# '''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 (<code>3</code>) is the correct source.
	# '''Set the Source:''' <code>~~@smsrun~~:obdoemdatasource:set:1:3</code>		# '''Set and Lock the Source:''' Send the <code>set</code> command specifying DID <code>1</code> and Source Index <code>3</code>.
	# '''Confirm:''' "Manual OEM source setting performed successfully~~" will be displayed.~~		# * '''Command:''' <code>obdoemdatasource:set:1:3</code>
			# '''Confirm Application:''' Verify that the device replies with the success confirmation payload.
			#* '''Device Response:''' <code>Manual OEM source setting performed successfully</code>

			[[Category:Manual]]
			[[Category:Commands]]

Maynard.castro at 11:21, 4 June 2026

2026-06-04T11:21:20Z

← Older revision		Revision as of 14:21, 4 June 2026
Line 12:		Line 12:

	== Command Syntax ==		== Command Syntax ==
	The command can be executed through various communication channels:		The command can be executed through various communication channels

	=== Parameter Reference ===		==== Parameter Reference ====

	==== Available Operations (<operation>) ====		==== Available Operations (<operation>) ====
Line 37:		Line 37:

	=== Available Operations (<operation>) ===		=== Available Operations (<operation>) ===

	{\| class="wikitable"		{\| class="wikitable"
	! Operation		! Operation

Maynard.castro at 11:16, 4 June 2026

2026-06-04T11:16:55Z

← Older revision		Revision as of 14:16, 4 June 2026
Line 15:		Line 15:

	=== Parameter Reference ===		=== Parameter Reference ===

	==== Available Operations (<operation>) ====		==== Available Operations (<operation>) ====
	{\| class="wikitable"		{\| class="wikitable"
Line 36:		Line 37:

	=== Available Operations (<operation>) ===		=== Available Operations (<operation>) ===

	{\| class="wikitable"		{\| class="wikitable"
	! Operation		! Operation
Line 49:		Line 51:
	\|}		\|}

	=== Data Identifier Mapping (<arg1>) ===		==== Data Identifier Mapping (<arg1>) ====
	{\| class="wikitable"		{\| class="wikitable"
	! <code><arg1></code>		! <code><arg1></code>

Maynard.castro at 11:15, 4 June 2026

2026-06-04T11:15:44Z

← Older revision		Revision as of 14:15, 4 June 2026
Line 15:		Line 15:

	=== Parameter Reference ===		=== Parameter Reference ===

	==== Available Operations (<operation>) ====		==== Available Operations (<operation>) ====
	{\| class="wikitable"		{\| class="wikitable"

Maynard.castro at 11:14, 4 June 2026

2026-06-04T11:14:27Z

← Older revision		Revision as of 14:14, 4 June 2026
Line 3:		Line 3:
	== Manual OEM Request Validation Guide ==		== Manual OEM Request Validation Guide ==

	This guide outlines the procedure for manual OEM request validation using the <code>obdoemdatasource:</code> command. This process is used to manage and verify data sources when the device retrieves multiple or incorrect diagnostic values.		This guide outlines the procedure for manual OEM request validation using the <code>obdoemdatasource:</code> 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 ==		== When to Use ==
	* '''Incorrect Values:''' When ~~an OEM parameter value is wrong due to incorrect validation.~~		* '''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.		* '''No Value:''' When no OEM parameter value is received by the device.
	* '''Erratic Data:''' When a source (e.g., OEM Ignition) provides sporadic data that does not correspond to the actual vehicle state.

	----		----
Line 15:		Line 14:
	The command can be executed through various communication channels:		The command can be executed through various communication channels:

			=== Parameter Reference ===

			==== Available Operations (<operation>) ====
	{\| class="wikitable"		{\| class="wikitable"
	! Method		! Method
Line 45:		Line 47:
	\| Sets the selected source and deletes all other sources for that identifier.		\| Sets the selected source and deletes all other sources for that identifier.
	\|-		\|-
	~~\| <code>delete</code>~~
	~~\| Deletes a specific source for a particular identifier.~~
	\|}		\|}

Line 82:		Line 83:
	----		----

	== Step-by-Step Validation ~~Examples~~ ==		== Step-by-Step Validation Example ==

	=== Example 1: Locking Total Mileage to a Correct Source ===		=== 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 <code>get</code> command for Mileage.		# '''Identify Available Sources:''' Use the <code>get</code> command for Mileage.
	#* '''Command:''' <code>obdoemdatasource:get:1</code>		#* '''Command:''' <code>obdoemdatasource:get:1</code>
Line 91:		Line 95:
	# '''Set the Source:''' <code>@smsrun:obdoemdatasource:set:1:3</code>		# '''Set the Source:''' <code>@smsrun:obdoemdatasource:set:1:3</code>
	# '''Confirm:''' "Manual OEM source setting performed successfully" will be displayed.		# '''Confirm:''' "Manual OEM source setting performed successfully" will be displayed.

	~~=== Example 2: Deleting a Faulty Source (e.g., Ignition) ===~~
	~~# '''Retrieve Sources:''' Use the <code>get</code> command for Ignition.~~
	~~#* '''Command:''' <code>@smsrun:obdoemdatasource:get:18</code>~~
	~~#* '''Response:''' <code>Sources: 1. val:1</code>~~
	~~# '''Delete the Source:''' <code>@smsrun:obdoemdatasource:delete:18:1</code>~~
	~~# '''Confirm:''' "OEM source deletion performed successfully" will be displayed.~~