Inovance MD200, MD310 & MD290 Drive
1
Posts
1
Users
0
Reactions
178
Views
Sep 07, 2024 7:34 am
Cause : Slave error in master-slave control comes when a problem with one or more of the slave drives. This can prevent the drives from operating in a synchronized mode, leading to reduced performance or instability.
"Err55" fault in inovance MD290 drive indicate "Slave error in master-slave control". This means a problems with the communication cable, connectors, or settings between the master and slave drives can cause synchronization errors.
Troubleshooting Steps
-
Verify Communication:
- Check cables and connections: Ensure that the communication cables between the master and slave drives are undamaged and securely connected.
- Verify communication settings: Make sure that the communication settings (baud rate, parity, stop bits) are identical on all drives.
- Test communication: Use a communication analyzer to verify that the drives can communicate with each other.
-
Check Synchronization Settings:
- Review synchronization parameters: Ensure that the synchronization parameters (e.g., speed reference, synchronization mode) are configured correctly on all drives.
- Adjust settings if necessary: If the settings are incorrect, make the necessary adjustments to ensure proper synchronization.
-
Inspect Slave Drive:
- Check for hardware faults: Look for any signs of damage, overheating, or other issues with the slave drive.
- Verify power supply: Ensure that the slave drive is receiving adequate power.
-
Reduce Noise and Interference:
- Identify noise sources: Look for any nearby electrical equipment or devices that might be generating noise or interference.
- Shielding: If necessary, shield the communication cables or drives to reduce the impact of noise.
- Grounding: Ensure proper grounding of all drives to minimize noise.