Comfigurator Version 3.0.0

[admin]

Comfigurator 3.0.0 is ready at last. Please download from Comfigurator 3 Link
Comfigurator 3 replaces Comfigurator 2. The new software is based on the .NET platform, and represents a major improvement to the user interface and functionality.
Both Comfigurator 2 and 3 can coexist in the same PC. Conversion between Comfigurator 2 and 3 is possible. The Icon for Comfigurator 3 is shown in the image below with a \"3\"
Please feedback and post any bugs found in this forum
A training slide on Comfigurator 3 programming is available for download from our website
Some of the new features include

1. New User Interface with 3 pane view allowing easier editing.
   
2. cclx file and cctx template formats to replace ccl and cct files
   
3. Auto Save interval
   
4. Selection of Toolbar items
   
5. Monitor I/O in View options instead of seperate pop-up window
6. Support for new UCM/USB. Connection settings include Serial, USB, Network
   
7. Modules Tab for UCMs. Supports Scanning of UCM Types and firmware version info
8. Supports new UCMs; Zwave, HDL Configurator in Modules Tab. UCM is no longer in Names
   
9. IR Transmit Codes which are used are saved in the cclx file 
   
10. Zones can be dragged and dropped, and copy/paste operation is supported
11. Configuration Flags for \"Detect Battery Disconnect\" and \"Require  Engineer Code to write\" 
    
12. In Sunrise/Sunset Times, the city is saved in the cclx file 
    
13. Response Wizard - IF x AND y, IF x OR Y conditions 
    
14. Response Wizard - Actions can be moved up/down in a Response
15. Response Wizard - Description will auto-generate the Name so there is no need to enter the Response name
    
16. Response Wizard - supports comments for each action
    
