I encountered a CPU fault on a 5/01 processor, causing a loss of program and communication failure. I promptly replaced it with a 5/03 processor from our inventory and obtained a program copy from the original equipment manufacturer (OEM) via email. The downloaded program appears to function correctly, except for output O:4/0. Another output, possibly O:4/1, is activating instead. I can manually trigger the output, but readdressing it in the rung has not resolved the issue. Could this be related to data table resizing when switching from a 5/01 to a 5/03 processor?
Download PDF Program
The 5/03 scan outperforms the 5/01 in terms of speed. If your O:4/0 is only active for one scan (B3:0/11 has an OSR), the counter Reset pulse might be too brief for it to register. Consider including a timer specifically for the O:4/0 output in Rung 47 to ensure proper functionality. Avoid extending the duration of B3:0/11 itself.
Thank you for responding. I plan to incorporate a timer into the project tomorrow and will provide an update afterwards.
It definitely sounds like the issue could be linked to the differences in data table sizes between the 5/01 and 5/03 processors. The 5/03 has a bigger memory capacity, which might be causing some mappings to shift or change if the program wasn't fully compatible. When you replaced the processor, check the I/O configuration to ensure everything aligns correctly. It could also be worth looking into the original program for any specific addressing conventions that might not carry over seamlessly. Sometimes, re-evaluating how outputs are mapped after a processor swap helps clarify these discrepancies!
It sounds like you’re dealing with classic addressing issues that can arise when moving between processor models. The 5/03 does have different memory and data structures than the 5/01, so it’s possible that when the program was transferred, the output addressing got misaligned or the data tables shifted. It might help to check the output configuration to ensure that every I/O point is mapped correctly, and also double-check if any other instructions related to that output were modified or overlooked during the migration. Additionally, looking into the hardware configuration and confirming that the output modules are set up correctly in the logic could provide some clues. Don’t forget to confirm any differences in inherent processor capabilities too!
✅ 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: This could be due to a data table resizing issue when switching processors, causing the outputs to be reassigned incorrectly.
Answer: Answer: You can manually trigger the output and check the program logic to ensure the correct addressing is used in the rung. Additionally, consider if data table resizing is affecting the output assignments.
Answer: Answer: Output activation issues, such as the incorrect activation of O:4/1 instead of O:4/0, can occur when switching processors due to potential differences in data table sizing and addressing.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.