Value Description; Module Sequence - Emerson AVENTICS AES OPC-UA Mode D'emploi

Structural data/elements
Values
MaterialNumber
Type
IO_Module02
...
IO_Module10
Values
MaterialNumber
Type
NumberOfConfiguredIO_Mod-
ules
ValveModules ValveModule01
Values
MaterialNumber
Type
ValveModule02
...
ValveModule32
Values
MaterialNumber
Type
NumberOfConfiguredValveMod-
ules
RawValues

4.2.2 Value description

Value
Per module, a JSON string is generated in the "Value" entry, where output and in-
put data are output at the update time. In large systems these are not always up-
dated with the minimum sampling rate (50 ms). If an update interval of 50 ms is
required for these systems, the RawValue can be used. This is updated preferen-
tially with a sampling interval of approx. 50 ms even in large systems.
Structure of the JSON string:
The string is structured as follows:
1. Opening brace: {.
2. If input data is available: "i":[ with the respective values.
If output data is available: "o":[ with the respective values.
3. Each value is output as a hex-encoded value with a leading "0x".
4. For analog modules, the summarized hex value of the bit length is inserted.
For digital modules, the bits are inserted in byte blocks. Leading zeros are
added to a byte if it is not used in full.
5. Individual values are separated by commas.
6. Closing bracket: "]".
7. Closing brace: "}".
The following examples illustrate the string structure for various modules:
Module Input values
4AI module 4x 8-bit input values
(10 dec, 20 dec,
30 dec, 40 dec)
AVENTICS™ AES OPC-UA | R412028203-BAL-001-AA | English
Specifications/value de- Data type
scription
Current state of the module
inputs and outputs as a JSON
object (see also value descrip-
tion)
Material number of I/O mod-
ule 1
Module name, encoded in an
Enum
I/O Module 2-10
Current state of the module
inputs and outputs as a JSON
object
Material number of I/O mod-
ule 10
Module name, encoded in an
Enum
Number of connected I/O
modules
Valve module 1
Current state of the module
inputs and outputs as a JSON
object (see also value descrip-
tion)
Material number of valve
module 1
Module name, encoded in an
Enum
Valve module 2-32
Current state of the module
inputs and outputs as a JSON
object (see also value descrip-
tion)
Material number of valve
module 32
Module name, encoded in an
Enum
Number of connected valve
modules
Current input and output data
with timestamp for when the
data was sampled, as a
comma-separated string
Output values String
{"i":
["0x0A","0x14","0x1E","
0x28"]}
Module Input values
2AI2AO module 2x 16-bit input values
String
(100 dec and
500 dec)
16DO module
String
Enum
Valve module, 2x
RawValues
String
The RawValue output was set up for high-performance data transfer. Therefore,
data is not processed on a module-specific basis here. Instead, the receiver must
assign the data to the modules (see
String
string is transmitted in big-endian format and is hex-encoded. Only the time-
stamp is in decimal code.
Enum
The following example illustrates the string structure for the module
M44,2AI2AO2M12-AE.
Byte
For calculation of the output and input values: see
Module
String
Valve side EP (M)
Valve module,
4x (4)
String
Valve module,
4x (4)
Enum
I/O side Analog com-
bination mod-
ule
(2AI2AO2M12
-AE)
String
Timestamp: 1 h, 26 min, 4 seconds and 608 ms since module start (5164608 ms)
The contents of the columns are separated by commas. In this example, this re-
sults in the following string: "5164608,01F4,01F455AA,07D02710,01F43A98".
String
Timestamp in Input data,
ms since start- valve side (hex-
Enum
up (decimal encoded)
code)
Byte
5164608 01F4
String

4.2.3 Module sequence

The input and output data used by the modules to communicate with the con-
troller consist of a byte string. The lengths of the valve system input and output
data are calculated from the number of modules and the data width of the indi-
vidual module. The data is only counted in bytes. If a module has less than 1 byte
of input or output data, the left-over bits are "stuffed" to the byte boundary us-
ing non-information bits.
Example: A 2x valve driver board with 4 bits of payload data occupies 1 byte in the
byte string, since the remaining 4 bits are stuffed with non-information bits. The
data of the next module therefore starts after a byte boundary.
The modules are numbered to the right of the bus coupler in the valve zone,
starting with the first valve driver board (module 1) and continuing to the last
valve driver board on the right end of the valve unit (module 9). See g Fig. 1.
Bridge cards are not taken into account. Supply boards and UA-OFF monitoring
boards occupy one module. See
OFF monitoring boards do not add any bytes to the input and output data. How-
ever, they are also counted, since they have diagnostic data. The data length for
pressure regulators can be found in the operating instructions for AV-EP pressure
regulators.
The numbering is continued in the I/O zone. There, numbering is continued start-
ing from the bus coupler to the left end.
M12/OB8 M11/IB2 M10/IB1
UA
Fig. 1: Numbering of modules in a valve system with I/O modules
Output values
2x 16-bit output val-
ues (700 dec and
1500 dec)
16x digital outputs,
set:
0b000100100011010
0
4x digital outputs,
set: 0b00001111
g 4.2.3 Module sequence). The data in this
g 4.2.3 Module
Input data Input data Output data
type type
16-bit integer 500 (decimal) 16-bit integer 500 (decimal)
--- --- 8-bit single bit 0x55 (hex)
--- --- 8-bit single bit 0xAA (hex)
2x 16-bit inte- 2000 (deci- 2x 16-bit inte-
ger mal) ger
10000 (deci-
mal)
Output data, Input data, I/O
valve side (hex- side (hex-en-
encoded) coded)
01F455AA 07D02710
g Fig. 1 (module 7). The supply boards and UA-
M1/OB1 M2/OB2 M3/OB3 M4/OB4 M5/OB5
AV-EP
(M)
P P A
S1 S2
String
{"i":
["0x0064","0x01F4"],"
o":
["0x02BC","0x05DC"]}
{"o":["0x12","0x34"]}
{"o":["0x0F"]}
sequence.
Output data
500 (decimal)
15000 (deci-
mal)
Output data, I/O
side (hex-en-
coded)
01F43A98
M6/OB6 M7/– M8/OB7 M9/OB8
UA
S3
11