Machine builders debugging a CANopen heartbeat consumer timeout on a joystick node often replace a healthy stick because the master logged “node lost” — when the real fault is consumer time (1016h) set shorter than producer interval (1017h), a busy master missing one beat, or a baud/termination glitch that drops only heartbeat frames [Source: CiA 301 heartbeat producer/consumer rules; CANopen device profile commissioning notes; Trunsin CANopen diagnostics cluster]. Trunsin ZS40 RFQs should document heartbeat producer ms, expected consumer guard, and NMT policy before field swap.
Start with CANopen diagnostics on industrial joysticks, CANopen joystick EDS file, CANopen PDO mapping joystick, and CANbus wiring termination before blaming the grip.
CANopen heartbeat consumer timeout — producer vs consumer math
| Object / setting | Role | Common mistake |
|---|---|---|
| 1017h producer heartbeat time | Joystick transmits guard frame interval | Left at factory default unknown to integrator |
| 1016h consumer heartbeat time | Master expects beat within window | Consumer shorter than producer + jitter |
| Guard time / life time factor | Legacy master terminology | Mixed with CiA 301 ms fields |
| NMT state | Pre-operational vs operational | Heartbeat OK but no TPDO motion |
| Node-ID conflict | Duplicate ID on bus | Intermittent timeout on boot |
A CANopen heartbeat consumer timeout fault with healthy TPDO when forced operational usually means timing policy — not failed Hall sensors inside the stick [Source: CiA 301 NMT error control; master stack guard configuration guides].
Commissioning checklist before RMA
- Read 1017h on the joystick EDS — Note producer interval in milliseconds.
- Set master consumer ≥ producer + margin — Allow bus load and master scan jitter.
- Log heartbeat for 60 s at neutral — Compare to PDO traffic on the same node.
- Verify termination and stub length — Single-frame drops mimic node loss.
- Confirm node-ID via LSS if needed — CANopen LSS node ID joystick.
After heartbeat is stable, map PDOs and deadband — CANopen integration EDS PDO deadband — before production run.
When timeout points to hardware
Replace or reseat the stick when heartbeat never appears after clean NMT reset, supply is in spec, and no duplicate node responds on the analyzer. Intermittent beats during cab vibration often trace to connector backshell strain — not internal CAN transceiver failure.
Frequently asked questions
Is heartbeat the same as PDO?
No — heartbeat is NMT error control; PDO carries axis data.
What margin should consumer use?
Typical practice: consumer window at least 2× producer interval; confirm with master vendor.
Does ZS40 ship with fixed heartbeat?
Document producer ms on RFQ; some builds are configurable via SDO.
Where is EMCY covered?
CANopen diagnostics guide — heartbeat healthy with EMCY is a different fault path.
Related articles
- CANopen diagnostics on industrial joysticks
- CANopen joystick EDS file
- CANopen PDO mapping joystick
- CANopen LSS node ID joystick
- Industrial joystick hub
- Configurator
Specify CANopen heartbeat policy on ZS40 via the Trunsin configurator after master stack guard settings and EDS revision are attached.