High-Speed ISOBUS: farm machinery moves beyond 250 kb/s CAN toward switched gigabit Ethernet

The interesting thing about High-Speed ISOBUS is not the speed. Farm machinery has run on a narrow, robust CAN bus for decades, and the AEF programme that is moving the standard toward switched gigabit Ethernet matters because the change in topology is a change in what a machine network can do and where it can be attacked. HSI 1.0 maturity is targeted for 2028, which gives an operator time to ask the right questions before the first units reach the farm.

What changes on the network

A shared CAN bus gives a controller few direct network paths, and a machine near the old 250 kb/s ceiling cannot move the payloads modern implements generate. Gigabit Ethernet changes that. A 1 Gb/s backbone is roughly 4,000 times the CAN rate, which is what high-rate sensor data, camera streams and firmware updates need (AEF High-Speed ISOBUS project; AEF on HSI 1.0). The legitimate upside is real, and it arrives with a second change that is easier to miss. On an Ethernet-based stack each node is addressable, and a diagnostic service becomes reachable from the network. No evidence in the cited AEF material identifies a specific vulnerability, and none is claimed here; the architecture shift changes the security surface independently of any single vulnerability. Risk materialises under familiar conditions: a reachable gateway, an unauthenticated remote diagnostic session, or a web path running from a telematics device to a controller.

The announced stack

The HSI stack chooses 1000BASE-T1, a 1 Gbit/s Ethernet link over a single twisted pair, as the physical layer, roughly 4,000 times the CAN rate and with a target of about 10 ms command and control timing. On top of that sit the Tractor Implement Management (TIM) layer, the Task Controller and diagnostics. The service-oriented layer is unresolved: SOME/IP and OPC UA remain under evaluation. The AEF runs an HSI Discovery Station at Plugfests as a proof of concept, with a little over a dozen companies participating and learning material ahead of wider adoption. The stack is therefore not finalised; use 2028 as the earliest product horizon, not a shipping date.

What maturity means in practice

A farmer should not expect HSI 1.0 overnight in every dealership: 2028 is the earliest date by which the standard's documents are expected to be mature enough that companies could realistically create and deliver product, not the date every manufacturer ships a first serial unit. The planning that matters happens before that date: what a service department can diagnose, who can reach the machine's network, and how a remote session is closed.

The South African angle

South African operators will meet High-Speed ISOBUS through the same channel as current machinery: imported equipment from manufacturers that adhere to the AEF standard. The reviewed AEF and industry material identifies no High-Speed ISOBUS-equipped machine operating in South Africa, and none is claimed here. When the first units arrive through import channels, the local gap will be service preparation: technician training for Ethernet diagnostics, access to the machine's network ports, and a clear remote path for a diagnostics tool. Those are questions to put to the dealer.

Questions to put to a supplier

Before the first HSI-compliant units reach the farm, ask how remote diagnostic sessions are authenticated. Ask whether the telematics gateway is a separate security-filtering device or sits on the same network as the engine controller. Ask whether firmware images are signed, by whom, and what happens to remote access after a service session ends. None of this implies a known failure in HSI; these are the operational questions any networked agricultural machine raises. Once an Ethernet bus is present, the boundary between office telematics components and implement controllers becomes a network configuration, not a physical one.

What to watch

Two decisions will show whether the standard answers the security question. The first is which of SOME/IP and OPC UA becomes the service layer. The second is whether the HSI 1.0 text specifies signed firmware, authenticated gateways and a separated security domain. An operator should verify that a dealer can name who opens a remote diagnostic session on an HSI machine, whether that path crosses the same network as the engine controller, and how the session is terminated. If a dealer cannot answer those three questions, the machine's network is being sold faster than its service model is being prepared.