Q: Which PLC source files can be edited
A: You can edit and create plain POU files or files compatible to Moeller Sucosoft
most CoDeSys export files which contains PRG, FB, F or global variable lists,
Siemens .awl & .scl and KW-Software IL and ST sources.
Q: What's about FUP and KOP programming languages?
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: Which PLC distributions are known as supported?
A: PLCEdit supports directly:
- CoDeSys v2.3.x files with POUs and GLOBAL_VAR lists, eg.:
- Beckhoff TwinCAT
- Bachmann M-PLC
- frenzel + berg CoDeSys
- Moeller easySoft CoDeSys
- WAGO-I/O-PRO 32
- infoteam OpenPCS .POE & .ST files
- KW-Software .IL & .ST sources
- logiCAD, by using ST language and .txt as output format
- Moeller Sucosoft S40 v4.x & v5.x
- Siemens Step7 .scl & .awl sources
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 select Export/Import
to start an import of the .txt file.
Q: Is it possible to open infoteam OpenPCS .POE and .ST files?
A: Yes. Normally both file extensions are related to Sucosoft S40 andMULTIPROG,
but PLCEdit checks the file content and if no reference to Sucosoft or MULTIPROG
can be found it will open such files as plain POUs. Therefore OpenPCS files with
the extension .POE or .ST are usable with PLCEdit but show as plain POU.
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 it again.
Q: Is it possible to open library files, eg. the oscat community library?
A: Yes, PLCEdit can handle the plain POU file from the oscat community - just drag the
.txt file to the main window. Notice: the file contains a large number of routines and
maybe it looks like PLCEdit is crashed, but it only takes a while to import this large
file. The error message on the end of the open process results from the library block
at the end of the oscat plain POU file - don't worry about it.
Q: Does PLCEdit have 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 all opened files in a batch process?
A: Yes. PLCEdit has an easy to use batch processing module.
Open all files which should be converted to an other PLC IDE format.
Next use the menu File/Batch converting and choose a directory
and the IDE compatibility.
Q: Is it possible to save my current work bench?
A: Yes. PLCEdit offers to ways to save your current work. The first one is the
session manager, which saves links to all open files into a session file.
The preferences contains some more options of the session manager.
Use the batch converter if all current open files should be saved.
The entry "copy only" at the compatibility box works perfect for your needs.
Q: How can I import PLCEdit-written files into other development environments?
A: First save the edited source code in PLCEdit with the correct 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.
Notice: The .txt files from PLCEdit can be read by many 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. 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 change the language or install other languages?
A: Yes, you can choose between the preinstalled languages (EN, DE, FR) by using the
preferences dialog in the menu Tools.
If you are interrested in another language please contact the developer or try it
by yourself with translating the file Wildcard.ts, which is located in the folder
"PLCEdit-install-directory/Lang". All you need is the program Qt Linguist, available
at qt-apps.org. Open the file Wildcard.ts and translate all english default strings into
your language. NOTICE: The context "transl. language" item 'LANG' should contain
your language (default is 'Wildcard'). At least click on the submenu Release As...
at the File menu of Linguist. The output/release .qm file must be named with the same
string as used for 'LANG' to enable PLCEdit reading the new translation file at start up.
Q: Which OS platforms are supported by PLCEdit?
A: Since version V2.x PLCEdit was developed by using the Qt toolkit of QTSoftware/Digia,
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: 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: 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 graphic toolkit of QTSoftware/Nokia.
Q: How can I compile PLCEdit from the sources?
A: PLCEdit is distributed as standalone executable for Windows, Linux and Mac OS X.
If you wish to compile it on your system follow these steps:
0. Prerequisites: Qt Software's Qt 4.x and a compiler distribution.
Linux and Mac OS X contains already a compiler. On Windows systems
you can use the free MinGW collection.
1. Extract the source from the package.
2. `cd` to the directory containing the package's source files and type
`qmake PLCEdit.pro` on Windows and Linux systems or type on Mac OS X
`qmake -spec macx-xcode PLCEdit.pro' to generate the Makefile.
3. Type `make` on Linux and Mac OS X or type `mingw32-make` on Windows
to compile the package. Mac OS users maybe need to open the generated
XCode file and run XCode (if qmake PLCEdit.pro was entered).
(PLCEdit's devlopment IDE is QDevelop.)
4. The executable file 'PLCEdit' is built in the directory 'release/'.
5. On Linux and Windows copy the folders 'Lang' and 'Help' into the folder
release (or PLCEdit's application directory).
On Mac OS X rightclick on the application file in the folder release,
select "show package content", open the folder Contents, next open the
folder MacOS and put in the folders 'Lang' and 'Help'.
NOTICE: If PLCEdit cannot found this folders in its application directory
you will miss the translations and the help.
6. PLCEdit uses also a folder Sessions, which will be created at start up,
if it does not exist. If you have already used PLCEdit and the session
function repeat the copy procedure from paragraph 5. for the sessions).
Q: Where can I get more information about PLCEdit or is it possible to collaborate?
A: If the Help and FAQ pages are not sufficient or if you are interested to collaborate
on the project, please use the contact site. For discussions about PLCEdit you can
subscribe to the mailing list by open the link:
Q: Is PLCEdit certificated by the IEC-61131 or PLCopen community?
A: No. The software was only written to be compliant to the standards and is not exhaustive!
The persons behind PLCEdit are not a member of the IEC-61131 or PLCopen community.
All rights of maybe named trademarks are reserved by its owners.