Template:FMX6 DM1 DM2 - Revision history

Arijus.C: Updating per GTPGTM-11768 - 3 new paragraphs added and existing ones updated or reworded

2026-04-01T04:59:12Z

Updating per GTPGTM-11768 - 3 new paragraphs added and existing ones updated or reworded

← Older revision		Revision as of 07:59, 1 April 2026
Line 5:		Line 5:
	With {{{model}}} you can read 2 types of DTC messages based on J1939 protocol:		With {{{model}}} you can read 2 types of DTC messages based on J1939 protocol:

	*DM1 – ~~Active codes~~		*DM1 – Communicates currently present faults
	*DM2 – ~~Previously Active codes~~		*DM2 – Reports stored faults

	{{{model}}} is able to read DM codes and pass them to the server in IO element. When active DM1 ~~or DM2~~ messages ~~appear~~ on CAN line ~~it is broadcasted very often –~~ {{{model}}} device ~~saves the~~ codes ~~into the~~ internal memory and ~~does not flood the server with irrelevant information –~~ only ~~new~~ DTC codes are ~~sent to the server~~.		{{{model}}} is able to read DM codes and pass them to the server in IO element. When active DM1 messages are present on the CAN line, they are broadcast frequently. The {{{model}}} device stores these codes in its internal memory and transmits only newly detected DTC codes.

			DM2 messages are not streamed, but instead, they must be requested.

	==Functionality Description==		==Functionality Description==
Line 72:		Line 74:

	'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';		'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';
	~~==Functionality Block Diagram==~~
	~~Graphic representation of '''DM1''' and '''DM2''' functionality:~~

	[[File:~~DTC Functionality blok diagram~~.png]]		==DM1/DM2 Message Structure==

			'''DM1''' is a J1939 diagnostic message used to broadcast active faults and warning lamp status. Its structure is split into a header (lamp status) followed by one or more diagnostic trouble codes. Unlike most J1939 messages, DM1 has a variable length: if there are 0–1 active DTCs, it fits in a single CAN frame, while 2 or more DTCs require a multi-frame message with additional DTC entries added.

			[[File:DM1 and DM2 Message Structure.png]]

			The first 2 bytes form the lamp status header, which is shared across all DTCs. Each lamp uses 2-bit values to indicate status (off/on), along with flash signals defining how the lamp blinks (slow or fast). These signals are interpreted collectively across ECUs, with a central controller typically deciding the final lamp behavior based on the most severe reported condition.

			Each DTC contains four key components:
			*'''SPN(''Suspect Parameter Number)''''' - Identifies the faulty subsystem.
			*'''FMI(''Failure Mode Identifier)''''' - Describes the type of failure.
			*'''CM(''SPN Conversion Method)''''' - Indicates the encoding method.
			*'''OC(''Occurrence Count)''''' - Counts how often the fault has occurred.

			These elements provide detailed, structured information about vehicle faults while supporting both standardized and proprietary diagnostics.

	==DM1 Lamp Status and Flash Signals==		==DM1 Lamp Status and Flash Signals==
