Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register
Comfort Home Automation/ Security System Forums > Third Party (interfacing to Comfort) > KNX (EIB) > Comm failure when configuring 3rd party device on KNX BUS

Comm failure when configuring 3rd party device on KNX BUS
 Moderated by: admin
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Monday Sep 24th, 2018 12:58 pm
   PM  Quote  Reply 
1st Post
Home
Comfort Distributors
 

Joined: Wednesday Jul 12th, 2006
Location: United Kingdom
Posts: 560
Status: 
Offline

  back to top

We have a confusing problem on a couple of sites where a communication failure for KNX UCM occurs each time we update the configuration of a 3rd party device that is also connected to the KNX bus.

3rd party device is a LOXONE miniserver (I know, don't laugh!)

Every time we update the configuration for that device something triggers a communication failure between Comfort and the KNX UCM.

I can't see anything wrong on the KNX bus (in the ETS group monitor) but the unit does issue quite a few 'read' telegrams when it boots in order to sync itself to  the system.
I can't see anything wrong in the monitor of the KNX UCM when we write to the Miniserver.

The event log in comfort simply logs the communication failure (as one would expect) and not the cause.

We do however see some items in the UCM IO monitor that I can't find any more info about when this happens.

The serial protocol lists the items as..."TT - Monitor Data The format depends on the specific UCM Type and is not covered in the general protocol"

Is there any info available on the format of this message?
Specifically the following messages...
< TT13BC112F1132E300800C20
< TT13BC1127114EE10081
< TT13BC11121002E10081
< TT13BC110F1006E10081
< TT13BC110F100EE10081
< TT13BC11101007E10081
< TT13BC1110100FE10081
< TT13BC11070A26E10000
< TT139C11070A26E10000

Also these status messages occur at about the same time as some of  the 'TT' messages and seem to refer to module 15, but I can't see this referenced in the serial protocol and can't work out which module it would be.
< SS0F000A
< SS0F0000

are any of these relevant to our problem?

Last edited on Monday Sep 24th, 2018 12:59 pm by Home



 Posted: Tuesday Sep 25th, 2018 12:48 pm
   PM  Quote  Reply 
2nd Post
slychiu
Administrator


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

  back to top

Are you using UCM/KNX1 instead of UCM/KNX2?
in UCM/KNX2, theMonitor mode will show the meaning of the mesages instead of the raw messages

The TT messages are the status shown on the bottom left of the screen eg "Normal/No error" or "KNX Bus not connected" so you do not have to decipher them
< SS0F000A means KNX Data error
< SS0F0000 means Normal/No error
I suggest changing to UCM/KNX2 for a better experience





 Posted: Monday Oct 1st, 2018 10:49 am
   PM  Quote  Reply 
3rd Post
Home
Comfort Distributors
 

Joined: Wednesday Jul 12th, 2006
Location: United Kingdom
Posts: 560
Status: 
Offline

  back to top

Yes, we are using UCM/KNX2.
So it seems that some kind of "Data Error" on the KNX bus might be causing Comfort to register a communication failure with the UCM/KNX2.



 Current time is 06:53 pm
Comfort Home Automation/ Security System Forums > Third Party (interfacing to Comfort) > KNX (EIB) > Comm failure when configuring 3rd party device on KNX BUS
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems