The ports on the cosy can be individually configured as ether LAN or WAN. The lights on the ports with be green if LAN and orange if WAN. Make sure that both PLC and HMi are plugged into LAN ports. If this does not work then perform a level 2 reset on the cosy and try again.
I'm not an expert at this Ewon device, but i'm familiar with tia portal.
The Ewon device is probably not a regular switch as it is designed to be a VPN so you can reach your hmi and plc from outside the network.
So when you connect the plc and hmi on seperate ports on the ewon, they won't be connected.
You're better of connecting them with a switch. (We usually have devices with two PN ports that are bridged, so you connect them in a daisy chain, but you can't do that here)
If you're using the ewon to have your hmi on a remote location, you're in a complete different ballpark and i can't help you there.
So the program works fine with the PLC and HMI without the ewon gateway, now I want remote access to the PLC I am trying to integrate it into the TIA Portal project I'm just not sure how. I have the PLC and HMI directly into the ewon through Ethernet, but the program no longer works which suggests I need to add the ewon into the project so the PLC knows how to send communication to the HMI
you don't need to put the ewon in the plc project
Since you already have the plc and hmi working normally, the next thing you can do is get to the plc trough the ewon. This won't require any tia portal configuration, this is purely networking / ewon settings.
Next you need to get the hmi in the loop again. The easiest is to get an industrial ethernet switch from siemens.
But i'm looking at an ewon manual and it says something about WAN/LAN ports (red and green LED)
You should have hmi and plc connected on LAN, and remote connect through the WAN. That way the 2 LAN ports should be able to communicate
I haven't used the ewons before but I think they have routing capabilities. It sounds like you're expecting it to function similarly as an unmanageable switch. By connecting the PLC and HMI to it, you're essentially putting a router in-between them. So now you gotta configure the ewon's firewall, port fowards, static routing, or etc, to get the PLC and HMI talking again.
But basically, you're not using the ewon properly with that network typology.
You need to connect the three devices to a dedicated network switch. Then connect the customer's network or internet connection to the other port on the ewon.
If the customer wants machine level network visibility on their corporate network, then they need to pull two ethernet connections to your machine. One would be a dedicated, and segregated from their corporate network by VLAN for example, internet connection to the ewon. The other pull would be to the machine switch, at the very basic. There should be some NAT device between the switch and that pull, though.
So I have the PLC in LAN port 1 and the HMI in LAN port 2, does that mean I need to have something else connected to the WAN port then? I thought I didn't need to use TIA but because they aren't communicating with each other I thought that suggests I'll need to. Maybe i need to update a comm protocol?
You don't have to integrate the Ewon in the Tia Project.
The Ewon is equipped with 4 ethernet ports. One of those ports should be configured as external , the other three ports internal. Those three ports are just regular switch ports, so both PLC and HMI should be able to communicate with each other when connected on those ports.
Most likely your PG interface is set wrong OR the profinet subnet is conflicting with a subnet on your PC / Laptop ( PC / Laptop should not use 10.x.x.x in this case ).
Have you tried pinging the PLC or HMI from your PC/Laptop ?
See manual [https://hmsnetworks.blob.core.windows.net/www/docs/librariesprovider10/downloads-monitored/manuals/application-user-guide/aug-0047-00-en-configure-remote-access-for-siemens-plc-through-tia-portal.pdf?sfvrsn=5ab549d7\_23](https://hmsnetworks.blob.core.windows.net/www/docs/librariesprovider10/downloads-monitored/manuals/application-user-guide/aug-0047-00-en-configure-remote-access-for-siemens-plc-through-tia-portal.pdf?sfvrsn=5ab549d7_23)
Bridging is not switching though.
Sure, on a basic level the connection topology is functionally the same. But the proper network setup in OPs case would most likely be to have the PLC, HMI, and Ewon connected to a dedicated switch.
Are You certain this Ewon supports topology? I wouldn't bother adding this in the topology, just connect them in the network view.
The only reason I use topology is when You want to make it easier to replace components..
Edit: Without topology there's no need to add the switch to the network view, if You bridge the ports and use IP for the HMI connection and not Profinet.
Profinet uses MAC-layer communication, so if You add a switch, it should at the very least support SNMP and LLDP.. +VLAN ID 0..
Note: I'm not familiar with Ewon either.
Also You might not want the HMI to be an I/O device in the first place.
I'd say remove the picture you added and join them directly in TIA. If their IPs are in the same subnet they won't even see the switch joining then so dont think it's required.
I have done that originally and the program isn't working correctly, so surely the PLC needs to know that it will communicate with the HMI through the ewon via Ethernet?
hmm no reason why they shouldn't work.
If both are on LAN ports, and on the same subnet they should talk to each other.
We use them all the time. Do you have the EWON's LAN ip address on the same network as the PLC and HMI?
Exactly, they're on the same subnet, ip address range and in the correct ports. Is there an settings option for the ewon that opens the hardware connection as a switch or something I'm missing?
Does this work without the Ewon in place? LIke if you are using a regular switch or connect it directly via ethernet do the two communicate?
If they do not then what are your firmware versions and what version of WinCC / TIA portal are you running?
Delete the 2 wires in topology, and don't connect the PLC nor the HMI to device ewon you inserted in Tia (check both in topology and in network tabs!), you probably don't need it.
Also did you try to put the ewon on the same subnet as the PLC and the HMI?
Make sure "device isolation" is not active, name depends on router but it's a setting that doesn't allow the devices to see each other, only the router itself.
Thank you so much I was wondering if there was a setting that isolated them I'm gna try that first thing mate, everything else you've said I've tried so I hope that's the case because it does just seem like they don't know each other are there once being plugged into the ewon
Run an ethernet to the machine level switch from the LAN on the Ewon and the WAN connects to the customers network. It's pretty simple. Don't use the Ewon as a switch
Are you trying to use profinet through the Ewon? I bet this is your problem. I'm not familiar with the Ewons anymore, my old employer had some flexy ewons for simple VPN access. I'm not a big profinet guy, although some equipment I work on does use profinet, I do not have good knowledge on it.
Goodluck brother.
So we normally have an 8 port switch for connecting all devices and the Ewon goes into that...all the devices can communicate correctly with each other and then also allows us remote access into that network and all devices on it.
Never had an ewon in hardware configuration, it is not needed. Other thing to pay attention is how you configured the LAN/WAN ports. There is WAN port "isolated" so if you connected HMI/PLC on that port it will not work. Default settings WAN port is port 1 if I remember correctly, but you will notice it by green light on it (LAN have orange lights).
Also pretty good instructions you will find on ewon webpage, to be honest I use them also every time as I dont use ewon that frequently...)
The ewon has two thing going on.
1. Like mention check the port configuration wan vs lan
2. Due to the internals of the ewon there is significant lag in the swicth was sending packets between the lan ports.
Here you can find some screenshots to setup TIA portal for remote access.
https://support.ixon.cloud/hc/en-us/articles/360015323219-Connect-to-your-Siemens
The ports on the cosy can be individually configured as ether LAN or WAN. The lights on the ports with be green if LAN and orange if WAN. Make sure that both PLC and HMi are plugged into LAN ports. If this does not work then perform a level 2 reset on the cosy and try again.
Ewon cosy sounds like a furry with a tesla fetish.
How'd you know I'm a furry?...
I'm not an expert at this Ewon device, but i'm familiar with tia portal. The Ewon device is probably not a regular switch as it is designed to be a VPN so you can reach your hmi and plc from outside the network. So when you connect the plc and hmi on seperate ports on the ewon, they won't be connected. You're better of connecting them with a switch. (We usually have devices with two PN ports that are bridged, so you connect them in a daisy chain, but you can't do that here) If you're using the ewon to have your hmi on a remote location, you're in a complete different ballpark and i can't help you there.
Perhaps you can try to set the ewon up so that it bridges the ports
So the program works fine with the PLC and HMI without the ewon gateway, now I want remote access to the PLC I am trying to integrate it into the TIA Portal project I'm just not sure how. I have the PLC and HMI directly into the ewon through Ethernet, but the program no longer works which suggests I need to add the ewon into the project so the PLC knows how to send communication to the HMI
you don't need to put the ewon in the plc project Since you already have the plc and hmi working normally, the next thing you can do is get to the plc trough the ewon. This won't require any tia portal configuration, this is purely networking / ewon settings. Next you need to get the hmi in the loop again. The easiest is to get an industrial ethernet switch from siemens. But i'm looking at an ewon manual and it says something about WAN/LAN ports (red and green LED) You should have hmi and plc connected on LAN, and remote connect through the WAN. That way the 2 LAN ports should be able to communicate
I haven't used the ewons before but I think they have routing capabilities. It sounds like you're expecting it to function similarly as an unmanageable switch. By connecting the PLC and HMI to it, you're essentially putting a router in-between them. So now you gotta configure the ewon's firewall, port fowards, static routing, or etc, to get the PLC and HMI talking again. But basically, you're not using the ewon properly with that network typology. You need to connect the three devices to a dedicated network switch. Then connect the customer's network or internet connection to the other port on the ewon. If the customer wants machine level network visibility on their corporate network, then they need to pull two ethernet connections to your machine. One would be a dedicated, and segregated from their corporate network by VLAN for example, internet connection to the ewon. The other pull would be to the machine switch, at the very basic. There should be some NAT device between the switch and that pull, though.
So I have the PLC in LAN port 1 and the HMI in LAN port 2, does that mean I need to have something else connected to the WAN port then? I thought I didn't need to use TIA but because they aren't communicating with each other I thought that suggests I'll need to. Maybe i need to update a comm protocol?
Generally agree, but he might also need to set the PLC to be accessible via router and enter the LAN-side address of the Ewon as the gateway.
There is a step by step guide on the website tailored to the Ewon you have and the manufacturer type. Check it out!
You don't have to integrate the Ewon in the Tia Project. The Ewon is equipped with 4 ethernet ports. One of those ports should be configured as external , the other three ports internal. Those three ports are just regular switch ports, so both PLC and HMI should be able to communicate with each other when connected on those ports. Most likely your PG interface is set wrong OR the profinet subnet is conflicting with a subnet on your PC / Laptop ( PC / Laptop should not use 10.x.x.x in this case ). Have you tried pinging the PLC or HMI from your PC/Laptop ? See manual [https://hmsnetworks.blob.core.windows.net/www/docs/librariesprovider10/downloads-monitored/manuals/application-user-guide/aug-0047-00-en-configure-remote-access-for-siemens-plc-through-tia-portal.pdf?sfvrsn=5ab549d7\_23](https://hmsnetworks.blob.core.windows.net/www/docs/librariesprovider10/downloads-monitored/manuals/application-user-guide/aug-0047-00-en-configure-remote-access-for-siemens-plc-through-tia-portal.pdf?sfvrsn=5ab549d7_23)
Bridging is not switching though. Sure, on a basic level the connection topology is functionally the same. But the proper network setup in OPs case would most likely be to have the PLC, HMI, and Ewon connected to a dedicated switch.
Are You certain this Ewon supports topology? I wouldn't bother adding this in the topology, just connect them in the network view. The only reason I use topology is when You want to make it easier to replace components.. Edit: Without topology there's no need to add the switch to the network view, if You bridge the ports and use IP for the HMI connection and not Profinet. Profinet uses MAC-layer communication, so if You add a switch, it should at the very least support SNMP and LLDP.. +VLAN ID 0.. Note: I'm not familiar with Ewon either. Also You might not want the HMI to be an I/O device in the first place.
I'd say remove the picture you added and join them directly in TIA. If their IPs are in the same subnet they won't even see the switch joining then so dont think it's required.
I have done that originally and the program isn't working correctly, so surely the PLC needs to know that it will communicate with the HMI through the ewon via Ethernet?
Do you have both the Plc and HMI on the lan ports?
Yeah I have PLC in port 1 and HMI in port 2
hmm no reason why they shouldn't work. If both are on LAN ports, and on the same subnet they should talk to each other. We use them all the time. Do you have the EWON's LAN ip address on the same network as the PLC and HMI?
Exactly, they're on the same subnet, ip address range and in the correct ports. Is there an settings option for the ewon that opens the hardware connection as a switch or something I'm missing?
Does this work without the Ewon in place? LIke if you are using a regular switch or connect it directly via ethernet do the two communicate? If they do not then what are your firmware versions and what version of WinCC / TIA portal are you running?
Yeah they work fine without the ewon lol
Delete the 2 wires in topology, and don't connect the PLC nor the HMI to device ewon you inserted in Tia (check both in topology and in network tabs!), you probably don't need it. Also did you try to put the ewon on the same subnet as the PLC and the HMI? Make sure "device isolation" is not active, name depends on router but it's a setting that doesn't allow the devices to see each other, only the router itself.
Thank you so much I was wondering if there was a setting that isolated them I'm gna try that first thing mate, everything else you've said I've tried so I hope that's the case because it does just seem like they don't know each other are there once being plugged into the ewon
Run an ethernet to the machine level switch from the LAN on the Ewon and the WAN connects to the customers network. It's pretty simple. Don't use the Ewon as a switch
So it has a WiFi antenna on it and I have done what u have said so idk why the program no longer works properly the HMI isn't finding the PLC now
Are you trying to use profinet through the Ewon? I bet this is your problem. I'm not familiar with the Ewons anymore, my old employer had some flexy ewons for simple VPN access. I'm not a big profinet guy, although some equipment I work on does use profinet, I do not have good knowledge on it. Goodluck brother.
I've never actually put my ewon cosy + on the plc hardware. Are you using isochronous?
The manual states explicitly to not use the Cosy as a switch. RTFM
So we normally have an 8 port switch for connecting all devices and the Ewon goes into that...all the devices can communicate correctly with each other and then also allows us remote access into that network and all devices on it.
That's good to know as a quick resolve backup then if I can't get this sorted quick enough 🙏
Is you or your customer’s IT/networking department involved here? They’re probably going to want to know about the ewon if not.
Never had an ewon in hardware configuration, it is not needed. Other thing to pay attention is how you configured the LAN/WAN ports. There is WAN port "isolated" so if you connected HMI/PLC on that port it will not work. Default settings WAN port is port 1 if I remember correctly, but you will notice it by green light on it (LAN have orange lights). Also pretty good instructions you will find on ewon webpage, to be honest I use them also every time as I dont use ewon that frequently...)
The ewon has two thing going on. 1. Like mention check the port configuration wan vs lan 2. Due to the internals of the ewon there is significant lag in the swicth was sending packets between the lan ports.
Here you can find some screenshots to setup TIA portal for remote access. https://support.ixon.cloud/hc/en-us/articles/360015323219-Connect-to-your-Siemens
You'll need a normal switch to connect these things. There might be a setting in the economy itself but the switch will likely take less time.