Rack contains slots of I/O; all I/O, even ethernet or messaged I/O, must be defined on a slot and rack. Rack IDs must be unique for the entire plant. In the case of ethernet or messaged I/O, this may be a virtual rack or a spare slot in an existing rack.
- Select the I/O tab and then the Rack sub-tab.
- Scroll to the bottom of the table and highlight the empty bottom row.
- Enter information for the following items:
Name – Any alphanumeric name. Typically, typically just Rack followed by its ID.
Slots – This just lists all the slots configured on the rack.
IP Address – (optional) a rack may contain an IP Address which is only required if this rack will contain a controller in a distributed system.
P2P Slot – (optional) a P2P Slot # that contains the ethernet module for peer communications.
Enclosure – (optional) name of enclosure holding the rack.
Area – (optional) physical location of the rack
Description – (optional) Enter a description of the rack.
ID – Pick a unique rack ID; 0 is typically used for the local controller rack but not required. The ID is limited by the size of the RSlots array in the controller. An array size of 500 would allow for 5 racks, 0-4.
Size – (optional) enter the anticipated number of slots (for documentation purposes only.