Cannot upgrade Slave firmware to 7.207

[caravanboy]

I\'ve just been installed a new UCM/4G7608 UCM and had to upgrade my main controller and ETH03 firmwares so I thought I may as well upgrade my Slave too...
Slave is on 7.141  and after a module scan Comfigurator offered me 7.207.
I can see from other posts in this forum that is probably the latest firmware for my older hardware (purchased ~2011).
However, when I tried to check for firmware upgrades Comfigurator gave an error saying the cbf file is not compatible with the module being upgraded.
Can anyone explain?

[slychiu]

did you upgrade the UCM to the latest version?

[caravanboy]

Hi, yes, my UCM ETH03 was upgraded first to the latest offered (v7.225). The Slave was the last thing I tried to upgrade

[slychiu]

can you snd your ccx file after scan for modules so I can see which modules are installed?

[caravanboy]

Hi - I just mailed you the CCLX for the Comfigurator Graph References bug so that should contain the latest info. Let me know if that one has sufficient detail.

[slychiu]

Sorry I did not realise it was the same case. There is nothing wrong with the modules. Did you right click on the slave and select Check for upgrades?

[caravanboy]

Yes, after the check for upgrade I would have confirmed to proceed (I forget exactly what it asked) and that is when it said the CBF file was incompatible.

Maybe I should just try it again if this isn\'t something you can explain?

[slychiu]

Yes please try again and copy the monitor io info

[caravanboy]

I tried the Slave upgrade again this morning and did as follows:

1. Start Comfigurator
2. Load active config (same as the one I emailed you 17/Jan)
3. Scan for all modules - it asked me to login
4. Wait...
5. Slave is on 7.141 and now says Latest Version is 7.207
6. Right-click on Slave and click \"Check for Firmware Upgrades\"
7. It asks to confirm upgrade from 7.141 to 7.207
8. I say ok and it then gives the same error as before \"the cbf file selected is not compatible with the module to be upgraded\" - see attached image

The I/O monitor logs between steps 3 and 5 were:[indent][indent]> LI****[/indent][indent]< LU01[/indent][indent]> DT[/indent][indent]< DT2025011912085800[/indent][indent]> EL[/indent][indent]< EL1111FFFFFFFF[/indent][indent]> UL000003[/indent][indent]< DL00000305FF22D7[/indent][indent]> V?[/indent][indent]< V?FE080D22400100[/indent][indent]> v?[/indent][indent]< v?05FF27010203FFFF[/indent][indent]> U?[/indent][indent]< U?0A07E1110100[/indent][indent]> SN01[/indent][indent]< SN0101010000[/indent][indent]> u?00[/indent][indent]< u?110A07E10000[/indent][indent]< u?121907F50001[/indent][indent]< SN11000000F0[/indent][indent]< SN12000000F0[/indent][indent]< u?21BE078D0000[/indent][indent]< SN2100000000[/indent][indent]< u?410401110000[/indent][indent]< SN4100000000[/indent][indent]< u?4204010C0000[/indent][indent]< SN4200000000[/indent][indent]< u?FFFFFFFF0100[/indent][indent]> RD12000002[/indent][indent]< RD120000020004E8[/indent][indent]> f?00[/indent][indent]> Y?[/indent][indent]> Z?[/indent][indent]> z?[/indent][indent]> M?[/indent][indent]> K?[/indent][indent]> a?[/indent][indent]> d?[/indent][indent]< f?00FE3F4DC3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF[/indent][indent]< Y?00000000[/indent][indent]< Z?00000000[/indent][indent]< z?000000000000000000000000000000[/indent][indent]< M?0001[/indent][indent]< KL00010000[/indent][indent]< a?110000000000000000[/indent][indent]< d?00[/indent][/indent] Then between steps 6 and 8 the I/O monitor showed:[indent][indent]> UL000003[/indent][indent]< DL00000305FF22D7[/indent][indent]> V?[/indent][indent]< V?FE080D22400100[/indent][indent]> v?[/indent][indent]< v?05FF27010203FFFF[/indent][indent]> U?[/indent][indent]< U?0A07E1110100[/indent][indent]> U?[/indent][indent]< U?0A07E1110100[/indent][indent]> V?[/indent][indent]< V?FE080D22400100[/indent][indent]> LT01[/indent][indent]< OK[/indent][/indent] Look forward to your analysis...

[slychiu]

Sorry there was a mistale in the firmware upgrade link, it was pointing to a different firmware, The link has been upgraded, so please try again