Slave not scanned or address 0

What does E4010 mean?

The IndraDrive MPx02 (acting as a slave device on a fieldbus network) has not been successfully scanned by the master controller, or its configured address is detected as 0, which is typically an invalid or unassigned address. This prevents communication and control via the fieldbus, rendering the axis inoperable.

• The IndraDrive MPx02 is incorrectly configured with a slave address of 0 (which is reserved or invalid for many protocols).
• The master controller is not correctly configured to scan or recognize the drive's assigned network address.
• Physical wiring issues on the fieldbus (e.g., loose connections, incorrect termination, cable damage) preventing the slave from being detected.
• Power-on sequence issues where the drive is not fully ready for communication when the master attempts to scan.
• Duplicate address on the network.

Click steps to track your progress.

1. 1

   Verify the slave address configuration in the IndraDrive MPx02 (e.g., via DIP switches or parameters) and ensure it is a unique, non-zero address within the network.

2. 2

   Check the master controller's configuration to ensure it includes the correct network address for the IndraDrive MPx02 and is set to scan for it.

3. 3

   Inspect the physical fieldbus wiring (e.g., SERCOS, CANopen, PROFIBUS) for continuity, correct termination, and absence of shorts or breaks.

4. 4

   Ensure that the IndraDrive MPx02 is fully powered on and initialized before the master controller attempts to scan the network.

5. 5

   Review the fieldbus diagnostics on both the master and slave devices for more specific communication error indicators.