The Plc Kid
Member
Guy's
In the past primarily on slc systems I would use rung comments on almost every rung of my program and go into great detail about what the rung did and why. It makes it much easier for the maintenance guys here to troubleshoot things that way.
Today I am trying to put some documentation into a RSL5K program that has nothing. Literally.
In slc when I did a rung comment I would tie it to an address vs. a rung because if rungs were added via online edits or whatever the case may be then you documentation had the tendency to get messed up. I always created dummy bits called document bits and would install them as an OTE with that logic so if rungs were added it would stay together.
I have been looking in logix 5000 all morning and see no way to do this? Am I missing something? Any other techniques or ideas?
In the past primarily on slc systems I would use rung comments on almost every rung of my program and go into great detail about what the rung did and why. It makes it much easier for the maintenance guys here to troubleshoot things that way.
Today I am trying to put some documentation into a RSL5K program that has nothing. Literally.
In slc when I did a rung comment I would tie it to an address vs. a rung because if rungs were added via online edits or whatever the case may be then you documentation had the tendency to get messed up. I always created dummy bits called document bits and would install them as an OTE with that logic so if rungs were added it would stay together.
I have been looking in logix 5000 all morning and see no way to do this? Am I missing something? Any other techniques or ideas?