J1939¶

CAN gains a heavy-vehicle vocabulary and source-addressing discipline.

A Concrete Artifact¶

# synthetic 29-bit CAN frame interpreted as J1939
0x0CF00400  ff ff ff 68 13 ff ff ff

Synthetic offline sample for explanation; not a real operational trace or live-system instruction.

Inspection Trap¶

A 29-bit CAN identifier can look self-explanatory once a PGN appears. The trap is to treat PGN extraction as signal truth before checking PDU1/PDU2 rules, SPN authority, source-address claims, and dictionary provenance. PGN is still not signal truth.

This page inspects one synthetic extended CAN frame as J1939-shaped evidence. It teaches identifier composition, candidate PGN reasoning, source-address evidence, and the boundary between PGN/SPN dictionaries and raw bytes.

Worked Decode¶

1. 0x0CF00400 is read as a 29-bit CAN identifier in the J1939 teaching model.
2. Priority is 3, source address is 0x00, and PF = 0xF0, so the example is treated as a PDU2-style parameter group. In that case, PS = 0x04 contributes to the PGN, giving 0xF004.
3. If PF were below 0xF0, PS would be interpreted as a destination address and the PGN calculation would differ. This is the first observer trap: the same 29-bit CAN shape does not always produce a PGN by the same rule.
4. The payload bytes are transport evidence. Under a common EEC1-style teaching dictionary, bytes 68 13 at the relevant offset can be interpreted as raw 0x1368.
5. Using a scale of 0.125 rpm/bit, raw 0x1368 gives an engine-speed-like value of 621 rpm.
6. That value is a source-grounded claim only if the PGN/SPN definition, offset, byte order, scale, and not-available conventions match the captured system.
7. SA = 0x00 is source-address evidence, not a permanent identity guarantee. A real observer still needs address-claim context, platform integration knowledge, and dictionary provenance before treating that source address as a specific controller.

What The Evidence Supports¶

• The artifact supports priority, PF/PS, source-address, and PDU2 PGN extraction under the page-local J1939 model.
• The payload can support an engine-speed-like toy calculation only under the named synthetic dictionary assumptions.
• A sequence of similar frames would support cadence, source-address population, and stale/missing broadcast hypotheses.

What The Evidence Does Not Support¶

• The artifact does not prove an actual engine speed, controller identity, sensor health, or fleet-specific SPN meaning.
• It does not cover proprietary PGNs, full J1939DA signal tables, address-claim edge cases, or transport-protocol conformance.
• It does not make a generic DBC or public explainer authoritative for a specific machine.

Field Layout / Anatomy¶

Visual Model¶

Timing And Authority¶

CAN arbitration still controls bus access, but J1939 adds semantic authority through PGN/SPN definitions, source-address claims, address-claim behavior, and vendor dictionaries. A repeated PGN cadence can reveal engine running state, missing modules, or diagnostic chatter; it cannot prove that a particular physical sensor is healthy.

Bytes rarely explain themselves. Name the source that defines meaning before naming engineering values: standard metadata, label table, DBC, PGN/SPN definition, object dictionary, register map, DID catalog, LDF, ARXML, channel metadata, or vendor profile.

Failure And Ambiguity¶

• PGN extraction differs between PDU1 and PDU2; treating all identifiers alike produces wrong group numbers.
• J1939DA covers standardized PGNs/SPNs, not every proprietary or OEM-specific parameter group.
• Source addresses can be reassigned or collide during address-claim behavior.
• Not-available values and error indicators can look like high numeric values if decoded naively.
• A generic DBC may decode a fleet incorrectly when firmware, options, or proprietary PGNs differ.

Python Model¶

The current package exposes a concrete identifier example:

"""Runnable J1939 identifier example for the schoolbus binder."""

from schoolbus.protocols.j1939 import J1939Identifier

identifier = J1939Identifier(0x0CF00400)

print(identifier.show_fields())
print(identifier.explain())

It demonstrates identifier decomposition before claiming SPN-level engineering values.

The first workbook sample pack includes a passive synthetic J1939 fixture under samples/first-workbook/ that keeps PGN evidence separate from SPN and payload authority.

Source Notes¶

Source confidence: High for identifier anatomy and semantic-authority framing. Signal-level claims are intentionally limited to the synthetic artifact and require dictionary provenance in real analysis.

The 0xF004 and engine-speed-like decode are synthetic teaching choices aligned with common J1939 pedagogy. The page does not reproduce J1939DA tables, proprietary PGNs, address-claim edge cases, or transport-protocol conformance behavior.

References¶

Public Sources¶

• SAE International
• SAE J1939 Serial Control and Communications Heavy Duty Vehicle Network — Top Level Document — canonical-standard.
• CSS Electronics
• J1939 explained — vendor-tutorial.
• Linux kernel
• Linux J1939 documentation — kernel-doc.
• Tooling references
• Linux J1939 kernel documentation — Linux J1939 sockets and transport.
• python-can — CAN log inspection and offline lab context.
• can-utils — CAN capture/log-format context.
• canboat — NMEA 2000 description and decode context.

Project posture is aggregated in the protocol support policy, source policy, and project charter.