1783 NATR Switch

› PLCGurus.NET Live & Interactive Forum › PLC Questions and Answers › Rockwell, Allen-Bradley, Stratix › 1783 NATR Switch

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • January 23, 2019 at 8:45 pm #3683
    jctingsonjctingson
    Participant
      Karma: 33
      Rank: Padawan

      H I need help, I have this set up

      PC- ip address is 10.104.43.123, 255.255.255.0

      NATR-Public ip address is 10.104.43.217, 255.255.255.0
      -Private ip address is 192.168.0.85, 255.255.255.0
      NAT Rule: 10104.43.216 > 192.168.0.80

      PLC- ip address is 192.168.0.80, 255.255.255.0

      what should I do since I cannot ping my plc?

      PS: I should not put gateway address to my PLC.

       

      Thanks

      -james

      January 23, 2019 at 9:12 pm #3684
      PLCGurutfgmedia_admin
      Keymaster

        Hi James and welcome to the forums!

        I’m a little confused by why you say you should not put a gateway address in the PLC? For NAT translation to work you need to setup the gateway translation which requires a gateway address in the PLCs. Perhaps it’s not clear what you were trying to communicate. Our moderators are ready to help!

        January 24, 2019 at 4:48 am #3686
        jctingsonjctingson
        Participant
          Karma: 33
          Rank: Padawan

          I cannot put gateway address in PLC because it has a password and the end-user doesnt want to redownload the program because a fault may occur. So now, Im having troubles to communicate with the plc thru 1783-NATR switch. I have read some conversation about making a rule to the PC’s ip address, and they dont need to set gateway to plc, and Im asking if it is possible.

           

          January 24, 2019 at 8:23 am #3687
          AlexAlex
          Participant
            Karma: 14
            Rank: Padawan

            The key is to make sure you can see devices on the public side and private side with RS Linx. You did not say whether you created a standard Ethernet driver in RS Linx and then created mapping for the driver.  You must do this step to allow RS Linx to route the traffic.

            If you cannot see the device in RS Linx, no mapping is going to take place.

             

            regards,

            Alex

            Attachments:
            You must be logged in to view attached files.
          • Author
            Posts
          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.