Troubleshooting
Gateway setup when a network scan finds no Linux runtime
Short answer
A runtime you can start from the Development Environment but cannot find with Scan for Devices is reachable for management but not for discovery. Install Gateway for Linux on the Debian industrial PC, add a gateway entry in the project that points at that PC's IP address, select it, and scan again; the IPC then appears.
On this page
- Why a running runtime still scans empty
- Two quick checks before you touch the gateway
- Install Gateway for Linux and point a new entry at the IPC
- Working the subnet check for a workstation at 10.0.4.11 and an IPC at 10.0.4.12
- Why the ARM64 runtime switch is a separate decision
- Open the gateway's port, not the whole host
- What each result decides
- Questions asked
A CODESYS Control for Linux SL runtime that starts cleanly from the CODESYS Development Environment but never appears in a network scan is a gateway problem, not a runtime problem. Starting the runtime and reading its system information proves the management path; the scan sends discovery requests through whichever gateway entry the project's communication settings select, and that gateway must reach the runtime on its own. The fix: install Gateway for Linux on the Debian industrial PC, add a gateway entry in the project that points at that PC's IP address, select it, and run Scan for Devices again. The sections below walk the quick checks that rule out a filtered scan, the install steps, one worked subnet check, and the decision for each result.
Why a running runtime still scans empty #
Management and discovery travel different roads. Starting the runtime from the Development Environment and reading its system information proves the management connection end to end. Scan for Devices does not reuse that path: it sends discovery requests through the gateway entry selected in the project's communication settings and reports only what that gateway can see. If the selected gateway sits on the engineering workstation with no working view of the runtime's network, the scan comes back with 'No device is responding to the scan request' or with nothing at all, and neither result says anything about the health of the runtime itself. Keep the two services distinct as well: the gateway and the control runtime run as separate processes on the target, so the state of one proves nothing about the state of the other.
Two quick checks before you touch the gateway #
Work these in order; each one has retired an empty scan on its own.
- Read the scan filter. The scan dialog filters results by the device configured in the project, so a project set to a 32-bit Windows soft runtime (Control Win (32bit) in the documented case) shows an empty list on a network that holds a Linux runtime until the filter is switched off. Disable the filter once to see everything the selected gateway reaches, then set the project device to the installed family, CODESYS Control for Linux SL, and scan again.
- Confirm which gateway entry the project selects. A scan through a leftover or default entry tests that entry's view of the network, not the target PC's, and an empty result from it proves nothing about the target.
- Ping the IPC from the workstation, and treat the reply as supporting information only. A reply proves the host answers at that address; a timeout can be filtering rather than a dead host; neither result tests the gateway service.
- Check both services on the IPC in their own right. The gateway and the control runtime run independently, so confirm each one's status separately.
Install Gateway for Linux and point a new entry at the IPC #
- Record the starting point: the installed runtime package (CODESYS Control for Linux SL in this case), the IPC's IP address and mask, the project device, and the gateway entry currently selected.
- Obtain Gateway for Linux through the vendor's official distribution channel and install it on the Debian PC by the package's own instructions. Read the listing of the exact package you install first; the vendor's listing for its Linux edge gateway, the related package for this job, states Debian- or Ubuntu-based Linux (32/64-bit), x86, x64 or ARMv7 CPUs, and a runtime of V3.5.10.0 or higher.
- Start the gateway service on the IPC and confirm it stays up, then check the control runtime separately, because the gateway needs a live runtime to discover.
- Preserve the project before changing its communication settings; the discipline is the same as backing up a PLC program the right way before touching the controller.
- In the Development Environment, open the project's communication settings and add a new gateway entry carrying the IPC's IP address and the connection settings the installed gateway requires.
- Select the new entry and run Scan for Devices. Select the IPC the scan returns, confirm from its reported information that it is the machine you expect, then log in and download.
If the modern communication page misbehaves while you work, the documented fallback is Tools > Options > Device Editor > Communication Page > Classic Mode: switch it on, then double-click the device to reach the communication settings from there and rescan.
Working the subnet check for a workstation at 10.0.4.11 and an IPC at 10.0.4.12 #
The addresses below are illustrative values for a flat machine network; the check is general and takes a minute.
Inputs. Engineering workstation: IP 10.0.4.11 with subnet mask 255.255.255.0 (a /24). Debian industrial PC: IP 10.0.4.12 with subnet mask 255.255.255.0.
Rule. Two IPv4 hosts share a network, and need no router between them, when each address ANDed with its own subnet mask yields the same network address.
Arithmetic. AND octet by octet, address against mask:
- Workstation: 10 AND 255 = 10; 0 AND 255 = 0; 4 AND 255 = 4; 11 AND 0 = 0, giving network address 10.0.4.0.
- IPC: 10 AND 255 = 10; 0 AND 255 = 0; 4 AND 255 = 4; 12 AND 0 = 0, giving network address 10.0.4.0.
Result. Both machines compute 10.0.4.0/24.
Decision. Equal network addresses mean a direct path exists: enter 10.0.4.12 as the address of the new gateway entry and scan through it. Unequal results, 10.0.4.0 against 10.0.5.0 for example, mean a router must carry the connection, and that router must pass the gateway's service port; put routing right, or move both interfaces into one subnet, before blaming the gateway. A successful ping in the same subnet supports the conclusion but never proves the gateway service answers.
Why the ARM64 runtime switch is a separate decision #
The installation this fix came from did not stop at the gateway: it also installed CODESYS Control for Linux ARM64 SL and changed the project device to match, and the scan then found the industrial PC immediately. Two variables moved at once, so that outcome proves a working combination, not which change cured the scan.
Keep three decisions apart. The gateway entry decides the discovery path. The runtime package decides the processor architecture and the features the controller supports; an ARM64 package belongs on ARM-class hardware, and that package was chosen here because it carries features the project would need later. The project device decides what the application targets, and this one carries a SoftMotion controller based on CODESYS Control for Linux SL. An empty scan alone is never a reason to migrate a working runtime to another family, and any device change deserves a rebuild and a recheck of the project before the next login.
Open the gateway's port, not the whole host #
The workstation-to-gateway connection is a TCP service, and the port it uses is recorded in the gateway's own configuration on the machine where it is installed. Read the port there and in the package's documentation rather than copying a number from an unrelated setup, then add one rule for the engineering workstation's address on the engineering network and leave the rest of the host closed. Do not disable the firewall to make discovery work: a blocked gateway port produces exactly the same empty scan as a missing gateway, which is why filtering sits high in the check list.
What each result decides #
- The runtime starts and the scan stays empty even with the filter off: the selected gateway cannot see the runtime. Install Gateway for Linux on the IPC, point a new entry at its IP address, select it, and rescan.
- The scan stays empty with the target-side gateway selected: the workstation cannot reach the gateway host or its port. Work the subnet check, then routing, then the firewall rule.
- The scan lists the IPC: select it, confirm its identity, log in and download. From then on the same connection carries the everyday diagnostics, and reading a USB datalog from an HMI in the CODESYS runtime is one that runs over a healthy runtime link.
Questions asked
What does 'Attention! The device was not found in the repository.' mean?
That message differs from an empty scan: discovery reached a device, but its device description is not installed in the Development Environment's repository. Install the device description that matches the target, then repeat the scan and select the device from the result.
Does a SoftMotion project scan differently from a plain one?
No. Scan for Devices locates the controller the same way regardless of the application. SoftMotion changes what the runtime must support, not how discovery works, so a SoftMotion project built on CODESYS Control for Linux SL needs an installed package that carries the SoftMotion features it uses. Confirm that before the first login and download rather than after a failed one.
Do I need to switch to the ARM64 runtime package to fix scanning?
No. Discovery follows the gateway entry, not the runtime family. An installation that paired the gateway change with a switch to CODESYS Control for Linux ARM64 SL did work, but it changed two variables at once. If you do change families, install the device description for the new target and rebuild the project before the next scan.
Does a successful ping mean the gateway connection will work?
No. Ping travels as ICMP and the gateway connection is TCP, so they can succeed and fail independently in both directions. A PC can answer ping while a firewall drops the gateway's port, and a failed ping can be filtering rather than a dead host. Test the connection itself by selecting the gateway entry in the Development Environment and scanning.