04-08-2012, 07:32 PM (This post was last modified: 04-08-2012, 08:12 PM by ekarak.)
I have an odd problem with a Comfort installation and my client is frustrated at this.
A certain KNX group address (a pool pump) is activated every 5 minutes! it is (supposedly) fired by a timer response that is set to fire every day (not every 5 minutes!!!).
The pool pump response is not related to any counter, its just a time program to turn on the pool at certain time of day.
This installation has 5.2xxx firmware (havent updated it to 6.xxx, the installation is some 200km away).
Comfort will only do something if it is programmed in some way to do it so this should be related to your program. Send the cclx file to support@cytech.biz for us to look at it, and also show what are the relevant responses and time programs or areas affecting it if the program is large
Well, after upgrading to 6.xxx the same problem manifests itself in another address. Take a look at the screenshot attached, every time someone sends a drive command to addr 0/2/4, a spurious \"ON\" is sent to 0/3/10 !
Update: the problem is related to the UCM/KNX module. I had mapped the \"initiating\" group addresses via \"KNX to comfort\" each one to its own (unused) counter. When I removed the binding, the problem went away.
Yes you are right. we will check again
Anyway it is good that you have upgraded the firmware to version 6 because that would allow future firmware upgrades over the Internet if the site has UCM/Ethernet, provided the UCM/ETH02 and Comfort firmware are also version 6
Can you run Bus Monitor from the Tools Menu
This monitors the internal messages between UCM/KNX and Comfort which we would like to examine
Start the Bus Monitor. Then send the KNX message which generates the spurious KNX from Comfort.
Halt the Bus Monitor and Save All then save as a text file and send it to support@cytech.biz
thanks
I\'ve just sent to support@cytech.biz the log file from the bus monitor. A drive control command is sent from a KNX touchscreen (GA 0/2/3 is move up/down and GA 0/2/4 is step/stop). A few tens of milliseconds later, a \"bogus\" KNX packet is sent by Comfort to GA 0/3/10.
I _think_ this problem relates to the floating values overwriting \"bug\" I mentioned earlier today. Not scientifically proven, but just a strong hinch.
