© Vestamatic GmbH
Ar
t.-Nr
.:
84501110 E1 •
V
estamatic GmbH • Dohrw
eg 27 • D-41066 Mönchengladbach • www
.v
estamatic.com
IF SMI KNX 24VDC
Subject to modifications.
14/15
G
User interface objects and properties (UIO interface)
User interface object 50001 and properties therein
The properties defined in user interface object 50001 are displayed and explained in the following table.
Prop ID
Data type
Length
R/W
Memory
Function
1
Obj-ID
2 byte
RO
Code
Object ID of the user interface object, fixed “50001”
51
Version
2 byte
RO
RAM
Internal firmware version
64
char[17]
17 byte
R/W
RAM
Gateway for SMI commands
65
char[8]
8 byte
RO
RAM
Status of channels 1 to 8
80
int
2 byte
RO
EEPROM
Mask of available slaves
81
char[6]
6 byte
RO
EEPROM
Channel no. / Type / Manufacturer ID / Key ID of slave 1
82
char[6]
6 byte
RO
EEPROM
Channel no. / Type / Manufacturer ID / Key ID of slave 2
...
...
...
...
...
...
87
char[6]
6 byte
RO
EEPROM
Channel no. / Type / Manufacturer ID / Key ID of slave 7
88
char[6]
6 byte
RO
EEPROM
Channel no. / Type / Manufacturer ID / Key ID of slave 8
Property 1
Property 1 displays the object ID in accordance with the KNX standard
and is read-only.
Property 51
Property 51 uses the 2-byte-long data type PDT_VERSION specified in
the KNX standard and allows the internal firmware version to be read out.
During initialisation, the firmware always produces a RAM copy of the soft-
ware version identifier permanently coded in the processor Flash; this
identifier cannot be externally altered. Each nibble in the 2-byte value has
its own significance: the highest value gives the major version number, the
second highest the minor version number and the two lower-value nibbles
give an additional sub- and sub-sub version numbering. In the version
identifier communicated with clients, the second lowest nibble is given as
a letter, whereby value 1 corresponds to “A”. The version 2232h therefore
corresponds to “02.02 C 2”.
Property 64
Property 64 acts as a gateway to the SMI bus – it is therefore bidirectional,
which means that it is both externally readable and writable. With a length
of 17 bytes, it enables the transmission of any SMI commands which the
actuator passes on unchanged to the SMI bus. These could be, according
to SMI specification, a maximum of 16 bytes long, with a start byte and up
to three blocks, each made up of one identifier byte with up to four para-
meter bytes. When an SMI command is given via writing of the property
64, there is no need for a checksum to be appended to the telegram – this
is accepted by the actuator before relaying to the SMI bus. Instead, an
additional byte (the one standing on the left – with index 0 according to KNX
definition) is provided as a control byte for regulating the data exchange
via the gateway property.
The control byte also enables the triggering of special actuator reactions.
It can be written with the following values:
If the control byte is written externally with the value 01h, the actuator will
then interpret the following 16 bytes as an SMI telegram which is to be
sent to the bus. The actuator generates the checksum and relays the tele-
gram on, if necessary also with the required retransmissions according to
the SMI standard.
All the values detailed in the table above that can be written into the con-
trol byte (except 00h and 04h for initialisation) are also immediately
acknowledged by the actuator in the control byte. Due to continuous read
out of the byte, it is therefore possible to determine the processing status
of the particular request. Here, just as is the case for the SMI standard, the
FFh value is essentially interpreted as ACK.
In the case of re-initialisation through the value 00h or 04h, it is possible to
change the assignment of slave drives to actuator channels. The proper-
ties 65 and 80 to 88 are then updated accordingly. The actuator will let the
0 in the control byte of property 64 stand until the initialisation is complete
and then replace it with the value FFh. This way, the completion of the initiali-
sation and therefore the time of the validity of the updated properties 65
and 80 to 88 are discernible externally.
Initially, the actuator acknowledges a re-calibration request in the control
byte with the value 12h. The ACK through the value FFh is only set once
the re-calibration is complete. Depending on the number and type of con-
nected drives, the calibration can take some time.
Once an SMI telegram has been transmitted to the SMI bus, the actuator
sets the control byte initially to the value 80h in order to signal that the tele-
gram has been sent on the SMI side. As soon as there is a communica-
tion event (i.e. a slave responds or not), the actuator writes the event of the
communication into the property 64. The slave response, beyond ACK or
NAK, is contained, if appropriate, in the bytes from index 1 upwards and
in the control byte (see values in the following table):
Property 65h
Property 65 reflects the current state of channels 1 to 8, as updated by the
actuator, and is not amendable externally. The channels 1 to 8 are assigned
from left to right to the byte indices 0 to 7. The meaning of the bytes is as
follows:
Value Function
00
Software reset of the application, i.e. re-initialisation of the actuator
01
SMI command in the additional 16 bytes for transmission
to the SMI bus
02
Re-calibration of all slaves configured as blinds
03
Re-calibration of an individual slave, slave address
in the follow byte (this command may not be available
depending on the software version).
04
Software reset of the application, i.e. re-initialisation
of the actuator, but without previously updating the
position data in the EEPROM.
08
Output of values of all properties in the user interface object
50001 to the diagnosis interface.
Value Meaning
FFh Slave has responded with ACK
E0h Slave has responded with NAK
70h
Internal error in the communication (should not occur)
7Dh SMI bus without function due to power failure
7Eh Communication error on the SMI bus
(slave response could not be decoded)
7Fh SMI communication is still not initialised (an SMI telegram may
have been transmitted too quickly following an actuator reset)
Value Meaning
00h
Drive present, error-free and travelling UP
01h
Drive present, error-free and travelling DOWN
02h
Drive present, error-free and at rest
03h
Drive present, error-free, movement status still unclear
04h
Drive error
08h
Error: SMI not yet initialised
10h
Error: drive response NAK
20h
Error in the SMI communication
40h
Error: SMI power is off
8Fh No drive is assigned to this channel
9Fh Drive, which should be assigned to this channel,
has not been found
AFh No programmable drive has been found for this channel
FFh Channel not yet checked
The error bits 04h to 40h may theoretically also occur in combination.
