How to Replace PowerFlex 40 Drive with Revision Mismatch on DeviceNet Network

Question:

Hello everyone, I am seeking advice on replacing a PowerFlex 40 drive on a DeviceNet network. The new drive I have purchased has a revision mismatch. Unfortunately, I am unable to change the revision in RSLogix5000 or RSNetworx as not all drives on DeviceNet are showing up. Can anyone advise on what steps I should take in this situation? Your assistance is greatly appreciated. Thank you.

Top Replies

Which specific Devicenet scanner model do you currently employ?

Whenever I encountered a firmware revision mismatch, I would simply go online using RSNetworx to perform an update, which effectively resolved the issue.

For older scanners, accessing the PLC in program mode is necessary for downloading the RS network configuration after making changes. However, newer models may allow for online editing of scan lists. This feature is especially beneficial for users who need to modify network settings on the go.

Good morning! I am using a 1756-DNB DeviceNet card for my device.

I can utilize RSNetworx to make updates and perform uploads/downloads to a new drive. However, the MOD light on the drive is continuously flashing and is accompanied by the error code F071.

Hi there! It sounds like a frustrating predicament with the revision mismatch on your DeviceNet network. First, I'd recommend double-checking the firmware version on all devices connected to the network to ensure they’re compatible with your new PowerFlex 40 drive. If you're still not seeing all drives in RSLogix5000 or RSNetworx, it might help to cycle the power on your network devices and ensure that termination resistors are properly in place. Additionally, try using the DeviceNet scanner’s online tools to see if it can recognize the new drive; sometimes a simple configuration refresh can do the trick. If the issue persists, checking the network configuration settings to confirm they match can also be a good bet. Hope you get it sorted out soon!

It sounds frustrating to deal with the revision mismatch and the visibility issue on DeviceNet! First, I’d recommend double-checking the firmware version of all your existing drives to ensure they are compatible with the new PowerFlex 40 drive you’ve purchased. If some drives aren't appearing in RSNetworx, try cycling the power to the DeviceNet network and running a network scan to see if that helps bring them back online. Also, make sure that your device definitions in RSNetworx are up to date; sometimes, outdated definitions can lead to these kinds of issues. If the problem persists, consider a temporary workaround by using a different gateway or device to facilitate communication until you can resolve the revision conflict. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. FAQ: How can I replace a PowerFlex 40 drive with a revision mismatch on a DeviceNet network?

Answer: Answer: If you are unable to change the revision in RSLogix5000 or RSNetworx due to not all drives showing up on DeviceNet, you may need to troubleshoot the network to ensure proper communication and address any issues causing the drives not to be detected.

FAQ: 2. FAQ: What steps should I take when facing a revision mismatch issue with a new PowerFlex 40 drive on a DeviceNet network?

Answer: Answer: You can try checking the network configuration, verifying the connections, ensuring the correct firmware versions, and troubleshooting any communication issues to resolve the revision mismatch problem.

FAQ: 3. FAQ: How can I address the situation of not all drives showing up on the DeviceNet network when trying to replace a PowerFlex 40 drive?

Answer: Answer: You may need to investigate potential network issues, such as faulty connections, improper addressing, or configuration errors, to ensure all drives are detected on the DeviceNet network before attempting to change the drive revision.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’