Raptor-Dev-J1939-DM-Messages: Difference between revisions

From NewEagleWiki
Jump to navigation Jump to search
 
No edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[RaptorWiki|Return to the main Raptor page]]
{{DISPLAYTITLE:Raptor-Dev J1939 DM Messages}}
 
{{Navigation}} [[Raptor-Platform | Raptor Platform]] > [[Raptor-Dev | Raptor-Dev]] > [[Raptor-Dev-J1939-Library|Raptor-Dev J1939 Library]] > '''Raptor-Dev J1939 DM Messages'''
[[Raptor:J1939|Return to J1939 page]]
[[File:RaptorJ1939DMMessages.JPG|right|frame|Raptor™ J1939 DM Messages]]
 
[[File:RaptorJ1939DMMessages.JPG|right|frame|Raptor J1939 DM Messages]]
<p>The DM messages blocks implement all of the necessary J1939 diagnostic messages to create an OBD compliant system. Many of the DM messages bloks interact directly with the Raptor OBD Fault Manager to query fault information. The use of these blocks requires the Raptor OBD Fault Manager to be included in the model as well as three Custom Field Definitions for the SPN, FMI, and Occurred Count of each fault. The data types of these fields should be uint32 for SPN and uint8 for FMI and Occurred Count.</p>
<p>The DM messages blocks implement all of the necessary J1939 diagnostic messages to create an OBD compliant system. Many of the DM messages bloks interact directly with the Raptor OBD Fault Manager to query fault information. The use of these blocks requires the Raptor OBD Fault Manager to be included in the model as well as three Custom Field Definitions for the SPN, FMI, and Occurred Count of each fault. The data types of these fields should be uint32 for SPN and uint8 for FMI and Occurred Count.</p>



Latest revision as of 18:53, 24 March 2015

New Eagle > Products Wiki > Raptor Platform > Raptor-Dev > Raptor-Dev J1939 Library > Raptor-Dev J1939 DM Messages

Raptor™ J1939 DM Messages

The DM messages blocks implement all of the necessary J1939 diagnostic messages to create an OBD compliant system. Many of the DM messages bloks interact directly with the Raptor OBD Fault Manager to query fault information. The use of these blocks requires the Raptor OBD Fault Manager to be included in the model as well as three Custom Field Definitions for the SPN, FMI, and Occurred Count of each fault. The data types of these fields should be uint32 for SPN and uint8 for FMI and Occurred Count.

Blocks

Block Description Appearance
DM1

This block implements PGN 65226 Active Diagnostic Trouble Codes (DM1). This block works with the Raptor OBD Fault Manager and sends all the faults in the confirmed state. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM1 Transmit block
DM1 Transmit block
DM2

This block implements PGN 65227 Previously Active Diagnostic Trouble Codes (DM2). This block works with the Raptor OBD Fault Manager and sends all the faults in the previously active state. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM2 Transmit block
DM2 Transmit block
DM3

This block implements PGN 65228 Diagnostic Data Clear/Reset of Previously Active DTCs (DM3). This block outputs a function call when the PGN is requested. The function call should be connected to a subsystem which clears the appropriate faults.

DM3 Rx Trigger block
DM3 Rx Trigger block
DM4

This block implements PGN 65229 Freeze Frame Parameters (DM4). The input to this block is a vector of type uint8 which contains the contents of the DM4 message according to the J1939 specification.

DM4 Transmit block
DM4 Transmit block
DM5

This block implements PGN 65230 Diagnostic Readiness 1 (DM5).

DM5 Transmit block
DM5 Transmit block
DM6

This block implements PGN 65231 Pending DTCs (DM6). This block works with the Raptor OBD Fault Manager and returns all the faults in the pending state which are defined as emissions-related. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM6 Transmit block
DM6 Transmit block
DM7

This block implements PGN 58112 Command Non-Continuously Monitored Test (DM7). This block implements the base of the DM7 message. Additional blocks will be needed inside to interface to the correct code to perform the requested test. Without modification, no tests are supported and all requests will cause a NACK response. The block will indicate, based on the Test Identifier if a DM8 or DM30 response is required, based on J1939-73 5.7.7.1 (Test Identifier).

