Comfort Firmware 7.183 to 7.202

[slychiu]

Firmware 7.196

1. Occupancy Action 27 for zone will  report dR01 only if occupancy timer has stopped to prevent dR01 report when movement is detected 

[slychiu]

Version 7.200
Bugs

• From firmware 7.198 - If UCM/knx, UCM/CBus, UCM/Modbus has address  mapped to Flag, Comfort broadcasts the flag to all UCMs but the source ID of the UCM changing the flag is not sent correctly by Comfort. This may cause the UCM to send an extra unneccessary message back to the external Interface for KNX, CBus, Modbus etc. This does not cause the UCM not to work , it just causes an extra message to be sent back to the Interface

Bugs Fixed

•  Fixed BUG wifi detection was wrong  if no module plugged in  on 10 way connector. Controller may keep resetting if there is no plug in. As a result Initialisation may take up to 3 seconds after power on if ETH03 is plugged in.
  
• LED03 RED  ON when wifi detected. LED3 red led will go off  if wifi submodule is not detected
  
• Fixed BUG for  LGX01, UCM/Logic, KNX/Logic - if eeprom file system is incorrect, Controller does not poll ucms so it was not possible to write to Comfort
• Fixed BUG in comfort protocol messages CTNNvv was seen as NNvv without CT

New Features and Changes

• d? query will reply d?00 if Motion Timer is  disabled ( NOT NA) -0 works  for ETH03 plug in not UCM which needs firmware upgrade
• Power failure alarm increased delay from 10 secs to 60 seconds  due to some systems having power failure alarms.  suspect short drop  in power caused the problem. Improved Saving Flags in eeprom for EMS and LGX

[Majik]

I\'m having major issues doing a cable firmware update. I have a relatively new Comfort II Ultra system which, unfortunately, failed a firmware update and stopped working.
So I have attempted to do a serial cable update as described in http://www.comfortforums.com/forum4/1216.html
I dug out my trusty old UCM serial unit which I have previously used for firmware updates. When I plugged it in as described, the UCM started up fine when the RS485 cable was connected, but as soon as the PROG connector is inserted, the UCM seems to go into a restart loop. I tried another UCM and it does the same thing, so it seems to be the controller, not the UCM.
Note that my controller does not seem to have a PP2 header. 


Am I doing something wrong, or is the firmware bricked?
Cheers,
Keith

[slychiu]

The ucm with programming cable should be able to upgrade the firmware. Make sure the cable with 4 way and 2 way connectors are on the ucm and the 6 way connector is connected to pp1 on the comfort. They\'re is no pp2 on the new comfort pcb. In your photo you do not show the connections to the programming cable

[Majik]

I did have the cable connected to the connectors as described.
As I said, when I connected the RS485 bus, the UCM powered up as expected. As soon as.I connected the 6 way cable, it started power cycling.
As it is, I\'m actually now at the airport traveling (to Singapore) for an extended period so I can\'t do anything about it now anyway.
I will have to sort it out when I come back to the UK.
By the sound of it, the board may have gone faulty.
Cheers,
Keith 

[Majik]

An update on this as I\'m currently home in the UK. This still doesn\'t work using a new UCM/USB board to try to program the firmware.

Just as with the previous UCM I tried, when you plug the programming cable in, it goes into a continuous reset loop:

https://photos.app.goo.gl/Je4xq96KPceWUyQi9

It looks like I may need to replace the main board.

Cheers,

Keith

[slychiu]

I suggest you send the Comfort PCB and ucm to Laser and get them to check if the upgrade can work, and verify which parts may need replacing

[Majik]

Unfortunately, I didn\'t have much time to look at this before I had to travel.
I had already ordered a replacement board from Laser, as well as the UCM/USB.
I ended up replacing the CPU board and leaving the DSP board, simply for speed and convenience, and reloading the config across the network, so it is back and running.
However, I did initially try programming the new CPU board from the UCM/USB using the programming cable, and that failed in the same way, with the continuous reboot.
So this indicates some other issue with the system which I haven\'t tracked down: I suspect either the DSP board or, maybe, a power problem (although I have the new enclosure with 2A supply, and I\'m not running that many things on it).
Either way, it currently works.
I was planning to bring the original CPU board back to Singapore with me but, in my rush, I forgot to pack it.
Cheers,
Keith

[Majik]

When I go back to the UK later in the year I\'ll do a few more tests and, if I don\'t find a solution, I\'ll try to remember to pack the board when I come back to SG.

Cheers,

Keith

[slychiu]

Firmware 7.202Bugs

From firmware 7.198 - If UCM/knx, UCM/CBus, UCM/Modbus has address  mapped to Flag, Comfort broadcasts the flag to all UCMs but the source ID of the UCM changing the flag is not sent correctly by Comfort. This may cause the UCM to send an extra unneccessary message back to the external Interface for KNX, CBus, Modbus etc. This does not cause the UCM not to work , it just causes an extra message to be sent back to the Interface

No functional difference from 7.200. The only change is to accomodate production test