11-05-2010, 06:51 AM
PLEASE IGNORE THE BUG ANNOUNCED BELOW - IT IS WRONG - SEE THE NEXT POST
[color=\"#5500ff\"]A potentially serious bug in Comfigurator which affects interfaces to 3rd party system like C-Bus, KNX, Velbus, Zwave etc has been identified and fixed in Comfigurator 3.2.4 http://www.comfortforums.com/view_topic.php?id=2030&forum_id=20
The action to send data to a 3rd party UCM interface uses action 197 like the eaxmple below for Velbus[/color] [color=\"#5500ff\"]
Velbus SwitchRelayOn 3 VMB4RY 4 8
197,19,248,4,2,2,8,255
Code 255 terminates the action 197, but not the Response. The Response will continue until another terminator 255 is encountered.[/color] [color=\"#5500ff\"]
For Responses which have more or less than 8 codes for Ultra or 6 codes for Optimum, this will not cause any problem because the unused codes in the rest of the Response are 255. However for Responses like the example above which have exactly 8 codes, the Response will continue to the next Response line, which is not what was intended, and will activate the next Response[/color] [color=\"#5500ff\"]
Hence this problem will not be common except under the aforementioned circumstances, which is why it was not discovered before now
Comfigurator 3.2.4 fixes this problem by adding a 255 terminator after the Action 197 when it is the last action in the Response.[/color] [color=\"#5500ff\"]
Hence the above Response in 3.2.4 will have the following actions
197,19,248,4,2,2,8,255,255
This will be 8 codes which will take up the next Response line. Hence configurations which were created in previous versions and opened in 3.2.4 may have their Response numbers changed.
We recommend that all configurations using 3rd party external UCMs be opened and saved using 3.2.4 if there are unexplainable problems with Responses not working as expected.[/color] [color=\"#5500ff\"]
[/color]
[color=\"#5500ff\"]A potentially serious bug in Comfigurator which affects interfaces to 3rd party system like C-Bus, KNX, Velbus, Zwave etc has been identified and fixed in Comfigurator 3.2.4 http://www.comfortforums.com/view_topic.php?id=2030&forum_id=20
The action to send data to a 3rd party UCM interface uses action 197 like the eaxmple below for Velbus[/color] [color=\"#5500ff\"]
Velbus SwitchRelayOn 3 VMB4RY 4 8
197,19,248,4,2,2,8,255
Code 255 terminates the action 197, but not the Response. The Response will continue until another terminator 255 is encountered.[/color] [color=\"#5500ff\"]
For Responses which have more or less than 8 codes for Ultra or 6 codes for Optimum, this will not cause any problem because the unused codes in the rest of the Response are 255. However for Responses like the example above which have exactly 8 codes, the Response will continue to the next Response line, which is not what was intended, and will activate the next Response[/color] [color=\"#5500ff\"]
Hence this problem will not be common except under the aforementioned circumstances, which is why it was not discovered before now
Comfigurator 3.2.4 fixes this problem by adding a 255 terminator after the Action 197 when it is the last action in the Response.[/color] [color=\"#5500ff\"]
Hence the above Response in 3.2.4 will have the following actions
197,19,248,4,2,2,8,255,255
This will be 8 codes which will take up the next Response line. Hence configurations which were created in previous versions and opened in 3.2.4 may have their Response numbers changed.
We recommend that all configurations using 3rd party external UCMs be opened and saved using 3.2.4 if there are unexplainable problems with Responses not working as expected.[/color] [color=\"#5500ff\"]
[/color]