No Communication?
- Verify RS232/RS485/Ethernet wiring matches pinout
- Check baud rate, parity, and communication settings
- Confirm correct IP address or node address
- Ensure drive communication interface is enabled
- Verify correct driver and port selection
Connection Established but No Response?
- Confirm correct parameter addressing or mapping
- Verify correct protocol (Modbus, EtherCAT, etc.) [manualzz.com]
- Check drive is in operational/enabled state
- Ensure controller/PLC is actively polling
Intermittent or Lost Communication?
- Check cabling and connectors for damage or noise
- Verify network stability or bus integrity
- Look for sync or communication faults (e.g., dropped frames) [kollmorgen.com]
- Confirm proper grounding and shielding
Drive Faults or Error Codes?
- Read fault code from display or software
- Identify fault type (overvoltage, overcurrent, temperature, feedback) [wakeindustrial.com]
- Correct condition (load, wiring, power quality)
- Clear fault and re-enable drive
No Motion or Motor Not Running?
- Verify drive is enabled and not faulted
- Confirm motor parameters are correctly configured
- Check command inputs and control signals
- Ensure safety circuits allow motion
Incorrect Motion or Behavior?
- Verify parameter configuration and tuning
- Check feedback device (encoder/resolver)
- Validate scaling, units, and limits
- Confirm correct motion commands
Read Works but Write Fails?
- Verify parameter is writable
- Check command syntax and execution conditions
- Ensure drive is not in protected or disabled state
- Confirm parameters are applied after write
Drive Not Responding Properly?
- Restart drive and communication interface
- Verify firmware/configuration compatibility
- Check power supply stability
- Test with minimal configuration
© HMS Networks AB 2025