PLCEdit FAQ

Q: Wich PLC source files can be edited with PLCEdit?
A: You can edit and create clean IEC61131-3 POU files or files, compatible to
    Moeller Sucosoft, CoDeSys export files which contains PRG, FB, F or
    global variable lists, Siemens .awl & .scl and KW-Software IL and ST sources.


Q: Does PLCEdit support FUP and KOP?
A: No, it comes only with support for Instruction List and Structured Text.
    PLCEdit supports FUP and KOP as text listing frome some IDEs.


Q: Does PLCEdit support any Siemens/Simatic/Step7 sources?
A: Yes. PLCEdit can create, edit and open Step7 compilant files.
    To view the proprietary toolbar for Step7 specific commands,
    you need to save a new file as a .awl or .scl source first.


Q: Can I use files from PLCEdit for logiCAD in any way?
A: Yes. The logiCAD IDE offers an import of ST sources as .txt files from PLCEdit
    In logiCAD use the right mouse button on a library and choose Export/Import
    to start a ST import.


Q: The Moeller Sucosoft shows an error during register .poe files.
A: The KM-header of the .poe files is not 100% correct (CRC checksum).
    Simply open the POE in the Editor of the Sucosoft and save the file again.


Q: Does PLCEdit includes a compiler for POU files?
A: No, it is not possible to compile the POU files with PLCEdit.
    You still need the software wich was delivered with the PLC.


Q: Is it possible to upload/download the software from/to a PLC?
A: PLCEdit comes without any functions for connecting to a PLC.


Q: Is it possible to convert opened files in a batch process?
A: Yes. PLCEdit has an easy to use batch saving module.
    Open all files which should be converted to an other PLC IDE format
    Next use the menu File/Batch converting and choose the destination
    and IDE compatibility.


Q: How can I import files written with PLCEdit to other development environments?
A: First save the edited source code in PLCEdit with the rigth file extension, like
    .poe for SucoSoft, .exp for CoDeSys, .awl or .scl for Siemens, .txt as clean POU.
    Then open your developement environment and search for an import menu.
    Some IDEs needs an opened project to allow importing external source code.
    Note, .txt files from PLCEdit can be read by many other PLC development distributions.


Q: How can I export files from my project to PLCEdit?
A: Use the export menu from your development distribution. Often the file it selve
    has a special context menu for this. Then open your exported file by drag & drop
    into PLCEdit. You can also use the open dialog in PLCEdit.


Q: Can I print POU files?
A: Yes, you can print all opened POU files by using the print dialog in the menu File.
    It is possible to set the printable sections in the preferences dialog.


Q: PLCEdit has an english interface. Can I switch the language?
A: Yes, you can choose between the installed languages (English and German)
    by using the preferences dialog in the menu Tools. The languages files are located in
    "PLCEdit-install-directory/Lang". If you are interrested in another language please
    contact the developer by using the contact menu of this website.

Q: Which OS platforms are supported by PLCEdit?
A: PLCEdit code base version V1 was written for Win32 systems only.
    Since version V2.x PLCEdit was developed by using the Qt toolkit from Trolltech,
    which supports many operatings systems. You can download compiled versions for
    Windows, Mac OS X and Linux.


Q: Is a portable version of PLCEdit available?
A: PLCEdit for Windows® comes as an installer package, but the installed folder
    can be copied to any removable drive, because this folder contains all needed data.
    The linux version is already available as a zipped folder and the Mac OS X application
    can also be copied to a removable drive, without loosing any bindings or settings.


Q: PLCEdit's application size grows up on Mac OS X.
A: PLCEdit on Mac OS X stores its preferences and all session files into its
    own application package. This is possible because Mac OS apps uses a
    Folder which contains the binary application file and other recources.
    As result PLCEdit can also be used as a portable app on Mac OS X.


Q: Is PLCEdit OpenSource?
A: Versions until v0.9.9 are closed source. With version V2.x PLCEdit is a GPL V2/3
    compliant open source project, using the Qt graphic toolkit from Trolltech.


Q: How much does PLCEdit cost and where can I buy it?
A: PLCEdit is Freeware/opensource and will not be sold here.
    But if you wish to express your appreciation, you can donate for it (see download page).


Q: Where can I get more information or does a PLCEdit forum exist?
A: Sorry, no forum or mailing list. For more information go to the contact menu of this website.