https://forge.codesys.com/forge/talk/Engineering/thread/cb2fb613cb/2021-11-19T18:18:38.156000ZRecent posts to Access the Raspberry Codesys from PC2021-11-19T18:18:38.156000Z2021-11-19T18:18:38.156000Zalrcastrohttps://forge.codesys.com/u/alrcastro/https://forge.codesys.com469273b27bcc2cba7957f81a00de9d6c9beec53c

<div class="markdown_content"><p>Thank you again for your ever kind help.</p></div>

2021-11-19T15:28:01.249000Z2021-11-19T15:28:01.249000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com648810613358dcb29940cefa40c996bc49c4e060

<div class="markdown_content"><p>no could do both..!</p></div>

2021-11-19T14:37:30.944000Z2021-11-19T14:37:30.944000Zalrcastrohttps://forge.codesys.com/u/alrcastro/https://forge.codesys.com1b00eafed97b2f0bf679f1a07e07874f8c97e47e

<div class="markdown_content"><p>An issue we just came accross is that, according to what we've found, sounds like the Edge Gateway do not performs a straight connection P2P between our Engineering tool and the gateway itself, but rather a cloud-based access trhought the CODESYS Automation Server; the End application on the factory side have restrictions regarding third parties connections.</p></div>

2021-11-19T12:45:24.670000Z2021-11-19T12:45:24.670000Zalrcastrohttps://forge.codesys.com/u/alrcastro/https://forge.codesys.com06756cf442f63ad15018a8794c5fc1569075af06

<div class="markdown_content"><p>Hi, I quite appreciate your help, it is seemingly exactly what we need. However I could not find any concise tutorial explainig the whole step-by-step, but only split videos covering specific issues. Could I ask you for a link explainig how to do that ? Many thanks in advance.</p></div>

2021-11-18T21:23:32.184000Z2021-11-18T21:23:32.184000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com28e6ca32b494470a10b10bf3f4811d21ded1b295

<div class="markdown_content"><p>just install the Edge Gateway on rhe Windiws PC, nothing else. Then add this Gateway in CODESYSban scan the PI via this new added Gateway</p></div>

2021-11-18T19:43:44.172000Z2021-11-18T19:43:44.172000Zalrcastrohttps://forge.codesys.com/u/alrcastro/https://forge.codesys.com0fcda55e4a40252e30227664790f3e3660de9df3

<div class="markdown_content"><p>Not bumping the thread, just adding an overview of the issue.</p> <p><strong>The original topology:</strong></p> <p><span>[ PC(WIN10) : Codesys runtime ]</span> &lt;=&gt; Engineering Tool</p> <p><strong>The wanted topology:</strong></p> <p><span>[ RPI3(Linux) : Codesys runtime ]</span> &lt;=&gt; <span>[ PC(WIN10) : Portfowarding(?) ]</span> &lt;=&gt; Engineering Tool</p></div>

2021-11-18T13:18:43.812000Z2021-11-18T13:18:43.812000Zalrcastrohttps://forge.codesys.com/u/alrcastro/https://forge.codesys.comc2fe007f76f034bc61027fa6cb5ecb862cc25f8c

<div class="markdown_content"><p>Hi there,</p> <p>We have been using last years the Codesys in WIN10, having the PC as the interface for the H/W of the PLC I/O's, so far so good. In this case, the PC is installed remotely, and its IP is normally routed through the wired network (eg. 10.20.30.40 ).</p> <p>However, we are carrying out tests with the I/O's of the PLC in another architecture, now embedded in an SBC (RPI3), and its IP is distinct from the external network, as it is located in another network adapter (USB/ETH) in the internal network ( 192.168.1.x ). We obviously uninstalled the Codesys runtime from the PC in this new approach.</p> <p>Separately, both options worked normally with the PLC I/Os, which attests that there are no system impediments. However, it is not clear how the access to the RPI through the PC should be done, would it be necessary to implement a PROXY, Portfowarding ? Is there any tutorial on this ?</p> <p>Thanks in advance,<br/> Andre.</p></div>