I am currently working on a CJ1 Omron PLC program and need assistance with a specific issue regarding the CIO address 54. This address is being set by a MOV command, which assigns it a particular value. Throughout the rest of the program, this value is compared to other values using the equality operator ( = ) with a reference of 300. However, I’ve noticed that the value assigned to address 54 is fluctuating between the set value and zero. I can confirm that no other part of the program is assigning a value to address 54. Is there a method to trace the origin of this unexpected assignment resulting in a value of zero?
User JuanPLC74 stated: "I'm currently modifying a program on a CJ1 Omron PLC. The CIO address 54 is part of a MOV command that sets its value. Throughout the program, this value is compared to other values using the expression =(300). However, I’ve noticed that this address fluctuates between the assigned value and 0. No other parts of the program appear to be changing the value of address 54. Is there a method to trace the origin of this unwanted assignment to 0? Additionally, I suspect it may be linked to a DeviceNet node; does anyone have insights on how to remove this node from the configuration?"
It sounds like you're dealing with a tricky issue! Since no other part of your program seems to be affecting CIO 54, it could be worth checking for any unintended side effects, such as PLC inputs that might be momentarily triggering a state change, even if they’re not directly referenced in your code. Additionally, consider monitoring the execution sequence closely—using a debugging tool or adding temporary logging could help pinpoint where the value is dropping. Also, ensure that there isn’t any hardware issue or noise affecting the input signal, which might cause random fluctuations. Good luck, and let us know what you find!
It sounds like you're facing a tricky issue with the fluctuating value in CIO address 54. One method to trace the source of this unexpected change is to use the "Watch" function in your programming environment, if it's available. This allows you to monitor the value of CIO address 54 in real-time and could help identify exactly when and possibly why it’s being reset. Additionally, double-checking for any logic conditions, timers, or interrupts that might be inadvertently affecting the value could also reveal hidden interactions. Good luck, and I hope you find the root cause 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.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.