![]() |
|
Comfigurator 3.6.4 - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html) +--- Forum: Comfigurator (https://www.comfortforums.com/forum-20.html) +---- Forum: Comfigurator 3.x Old Versions (Archive) (https://www.comfortforums.com/forum-87.html) +---- Thread: Comfigurator 3.6.4 (/thread-3261.html) |
- ident - 01-27-2013 Either way should not cause any problem I prefer the stronger warning to scan for Modules to make sure that the user does do it. Scanning for modules is a much better way of getting the required info into Comfigurator for the new method of upgrading and other features - Ian - 01-27-2013 Hi - I have a Comfort 1 and seem unable to scan for modules. - ident - 01-27-2013 What is the firmware version of your Comfort I? If is too old it may not be able to support Scan and you have to manuallly add the modules - Ian - 01-27-2013 4.209 according to Wizcomfort - ident - 01-28-2013 That version is probably to support the scan commands You will have to manually add the modules in Comfigurator > Modules Tab Better still, it may be time to upgrade to Comfort 2, as firmware 4.204 was released in 2004 - Ian - 01-28-2013 Thank you for getting back to me. I would love to upgrade to Comfort 2 but at this moment can\'t afford to. :-( If you are having a sale on upgrade kits - let me know :-) - ident - 02-01-2013 There is a config file which is not updated in Comfigurator 3.6.4 idstatus.cfg should be copied into the ComfiguratorConfig folder This file contains the status infiormation in the UCMs for Zwave, velbus and Universal UCM when the Get Status function is used. This UCM status is displayed in the status bar. Formerly the status could only be seen on the UCM Leds which is not convenient unless the case is open - ident - 02-02-2013 Sorry the idstatus.cfg file in the last post was not the correct one. That was actually the same file as in Comfigurator 3.6.4. Please use the attached file instead - ident - 02-13-2013 Known Bugs found in Comfigurator 3.6.4
- juwi_uk - 02-15-2013 I\'ve noticed that if you minimise Comfigurator during a firmware update then you cant maximise it again and the firmware upgrade doesn\'t finish. I had to abort the process and start again. Julian |