![]() |
|
Modules and Settings does not match Modules in Modules Tab - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Support (https://www.comfortforums.com/forum-2.html) +--- Forum: Comfort Installation and Programming Guide (https://www.comfortforums.com/forum-124.html) +---- Forum: How to Use Comfigurator (https://www.comfortforums.com/forum-128.html) +---- Thread: Modules and Settings does not match Modules in Modules Tab (/thread-2334.html) |
- slychiu - 07-09-2011 When a cclx file is opened, you may see a popup window with a warning ![]() This means that the numbers of UCMs, Keypads, Door stations, Slaves, or SCS/RIO in Modules and Settings does not match the modules which have been added or scanned in the Modules Tab ![]() ![]() Modules and settings ![]() Modules Tab Default view The Modules Tab gives extra information about the Type of UCM, Keypad, Door station and their firmware, which is very useful, and is saved in the cclx file. Hence the warning that comfigurator gives when it finds the numbers do not match. After Scan for All Modules, a typical results is as shown ![]() Comfigurator does NOT automatically make the two sets of numbers the same because the point is to tell you to a a Scan for Modules. Comfigurator only uses the numbers in Modules and Settings to write to Comfort, so an unconfigured Modules Tab will NOT cause an error The instructions on how to do a Scan for Modules in found in http://www.comfortforums.com/forum92/2103.html - ident - 09-17-2011 Comfigurator 3.3.2 fixed a Bug where if UCM#1 is not present in the configuration file in the Modules Tab, the warning message \"Modules and Settings do not match Number of Modules in Modules Tab\" appears UCM#1 is the UCM with ID #1 is reserved for the programming UCM and it can be removed from Comfort without any Communications Failure warning, unlike UCms 2 to 8 After scanning for UCMs in which UCM #1 is not present, and saving the file, opening the file used to produce the above error message, This has been fixed in Comfigurator 3.3.2 see http://www.comfortforums.com/forum20/2469.html |