Jim Hortenberry

MrPLC Member
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jim Hortenberry

  • Rank
    Hi, I am New!

Profile Information

  • Country United States
  1. 1783-NATR Modbus TCP

    NATR received. We've run it across our MB Simulator and everything is working... MB Sim  (@ 192.168.1.131/24 GW 192.168.1.1) < -- [Modbus TCP on Port 502] -- > KepWare OPC (@ 10.0.11.123/24 GW 10.0.11.1) NATR Config:          Public IP:  10.0.11.139/24 GW 10.0.11.1          Private IP:  192.168.1.1/24 GW <blank>          Network Address Translation:                   Public IP (Translated):  10.0.11.131                   Private IP (Destination):  192.168.1.131 NOTE:  Private IP (Destination) should be actual IP addresses (physical devices) in the NAT'd area with each device Gateway set to the NATR Config Private IP (192.168.1.1). Custom Rule:            tcp/udp          502   We'll get real hardware to validate against over the next few days...        
  2. 1783-NATR Modbus TCP

    Thanks for the replies... I have a demo unit on the way...we'll test and post the results.  
  3. 1783-NATR Modbus TCP

    Has anyone successfully used a 1783-NATR for Modbus TCP communication between a ProSoft MNET card (in the ControlLogix rack) and a Modicon Quantum? ProSoft MNET:  10.x.y.z Modicon Quantum:  192.168.1.x There is one (1) ProSoft MNET and four (4) Modicon Quantum's. NOTE:  I know there are other devices that support this behavior...the NATR is the suggested standard hardware.  We are getting various responses from distribution and support.  ...I was hoping someone in the community could confirm.   Thanks for your time!