CodeMeter Network Server: Keep runtime dongle local-only and export only a second CmStick

Wold — Sun, 02 Aug 2026 01:11:34 -0000

Hello,

I am running a CODESYS Control Runtime on a Raspberry Pi.

Two CmSticks are connected to the same system:

CmStick A
- Runtime license
- MultiCore license
- KNX license

CmStick B
- Engineering / Developer licenses

My goal is:

The runtime on the Raspberry Pi shall use CmStick A locally.
Licenses from CmStick A shall NOT be provided by the CodeMeter Network Server.
Only licenses from CmStick B shall be available to remote network clients.

During troubleshooting I observed that the CodeMeter Network Server collects licenses from both CmSticks. The KNX license appears to be local-only, but the runtime and multicore licenses of the same dongle are still visible through the server.

I would like to know if a supported configuration exists for the following scenario:

One CmStick remains strictly local to the runtime.
A second CmStick on the same machine is exported through the CodeMeter Network Server.

Questions:

Is it possible to exclude a specific CmStick from being exported by the CodeMeter Network Server?
Can this be configured via License Access Permissions (ACL), WebAdmin, or another mechanism?
Can export rules be applied per CmStick, per Firm Code, or per Product Code?
If supported, could you provide a configuration example or a reference to the relevant documentation?

The reason for asking is that after removing a separately installed CodeMeter server component and returning to a local-only setup, the runtime licensing behaviour became stable again. Therefore I am looking for the officially supported way to keep the runtime dongle local while still providing engineering licenses from a second dongle over the network.

Thank you.

Recent posts to CodeMeter Network Server: Keep runtime dongle local-only and export only a second CmStick

CodeMeter Network Server: Keep runtime dongle local-only and export only a second CmStick