Page 33 - Serial Data Transmission and KNX Protocol

KNX TUTOR SEMINAR

MaskVersionResponse
Response to MaskVersionRead containing the requested data.

11 01 xxxxxx mmmmmmmm vvvvuuuu
m...m: mask type (first nibble indicates medium, second nibble indicates main
profile)
v..vu..u: mask version (first nibble main version, second nibble subversion)
For more information on the existing system profiles, see appropriate paragraphs in Basic
Course, Part ‘Bus devices’
4
x...x: no significance

Restart
Resets the bus device of the addressed bus device. Whether or not the application
module, too, is reset, depends on the respective bus device to which the message was
sent.

11 10 xxxxxx

4
x...x: no significance

Escape
In case the APCI has the underneath value, the exact meaning of the APCI is indicated in
the six bits following the Escape APCI.

11 11 eeeeee

e...e: extended APCI bits

M_BitWrite (in case of eee eee = 010 000)
This service allows individual bits in the memory to be manipulated: In this way it is
possible to change up to 1 to 48 bits in the memory of the bus device

M_AuthorizeRequest/Response (in case of eee eee = 010 001, respectively 010 010)
These services allow accessing a bus device with memory access-protection. 16 different
access levels are possible. A 32 bit number (FFFF FFFF) is required to be granted
access to memory. If no access protection is used, the number remains at FFFF FFFF
and all the access levels are enabled.

The process is started by an M_ AuthorizeRequest message which contains the number.
The device that receives the message compares the number with its table and enables
the corresponding access levels. If the number is not in the table, the device disables all
memory access. The bus device replies with an M_ AuthorizeResponse; this reply
contains the information about to which level access has been granted.

Home and Building Management Systems KNX Association
Serial Data Transmission and KNX Protocol Serial Data Transmission_E0808f.doc 33/41