An ISOBUS gateway bridges the ISOBUS CAN network to something outside it: a different bus protocol, a cellular link, or a set of physical outputs. The word gets used loosely, which makes it hard to know what you are shopping for. Here is what an ISOBUS gateway actually does, the categories you will meet in the ISOBUS solutions market, and where a relay module like ISOBUS Block fits.
What an ISOBUS gateway actually is
ISOBUS (ISO 11783) is the CAN-based communication standard for agricultural machinery. Every device on the bus, whether it is the tractor's Virtual Terminal, an implement ECU, or a relay module, speaks the same protocol. A gateway sits at the edge of that network and either translates ISOBUS messages into a different format, or forwards data from the bus onto a link that is not CAN at all.
Two things follow from that definition. First, a gateway is a bridge between networks, not a control device you press buttons on. Second, whether a specific product is really a gateway depends on what it connects the ISOBUS bus to. Farmers use the word for anything that "sits between the tractor and something else," which is where the confusion starts.
ISOBUS solutions: where a gateway fits
If you search for ISOBUS solutions or terminals and ISOBUS solutions you get a mix of terminals, implement ECUs, gateways, and Task Controller software. They are related but do different jobs.
| Layer | What it does | Examples |
|---|---|---|
| Terminal (VT / UT) | Displays implement interfaces, accepts soft key and AUX-N input | Tractor VT, aftermarket VT |
| Implement ECU | Executes commands on the implement (switches outputs, drives sensors, reports state) | Relay module, section-control ECU, sprayer controller |
| Gateway | Bridges the ISOBUS bus to a non-ISOBUS network | Telematics modem, protocol converter |
| Task Controller | Runs prescription maps and coordinates section control | TC on tractor, TC-BAS / TC-SC / TC-GEO |
The terminal is the user side. The implement ECU is the working side. A gateway is neither: it carries data on or off the ISOBUS bus in a form ISOBUS itself cannot handle. For the terminal side of this stack, see ISOBUS terminal solutions: VT, UT and AUX-N. For the implement side, see ISOBUS implement control: VT and AUX-N setup guide.
Three categories of ISOBUS gateway
Most gateways in the market fall into one of three groups. Each solves a different problem.
Telematics gateway
A telematics gateway reads data off the ISOBUS bus and sends it off-machine over cellular, WiFi, or satellite. Engine hours, fault codes, GPS position, PTO state, fuel level. It does not switch anything on the implement side. OEM examples include the fleet-monitoring platforms that ship as options on modern tractors, and third-party fleet-tracker boxes that clip onto the bus.
This is the most common thing farmers mean when they say "ISOBUS gateway" in a business context: remote monitoring, hour tracking, service alerts.
Protocol converter
A protocol converter translates message frames between ISOBUS and a different CAN protocol, typically J1939 or a proprietary manufacturer bus. You need one when a controller in your workflow does not speak ISO 11783 natively and you want it visible on the tractor's Virtual Terminal, or when a legacy implement uses a bus format the tractor cannot read.
These are specialist devices, usually sold by system integrators. They do not appear on a farm supply shelf.
Section-control ECU (sometimes called a gateway)
A TC-SC (Task Controller, Section Control) ECU listens to the tractor's Task Controller, reads the current GPS position, and switches implement sections on or off according to the prescription map or field boundary. Strictly speaking this is an implement ECU with a TC client, not a gateway. But farmers regularly call it one because it sits between the tractor's map data and the implement's valves, and "gateway" is the word people reach for.
If the term appears in a product listing next to boom section counts and GPS accuracy, that is what it means.
When you actually need an ISOBUS gateway
Three scenarios where a gateway is genuinely the right answer:
- You want to log or transmit machine data off the tractor. A telematics gateway reads the CAN traffic and pushes it to a service platform. Nothing else on this list does that.
- You have a legacy implement on a non-ISOBUS CAN bus and want it visible on the tractor's VT. A protocol converter re-encodes the messages so the tractor's terminal can render the implement's interface.
- You need automatic, map-driven section control on an implement that has valves but no Task Controller client. A TC-SC ECU turns each section on and off based on GPS position and the prescription map. This is a different product category from a relay module, which switches sections manually from a button.
If none of these three matches what you are trying to do, you probably do not need a gateway. You need a terminal, an implement ECU, or a relay module.
How a gateway sits on the CAN bus
Whichever category applies, the physical picture is similar. The gateway connects to the ISOBUS network through the standard 9-pin socket, in-cab or rear external, and shares the bus with every other ISOBUS device on that machine. See the ISOBUS connector pinout guide for the pin assignments on both sockets.
On the bus side, the gateway claims a source address and either listens (telematics), translates (protocol converter), or actively participates as a Task Controller client (TC-SC ECU). On the far side it drives whatever the non-ISOBUS link is: a cellular modem, a J1939 stub, a set of valve outputs. The bus itself runs at 250 kbit/s with 120 ohm termination at each physical end, and the gateway does not change that.
Multiple ISOBUS devices coexist on the same bus, so adding a gateway does not knock a relay module or a VT out of contention. Address arbitration is part of the standard.
ISOBUS Block is not a gateway
ISOBUS Block is a universal implement ECU. It retrofits ISOBUS control onto any implement by giving you eight relay outputs the operator switches from the tractor's Virtual Terminal or AUX-N buttons. It is not a gateway in the strict sense: it does not translate between networks or push data off the machine. It uses the ISOBUS bus, it does not bridge it.
That distinction matters because it is the reason ISOBUS Block does not need any of the categories above to work. Plug it into the in-cab or rear external ISOBUS connector, the tractor sees it as a working set, and you assign buttons on the screen. No telematics platform in the middle, no protocol converter, no TC-SC client. The relay switches, the load turns on.
The channels are CH1 through CH8, each independently set to TOG (toggle) or MOM (momentary) mode from the VT. Multiple channels can be grouped to a single button so a diverter valve and a work light activate together. 8 channels, 10 A per channel, 12 V and 24 V systems supported by the same module.
WiFi is on the module, but its scope is diagnostics and firmware only. It is not a telematics link and does not push data to a cloud service. Configuration happens on the VT screen.
Using ISOBUS Block alongside a gateway
You can run ISOBUS Block on the same tractor as a telematics gateway or a TC-SC ECU. They occupy different roles on the bus and do not conflict at the CAN layer. A common setup: the tractor has an OEM telematics gateway logging engine data, the implement has a TC-SC ECU running automatic section control, and ISOBUS Block sits on a separate channel-count you want to switch by hand from the armrest. Each device claims its own address and shows up as its own working set on the VT.
If all you want is to switch relays from your tractor screen, though, you do not need any of the others. That is the whole point of a universal implement ECU.
Frequently asked questions
What is an ISOBUS gateway?
An ISOBUS gateway is a device that bridges the ISOBUS CAN network to a network it cannot talk to natively. That includes telematics gateways (ISOBUS to cellular), protocol converters (ISOBUS to J1939 or a proprietary CAN protocol), and Task Controller section-control ECUs (which farmers often call gateways). It is a bridging device, not a user interface and not a load-switching device.
Do I need an ISOBUS gateway to use ISOBUS Block?
No. ISOBUS Block plugs directly into your tractor's ISOBUS socket, appears on the Virtual Terminal, and takes commands from the VT screen and AUX-N buttons. No gateway sits between them. If a gateway is already on the tractor for other reasons, ISOBUS Block coexists with it on the CAN bus without conflict.
How is an ISOBUS gateway different from a Virtual Terminal?
A Virtual Terminal is the display inside the cab that renders implement interfaces. It is the screen the operator presses buttons on. A gateway sits on the bus and translates ISOBUS traffic to or from something else, with no user interface. The VT is what you touch; the gateway is what you do not.
What ISOBUS gateway solutions are on the market?
Three main types. Telematics gateways read the bus and send data off-machine over cellular or WiFi (OEM fleet platforms and third-party fleet trackers). Protocol converters bridge ISOBUS to J1939, Modbus, or a proprietary CAN bus for legacy implements or cross-industry equipment. Section-control ECUs are TC-SC clients that switch implement sections based on GPS position and a prescription map. All three are sold by different suppliers and solve different problems.
Is ISOBUS Block a gateway?
No. ISOBUS Block is a universal implement ECU, a relay module that receives commands from the tractor's Virtual Terminal and AUX-N inputs and switches eight physical relay outputs. It uses the ISOBUS network but does not translate to another one and does not send data off the machine.
Can an ISOBUS gateway control hydraulic functions?
Not directly. A gateway bridges networks; it does not switch relays or drive solenoids. What switches a hydraulic function is the relay on an implement ECU, which energises the solenoid valve. If you want ISOBUS control of a hydraulic function, you need the ECU with the relay, not a gateway. See ISOBUS implement control: VT and AUX-N setup guide.
How does an ISOBUS gateway connect to the tractor?
Through the standard 9-pin ISOBUS connector, either the in-cab connector or the rear external connector, depending on where the gateway is mounted. Both sockets use the ISO 11783-2 pinout: pins 2 and 4 for CAN, pin 7 for power, pin 9 for ground on the in-cab side. The ISOBUS connector pinout guide covers both connectors in detail.
If nothing is working, where do I start?
Check the CAN bus first. Measure roughly 60 ohm between CAN_H and CAN_L with the system powered off (that is two 120 ohm terminators in parallel). Confirm the connector is fully seated on the correct socket, in-cab versus rear external. Address conflicts and missing termination cause most first-plug faults. The ISOBUS troubleshooting guide covers the common ones in detail.
Need to switch relays from your tractor's Virtual Terminal? ISOBUS Block is a universal implement ECU with 8 relay outputs, controlled from the screen you already have. Kit-selection and installation questions are answered on the FAQ page.