Default communication profile configuration

What does 9 mean?

The drive is stuck in its default communication profile configuration state during boot-up, preventing it from initializing correctly. This can be caused by mismatched encoder configurations or corrupted drive parameters. If unresolved, the drive will not enter an operational state or establish proper communication.

• Mismatched encoder configuration (e.g., Parameter P2-01 (Feedback device type), P2-02 (Number of encoder lines)) preventing the drive from establishing motor feedback.
• Corrupted communication profile settings in non-volatile memory (NVRAM).
• Invalid or unsupported communication settings for the fieldbus (e.g., EtherCAT, CANopen) configured in parameters (e.g., P6-01, P6-02).
• A critical internal data structure related to communication initialization is corrupted.
• Attempting to boot with a generic communication profile that doesn't match the specific fieldbus hardware or requirements.

Click steps to track your progress.

1. 1

   Connect to the drive using commissioning software and verify the current values of critical feedback parameters (e.g., P2-01, P2-02, P2-03) against the actual encoder specifications.

2. 2

   Check communication profile parameters (e.g., P6-01 for fieldbus type, P6-02 for node ID) for consistency with the network configuration.

3. 3

   Perform a partial reset of communication-related parameters (if supported) or a full factory reset (e.g., using Parameter P0-00) if configuration is suspected to be corrupt.

4. 4

   Re-download a known good communication configuration or a complete drive parameter file to ensure correct settings.

5. 5

   Isolate the drive from the fieldbus network during boot-up to determine if network communication issues are contributing to the boot failure.