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 Control Standard M

Overview of application metrics for determining the appropriate license:

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

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.

Demobetrieb

Eine Steuerung ohne Lizenz läuft im Demobetrieb 2 Stunden. Danach beendet sich das Laufzeitsystem und muss neu gestartet werden. Funktional ist der Demobetrieb nicht eingeschränkt. Nicht lizenzierte Funktionen haben eine kürzere Demo-Laufzeit (z. B. Feldbusse laufen 30 Minuten).

Lizenzprüfung

Ist eine applikationsbasierte Lizenz auf der Steuerung verfügbar, werden alle Kriterien gegen das in der Lizenz hinterlegte Limit geprüft. Überschreitet ein Kriterium das definierte Limit, wird ein Download der Applikation bzw. das Laden der Bootapplikation verhindert. Es erfolgt kein Wechsel in den Demomodus.

Damit wird verhindert, dass Applikationen im Produktivbetrieb in einen zeitlich begrenzten Demomodus zurückfallen.

Upgrade-Lizenzen

Für jede Performanceklasse (Runtime, Visualisierung, OPC UA, Motion) gibt es Upgrade-Lizenzen, die einen Wechsel von einer kleineren Lizenz zu einer beliebig höheren Lizenz ermöglichen. Ein Wechsel von einer größeren Lizenz zu einer kleineren Lizenz wird nicht unterstützt.

Einschränkung mit weiteren Store Produkten

Applikationsbasierte Produkte können mit bestehenden Lizenzen kombiniert werden, außer dies wird explizit beim Produkt ausgeschlossen. Die E-A-Kanäle von hinzugekauften Feldbussen werden bei der Lizenzmetrik E-A-Kanäle berücksichtigt und ebenfalls gezählt.

How do I find the right license?

Answer the following questions to find the right runtime system license for your application.

1. Which fieldbus is needed? How many fieldbus instances?

2. How many input and output channels are needed in the application?

3. Do you plan to implement additional functions and logics?

4. 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.

Requirements