Access to Safety C.1x through EoE without adding windows route

[LucasTBC]

Hi all,

Working on deploying my first CtrlX core system and I'm trying to setup EoE access to the Safety C.12 controller. I saw this article:

https://developer.community.boschrexroth.com/t5/Store-and-How-to/ctrlX-Safety-Engineering-remote-acc...

However, I don't have admin rights on my machine, (and it's not happening any time soon). So I was wondering if there's a way to use just firewall rules on the CtrlX itself to do a Network Address Translation between my PC and the safety controller?

Thanks!

[AutomateSHANE]

I don't believe so. The IP packets from your PC need to be forwarded from the incoming port on the ctrlX CORE to the port of the ECAT master. Even if there were a way to set up NAT on the CORE to translate the ECAT master EoE IP address, it would not work because your PC is trying to communicate with the SAFEX, not the ECAT master. This is why the routing table of your PC needs to know that the traffic to the SAFEX is intended to be routed through the ctrlX CORE as a gateway. 

[CodeShepherd]

If you open the Engineering tool for an EoE device out of the ctrlX OS Web UI, like ctrlX DRIVE Engineering for our ctrlX DRIVES, the routes are set automatically to your Windows PC. See also "Establish connection to ctrlX DRIVE via ctrlX CORE".

I am not sure if it works the same for ctrlX SAFETY but if you also have drives you could use this mechanism as workaround.