Q&A - What Is SAE J1939?: (Source For The Following Answers: SAE HS-1939)
Q&A - What Is SAE J1939?: (Source For The Following Answers: SAE HS-1939)
What is a PGN?
A Parameter Group Number (PGN) is a part of the 29-bit identifier sent with every message. The PGN is a combination of the Reserved bit (always 0), the data page bit (currently only 0, 1 is reserved for future use), the PDU Format (PF) and PDU Specific (PS). PDU stands for Protocol Data Unit, and can also be read as the message format. The PF and PS are both a byte (8-bits) long. The PS is dependent on the value in the PF field. If the PF value is between 0 and 239, the PS field will contain the destination address of the node that will receive the message. If the Global Address (FF16) is used, then all nodes on the bus will receive the message. This type of message, one that can be directed to a specific ECU on the bus by sending the message to its address, is called a PDU1 message. If the PF field is between 240 and 255, then the PS field will contain a Group Extension (GE). The GE provides a larger set of values to identify messages that are broadcasted to all nodes on the network. This type of message, one that is sent to all ECUs on the bus, is called a PDU2 message. The PGN uniquely identifies the Parameter Group (PG) that is being transmitted in the message. Each PG (a grouping of specific parameters) has a definition that includes the assignment of each parameter within the 8-byte data field (size in bytes, location of LSB), and the transmission rate and priority of the message. The structure of a PGN permits a total of up to 8672 different parameter groups to be defined per page. When an ECU receives a message, it uses the PGN in the identifier to recognize the type of data that was sent in the message. For a complete listing of the PGNs assigned by the SAE committee, refer to Table C1, Suspect Parameter Numbers, in SAE J1939. For details on the data contained in each PGN, refer to SAE J193971, Vehicle Application Layer.
What is an SPN?
Each parameter used in the J1939 network is described by the standard. A Suspect Parameter Number (SPN) is a number that has been assigned by the SAE committee to a specific parameter. Each SPN has the following detailed information associated with it: data length (in bytes); data type; resolution, offset; range; and a tag (label) for reference. SPNs that share common characteristics will be grouped into a Parameter Group (PG) and will be transmitted to the network using the same PGN.
For a complete listing of the SPNs assigned by the SAE committee, refer to Table C1, Suspect Parameter Numbers, in SAE J1939. For detailed information about the SPN, refer to SAE J1939-71, Vehicle Application Layer.
What happens if my ECU has parameters that have not been assigned an SPN by the SAE Committee?
The J1939 standard has two types of messages (PGNs) that can be used by manufacturers to handle parameters or messages that are not already covered by the standard. The Proprietary A PGN (00EF0016) is a PDU1 message, and is used where the manufacture wants to direct the message to a specific destination node. How the data field of this message is used is up to each manufacturer. Alternatively, Proprietary B PGNs (00FF0016 to 00FFFF16) are PDU2 messages allowing the manufacture to define the GE fields, as they desire. The data length and how the data fields of these messages are used are up to each manufacturer. Two manufacturers may use the same GE value, and the receivers of the information would have to differentiate between the two manufactures. For more information about Proprietary A and Proprietary B messages, refer to SAE J1939-21, Data Link Layer.
how to interpret the SPN. Together, the SPN, FMI, OC and CM form a number that a diagnostic tool can use to understand the failure that is being reported. When an ECU detects a fault, it will send an Active Diagnostic Trouble Code, DM1, message. The DM1 message send by the ECU will also contain the status lamps of the module. While the fault is still present, the ECU will continue to broadcast the DM1 message to the network every second. When the fault clears, the ECU will send a final DM1 message showing that there are no further faults present. If multiple faults are present simultaneously, the ECU will send all the active faults in a single DM1 by using the Broadcast Announce Message (BAM) in a Transport Protocol session. Refer to a product's datasheet to see if it will send a DM1, and what type of DTCs it supports. An ECU on the bus may respond to the data in the DM1, or a diagnostic tool may be connected to the network to show an operator all the active faults on the network. Refer to a product's datasheet to see if and how it will respond to a DM1. There are lots of other features for diagnostics, such as retrieval of information from a log by requesting a DM2, Previously Active DTCs, which are supported by the J1939 standard. For more information about Diagnostic Messages, refer to SAE J1939-73, Diagnostics.