6 - 4 WBPEEUI240751C0
Labels
Device Label
All I/O blocks must have a device label assigned to communi-
cate on Hnet. The Harmony controller uses the device labels to
direct messages to specific I/O blocks and to identify the
source of any received messages. In the control configuration,
device labels map function codes to specific I/O blocks.
Electronic ID
Each I/O block has a unique electronic ID. This ID is fixed in
memory and cannot be modified. This method of identification:
• Eliminates the need for a physical address switch that
must be uniquely set and subsequently recorded for identi-
fication and configuration purposes.
• Removes any hardware address management requirements
necessary to insure each I/O block has a unique identifier.
• Simplifies configuration.
The identification label, which is physically adhered to the
front panel of the I/O module, gives the electronic ID of the
I/O block; refer to I/O Module Front Panel
I/O Module Front PanelI/O Module Front Panel
I/O Module Front Panel in Section 7 for fur-
ther description. The electronic ID does not
notnot
not need to be remem-
bered or recorded for use in configuration. User-defined device
labels are used instead. The Harmony controller automatically
associates device labels with electronic IDs during the device
labeling process.
Establishing a Device Label
When an I/O block is first removed from its packaging or after
it has been initialized, it does not contain a device label. The
device labeling procedure explained in the Primary Interface
Primary InterfacePrimary Interface
Primary Interface
instruction must be performed to establish the label. Once
established, the label is retained by the block. The block can
be removed and reinstalled without requiring a new label to be
assigned.
NOTES:
1. An I/O block needs to be relabeled after performing a firmware download.
After copying firmware from one block to another, both the source block and
the destination block must be relabeled.
To Next Page
Loading...
