Comfort Automation/ Security System Forums > Products > UCM > UCM 6.xxx or KT03 - How to Upgrade its own firmware |
Moderated by: slychiu | Topic closed |
Author | Post | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
admin Administrator
|
The original post is now obsolete as newer methods are now available Please go to post at http://www.comfortforums.com/forum92/3400.html for instructions on how to upgrade firmware Superseded Method below ---------------------------------------------------------------------------------------------- The UCM/USB, Ethernet and /232 is able to upgrade the flash firmware in Comfort II, Slave and other UCMs using the programming cable. See http://www.comfortforums.com/forum81/2280.html for details of the new UCM firmware However it was unable to upgrade its own firmware, as this required another UCM with a programming cable. This limitation is now a thing of the past with the new UCM 6.xxx and KT03 2.xxx firmware, see http://www.comfortforums.com/forum81/2280.html This makes it very convenient to upgrade UCM firmware. You will need Comfigurator 3.3.1 and above which can be downloaded from http://www.cytech.biz/comfigurator.html To summarise the 3 methods of firmware upgrading are;
Note that KP03, KP04, DP03, RIO and SCS cannot be upgraded by this way. They will be replaced by newer products that can be upgraded by Bus To upgrade UCM 6.xxx or KT03 2.xxx firmware,
If the firmware upgrade fails and cannot be recovered even after the above, you will need another UCM to upgrade firmware using the old programming cable method Last edited on Monday Jul 1st, 2013 01:40 pm by |
|||||||||
palmlodge Member
|
Assumption is that the UCM is v6 or higher before you can do this new method ? My 5.192 UCM refuses to upgrade using the new direct to pc method stating it needs to be v6.xx |
|||||||||
admin Administrator
|
Yes, this post is about the new features of UCM 6.xxx It does not apply to older firmware Last edited on Thursday Jun 28th, 2012 04:34 am by |
|||||||||
ident Administrator
|
The KT03 firmware can also be upgraded directly in the way using KT03 firmware 2.001, see http://www.comfortforums.com/forum90/2290.html |
|||||||||
Ingo UCM Pi Users
|
I just tried to downgrade from 6.002 to 5.228 using the direct method and found that it doesn't work. If you try this you will need a second UCM to recover fom this. What I found is that the Direct method does downgrade the firmware to 5.228 but at the 100% completion point Comfigurator 3.2.9 give an Exception and probably doesn't complete the last step. I haven't tried to reset the UCM to see if that was the last step, I just removed it and reflashed using the cable method. Regards, Ingo |
|||||||||
ident Administrator
|
If for any reason the direct upgrade does not complete, like due to Comfigurator exception, the instructions in http://www.comfortforums.com/forum4/2283.html say that you should not reset the UCM or remove power. You should restart Comfigurator and do the upgrade again. The firmware upgrade process is designed to take care of this, but once the UCM is reset or the power is removed then you will not be able to continue and you will have to resort to the old programming cable again Upgrading the UCM firmware with an older version should not cause the upgrading to fail for the reason that it is older firmware because it does not matter what the contents of the cbf file are. It is only after the firmware has been restarted that the upgraded firmware will take effect |
|||||||||
Ingo UCM Pi Users
|
That wasn't applicable in this case, the UCM didn't respond after the attempted downgrade, it's like it was just hanging and didn't allow me to login again. I had to remove power to use the cable method. Ingo |
|||||||||
ident Administrator
|
When you say the direct upgrade goes to 100%, there are two sets of data transfer with the progress bar, the first one takes longer and the 2nd one is only a few seconds Do you recall if it was at the end of the 1st set or the 2nd? |
|||||||||
Ingo UCM Pi Users
|
I retried the process on my Development system and no exception was generated. I will send a screenshot to support@cytech.biz becausethe UCM was again unresponsive until I did a manual reset. Ingo |
|||||||||
ident Administrator
|
After seeing the screenshots, the Upgrade process was successful. However in certain cases especially when downgrading the firmware to pre version 6, the UCM does not get reset at the end. You just need to manually reset the UCM, that is all. The "downgraded" UCM is working fine |
|||||||||
Home Comfort Distributors
|
Excellent we have just upgradea al lour stock UCM's will there be a 6.0 version for the other UCM's e.g. KNX CBUS etc - if so will the existing versions be backward compatible? |
|||||||||
ident Administrator
|
UCMs for Rs232, Ethernet and USB are directly connected to the PC so can be upgraded this way. (Not the old UCM01s though) UCMs for Cbus, KNX, Velbus etc as well as Slaves will be upgraded by another method - over the Bus in firmware 6 when it is available. It will apply to Flash-based modules |
|||||||||
gaynorc Member
|
Being a little nervous of beta software ( the Comfigurator 3.2.9 version is listed as beta), can I install the 6.002 firmware using the two UCMs method and Comfigurator 3.2.8, or must Comfigurator 3.2.9 be used with 6.002? |
|||||||||
ident Administrator
|
You need 3.2.9. Although it is listed as beta it is only because another version 3.3.0 is expected as the release version 3.2.9 does not warn you to press F0 before doing the upgrade If you look at the comfigurator version history you will find that 3.2.9 fixes bugs in 3.2.8 so it is more stable It will not cause your security system to have false alarms or crash it |
|||||||||
slychiu Administrator
|
Please note that when upgrading the UCM firmware 6 + directly using this procedure, it is important that if any error occurs during the upgrade, do NOT reset the UCM or remove power from the UCM as this will prevent the UCM firmware from being upgraded again. Just repeat the firmware upgrade. If the login does not work, waiit a minute or so for a time-out and try again. If the firmware upgrade cannot be done even after the above, eg if the power was disconnected from the UCM or the UCM was reset, you will need another UCM to upgrade firmware using the old programming cable method Last edited on Thursday Jun 28th, 2012 04:35 am by |