Skip to main content

HMI in WAN erreichen

Comments

3 comments

  • Franziska Gültig

    Hi Cedric!

    Whitch Cosy do you use exactly? Cosy+ or Cosy 131?

    So you are saying WAN and LAN are not seperated. There already is a Router connecting these two that is not the Cosy?

    You could try this:

    Adding a Permanent Route to the HMI in the Routing Table of the Ewon using the IP adress of the Router on the LAN side of the Cosy as the Gateway... (you might need to enter the number of hops / Routers /Lev 3 Switches exactly to make it work) trace cert with cmd should show you how many hops if you (your PC is on the LAN side in the Network there...

    How to Use Tracert/Traceroute Command in Windows | GeeksforGeeks (this link is not afiliated with hms please take care)

    br

    Franziska Gültig

     

    0
  • Cédric Mauron

    Hi Franziska

     

    I'm using the Cosy+ (EC71330)

     

    Yes there is a scalance router which manages the two networks. The Remote Acces is new in this machine. It wasn't needed before.

    I will try this out.

     

    Should i see the HMI in the EWONs Profinet Explorer?

     

    Do i need to do a routing on my computer? So that when i try to load the HMI the Software goes over the Ewon and not another path?


    br

    Cédric Mauron

    0
  • Franziska Gültig

    Hi Cedric!

    The Profinet Explorer communicates on a Mac layer that can not be routed (Only IP layer is routed) because of this we created the Profinet Explorer locally...

    Unfortunately you can't do basic coding like in the Flexy to try to open a socet localy to test if it is reachable.

    Yes if you do Remote Access you also need to add the Route in the PC you are connecting to the Cosy on. Sorry I didn't mention that before was focused on the local aspect... But since you don't use a Flexy I should have though of you using Remote Access. And for that Using ADD Route on the PC is nessesary (also check if there are any conflicts on the PC already using that Range. A narrow route to only the HMI should give it priority though even if there is an overlap.)

    If it doesn't work you could define the Route to be as narrow as possible. In the Cosy (and on the PC) To only Route the IP adress of the HMI. (to not conflict with the WAN settings a more narrow Route could help) so not Routing a whole Network but just that one IP.

    If the used gateway is intelligent and can do mapping you could also define a totaly new IP adress for the HMI in the Gateway so there are no conflicts possible with the WAN side of the Cosy. And add the route to that new IP adress to the Cosy and PC .

    If above are not an option or don't work you could connect the WAN and LAN side of the Cosy reducing the security in the process since it will expose the Webpage of the Cosy to the WAN network... the Cosy will Route any traffic intended for the LAN or WAN side like that.

    the parameters doing that are: 

    FwrdToWAN=1 (will be switched to 0 if most wizards are run)

    WANItfProt=2 (will be reset if most wizards are run)

    on the Webpage you can find these here: 

     System Setup > Storage > Tabular Edition > Edit COM cfg

    But we do not recommend it from a security point of view.

    hope that helps!

    br

    Franziska Gültig

    0

Please sign in to leave a comment.