I have a piece of equipment using a Moxa NAT-102 to access our shopfloor network. I have the NAT configured to where I can find the CPU in RSLinx and get online from my desk so I know the translation is working. The CPU is a 1769-L30ER v32.11 and the NAT firmware is 1.00.
To setup the OPC device connection in Ignition I am using the Allen-Bradley Logix Driver and entering the translated (shopfloor) network address, same as I have in the RSLinx driver and leaving all other settings at the default. After saving the configuration the status just says, 'ReconnectWait'. I don't see anything in the Ignition or Moxa logs that appears to reference the OPC traffic.
Has anyone had any similar experiences or any ideas what to look at?
Is the Ignition Gateway on the same subnet and VLAN as the Moxa?
The Logix Driver you use for a CompactLogix L30 talks on port 44818, which should be the same port that RSLinx talks to the processor on. You won't see a difference in the traffic except the source IP.
Yes, the gateway and Moxa are on the same subnet and VLAN. We have several other L3x PLCs that are communicating through 1783-NATRs on the same network without problem and I verified that all the settings are the same (except IP address). Port 44818 is what's configured in all the drivers, including the Moxa.
For clarity, is "shopfloor" network on the private network, where the control equipment lives? If so, you'll want to enter in the translated IP (on the "office" network) into Ignition.
Do you have access to a command line interface from your Ignition gateway?
If so, can you try to ping the office address from the Ignition gateway? The Moxa NAT devices do have some varying levels of firewall rules that can be configured. A ping request might be a good starting point.
No, shopfloor is the "public" network here. The private PLC network is 10.10.10.x and the public (shopfloor) network is 10.0.49.x - in this case I use the NAT to translate the PLC from 10.10.10.5 to 10.0.49.128, which is what I used in Ignition.
What ended up happening is the NAT created a secondary IP that took the Ignition server IP address. I had to remove that secondary IP and now everything is working. Moxa didn't have a good reason for why the NAT device created that secondary IP.