This is a convo betweeen Dragon4Death and ryanlupo over at our discord server:
Dragon4Death:
I'm only sort of following since I'm currently working, but I have had mixed results with Logix Echo using the same IP address as the server IP address. Instead, in your Logix Echo setup configure your processor to have an IP address of None and add a second processor (Slot 16 is where I have mine) as a comms pass-through and then use the ProcessorSlot to choose the slot it is located in.
ryanlupo:
I don't understand... I'm gonna have two PLC running in Echo?
Dragon4Death:
Two processors in your rack, but only 1 processor that you have to manager and download to. The processor in slot 16 will be just a comms pass-through processor.
Setup your comms-pass through to be in slot 16 with it pointing to your server IP address. Then in your Pylogix script you'd point to your server IP with the comms.ProcessorSlot = 0 (Assuming the processor you're using is in slot 0)
(Pylogix defaults to slot 0, so it'd work without it, but I'm hoping it clarifies things a bit.)
I can give an example in a minute.
ryanlupo:
Like this?
Dragon4Death:
You need to turn your device on (Esssentially like power for the processor) and then you'd download to that processor through the backplane of the 192. 168.30.64 using FactoryTalk Linx.
In Pylogix you'd use the 192.168.30.64 IP address. Since you're using slot 0 you don't need to specify the slot.
'm currently talking to several different Logix Echo processors with Pylogix, so I know it works.
[11:16 AM]
I am using FactoryTalk Logix Echo v3 with the May 2024 patches installed.
ryanlupo:
And the real PLC are with none in the IP adress, correct?
Dragon4Death:
did that work at all?
ryanlupo:
With the controller is everthing ok, now i'm gonna try to read the tags!
IT READSSSSSS!!!! Thanks guys!
This is a convo betweeen Dragon4Death and ryanlupo over at our discord server:
Dragon4Death:
I'm only sort of following since I'm currently working, but I have had mixed results with Logix Echo using the same IP address as the server IP address. Instead, in your Logix Echo setup configure your processor to have an IP address of None and add a second processor (Slot 16 is where I have mine) as a comms pass-through and then use the ProcessorSlot to choose the slot it is located in.
ryanlupo: I don't understand... I'm gonna have two PLC running in Echo?
Dragon4Death: Two processors in your rack, but only 1 processor that you have to manager and download to. The processor in slot 16 will be just a comms pass-through processor. Setup your comms-pass through to be in slot 16 with it pointing to your server IP address. Then in your Pylogix script you'd point to your server IP with the comms.ProcessorSlot = 0 (Assuming the processor you're using is in slot 0) (Pylogix defaults to slot 0, so it'd work without it, but I'm hoping it clarifies things a bit.) I can give an example in a minute.
ryanlupo: Like this?
Dragon4Death: You need to turn your device on (Esssentially like power for the processor) and then you'd download to that processor through the backplane of the 192. 168.30.64 using FactoryTalk Linx. In Pylogix you'd use the 192.168.30.64 IP address. Since you're using slot 0 you don't need to specify the slot.
'm currently talking to several different Logix Echo processors with Pylogix, so I know it works.
[11:16 AM]
I am using FactoryTalk Logix Echo v3 with the May 2024 patches installed.
ryanlupo: And the real PLC are with none in the IP adress, correct?
Dragon4Death: did that work at all?
ryanlupo: With the controller is everthing ok, now i'm gonna try to read the tags! IT READSSSSSS!!!! Thanks guys!