Forum

Share:
Notifications
Clear all

Err16 Communication fault in inovance MD200 drive

1 Posts
1 Users
0 Reactions
70 Views
Posts: 18137
Admin
Topic starter
(@click2electro)
Member
Joined: 4 years ago

Cause : Communication fault comes when no control data was received from the connected PLC when using serial communications. This can prevent the drive from operating correctly or cause erratic behavior.

"Err16" fault in inovance MD200 drive indicate "communication fault". This means a problem with the communication between the drive and other devices or systems.

Common Causes

  • Cable Issues: Damaged, loose, or mismatched cables can disrupt communication.
  • Connection Problems: Faulty connectors or incorrect wiring can prevent proper communication.
  • Configuration Errors: Incorrect communication settings in the drive or connected devices can lead to communication failures.
  • Device Faults: Faulty communication modules or other hardware issues in the connected devices can cause communication problems.

Troubleshooting Steps

  1. Check Cables and Connections:

    • Inspect cables: Ensure that the communication cables are undamaged and free of kinks or bends.
    • Verify connections: Make sure that all connectors are securely plugged in and that the correct pins are connected.
    • Try a different cable: If possible, use a different cable to eliminate the possibility of a cable issue.
  2. Review Communication Settings:

    • Check communication parameters: Verify that the communication settings in the drive and connected devices are compatible (e.g., baud rate, parity, stop bits).
    • Correct any errors: If the settings are incorrect, make the necessary adjustments.
  3. Test Communication with Other Devices:

    • Connect to a different device: Try connecting the drive to a different device (e.g., a different PLC or HMI) to isolate the issue.
    • Test communication with a known-good device: If the problem persists, it may indicate a fault in the drive's communication circuitry.
  4. Inspect Connected Devices:

    • Check for device faults: If the problem is specific to a particular connected device, inspect that device for any issues.
    • Test the device with another drive: If possible, connect the device to a different drive to determine if the problem is with the device or the communication link.
Share: