Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

Bypass zone from KNX & getting feedback
 Moderated by: ident
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Wednesday May 4th, 2011 08:36 am
   PM  Quote  Reply 
1st Post
Glouba
Member
 

Joined: Tuesday Apr 19th, 2011
Location:  
Posts: 15
Status: 
Offline

  back to top

Hello again,

I need some help regarding zone bypassing using KNX.
I assigned group addresses to the "zone bypass" KNX to Comfort values.
The UCM/KNX manual states that this is a "1 bit Scaling (EIS 6)" (I assume this is a typo and you mean 1 byte ?).

Using ETS, I tried to write values to the group address corresponding to, for example, zone 24.
1.) I'm not quite sure which value should be written ? 1 for bypass, 0 to unbypass ? or maybe 255 for bypass ?

When writing a value, the only response I get from comfort on the KNX bus is :
Service    Flags    Src.addr   Dest.addr    Destination            DPT    Type     Data    
from bus   L        1.1.1      10/1/10      Alarm Type             6      1 Byte   Write    $10 | 6 %   
from bus   L        1.1.1      10/1/3       Alarm State            6      6 Bit    Write    $00   
from bus   L        1.1.1      10/1/20      Alarm State (Value)    6      1 Byte   Write    $01 | 0 %    

Moreover, if I try to check the bypass status from the keypad menu, it stays "off" for zone 24, so no change has been made.

I also ran another test :
2.) When changing the bypass of zone 24 to on from the keypad menu, almost the same feedback is emitted to the KNX bus, and I don't see any message telling that zone 24 is actually bypassed.
Should I check that by myself by reading a specific values from the UCM/KNX ? It seems unlikely as from what I've understood, the comfort to KNX interaction is event driven (not possible to read values directly).

So any help is welcome regarding what (value, type, ...) I should write to the bus to bypass a zone, and how I can detect that a zone has been bypassed.

Thanks for your help!



 Posted: Wednesday May 4th, 2011 09:07 am
   PM  Quote  Reply 
2nd Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

Sorry there is a typo. The Bypass zone group addresses should be 1 bit, not 1 byte object. Hence you "switch on" the group address to bypass the zone on Comfort and off to unbypass it. The group address state will also change when the zone is bypassed or unbypassed on Comfort.

The mapped group address for Bypass Zone corresponds to Zone 1 on Comfort. hence if 1/1/1 is mapped to zone 1 bypass, then 1/1/64 is mapped to Zone 64 bypass

The manual will be revised accordingly



 Posted: Wednesday May 4th, 2011 09:56 am
   PM  Quote  Reply 
3rd Post
Glouba
Member
 

Joined: Tuesday Apr 19th, 2011
Location:  
Posts: 15
Status: 
Offline

  back to top

Thanks for the fast reply.

I'll try writing a 1bit value then. I'm almost sure I already tried before.
So you mean that if my "Bypass Zone 1" is set to group address 1/1/1, if I bypass the zone with the comfort keypad, comfort will trigger a message on the KNW bus saying that 1/1/1 is set to 1 ?
I didn't notice that with the ETS group monitor when setting the bypass with the keypad.

I'll run some more tests tonight.

Thanks again.





 Posted: Wednesday May 4th, 2011 11:49 am
   PM  Quote  Reply 
4th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

That is correct, that is the way it works

Dont forget to write to eeprom after you map the Bypass group address



 Posted: Wednesday May 4th, 2011 05:21 pm
   PM  Quote  Reply 
5th Post
Glouba
Member
 

Joined: Tuesday Apr 19th, 2011
Location:  
Posts: 15
Status: 
Offline

  back to top

Hello again,

I just ran some test with ETS and it seems that writing 1bit to the group address for zone 1 bypass is working fine. I tested this by writing 0 or 1 and checking with the comfort keypad that the zone bypass was correctly switched off or on.

But I still don't understand the feedback I get from the UCM/KNX (I wrote the EEPROM again just to be sure) : When writing a 0, I get a response for zone 1 with 0, but I don't get that response when writing a 1 (even if set to on with the comfort keypad).

