CODESYS Licensing
CODESYS licensing: which package, and why?
The expensive mistake is not buying a package you do not need — it is coming up short on one you do and stalling the machine at commissioning. This page explains what each item does and how to choose for your machine.
The three questions that decide the licence
These are the first three questions we ask when preparing a quote. Once they are answered, the package list almost writes itself.
- Are the axes locked to each other? If yes, you need the real-time runtime and a motion package; if no, the standard edition will usually do.
- From how many places will the screen be viewed? Only the panel on the machine, or concurrent access for maintenance and production monitoring as well?
- Is this a series product or a one-off? In series production, unit cost and automated activation come first; on a single machine, flexibility is worth more.
Activation: dongle or software container?
There are two methods, and the choice follows how the machine is produced.
| Criterion | Hardware dongle | Software container |
|---|---|---|
| When the device changes | Just move the dongle | Needs reissuing |
| In series production | A physical part to manage | Can be automated |
| Service pool / spare device | Practical | Needs planning |
| Loss or failure risk | Can be physically lost | Backup must be kept |
A starting configuration by machine type
The table below is a starting point for the machines we meet most often. The definitive list follows once axis count and communication needs are settled.
| Machine type | Runtime | Motion | Visualization |
|---|---|---|---|
| Logic-controlled process line | Standard / Linux | Not needed | Panel |
| Synchronised cutting (rotary / flying shear) | Real-time | SoftMotion | Panel + browser |
| CNC router / plasma cutter | Real-time | SoftMotion CNC | Panel |
| Palletising / robot cell | Real-time | Robotics kinematics | Browser |
| Series embedded product | Linux / ARM | As required | Browser |
A licence is not just a purchase line; it is the consequence of an architecture decision. That is why, before quoting, we prefer to talk through the runtime and motion sides together.
Frequently asked questions about licensing
Do I have to pay for the development environment?
No. The environment you write the program in is free, and you can try it without a licence in simulation mode. Charges apply to the runtime on the target device and to whichever add-on packages you choose.
Can I move a licence from one machine to another?
With a hardware dongle, yes — the licence is valid wherever the dongle is plugged in. With a software container the licence is bound to the system it is installed on and has to be reissued if the hardware changes. In series production the second method is usually preferred.
Why is there no ready-made price list?
Two different architectures for the same machine produce very different licence totals. Any figure quoted before the axis count, motion requirement, visualization client count and communication protocols are settled would be misleading. Send us your axis list and we will prepare an itemised quote.
Is there support after purchase?
Yes. Supplying the licence is where the work starts for us: commissioning, remote support and engineer training all run under the same roof. When you hit a timing or synchronisation problem in the field, we go through the recording with you.
Is the licence annual or one-off?
Runtime and add-on package licences are bought once per machine; they are not a subscription. The only time-limited element is an optional support and update agreement. You can keep running the same version for the life of the machine.
Do I need a second licence for a standby controller?
If both devices will run at the same time, yes. For a standby that only comes in on failure, moving the dongle is usually enough — swapping it into the spare takes a couple of minutes. On critical lines we do recommend a second licence to shorten downtime.
Can I increase the axis count later?
Yes, the licence can be upgraded. The real constraint is usually not the licence but the hardware’s cycle budget: the new axes have to fit inside the target cycle time. That is why we prefer to discuss likely growth at the start and choose the processor class accordingly.
Do you handle licence activation?
Either we do it or your own team does. In series production it pays to tie activation into the production line, and we help set that up. On a single machine we normally complete it together during commissioning.
What happens if I lose the dongle?
If the dongle is lost, the licence is lost with it — which is why we recommend fixing it inside the cabinet and keeping a record of serial numbers. A software container carries no risk of physical loss, but its backup has to be managed deliberately.
How quickly can you prepare a quote?
Usually a few business days once we have the axis list and screen requirements. The only thing that stretches it is an architecture decision that is still open; in that case we hold a short technical call first and price the two options side by side.