Posted: Friday Jul 13th, 2012 08:26 pm |
|
1st Post |
ekarak
Member
Joined: | Wednesday Apr 21st, 2010 |
Location: | Athens, Greece |
Posts: | 51 |
Status: |
Offline
|
back to top
|
I just had one slave panel in an installation with 5.2xx firmwares go dead after upgrading to 6.004 (so as to have the wonderful remote upgrade capability....)
The slave locks up the whole bus when it boots, and I had to disconnect KA+KB so as to let the others (master + another slave) operate properly. All the other system components were successfully upgraded from various 5.2xx versions on to the latest 6.0xx versions and Comfigurator can query and report back all the modules in the system that can be upgraded via the bus.
The slave in question cannot be reflashed ("Product number or type does not match")
Looking at the cclx file, I found out that the SEM in question was at an unknown version:
< Slave Number="2" Name="Slave02" Version="Unknown" />
What can I do? How do I reflash it so as to make it operable again?
Last edited on Friday Jul 13th, 2012 08:29 pm by ekarak
|
Posted: Saturday Jul 14th, 2012 01:40 am |
|
2nd Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
Did the upgrade fail, or did the upgrade complete? What was the error message?
Connect the Slave for upgrading by UCM cable again. Disconnect the SEM from Comfort and leave it connected only by the programming cable
Turn on View > I/O monitor, then do the upgrade
Copy the I/O Monitor to Clipboard and show us what appears there
|
Posted: Saturday Jul 14th, 2012 03:30 am |
|
3rd Post |
ekarak
Member
Joined: | Wednesday Apr 21st, 2010 |
Location: | Athens, Greece |
Posts: | 51 |
Status: |
Offline
|
back to top
|
Apparently the version sticker on the SEM says the previous version was 5.139 (although it was bought alongside another SEM with version 5.175 on it). That's the cause of the problems I guess.
The initial upgrade to 6.004 completed successfully, without errors.
I tried re-flashing 5.175 onto it, and..:
> UB0100BE
< UBF00100Last edited on Saturday Jul 14th, 2012 03:30 am by ekarak
|
Posted: Saturday Jul 14th, 2012 03:45 am |
|
4th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
I will give instructions on how to recover the firmware by private message
|
Posted: Saturday Jul 14th, 2012 03:54 am |
|
5th Post |
Posted: Saturday Jul 14th, 2012 04:02 am |
|
6th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
I have given instructions on how to upgrade the firmware by private message
By the way, upgrading from 5.139 is not the problem. Any SEM firmware version 5 and above can be upgraded to version 6 using the UCM programming cable. The CBF file may have been corrrupted by a virus or some other problem
You can always re-upgrade the firmware using the programming cable
|
Posted: Saturday Jul 14th, 2012 07:52 am |
|
7th Post |
ekarak
Member
Joined: | Wednesday Apr 21st, 2010 |
Location: | Athens, Greece |
Posts: | 51 |
Status: |
Offline
|
back to top
|
Problem solved! Thanks again for the life-saving info!
I've managed to reflash the SEM in question after sending it the manual commands you sent me.
One more time, Cytech support is #1!
|
Posted: Saturday Jul 14th, 2012 08:37 am |
|
8th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
Thanks. This has been moved to a new Forum called "Firmware Upgrading Problems" under "Problems and Troubleshooting" so that all such questions and support issues can be grouped together
|
Posted: Saturday Mar 16th, 2013 07:43 pm |
|
9th Post |
mikegriff
Member
Joined: | Saturday Aug 19th, 2006 |
Location: | United Kingdom |
Posts: | 101 |
Status: |
Offline
|
back to top
|
I have the same problem.
Tried to upgrade my SEM to the latest firmware from 6.004 > 6.068 and that failed said it encountered a problem.
Red light and green light were on, stupidly I turned it off!
Tomorrow I will try and and re firmware it locally with a cable. any chance of the magic other method instructions?
Thanks in Advance
Mike
|
Posted: Sunday Mar 17th, 2013 02:11 am |
|
10th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
If the upgrade failed in the 1st part (up to 90+ %) it may be possible to repeat the upgrade with the non-cable method
If failed in the 2md part (last few %) it needs to be upgraded by the UCM programming cable
Upgrade to Comfigurator 3.6.5 first. This version has a new feature that if the upgrade is interrupted (not because of an error) there wil be a message "Retry Upgrade from last address"? This continues the upgrade. This may happen for ethernet connectiion if the connection is lost which may happenn sometimes
|
Posted: Sunday Mar 17th, 2013 04:11 pm |
|
11th Post |
mikegriff
Member
Joined: | Saturday Aug 19th, 2006 |
Location: | United Kingdom |
Posts: | 101 |
Status: |
Offline
|
back to top
|
Thanks for this
I got the firmware back on via a cable.
Slave 3 is at the end of the KA/KB line so thought it better to load it direct.
Thank you for yet again a quick response.
I now still have the problem that kicked it all off
After upgrading the main Unit to 7.024 the System does its normal startup then goes into Communications Failure and the system locks out
The keypad has no lights on and the whole system hangs
And I cant access a the UCM to use Configurator
(which is why I upgraded all the firmware I could)
I can clear the fault by disconnecting the KA/KB which feeds the keyboards and Slaves
then reset then plug back the KA/KB sign in
It then say Comms Failure restore and all seems to settle
This is definitely a result of the Firmware upgrade 7.024
I will send my Configurator file to the PM
As I say once sorted the system is fine
I have GSM and CBUS UCM + 2 old slaves + 1 new slave
Looking at the Log the problem is always SCS/RIO 3 which is a really old switch going back to my Comfort 1 days Could it be that 7.024 doesn't like these old SCS?
Once the system is up and runnning the SCS 03 works fine
Mike
Last edited on Sunday Mar 17th, 2013 04:49 pm by mikegriff
|
Posted: Monday Mar 18th, 2013 02:48 am |
|
12th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
If you reset Comfort, does the communication failure happens again?
If so can you disconnect the SCS and repeat the reset and see if it still happens?
|
Posted: Monday Mar 18th, 2013 01:49 pm |
|
13th Post |
mikegriff
Member
Joined: | Saturday Aug 19th, 2006 |
Location: | United Kingdom |
Posts: | 101 |
Status: |
Offline
|
back to top
|
Even if I remove the SCS3 I still get the same error
I have deleted SCS3 from the schedule and refs to it
Can i have id 1,2, 4
do I need to move 4 >3?
Any ideas
Mike
the SCS3 is PC01-033A
Last edited on Monday Mar 18th, 2013 01:53 pm by mikegriff
|
Posted: Monday Mar 18th, 2013 02:01 pm |
|
14th Post |
Home
Comfort Distributors
Joined: | Wednesday Jul 12th, 2006 |
Location: | United Kingdom |
Posts: | 771 |
Status: |
Offline
|
back to top
|
Well if you will do such things on Friday 13th !
|
Posted: Monday Mar 18th, 2013 03:11 pm |
|
15th Post |
mikegriff
Member
Joined: | Saturday Aug 19th, 2006 |
Location: | United Kingdom |
Posts: | 101 |
Status: |
Offline
|
back to top
|
I have now moved SCS4 to SCS3
And all is good
|The original SCS3 isn't faulty as it worked fine just throw a comms error on reboot
The OLD SCS3 only has 4 buttons not 8
Is there a Bug with 7.024 that it throws a comms error because it cant find buttons 5678?
Can you tell me what the outcome is I would like to put my 4 Button SCS back in the system at some point.
Thanks again for your fast response
Mike
Last edited on Monday Mar 18th, 2013 03:12 pm by mikegriff
|
Posted: Tuesday Mar 19th, 2013 03:14 am |
|
16th Post |
hendy
Cytech
Joined: | Wednesday Sep 19th, 2007 |
Location: | Singapore |
Posts: | 221 |
Status: |
Offline
|
back to top
|
Did the SCS3 throw the same Comms Failure error when the system was run on the older firmware before ULT 7.024?
What was the previous firmware version?
|
Posted: Tuesday Mar 19th, 2013 08:42 am |
|
17th Post |
mikegriff
Member
Joined: | Saturday Aug 19th, 2006 |
Location: | United Kingdom |
Posts: | 101 |
Status: |
Offline
|
back to top
|
Worked perfectly under
6.011
6.005
5.217
5.183 (08/04/2010)
and well beyond to Comfort 1
Mike
|
|