Array Points Rule

When configuring CIMPLICITY data points for an unsolicited data message that contains a block of data from a PLC, a CIMPLICITY array point must be configured. The Element attribute specifies the number of data points contained in the message, and the Address specifies the starting address where the data is to be mapped.

For example, if the unsolicited data consists of one register, a single point with an address of N7:10 is updated with the unsolicited data. If the unsolicited data message contains 10 registers of data, then: element [0] of the array point contains the data for the address N7:10, element [1] contains the data for N7:11,... , and element [9] contains the information for data originating at N7:19.

Certain restrictions apply to CIMPLICITY array points. For example, alarms cannot be configured for array points, and setpoint actions are not allowed.

To circumvent these restrictions, you can configure individual points with their corresponding PLC memory addresses. These points can be configured as polled points with a very slow scan rate. They will be updated each time the scan interval occurs. You can also set a global parameter to have these individual points updated by unsolicited data messages that map to the corresponding memory addresses.

For example, if an unsolicited data point is configured as a ten element array point with a point address of N7:100, you can also configure ten points addressed at N7:100 through N7:109. If the multiple point update global parameter is set to "true", then each time an unsolicited data message is received for the array points, the individual points addressed at N7:100 through N7:109 are also updated.

More information

Rules for defining points for unsolicited data.