OEM software engineers search for CANopen joystick EDS file documentation when adding a cab stick to a CiA 301 tool chain — DeviceNet Designer, CANopen DeviceDesigner, or in-house importers [Source: CiA 301 device profile]. Without correct PDO mapping, the ECU reads scaled axes but safety interlocks never see neutral.
Trunsin ZS40 ships configuration-specific object dictionary data on approved programs. Extend CANopen integration with this EDS-focused checklist.
CANopen joystick EDS file — import workflow
- Import vendor EDS into network project
- Assign node ID — avoid J1939 address conflicts on mixed buses
- Map TPDO/RPDO to ECU variables
- Set heartbeat consumer timeout
- Commission deadband and neutral window
- Log EMCY on fault injection test
EDS vs live PDO — common gaps
| Issue | Symptom | Fix |
|---|---|---|
| Wrong EDS revision | Missing objects | Request config-specific EDS from Trunsin |
| Bitrate mismatch | No heartbeat | 250k vs 500k — wiring guide |
| Deadband too tight | Centering fault | Commission per integration article |
| Safety assumed | SRDO expected | Read SRDO guide |
Frequently asked questions
Does Trunsin publish public EDS for all ZS40 builds?
EDS is configuration-specific — request with your signed PDF.
CANopen vs J1939 EDS?
Different object models — pick bus per ECU, not both on one stick port.
elobau EDS compatible?
No — import Trunsin object dictionary for ZS40 builds.
Who owns PDO bit layout?
Defined in approved configuration — document in FAI report.
Related articles
- CANopen integration
- J1939 source address
- CAN bus wiring
- CANopen diagnostics
- elobau alternative
- Configurator
Request ZS40 EDS package
- Export ZS40 PDF with CANopen options
- Share ECU tool chain and node ID plan
- Schedule bench PDO test before vehicle trial