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...
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.
are any of these relevant to our problem?
Last edited on Monday Sep 24th, 2018 01:59 pm by Home
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