CODESYS® Licensing

License container

Depending on the product or product category, different license conditions and procedures apply. 
Licenses are stored in one of the two license containers, depending on the product:

Hardware dongle

The USB dongle is called CODESYS Key and contains up to 4,000 licenses. At the same time, the CODESYS Key serves as encryption hardware for numerous security tasks.

 

Software license container

This storage for licenses is set up along with the initial installation of CODESYS on the desired device (e.g. workstation PC or control hardware) and remains bound to it thereafter.

To help you decide which license container is right for you, see here.

 

Engineering

The CODESYS Development System is free of charge. The only requirement for installation is acceptance of the End User License Agreement. A license is required for add-on products from the CODESYS Store that extend the CODESYS Development System, such as CODESYS Git. Each product lists its license terms in the Store.

Add-on Products for the CODESYS Development System

Workstation License

Classification: For add-ons on a fixed workstation PC

  • The license is stored either in the PC’s software license container or on the CODESYS Key.
  • Depending on the product, it is either permanent or a subscription for a specific period, as is the case with the products in the CODESYS Professional Developer Edition.
  • The License Manager in the CODESYS Development System activates the license.
  • If you use a product on multiple computers, you can store the license on a CODESYS Key and take it with you.

Network License

Note: Currently available exclusively for CODESYS Professional Developer Edition products

  • The licenses are stored on a license server on the local network, and all connected users can use them.
  • The number of licenses determines how many users can work with the products simultaneously.
  • The CODESYS Professional Developer Edition is available as a network license for five users.

Decision-Making Guide:

Those who work alone or at a fixed workstation use workstation licenses.
A team that shares the tools uses a network license: It purchases only as many licenses as there are people working at the same time and installs them at a single location on the network.

Runtime Systems

Soft PLC systems and add-on products for CODESYS-compatible devices

Anyone who licenses a CODESYS Control SL soft PLC from the CODESYS Store makes two decisions. The application-based license determines how much the controller is allowed to execute. The activation method determines where the license is located: as a single-device license on the controller itself or, in the case of generic runtime systems, as a network license on a license server. The license level is the same for both methods.

Application-Based License

Application-based licenses are the licenses offered by the CODESYS Store for the CODESYS Control SL soft PLC systems. The license is based on the scope of the application, not on the hardware: The same license allows an application to run on an industrial PC running Windows or on an edge device running Linux, and it applies to all CODESYS Control SL products. Application-based licenses are available for all CODESYS Control SL platforms starting with version 4.9.0.0 and for the CODESYS Development System starting with CODESYS V3.5 SP19 Patch 1.

The scope is determined by metrics such as the number of I/O channels, fieldbus networks, and visualized variables, as well as options like SoftMotion. After compilation, the CODESYS Development System displays the project’s metrics and the licenses required by the application. During the download, the runtime system checks whether the installed license covers these metrics and, if not, rejects the download. Without a license, a controller runs for two hours in demo mode and then stops; for continuous operation, it requires a license that matches the application.

The tiers build on one another, ranging from CODESYS Control Basic to Standard to Performance, supplemented by licenses for visualization, communication, SoftMotion, and safety. Tiers and prices are listed in the CODESYS Store.

Single-Device License

Classification: for a controller that operates independently, such as an embedded controller in a machine

  • The license is stored either in the software license container or on the CODESYS Key directly on the target device.
  • A license is valid for exactly one controller.
  • The software license container remains tied to the controller; a license on the CODESYS Key can be used on another controller by moving it there.
  • The controller does not need to be connected to another system to remain licensed.

Network License

Application: For generic runtime systems such as CODESYS Control for Linux SL and CODESYS Virtual Control SL, when many controllers are managed from a single location—for example, virtual controllers or a system with many software PLCs

  • The licenses are stored on a license server, and the controllers retrieve their licenses from there.
  • The number of licenses on the server determines how many controllers it can support simultaneously.
  • The license server runs on the local network or on the same device as the controllers, under Windows or Linux. On Linux, CODESYS LicenseServer for Linux SL sets it up.
  • The controller locates one or more license servers via its configuration file; for CODESYS Virtual Control SL, they are specified in the instance settings within the CODESYS Control SL Deploy Tool.
  • CODESYS Virtual Control SL obtains its license exclusively in this manner.
  • Device-specific runtime systems such as CODESYS Control for Raspberry Pi SL or the runtime systems for PFC controllers do not obtain a license from the license server; their license is stored on the device.

Decision-Making Guide:

The single-device license is tied to the device and does not depend on any network. The network license is located at a single point on the network; it can be dynamically assigned and maintained redundantly. However, the controllers depend on the license server: If the server fails or the network is disrupted, all connected controllers may lose their licenses without a redundant license server.

Upgrades and Updates for Application-Based Licenses

If an application outgrows its license—for example, by adding another fieldbus—an upgrade license elevates the application-based license to a higher tier. When purchasing an upgrade, you specify the license already installed on the device in the CODESYS Store; the store will fully credit the price of that license, and you’ll only need to pay the difference. After activation, the device will carry only the new license. Upgrades only move you to a higher tier and are available exclusively for application-based licenses.

Every application-based license includes five years of runtime system updates. The five-year period begins with the activation of the license, not with the purchase. The runtime system can be updated at any time to any version released within this maintenance period, even after it has ended. An upgrade does not affect the maintenance period.

After the maintenance period expires, all licensed runtime systems and features remain fully functional; the machine continues to run without any time limit. Only an update to a version released after the expiration date requires a license renewal.

CODESYS-compatible devices from device manufacturers

If you purchase a CODESYS-compatible device from a device manufacturer, the required licenses are usually already included on the device. No additional licenses are required to use the device, unless the device manufacturer specifies otherwise.

If the device supports the licensing of additional functions, the licenses for these are available in the CODESYS Store. Depending on how the device manufacturer has configured the device, these licenses are either stored in the software license container on the device or on a CODESYS Key inserted into the device. The device manufacturer determines which functions can be licensed separately.

Licensing Tools

A license from the CODESYS Store can be added to your license container in three ways: directly upon purchase in the CODESYS Store, at any time in the CODESYS Development System, or at any time via the License Central web interface at license.codesys.com. Which tool is appropriate depends on the product, the controller’s operating system, the type of license, and whether the license is used on a workstation or a controller.

License Manager in the CODESYS Development System

It activates licenses on a controller, workstation, or license server and generates license requests for offline activation. It is the preferred tool for runtime systems.

CodeMeter License Central WebDepot at license.codesys.com

It transfers licenses to the software license container on the user's computer or to an inserted CODESYS Key, even offline via a license file. The License Manager licenses a controller; WebDepot does not.

CODESYS Mass Licenser

It licenses any number of controllers with the same licensing requirements via a configuration file—for example, in automated production environments. The tool runs on Windows.

CODESYS Automation Server

He imports licenses and activates them on the connected controllers.

CODESYS LicenseServer for Linux SL

He is setting up a license server on Linux where application-based licenses can be activated via a browser, both online and offline.

CodeMeter WebAdmin

It sets up a local license server, helps with troubleshooting, and displays license information.

Internet access is required for activation. If the target device does not have Internet access, the activation process is divided into several steps: The License Manager sends a license request; WebDepot uses this request to generate a license update on a computer with Internet access; and the update is then sent back to the target device. The license server running on Linux offers the same process.

Licensing via software license container or CODESYS Key? A decision aid for you.