Hi Chandru,
Why blame Allen Bradley alone? at least their software is simple to learn and their communication drivers and protocols are robust. For exmple, to people unfamiliar with this art, it is intimidating use the Uni-Telway drivers of Modicon-Telemecanique and they are not very cheap either.There, are in addition, many hardware and software versions, which are not always compatible. Also changes in the Windows OS versions, often render software which you pay for, useless without warning!. Other kinds of problems are found with versions of HMI, its software and also cables, especially USB cables. However, unravelling these version conflicts, unpleasant as they may seem, do provide me a certain portion of livelihood.
I work for a Schneider system house and I've seen a lot of these issues. Ideally, we should all be using a high level language editor common to all PLCs but as the processors inside different PLCs are different, It is a long road there. The promise of Java for example as a platform independent programming language was not to live very long a decade ago. Now that Dot Net attempts to do the same thing, at least in the PC world, that hope is still there.
My own view of the future is that PLCs will have all the features of powerful parallel multiprocessor some day and in the near future, we should see much more object orientation in the PLC world as well. As it is web-servers are being built into PLCs and PACs are encroaching on to PLC turf. And thus the day when we can use a universal program editor for all PLCs, may yet come to pass sooner than later.
Regards, best wishes,
Raj S. Iyer