Comfort Automation/ Security System Forums

I had been using an old version of Comfigurator on an old laptop to update settings on my Comfort Pro. Due to lack of a daylight sensor I have to manually change the sunrise/sunset times once in a while. I was trying to update this recently when that latop stopped working.

So now I have a different laptop on which I have installed Comfigurator 3. I imported my old settings file and managed to upload it, but none of my lights were getting switched on in response to movement sensors. The system was responding to the keypads.

I\'m trying to resolve that by uploading again. I enter the user code, but then get prompted to press F0 on the keypad and enter the engineer code. That always fails now, but I think it worked the first time as above. If I try to enter engineer mode via the keypad it just gives a long beep after the code. Is it possible my engineer code has changed?

Also, I understand that there is a new feature of setting sunrise/sunset for each week. This would make my above adjustments redundant. Is this something I can use on my Comfort? Is there some documentation on how to use it?

Thanks

Did you enter F0 on the keypad before your engineer code?
If your engineer code does not work, you may have to erase all codes by going to user menu, 9 for Program menu 5 for user, 0 for erase all codes and 1 to confirm
This erases all user codes and messages and resets user code and engineer code to default

In Comfigurator > Configuration > Modules and settings, there is a box Require Engineer Code to write to Comfort. Uncheck this to be able to use user code to write to comfort so you do not haveto press F0 and engineer code

The Sunrise/sunset times is a feature of Comfort II so it will not work on Comfort I
You may like to take advantage of the attractive upgrade packages to Comfort II see http://www.comfortforums.com/forum25/1403.html

I disabled the need for an engineer code and was able to upload.

The problem I have now is that some of my responses are operating a bit slow. I\'m using the same settings I had before, but after a PIR is activated it can take up to ten seconds before the light comes on. All that has changed is that I uploaded from the new Comfigurator. All the response is to check the Daylight flag and then send an X10 On. Running the X10 On directly from Comfigurator causes the light to come on immediately.

Any ideas why I\'m getting delays? It\'s annoying the family.

I\'m not sure I\'ll be upgrading my Comfort just now. The upgrade cost is not justified for me as I am not using all the features I have now.

There may be a change in the code causing this. checking a flag does not take any time and there should be no delay
Turn on the I/O Monitor and see when the X10 commands are sent when the PIR is triggered
The PIR should be reported  as IPxxxx and the X10 command as XT...
Get someone to walk past the PIR

Using the I/O Monitor led me to trying firing the light events from the sensor Off rather than the On. That fixed it! Now the lights come on almost immediately.

It seems strange that this behaviour should have changed just by moving to a new version of Comfigurator. Any comments?

Can you send the cclx file to support@cytech.biz?