Comfigurator 3.2.7 Beta

[slychiu]

This is a new beta version which willl eventually replace Comfigurator 3.2.5, see http://www.comfortforums.com/forum20/2111.html

New Features

1. Scenarios Import and Export. A Scenario is a collection of Events and Responses which implement a function in Comfort. For example, Intruder Alarm Type causes the lights in the house to flash until the system is disarmed. This can be programmed in Comfigurator and exported as a Scenario file with extension .crsx. The Scenario can be imported into another file so that the same functionality can be implemented. This replaces the previous Responses Import and Export feature which was limited to Responses, and did not include the Events which trigger the Responses. This will be a very useful and important feature. See http://www.comfortforums.com/forum92/2185.html for a tutorial on how to use Scenarios
   
2. Improvements and more complete support for Universal UCM
3. Play Reminder Action - added Play Reminder for All Keypads, and All UCMs
4. When the number of Modules in Modules and Settings does not match that in the Modules Tab, a warning message is shown \"[color=\"#ff5500\"][color=\"#ff0000\"]Please do a Scan for Modules to determine the numbers of each module connected to Comfort[/color] [/color]\" The discrepancy could be because of conversion from Comfigurator 2 ccl files or because the configuration was created in an older version of Comfigurator 3 where the Scan Modules function was not available
5. In Options > Settings > UCM Connection for USB Interface, a button  \"Scan for USB Devices\" is added. Previously when a UCM/USB is connected to the USB port of the computer, yoiu had to exit from the Options > Settings page in order to detect the USB. The new button allows the USB to be detected while on the page.
6. When connecting to KT03 via USB in the KT03 Configuration screen,  if Comfigurator fails to connect, a message \"[color=\"#ff0000\"]Failed to connect to KT03.  Connect the PC directly to the USB Port of the KT03. If there is another UCM/USB, select the serial number for the KT03 USB[/color]\"  Initial problems encounteredc by users is that they did not realise that the computer has to be connected to KT03 directly, and that the USB serial number for KT03 has to be selected if there is a UCM/USB which also has a USB serial number. Selecting the UCM/USB serial number would cause Comfigurator to try to write the KT03 configurationto the UCM/USB which would not work.
   
   

Bug Fixes

1. Exception occured when editing KT03 Configuration using Windows 7 Professional (Other Win7 versions may be affected as well). Clicking on the Pages Tab caused unhandled Exception. Clicking OK caused another exception.
2. When a page in KT03 is renamed, the name is not reflected in other items which reference the changed page
3. Reading from a Comfort programmed with older Comfigurator versions sometimes caused an exception after the Read is complete.
4. When the name of an Alarm Type is changed, the Zone Types which trigger that alarm type still showed the old name until the Alarm Type for that Zone type is selected again.
5. IR Transmit codes which had codes numbered near the end of the table ie 250 but which have gaps in the IR numbers may overflow into the Alarm Types Table without warning causing the Alarm Types to have the wrong information. It is still recommended that there should be no gaps in the IR codes as this takes up extra space  in memory.

Known Issues

1. Selective Write causes incomplete data to be written due to Comfigurator resetting Comfort before the write is complete. Please use Full Write instead of Selective Write. This is not a new issue, and affects previous versions of Comfigurator. See http://www.comfortforums.com/view_topic.php?id=2197&forum_id=20 for full details.
   
2. For Universal UCM, when a referenced Response number changes due to manipulation of other Response numbers, the change is not reflected in the Universal UCM response.
3. The Alphanumeric Text ID feature for UCM/GSM does not work on Comfort Optimum because of an error in the IOMAP.CYM file. Contact Cytech for the correct file

[gazza]

Thanks for that, just what I needed to get round the KT03 crashes.

However, I can no longer talk direct to comfort via the UCM/Ethernet module. I get a Failed to Connect to UCM error after entering my sign in code in comfigurator

I installed the beta to a different location, and if I switch back to 3.2.5, I can connect to the panel ok as before so it would seem like its a problem in the beta version?

I am running on windows 7 pro, and wonder if you have any ideas on this.

Many thanks.

[juwi_uk]

Hi,

I\'m running 3.2.7 on Windows 7 Pro too and I connect to the UCM fine.

Could it be that your firewall/av is blocking? I guess installing a new version could look like a different app to the firewal/av and it blocks it?

Regards

Julian

[slychiu]

Comfigurator 3.2.7 should not be a problem for UCM/Ethernet if 3.2.5 can work.
Can you also try 3.2.7 on another computer?

[gazza]

I don\'t think it would be the firewall, it didn\'t need any config to work the first time. But I can try turning it off.

I do have access to another machine, so I will try that and let you know.

Thank you both for the responses

[gazza]

It did not work on the other machine either, which again was a windows 7 machine.

Same symptom. However I loaded the Tibbo DS manager and that is able to talk to the UCM fine, so I think the link between comfigurator and the tibbo drivers is the problem.

On both machines the standard DS Manager download on the cytech web site would not install, so I had downloaded the latest tibbo DS manager bits from the tibbo web site. Maybe this is somehow the problem, although it still works in the current release of Comfigurator. Did anything change in comfigurator?

Hope this is of use, I may try and borrow a XP machine and try that meanwhile.

[slychiu]

On the tibbo downloads page there is an x86 and x64 version of the TDST exe file. Did you download the correct one for your computer?

I suggest to reinstall the drivers

[gazza]

Yes, I got the right versions, (one machine was 64 bit one was 32 bit). I will play around some more.