IMDHMIControls LibraryShop main store

Troubleshooting

Why the CODESYS EtherNet/IP scanner runs in demo mode

Industrial networks Published 6 min read

Short answer

The scanner runs in demo mode because the installed Fieldbus communication IEC 61784 license covers the PROFINET controller stack, not the EtherNet/IP scanner. Activate the EtherNet/IP Scanner add-on license on the control running the CODESYS runtime and restart it; the 30-minute limit and the license message then clear.

On this page
  1. Why is the EtherNet/IP scanner in demo mode when a license is installed?
  2. Why does EtherNet/IP communication stop after 30 minutes?
  3. What does the IEC 61784 license actually cover?
  4. Where in the data path does the license gate sit?
  5. How do you activate the EtherNet/IP Scanner license?
  6. What else stops EtherNet/IP communication on a timer?
  7. How do you confirm demo mode is cleared?
  8. Questions asked

The scanner runs in demo mode because the license on the control belongs to a different protocol stack. The installed license, "Codesys Fieldbus communication IEC 61784 family controller", covers the PROFINET controller functionality of the CODESYS packages; the EtherNet/IP scanner device in your project checks for its own add-on, "ctrlX OS License - CODESYS - EtherNet/IP Scanner (add-on)". Until that add-on is active on the control running the CODESYS runtime, the scanner runs as a timed demo and communication stops after 30 minutes. Activate the scanner license, restart the runtime, and the message clears.

Why is the EtherNet/IP scanner in demo mode when a license is installed? #

The installed license unlocks the PROFINET controller stack only, and the EtherNet/IP scanner device checks for a scanner-specific add-on license, so the runtime flags the scanner stack as unlicensed and runs it as a demo.

The Ethernet interface of the scanner in PLC engineering shows the message exactly: "The license is missing or invalid. The PLC runs in demo mode." The control's license list is not empty, because the family license is present and its title sounds protocol-neutral, which is why this reads like a network fault. It is a licensing fault. The license gate is per protocol stack, the stack behind the device you added is EtherNet/IP, and that is the license the runtime looks for.

Why does EtherNet/IP communication stop after 30 minutes? #

An unlicensed scanner stack runs as a timed demo that limits communication to 30 minutes of runtime, so the connection opens, cyclic data flows, and then the I/O assemblies stop at the 30-minute mark with the license message still in the device editor.

The 30-minute value is the demo limit of this runtime for an unlicensed stack, a licensing behavior rather than a protocol timeout, and not something the adapter or the switch controls.

Worked example, on numbers you can check against your own schedule: one production shift is 8 hours. 8 h × 60 min/h = 480 min of required runtime. The demo timer covers 30 min, so an unlicensed control would hit 480 min ÷ 30 min = 16 expiry events per shift, and each expiry drops the cyclic I/O. The decision follows from the arithmetic: any run longer than 30 continuous minutes needs the license, and the demo belongs on the bench.

One safety note: if the adapter I/O feeds a drive run command or an interlock, expiry is an I/O loss like any other, and the machine's response to lost data must already be defined before you test.

What does the IEC 61784 license actually cover? #

IEC 61784 is the family name for several fieldbus profiles, so a license carrying that title still unlocks only one protocol stack, in this case the PN-Controller functionality of the CODESYS packages, and the EtherNet/IP scanner ignores it completely.

The standard itself defines the profiles; it does not license anything, and a title built on the family name tells you the stack only when the title says so. CODESYS licenses each protocol stack as its own functionality: a PROFINET controller device in the project matches the family license already on the control, and an EtherNet/IP scanner device matches only the scanner add-on, which the vendor's listing describes as enabling the control to exchange data with EtherNet/IP adapter devices. Which master device to add in the first place is the project-side decision covered in selecting a CODESYS fieldbus master for industrial Ethernet; what this article covers is the runtime-licensing consequence of that choice.

License on the control Unlocks the EtherNet/IP scanner? Runtime limit Decision
"Codesys Fieldbus communication IEC 61784 family controller" (PN-Controller functionality) No 30-minute demo Keep it only where PROFINET controller devices run on the same control
No scanner license installed No, timed trial 30-minute demo Bench commissioning and adapter integration tests only
"ctrlX OS License - CODESYS - EtherNet/IP Scanner (add-on)" Yes No timer from this license Production, and any run past 30 minutes

Where in the data path does the license gate sit? #

The gate sits inside the controller, in the EtherNet/IP scanner stack that runs in the CODESYS runtime, so the stop happens with the network healthy — link up, adapter reachable, connection open — which is why switch and cable work wastes time here.

Element in the path Can it cause the timed stop? How its own faults look
EtherNet/IP scanner stack in the PLC runtime Yes, the license check runs here and an unlicensed stack runs as the timed demo Fixed stop at the demo limit, with the license message in the device editor
IP address, subnet and interface assignment No No connection at all, not a timed loss
Cabling and switch: link, speed, duplex No Immediate or intermittent connection failures
Adapter: implicit connection, RPI (requested packet interval), assembly instances No Mismatched assemblies fail when the connection opens

