https://forge.codesys.com/forge/talk/Engineering/thread/b20a5c24b6/2020-07-13T06:42:31.972000ZRecent posts to Loss of connection via VPN2020-07-13T06:42:31.972000Z2020-07-13T06:42:31.972000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comee910cb5fba3f4190ea4e701de654cf3d0b038de

<div class="markdown_content"><p>.. not tired of preaching that exactly this is a typical task for using CODESYS Automation server.<br/> There is one important restriction - at the moment this does not work with e!Cockpit.</p> <p>Till then, you might use CODESYS V3 on PFC side and CODESYS V3 as development system. Later if implemented you could switch back to e!COCKPIT - ( missing UserManagement - on Automation server side).</p> <p>You could reach the webvisu via Automation server and you could login via the Automation Server to the PFC's. ( no Teamviewer needed no VPN needed)<br/> Just install the Edge Gateway on the PFC and add these Devices to the Automation server.</p> <p>By the way, not sure if this works on PFC with e!COCKPIT - SysProcessExecuteCommand - from SysProcess lib should work to reboot the PFC's.</p></div>

2020-07-13T00:07:30.558000Z2020-07-13T00:07:30.558000Zalvarochaconhttps://forge.codesys.com/u/alvarochacon/https://forge.codesys.com7c62b5466a0f2141f3bb2c1debfbff6da27a24ca

<div class="markdown_content"><p>Hello colleagues, I have a big problem with my project, I am working with a <strong>PFC200 PLC</strong> (750-8202 / 025-002). I am using the <strong>e!Cockpit</strong> software, which is based on <strong>Codesys 3.5</strong>.</p> <p>To access this PLC, I must do it through a <strong>VPN</strong>, since the project involves different places (Solar Farm).</p> <p>The basis of the project is as follows, The User Enters a Hosted Application on a WEB page, this API (Master) communicates with the PLC through Modbus TCP (Slave), and this PLC (Now MASTER) communicates with a TESLA battery (Slave).</p> <p>Everything Works Perfect as long as the VPN service on the PLC is working. I don't know why, but the VPN service in the PLC stops (Although the VPN continues to work without a problem). Here comes the big problem, someone must go to the PLC Site and Restart it, or we must connect via TeamViewer to a PC in the same Local Network of the PLC and restart it through WBM. While all this is happening, the PLC remains isolated from the API.</p> <p>Already in context, this would be my great concern:<br/> <strong>How can I restart or reboot the PLC through Programming?</strong></p> <p>I can ping the Server regularly from the PLC and when it stops responding for a while I can hook a Boolean, now I only need the Important part, how do I restart the PLC with that contact.</p> <p>Or how can I programmatically re-establish the service in the VPN?</p></div>