17. Prevent writing wrong or mismatched  file system to Comfort which would  cause red/green leds to turn on and system not to operate
18. Import Configuration screens (Tuning Parameter, Voice Settings, etc from other files
19. Sorting order of Responses (Name, Number) is saved for each file

Known Issues

1. Conversion of ccl files to cclx with Accented Characters in Response Descriptions cause Exceptions. Accented non-ASCII characters are handled correctly when entered as comments in Comfigurator 3
   
2. Scan for UCMs gives the number of UCMs found rather than the number of the last UCM, eg UCM 1 may be missing, so if there are UCMs 2 to 6, Number of UCMs will be set to 5
   
3. In Alarm Types, the checkboxes for phones 5 and 6 turn on and off together when Phone 5 is selected
4. For Z-Wave configurator, Reset To Default may result in invalid data read from the EEPROM
5. Selective Write in some circumstances gives an Exception Error
6. UCM01 < 5.092 unable to write and read to Comfort
7. Default template for Comfort II Ultra has all Siren Settings for BELL  to OFF. This is not a Comfigurator bug, it is a wrong setting of the template. Please correct on the cclx file. Conversion from ccl files does not have this problem. Please replace the def34.cctx file with the one attached in the next post
   
8. Pager ID Code leading zeroes are removed eg \"0123\" becomes \"123\"
9. Counters assigned in Zwave and HDL UCMs are not shown as referenced in blue in Events > Counters
10. Changes in Control Menu may not be auto-selected in Selective Write
11. When the U4 eeprom contains the wrong file system, Comfigurator does not write the correct file system into the EEPROM. For example, if the U4 was previously wriiten with a different file system or if it is blank, Comfigurator 3 is not able to write the correct file system data into it. Hence Comfort will start with red and green leds on indicating mismatched file system. Use Comfigurator 2 to correct this by writing the correct file system.
12. Action 31 (Get Last UCM Counter) entered as Action Code is removed by Comfigurator. Get Last UCM Counter can be entered by Response Wizard
13. If two responses have the same name except for a difference in Capitalisation, eg Responses named ABCDEFG  and ABCefg, then when an event selects  one of these Responses, the incorrect one may be selected, as Comfigurator should not allow the same Response name with different capitalisation.
14. When a response referenced by a Event has its Description changed and then the Response name is changed using Autogenerate Name, the Event  still point to the the old Response name. The renamed Response is not referenced, ie does not appear in blue
    

[admin]

We have just discovered that the Comfort II default template def34.cctx (the configuration opened when you select File > New Comfort II Ultra) has an incorrect setting for Siren Types
All the siren types have BELL set to OFF so the bell will not turn on when there is any alarm. If you have created a file using the def34 template please check and enable the BELL setting for relevent Siren types
The amended def34.cctx file is attached. Please copy to Comfigurator 3 folder, configs subfolder (\\Program Files\\Cytech\\Comfigurator 3\\Config)

[slychiu]

Please check the known issues with Comfigurator 3.0.0 regularly as we will update the list above when new bugs are found

[admin]

Comfigurator 3.0.1 is available  from Software Download Link
This fixes the bugs described above in the original post
Please download and replace 3.0.0

[juwi_uk]

You havent got around to updating this window then?



J

 

[admin]

No, I think nobody even noticed it yet

[Ingo]

One more for the Known Bug list:

When loading a V2 ccl file into V3 and you have a CBus UCM, the concatenate flag changes from Yes, in the V2 file, to No in the V3 file.

[admin]

Comfigurator 3.0.1 Known Issues

1. After installation in some PCs, there is an exception which prevents the program from running This is due to a known problem caused by a Microsoft bug introduced in the .NET Framework 2.0 SP1. It is fixed in SP2 which can be downloaded from here
   
   
2. Conversion of file from .ccl to .cclx with Concatenate CBus checked will in the filed being unchecked
   

[lms]

Two questions re: Comfigurator 3.0.1:

(1) One of the problems listed under known issues for 3.0.0 earlier in this thread included \"UCM01 < 5.092 unable to write and read to Comfort\". Another message indicates that Comfigurator 3.0.1 \"fixes the bugs described above in the original post\". Can I thus asume that the UCM01<5.092 problem is also resolved?

(2) Another message re: 3.0.1 indicates \"After installation in some PCs, there is an exception which prevents the program from running\". Is this the same problem that is causing the following behaviour:

On opening 3.0.1, I get the following (in a Windows behind the splash screen):

--------------------------------

Error reading file C:\\Program Files\\Cytech\\Comfigurator 3\\Config\\def34.cctx:
System.Exception: Error deserializing C:\\Program Files\\Cytech\\Comfigurator 3\\Config\\def34.cctx: System.InvalidOperationException: Unable to generate a temporary class (result=1).
error CS0200: Property or indexer \'Comfort.DrawButton.ResponseNameSpecified\' cannot be assigned to -- it is read only

   at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
   at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
   at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
   at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
   at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
   at System.Xml.Serialization.XmlSerializer..ctor(Type type)
   at Comfort.Util.XmlDeserialize[T](String pathName)
   at Comfort.Util.XmlDeserialize[T](String pathName)
   at Comfort.Form1.NewConfiguration(String filename)

------------------------------------------

Almost anything I click on in 3.0.1 results in a similar window popping up. Can\'t even close Comfigurator - just get a similar window and doesn\'t allow exit - have to terminate the process from Task Manager.

Have I stupidly missed something or will I just have to wait for a new version?

Because of (1) above, I can\'t run 3.0.0 either as I have old UCM\'s. I am planning to get new UCM05\'s very soon, but was hoping to start using Comfigurator 3 immediately. (I\'m still on Comfigurator 2.2.3 and have just upgraded to firmware 5.145 so will need to get new UCM\'s anyway to be able to upgrade from 5.145 and also to upgrade the SEMs.)

Any pointers appreciated.

[Ingo]

Try updating your .NET software to the latest via Windows Update, it solved my 3.0.1 loading issue.

Ingo