Description
The new application-based licenses are completely independent of the hardware used and can be used across products. This offers maximum flexibility when choosing your device. Another advantage is the scaling of licenses via application metrics. This means you only pay for as much CODESYS as you use.
A license! From small embedded devices to large IPC solutions, always a perfect fit!
License Control Basic L
Overview of application metrics for determining the appropriate license:
| Characteristic | Basic M | Basic L | Standard S |
| EtherCAT/Profinet/EthernetIP | no | no | 1 instance |
| CANopen/Profibus/Modbus/J1939 | 2 instances | 2 instances | 4 instances |
| Number of input/output channels | 128 | 256 | 512 |
| Code size | 1MB | 3MB | 3MB |
| Visualization | Visu S | Visu S | Visu S |
| communication | Communication S | Communication p | Communication p |
| DataSource Manager | Yes | Yes | Yes |
| Reloadable C code | No | No | Yes |
| Core assignment of IEC task groups | No | No | No |
Further information on the performance classes and license metrics can be found in the document “CODESYS Control Application Based Licenses_de” linked below.
Additional products for the license
CODESYS OPC ETC
CODESYS Visualization
Description of properties
A detailed description of the properties listed above can be found in the “CODESYS Control Application-Based Licenses” data sheet.
Demo operation
A control without a license runs for 2 hours in demo mode. The runtime system then shuts down and must be restarted. The demo operation is not functionally restricted. Unlicensed functions have a shorter demo runtime (e.g. fieldbuses run for 30 minutes).
License check
If an application-based license is available on the controller, all criteria are checked against the limit stored in the license. If a criterion exceeds the defined limit, downloading the application or loading the boot application is prevented. There is no switch to demo mode.
This prevents applications from falling back into a time-limited demo mode during productive operation.
Upgrade licenses
There are upgrade licenses for each performance class (runtime, visualization, communication, motion) that allow you to change from a smaller license to an arbitrarily higher license. Changing from a larger license to a smaller license is not supported.
Restriction with other store products
Application-based products can be combined with existing licenses, unless this is explicitly excluded for the product. The EA channels of purchased fieldbuses are taken into account in the EA 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 required? How many fieldbus masters?
- How many input and output channels are required in the application?
- Are you planning to implement additional functions and logic?
- Would you like to assign tasks or task groups to specific cores in order to achieve higher performance or optimized real-time behavior?
Case study 1: Porting an existing application
The control of an existing system is to be modernized. Over the years, our own libraries have been developed, which will also be used on the new control system. The system’s sensors and actuators are connected via two CANopen masters, but EtherCAT will be used in future models. In total, the system has around 200 digital IO signals
- 2 CANopen masters: at least Basic M license
- Option: EtherCAT master: at least License Standard S
- 200 EA channels: at least Basic L license
- Additional libraries are used: 3 MB of code from the Basic L license enables a lot of additional logic.
- Real-time behavior: In the range of 4-10 ms
-> The CODESYS Control Basic L license is required per device. -> Option with EtherCAT Master: The CODESYS Control Standard S license 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 using MQTT should be implemented. The machine has around 800 EA signals. Since the controller has to command simple drives, the real-time behavior of the bus task is very important. In addition, an existing C code library is to be connected and a small web visualization is to be developed for commissioning.
- EtherCat master: at least License Standard S
- 800 EA channels: at least License Standard M
- Additional logic for connecting to the cloud: 5 MB code from the Standard M license enables 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 is required
-> The licenses CODESYS Control Standard L and CODESYS IIoT Libraries SL are required per device
Case study 3: Higher-level control with Profinet
A control monitors a production line in a plant. The application is intended to collect and process the data via a Profinet network and control the individual system parts. In addition, an HMI based on web technology is required to maintain the system. Finally, production data must be transferred via MQTT for overlaid data analysis.
- Profinet Master: at least License Standard S
- 1,500 EA channels: at least License Standard L
- A lot of logic due to the diverse monitoring and cloud connection: 6 MB code of the Standard L license enables very large applications
- HMI for maintenance: At least CODESYS Visualization M
- Use of MQTT: CODESYS IIoT Libraries SL license is required.
-> The licenses CODESYS Control Standard L, CODESYS Visualization M and the CODESYS IIoT Libraries SL are required per device.
Case study 4: Application with 2D portal and a four-axis SCARA robot
A controller is supposed to control a 2D portal and a SCARA robot with 4 axes via EtherCAT, as well as two additional drives for a conveyor belt and a rotary table. No further functions are planned
- EtherCAT Master: at least License Standard S
- 200 EA channels: Standard S license is sufficient
- Predominant use of CODESYS libraries whose code size is not taken into account in the licensing: 3MB code from the Standard S license is sufficient.
- Increased real-time requirement: at least Standard L to use the multi-core functionality
- Control of 8 axes in total: SoftMotion Axis (8) license for 8 axes
- Control of the 2D portal and the SCARA robot: SoftMotion Axis Groups/CNC Interpolators (2) for 2 axis groups
-> Licenses CODESYS Control Standard L, CODESYS SoftMotion Axis (8) and CODESYS SoftMotion Axis Groups/CNC Interpolators (2) are required.
Requirements
Programming system | CODESYS Development System V3.5.19.10 or higher |
Runtime system | Control SL V4.9.0.0 or higher (includes runtime system V3.5.19.10) |
Supported platforms/devices |
|
Runtime system updates | This product also includes a three-year update authorization for the runtime system. The three years begin from the activation of the runtime system license. The update authorization can optionally be extended at any time. |
Additional requirements | /- |
restrictions |
|
Licensing | Single device license: The license can be used on the controller on which the CODESYS runtime system is installed. The license activation takes place on a software-based license container (soft container) that is firmly tied to the controller. Alternatively, the license can be stored on a CODESYS key (USB dongle). By changing the CODESYS key, the license can be used on another controller. Note: Without a license, the software runs in demo mode for two hours. A manual restart is then required. |
Required accessories | Optional CmStick from version 3-xxxxxxx (version 2-xxxxxxx is no longer supported) |
