CompactLogix can't communicate over NAT 1:1


#1

@anonocflzesv
Hi Leo,

I went over the Rockwell literature (https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/enet-rm002_-en-p.pdf) and didn’t see any reason why this shouldn’t work.

Can you check a couple settings in the eWON for me? In the Setup/System/Storage/Edit COM cfg check that:

NatItf=2
FwrdToWAN = 1

Kyle


#3

Kyle,

The settings you listed below are set properly. We have the NAT function working, but where we are at now is being able to get the produce/consume function to work. Any tips or ideas, please let us know.

Regards,

JEFF KLEIN • Automation Support Specialist


#5

Are you using EthernetIP/CIP, ModbusTCP, Ethernet w/PLC-5 mapping?


#6

We are using ethernetIP

JEFF KLEIN • Automation Support Specialist

P: +1-651-769-8115 • F: +1-651-768-5204 • M: +1-651-343-4117

JKlein@WernerElec.com

WERNER ELECTRIC - Solution • Supply • Support

7450 95th Street South, Cottage Grove, MN 55016

www.wernermn.comFacebookTwitterYouTube

https://www.wernermn.com/wernersig.png


#7

And your tags are unicast?


#8

Correct. I found a post on your forums where he is doing something similar and is also unable to get the produce consume working.

See below

anon1118574648

May '18

Hi Rich!

Good news! We are communicating. Several dumb things I did / didn’t do:

· I didn’t need to have the extra line to assign the WAN side PLC (192.168.1.90 – 10.10.4.1). The eWON already had that line covered, and the settings allowed the LAN PLC to talk to the WAN PLC. Once this line was removed, their RSLinx was able to see my PLC. I never did see their PLC on my RSLinx, but that didn’t matter

· On the configurations inside my (AB) PLCs (both LAN and WAN), I needed to remove the default Rack Optimization for the Ethernet Card set up. I almost always forget that, since I don’t have to do this too often. The IP address for the WAN PLC is its true 10.10.4.1. The IP in the address for the LAN PLC is also its WAN IP 10.10.4.30 (or 31, depending on the unit). https://hms-networks-s3.s3.amazonaws.com/original/2X/e/e2cc571b025c47e5527ad032e47b71bc4b71349c.jpg

See above for the remote PLC Ethernet card configuration in the LAN PLC.

We did have some issues with the produce / consume tags that we were trying to use. The live status indication on either PLC for the remote Ethernet card kept cycling through “Connecting…” and “Timeout…” (or something like that). We ended up using messaging, with each PLC reading the others source file (produced tags – but we changed the tags to base instead of produce type). We even had to pulse the message statements on short timers to allow the devices in the NAT to keep up with each other.

The end result, although I would have loved to keep the produce / consume function (AB website states that it should work, but I had to get in a taxi to start heading home) is that we are now communicating, and I am writing up this experience so that our office won’t have to bother you with THIS problem again, although I will probably be in touch before you want me to be. I am also sharing this with you in hopes that it will help you guy, the guy in eWON who was helping, and maybe someone else will share how to get that darn produce / consume working in this format.

Thanks to you and Deryck for helping as much as you did. Your information and questions helped guide us and move forward in our trouble shooting (we sat in a hole without email / Internet support while we worked this crud out). I look forward to an easier time, next time. If there are any manuals to help us work out the settings for the advanced eWON settings, please feel free to forward it (them – or their links).

Our next project should be right around the corner…

Best regards.

**Glen

JEFF KLEIN • Automation Support Specialist

P: +1-651-769-8115 • F: +1-651-768-5204 • M: +1-651-343-4117

JKlein@WernerElec.com

WERNER ELECTRIC - Solution • Supply • Support

7450 95th Street South, Cottage Grove, MN 55016

www.wernermn.comFacebookTwitterYouTube

https://www.wernermn.com/wernersig.png


#9

I’m starting to feel like this particular transaction you are trying to do between the 2 PLC’s (produce/consume) is a Layer 2 transaction that is not going to work over NAT. But of course, this is a question that Rockwell is going to have to answer… have you spoken to anyone there? I will continue to research as well…


#10

But… this doc seems to suggest it’s Layer 3. Have you seen this: https://rockwellautomation.custhelp.com/app/answers/detail/a_id/50977

you are using version >=16?

Check this doc if you havent’ yet.


#11

We are using unicast, and we are up to V31 right now. So we are good there. I guess I’m confused where you see that unicast would be layer 3?

JEFF KLEIN • Automation Support Specialist

P: +1-651-769-8115 • F: +1-651-768-5204 • M: +1-651-343-4117

JKlein@WernerElec.com

WERNER ELECTRIC - Solution • Supply • Support

7450 95th Street South, Cottage Grove, MN 55016

www.wernermn.comFacebookTwitterYouTube

https://www.wernermn.com/wernersig.png


#12

What I was noting is that the unicast produce tags should be able to be routed:


#13

Have you guys ever used Wireshark?


#14


#15

Here is another doc that may help… states that routing produced and consumed tags is possible, but not “supported.” (page 12)

Logix5000_Produced_Consumed_tags.pdf (2.2 MB)


#16

Kyle,

Thanks for this. I will look into it. I will be digging more into this today so I’m sure you’ll hear back from me later.

Regards,

JEFF KLEIN • Automation Support Specialist

P: +1-651-769-8115 • F: +1-651-768-5204 • M: +1-651-343-4117

JKlein@WernerElec.com

WERNER ELECTRIC - Solution • Supply • Support

7450 95th Street South, Cottage Grove, MN 55016

www.wernermn.comFacebookTwitterYouTube

https://www.wernermn.com/wernersig.png


#17

Kyle,

See attached from Rockwell. Their NATR device is capable of produce consume through NAT. We’ve tried multiple configurations and still get the same result, so I think that this might not be possible with the Cosy.

Regards,

638107 - Produced_Consumed tags Through a Network Address Translation Connection.pdf (602 KB)


#18

Jeff,

Thanks for sharing that. Looks like there is no special configuration required (other than NAT 1:1 and unicast), it just works with their router. I will try to find out more about how they implemented this, but in the meantime I think you’re right that the Cosy isn’t going to work in that configuration. I’ll let you know if I find anything out. Good luck with your project.

Kyle