Yes - I have always been an Omron fan. The main reason is software development time - I do not do much planning - just my external I/O. Then I decide on the sections I want eg: urgent alarms, non urgent alarms, communications, fuel control, main control, BMS signals and the like - set them up as sections in the program. Then I put my head down and just write software. It flows. I also have Excel open and copy and paste tags in and out of CX-P - it is just so easy it is not funny. I work for myself and can make or lose good money writing software - the second option is not acceptable of course.
In the old days I would not even use the Omron LSS software as it was rubbish but used to use CAPS from the US.
The first decent Omron software was Syswin and it was very good and quick to use.
Then along came CX-Programmer - wonderful to use.
Over the years I have used Schneider, AB, AD, Hitachi, Square D, Siemens, April, Modicon, Telemecanique, Fuji, Eberle, and probably another dozen or so.
I am not a fan of Siemens or AD - many of the others have vanished. The latest Schneider software is a PITA for mine as well. I just want to be able to write software fast and make a quid at the end of the day. AB is OK but there are way too many memory areas.
I program using I/O numbers and Omron generally have very few memory areas - CIO (common I/O) W (memory bits if you will - internal)DM (data memories or registers - memory retentive)HR (holding relays or memory retentive bits and words)and some system areas and the like.
Most areas in CIO are allocated for special cards, communications cards and the like but I can program all of these to where I want - not an issue.
On a large job I do allocate memory to where I want so I know where it all is.
I also allocate network stuff to where I want for multiple PLCs - have had jobs with over 20 PLCs networked and then a heap of remote I/O off each PLC. Just make myself notes and an Excel spreadsheet - easy.
I find tag based stuff of any kind absolutely painful to be honest - hate it! Too slow - cannot make enough money with it. Takes too long.
It is all relative - came up with a keypad on the front of the controller, then a hand held, EPROM burners - even special printer interface modules.
Then software appeared - WOW! DOS software of course.
the pretty stuff is fine as long as there are programmable key combinations so I can use a keyboard - 74 now - no desire to get RSI dropping and dragging with a mouse - give me a keyboard any day. Still use keyboard shortcuts with Word and Excel.
GOB - grumpy old *******!
No time to fiddle - just want to get on with it.
By the way I programmed the automation of several diesel generator power stations with my theory of the software just flows - one of them was 26 PLCs with a heap of remotes - that was with the old Syswin.
Oh - and all the big ones had a Citect SCADA system as well - Excel copy, modify and paste in and out of the PLC software and the Excel add in for Citect - too easy. Citect still uses dbf files because they are much faster and more efficient than anything since.