We often must design for the lowest common denominator.
The program I wrote for this system is actually quite outstanding. I'm just dropping in the fluffy parts and removing programmers stuff.
We often must design for the lowest common denominator.
Yea, thats handy.
I wish RA had one like that, basically a NOTE instruction just to bring a value to the surface where you need it.
I agree it would be nice to be able to show data values in the rung comments, sort of like a mini HMI in the middle of the ladder logic. The software lets you save watch lists, imagine being able to embed a watch list in a rung comment.
Who am I, the Oracle at Delphi?I'm just waiting on Dr.BitBoy to chime...
Who am I, the Oracle at Delphi?
Anyway, I think it's a neat hack. MOV would work, as would any compare instruction, or a CLR with an XIO/XIC pair on some bit at the front of the rung.
But IsNAN minimizes the vertical and horizontal screen real estate used up.
A MOV instruction with the same variable for both the source and destination should do the same thing.
me2! LOL!I forgot to put in LOL. LOL!
well done!Anyway, I just wanted to find the most benevolent, single item instruction I could find, that doesn't really do anything, but hold the tag for display in logic. That way, no need for 2 part items where you have to create new tags.
I agree it would be nice to be able to show data values in the rung comments, sort of like a mini HMI in the middle of the ladder logic. The software lets you save watch lists, imagine being able to embed a "watch list" in a rung comment.