OEM controls engineers integrating a CANbus industrial joystick ECU interface face three recurring gaps: PDO mapping ambiguity, bus termination errors, and missing fault-handling logic when a stick drops off the network. Trunsin CANopen sticks — notably ZS40 and AT11 — ship with documented CANopen joystick mapping sheets tied to each configurator build.
For operator-facing benefits on construction fleets, see seven game-changing CANbus joystick ways — this article is the engineering integration layer.
CANopen stack basics for joystick nodes
Industrial mobile machines typically run CAN 2.0B physical layer with CANopen application layer. The joystick acts as a slave node publishing process data:
| Object | Purpose |
|---|---|
| TPDO | Axis position, button bits, fault flags to ECU |
| RPDO | Configuration commands from ECU (when supported) |
| SDO | Parameter access during commissioning |
| Heartbeat / NMT | Online detection and state management |
| EMCY | Fault broadcast when sensor or internal error occurs |
The ECU master must allocate unique node IDs and map TPDOs into hydraulic control algorithms — integration fails when teams treat the stick as “plug and play” without a signed PDO table.
Integration checklist for OEM engineers
- Bus physics — 120 Ω termination at network ends; stub length within OEM network guide
- Node ID plan — document stick node ID vs other slaves (ECU, I/O modules, displays)
- PDO map — axis scaling, neutral deadband, and button bit order signed by controls lead
- Fail-safe behavior — define ECU response when heartbeat stops (neutral command, safe shutdown, or limp mode)
- Commissioning tool — CAN analyzer trace saved with first-article sign-off
- Harness — shield termination per ECU supplier rule; separate power ground from signal reference
Trunsin releases PDO defaults per configured model. OEM teams override scaling in the ECU — but the released PDF is the contract baseline for field replacement sticks.
ZS40 vs AT11 on the same bus
Both appear on industrial joystick mobile machinery programs:
- ZS40 — compact CANbus stick for excavator and loader cabs; common on construction ECU retrofits
- AT11 — multi-axis controller for mining and complex hydraulic machines requiring integrated axis packs
Node ID collisions happen when fleets mix stick models without updating the bus table — treat each configurator PDF as a unique network object.
How we validate CANbus integration
- Desk review — OEM engineer submits ECU PDO plan; Trunsin confirms object compatibility before shipment
- Bench hookup — stick on terminated bus with USB-CAN adapter; trace heartbeat and TPDO rates
- Fault injection — disconnect stick; confirm ECU executes documented fail-safe
- First article on machine — full hydraulic function sweep with logged CAN trace
- Replacement parity — spare stick from same configurator build reproduces PDO map without ECU reflash
Frequently asked questions
Does Trunsin supply EDS files?
CANopen device description files are available for configured builds on request — attach the configurator PDF when asking sales@trunsin.com.
Can one ECU read two Trunsin sticks?
Yes, with unique node IDs and separate PDO maps — common on crane master/slave layouts.
What bitrate should we standardize on?
250 kbit/s and 500 kbit/s dominate mobile machinery; match existing ECU and display nodes — do not mix bitrates on one bus.
Related resources
- Industrial joystick hub
- ZS40 CANbus joystick
- CANbus construction application note
- Configure ZS40 online
Start ECU integration
- Export ZS40 or AT11 PDF from configure
- Send ECU PDO plan to Trunsin engineering
- Schedule bench commissioning before fleet rollout