+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Products (https://www.comfortforums.com/forum-3.html)
+--- Forum: UCMs (https://www.comfortforums.com/forum-146.html)
+---- Forum: UCM Problems (https://www.comfortforums.com/forum-73.html)
+---- Thread: Strange counter 128 behaviour. (/thread-1788.html)
- ident - 04-06-2010
If you mean that you changed the state of the counter to FF in Comfort, and the corresponding Cbus counter was in the opposite state (0), then when you toggle the CBus button to switch to FF, then there will be no Counter Response in Comfort because the counter is already at FF
The Counter report and response happens only if there is a change in value
eg
set Counter 128 to FF
> C!80FF change counter 128 to FF
< CT80FF is the counter report that Counter 128 changed to FF
> C!80FF change counter 128 to FF again
This time there is no counter report because the counter 128 value was not changed
> CT8000 set counter 128 to 00
< CT8000 report that counter 128 is changed to 00
Does this correspond to what is happening with your setup?
- Ingo - 04-06-2010
Ident,
This is what you need to do. I\'ll explain the tricky part at the end.
1. Set Counter 128 ON from CBus side.
[06:43:18] < CT80FF
2. Check Counter 128 value on Comfort side.
[06:43:23] > C?80
[06:43:23] < C?80FF
3. Do the following command:
[06:43:30] > Z?
4. At his point I Switched Counter 128 OFF from the Cbus side, notice NO corresponding CT8000 command back from the UCM.
5. Do a Counter 128 check on the Comfort side.
[06:43:51] > C?80
[06:43:51] < C?8000
This is the tricky part. Immediately the Counter value changed to what it\'s supposed to be. Without the receiving CT8000 command my ComfortClient thinks the light is still on. Only a subsequent On/Off toggle will restore the true nature of the light state.
Ingo
- hendy - 04-07-2010
Hi Ingo,
I\'ve tried exactly the 5 steps you mentioned but still managed to get CT8000 received by ComfortClient.
One thing I notice is that the latest ComfortClient version posted by Julian is 1.20.2.35 (http://www.comfortforums.com/forum65/1656.html) but you are using 1.21.1.5.
Is there any major differences for the two versions?
Do you know where I can get the same version as yours so I can try to duplicate your problem here?
I\'ve also tried with our Wizcomfort beta (see: http://www.comfortforums.com/view_topic.php?id=1662&forum_id=21), the CT8000 is sent correctly to Wizcomfort when it is turned off from C-bus.
- Ingo - 04-07-2010
Hendy,
I am using an Alpha version of ComfortClient which is not yet available to everyone. There is a big feature difference between the two versions so watch this space :-). I\'ve also used Comfigurator and the results are similar. The problem is not with the client software monitoring the bus.
It is VERY strange that I can replicate the problem at will and you guys can\'t. I\'ll try a last time on my \'Test\' system which has only 8 zones, my production system is fully populated with 64 zones.
Ingo
PS. I replaced my UCM/Ethernet with another one and it still does the same, unfortunately I don\'t have another UCM/Cbus. Give me some time to setup my Test system and I will post the results soon.
- hendy - 04-07-2010
[user=436]Ingo[/user] wrote:
Quote:Ident,Ingo,
This is what you need to do. I\'ll explain the tricky part at the end.
1. Set Counter 128 ON from CBus side.
[06:43:18] < CT80FF
2. Check Counter 128 value on Comfort side.
[06:43:23] > C?80
[06:43:23] < C?80FF
3. Do the following command:
[06:43:30] > Z?
4. At his point I Switched Counter 128 OFF from the Cbus side, notice NO corresponding CT8000 command back from the UCM.
5. Do a Counter 128 check on the Comfort side.
[06:43:51] > C?80
[06:43:51] < C?8000
This is the tricky part. Immediately the Counter value changed to what it\'s supposed to be. Without the receiving CT8000 command my ComfortClient thinks the light is still on. Only a subsequent On/Off toggle will restore the true nature of the light state.
Ingo
Could it be that in between of those steps above the UCM/Cbus get reset, somehow?
- Ingo - 04-07-2010
Nope, not a chance. It\'s securely mounted inside a panel well hidden from anything.
Ingo
- Ingo - 04-07-2010
Hendy,
These are the tests I did to try and localise the problem:
1. Downgrade the UCM/Cbus to 5.200 - Same result.
2. Disconnect my PAC from the network to eliminate any CBus interference - Same result.
3. Clear my Comfort Configuration - Same result.
and just before I went insane....
4. Connect my existing UCM/CBus to my \'Test\' system with 8 zones only. Downloaded my original 64 zone configuration - Working perfectly.
It seems that with a system as fully populated as mine, something goes \'missing\' when doing the test procedure stated in an earlier post.
I hope this help you guys simulate the problem. Just a note, I used Comfigurator 3.1.3, in Monitor IO mode, to check the bus messages.
Regards,
Ingo
PS. Julian, your Client is working as designed, even an earlier release showed me what Comfigurator showed.
- ident - 04-08-2010
We had better duplicate your full configuration. Can you send your cclx file to support@cytech.biz
- admin - 04-13-2010
I can report that we have managed to duplicate your problem now using your cclx file.
The number of slaves must be 3.
Set Cbus group addresses 80H and/or 81H on
do Z? on the UCM
C?80 and C?81 will show that they are ON (FF)
Now switch off group addresses 80H and 81H
There will be no report CT8000 and CT8100
However the counters 80H and 81H have the correcct values 00, but they are not reported by the UCM for some reason
We are now investigating this curious incident
- Ingo - 04-13-2010
This is indeed good news. Remember that counters 128 - 133 exhibit the same symptoms. The rest seems to work fine.
Ingo