Line 110:		Line 124:
	The SPNs for proprietary codes typically occupy the high end of the 19-bit field, ranging from '''516,096 to 524,287'''. FMI values may be standard or custom, but the meaning of the SPN is defined by the manufacturer. Accurate interpretation requires access to OEM documentation, as these codes are not universally defined or interpretable.		The SPNs for proprietary codes typically occupy the high end of the 19-bit field, ranging from '''516,096 to 524,287'''. FMI values may be standard or custom, but the meaning of the SPN is defined by the manufacturer. Accurate interpretation requires access to OEM documentation, as these codes are not universally defined or interpretable.

	==DM1/DM2 ~~Message Structure==~~		==Functionality Block Diagram==
			Graphic representation of '''DM1''' and '''DM2''' functionality:

	'''DM1''' is a J1939 diagnostic message used to broadcast active faults and warning lamp status. Its structure is split into a header (lamp status) followed by one or more diagnostic trouble codes. Unlike most J1939 messages, DM1 has a variable length: if there are 0–1 active DTCs, it fits in a single CAN frame, while 2 or more DTCs require a multi-frame message with additional DTC entries added.		[[File:DTC Functionality blok diagram.png]]

	[[File:~~DM1 and DM2 Message Structure~~.png]]

	The first 2 bytes form the lamp status header, which is shared across all DTCs. Each lamp uses 2-bit values to indicate status (off/on), along with flash signals defining how the lamp blinks (slow or fast). These signals are interpreted collectively across ECUs, with a central controller typically deciding the final lamp behavior based on the most severe reported condition.

	~~Each DTC contains four key components:~~
	*'''SPN(''Suspect Parameter Number)''''' - Identifies the faulty subsystem.
	*'''FMI(''Failure Mode Identifier)''''' - Describes the type of failure.
	*'''CM(''SPN Conversion Method)''''' - Indicates the encoding method.
	*'''OC(''Occurrence Count)''''' - Counts how often the fault has occurred.

	~~These elements provide detailed, structured information about vehicle faults while supporting both standardized and proprietary diagnostics.~~

Arijus.C: Updating per GTPGTM-11768

2026-03-31T12:05:39Z

Updating per GTPGTM-11768

← Older revision		Revision as of 15:05, 31 March 2026
Line 76:		Line 76:

	[[File:DTC Functionality blok diagram.png]]		[[File:DTC Functionality blok diagram.png]]

			==DM1 Lamp Status and Flash Signals==

			The '''DM1 (Diagnostic Message 1)''' in the '''J1939''' protocol reports active '''Diagnostic Trouble Codes (DTCs)''' and controls vehicle warning indicators. It defines the behavior of the '''Malfunction Indicator Lamp (MIL)''' and other warning lamps, which can be off, on solid, or flashing, depending on the severity and priority of detected faults. Flashing typically signals a more urgent or severe condition, while a solid light indicates an active but less critical issue.

			The first byte represents the status of four indicator lamps:

			*'''PL (Protect Lamp)''' - DTC's indicate non-electronic subsystem issue.
			*'''AWL(Amber Warning Light)''' - DTC's indicate a non-critical issue that does not warrant stopping the vehicle.

			*'''RSL(Red Stop Lamp)''' - DTC's indicate a critical issue that warrants stopping the vehicle immediately.

			*'''MIL(Malfunction Indicator Lamp)''' - At least one DTC indicates emissions related issue.

			Each lamp is encoded using 2 bits, allowing four possible states: '''off, on, slow flash, and fast flash'''. This compact encoding means all lamp states are conveyed within a single byte, with each pair of bits mapped to a specific lamp in a fixed order. These lamp states directly inform the operator about the severity and urgency of active faults.

			DM1 encodes warning lamp information in its first 2 bytes, combining both lamp status and flash behavior. Each lamp is represented by two 2-bit fields—one in byte 1 (status) and one in byte 2 (flash).

			To decode, split each byte into 2-bit segments and map each pair to its corresponding lamp. The final behavior is determined by combining status and flash (e.g., ON + fast flash = rapidly blinking warning).

			==Global and Manufacturer SPN Codes==

			===Global-Level SPN codes===

			Standard codes are defined by the SAE J1939 standards and are recognized across all compliant vehicles and equipment. The SPNs for these codes fall within the range of '''1 to 24,324''' representing widely used parameters such as engine speed, coolant temperature, or oil pressure. FMI values are standardized, describing specific failure patterns such as high voltage, circuit open, or out-of-range conditions.

			Because they are standardized, these codes are universally interpretable by any compliant diagnostic tool without requiring manufacturer-specific references.

			===Manufacturer-Level SPN codes===

			Manufacturer-level or proprietary codes are reserved for OEM-specific faults that are not defined in the J1939 standard. These allow manufacturers to monitor unique components, systems, or operational conditions that are specific to their equipment.

			The SPNs for proprietary codes typically occupy the high end of the 19-bit field, ranging from '''516,096 to 524,287'''. FMI values may be standard or custom, but the meaning of the SPN is defined by the manufacturer. Accurate interpretation requires access to OEM documentation, as these codes are not universally defined or interpretable.

			==DM1/DM2 Message Structure==

			'''DM1''' is a J1939 diagnostic message used to broadcast active faults and warning lamp status. Its structure is split into a header (lamp status) followed by one or more diagnostic trouble codes. Unlike most J1939 messages, DM1 has a variable length: if there are 0–1 active DTCs, it fits in a single CAN frame, while 2 or more DTCs require a multi-frame message with additional DTC entries added.

			[[File:DM1 and DM2 Message Structure.png]]

			The first 2 bytes form the lamp status header, which is shared across all DTCs. Each lamp uses 2-bit values to indicate status (off/on), along with flash signals defining how the lamp blinks (slow or fast). These signals are interpreted collectively across ECUs, with a central controller typically deciding the final lamp behavior based on the most severe reported condition.

			Each DTC contains four key components:
			*'''SPN(''Suspect Parameter Number)''''' - Identifies the faulty subsystem.
			*'''FMI(''Failure Mode Identifier)''''' - Describes the type of failure.
			*'''CM(''SPN Conversion Method)''''' - Indicates the encoding method.
			*'''OC(''Occurrence Count)''''' - Counts how often the fault has occurred.

			These elements provide detailed, structured information about vehicle faults while supporting both standardized and proprietary diagnostics.

