« previous next »
Pages: [1]

Author Topic: PLC IP address when going through another rack  (Read 2270 times)

agent64usa

  • Newbie
  • *
  • Posts: 2
    • View Profile
PLC IP address when going through another rack
« on: August 25, 2018, 02:56:50 PM »
So for a contrologix PLC, the comms path in RSLinx is:  192.17.168.100\Backplane\1\A\192.17.168.99\Backplane\0

How do I go about typing this in AdvancedHMI? Thanks.
Logged

bachphi

  • Hero Member
  • *****
  • Posts: 690
    • View Profile
Re: PLC IP address when going through another rack
« Reply #1 on: August 25, 2018, 04:49:16 PM »
Interesting question! Although your example is using the same subnet, but it can be different. For example, slot 1 for external network ( 134.200.73.202) and slot 11 for internal network (192.168.1.10). May be you can try

134.200.73.202.1.11.192.168.1.10.1.0
Logged
UCL =================
This is NOT alt.read.my.mind.
No such thing is sh^t-for-brains unless you are posting to alt.read.my.mind.
My understanding of computer is well below six Σ.
Unless what I am saying is logically defined in a PLC, everything else might be beyond my control.
LCL =================

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5359
    • View Profile
    • AdvancedHMI
Re: PLC IP address when going through another rack
« Reply #2 on: August 25, 2018, 11:19:08 PM »
I'm thinking the RoutePath should be:

1,1,2,192.17.168.99,1,0
Logged

bachphi

  • Hero Member
  • *****
  • Posts: 690
    • View Profile
Re: PLC IP address when going through another rack
« Reply #3 on: August 26, 2018, 01:28:49 PM »
How rusty I am! I have not touched the CLX platform during the past few years.
Continuing with my example, I'd need to specify the target PLC (192.168.1.11)

Path: 1,11,2,192.168.1.11
or      1,11,2,192.168.1.11,1,0
or      134.200.73.202,1,11,2,192.168.1.11,1,0     to access from external network

Is it correct?
« Last Edit: August 26, 2018, 01:50:00 PM by bachphi »
Logged
UCL =================
This is NOT alt.read.my.mind.
No such thing is sh^t-for-brains unless you are posting to alt.read.my.mind.
My understanding of computer is well below six Σ.
Unless what I am saying is logically defined in a PLC, everything else might be beyond my control.
LCL =================

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5359
    • View Profile
    • AdvancedHMI
Re: PLC IP address when going through another rack
« Reply #4 on: August 26, 2018, 05:36:25 PM »
The way I remember route paths is first they always come in pairs. Then to think of it as going out a door to an address.

So the first pair of 1,1 says to go out the "back door" or backplane to the address of slot 1 (which I assume is an Ethernet card)

The next pair of 2,192.17.168.99 says to go out the first front door (A) of the Ethernet card, then to address 192.17.168.99

Once arrived it should then go out the back door (backplane) then to slot 0 which give the final pair of 1,0
Logged

agent64usa

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: PLC IP address when going through another rack
« Reply #5 on: September 05, 2018, 02:13:41 PM »
So if I understood correctly, it is supported by the comms driver and just a matter of specifying the correct path. I'll give it a shot and let you guys know, thanks for the help.
Logged

bachphi

  • Hero Member
  • *****
  • Posts: 690
    • View Profile
Re: PLC IP address when going through another rack / Connection Path
« Reply #6 on: February 11, 2019, 09:02:18 PM »
Good example of Connection Path

Logged
UCL =================
This is NOT alt.read.my.mind.
No such thing is sh^t-for-brains unless you are posting to alt.read.my.mind.
My understanding of computer is well below six Σ.
Unless what I am saying is logically defined in a PLC, everything else might be beyond my control.
LCL =================
Pages: [1]
« previous next »