I am currently facing an issue with the logic in a 90-30 PLC (364 CPU). Despite having three Machine Edition backups with different names, all showing Config=NE and logic=NE on Connect, I have tried uploading the logic without any errors. However, the issue still persists as Config=NE and logic=NE. I have checked the validation, which appears to be clean. I may need to consider stopping the CPU to resolve the Config error, but the logic issue is still puzzling me. I am running ME 10.2, and it seems that the older backups were from a previous version of ME. It may be necessary to download the Config in order to clear the error, but the logic problem continues to be a concern. Are there any other suggestions or ideas on how to address this issue effectively?
In case the PLC program was developed using a different version of the programming software than the one installed on the connected PC, it will be necessary to download in order to synchronize logic or configuration settings. Before proceeding with the download, you can generate a comparison report in the programming software to ensure that both versions match. This report will highlight any discrepancies between the version on the PC and the one in the PLC, providing peace of mind before making any changes.
I agree with you on that, but I'm just puzzled as to why it didn't display "Logic equals" as expected. Can you help me understand why?
This seems to be a challenging scenario. Have you considered checking for firmware compatibility between the current and older version of Machine Edition? Sometimes, differences in firmware versions can cause issues. If possible, take a look at whether the problem is a result of specific blocks of logic, or whether it's more widespread. As a last resort, if it's feasible, you may also consider transferring the logic line by line to a new, clean program. This is a tedious process, but it could help identify if there is a small, specific portion causing it to read as NE.
It sounds like you're dealing with a pretty frustrating situation! Since you've already validated the logic and checked the connection, one approach you might consider is to completely power cycle the PLC after stopping it; sometimes that can help clear out lingering configurations that don’t reset even after uploads. If the backups are from older versions, it could cause compatibility issues, so you might want to try re-creating the config in your current version of ME if possible. Also, ensure all modules are properly seated and check for any firmware updates that might improve stability. Good luck, and I hope you find a resolution 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: Answer: The Config=NE and logic=NE errors on a 90-30 PLC could be due to discrepancies in the software version used for backups and the current version in use. It is recommended to ensure compatibility between the backups and the current Machine Edition version.
Answer: Answer: To resolve the Config=NE error, you may need to consider stopping the CPU and then attempting to upload the configuration again. This process can help in clearing the error related to configuration.
Answer: Answer: If uploading the logic without errors did not resolve the logic=NE problem on the 90-30 PLC, you may need to download the Config to clear the error. Additionally, ensure that the validation is clean and consider checking for any potential issues in the logic programming.
Answer: Answer: It is advisable to verify the compatibility of backups with the current Machine Edition version, ensure a clean validation, and review the logic programming for any potential issues. Seeking assistance from technical support or referring to the user manual for troubleshooting guidance may
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.