Drive not ready during axis start

What does 4225 mean?

During the startup sequence of an axis, the associated drive is found to be in a non-ready state. Possible causes include the drive being in a hardware error state, still in its power-up or boot-up phase (which can take several seconds after a reset), or lacking the necessary controller enable signal. This prevents the axis from becoming operational.

• Associated servo drive (e.g., via EtherCAT, PROFINET) is in a fault state (e.g., overcurrent, overvoltage, motor temperature).
• Drive has not completed its power-up and initialization sequence (e.g., still booting or performing self-diagnostics).
• No power supply to the servo drive (e.g., missing 24VDC control power, missing 400VAC main power).
• Communication error between the NC controller and the drive (e.g., broken EtherCAT cable, incorrect IP address).
• Drive parameters preventing it from reaching a ready state (e.g., incorrect motor type, encoder setup, safety configuration).

Click steps to track your progress.

1. 1

   1. Check the diagnostic display or LEDs on the associated servo drive for any active fault codes or warnings.

2. 2

   2. Verify main power supply (e.g., 400VAC phase-to-phase) and control power (e.g., 24VDC) to the servo drive terminals.

3. 3

   3. Inspect the communication cable (e.g., EtherCAT X2 connector) between the NC and the drive for breaks or loose connections.

4. 4

   4. Cycle power to the servo drive independently and observe its boot-up sequence and readiness status.

5. 5

   5. Review drive parameters (e.g., P01 'MotorType', P02 'EncoderType') to ensure they match the connected hardware.

6. 6

   6. Confirm the drive firmware is compatible with the NC controller's firmware version as per manufacturer documentation.