SAFEPLC watch setup via remote connection

Hi Communitiy,

im using a AS remote connection to connect to a X20CP1686X through a Win10 PC. Im in Run in AS, but cant watch any Variables in SAFEDesigner. Is there any way to establisch such a connection? Using AS6.3.4.31(localy) and PVI6.0.2.50 (Win10-PC).

KR and Thanks!

Hi,

as I understood you’re using a Windows pc as remote endpoint, from where the online protocols have to be forwarded to the plc and the safe logic? And you’re able to access the plc via AutomationStudio, but not the safe logic via safe designer? Am I right?

If yes, can you please give us more details about how the remote connection looks like?
Of which type is the remote connection, is a vpn tunnel with routing pr port forwarding on the remote side, or is it pvi remote?

Best regards!

Correct! The Win10-PC is my remote endpoint running PVI on it. AS connection to the PLC is already working. Safedesigner to SPLC is not. No VPN tunnel/port forwarding is setup on the remote endpoint.

Here is the connection:

BR Kenan

Okay, got it!

Unfortunately I can’t deliver a “full-featured solution”, but at least I think I understood the cause and can try to explain it.

SafeDesigner uses a different protocol (and tcp port) then Automation Studio / PVI.
Using PVI, only the PLC online protocol (ANSL) is handled, the safe designer protocol is not part of PVI.
The PLC itself acts as a “protocol proxy” for the SafeDesigner communication, but to do this, the PLC has to receive the safe designer data also on the different channel and port.

As with PVI, also when using Remote PVI only ANSL data is handled via the Remote PVI channel, but not safe designer communication - I think that’s the reason why it doesn’t work.

As I said, I haven’t a out-of-the-box solution, there’s no “safe designer remote” solution available from B&R.
But technically spoken, if there would be a second “port proxy/forwarder” on your Windows remote endpoint, that would be able to receive tcp data and forward it to the PLC (like Remote PVI does for ANSL), I could imagine that this could be at least worth a try.
In your specific use-case (no VPN tunnel), maybe a port forwarding would even be possible on the Windows remote endpoint side (via Windows Firewall or so - not sure about W10, in older version I can remember that a bi-directional port forwarding was at possible with Windows).

I hope this general information helps a bit,
best regards!

2 Likes

Thank you for your detailed explanation regarding this topic. I will try to play around with port-forwarding. Ill post the solution here if i find something. BR

1 Like

Relevant default ports, you should try:

Port Protocol type Description Configuration options
52000 + SafeDOMAIN ID - 1 TCP Remote control connection in SafeDESIGNER for mapp Safety Project engineering of a SafeLOGIC module
50000 TCP SPROXY port for SafeDESIGNER-to-SafeLOGIC communication Module - Configuration: SafeDESIGNER-to-SafeLOGIC communication

Automation Help: Default ports

2 Likes

Hi @Kenan_Dautovic , I have marked answer from Alex as a possible solution. Still curious if you can confirm that this was the solution for your topic?

Hi guys,

I just wanted to shortly share the solution to this. I have create a port-forwarding script on the windows host.

X20PLC ip: 10.10.0.20

(Im using mappSafety → this requires to forward also 52000 in order to be able to operate the remote control dialog)

For some internal reason i had to put the SafeDesigner<>SPLC communication port on 49999. (Variable watch and legacy controller dialog operation possible)

See SafeLogic config in the HW-Tree:

.bat file:

netsh interface portproxy add v4tov4 listenport=11159 connectport=11159 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=11169 connectport=11169 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=2323 connectport=2323 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=49999 connectport=49999 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=52000 connectport=52000 connectaddress=10.10.0.20

netsh interface portproxy add v4tov4 listenport=4840 connectport=4840 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=80 connectport=80 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=81 connectport=81 connectaddress=10.10.0.20
netsh interface portproxy add v4tov4 listenport=8084 connectport=8084 connectaddress=10.10.0.20

netsh advfirewall firewall delete rule name=“BuR_INA” protocol=tcp localport=11159
netsh advfirewall firewall delete rule name=“BuR_ANSL” protocol=tcp localport=11169
netsh advfirewall firewall delete rule name=“BuR_GDB” protocol=tcp localport=2323
netsh advfirewall firewall delete rule name=“BuR_OPC” protocol=tcp localport=4840
netsh advfirewall firewall delete rule name=“BuR_Saf” protocol=tcp localport=49999

netsh advfirewall firewall add rule name=“BuR_INA” action=allow protocol=tcp localport=11159 dir=in
netsh advfirewall firewall add rule name=“BuR_ANSL” action=allow protocol=tcp localport=11169 dir=in
netsh advfirewall firewall add rule name=“BuR_GDB” action=allow protocol=tcp localport=2323 dir=in
netsh advfirewall firewall add rule name=“BuR_OPC” action=allow protocol=tcp localport=4840 dir=in
netsh advfirewall firewall add rule name=“BuR_Saf” action=allow protocol=tcp localport=49999 dir=in

REM Safelogic connection 1 mappSafety
netsh interface portproxy add v4tov4 listenport=52000 connectport=52000 connectaddress=10.10.0.20
netsh advfirewall firewall delete rule name=“BuR_mS1” protocol=tcp localport=52000
netsh advfirewall firewall add rule name=“BuR_mS1” action=allow protocol=tcp localport=52000 dir=in

pause
2 Likes