Setup guide
Setting up the Host to Reference the I/O Rack
24
The "Board Name" and "Map Type" may be left at their defaults.
"Slot Number" should be set to the I/O slot number (1 through 8) in the I/O Expansion Rack
which holds the corresponding board. NOTE: I/O slot 1 is equivalent to the 3
rd
slot in the chassis,
I/O slot 2 is the 4
th
slot in the chassis, etc. Also, be aware that slot numbering between I/O
rack(s) and local I/O in the host controller does not conflict, i.e. you can have the same slot
number used in multiple I/O racks, and in the host ControlWave, because the IP addresses
identify them as residing in different physical devices.
"IP Address" should be set to the IP address for the I/O Expansion Rack's Ethernet Port (see
Defining an Ethernet Port earlier in this manual).
"Related Task” allows you to associate this board with a cyclic task in your project.
“Redundant Expansion Rack” should only be checked if this I/O Expansion Rack is a member
of a redundant pair of I/O Expansion Racks, used in conjunction with the ControlWave
Redundant I/O Switcher (CWREDIO). Checking this box causes software variables to be created
which are used to support redundant operations.
“Mark Variables as PDD OPC” determines how values of the I/O variables associated with
this board will be made available to other software programs. Checking “PDD” allows the
controller to reference variables by name, which is necessary if you intend to access a variable
by external software which requires ‘read-by-name’ access, such as DataView, or one of the
other Open BSI Utilities. Checking “OPC” adds this variable to a collection list used by the
OPC Server or by the Open BSI Signal Extractor. This is necessary when data is to be extracted,
and sent to a database.
Click on the [Show Detail Pins' Information] button to configure the I/O pins for the board. Pin
configuration varies somewhat depending upon the type of board being configured. See the
pages that follow for information on particular board types:
IMPORTANT:
It is recommended that you use the "Related Task" field to associate the board with an
executing task in the ControlWave project that uses data from this board. This ensures that
data will be requested from the board whenever the cyclic task using the data executes.