I am working on a 1756-L71S GuardLogix 5570 controller (Ver. 32) where I am having a persistent problem with some of my routines.
A couple of my routines have lots of similar rungs with variations in array index references to work with my recipes.
Here is a snippet of one of the correct rungs. Notice all the indexes are 24. There is another rung with all 26, another with 28, etc.
Now this may not be the most efficient way to do this but it's what I was given to work with. The problem arises when these indexes get randomly changed. I will import the correct routine, save, and then a couple days later check on the PLC and the rungs will look something like this...
Notice how a couple of the indexes got changed to something else, this changes almost all of the rungs in the routine when it happens.
There are multiple people that connect to the line so that could be the issue. I talked to Allen Bradley and they said to save the entire project as an .L5K instead of a .acd but that doesn't seem to stop it, not to mention coordinating everyone that connects to do that is difficult as they are from different companies.
I have tried Source Protection as well and that does nothing to prevent the issue.
Anyone have any ideas about fixing this? or at the very least the root cause?
Thanks
A couple of my routines have lots of similar rungs with variations in array index references to work with my recipes.
Here is a snippet of one of the correct rungs. Notice all the indexes are 24. There is another rung with all 26, another with 28, etc.
Now this may not be the most efficient way to do this but it's what I was given to work with. The problem arises when these indexes get randomly changed. I will import the correct routine, save, and then a couple days later check on the PLC and the rungs will look something like this...
Notice how a couple of the indexes got changed to something else, this changes almost all of the rungs in the routine when it happens.
There are multiple people that connect to the line so that could be the issue. I talked to Allen Bradley and they said to save the entire project as an .L5K instead of a .acd but that doesn't seem to stop it, not to mention coordinating everyone that connects to do that is difficult as they are from different companies.
I have tried Source Protection as well and that does nothing to prevent the issue.
Anyone have any ideas about fixing this? or at the very least the root cause?
Thanks
Last edited: