Startup Prevented

What does 26 mean?

The drive cannot perform a startup because a new software (firmware or application), parameter setting, or other file affecting operation was loaded while a Run request was ON. The drive prevents startup to ensure configuration integrity and prevent improper operation.

• A firmware update or parameter upload was performed while a run command (e.g., DI1 active, P0-10 = 1) was still present.
• Application program was loaded or changed with the drive in a 'Ready' state, not 'Stopped' or 'Faulted'.
• Changes to critical safety parameters or hardware configuration (e.g., option board change) were saved without cycling power.
• Parameter setting download from an external tool (e.g., DriveWorks) occurred while the drive was expecting a run command.
• Persistent run command signal (e.g., stuck digital input, communication bit) remained active during a configuration change.

Click steps to track your progress.

1. 1

   Cycle the main input power to the drive (power off, wait for DC link discharge, power on).

2. 2

   Ensure that any run command signals (e.g., digital input terminal 1 (DI1), communication command) are deactivated before attempting further configuration changes.

3. 3

   Verify that no external control system is sending a persistent run command. Temporarily disconnect control wiring from terminals like DI1 to rule this out.

4. 4

   Re-check the drive's run/stop source parameter (e.g., P0-10) to ensure it is correctly configured for the desired control method (e.g., HMI, DI, fieldbus).

5. 5

   If a parameter file was recently uploaded, ensure the correct file version for the current application is active after cycling power.