the development was a lack of freeware for PLC
source code editing and the bad interoperability
between the PLC IDEs. The development has started
in 2005 with a simple notepad which was able to
edit Moeller Sucosoft .poe files. As a next step a
basic compatibility to Siemens STEP 7 and 3S's
CoDeSys was implemented. During the last years
PLCEdit got some great improvements, e.g. the batch
converter includig a function block call model
transformation and the function block call dialog.
Starting in the mid of 2007 the codebase of PLCEdit was rewritten by using the open source edition of QtSoftware's (Nokia/Trolltech) application framework Qt4. As a result PLCEdit is the first cross-platform POU editor with basic IEC61131-3 compatibility which opens up the way for PLC engineering out of Windows.
If you work with only one PLC manufacturer/IDE and if no external files in use, you will not need this millionth text editor. Everything what PLCEdit can do is open some POU files, edit them slightly and store them back into a compatible format - it is not an IDE. PLCEdit is an easy to use notepad which starts up simply, without any deamons or background Apps and it will not bend your Windows registry.
This small App allows you to view, edit, create and to print POU files. But PLCEdit can be more for you. The program includes a batch converter to prepare exisiting POUs for another PLC platform. And which IDE allows a good source code and version management? Maybe you have a folder based version management which contains the function blocks as single files. In this case PLCEdit can be used as a reader which is able to save file paths as a session. You can increase your version management with sessions of a POU's development line.