02-20-2013, 12:04 PM (This post was last modified: 05-13-2013, 12:08 PM by ident.)
KNX 6.111 (beta) has the following changes
Fixed BUG from KNX 6.024 - KNX to Comfort mapping for Keypad Keys, Arm commands, Panic, Bypass Zones, and Zones did not work. Map to Counters, Sensors, Virtual Inputs do work
Function to use COPY button to press and hold to change UCM/KNX ID has been implemented. However this only affects UCM/KNX which has the pushbutton available.
KNX 1 bit and 1 byte objects mapped to Comfort Counters are ignored if the value is unchanged, eg On command folllowed by another ON command, or Off comand followed by another off command, or the same value in a 1 byte object
02-20-2013, 12:37 PM (This post was last modified: 05-13-2013, 12:14 PM by ident.)
For KNX 6.111, KNX 1 bit and 1 byte objects mapped to Comfort Counters are ignored if the value is unchanged, eg On command folllowed by another ON command, or Off command followed by another off command, or the same value in a 1 byte object
The above behaviour of KNX6.111 was introduced in KNX6.024. In the previous firmware 6.015, 1-bit and 1 byte objects always updated the mapped counters even if their value does not change. It has been pointed out that this is better because KNX Scene buttons must send the same value when they are pressed
hence we have also a version 6.112 which behaves in the \"old\" way ie like 6.015, in the attached file
When we have feedback as to the best way to implement this then future firmware will be fixed in that behaviour
The two versions 6.111 and 6.112 otherwise are the same
Known Bugs Sending telegrams to KNX group addresses causes the mapped counter to be updated for status but it should not cause Countter Responses to be activated. The bug is that counter Responses are activated by telegrams to KNX.
Counter Responses should only be activated by telegrams from KNX to Comfort
Known Bugs Sending telegrams to KNX group addresses causes the mapped counter to be updated for status but it should not cause Countter Responses to be activated. The bug is that counter Responses are activated by telegrams to KNX.
Counter Responses should only be activated by telegrams from KNX to Comfort
It should not cause an endless loop
Lets say you send a telegram to KNX group address. The counter is updated and activate a Response. This should not cause a telegram fromKNX which would cause an endless loop
Now the case where a telegram is received from KNX which activates a counter response. That Response should not send a telegram backto the same KNX group address as that would be wrong and unnecessary. if a KNX address is switched ON, you dont want to send a telegram to switch it on again, or switch it off again
Nevertheless there may be undesirable effects in certain cases. A new version wil be released soon
Quote:It should not cause an endless loop
Lets say you send a telegram to KNX group address. The counter is updated and activate a Response. This should not cause a telegram fromKNX which would cause an endless loop
Now the case where a telegram is received from KNX which activates a counter response. That Response should not send a telegram backto the same KNX group address as that would be wrong and unnecessary. if a KNX address is switched ON, you dont want to send a telegram to switch it on again, or switch it off again
Nevertheless there may be undesirable effects in certain cases. A new version wil be released soon
