Communication & control
The terminal sits on the machine bus and, where required, controls it. This page states exactly which protocols we support, which are in development, and what that means for your project.
| Protocol | Status | What it gives you |
|---|---|---|
| CAN 2.0B | Supported today | Two independent channels, 20 kbit/s to 1 Mbit/s, default 125 kbit/s. Custom transmit and receive variables without writing code. |
| SAE J1939 | Supported today | Engine, hydraulic and transmission parameters by SPN, plus DM1 and DM2 diagnostic trouble codes with an alarm channel. |
| CANopen | Supported today | Node and object-dictionary configuration, PDO and SDO mapping through the visual configuration tool. |
| J1939 DM1 / DM2 | Supported today | Fault lamp status, active and previously active trouble codes, with a searchable code library. |
| RS-232 / RS-485 | Supported today | One serial channel up to 115200 bit/s, point to point, for scales, printers and third-party devices. |
| Ethernet / TCP-IP | Supported today | RJ45, auto-negotiating. Used for programming, diagnostics and machine-side network integration. |
| MQTT / HTTP | Supported today | Telemetry to the cloud platform: machine state, work data and alarms. Also the path used for OTA updates. |
| ISOBUS / ISO 11783 (UT) | In development | Universal Terminal implementation and AEF conformance testing. Not available today — see the note below. |
| CAN FD | In development | Planned on the next board revision. Not available today. |
| EtherCAT | Not supported | We do not implement EtherCAT. If your machine is EtherCAT-based, a gateway would be needed, and we would rather tell you that now. |
Configured in EmbedBuilder
A note on ISOBUS
ISOBUS (ISO 11783) is required by most European agricultural OEMs, and we do not have it certified yet. Developing a Universal Terminal implementation and passing AEF conformance testing takes 12 to 18 months of dedicated engineering. It is on our roadmap.
Until then we will not quote an ISOBUS machine. If your project needs it, tell us — the volume informs whether we bring the schedule forward, and we would rather decline the business than deliver something that fails your conformance test.
From sensor to actuator
The same terminal that shows a value can act on it. Five stages, one project file.
- 01 Sensor acquisition
- 02 Communication & parsing
- 03 Control logic
- 04 Actuator output
- 05 Feedback & diagnostics
Not sure which protocol you need?
Send us the machine description or the existing bus specification. We will tell you whether we can read it, and which terminal fits.