![]() |
|
Help, UCM is not a UCM/KNX after first WRITE TO EEPROM - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Third Party (interfacing to Comfort) (https://www.comfortforums.com/forum-5.html) +--- Forum: KNX (EIB) (https://www.comfortforums.com/forum-12.html) +---- Forum: KNX Support (https://www.comfortforums.com/forum-112.html) +---- Thread: Help, UCM is not a UCM/KNX after first WRITE TO EEPROM (/thread-1553.html) |
- TheMax74 - 07-27-2009 After the first WRITE TO EEPROM command, Comfort says \"this is not a UCM/KNX\" No luck after reset from comfigurator. Same thing if i press \"Read from EEPROM\" If i scan for UCM, Comfort says \"Other\" instead of KNX in the UCM list. To restore the operativity of the ucm, i need to open the comfort chassis, and press the UCM/KNX reset pushbutton. UCM/KNX 5.191 UCM05 5.178 Ultra II 5.164 PS: may be related to \"Monitor mode\" option... Another problem, KNX commands doesn\'t work in responses. The UCM/KNX is working, because when i press \"switch device on\" from the UCM property window, it works. - slychiu - 07-28-2009 Does this happen every time after you write to the EEPROM? - TheMax74 - 07-28-2009 No. I maded further investigations. seems to be random. After a while, it seems to change \"his personality\". It becomes UCM/Other instead of UCM/KNX. I need to press Ucm reset button. If i reset comfort, ucm does not resets. Sending knx commands (simply on/off) in responses, never worked. No LED error indications on the UCM when it freezes. If you at Cytech have successfully tested the UCM/KNX firmware, can be a wrong firmware update transfer, the cause of my troubles? Maybe the firmware is still at 5.132, but the user manual, says that Comfigurator 3.0.8 is able to detect if the UCM is EIB or KNX, so i think more in a faulty firmware update transfer. - TheMax74 - 07-28-2009 Just downloaded FW 5.192 No luck, same issue. FYI, knx commands in responses doesn\'t trigger. I have tried a response like - KNX On 3 52 - Siren Beep the knx command is not executed and the siren does not beep. The rows after the knx command, are not executed. if i swap like this - Siren Beep - KNX On 3 52 the siren beeps, but no knx command sent Smell like the xml cclx file is the issue... ***NOTE: i started a new project from scratch and responses seems to work. The problem is in my cclx file. Tried several things then tried to delete the response comment... that work! Strange, because there was no chars outside the ascii table in the comment. I think this has \"reformatted\" the xml correctly, because now all responses seems to work. If i come in touch what exactly the problem was, i tell you, because this is one of the problem in witch you can spend a lot of time to overcome!!ÃÂ For me, this issue is closed. - admin - 07-29-2009 There is a new firmware for UCM05, UCM5.192 which should fix the intemittent wrong detection of the UCM/KNX, please download from here If the UCM/KNX is not detected then the KNX Responses will not work. This may be the cause of the problem which you encountered - Domoconcept - 04-24-2012 Hi I have the same problem. The leds Ready, Busy1, Busy2 and Error are all off. When I try to upgrade the firmware, the system says: \"Firmware upgrade encountered erros\". When I do a \'read from eeprom\', the message is UCM is not a UCM/KNX When I do a read confort to PC, the UCM/KNX is not found, but the others UCM are founded (z-wave, rs232) I don\'t know how to solve this problem... Any idea? - ident - 04-24-2012 Your issue should not be related to the earlier posts which were 3 years ago If all the LEDs are off it probably means that there is no power to the UCM The 4 way cable should be connected from UCM/KNX to Comfort or another UCM You must set the UCM ID to 2. The D9 and D10 leds should both be blinking if the ID is correct If the firmware was corrupted which should not be the case unless you tried a firmware upgrade earlier. please try to upgrade the firmware again following the procedure in http://www.comfortforums.com/forum92/2409.html. DO NOT RESET or disconnect the UCM/KNX after a failed firmware upgrade |