Subject: Help Needed: GE IC200UDR164 Controller Configuration Fault Hello everyone, I apologize if this issue has been addressed in a previous discussion, but I couldn't locate the relevant information. I'm currently working with a GE IC200UDR164 controller and I've encountered a frustrating problem that I haven't faced before. Whenever I download my program to the controller, it triggers a system configuration fault. Typically, this issue arises from a mismatch due to an incorrect controller specified in the configuration. I'm utilizing PME 9.0 for programming. In the lower right corner of my screen, it indicates that both Hardware and Logic configurations are equal. Despite this, I can clear the stop fault and run my program without any issues. However, if the PLC loses power, it reverts to stop/fault mode during startup, requiring me to manually clear the configuration fault each time. I'm reaching out for assistance to resolve this issue; any guidance would be greatly appreciated, as this situation is becoming quite overwhelming. Thank you!
Is the error message displayed in the feedback area, or are you retrieving it from the I/O or CPU fault tables? Is your system set up to load its configuration from flash memory during startup? When it enters a fault state upon power-up, do the logic and configuration remain identical when you connect the PME?
1. Upon downloading, the feedback section indicates that there are configuration errors present. These errors are recorded in the CPU fault table as a system configuration mismatch. 2. The system is currently set up to retrieve data from RAM; however, I did attempt to access data from flash memory. 3. Indeed, when the system is in a stop or fault state during power-up, it confirms that the logic and configuration settings are aligned.
In the fault table, what should be recorded in the "location" column? It’s essential to verify the part numbers for both your CPU and any associated expansion modules to ensure they align with what you inputted in the hardware configuration. For instance, if you entered an IC200UDR164 as your CPU configuration but actually have an IC200UDD164, this discrepancy could lead to problems. Although both models have the same I/O count, you can clear the mismatch fault temporarily and run your program. However, keep in mind that every time the system performs a self-check upon startup, it will trigger the fault again. Make sure to rectify any part number inconsistencies to prevent recurring issues.
I have confirmed that my controller number is correct after thoroughly checking it multiple times. I chose the model IC200UDR064/164, and the physical identifier on my controller is IC200UDR164-DK. The controller is located at address 0.0. Currently, the fault status is as follows: Error Code: 34, Group: 11, Action: 3 (Fatal), Task Number: 20.
To check the status of your PLC while online, navigate to the "Status" window located within the "Target" menu, followed by "Online Commands." Here, you can view essential information such as your CPU model and firmware version. It's worth noting that instances of mislabeling have occurred. If your CPU's firmware is outdated, you may encounter compatibility issues with your current version of PME (Project Management Environment). To verify any potential incompatibilities, refer to the "Important Product Information" section in the PME help documentation. Additionally, if possible, please share a screenshot of the fault table and a backup of your project file. I would be happy to review them for any anomalies or issues.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.