DM7 Receive block
DM7 Receive block
DM8

This block implements PGN 65232 Test Results For Non-Continuously Monitored Systems (DM8).

DM8 Transmit block
DM8 Transmit block
DM11

This block implements PGN 65235 Diagnostic Data Clear/Reset for Active DTCs (DM11). This block outputs a function call when the PGN is requested. The function call should be connected to a subsystem which clears the appropriate faults.

DM11 Rx Trigger block
DM11 Rx Trigger block
DM12

This block implements PGN 65236 Emissions-Related Active Diagnostic Trouble Codes (DM12). This block works with the Raptor OBD Fault Manager and sends all the faults in the confirmed state which are defined as emissions-related. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM12 Transmit block
DM12 Transmit block
DM19

This block implements PGN 54016 Calibration Information (DM19).

DM19 Transmit block
DM19 Transmit block
DM20

This block implements PGN 49664 Monitor Performance Ratio (DM20).

DM20 Transmit block
DM20 Transmit block
DM21

This block implements PGN 49408 Diagnostic Readiness 2 (DM21). This block uses the SPN Library for the required SPN data.

DM21 Transmit block
DM21 Transmit block
DM22

This block implements PGN 49920 Individual Clear/Reset of Active and Previously Active DTC (DM22). When a request is received this block will clear the specified fault and then trigger the User FnCall with the obdfault port set to the fault which was cleared. Any additional fault specific information that needs to be cleared or reset should be done here. After the user function has run the block will send the appropriate ACK. If the requested fault is not found or is not in the correct state, the user FnCall will not execute and the request will be appropriately NACKed.

DM22 Rx Trigger block
DM22 Rx Trigger block
DM23

This block implements PGN 64949 Previously Active Emission Related Faults (DM23). This block works with the Raptor OBD Fault Manager and sends all the faults in the previously active state which are defined as emissions-related. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM23 Transmit block
DM23 Transmit block
DM24

This block implements SPN 64950 SPN Support (DM24). This block automatically links to the DM25 block (if available) on the specified J1939 bus to determine extended freeze frame support. Block input DM30 SPNs indicates the SPNs that are supported via a DM30 response.

DM24 Transmit block
DM24 Transmit block
DM25

This block implements PGN 64951 Expanded Freeze Frame (DM25). This block works with the Raptor J1939 Extended Freeze Frame blocks to send freeze frame data.

DM25 Transmit block
DM25 Transmit block
DM26

This block implements PGN 64952 Diagnostic Readiness 3 (DM26).

DM26 Transmit block
DM26 Transmit block
DM27

This block implements PGN 64898 All Pending DTCs (DM27). This block works with the Raptor OBD Fault Manager and sends all the faults in the pending state. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM27 Transmit block
DM27 Transmit block
DM28

This block implements PGN 64896 Permanent DTCs (DM28). This block works with the Raptor OBD Fault Manager and sends all the faults in the permanent state which are defined as emissions-related. Use the raptor_j1939_spn_write block with SPNs 1213, 623, 624, 987, 3038, 3039, 3040 to set the lamp statuses.

DM28 Transmit block
DM28 Transmit block
DM29

This block implements PGN 40448 DTC Counts (DM29). This block works with the Raptor OBD Fault Manager and sends number of faults in each state.

DM29 Transmit block
DM29 Transmit block
DM30

This block implements PGN 41984 Scaled Test Results (DM30). SLOT input describes a parameters Scaling, Limits, Offset and Transfer Function, see J1939-71 Appendix A.

DM30 Transmit block
DM30 Transmit block
DM33

his block implements PGN 41216 Emission Increasing Auxiliary Emission Control Device Active Time (DM33).

DM33 Transmit block
DM33 Transmit block
DM34

This block implements PGN 40960 NTE Status (DM34).

DM34 Transmit block
DM34 Transmit block
DTC Send

This block is used by many of the DM blocks which must return a list of faults in a given state. It should not be used without fully understanding underlying mechanisms of the Raptor OBD Fault Manager.

DTC Transmit block
DTC Transmit block