Dear Sirs, I have been exploring solutions for the issue mentioned above, but so far, my attempts have been unsuccessful. I am in need of assistance. The drive in question utilizes a 20 Comm-d device net card to communicate and is being scanned by a 1756 DNB scanner in a control logix L62 PLC rack. Although the drive may be over 10 years old, we only recently began using it after taking over the facility. Initially, it operated smoothly for a few days, but then the mentioned fault began to occur multiple times during operation. When this happens, the drive's status ceases to update, and if the drive was currently active, it stops functioning. Strangely, the DNB scanner does not detect any faults as it fails to update the statuses monitored by the PLC, indicating that the drive is still active and running. When I checked in RsNetworx, I found that the only node not communicating is this particular drive. All nodes before and after it are functioning properly. After perusing various forums, I attempted the following troubleshooting steps: 1. Separating the Device net cable from the frontside of the drive from higher voltage sources. 2. Swapping the 20 Comm-d card with a spare drive we had. 3. Adjusting Parameter 270- DPI Data rate to 500 Kbps. 4. Searching for a firmware update on the Rockwell Automation website, but the latest version available is 2.001, which matches the current version on the card. Despite these efforts, the fault persists. It has been noted that the issue also arises when attempting to start the system after it has been idle for a few hours. Your time and assistance are greatly appreciated. Thank you for your support. Sincerely,
In addition to my previous post, I made sure to verify the termination resistors at both ends of the DeviceNet network. I tested the resistance and found it to be 121 ohms, which aligns with information from various forums. Despite this, the issue persists and I am struggling to pinpoint the root cause. Any advice or suggestions would be greatly appreciated. Thank you.
Hi there! It sounds like you've done a thorough job troubleshooting already, which is impressive given the complexities of older systems. One thing you might want to look into is the power supply to the drive; sometimes older equipment can be sensitive to voltage fluctuations, which might explain why the issue arises after being idle. Additionally, if you haven't already, checking the grounding of the drive and its cable might help, as ungrounded or poorly grounded connections can cause communication issues over time. Hopefully, this resolves your issue or at least gives you a new direction to explore! Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Fault 75 on a Powerflex-70 EC 600V Drive with a 20 Comm-d Card is a specific issue that causes the drive's status to cease updating and may result in the drive stopping its operation.
Answer: - Some troubleshooting steps for Fault 75 on a Powerflex-70 EC 600V Drive with a 20 Comm-d Card include separating the Device net cable from higher voltage sources, swapping the 20 Comm-d card with a spare one, adjusting Parameter 270 - DPI Data rate, and checking for firmware updates.
Answer: - The DNB scanner may fail to detect faults related to the communication issue with the drive because it does not update the statuses monitored by the PLC, indicating that the drive is still active and running.
Answer: - The persistent Fault 75 issue could be caused by various factors, such as specific hardware malfunctions, compatibility issues, or communication errors within the system. Further investigation may be needed to pinpoint the exact cause.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.