I encountered an issue while trying to install a 2080-OF2 module for the first time on a Micro820 PLC. I suspect that the brand new module, purchased from an authorized distributor, may be faulty. Despite sending valid raw output counts from my logic, I am getting 0 mA on both channels. I have researched similar posts to troubleshoot my problem, but they mainly discuss the "raw count" issue, which I believe is not the root cause. Even though I am receiving a constant 14.32 VDC instead of the expected 0-10 VDC range, I am not getting any current values. This leads me to believe that the module might be damaged due to the higher voltage, preventing the current values from registering. Do you think this is a reasonable assumption? Let me know your thoughts on this issue.
Encountered a problem with the micro-controller that locks a channel when a broken wire is detected. One solution to try is to reset the module after a wire is disconnected on 2/24/2021. The 2085-OF4 module may stop working due to hardware errors detected by the DAC, like broken wires or high resistance loads on a specific channel. To resolve this issue, the corresponding channel is disabled until the error is cleared by the user. To learn more, refer to the Micro800 Discrete and Analog Expansion I/0 User Manual Publication 2080-UM003. CE errors can be addressed during run mode to clear hardware error bits and re-enable the disabled channel. Specific bits are associated with each channel (CEO for Bit 8, CE1 for Bit 9, CE2 for Bit 10, and CE3 for Bit 11). A value of 3848 will reset all 4 channels, while a value of 2056 will reset channel 3 (CE3).
Thank you for the reply, diat150. I have noticed that the troubleshooting options for a 2085 expansion module differ from those for a 2080 plugin module. The plugin module only displays raw values without diagnostic bits. Moving the module to a different slot or power cycling it did not resolve the issue. It is puzzling to see voltage readings when no wires are connected to the terminals.
I discovered a troubleshooting guide available to everyone regarding erratic readings in a specific module. While it may not directly address your issue, the recommended "fix" is definitely worth a shot. According to the guide on Rockwell Automation's website, the problem could potentially be caused by a corrupted project. The suggested solution involves removing the module from the project, saving it, downloading it to the PLC, re-inserting it, and downloading it again. This may seem unconventional, but it is recommended to give it a try.
The solution suggested by joseph_e2 may have seemed unusual, but it turned out to work perfectly! Despite hours of technical support with RA, this simple fix wasn't mentioned. Many thanks to joseph_e2 for sharing this valuable tech note here. If you stumble upon this thread while searching for a similar issue in the future, consider diat150's advice on clearing Channel errors. joseph_e2's suggestion indirectly achieved this, albeit with a different module. This solution worked for me, and I am grateful for their assistance.
Eric from ITC praised joseph_e2 for finding an unconventional yet effective solution to a technical issue. Despite struggling for three days with RA Technical Support, the solution provided by joseph_e2 proved to be successful. This underscores the importance of sharing knowledge and experiences in troubleshooting tech problems. For future reference, diat150's advice on clearing Channel errors aligns with joseph_e2's recommendation, which resolved the issue at hand. The solution may vary depending on the specific module being used, such as a plugin versus an expansion module. Nonetheless, the collaborative effort between the community members led to a successful outcome. If you encounter a similar problem, remember to refer back to this thread for potential solutions. In a related experience with the 2080-OF2 module installation, the shared solution proved effective once again. This highlights the value of collective problem-solving in resolving technical challenges.
Your assumption seems logically sound, particularly if you have already eliminated all possible programming and wiring errors. The increased voltage value you're noticing can indeed damage the module and hinder its functioning. It's possible that an internal component got damaged due to this, preventing the correct current values from registering. If the module is indeed faulty, I would recommend reaching out to the distributor for a replacement, especially if it's still under warranty. However, before going that route, you might want to try a factory reset of the module just to ensure it's not a software related issue.
Given the information you've provided, it's plausible to consider the potential damage due to higher voltage as a reason behind the issue. However, before jumping to the conclusion that the 2080-OF2 module is faulty, another factor to examine could be the configuration. Ensure that the output type is set up correctly in the software and matches the physical attributes of the module. It's possible for the software to depict valid raw counts while the hardware behaves differently if there's a mismatch. If after checking all these, the problem persists, a defective module could indeed be the cause.
It seems like you've done a thorough job of diagnosing the issue, so kudos for that. Your assumption regarding the module damage might hold some water. Considering that you're receiving a constant 14.32 VDC instead of the expected 0-10 VDC range, that could potentially point towards overvoltage damage. However, it would be best to be sure before you replace the module altogether. Maybe try swapping out the module with another 2080-OF2 if you have one handy, to see if you get the same result. Also, double-check that you've configured the module correctly. Incorrect configuration could also cause problems. Keep us updated on your progress!
It definitely sounds like you’ve put a lot of thought into your troubleshooting process, and your assumption about the module being possibly damaged due to that constant voltage is quite reasonable. It’s unusual for a brand-new module to fail right off the bat, but electronic components can sometimes be sensitive. Have you tried checking the wiring and connections again, just to rule out any installation errors? Also, it might be worth looking into whether there are any specific settings in your PLC programming that could affect the output range. If all else fails, reaching out to the distributor for a replacement or further support could be a good next step!
It sounds like you’ve done a thorough job troubleshooting the situation, and I can see why you suspect the module might be faulty. The constant 14.32 VDC could definitely indicate an issue if you're expecting a range between 0-10 VDC, which may have led to damage in the module. Before jumping to conclusions about the module's health, though, I’d recommend double-checking the wiring and configuration settings in the PLC to make sure nothing is misconfigured. If everything checks out and the voltage readings don't fall within the expected parameters, it might be worth contacting the distributor for a replacement or further testing. Good luck, and I hope you get to the bottom of this soon!
✅ 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: The issue could potentially be related to a fault in the module, especially if you are receiving a constant 14.32 VDC instead of the expected 0-10 VDC range.
Answer: Yes, the constant higher voltage output could be a sign of a damaged module, potentially preventing the current values from registering as expected.
Answer: If you suspect a faulty module, you may need to consider contacting the authorized distributor for support or possibly requesting a replacement to address the issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.