CAN, Modbus and serial equipment integration
Every integrator hits the job the standard tracker can't do: a generator to monitor over Modbus, a truck whose CAN data the platform doesn't decode, a legacy device on RS232. Usually that means an extra PLC or a custom firmware request.
How the logic runs
Pick the interface: CAN bus, RS232, RS485 (Modbus-RTU), or Bluetooth/BLE — all covered by ready templates.
The algorithm reads the raw messages — e.g. J1939 error codes, brake-pedal and engine-speed values off CAN, or register values from a Modbus meter.
On-device processing turns them into variables, events, or output actions — your logic, not a firmware feature request.
Processed values transmit to your platform in the normal data stream.
The parsing and the decision logic run at the equipment, not after a round-trip. And when a job needs more I/O, there's a ready template for extending the tracker with a Canny PLC.
- Reading error codes from CAN-bus
- Receiving and processing data from CAN-bus
- Sending CAN messages
- Equipment integration via Modbus protocol
- Modbus server
- Data transfer between RS 232 and RS 485 interfaces
- Receive Bluetooth messages
- Connecting a Canny PLC
Proven templates from the Easy Logic library — we commission and adapt them to your fleet.
Straight answers
Is J1939 fault-code reading really a template, not custom firmware?
'Reading error codes from CAN-bus' is a ready partner template monitoring J1939 messages and reporting CAN bus errors.
What Modbus equipment has been integrated?
Templates cover generic Modbus equipment integration, a Modbus server exposing the tracker's own I/O, and partner templates for OWEN meters and displays.
Bluetooth sensors too?
Yes — templates exist for both receiving and sending BLE messages, recording peripheral data to your monitoring server.
Want this running on your fleet?
Describe the operation — we quote the hardware and commission the algorithm with you. Stock in Johannesburg, no MOQ.