J1939 is the language of heavy machinery — and any GNSS receiver feeding a machine-control system needs to speak it (directly or through a gateway). This guide explains SAE J1939 for GNSS integrators: what it is, why machine ECUs use it, and how the Septentrio-powered receivers from UAV GNSS connect to J1939 machine buses.
What is J1939?
SAE J1939 is a protocol stack built on CAN 2.0B (29-bit extended identifiers) used across heavy-duty vehicles, construction equipment and agricultural machinery. Data travels as PGNs (Parameter Group Numbers) — standardized messages for speed, position, heading, engine data and more. Machine ECUs, displays and autosteer controllers all listen to the same bus.
For GNSS, the relevant PGNs carry position (latitude/longitude), heading, speed and status. A receiver publishing these on the J1939 bus looks like a native machine component — no proprietary protocol, no extra PC in the loop.
J1939 vs ISOBUS vs CANopen
- SAE J1939 — the off-highway standard (construction, trucks, ag implements). What most machine-control OEMs ask for.
- ISOBUS (ISO 11783) — agriculture’s J1939-based variant for implements and tractors; shares the same physical layer.
- CANopen — used in industrial automation and some robotic platforms; different object dictionary, same CAN bus.
All three ride on CAN 2.0B — the physical interface is compatible, the application layer differs. That is why a receiver’s protocol support matters as much as its CAN connector.
How a GNSS receiver integrates with the J1939 bus
- Direct CAN output: the receiver has a CAN transceiver on its connector and publishes position/heading PGNs itself. Simplest installation — wire to the machine harness.
- Via a gateway: the receiver outputs NMEA/SBF over serial or Ethernet; a CAN gateway converts it to J1939 PGNs. More flexible, one extra component.
Key things to confirm before buying: the CAN protocol (J1939 PGNs vs raw CAN), the PGN mapping for position/heading, DBC file availability, and the connector type (M12, Deutsch, etc.).
Septentrio-powered options from UAV GNSS
A note on silicon: the Septentrio AsteRx-m3 Pro+ and mosaic-X5/mosaic-G5 engines provide high-speed serial, USB and Ethernet — CAN/J1939 is not native to the chip. Machine-bus output comes from the product level, and that is exactly where UAV GNSS receivers differ:
| Receiver | J1939 / machine-bus path |
|---|---|
| HB3 (IP67 box) | Direct CAN (PWR) M12 ×2 — CAN + power on the connector; serial M12 and Ethernet M12 alongside. Protocol (J1939 / CANopen / raw CAN 2.0B) configured for your application. |
| HB10 (module) | 3× UART (LVTTL, up to 4M bps) + USB — feeds a J1939 gateway on your carrier. Ideal for OEM boards. |
| HB59 (OEM board) | 3× UART + 100M Ethernet — Ethernet-to-J1939 gateway path for machine-control networks and base stations. |
All three carry AIM+ anti-jamming, dual-antenna heading (0.15° @ 1 m) and RTK accuracy of 0.6 cm + 0.5 ppm — the combination machine-control integrators need when the bus is noisy and the pass must be precise.
FAQ
Which receiver should I pick for a J1939 machine?
For direct harness wiring on a J1939 machine, the HB3 with its CAN (PWR) M12 connectors is the intended choice — confirm the exact PGN set with our engineering team. For custom OEM boards, the HB10 or HB59 with a J1939 gateway is the flexible route.
Do you provide DBC files or PGN maps?
Yes — for HB3 machine-bus output we provide the message map for your configured protocol. Contact engineering with your machine model for the exact PGNs.
Is ISOBUS supported?
ISOBUS shares the CAN physical layer with J1939. Whether the receiver publishes ISO 11783 messages depends on the protocol configuration — check with our engineering team for your implement or tractor.
Talk to a GNSS engineer about J1939 integration
Tell us your machine bus (J1939 / ISOBUS / CANopen), the ECU or display, and your accuracy target — we will specify the receiver, protocol and wiring. Request a quote →
