By

ISOBUS Gateway Explained: Types & How They Work

What an ISOBUS gateway is, the three main types, and how an I/O gateway bridges ISOBUS commands to relay outputs for solenoids, valves, and lights.

An ISOBUS gateway bridges the ISOBUS CAN network to something else β€” a different protocol, a set of physical outputs, or a remote diagnostic system. Here's what the main types are, how they work, and where a relay I/O module fits in.

What Is an ISOBUS Gateway?

ISOBUS (ISO 11783) is the CAN-based communication standard for agricultural machinery. Every device on the bus β€” the tractor's Virtual Terminal, the implement ECU, a relay module β€” speaks the same protocol. An ISOBUS gateway sits at the edge of that network and translates between ISOBUS and something it can't talk to natively.

That "something else" varies a lot. It could be a legacy CAN bus running a different protocol, a cellular modem sending telematics data off the machine, or a bank of physical relay outputs that need to be switched by signals from the tractor screen. The gateway concept is the same in each case: ISOBUS on one side, a different domain on the other.

The term is used loosely in the industry, so it helps to separate the main categories before choosing one.

Types of ISOBUS Gateways

TypeWhat it bridgesTypical use case
Protocol bridgeISOBUS ↔ J1939, Modbus, or proprietary CANConnecting legacy implements or non-ISOBUS controllers to the tractor bus
I/O gatewayISOBUS ↔ physical relay or digital outputsSwitching work lights, solenoid valves, section valves from the VT screen or AUX-N buttons
Diagnostic / telematics gatewayISOBUS ↔ cellular / WiFi / cloudRemote machine monitoring, GPS fleet tracking, over-the-air software updates

Each type solves a different problem. Knowing which one you need usually comes down to one question: what are you trying to connect?

Protocol Bridges

A protocol bridge translates message frames between incompatible buses. If a tractor speaks ISO 11783 but you need to control an older implement that runs J1939 or a proprietary manufacturer protocol, a bridge sits in between and re-encodes the messages so each side understands the other. These are generally specialist devices for system integrators β€” not something a typical farm operator needs to buy off the shelf.

I/O Gateways

An I/O gateway is simpler in concept: it receives ISOBUS commands from the tractor's Virtual Terminal or AUX-N inputs and uses them to switch physical outputs. The outputs are typically relays β€” electromagnetic switches that can handle real loads like solenoid valves, work lights, and hydraulic section valves.

This is the most common type a field operator will encounter, and the one most people mean when they search "ISOBUS gateway" in the context of adding outputs to a tractor.

Diagnostic and Telematics Gateways

A telematics gateway reads data from the ISOBUS network β€” engine load, PTO speed, GPS position, fault codes β€” and transmits it off the machine over cellular or WiFi. These devices are mostly fitted by OEM dealers and fleet managers. They do not control physical outputs and cannot switch relays. If you need remote monitoring and data logging, this is the category. If you need to switch a solenoid from a joystick button, it is not.

How an ISOBUS I/O Gateway Works

The signal chain from button press to switched load runs through four stages.

1. Operator input. The operator presses a soft key on the Virtual Terminal or a physical button assigned via AUX-N. Both generate the same type of message on the ISOBUS CAN bus.

2. CAN message. The tractor's VT or AUX-N input unit broadcasts the command on the CAN bus at 250 kbit/s. The message contains the function identifier β€” which output to activate and in what mode.

3. Gateway device receives and decodes. The I/O gateway listens on the CAN bus, recognises the message addressed to it, and maps it to the correct output channel.

4. Physical output switches. The relay on that channel closes (or opens), switching current to the connected load β€” a solenoid, a work light, a diverter valve coil.

The whole sequence takes milliseconds. From the operator's perspective it feels instant. The relay is doing the heavy lifting: it handles the actual load current while the ISOBUS side carries only low-power control signals.

One important distinction: the gateway controls the relay and the solenoid. It does not move oil or extend a cylinder directly. That chain β€” relay closes β†’ solenoid valve opens β†’ hydraulic oil moves β†’ cylinder extends β€” is the full picture. The product controls the first two steps.

ISOBUS Block as an I/O Gateway

ISOBUS Block is an 8-channel relay I/O gateway. It connects to your tractor's ISOBUS network, registers on the CAN bus, uploads its interface to the Virtual Terminal, and provides eight independent relay outputs you control from the tractor screen or armrest buttons.

The channel labels are CH1–CH8. Each channel is independently set to toggle (TOG) or momentary (MOM) mode from the VT screen. Toggle mode latches the relay on until the next button press β€” good for work lights. Momentary mode holds the relay active only while the button is pressed β€” useful for hydraulic valves where you want the valve to close the moment you release.

Two channels can be grouped to a single button. Press once and both fire together. That covers diverter valve applications where you want to activate a solenoid and a work light at the same time without separate assignments.

