Upgrade of old system from 2011

[slychiu]

Please see further comments and replies to some points in your original posts that I have edited in RED

[caravanboy]

Ok, I\'ll try all that tonight. The first time the UMC/ETH03 was ever powered-up it was connected to comfort with the programming cable (and standard cable too).

I don\'t see how the UCM firmware can be corrupted by a failed attempt as I\'ve not yet been able to even try upgrading its firmware as Comfigurator has always said it has failed to contact it.

Anyway, I\'ll follow your suggestions and see where I get to. Thanks again for all your help so far.

[caravanboy]

Actually, reading your instructions closely - I forgot to say I cannot select \"Check for upgrades\" as it is always greyed out because the UCM is not showing up in the list for COmfigurator. I tried the \"upgrade from local file\" but that was failing with the \"cannot communicate error\".

Ahh - just seen your red edits too.  Yes, sorry, I mentioned the D9 and D10 the wrong way around. There are no other error/busy lights, just green RDY all the time on UCM.  I really don\'t think I\'ve see the red D10 blink ever though, perhaps just one brief flicker for a fraction of a second.

I\'ll start from scratch again tonight with your red comment edits as it sounds like if I get the first \"UCM does not support this operation\" I should just try again - I\'m sure I did try that though and I had ignore the login the first few times (as I\'d seen the instructions saying it wouldn\'t work). I only tried it later out of desperation.

[slychiu]

Even if Check for Firmware upgrades is grayed out because you have not logged in, Uphgrade from local file should wrok

[caravanboy]

yes, but after selecting the local file that was the point where it says \"Unable to communicate with UCM\".

Can you confirm if my Comfigurator screenshot above is what you\'d expect to see - it shows no details of the UCM at all?

[slychiu]

It shoukd be detected
The first step is to check if the D9 and D10 leds are blinking (wiuthihut the ucmn programming cable connecte)

[caravanboy]

Ok. That will have to be tonight but I\'m sure I already did that list night as follows when I was going to try upgrading the UCM firmware:
a) UCM/ETH03 connected to Ethernet cable
b) UCM/ETH03 connected with the standard RS485 cable to Comfort (which is still on 5.206 firmware)
c) Programming cable was NOT connected
d) Comfort PP2 was NOT shunted
I\'m 99.9% certain that only the green D9/10 LED was flickering very fast, the red one did nothing. Does that mean I have a faulty UCM?

[slychiu]

Also check the RDY led? Is it on?

[caravanboy]

Yes, RDY was on all the time. Also, FYI, as I mentioned in my post after first trying the ETH03 to upgrade Comfort, the BUSY1 lights up after the first (failed) attempt to upgrade firmware by cable.

I did notice two more LEDs hiding under the ETH03 daughterboard last night. Those are not lit up.

[slychiu]

The UCM cannot be faulty as it does reply as you copied from UCM IO Monitor

> LT01
> LT01
> LT01
> UB0100FE
< NA
< NA
< NA
< UB01F0
< LU00
> LT01

At least that was the case when you tried the initial upgrade

Now you are not able to log in

This could be because of the Comfort firmware being corrupted by a partial upgrade.
If that is the case the keypad would not be able to login, and may make a beeping sound until you press any key
This can be fxied by the UCM upgrade cable

Another possibility if the UCM has been corrupted due to a partial firmware upgrade. if this is the case then the UCM firmware can be upgraded by Comfigurator

A 3rd possibility is that both UCM and Comfort firmware are working but Comfigurator is not connecting to the UCM due to a connection problem


So..
if D9 and D10 are blinking, it means both are working and you should be able to login

If D10 is blinking and D9 red is not blinking it means Comfort is working but UCM is not responding. Either the UCM firmware is corrupt or there is an ID issue