RBergmann
Member
I'm in the middle of writing code for a SLC 5/05 and PanelView Plus on an Ethernet connection.
I've found from past experience that the most difficult part of programming an Allen-Bradley networked configuration is communication among all the components.
Here's my question:
Before being able to test out communications, the enclosure had to ship out to the site with both the PLC and OIT installed. I'd like to have both (PLC and OIT) shipped back to me so that I can validate what I've written so far, but I don't know if the PLC will accept OIT commands if the "Phoenix" style connectors (wired to the I/O) are removed. A-B units seem to be pretty smart about what's hanging off their buss. I think that I have to have all the modules installed on the rack to make this work, and I can have this, but don't want the wiring removed at the site, just disconnected. Is any of this of a correct assumption on my part? Is there a way to run bench tests on this hardware with the connectors removed?
... rab
I've found from past experience that the most difficult part of programming an Allen-Bradley networked configuration is communication among all the components.
Here's my question:
Before being able to test out communications, the enclosure had to ship out to the site with both the PLC and OIT installed. I'd like to have both (PLC and OIT) shipped back to me so that I can validate what I've written so far, but I don't know if the PLC will accept OIT commands if the "Phoenix" style connectors (wired to the I/O) are removed. A-B units seem to be pretty smart about what's hanging off their buss. I think that I have to have all the modules installed on the rack to make this work, and I can have this, but don't want the wiring removed at the site, just disconnected. Is any of this of a correct assumption on my part? Is there a way to run bench tests on this hardware with the connectors removed?
... rab