Arijus.C at 08:18, 12 December 2025

2025-12-12T08:18:33Z

← Older revision		Revision as of 11:18, 12 December 2025
Line 72:		Line 72:

	'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';		'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';
			==Functionality Block Diagram==
			Graphic representation of '''DM1''' and '''DM2''' functionality:

			[[File:DTC Functionality blok diagram.png]]

Arijus.C at 07:34, 11 December 2025

2025-12-11T07:34:50Z

← Older revision		Revision as of 10:34, 11 December 2025
Line 1:		Line 1:
	==Introduction==		==Introduction==

	With professional device lineup, telltale information (dashboard ~~lights~~) can be read remotely ~~indicating various~~ issues ~~with heavy duty vehicles~~. New feature of Diagnostic Trouble Code (DTC) reading will help to narrow down the specific faults happening in vehicles.		With a professional device lineup, telltale information (dashboard indicators) from heavy-duty vehicles can be read remotely to identify a variety of issues. New feature of Diagnostic Trouble Code (DTC) reading will help to narrow down the specific faults happening in vehicles.

	With {{{model}}} you can read 2 types of DTC messages based on J1939 protocol:		With {{{model}}} you can read 2 types of DTC messages based on J1939 protocol:

Line 10:		Line 11:

	==Functionality Description==		==Functionality Description==

			This functionality is available from Firmware version '''03.01.02.rev.06''' or higher.

	For proper functionality, the device requires ignition to be active. Source of ignition and voltage level can be selected from '''System''' tab.		For proper functionality, the device requires ignition to be active. Source of ignition and voltage level can be selected from '''System''' tab.
Line 34:		Line 37:
	„DTC DM1“ and “DTC DM2“ shows the last DTC that has been detected. „Active DM1 List“ and „Active DM2 List“ provides a list of all active DTCs for a given source.		„DTC DM1“ and “DTC DM2“ shows the last DTC that has been detected. „Active DM1 List“ and „Active DM2 List“ provides a list of all active DTCs for a given source.

	Example of generating DM1 / DM2 list: To register DM1 code, ~~there~~ is ~~a need~~ to send command using ( pgn 0xFEFA ). Device will first check if such DTC code exist in the system (MCUID and CAN Source has to be unique for each DTC). Otherwise, DTC will be rejected.		Example of generating DM1 / DM2 list: To register DM1 code, it is required to send a command using (pgn 0xFEFA). Device will first check if such DTC code exist in the system (MCUID and CAN Source has to be unique for each DTC). Otherwise, DTC will be rejected.

	[[File:DTC Configurator outputs.png]]		[[File:DTC Configurator outputs.png]]