The messages sent to the bus when setting bypass OFF (through KNX or keypad) are :

from bus         L    1.1.1        10/1/17    Zone Trouble    6    6 Bit    Write    $00   
from bus         L    1.1.1        10/0/1    Zone (1)    6    6 Bit    Write    $00   

Which looks fine, I can tell that zone 1 is bypassed.

BUT if setting the bypass ON (through KNX or Keypad), I only get these on the bus :

from bus         L    1.1.1        10/1/10    Alarm Type    6    1 Byte    Write    $10 | 6 %   
from bus         L    1.1.1        10/1/3    Alarm State    6    6 Bit    Write    $00   
from bus         L    1.1.1        10/1/20    Alarm State (Value)    6    1 Byte    Write    $01 | 0 %   

I would expect to receive a "Zone 1" (10/0/1) with a value of 1 or something. How could I deduct from these 3 messages that zone 1 has been bypassed ?

Also note that I'm using address 11/0/1 to set the bypass status, and that the response (in case of bypass OFF) is coming from 10/0/1, which correspond to the "Comfort to KNX" zone status. But that seems logical.

Do you have any clue ? Are the received messages the normal behavior ?
Again, any hint would be appreciated :)

Thanks again.



 Posted: Thursday May 5th, 2011 01:45 am
   PM  Quote  Reply 
6th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

When bypassing the zone from Comfort, you should be a telegram on the mapped Bypass group address
eg if zone 1 is bypassed, you should get a telegram 11/0/1 ON and vice versa

The status on 10/0/1 is the zone status for on or off. If the zone is unbypassed you may get the actual status of the zone



 Posted: Thursday May 5th, 2011 06:37 am
   PM  Quote  Reply 
7th Post
Glouba
Member
 

Joined: Tuesday Apr 19th, 2011
Location:  
Posts: 15
Status: 
Offline

  back to top

Well, I'm not receiving any messages on the "bypass" group addresses on the bus then.
Either ETS group monitor is missing them (but I don't see why), or the UCM/KNX is not sending them.

Do you see anything that could cause this problem ? Maybe I missed something in comfort configuration ? Do I have to enable bypass message echo somewhere ?
I'm running the latest version of UCM/KNX (5.213).

I tried to change the group addresses for zone bypass, but that didn't help.

Thanks for your help.



 Posted: Tuesday May 17th, 2011 04:12 am
   PM  Quote  Reply 
8th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Can you send your cclx file for us to look at this problem?



 Posted: Tuesday May 24th, 2011 05:03 pm
   PM  Quote  Reply 
9th Post
Glouba
Member
 

Joined: Tuesday Apr 19th, 2011
Location:  
Posts: 15
Status: 
Offline

  back to top

I just sent an email to cytech support including my basic cclx file.
Thanks for your help.



 Posted: Thursday May 26th, 2011 11:18 am
   PM  Quote  Reply 
10th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 4307
Status: 
Offline

  back to top

Hi Glouba
We have managed to duplicate this problem and are in the process of investingating
We will let you know when we have a solution and a new firmware version
Thanks for the info



 Posted: Thursday May 26th, 2011 03:20 pm
   PM  Quote  Reply 
11th Post
Glouba
Member
 

Joined: Tuesday Apr 19th, 2011
Location:  
Posts: 15
Status: 
Offline

  back to top

Hello,

Thanks for investigating in this.
It's good to know that I'm not crazy and my problem is real :)

I hope you'll be able to find a solution soon.



 Posted: Saturday May 28th, 2011 05:49 am
   PM  Quote  Reply 
12th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

It has been confirmed  that is is a bug from KNX 5.203 and will be fixed in the next firmware due soon, after our testing is complete. see http://www.comfortforums.com/forum89/1876.html



 Posted: Saturday Dec 10th, 2011 04:18 am
   PM  Quote  Reply 
13th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Just for the record this bug was fixed in KNX 5.234, see http://www.comfortforums.com/forum89/2294.html



 Current time is 01:16 am
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems