OkiePC
Lifetime Supporting Member
I personally love the 500 environment, but most of that is because I've worked with it enough to know (a lot of) the quirks. It's definitely a little dated, but there's not much you can't do with it if you know how, and it's decently user-friendly as well.
Me too. I am tempted to make a video showing me with RSLogix 500 editor open, 4 different data tables open, two of them of the same file with different radix displays, two trends running, while I am dragging and dropping addresses from one of the data views onto a ladder editor. I will title the video "Show me how to do this in Studio 5000. I'll wait."
And another video where I open a lengthy telemetry master program and search and replace "N10:5/*" with "Well_16/*" and it works just fine because "Well_16" is a symbol that is already defined. "Show me how to use find and replace for tag addresses with wildcards in Studio 5000. I'll wait."
I could go on and on.
I would probably like Studio 5k more if I didn't frequently run into stupid applications of the power it gives these fools writing code for it. Just yesterday, I had to spend an hour trying to figure out how to correct the PLC clock on a Compactlogix because some fool decided he would write a nice and neat AOI called "PLCClock" to wrapper what amounts to 5 rungs of normal logic. Except his code was broken and I could not edit it live. I had to add a new SSV instruction in the MAIN to fix the time and date and leave his broken code alone, because we can't just go shut down a wastewater plant because some wise guy thinks AOIs FTW. Writing AOIs that aren't perfect turns that L83E into a Micrologix 1200. Whad'ya mean I gotta shut 'er down? To change the time?
I could go on and on about this subject too, but it is Friday so I am going to go back to barking about all the reasons you should smack your panelview minus with a hammer and replace it with a red lion.
:site:
Last edited: