Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Hi
We have a display (on a mobile machine) programmed using Codesys 3.5. Usually we connect to the display over ethernet from a laptop running the development system (over the local tcp/ip gateway, the display has a fixed IP address and we simply connect it directly to the ethernet port on the laptop, the laptop and device are on the same subnet).
We now want to connect remotely to the display through a remote access gateway/device on the machine (a linux/raspian box that uses zerotier to create a virtual switch over a vpn). The display (on the machine) and the laptop (in the office) are still on the same subnet (192.168.2.0/24). We can ping the display - no problem, but the local codesys gateway running on the laptop can't find the display. Broadcast seems to be enabled and firewalls are open, so we are not sure what is wrong.
We were hoping that the codesys development system would find the display given that they remain on the same subnet. Do we have to install codesys (and a codesys gateway) on our remote access device (running linux)? Or can we solve this in a simpler way.
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometimes I've had it where my development system won't see a PLC. In cases like that I need to add a favorite device and I need to specify its IP address.
Would a web visualization with the browser in kiosk mode work for you? That's definitely the cheapest way.
What Eschwellinger says might be easier for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Simpler way... would be using CODESYS Automation Server, install the EdgeGateway to the Pi ans add this EdgeGateway to your server...and scan your PLC, add it to the Server...login via CODESYS to your remote PLC... https://youtu.be/8KLywg51Xyk
👍
1
Last edit: eschwellinger 2020-09-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
have set up the edge gateway on the raspberry pi gateway device, and it is showing in the automation server (green). The display (PLC) is found when running network scan, but there is an error when adding it to the automation server:
Unable to add installed PLC (error: Error -1 returned: Writing ID setting failed: 0x0001
any thoughts?
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
this version 3.5.1.x is to old, minimum requirement for CODESYS Automation server is 3.5.8.x,
Filesystem on plc would be needed too, therefore the only way is to go by VPN.
I would add in CODESYS the remote Gateway (you have installed the EdgeGateway on your PI).
So add a new Gateway with the IP address of your Raspberry PI and scan your plc via this Gateway in CODESYS. This should work.
Hi
We have a display (on a mobile machine) programmed using Codesys 3.5. Usually we connect to the display over ethernet from a laptop running the development system (over the local tcp/ip gateway, the display has a fixed IP address and we simply connect it directly to the ethernet port on the laptop, the laptop and device are on the same subnet).
We now want to connect remotely to the display through a remote access gateway/device on the machine (a linux/raspian box that uses zerotier to create a virtual switch over a vpn). The display (on the machine) and the laptop (in the office) are still on the same subnet (192.168.2.0/24). We can ping the display - no problem, but the local codesys gateway running on the laptop can't find the display. Broadcast seems to be enabled and firewalls are open, so we are not sure what is wrong.
We were hoping that the codesys development system would find the display given that they remain on the same subnet. Do we have to install codesys (and a codesys gateway) on our remote access device (running linux)? Or can we solve this in a simpler way.
thanks
Sometimes I've had it where my development system won't see a PLC. In cases like that I need to add a favorite device and I need to specify its IP address.
Would a web visualization with the browser in kiosk mode work for you? That's definitely the cheapest way.
What Eschwellinger says might be easier for you.
Simpler way... would be using CODESYS Automation Server, install the EdgeGateway to the Pi ans add this EdgeGateway to your server...and scan your PLC, add it to the Server...login via CODESYS to your remote PLC...
https://youtu.be/8KLywg51Xyk
Last edit: eschwellinger 2020-09-22
thanks for your feedback
have set up the edge gateway on the raspberry pi gateway device, and it is showing in the automation server (green). The display (PLC) is found when running network scan, but there is an error when adding it to the automation server:
Unable to add installed PLC (error: Error -1 returned: Writing ID setting failed: 0x0001
any thoughts?
Which runtime version is on your PI installed?
3.5.x.x?
Last edit: eschwellinger 2020-09-23
The edgegateway is the latest: 3.5.16.10 (downloaded today)
The PLC (display) however is quite old:
Vendor Telestar srl
Device type 4096 / CoDeSys Control Cortex
Version 3.5.1.0
Target ID 272375814
Ok let us check If a workaround is possible...write to CODESYS Store - my question - bug report or is an update possible?
Last edit: eschwellinger 2020-09-23
thanks, have submitted bug report under "error adding PLC to automation server"
Unfortunately the runtime on the display/PLC cannot be updated at this time
Hi,
this version 3.5.1.x is to old, minimum requirement for CODESYS Automation server is 3.5.8.x,
Filesystem on plc would be needed too, therefore the only way is to go by VPN.
I would add in CODESYS the remote Gateway (you have installed the EdgeGateway on your PI).
So add a new Gateway with the IP address of your Raspberry PI and scan your plc via this Gateway in CODESYS. This should work.
Last edit: eschwellinger 2020-09-25