+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Support (https://www.comfortforums.com/forum-2.html)
+--- Forum: Firmware History (https://www.comfortforums.com/forum-60.html)
+---- Forum: Slave Firmware (https://www.comfortforums.com/forum-78.html)
+---- Thread: Cannot upgrade Slave firmware to 7.207 (/thread-5600.html)
Pages:
1
2
- caravanboy - 01-21-2025
Hi - that worked now.
However, it possibly highlighted a minor bug in Comfigurator? After the Slave firmware was upgraded Comfigurator asked if I wanted to scan modules again to update firmware versions, I said \"ok\". However, I waited a minute or so but my current Slave firmware did NOT change.
I initially panicked and remembered all the old comments about needing to immediately do the upgrade again without disconnecting...
Anyway, instead I tried Scall ALL Modules and then the latest firmware version did show up for my Slave. So, I wondered if perhaps when Comfigurator does a re-scan after an upgrade it only scans UCMs and not Slaves?
- slychiu - 01-26-2025
The initial scan after upgrading does not update the modules. you need a proper scan to et the updated firmware info. Anyway if the upgrade completed without error then you can be sure that it was updated successfully
- slychiu - 04-07-2025
The problem is the old Slave board without EEPROM. It takes time to detect that the eeprom is not present so during that time after reset, the slave does not communicate
The new Slave with eeprom saves the ID in the eeprom as that does not have any ID switches
You can downgrade to 7.142 from this link https://www.cytech.biz/download_files.php?item_id=1254
- caravanboy - 04-08-2025
Hi. Oh, are you saying I NEED to downgrade to 7.142? Everything seemed to be working fine with the slave on 7.207 (after you\'d fixed the link).
Thanks
- slychiu - 04-08-2025
No you do not need to downgrade if that firmware is not giving comms failure