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 12: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
I've just updated the knx UCM firmware from knx to knx2 last version.Since, I encounter very often "RS485 Comm Failure" Alert. Previously, I never had this message.
Maybe this is related to some wrong messages on the knx bus or some object from Comfort who don't have a dummy object in ETS ? But not sure that it woiuld be possible to manage all those errors on the knx bus if any...
Anyway, I would like at least disable this comm failure message. Could you help me. I cahnge the alarm type to "Not Assigned" and the related alarm status from "Trouble" to "Idle" but I still get the Alert on the KeyPad and on the monitoring.
Any suggestion to hide or to solve the comm failure issue ?
The way to disable the RS485 comms alarm is to go to Non Detector alarms, go to Alarm 25 which is "RS485CommsFail" and set the alarm type to Null or not assigned
Does this happen after a specific group address is sent?
This is excatly what I did to try to remove "RS485 Comm Failure" (I've used "Not Assigned"). But still, the message is displayed on the keypad and the central monitoring show "RS485 Comm Failure" as alarm state. At least, it doesn't play any siren but the status is very annoying while you're remotely looking at the alarm system state. This is because, in this case, you only see "Communication Failure" instead of either "Armed", "Disarmed", "Alarm"...So, is it not possible de setup comfort such it doesn't check for communication failure ?
Regarding to which group address it's related, I've still have to do my howework to understand.
Can you send the cclx file to email@example.com want to check what KNX devices you are using which may cause this problemThere seems to be no ay of preventing the display of comns failure on the keypad
How often does it hapen?