EFB config file

What does 6682 mean?

The embedded fieldbus (EFB) configuration file could not be read by the drive. This prevents the EFB protocol from initializing correctly. The fieldbus communication will not function, and the drive cannot be controlled via EFB.

• The embedded fieldbus (EFB) configuration file stored on the drive is corrupt, incomplete, or missing.
• An incorrect EFB configuration file was downloaded to the drive, not matching the selected EFB protocol (e.g., P7-00 EFB Protocol).
• Drive firmware version (P0-01 Firmware Version) is incompatible with the EFB module or the specific features defined in the configuration file.
• Insufficient memory or storage on the drive to properly load and initialize the EFB configuration.
• Power interruption during EFB configuration file write operation, leading to data corruption.

Click steps to track your progress.

1. 1

   Attempt to re-upload the correct EFB configuration file from the PC configuration software (e.g., DriveWorks, Drive Composer) to the drive.

2. 2

   Verify that the EFB protocol selected in parameter P7-00 (EFB Protocol) is correct and matches the fieldbus system in use.

3. 3

   Check the drive's firmware version (P0-01 Firmware Version) against the EFB module documentation for compatibility requirements. Update firmware if necessary.

4. 4

   Perform a drive parameter reset to factory defaults (e.g., P9-02) and then manually reconfigure only the essential EFB parameters.

5. 5

   If using a removable memory card for configuration storage, ensure it is properly inserted and not corrupted. Try a different memory card if available.