Comfort Automation/ Security System Forums

After upgrading Comfort Action 4.221 to 4.234 (PC01-001E Rev E) system was functioning properly for a couple of weeks, then suddenly (for no reason at all) system start resetting itself.
This never-ending loop of resets starts within a few minutes after normal reset or engineer reset or power reset. After a power reset I have managed to download the configuration to Comfort just to make sure that settings are correct. Unfortunately, it didn\'t solve this problem, after 30min system reentered the reset loop. The only way to fix this problem was to revert to the old 4.221 chip. The older chip with exactly the same configuration does not enter the reset loop. So now we are stuck with the older firmware, please advise.

See the event log below, all events related to server loop have time 00:00

06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 Unknown Event #3019
06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
and so on .........

First, can you upgrade to Comfogurator 2.1.0 which can be downloaded from https://www.cytech.biz/software.html.
You have an Unknown Event #3019. That code is not recognised by older versions of Comfigurator. Also please downlaod this attached file eventlog.cfg (which handles the new event log codes) into the Comfigurator folder
The event log code #3019 seems to be due to a GSM Module. Do you have a UCM/GSM installed in your system
What modules do you have? Can you email your ccl file to support@cytech.biz
Can you download a default or empty configuration for File System 24,  ie def24.cct into your Comfort

A possible reason for an endless Reset in Comfort is that one of the Responses has and endless loop, it responses call themselves

I have 3 UCMs, GSM 5-68, C-Bus 5-66 and UCM 5-92 with Tibbo NetModule

I was using version 2.1.0 but the file you sent me had few more entires.

Event27=Change Code User #,Param
Event28=Delete User #,Param
Event29=GSM Trouble ID #,ID
Event30=GSM Restore ID #,ID

I’m assuming that this new file will simply display GSM Restore ID #19

I’m fairly confident that there are no events that could cause an infinite loop (bare in mind that system is stable on the 4.221 firmware). With the 4.234 firmware you don’t have to touch anything (read trigger any events) to enter the reset loop.

I will try downloading the def24.cct file, it may be a challenging task as one has to be very lucky to establish connection to the 4.234 before it enters the reset loop.

Is the configuration stored in the flash rom of the microcontroller? If not, could I upload the def24.cct file using 4.221 and then simply swap the chips?

The configuration is stored in the U4 EEPROM.

Do you have any other U4 that can be used to replace the current one onboard?

Alternatively, do you have any other (non-ULtra, e.g. Outside) microcontroller U1 IC? If so, you could swap the microcontroller, which will then give a mismatch between the U1 and U4, then force download the configuration for the def24.cct and then replace back the Action 4.234 U1 later.

Ok I\'ve managed to upload the def24.cct template while 4.234 was installed.
I’m sure that upload worked as I was able to log in via keypad with the default password but I couldn’t download the event log “No response from UCM” using Comfigurator.
The moment I took out this 4.234 chip and replaced with 4.221 all went back to normal, I was finally able to download the event log, the repeating new log entry is:

06/14  00:00 Reset
06/14  00:00 Sign in - User #
06/14  00:00 Mode Change #Security Off
06/14  00:00 GSM Restore ID #UCM 3

So absolutely nothing has changed with the default template uploaded to Comfort.
I have wasted more time on it than I can justify, do you want me to send you back the 4.234 chip so you can play with it?

It is not necessary to send the 4.234 IC back as we have plenty of those. The possibility could be that the IC itself may be damaged or the pins or socket may be slightly deformed due to the insertion or extraction. If you give me your address and contact number we wil arrange for another 4.234 to be sent to you

regards

I’m sorry for my delayed reply, I was away from the office. I have installed the replacement chip and everything seems to be working as it should. I would like to take this opportunity to thank you for your prompt and professional help, the replacement chip was delivered within a few days of your message. The log finally looks clear with correct dates and times next to the GSM Restore ID event (that so far happened only once).

09/09  14:00 Reset
09/09  14:00 Sign in - User #
09/09  14:00 Mode Change #Security Off
09/09  14:00 GSM Restore ID #UCM 3
09/09  14:05 Sign in - User #Keypad
09/09  14:05 Mode Change #Security Off
09/09  14:05 Alarm Type #ArmFail (4)
09/09  14:05 Dial Number #2
09/09  14:05 Alarm Type #AlarmAbort (20)
09/09  14:05 Sign in - User #1
09/09  14:05 Mode Change #Security Off
09/09  14:05 Remote Signin - User #SMS Acknowledge
09/09  14:06 Sign in - User #Keypad
09/09  14:06 Mode Change #Away Mode
09/09  16:30 Zone Activation #Zone17 (17)
09/09  16:30 Alarm Type #EntryAlert (10)
09/09  16:30 Sign in - User #1
09/09  16:30 Mode Change #Security Off

Good to see that the problem was resolved