CMeX50 Users Manual English
CMeX50 Users Manual English
Document id: 1090055 Version 1.5
Send unsolicited/periodical application data from
meter without request from master unit (Send /No
Reply)
Manually initiated sending of telegram with
request for installation in master unit (Send
Installation Request)
Sending of application data after a request from
the master (response of user data)
Table 7 Handled C-Fields
6.1.4.2 Handle CI-fields
6.1.4.2.1 Handled CI-fields for ”Extended Link Layer”
Type I with CC- and ACC-field
Type II with CC-, ACC-, SN-
and PLCRC-field
Encryption type 1 for extended link layer is
supported (AES128/CTR).
Type III with CC-, ACC-, M2-,
and A2-field
Encryption not possible. The fields M2 and A2 are
intended for destination address and are presently
ignored by the product.
Typ IV with CC-, ACC-, M2-,
A2-, SN- and PLCRC-field
Encryption type 1 for extended link layer is
supported (AES128/CTR). The fields M2 and A2 are
intended for destination address and are presently
ignored by the product.
Table 8 Handled CI-fields for “extended link layer”
6.1.4.2.2 Handled CI-fields for application data
Normal data telegram with
long application header
Telegram with 12-byte header. Secondary address
for the corresponding virtualized meter on wired
M-Bus is taken from the ID-field in this header.
”Compact frame” data
telegram with ”long
application” header
”Compact frame” format
telegram with ”long
application” header
”Application error”-telegram
with ”long application”
header
”Alarm”-telegram with ”long
application” header
Normal data telegram with
”short application” header
Telegram with 4-byte header. Secondary address
for the corresponding virtualized meter on wired
M-Bus is taken from the ID-field ”Link layer
header”.
”Compact frame”
datatelegram with ”short
application” header