Posted: Tuesday Jun 7th, 2011 02:27 am |
|
1st Post |
admin
Administrator
Joined: | Saturday Mar 3rd, 2007 |
Location: | Singapore |
Posts: | 1200 |
Status: |
Offline
|
back to top
|
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;- By UCM Programming cable from UCM - This is the old way where a UCM with its programming cable has to be connected to the module to be upgraded. See This is described in http://www.comfortforums.com/forum4/1782.html
- By Direct Connection to PC - This applies to UCM/232, UCM/Ethernet and UCM/USB which is connected to a PC ie in Options > Settings> UCM Connections. This is described here.
- By Comfort Bus - this applies to the following modules; Comfort, Slaves, UCM/GSM, UCM/Zwave, UCM/Cbus, UCM/Velbus, UCM/Universal (and other "external" UCMs which cannot be directly connected to a PC and Comfigurator. This upgrades the modules on the Comfort Bus. See http://www.comfortforums.com/forum92/2409.html
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, - Connect the UCM to the computer in the usual way and select the Connection Method under Options > Settings.
- If Upgrading KT03 Firmware, the computer must be connected to the KT03 USB Port. In Options > Settings, select the USB serial number of the KT03. If you have another UCM/USB you will see both USB serial numbers. Disconnect the UCM/USB to ensure you seect the correct KT03 USB port. Then check the "Via KT03" box.
- The PP2 shunt need not be inserted
- Go To Transfer > Firmware Upgrade
- There are 3 choices shown; By Firmware Programming Cable connected to UCM, For KP06 connected to the Comfort Bus, and for UCM or KT03 connected to PC
- Select the last option "UCM or KT03 connected to PC" This means that you are upgrading the UCM which is connected to the PC now, ie selected in Options > Settings > UCM Connection
- select the cbf firmware file to upgrade the UCM with. For testing purposes you can select the same UCM cbf file.
- Press F0 on the keypad. This is an added security feature, because firmware can be upgraded from the Internet with the UCM/Ethernet with port forwarding.
- Comfigurator will confirm the firmware version of the selected file and start the upgrade process.
- DO NOT reset the UCM or Comfort or interrupt the communications in any way during this process which takes less than 1 minute. Do NOT unplug power from the UCM or reset the UCM, as this will corrupt the firmware
- If the upgrade fails for any reason like Comfigurator crashing, or any error message, DO NOT reset the UCM or unplug power from the UCM. Repeat the upgrade firmware procedure immediately.
- The progress bar for the process will be seen. There will be a second progress bar lasting only a few seconds.
- After the upgrade completes, and the progress bar disappears, the firmware will be upgraded. You can login to the UCM immediately
- In case the UCM does not reset automatically after the upgrade completes successfully, (ie it does not respond to commands) just reset it manually. However do not reset the UCM if there is an Error message which terminated the upgrade, see above point
Note that this applies only to UCMs that are connected directly to the computer, ie UCM/SB, UCM/232 and UCM/Ethernet. It does not apply to Comfort, UCM/Cbus, UCM/GSM, UCM/KNX, UCM/Velbus or other UCMs that are connected to third party systems. These modules firmware can be upgraded using the method "Firmware Upgrade for Module connected to Comfort Bus" which is described in http://www.comfortforums.com/forum92/2409.html
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
|
Posted: Tuesday Jun 7th, 2011 05:27 pm |
|
2nd Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
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
|
Posted: Wednesday Jun 8th, 2011 01:21 am |
|
3rd Post |
admin
Administrator
Joined: | Saturday Mar 3rd, 2007 |
Location: | Singapore |
Posts: | 1200 |
Status: |
Offline
|
back to top
|
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
|
Posted: Thursday Jun 9th, 2011 12:54 pm |
|
4th Post |
Posted: Sunday Jun 12th, 2011 08:05 am |
|
5th Post |
Ingo
UCM Pi Users
Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 557 |
Status: |
Offline
|
back to top
|
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
|
Posted: Sunday Jun 12th, 2011 08:34 am |
|
6th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
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
|
Posted: Sunday Jun 12th, 2011 08:45 am |
|
7th Post |
Ingo
UCM Pi Users
Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 557 |
Status: |
Offline
|
back to top
|
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
|
Posted: Sunday Jun 12th, 2011 09:58 am |
|
8th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
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?
|
Posted: Sunday Jun 12th, 2011 11:26 am |
|
9th Post |
Ingo
UCM Pi Users
Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 557 |
Status: |
Offline
|
back to top
|
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
|
Posted: Monday Jun 13th, 2011 01:36 am |
|
10th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
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
|
Posted: Monday Jun 13th, 2011 08:11 pm |
|
11th Post |
Home
Comfort Distributors
Joined: | Wednesday Jul 12th, 2006 |
Location: | United Kingdom |
Posts: | 771 |
Status: |
Offline
|
back to top
|
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?
|
Posted: Tuesday Jun 14th, 2011 02:40 am |
|
12th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
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
|
Posted: Wednesday Jun 15th, 2011 08:33 am |
|
13th Post |
gaynorc
Member
Joined: | Sunday Dec 31st, 2006 |
Location: | Ireland |
Posts: | 130 |
Status: |
Offline
|
back to top
|
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?
|
Posted: Wednesday Jun 15th, 2011 11:44 am |
|
14th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
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
|
Posted: Friday Jun 24th, 2011 01:38 pm |
|
15th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
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
|
|