Introduction:
Thank you for considering Weintek’s built-in Codesys for your next application. This post contains information related to Weintek’s implementation of Codesys and a list of common questions and answers. If you are new to Weintek’s Codesys, please ensure that you have read this post thoroughly.
Why Codesys?
Codesys is an exceptional PLC IDE that is the framework of many PLC IDEs on the market. If you have used Schneider, Bechoff, or Wago’s PLC software you will find the Codesys IDE to be quite familiar. In addition, the control logic complies with IEC 61131-3 which means that you can use ladder logic, function-block diagrams, sequential function charts, instruction lists, or structured text within your application.
Where can I download Codesys?
To provide the best experience for our customers, Weintek’s R&D has validated CODESYS IDE v3.5.15.50 and related drivers extensively to ensure consistent functionality. We only recommend using versions validated by Weintek’s R&D with Weintek’s CODESYS equipped HMIs or the cMT-CTRL-01. To download the recommended version of CODESYS free-of-charge, please click the link below:
When finished, please review this short tutorial to help you create your first Codesys application: Link
Can I remove Weintek’s Codesys after activation?
No, once activated the built-in CODESYS cannot be deactivated.
Can I create my Codesys project within EasyBuilder Pro?
No, you will need to use the Codesys IDE (see above) to create your Codeys project. The HMI can be programmed for visualization using EasyBuilder Pro.
How do I connect to Weintek’s Codesys?
Codesys has complete control over LAN-1, please make sure that your PC is connected to LAN-1 or that you have “Codesys Login” enabled on the HMI. While “Codesys Login” is enabled, you can connect to the HMI and Codesys using LAN-2. To enable Codesys Login, please read this post:How to enable Codesys login
Once finished specify the HMI’s LAN 2 IP within the “Device” communication setting in your Codesys project:
What protocols does Weintek’s Codesys support?
Currently Weintek’s built-in Codesys supports the following protocols:
- Modbus TCP/IP (master)
- EtherCAT (master)
- CANopen (master)
Prerequisite: CANopen is only available on Weintek CMT-X HMIs that are equipped with a CANBus port. - EtherNet/IP (master)
Can Weintek’s Codesys communicate with a 3rd party device?
Certainly! You may use any of the protocols mentioned above to communicate with an external device of your choice.
What communication drivers should I use within Codesys?
We recommend that you use device drivers included with Weintek’s Codesys package:
Device | Version |
---|---|
CANbus | 3.5.15.0 |
CANopen manager | 3.5.15.0 |
Ethernet adapter | 3.5.15.0 |
Ethernet IP Scanner | 3.5.15.50 |
Modbus TCP master | 3.5.15.0 |
EtherCAT master | 3.5.12.0 |
Note: You may need to select “Display all versions” within the “Add Device” dialog to select the appropriate driver. For more information, please read this post: How to update device drivers
How many devices can Weintek’s Codesys communicate with?
- Modbus TCP/IP: 32 devices
- EtherCAT: 65,535 devices
- CANopen: 126 devices
- EtherNet/IP: 32 devices
What features cannot be used with Weintek’s Codesys runtime?
- OPC UA features
- Network Variable List
- Alarm Configuration
- Redundancy Configuration
- CODESYS TargetVisu
- CODESYS WebVisu
- CODESYS HMI
- SoftMotion
- CODESYS IIoT Libraries SL
- CODESYS OPC UA Client SL
- CODESYS OPC UA Server SL
- CODESYS Safety for EtherCAT Safety Module SL
- Other add-ons
Trying to install other licenses from the CODESYS website will not work.
What libraries does Weintek’s Codesys support?
Weintek’s built-in Codesys is compatible with wide range of built-in libraries. However, certain libraries that require OS support are not compatible with the device runtime.
The libraries within the table below are compatible with Weintek’s built-in Codesys. Libraries that do not require OS support are also compatible with Weintek’s built-in Codesys.; e.g. OSCAT Basic, Util library…etc.
Sys Library | Cmp Library | CAA Library |
---|---|---|
SysTimeRtc | CmpTraceMgr | CAAType |
SysTimer | CmpSrv | CAATick |
SysTime | CmpSettings | CAATickUtil |
SysTask | CmpSchedule | CAAStorage |
SysTarget | CmpRouter | |
SysSocket | CmpPlcShell | |
SysMem | CmpLog | |
SysFile | CmpIoMgr | |
SysExcept | CmpIoDrvC | |
SysEvent | CmpIecVarAccess | |
SysEthernet | CmpIecTask | |
SysDir | CmpEventMgr | |
SysCpuHandling | CmpDynamicText | |
SysCom | CmpCheckSum | |
CmpChannelServer | ||
CmpBinTagUtilIec | ||
CmpAsyncMgr | ||
CmpAppBP |
How fast is Weintek’s Codesys?
Here are some base level measurements for comparison:
How much memory can be used in a Weintek’s Codesys project?
Here are the specs for reference:
Data, Input, Output, Memory, Code | 3 MB | |
Retain area (Data persists after reboots) |
16 KB (Data is saved every 1 minute) |
|
Persistent area (Data persists after downloads) |
16 KB (Data is saved every 1 minute) |
|
File system | 8 MB |
Note: 3MB for “Data, Input, Output, Memory, Code” is the max. size of a Weintek’s Codesys project (a file which is compiled by Codesys IDE and loaded into Weintek’s Codesys runtime). If the file size exceeds the capacity listed above, the following error message will display during compilation: “[ERROR] Out of code memory…No download possible”
Note: CODESYS firmware v20240703 have increased storage and memory space.
Note: When using CODESYS firmware is v20240703, please use CODESYS & Remote IO Package” 1.5.3.500 or later.
Data, Input, Output, Memory, Code | 5 MB | |
Retain area (Data persists after reboots) |
32 KB (Data is saved every 1 minute) |
|
Persistent area (Data persists after downloads) |
32 KB (Data is saved every 1 minute) |
|
File system | 12 MB |