PC Interface and Industrial LAN Routers

Robot Controller
1

I am trying to connect to 2x 6620 robots remotely through the PC Interface. I have a eWon 2055CD industrial LAN Router connected to the internet on a fixed IP address.

I can access the robots via my laptop when directly connected onto the switch side of the router and see both robots and PLC, but when I try to access via the internet through the LAN Router’s VPN tunnel, I can only see the PLC. I can’t even ping the robots! I have been trying to get this setup to work with help from the eWon rep with no success yet and time is running out. I have tried mapping all the necessary ports mentioned on both TCP/UDP/FTP mentioned in the ABB documentation,

  1. Has anyone out there managed to successfully work a eWon with ABB (I know ABB use eWons for their own remote diagnostic service). How do you do it?

  2. Has anyone used an alternate vendor (rather than eWon) successfully to access the PC Interface via internet VPN?

Cheers

2

Be aware that your IP-adress is in the same range as the adress of the controller, otherwise it will not work.
We are working with eWonn succesfully with VPN

Good Luck :neutral_face:

3

I am running different IP address ranage (eg 192.168.1.1 and 191.16.1.1) so there is no conflict.

I can access the eWon through Talk2M via there server, just not through the My Connections TAB in eCatcher.

Can you connect throguh both methods?

4

No problem with both methods.

Make sure the UPD is not blocked in the firewall.

What I ment with the IP range is, that the ip-adress you get after connection with the eWonn must be in the same range as your ABB controller.

So eWonn 192.168.10.x (255.255.255.0)
Than your controller has to be 192.168.10.2 for example

5

I am interested in adding an eWon to existing robots we have in the field. I assume we use the LAN connection but do we need to have Option 616-1 PC Interface or is just setting the IP on the LAN connection good enough to get us in?

6

You do need the PC-Interface option to access the robots remotely unfortunately.

7

I assume the PC-Interface be added with a new key string?

8

Yes you need a new key string to add PC interface to the system

9

Hi there,

Same problem over here. My hardware:

-IRB 2600 RW6.03.02 w TCP/IP master/slave
-eWon Cosy
-PC Interface
-Allen Bradley PLC TCP/IP
-Beckhoff Fieldbus Box TCP/IP as periphery I/O for Axis 3.

My current net schedule:
-eWon to WAN thru direct cable
-eWon to Switch
-Allen Bradley to switch
-Beckhoff to Switch
-Switch to LAN2

So, if I put Private LAN and WAN in the same subnet: 192.168.250.xxx, it pops up an IP Address Overlap. I changed Private LAN to 192.168.251.xxx and no error, but, the problem is that PLC and Robot gonna be in diferent subnets, (both were 250 before), so connection will be lost. Otherwise, if I changed WAN to 251 instead private LAN, I’m not gonna have connection to PLC & Robot at the same time…

There is any way to have both on the same subnet???

Thanks for your time buddies.

10

Try connecting the switch to the LAN3 port as this is configured as an isolated network (as default).

11

What do you want to connect to the LAN3? The Ewon, the PLC or the Beckhoff I/O Module?

On Ethernet IP, the PLC and beckhoff goes on private LAN, so LAN2, no on isolated LAN3 like Profinet.

12

Actually if you configure the LAN3 as private you can connect the PLC to LAN2, the Beckoff to LAN3 and the Ewon to WAN no need for an external switch?

13

That’s it. You will have 2 ethernet ports for industrial communication, and the WAN for the public.

14

What’s the way to connect an eWon(Public) and a PLC(Private LAN) with the same subnet? I have an IP Address Overlap fault. I’ve even tried with a A Class IP, and still have the same fault. I would like to have only one eWon for the remote connection to PLC and Robot all together…