JUMO AQUIS touch P, Interface Description

Page: 21 / 52

21
5 Noncyclical data exchange
Declaration of a data structure in the "Multi-ID" format
In the IO controller, you need to declare 1 data structure (user-defined "STRUCT variable") as both the
target and the source memory for incoming/outgoing data exchange packets for incoming and outgoing
data exchange packets. Data exchange packets in the "Multi-ID" format have a fixed length of 640 bytes
and must be created with the following structure:
Structure variable for data exchange packets in the "Multi-ID" format
Data type Name Explanation
BYTE ID-PLC Sequential numbering for assigning the data exchange packets
from queries and responses
The "ID-PLC" value must be used by the IO controller for se-
quentially numbering the outgoing data exchange packets.
JUMO IO devices enter the same number in the ID-PLC in the
data exchange packet of the ensuing response, so that re-
sponse and query at the IO controller can be assigned, or so
that an error in the sequence of query and response can be in-
tercepted by suitable control structures in the IO controller.
BYTE NUMBER Number of data points of noncyclical data to be transferred
The data structure for data exchange packets in the "Multi-ID"
format is created with variables for 32 data points. The "NUM-
BER" parameter specifies the number of data points to be trans-
ferred between JUMO IO device and IO controller. The first of
the indicated number of corresponding data points are read/
written. The subsequent data points are not processed by the
JUMO IO device.
WORD DUMMY Fill bytes (no function; used to satisfy requirements for certain
data structures)