| Posted: Thursday Jun 27th, 2013 12:00 pm |
|
1st Post |
lennyh
Member
| Joined: | Tuesday Feb 1st, 2011 |
| Location: | |
| Posts: | 20 |
| Status: |
Offline
|
back to top
|
We are experiencing difficulties after recent firmware updates. We upgraded to ULT7_033 and UCM7_023.
At present we are stuck at an error code UB0100FE.
The UCM/USB unit was bought some months ago to replace an older serial connection that could not be upgraded, and came with UCM7_008 pre-installed.
Upgrading the GSM and ULT firmwares where without error prior to this update.
We have tried many times to update the firmware without success and even use of the programming cable (including shunt on main board at pp2, and correct connection of all cables to ucm and from the main board) has been unsuccessful.
We also have powered down the system many times. It seems the UCM is now unreachable and has corrupted firmware.
Much time has been lost between this and another problem yesterday with a sim card not being recognised/usable by comfort.
Can you supply a solution?
|
| Posted: Thursday Jun 27th, 2013 01:55 pm |
|
2nd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Is the problem with upgrading the ucm/USB?
In order to upgrade by ucm cable you need another ucm/USB or eth02
How did you originally attempt to upgrade the ucm?
If the firmware is corrupted and you do not have another ucm your distributor should be able to upgrade the ucm for you
You would have to send it back to him
Apologies for the problem
The later ucm firmware should not have upgrade problems
|
| Posted: Friday Jun 28th, 2013 04:32 pm |
|
3rd Post |
lennyh
Member
| Joined: | Tuesday Feb 1st, 2011 |
| Location: | |
| Posts: | 20 |
| Status: |
Offline
|
back to top
|
The supplier stipulated that once the ucm is 6.008 and above it can upgrade itself as well as other boards. Where we mistaken in assuming this was correct? The errors occurred after we attempted this suggested upgrade path. The USB/UCM was supplied to us with 7.008 firmware. Last edited on Friday Jun 28th, 2013 04:33 pm by lennyh
|
| Posted: Saturday Jun 29th, 2013 02:09 am |
|
4th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Yes UCM version 6 is capable of upgrading itself
Using Comfigurator 3.6.8, you rightclick on the UCM in the Modules tab and select "Check for updates" see http://www.comfortforums.com/forum92/3400.html
If there is an error, eg the connection was lost, then the upgrade should be repeated
If the operation fails annd the UCM or Comfort is powered off, or UCM is reset, then the firmware is corrupted and must be upgraded using another UCM with a programming cable
How did you attempt to upgrade the UCM firmware and what error did you see?
Did you try to upgrade the firmware again?
|
| Posted: Monday Jul 1st, 2013 11:11 am |
|
5th Post |
lennyh
Member
| Joined: | Tuesday Feb 1st, 2011 |
| Location: | |
| Posts: | 20 |
| Status: |
Offline
|
back to top
|
We followed the procedure outlined in this post http://www.comfortforums.com/forum4/1216.html which described attaching the programming cable.
We did not identify the solution you have suggested in this reference post http://www.comfortforums.com/forum92/2409.html
It would perhaps be of benefit to other users of the forum to update the firmware section of the forum with a sticky post with the viable methods of upgrade and working links. Inputting “upgrade firmware†or similar in the search bar or manually searching the forum brings multiple results.
From the outset there was a loss of communication with the GSM unit and went on to include ghost UCM's and the main board staying in programming mode even when the shunt was removed.
Clearly after reviewing the post you have suggested it is no wonder the UCM became corrupted.
We tried several times to reacquire communication with the UCM unit, without success. It seems it is corrupted beyond a second programming UCM.
We are sending back all units, including the main board to the supplier for firmware updates as we simply do not have the time to wait if the motherboard/ GSM is also was unrecoverable by us. The client is soon to go on vacation and needs a working alarm before then.
Last edited on Monday Jul 1st, 2013 11:16 am by lennyh
|
| Posted: Monday Jul 1st, 2013 12:54 pm |
|
6th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
That link http://www.comfortforums.com/forum92/2409.html is in the archived forum as it was referring to the methods prior to the latest comfigurator which allows right clicking to upgrade firmware
In order to avoid references to it in future we have replaced it by a link to the correct forum which is http://www.comfortforums.com/forum92/3400.html
I still am uncertain what upgrade was attempted and how it went wrong
You say you upgraded the ULT and GSM without any problems. Presumably this was done by a UCM programming cable.
Then you say you had problems upgrading the UCM/USB. How was this done? Also using programming cable or by direct connection? If by programming cable you would need another UCM
The error message UB0100FE means that you attempted to upgrade by programming cable a different module with the ULT firmware but it was not accepted. But that does not corrupt the firmware of either module
When did you start having problems with the GSM? was that the module that failed to program
If the GSM or Comfort firmware is corrupted and the UCM is working then you can still use the UCM to upgrade their firmware
If we can understand what went wrong then we can see how to prevent it in future
|
| Posted: Monday Jul 1st, 2013 02:31 pm |
|
7th Post |
lennyh
Member
| Joined: | Tuesday Feb 1st, 2011 |
| Location: | |
| Posts: | 20 |
| Status: |
Offline
|
back to top
|
Before we knew about the post you have brought to our attention Comfigurator (the latest version)firmware upgrade was giving us no 2nd and 3rd option. The only option we had in Windows 8 64bit was upgrade by programming cable. That is how we proceeded with all firmware upgrades.
That clearly is why the UCM upgrade failed as it should have been done by the suggested method in your 2nd last post. After the failed upgrade we went to windows 7 32 bit and that's where we had options by direct cable and cbus.
The solution in your post was not found by us even after a good amount of searching. We are glad that the links have been updated.
At present we are not able to scan for all modules as there is an error. We are not able to investigate further as the contents of our panel are in the post to our supplier.
On investigating the progman.pdf we see the same detail as to upgrading as you have suggested. We chose to go with the forum initially because it seemed like the most probable place to look for up-to-date information.Last edited on Monday Jul 1st, 2013 02:32 pm by lennyh
|
| Posted: Tuesday Jul 2nd, 2013 02:30 am |
|
8th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
There should not be any difference between Windows 64 bit and 32 bit. The Comfigurator version you should be using is 3.6.8 in both
Transfer > Firmware Upgrade should only have one option and that is By Programming Cable in Comfigurator 3.6.8
The correct way to upgrade firmware for version 6 and 7 is by right clicking the module and selecting Check for Firmware Upgrades as shown below
If you need to do a firmware upgrade again when the products come back from the supplier, please do it this way with Comfigurator 3.6.8
We apologise for the old information that you found. The forum should be able to give the up to date information
|
| Posted: Tuesday Jul 2nd, 2013 08:00 am |
|
9th Post |
lennyh
Member
| Joined: | Tuesday Feb 1st, 2011 |
| Location: | |
| Posts: | 20 |
| Status: |
Offline
|
back to top
|
We use the 32 bit windows 7 OS as a backup and it unlike windows 8 had an older version of comfigurator. This version gave us the additional options on the upgrade page we where viewing, but this was only a recovery attempt after the upgrade failed on windows 8.
We are glad that posts and links have been updated, as we feel this was the major contributing factor in our failed firmware upgrade.Last edited on Tuesday Jul 2nd, 2013 08:03 am by lennyh
|
|
