DISTRIBUTED I/O
EN0B-0090GE51 R0802
26
MMI. Such modules must be decommissioned using
the L
ON
W
ORKS
network management tool, or the
L
ON
W
ORKS
service pin must be pressed for at least
three seconds.
If an Excel 500 controller in the shared/open mode is deleted
from the LonMaker project, all of its bindings will also be
deleted. In this case, the deleted Excel 500 controller will
restore all of the autobindings (if any) automatically after 3
minutes (provided no bindings are performed or changed in
LonMaker in the meantime), but there will be numerous
system and application alarms as a result.
Assignment
The following refers to the assignment of Distributed I/O
modules to Excel 500 controllers into which controller
firmware version 2.04.xx has been downloaded.
There are two methods of assigning Distributed I/O modules
to a particular Excel 500 controller. Regardless of which of
these two assignment methods is employed, assignment
requires that the modules' rotary HEX switches be set
according to the CARE terminal assignment.
Recommended Assignment Method
The Ideal approach is to know the Neuron IDs of the Dis-
tributed I/O modules when engineering the application using
CARE, thus enabling you to enter the Neuron ID during the
CARE terminal assignment. When this is done, every module
will be fully identified and assigned automatically by the Excel
500 controller after the application is downloaded.
Alternate Assignment Method
If the Neuron ID is not available when engineering the
application using CARE, it will be possible to correctly assign
the Distributed I/O modules to their controller(s) only after
having downloaded the application. In this case, assignment
is performed via the MMI as described in detail in the
XI581/XI582 User Guide, EN2B-0126.
IMPORTANT:
It is essential that Distributed I/O modules
not
be
assigned simultaneously via different MMIs. When
using the alternative assignment method, work on
only one MMI at a time so as to avoid competing
network accesses. Disregarding this will result in
contradictory and unreliable assignments. There will
be incomplete Distributed I/O module lists displayed,
and there is the danger that one controller will take
away an existent assignment from another
controller.
Priority of Distributed I/O Module Assignments
Assignments made via an MMI always have priority over
assignments made using CARE. Thus, in the event of a con-
flict (e.g. when the Neuron ID entered using CARE differs
from the Neuron ID entered via the MMI), the assignment
carried out via the MMI will have priority.
Flashing of Distributed I/O Module Assignment
The Distributed I/O module assignment that was made in
CARE or via the controller MMI must be manually saved to
Flash memory. When Distributed I/O module assignment has
been made during the test mode, the assignments are
automatically saved in Flash memory. These assignments
can be reused for the application after the application has
been downloaded (the MMI's assignment dialog will offer the
option of keeping the existing assignment).
Controller Reset
IMPORTANT:
Resetting a controller will erase the Distributed I/O
module assignment. After a reset, one of the
following procedures must be performed.
•
Restore the application (including the assignments) from
Flash (this is the simplest method).
•
Restore the assignments during the "start-up" sequence
(this requires somewhat more effort because all of the
modules are searched on the LonWorks network
automatically).
•
Download the application and re-assign the Distributed
I/O modules (this method requires the most effort
because it must be done manually).
Manual Binding
The following refers to the manual binding of the NVs of
Distributed I/O modules to Excel 500 controllers into which
controller firmware version 2.04.xx has been downloaded.
There are several cases in which it is necessary to manually
bind the NVs of the Distributed I/O modules to their
respective controller(s). This is done using a L
ON
W
ORKS
network management tool (e.g. LonMaker).
More than 16 Modules per Excel 500
Autobinding can be used to bind the NVs of a maximum of 16
Distributed I/O modules per controller, only. If the application
requires more than 16 Distributed I/O modules per controller,
you must use CARE to allocate those additional NVs
requiring mapping with the data points, and you will also have
to use a L
ON
W
ORKS
network management tool to bind the
NVs of the additional modules to the controller.
Double-Mapping a Data Point
It is possible to preserve the autobinding by mapping the
data point with a second NV. However, the second NV must
then be bound (using a L
ON
W
ORKS
network management
tool) to another L
ON
W
ORKS
device. While this method
preserves autobinding, it does require one controller NV
more than if all binding is performed using a L
ON
W
ORKS
network management tool (e.g. LonMaker).
Binding to Other Devices
If you wish to bind the NVs of Distributed I/O modules to
other devices (i.e. other than the host Excel 500 controller),
autobinding cannot be used. Instead, you will have to employ
a L
ON
W
ORKS
network management tool (e.g. LonMaker) to
(manually) bind all of the Distributed I/O modules' NVs.
