Troubleshooting
Edge gateway shows offline: check the 3.5.16 requirement
Short answer
An edge gateway that flipped from green to offline most likely sits on 3.5.15 while the Automation Server lists Edge Gateway 3.5.16.0 or higher as the runtime system requirement. Read the installed version first, then remove and re-add the gateway, replace it through the service tool, update to 3.5.16.0 or higher, and escalate through a CODESYS Store support question if it stays red.
On this page
An edge gateway that sat green in the CODESYS Automation Server and now shows offline is a version question before it is anything else. The Automation Server's download page lists the runtime system requirement as Edge Gateway 3.5.16.0 or higher, and it used to read 3.5.15, so a gateway installed under the old rule fails the new one on paper. Read the installed version first, then work the ladder the vendor documented: remove and re-add the gateway, replace it through the service tool, update to 3.5.16.0 or higher, and escalate through a CODESYS Store support question if it is still red.
What the offline circle tells you #
The number to act on is 3.5.16.0. The download page states it as "Edge Gateway 3.5.16.0 or higher" for the runtime system; the same page previously named 3.5.15, which is why a gateway installed a while ago passes every old checklist and fails this one. Nothing on the device changed — the floor moved under it.
Hold one nuance from vendor support: the SP16 gateway requirement was introduced primarily to enable remote debugging and to connect to runtimes with a version greater than SP16, and the connection itself should not be affected, so a 3.5.15 gateway should still be able to appear as connected, green circle included. That makes the version gap the first gate, not a proven root cause. The decision is still clean: below 3.5.16.0 the update is decided; at or above it, the offline state has another cause and the rest of the list finds it.
The check list, in order #
Work it top to bottom; each step either turns the circle green or warrants the next one.
- Read the installed Edge Gateway version on the device. This is the gateway's own number, not the runtime's. If it reports 3.5.15, the update is decided: the third field, 15, sits below the floor's 16, and nothing after that field changes it.
- Restart the gateway service and re-test the connection from the Automation Server. A stopped or stuck service displays as offline exactly like a version fault.
- Reconfigure the gateway entry: remove it from the Automation Server and add it again, then watch for the green circle. Before re-adding, make sure the gateway is open to configuration — that switch lives in the CODESYS Gateway systray as "Allow Edge Gateway configuration..".
- Replace the edge gateway through the service tool. This is the vendor's named replacement path when removing and re-adding does not restore the connection.
- Update the gateway to 3.5.16.0 or higher and re-verify its status. That is what makes remote debugging and runtimes newer than SP16 reachable.
- Still offline after the steps above: open a support question through the CODESYS Store request channel. For this exact symptom the vendor's escalation was an online session, so have the gateway version, the runtime version and the result of each step ready.
Why the floor moved #
Support stated the requirement to use SP16 gateways had been changed about a year before that reply, primarily to enable remote debugging, and that an SP16 gateway is also necessary to connect to runtimes with a version greater than SP16. The connection itself should not be affected. Two cases, two decisions:
- Runtime newer than SP16, or remote debugging in use: a 3.5.15 gateway cannot do the work the requirement exists for. Update it; no configuration substitutes for the version.
- Runtime at SP16 or older, remote debugging unused: the vendor's own statement says the gateway should still show green. If it is red anyway, keep the update on the schedule but hunt the real cause in steps 2 to 4 — service state, stale entry, certificate.
Remote debugging is a live path into the control network: open it for the session you are running and close it afterward.
Worked example: auditing a mixed fleet #
Illustrative fleet, not a measurement. Fourteen gateways report to one Automation Server: nine at 3.5.16.20 and five at 3.5.15.40, against the floor of 3.5.16.0. Compare field by field: 3 equals 3, 5 equals 5, and the third field decides. Sixteen is at or above sixteen, so the nine pass. Fifteen is below sixteen, so the five fail, and the 40 in the fourth field never rescues them, because 3.5.15.40 sits below 3.5.16.0. Arithmetic: 9 + 5 = 14 accounted for, and 14 − 9 = 5 gateways to update. Decision: schedule those five, leave the nine as they are, and re-check the fleet afterwards so every third field reads 16 or higher.
Gateway green, device behind it red #
If the red circle belongs to the PLC behind a green gateway, the Automation Server link is healthy and the fault is on the gateway-to-controller path. That is a different failure with its own method, laid out in edge gateway online but PLC offline: diagnose the link, and the version ladder above will not move it.
If it stays offline after the list #
Do not loop the steps a second time. Open a support question through the CODESYS Store request channel; the vendor's answer for this symptom was that the case needs checking online, with support looking at the system directly. Bring the gateway version, the runtime version, which steps ran, and what changed between the last green state and the first red one — an operating system update, a certificate renewal or a network change inside that window narrows the search for them.
Questions asked
Does every 3.5.15 edge gateway need the update immediately?
No. The vendor states the plain connection is not affected by the SP16 change, so a 3.5.15 gateway serving a runtime at SP16 or older should still show green. The update is mandatory when you use remote debugging or the runtime is newer than SP16. Updating every gateway anyway removes the mixed-version trap the next time the fleet is audited.
My gateway is green but the PLC behind it shows offline. Same fault?
No. That failure sits between the gateway and the controller, not between the gateway and the Automation Server. Because the PLC is already registered, running the network scan again changes nothing; it will not reconnect a device the server already lists. Work the route from the gateway to the device instead.
Can I check gateway status without opening the CODESYS IDE?
Yes. The Automation Server portal itself shows the gateway, and a device behind it, as online or offline. A workstation with the IDE is what you connect from when configuration or remote debugging is needed; reading status does not require it.
Can an expired certificate make the gateway show offline?
Yes. Certificate expiry blocks the connection. The Automation Server can establish a temporary connection to an edge gateway despite an expired certificate, which gives you a window to reach the gateway and renew the certificate instead of losing the path entirely. If several gateways dropped at the same moment, check certificate validity early.