https://forge.codesys.com/forge/talk/automation_server/thread/d6d2deb8b3/2022-06-15T12:55:35.275000ZRecent posts to Unable to scan2022-06-15T12:55:35.275000Z2022-06-15T12:55:35.275000Zsgronchihttps://forge.codesys.com/u/sgronchi/https://forge.codesys.comf8e8ae2c44c798c9f4888e9fec2ec840409870ad

<div class="markdown_content"><p>Sorry, I forgot to say that the resolution was much more mundane.<br/> The loopback interface on Topcon devices is off by default. Both the running gateway AND the edge gateway can run in parallel without interference if it is enabled.</p> <p>Anyway, they plan to integrate the CmpEdgeGateway component in the next releases of the runtime, so the problem would solve by itself ;-)</p></div>

2022-06-15T12:11:08.227000Z2022-06-15T12:11:08.227000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com6d5201aee052ef88b3544687a89f65dc6a0ec253

<div class="markdown_content"><p>probably there is allready a gateway running on the A8.<br/> This should be removed (ask the plc manufacturer)</p></div>

2022-05-25T05:55:58.476000Z2022-05-25T05:55:58.476000Zsgronchihttps://forge.codesys.com/u/sgronchi/https://forge.codesys.com3a0ac6b3371eabf7c20b718af977ccbcda529c4a

<div class="markdown_content"><p>Also on Automation Server web page the Edge Gateway on A8 reports itself running on port 1217 instead of 11217 (verified with netstat, it would fail the bind otherwise).</p></div>

2022-05-24T11:01:43.195000Z2022-05-24T11:01:43.195000Zsgronchihttps://forge.codesys.com/u/sgronchi/https://forge.codesys.com717faf9df99fc9f120df734d4d71771e576b2fbb

<div class="markdown_content"><p>I have a Topcon A8 in which I manually installed the Edge Gateway 4.0.1.0 (because of SP16) from .deb file (since it does not have dpkg).<br/> It is configured to bind on ports 11217 and 11741 (because the default gateway already binds on 1217 and 11743).</p> <p>The Edge Gateway connects successfully on Automation Server, but one cannot see the actual PLC runtime listed after a scan.</p> <p>stracing it shows EADDRNOTAVAIL in binding on 127.0.0.1:4965 and 127.0.0.1:4966, reflected on messages "CommDrvTCP: 'Bind' failed on signaling socket with error" in the log file.</p></div>