ISO FastLane: Faster ISO 11783 with Dual Stack Approach as a Short Term Solution

The agricultural industry has been searching for a high-speed successor to the 250kbit/s CAN bus backbone of ISO11783 (ISOBUS) for over a decade, yet no protocol-level solution has reached standardization. Meanwhile, modern planters, sprayers, and Virtual Terminals are already constrained by the bus bandwidth. This paper presents ISO FastLane, a gateway-less dual-stack approach that routes point-to-point ISOBUS traffic over Ethernet while keeping broadcast messages on the existing CAN bus. The solution requires no new state machines, no middleware, and no changes to application layer code: only a simple Layer3 routing decision and a lightweight peer discovery mechanism called Augmented Address Claim (AACL). Legacy devices continue to operate unmodified and unaware of FastLane traffic. Preliminary tests reported on the paper demonstrate that ISO FastLane accelerates Virtual Terminal object pool uploads by factor of 8 and sustains Task Controller message rates over 100 times beyond the current specification limit. Because ISO FastLane builds entirely on existing J1939 and ISO11783 conventions, it can be implemented by ISOBUS engineers in a matter of weeks. This is delivering tangible performance gains today, without waiting for the long-term High Speed ISOBUS solution.

💡 Research Summary

The paper addresses the growing bandwidth bottleneck of the 250 kbit/s CAN‑based ISO 11783 (ISOBUS) backbone that has limited modern agricultural equipment such as planters, sprayers and virtual terminals. While a long‑term high‑speed ISOBUS (HS‑ISOBUS) solution is still under standardisation, the authors propose a short‑term, low‑cost “ISO FastLane” that runs a dual‑stack network: the traditional CAN bus remains the primary channel for broadcast traffic, and a secondary Ethernet (HSI) channel is used for all point‑to‑point communication.

The key technical contribution is the Augmented Address Claim (AACL) mechanism. It extends the existing J1939 address‑claim process on CAN with a new PGN (19200) that carries the ECU’s Ethernet IP address (IPv4 or IPv6) and UDP port. This information is exchanged using the J1939 Transport Protocol, allowing any ECU that supports Ethernet to learn the IP endpoint of its peers without any changes to the higher‑layer application protocols.

With AACL in place, the system operates as follows:

1. All broadcast messages (PDU Type 2 and global‑address PDU Type 1) continue to be transmitted on the CAN bus exactly as today, preserving the deterministic timing of vehicle‑speed, engine‑speed, hitch‑position and other safety‑critical signals.
2. When a client and a server both detect that each other have a valid Ethernet endpoint, they switch the entire point‑to‑point session (VT2ECU/ECU2VT, PD, FS, etc.) to UDP unicast (or TCP) over Ethernet. This removes the 8‑byte CAN frame limitation for those sessions and enables orders of magnitude higher message rates.

The authors report experimental results showing an eight‑fold speedup for Virtual Terminal object‑pool uploads and more than a hundred‑fold increase in Task Controller message rates, effectively moving from the ISO 11783‑specified average of 10 messages / s to well over 100 messages / s on the Ethernet side. File transfers and extended transport protocol (ETP) payloads also benefit from the higher throughput.

FastLane is deliberately “gateway‑less”. No dedicated bridge or state‑machine is required between the two media; the only added software components are a lightweight router that decides, based on the AACL table, whether a given message should be sent on CAN or Ethernet, and the AACL parser itself. Consequently, existing ISO 11783 stacks can be extended with a few weeks of engineering effort, and legacy ECUs that lack Ethernet simply ignore the AACL messages and continue to operate on CAN unchanged.

The paper also discusses practical constraints. The AACL payload (up to 128 bits for an IPv6 address plus a port and a flag) consumes CAN bandwidth, especially during initial discovery, but this overhead is modest compared to the gains. Ethernet traffic introduces the need for proper network management (VLANs, QoS, broadcast storm control) in field environments, and security is not inherent in the raw IP transport; the authors suggest optional MACsec or IPsec layers for authentication and encryption.

In the broader context, FastLane is positioned as a bridge between the current CAN‑only ISOBUS and the future HS‑ISOBUS. It satisfies the short‑term requirements of simplicity, backward compatibility, and rapid market entry, while still adhering to J1939/ISO 11783 conventions. The approach allows manufacturers to roll out high‑speed features on existing hardware platforms, deferring the costly redesign that a full HS‑ISOBUS rollout would entail.

Overall, ISO FastLane offers a pragmatic, standards‑based pathway to dramatically increase data rates on agricultural machines today, without waiting for the finalisation of a long‑term high‑speed ISOBUS specification.