J1939 guides
J1939 is the CAN protocol used in trucks, buses and off-highway machines. Learn PGNs and SPNs, decode data with a DBC, read DM1 fault codes, and understand the transport protocol and address claiming.
7 guides Read them in this order
- What Is J1939? A Simple CAN Bus Guide Learn what SAE J1939 is, where it is used, and how PGNs, SPNs, source addresses, and 29-bit CAN IDs fit together.
- What Is a PGN in J1939? PGNs and SPNs Explained Learn what a J1939 PGN is, how to extract it from a 29-bit CAN ID, and how PGNs and SPNs are used to decode heavy-vehicle data.
- Common J1939 PGNs and SPNs: engine speed, vehicle speed, temperatures, fuel, and more A practical reference for the J1939 PGNs and SPNs engineers use most, with byte positions, scaling, and offsets for engine speed, vehicle speed, coolant temperature, oil pressure, fuel rate, engine hours, and diagnostics.
- How to decode J1939 data with a DBC file (and why half your frames don't decode) J1939 DBC files store one 29-bit ID per message, but real buses send each PGN from many source addresses. Learn how J1939 DBCs work, why exact-ID decoding misses frames, and how to decode by PGN with Python and cantools.
- How to read J1939 fault codes: DM1, SPN, FMI, and lamp status explained Decode J1939 DM1 active fault messages byte by byte. Learn how lamp status, SPN, FMI, and occurrence count are packed, how multi-fault DM1 uses the transport protocol, and how to decode it in Python.
- J1939 transport protocol explained: BAM and RTS/CTS with examples How J1939 sends messages longer than 8 bytes. A walk through TP.CM and TP.DT frames, BAM broadcasts, RTS/CTS connections, the control bytes, real frame examples, and a Python reassembler.
- J1939 address claiming and the NAME field explained How J1939 ECUs get their source address. Learn the Address Claimed message (PGN 60928), the 64-bit NAME and its fields, how conflicts are resolved, and how to decode a NAME in Python or test claiming on Linux.