The new application-based licenses are completely independent of the hardware used and can be used across all products. They thus offer maximum flexibility in the choice of devices. Another advantage is the scaling of the licenses via metrics of the application. So you only pay for exactly as much CODESYS as you use.
One license! From small embedded devices to large IPC solutions, always a perfect fit!
License CODESYS Control Standard S
Overview of application metrics for determining the appropriate license:
Number I/O channels
OPC UA S
OPC UA S
OPC UA S
Reloadable C code
Multi core in the application
For more information about the performance classes and the license metrics, please refer to the document “CODESYS Control Application Based Licenses_en” linked below.
Additional products to the license
CODESYS OPC UA
CODESYS OPC UA S: OPC UA license for client and server with up to 512 tags
CODESYS OPC UA M: OPC UA license for client and server with up to 4096 tags
CODESYS OPC UA XXL: OPC UA license for client and server with unlimited number of tags
CODESYS Visualization S: License for target and web visualization with up to 128 tags
CODESYS Visualization M: License for target and web visualization with up to 2048 tags
CODESYS Visualization L: License for target and web visualization with up to 4096 tags
CODESYS Visualization XL: License for target and web visualization with up to 8192 tags
CODESYS Visualization XXL: License for target and web visualization with up to unlimited number of tags
CODESYS SoftMotion Axes
Note: All axes must be counted, regardless of whether or not axes within axis groups or CNC interpolators are used.
CODESYS SoftMotion Axes (4): SoftMotion license with up to 4 axes.
CODESYS SoftMotion Axes (8): SoftMotion license with up to 8 axes.
CODESYS SoftMotion Axes (16): SoftMotion license with up to 16 axes.
CODESYS SoftMotion Axes (32): SoftMotion license with up to 32 axes.
CODESYS SoftMotion Axes (48): SoftMotion license with up to 48 axes.
CODESYS SoftMotion Axes (64): SoftMotion license with up to 64 axes.
CODESYS SoftMotion Axis Groups/CNC Interpolators
Note: Axis groups/CNC interpolators do not include axes, these must be purchased separately.
CODESYS Axis groups/CNC interpolators (1): One axis group or CNC interpolator
CODESYS Axis groups/CNC interpolators (2): Two axis groups or two CNC interpolators
CODESYS Axis groups/CNC interpolators (3): Three axis groups or three CNC interpolators
CODESYS Axis groups/CNC interpolators (4): Four axis groups or four CNC interpolators
CODESYS Axis groups/CNC interpolators (5): Five axis groups or five CNC interpolators
CODESYS Axis groups/CNC interpolators (6): Six axis groups or six CNC interpolators
Description of properties
A detailed description of the properties listed above can be found in the “CODESYS Control Application-Based Licenses” data sheet.
A controller without a license runs for 2 hours in trial mode. After that, the runtime system is terminated and must be restarted. Functionally, trial operation is not restricted. Unlicensed functions have a shorter trial runtime (e.g. fieldbuses run for 30 minutes).
If an application-based license is available on the controller, all criteria are checked against the limit specified in the license. If a criterion exceeds the defined limit, a download of the application or the loading of the boot application is prevented. The system does not switch to trial mode.
This prevents live applications from falling back into a time-limited trial mode.
Each performance class (Runtime, Visualization, OPC UA, Motion) offers upgrade licenses that allow switching from a smaller license to any higher license. A change from a larger license to a smaller license is not supported.
Restriction with other store products
Application-based licenses can be combined with other store products, unless explicitly excluded. The I/O channels of additionally purchased fieldbuses are taken into account in the I/O channels license metric and are also counted.
How do I find the right license?
Answer the following questions to find the right runtime system license for your application.
Which fieldbus is needed? How many fieldbus instances?
How many input and output channels are needed in the application?
Do you plan to implement additional functions and logics?
Do you want to assign tasks or task groups to specific cores to achieve higher performance or optimized realtime behavior?
Case study 1: Porting an existing application
The PLC of an existing plant is to be modernized. Over the years, own libraries have been which are also to be used on the new PLC. The sensors and actuators of the plant are connected via two CANopen master instances, but EtherCAT is to be used in future models. In total the plant has about 200 digital E-A signals
2 CANopen master instances: at least license Basic M
Option: EtherCAT Master instance: at least license Standard S
200 E-A channels: at least license Basic L
Additional libraries are used: 3 MB code of license Basic L allow a lot of additional logic.
Real-time behavior: In the range of 4-10 ms
-> License CODESYS Control Basic L is required per device.
-> Option with EtherCAT Master instance: License CODESYS Control Standard S is required per device.
Case study 2: Standard application with EtherCAT
A new application for a machine with EtherCAT is to be developed. In addition a connection to the cloud for data analysis via MQTT is to be implemented. The machine has about 800 E-A signals. Since the PLC has to command simple drives, the real-time behavior of the bus task is very important. Additionally an existing C-code library shall be connected and a small web visualization for commissioning should be developed.
EtherCat instance: at least license standard S
800 E-A channels: at least license standard M
Additional logic to connect to the cloud: 5 MB code of license Standard M allows a very large application.
Separation of the bus task on its own core : at least standard L
Connection C code: Dynamic C code included in Standard L.
MQTT protocol: CODESYS IIoT Libraries SL license required
-> The CODESYS Control Standard L and CODESYS IIoT Libraries SL licenses are required per device.
Case study 3: Supervisor PLC with Profinet
A PLC monitors a production line in a plant. The application is to collect the data via a Profinet network, process it and and control the individual plant components. In addition, an HMI based on web technology is needed to maintain the plant. Lastly, production data must be transmitted via MQTT for higher-level data analysis.
Profinet instance: at least license standard S
1,500 E-A channels: at least license standard L
A lot of logic due to multiple monitoring and cloud connection: 6 MB code of license standard L allow very large applications
HMI for maintenance: at least CODESYS Visualization M
Use of MQTT: CODESYS IIoT Libraries SL license is required.
-> CODESYS Control Standard L, CODESYS Visualization M and CODESYS IIoT Libraries SL licenses are required per device.
Case study 4: Application with 2D portal and a four-axis SCARA robot
A PLC is to control a 2D portal and a SCARA robot with 4 axes via EtherCAT, as well as an additional 2 drives for a conveyor belt and a rotary table. Further functions are not planned.
EtherCAT instance: at least license standard S
200 E-A channels: License Standard S is sufficient
Mainly use of CODESYS libraries whose code size is not taken into account in the licensing: 3MB code of the Standard S licence is sufficient.
Increased real-time requirement: at least Standard L to use multi-core functionality.
Control of 8 axes in total: SoftMotion Axis (8) license for 8 axes
Control of 2D portal and SCARA robot: SoftMotion Axis Groups/CNC Interpolators (2) for 2 axis groups
-> CODESYS Control Standard L, CODESYS SoftMotion Axis (8) and CODESYS SoftMotion Axis Groups/CNC Interpolators (2) licenses are required.
CODESYS Development System Version 188.8.131.52 or higher
Control SL V184.108.40.206 or higher (build on runtime system SDK V220.127.116.11)
Supported Platforms / Devices
Runtime System Updates
This product additionally includes a three-year update authorization of the Runtime System. The three-year period starts with the activation of the Runtime System License. The update authorization can be extended at any time.
Single device license: The license can be used on the target device/PLC on which the CODESYS runtime system is installed.
Licenses are activated on a software-based license container (soft container), which is permanently connected to the controller. Alternatively, the license can be stored on a CODESYS Key (USB dongle). By replugging the CODESYS Key, the license can be used on any other controller.
Note: In demo mode, the software runs for two hours without a license. After that, a manual restart is required.
Optional CODESYS Key Version 3-xxxxxx (version 2-xxxxxx is not supported)
The CODESYS Development System is the IEC 61131-3 programming tool for industrial control and automation technology, available in a 32-bit and a 64-bit version.