Extract engine RPM from a heavy-duty truck's J1939 CAN bus by decoding SPN 190 out of the PGN 61444 (EEC1) broadcast frame
domain: csselectronics.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Capture the 29-bit extended CAN ID and confirm it maps to PGN 0xF004 (61444, EEC1) by masking out priority and source address bits
Locate SPN 190 (Engine Speed) at data bytes 4-5 of the 8-byte payload
Reverse the two bytes from Intel (little-endian) order before converting to decimal
Apply the SPN 190 scale factor of 0.125 rpm/bit with zero offset to get the physical RPM value
Treat special byte values (0xFF = not available, 0xFE = error) per the J1939 Digital Annex as invalid before trusting the reading
Known gotchas
EEC1 is a PDU2 (broadcast) PGN, so use the PDU2 mask (0x3FFFF00) not the PDU1 mask (0x3FF0000) when identifying the PGN, or identification will be wrong
Byte value 0xFF signals 'not available' and 0xFE signals 'error' per J1939-71 — filter these before scaling, don't treat them as valid data
The J1939 Digital Annex is the authoritative, continuously revised source for SPN scale/offset/position; a hardcoded mapping can go stale as OEMs add proprietary variants
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?