For easy integration of this driver into the application it is handy to use: Preconfigurations in group "ADAM module"
The messages are divided by individual devices (for each PLC the corresponding set of messages is defined) or the "ADAM type" = "Common ADAM" can be set in the message parameters window and thus all implemented messages for all ADAM devices are displayed.
To define non-implemented message we can set the "ADAM type" - "set by user" in the message parameters window. Then the message allows transmitting and receiving a common string value defined by the user after data setting.
Each message is positively identified by the description (see the message parameters window - "Message type") that equals to the identification in the original documentation. The only exception is the #aaSiBB(data) message that was separated by usage into two parts:
Float values are encoded into the char string by the "Engineering Units" format - it means to 7 chars where a sign, 5 digits and a decimal period is included.
At the "Analog Output Command Set" message set of the ADAM 5000 series the #aaSiCj(data) and #aaSiCj6 messages occur that use another format of Float values. For encoding only 6 chars are required that don't include a sign and the decimal period is given by the fixed position in the third char.