04-29-2009, 11:56 AM
This topic is for the new Comfigurator 3.0.1. It fixes all the bugs in 3.0.0 listed in http://www.comfortforums.com/view_topic.php?id=1389&forum_id=20 including the wrong FS34 template
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. Comfigurator 3.0.1 can be downloaded from Comfigurator 3 Link
Please make sure that you have .NET Framework 2.0 SP2. There is a known problem caused by a Microsoft bug introduced in the .NET Framework 2.0 SP1. It\'s supposed to be fixed in SP2 which can be downloaded from here
Please check that the download page says
[size=\"2\"]Microsoft .NET Framework Version 2.0 Service Pack 2 Redistributable Package (x86)[/size]and NOT [color=\"#ff0000\"]Compact Framework Version 2.0[/color]. If you have installed the Compact version by mistake please uninstall it and install the
Please feedback and post any bugs found in this forum [color=\"#ff0000\"]Latest - Please read important information about .NET Frameworks in the next reply immediately below[/color]
A training slide on Comfigurator 3 programming is available for download from our website
Comfigurator 3.0.1 Known Issues
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. Comfigurator 3.0.1 can be downloaded from Comfigurator 3 Link
Please make sure that you have .NET Framework 2.0 SP2. There is a known problem caused by a Microsoft bug introduced in the .NET Framework 2.0 SP1. It\'s supposed to be fixed in SP2 which can be downloaded from here
Please check that the download page says
[size=\"2\"]Microsoft .NET Framework Version 2.0 Service Pack 2 Redistributable Package (x86)[/size]and NOT [color=\"#ff0000\"]Compact Framework Version 2.0[/color]. If you have installed the Compact version by mistake please uninstall it and install the
Please feedback and post any bugs found in this forum [color=\"#ff0000\"]Latest - Please read important information about .NET Frameworks in the next reply immediately below[/color]
A training slide on Comfigurator 3 programming is available for download from our website
Comfigurator 3.0.1 Known Issues
- After installation in some PCs, there is an exception which prevents the program from running If you have this exception please downloaad .NET Framework 2.0 SP2 using the link mentioned above
- Conversion of file from .ccl to .cclx with Concatenate CBus checked will in the field being unchecked
- In Sunrise/Sunset Times, any changes in the Location or country/city are not written to Comfort in Selective Write when Sunrise/Sunset Times checkbox is selected. A full Write must be selected
- In Sunrise/Sunset Times, if the Location/Country/City is not selected and there is a full Write to Comfort, Daylight savings offset of 60 minutes is written to Comfort. To prevent this, always select a Location or City
- When writing File System 31 (Comfort II OPT), every zone is automatically announced when opened. Those who do not want this \"feature\" please revert to Comfigurator 2.2.3 for the time being
- Note that CMS Dial Test Action 11 has no function
- In Dynalite Actions, the Preset number increments each time the Response is saved
- \"Use Configuration Connection\" Settings is not working correctly
- Dynalite Recall Preset Action causes exception
- When a second instance of Comfigurator is opened while a first instance has not been saved, the message saying \"the (1st file) has been recovered\" This means that the contents of the first file being worked on was recovered
- In Security > CMS, if the Account Code is less than 6 digits, the leading digits 00 are added. eg 4567 becomes 004567. Change using the keypad Engineer Menu 4 for Phone Numbers, select Phone 1 or 2 , 1 for Type CMS, 1 for Monitoring Station Code and enter the account code and # key, eg 4567#. This bug was from Comfigurator 2
- IR Receive Responses - if assigned to NULL, will call Response 255 if the IR signal is received. To workaround, do not use Response Number 255