Troubleshooting

Scope

Use this page as the symptom-based index for the knowledge base. Start here when you know the visible problem, but not yet which detailed page to use.

Fast Routing

1. Check panel for overall status.
2. Check ethercat command line interface if EtherCAT or slave state is in doubt.
3. Use the symptom groups below to pick the detailed page.

Startup and EtherCAT

• EtherCAT validation fails: verify slave order/ids, confirm process image matches hardware, and check for missing power or ESTOP on drives. Use: general, ethercat command line interface, hardware
• IOC will not start after partial hardware failure: fix cabling and power first; restarting with missing slaves can leave the IOC unusable. Use: general, hardware
• No slaves are visible or link is down: Use: ethercat command line interface, host / ecmc server, hardware

Motion and Axis Behavior

• Axis will not enable: check auto-enable strategy, STO/brake signals, and drive readiness. Use: motion, hardware
• Axis moves in the wrong direction: Use: direction, motion
• Homing stalls or never completes: Use: homing, motion
• Soft limits are not respected: Use: motion, yaml configuration
• Following error, stall, or poor motion quality: Use: motion, tuning

PLC and Scripting

• Limit logic overrides do not behave as expected: when using plcOverride, verify that PLC code writes ax<id>.mon.lowlim/highlim correctly. Use: motion, PLC configuration
• Startup scripts or verification scripts behave unexpectedly: review SCRIPTEXEC use and macro expansion. Use: general, Script Reference

Diagnostics Tools

• Use the hardware diagnostics guide for ec_diagnostic_messages.py usage and interpretation: Diagnostics
• Use read_el70xx_diag.sh or read_el5042_diag.sh for Beckhoff drives/encoders.
• Check iocsh output for YAML lint/schema errors.

Error Code Quick Map

Related Pages

• knowledge base
• panel
• ethercat command line interface