Rules for application addresses include:
An application address must be
unique for each point on your computer.
An application address does not
have to be sequentially assigned.
The same application address can
be used for multiple devices communicating to the same CIMPLICITY
device communications process. When multiple AllenÂBradley Ethernet
device communications processes are configured for a CIMPLICITY
host computer, the same application address cannot be sent through
the same network interface to two different CIMPLICITY device
communications processes.
You cannot dynamically update the
application address for an unsolicited data point.
The application address is used to identify the CIMPLICITY point to the RSLINX interface software. As a result, there are several restrictions that must be applied to the use of application addresses with unsolicited point data:
For each unsolicited message that
a device sends to your CIMPLICITY project you must configure a
device point with an application address. Configure the device
point to have the exact same size and data type as the message
being sent. Also the application address should match the CIF
offset of that message.
For example, if you are sending a message containing integers from N7:20 to N7:40 (inclusive) at CIF offset 3, you should configure a point of type INT or UINT with 21 elements at the address N7:20>3.
If you use the ALL_UNSO parameter and configure
additional overlapping points for an unsolicited message, the
additional points should not have an application address in their
point address and do not need to be the exact same size as the
unsolicited message.
To insure that unsolicited
communications is correctly initiated for every message, points
that have been configured with an application address should never
be configured as Delay Load point or as Just-in-time attributes of
a point object.
|
|
Rules for defining points for unsolicited data. |