Connection to the tractor uses the standard ISOBUS connector β€” see the ISOBUS Connector Pinout Guide for pin assignments and wiring details. The module works with the in-cab ISOBUS connector (inside the cab) or the rear external ISOBUS connector (for implement-mounted installs). Power comes through the ISOBUS connection itself β€” no separate power supply wiring.

The module includes a WiFi access point for diagnostics: viewing output states, checking firmware version, and updating firmware. Button assignments and channel configuration happen through the tractor screen, not through WiFi.

8 channels. 10A per channel. 12V and 24V systems. Your outputs, your control.

When You Need a Different Gateway

ISOBUS Block switches relays. That is all it does. If your problem is different, so is the solution.

Protocol bridge needed? If you have an implement with a proprietary CAN bus that won't talk ISOBUS, you need a protocol bridge from a system integrator or specialist supplier. ISOBUS Block is not a protocol bridge β€” it does not translate message formats between incompatible buses.

Telematics or remote monitoring needed? If you need to read machine data over cellular, track GPS position, or log engine hours off-site, you need a telematics gateway. Several OEM and aftermarket suppliers offer these. ISOBUS Block's WiFi is for local diagnostics only β€” it is not a telematics device.

More than 8 outputs needed? For very large I/O counts, purpose-built ISOBUS I/O controllers from agricultural ECU manufacturers may be more appropriate. ISOBUS Block covers installs up to 8 independently switched loads.

The right tool is the one that solves the actual problem. Knowing what category of gateway you need is the first step.

Frequently Asked Questions

What is an ISOBUS gateway?

An ISOBUS gateway bridges the ISOBUS CAN network to another domain. That could be a different protocol (J1939, Modbus), a set of physical relay outputs, or a cellular/cloud connection for telematics. The category of gateway depends on what you are connecting to the ISOBUS network and why.

Is ISOBUS Block an ISOBUS gateway?

Yes β€” it is an ISOBUS I/O gateway. It receives control commands from the tractor's Virtual Terminal and AUX-N inputs over the ISOBUS CAN bus and switches 8 physical relay outputs. It is not a protocol bridge (it does not translate between incompatible bus standards) and it is not a telematics gateway (it does not transmit data off the machine).

Do I need an ISOBUS gateway for my tractor?

Only if you want to add outputs that the tractor does not already provide. ISOBUS Block is for operators who want to control additional loads β€” work lights, solenoid valves, diverter valves, section valves β€” from the tractor screen and armrest buttons. If your tractor already has enough hydraulic spools and switch outputs for everything you need, you may not need one.

How does an ISOBUS I/O gateway connect to my tractor?

Through the standard 9-pin ISOBUS connector β€” either the in-cab ISOBUS connector or the rear external ISOBUS connector. The connection carries both CAN bus signals and power. See the ISOBUS Connector Pinout Guide for pin assignments. No additional power supply wiring is needed.

Can an ISOBUS gateway control hydraulic functions?

It can switch solenoid valves that control hydraulic flow β€” but that is not the same as direct hydraulic control. The relay closes, the solenoid valve opens, hydraulic oil moves, the cylinder extends. The gateway controls the relay and the solenoid. The hydraulic hoses, pump, and cylinder are unaffected by the gateway β€” they work exactly as before. The gateway replaces the control signal, not the hydraulics.

What is the difference between an ISOBUS gateway and an ISOBUS VT?

A Virtual Terminal (VT) is the display inside the tractor cab that renders control interfaces for connected implements. It is the screen you press buttons on. An ISOBUS gateway is a device that sits on the bus and translates between ISOBUS and something else β€” physical outputs, another protocol, or a remote system. The VT is the user interface; the gateway is the bridging device. An I/O gateway like ISOBUS Block appears as a working set on the VT β€” the VT shows its interface, but the gateway itself does the switching.

What is the difference between ISOBUS and J1939?

Both are CAN-based communication standards. J1939 is a general-purpose standard originally developed for trucks and heavy vehicles. ISOBUS (ISO 11783) is derived from J1939 but adds agricultural-specific protocols β€” Virtual Terminal, Task Controller, AUX-N, and others. Agricultural tractors and implements use ISOBUS. A protocol bridge can translate between the two when legacy or cross-industry equipment is involved.

If something is not working, where do I start?

Check the CAN bus first: verify the termination resistance between CAN_H and CAN_L (should measure approximately 60Ξ© with the bus powered off), confirm the connector is seated, and make sure no address conflict exists on the bus. The ISOBUS Troubleshooting Guide covers the most common fault scenarios in detail.


Need an ISOBUS relay module for controlling solenoids, work lights, or hydraulic valves? ISOBUS Block provides 8 relay outputs controlled directly from your tractor's Virtual Terminal display. Common questions about which kit to choose and how installation works are answered on the FAQ page.

ISOBUS Gateway Explained: Types & How They Work | ISOBUS Block