BAB TECHNOLOGIE KNXEASY, Documentation

Page: 33 / 44

Documentation KNXEASY
KNXEASY Version 1 b.a.b-technologie gmbh 33
3.5 STATE TABLE
Each time KNXEASY receives a “write” KNX telegram or ASCII string, it writes the value sent in a state table.
When it receives a “read” ASCII string, it checks first if the group/physical address is present in the state
table. If it is, it returns the value present in the state table. Otherwise, it sends a “read” KNX telegram on
the KNX bus. This process allows the user to ask for the state of any group/physical address at any moment.
3.6 CONNECTION CONFIGURATION
Connections have extra configuration directly linked to the KNXEASY protocol. Go back to “Configuration” -
> “KNXEASY”. In the “Connections” field edit the default UDP connection for instance.
Figure 39: Connection configuration
FORCE SEND TELEGRAMS
If this field is checked, it will cause extra behaviours:

KNXEASY can be use without importing an ETS 4 project. It will try to get the datatype from the
ASCII string.

KNXEASY can use an ETS 4 project where datatypes are not configured. It will try to get the
datatype from the ASCII string.

If device is the name linked to a group address and the same name is used for more than one
group address, a telegram will be sent to every group addresses having the same name.
For example if group address 1/1/1 has the name “lamp1” and 1/1/2 has the name “LAMP1”.
According to the protocol (not case sensitive), they have the same name. Therefore the same
telegram will be sent to group addresses 1/1/1 and 1/1/2.
RECEIVE ACKNOWLEDGMENT
If this field is checked, after each successful ASCII string sent, you will receive an acknowledgment JSON
string.
Structure of the acknowledgment string:
{"type": "ack","command": "[ASCII string sent]"}