1633

Category: Alarm

Cause

1. Drive debugging cable disconnected or making poor contact
2. Drive debugging serial communication subject to interference

Corrective action

1. Check the drive debugging cable wiring and ensure secure connections
2. Replace it with an isolated serial debugging cable
3. Strengthen interference suppression for the debugging cable, for example by adding ferrite cores, reliably grounding the debugging computer, and supplying the debugging computer and drive separately