Line 52:		Line 55:
	[[File:DTC Terminal logs.png]]		[[File:DTC Terminal logs.png]]

	To remove one of the DTC from DM1 list, DM2 code ( pgn 0xFEFB ) is required. Device will check if the sent DTC code exists in the system (MCUID and CAN Source has to be unique for each DTC). If sent DTC does not exist in the system, it will be rejected.		To remove one of the DTC from DM1 list, DM2 code (pgn 0xFEFB) is required. Device will check if the sent DTC code exists in the system (MCUID and CAN Source has to be unique for each DTC). If sent DTC does not exist in the system, it will be rejected.

	Based on previous example, sending DTC 9D000301 with MCUID 01 on CAN2, device remove this DTC from the system, as the result, this DTC is removed from „Active DM1 List“ and added to the „Active DM2 List“.		Based on previous example, sending DTC 9D000301 with MCUID 01 on CAN2, device remove this DTC from the system, as the result, this DTC is removed from „Active DM1 List“ and added to the „Active DM2 List“.

Arijus.C at 05:21, 11 December 2025

2025-12-11T05:21:57Z

← Older revision		Revision as of 08:21, 11 December 2025
Line 69:		Line 69:

	'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';		'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';

	~~==Functionality Diagram==~~

Arijus.C at 13:48, 10 December 2025

2025-12-10T13:48:55Z

← Older revision		Revision as of 16:48, 10 December 2025
Line 1:		Line 1:
			==Introduction==

			With professional device lineup, telltale information (dashboard lights) can be read remotely indicating various issues with heavy duty vehicles. New feature of Diagnostic Trouble Code (DTC) reading will help to narrow down the specific faults happening in vehicles.
			With {{{model}}} you can read 2 types of DTC messages based on J1939 protocol:

			*DM1 – Active codes
			*DM2 – Previously Active codes

			{{{model}}} is able to read DM codes and pass them to the server in IO element. When active DM1 or DM2 messages appear on CAN line it is broadcasted very often – {{{model}}} device saves the codes into the internal memory and does not flood the server with irrelevant information – only new DTC codes are sent to the server.

	==Functionality Description==		==Functionality Description==

Arijus.C at 13:42, 10 December 2025

2025-12-10T13:42:26Z

Show changes

Arnas Šaduika at 06:06, 8 September 2023

2023-09-08T06:06:36Z

Arnas Šaduika at 06:05, 8 September 2023

2023-09-08T06:05:07Z

@@ Line 16: / Line 16: @@
 ! style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |Max
 |-
 |}

Arnas Šaduika at 06:00, 8 September 2023

2023-09-08T06:00:48Z

← Older revision		Revision as of 09:00, 8 September 2023
Line 12:		Line 12:
	! rowspan="2" style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" \|HW Support		! rowspan="2" style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" \|HW Support
	! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" \|Parameter Group		! rowspan="2" style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" \|Parameter Group
			\|-
			! style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" \|Min
			! style="width:5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" \|Max
	\|-		\|-
	\|}		\|}

← Older revision		Revision as of 09:06, 8 September 2023
Line 24:		Line 24:
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: ~~left~~;" \|DTC DM1		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|DTC DM1
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements
Line 37:		Line 37:
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| s		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| s
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: ~~left~~;" \|DTC Time DM1		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|DTC Time DM1
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements
Line 49:		Line 49:
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: ~~left~~;" \|DTC DM2		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|DTC DM2
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements
Line 61:		Line 61:
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| -
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| s		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \| s
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: ~~left~~;" \|DTC Time DM2		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|DTC Time DM2
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|[[FMB640]]
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" \|FMS elements
	\|}		\|}