A connection that opens, exchanges data, then stops at a fixed mark with the license text present is the first row. Leave the switch and the adapter alone until the license message is cleared.

How do you activate the EtherNet/IP Scanner license? #

Activate the scanner add-on license on the same control that hosts the CODESYS runtime, then restart the runtime so the scanner stack re-evaluates its license at start; a license sitting on the engineering PC changes nothing.

  1. Open the license listing of the ctrlX OS control that runs the PLC runtime and record what is installed; expect the family license as the only fieldbus entry.
  2. Order the scanner add-on using the exact order reference from the ctrlX OS store listing or your supplier's quotation, not from the title of the license you already hold.
  3. Activate it on that same control, because the scanner stack runs there and the engineering PC is not the target.
  4. Restart the PLC application or the CODESYS runtime so the stack re-reads its license at start.
  5. Go online in PLC engineering and open the scanner's Ethernet interface; the demo-mode message must be gone.

What else stops EtherNet/IP communication on a timer? #

Only the demo timer stops communication at a fixed interval from runtime start; a stop at any other moment, or without the license message, points at the adapter's connection timeout, the switch, or the assembly configuration instead.

Symptom Cause Check
PROFINET devices keep running while EtherNet/IP stops Family license present, scanner license absent The license list shows no EtherNet/IP Scanner entry
Scanner license bought and listed, message persists License activated on a different control, or the runtime was not restarted Compare the licensed control with the one hosting the application
No connection at all, no license message IP, subnet, link or assembly instance mismatch Link LEDs, ping the adapter, compare assembly instances and RPI
Stop at an interval other than the demo limit Not the demo timer Adapter connection timeout and switch multicast behavior

A working PROFINET controller is what masks this: the license list looks populated, so the missing scanner entry is easy to overlook.

How do you confirm demo mode is cleared? #

Confirm the Ethernet interface in PLC engineering no longer shows the license message, every adapter connection reports running, and the input assemblies keep updating past the demo limit with margin — one hour online covers two demo periods.

  • The device editor shows no license message on the scanner's Ethernet interface.
  • Every adapter connection reports running status and input assembly data updates.
  • The runtime stays online for 60 min: 60 min ÷ 30 min = 2 demo periods, with all connections open and values updating.

Decision, case by case: a control that scans EtherNet/IP adapters in production gets the scanner add-on license; the family license stays installed only on controls that also run PROFINET controller devices; anything unlicensed stays on the bench, where the demo limit is an inconvenience rather than a fault.

Questions asked

Does the EtherNet/IP Scanner add-on also license adapter mode?

No. On ctrlX OS the EtherNet/IP adapter, the slave side that an external scanner connects to, is a separate product licensed per controller. The scanner add-on covers the master side only: exchanging data with EtherNet/IP adapter devices from the CODESYS runtime.

Is a communication stop at 30 minutes always the license?

If the stop comes 30 minutes after the runtime starts and the device editor carries the license message, yes, that combination is the demo timer. A stop at any other interval, or with no license message, is a network or adapter problem instead; work the connection timeout and the switch before touching licenses.

Can the PROFINET controller license and the scanner license run on the same control?

Yes. The two are independent and both can be active on one control, which is the correct setup when the project runs PROFINET controller devices and an EtherNet/IP scanner at the same time. Each stack checks only its own license, so neither substitutes for the other.

Does installing the license change the scanner configuration?

No. The connection parameters stay as configured: the same assembly instances, the same requested packet interval, the same adapter addresses. The license only removes the demo timer, so after activation and a runtime restart the existing configuration keeps running past the limit.

Keep reading

  • Troubleshooting

    Fixing a TwinCAT EtherNet/IP slave connection from an Omron PLC

    The CIP1 fault is a Forward Open mismatch: each Omron direction must carry the full serialized TwinCAT assembly, not the process variables alone. With 2 bytes in and 2 bytes out, the 4-byte ConnCtrl on outputs and ConnState on inputs make each direction 6 bytes, and the instances must follow producer and consumer roles. If a capture shows the request and a rejection, read the sizes and instances the originator actually serialized.

    Industrial networks

  • Explainer

    Can a Modbus write change PLC outputs?

    Yes, but not by outrunning the scan. On a Modicon CPU the communication interface reaches data memory only between scans, so a write is applied whole and the next scan either consumes it or overwrites it. The real exposure is that Modbus TCP authenticates nothing: any host that can reach the CPU can write an unprotected holding register your logic unpacks into outputs, so pack status into read-only words, keep commands in a separate writable range, and enforce write protection with an IP access control list.

    Industrial networks

  • How-to

    Configure a PowerFlex 525 on EtherNet/IP from an Omron NJ301

    The tag data link fails after a good ping because the NJ, as the EtherNet/IP originator, must send the drive's chosen output assembly plus a 32-bit Run/Idle header: error 0x0127 means the output connection size is wrong. Import the revision-matched EDS, select the target assemblies it lists, create Input and Output network variables of exactly those sizes with the header included, and register them on the Tag Set tab.

    Industrial networks