RussB said:
It is designed for those who know how to type, maybe not so good for mousers.
Get to know the mnemonics and type away, need only to stop and sip your coffee between breaths. This includes the expansion of rungs and columns.
But the mistake GE is making is ignoring the fact that another generation of programmers is out there who grew up using a mouse. Don't get me wrong, people who are true programmers will use the all the keyboard commands at their disposal and become expert at the mnemonics however not all PLC programmers are programmers at heart (what maintenance tech is going to remember it all??) and will rely on the mouse/keyboard combo more often than just keyboard strokes. At least with AB you can pretty much use both methods efficiently. Double-clicking an instruction to configure it is pretty quick. Compare an MSG instruction from AB and an Comm_Req instruction of GE. The Comm_Req configuration is not intuitive at all to program (Maybe that is a poor comparison, as I mentioned before it's been a few years for me).
Is the ladder editor still limited to 10 columns(I think that is what it was)? In this age of wide-screen high resolution monitors it has to be as much of a hassle as working on an InTouch application with a low-resolution.
Again, I think it's all built on the original MS-DOS based software and they are at a brick wall. An over-haul means you probably lose that nice ability to port old projects to the new software. No doubt people will be upset when that happens.
NetNathan said:
I will admit that ME has its faults and as far as Windows software AB has the edge.
But as far as PLC structure.....AB is horrific to me. To much file structure. N, F, B.....and so on.
It is a lot easier to understand that an "M" bit is a memory bit....but "B"? Plus in GE you can force anything including memory bits.
An " R " is far easier to understand as a register bit than N or F.
Sequentially numbering of bits in GE PLCs is far easier to follow than using decimal with all the backslashes and colons.
I disagree. You have to use a % as a prefix for everything. %Q = Outputs? Only makes sense because an O and 0 would be harder to decrypt visually..%O00001 versus %Q00001. At least with AB the structure has obvious meaning:
B = Bits
I = Input
N = iNteger
F = Float
T = Timer
C = Counter
O = Output
How do you organize %R memory locations when they can be used for INTS, DINTS, REALS, TIMERS, COUNTERS? Especially when you consider that it all depends on what you use it for as it may require 1, 2 or 3 sequential registers? If you fudge up, you can easily overlap. Compare a timer instruction, AB by default has .Preset, .Accumulated, .Timer-Timing Bit, .Done Bit, .Enable bit (and its obvious!) for GE you have 3 Registers, and you have to remember the order to know which is the preset and which is the accumulated then you need to manually program equivalent TT, DN and EN bits (if you need them) and assign a completely unrelated %M bit to each.
Comparing memory schemes "now" is pretty much a wast of time as everything is moving towards a tag-based system, it doesn't matter. I left the GE world right as the RX systems where making headway, and I believe they added a tag-based system for those processors but I'm not that familiar with it. IIRC it was more of an "alias" system as the %M, %R, %I, %Q...memory structure still technically existed?
Anyway, having to organize your memory based on any structure is 10yrs in the past. Now-a-days make whatever structure you can imagine.
EDIT: I will say, I always like the overall programming environment of Proficy, just cringed when I had to use the ladder editor.