Comfort Automation/ Security System Forums - Comfigurator 2.X

Comfigurator 2 Compatibility with Comfort Firmware

Tue, 13 Feb 2024 23:37:22 -0500

If you still want to use Comfigurator 2 with Comfort v7 firmware, the last firmware version which can be used is version 6.007 (in 2001). Up to this firmware version, the Engineer User number is 18. after this version the engineer user number was changed to 254. This was done so as to allow more Users (eg CM9001-EX) has 99 users.

Comfigurator 2 expects Engineer user number to be 18, and you need the engineer code sign in to write and read to Comfort.Hence Comfigurator 2 will not allowe write and read to Comfort Firmware > 6.007 Comfigurator 3 does not require engineer code sign in

It is highly recommended to change to Comfigurator 3 wjhich can co-exist wioth Comfigurator 2 in the same PC

Where to find Configurator 2

Thu, 09 Apr 2020 08:56:00 -0400

Hi folks,
On this page http://comfortforums.com/forum67/873.html there is a link to download Comfigurator. It looks like any V2 entries have dropped off the end of the list.
From reading around here, it looks like I need V2 to read from Comfort 1 back to my PC (don\'t ask!).
Any pointers?
Thanks,
Nick

Old Version of Configurator

Thu, 11 Nov 2010 12:09:32 -0500

Strange request - but can anyone tell me where I can get an old version of configurator? I need a verson less than V2. I have lost the engineer code and understand that I can change it via an early version, then use a later version to make further config changes.

Kind Regards
Nick

When to upgrade from Comfigurator 2 to 3

Tue, 09 Mar 2010 09:20:26 -0500

Comfigurator 3 (\"CF3\")is a landmark improvement compared to the previous Comfigurator 2 (\"CF2\") in terms of ease of use, features and speed.

When should installers make the change?

We recommend that Comfigurator 3 be used for all new installs.

For installed systems that have been completed, obviously there is no reason to change the software

For ongoing projects, which have been substantially completed with CF2, then it may be easier to stick to CF2

If there is new work or addition of modules to exiting systems then thatmay be a more difficult decision

Converting a file from CF2 to CF3 as just a metter of opening the .ccl file and saving as a .cclx file

If you have to Read the existing configuration from a Comfort that has been programmed with CF2 (because the original ccl file is not available, you may encounter exceptions when using CF3 due to certain incompatibilities. If so then use CF2 to Read the system (Comfort > PC) and continue from there.

Another reason to stick to Cf2 is if a UCM/EIB (as opposed to the new UCM/KNX ) is installed in the system. There is a difference in the format used in UCM/EIB and UCM/KNX to send telegrams to the KNX bus (Action 197). CF3 is suposed to detect which type of UCM is installed but this may not be foolproof. hence stick to CF2 in such cases. Nevertheless CF2 and CF3 can co-exist in the same computer (and both should be installed) so there is no problem with switching between CF2 and CF3 even in the same Comfort.

If a UCM/KNX is used in the system then CF3 MUST be used

Comments and tales from the field are welcome

Configurator - which version

Sat, 14 Mar 2009 16:46:18 -0400

Hi

My comfort system is about 7 years old. In the past I used configurator to configure. But I\'ve forgotten what version etc.

So - what version of configurator so I need and do I need to upgrade my comfort ?

I have the original license key and it seems to work in v1.6.10 (the interface looks like the version I used to use).

Thanks

Bill

Word lists

Fri, 01 Aug 2008 16:00:43 -0400

I\'m user of a comfort PRO, is it possible to add the Spanish residential in the word list for file system 18?
Perhaps the Spanish distributor Carlos Ask something about that today to someone.
Thanks

Requests for Comfigurator V2.2.4

Mon, 21 Jan 2008 10:44:46 -0500

Might be handy for people to list changes they would like to see in the next version of comfigurator...

My first one:

Store the connection details (serial, network ip address etc.) in the config file not the program.

Comfort 1 Ultra - Comfigurator version

Wed, 02 Jan 2008 18:29:10 -0500

I am considering re-writing all my responses for Comfort when I move from Pro to Ultra (Comfort 1).

Can anyone advise if it is still recommended to program Comfort 1 Ultra using Comfigurator version1.6.1 or can version 2.2.3 be used to deal with the FS24 type file.

Additionally, can you advise how to see all repsonses from 255 to 1023, to enable editing.

many thanks

Campbellhock:

Comfigurator 2.2.3

Mon, 26 Nov 2007 08:12:48 -0500

The last version of Comfigurator 2 can be downloaded from https://www.cytech.biz/comfigurator_v2.html

Comfigurator 2 should be used for Comfort 1 systems only. Use Comfigurator 3 for Comfort 2

This is a minor version release but it incorporates some useful features which were requested by users; eg comments in Actions, System Information from Comfort saved in the ccl file.
Sunrise/Sunset Responses have also been added

V2.2.3 19/11/2007
Bug fixes

Fix incorrect upload of alarm type name
Show Miscellaneous Events -> User Responses as references
Show Reminders as references
Fix problem with X10 received responses reverting to housecode A for FS18 and FS31
Handle Open Door action id as doorstation id, not UCM
Reminder message on All Doorstations should use id 48, not 32
Increase timeout for sentence download operations
Fix bug in editing tuning parameters
Fix Reminders 9 to 16 On/Off settings download wringly
Reminder message on All Doorstations should use id 48, not 32
Increase timeout for sentence download operations
Fix bug in editing tuning parameters
Fix Reminders 9 to 16 On/Off settings downloaded wrongly

New Features

Add comment to response action (editable in Select Action dialog)
Save Comfort version information in CCL file (viewable in General Information screen)
Monitor window can now be resized and minimised
Add sunrise/sunset times for Vietnam
Emphasise warning when attempting to download incompatible filesystem
Number nondetector alarms
Add Miscellaneous Events: Sunrise Response, Sunset Response, Door Station Voice On Response, Door Station Voice Off Response
Sort word list alphabetically in printed worksheet

Known Bugs

Timer 64 causes Unknown Exception Error
Optimise Responses Option causes Sunrise and Sunset Response to be disabled. Please DISABLE \"Optimise Responses\" in the Options menu
Entry Alert Response 7 PM to 7AM do Response - does not work
Sunrise and Sunset Responses do not show as referenced in blue in Responses
City is not saved in the ccl file for Sunrise/Sunset but the sunrise/sunset times are saved
When a \"Do Response After Timer\" Action is edited in Response Wizard AND the value of the timer is greater than 255, the wrong Timer name is selected in the drop-down list. When editing, be careful to select the correct timer name before pressing OK, although if you press OK without changing the Timer name, the action code still remains correct
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

[color=\"red\"][size=\"3\"]From Comfigurator 2.2.0 onwards, Engineer Code (default 6789) is required for download. User Code is not allowed for download

In order to auhorise the use of Engineer code, you need to press F0 on the keypad in order to authorise Engineer Code.

This is a protection from unauthorised access by Installers or other people[/size][/color]

Comfigurator 2.2.2

Wed, 19 Sep 2007 02:49:58 -0400

Comfigurator 2.2.2 is a maintenance release to fix known bugs in 2.2.1

Released 18 Sept 2007
Bug fixes

Validate name in new zone, zonetype and alarmtype dialogs
Fix problem uploading/downloading sensor feedback in control menu
Show referenced sensor responses
Fix problem with Dynalite commands shown as SendRS232
Update references when alarmtype or zone name is changed
Fix incorrect Ulti action descriptions
Fix crash when executing very long response
Fix problem with progress > 100% in event log upload

New Features

Known Issues

Alarm Types Names not uploaded correctly (Comfort > PC)
Misc Events > User Responses are not shown as Referenced responses
Reminders are not shown as References
No Sunrise/Sunset available for Vietnam
X10 Responses and housecode for FS31 and FS18 revert to default after saving the ccl file
Reminders 9 to 16 on/off settings download wrongly
Open Door Action allows UCM ID, not Door Station ID
Editing Tuning Parameters incorrect limits applied
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

[size=\"2\"][color=\"red\"]Please note that Engineer Code is required for download and upload. First, press F0 to enable Engineer code before entering Engineer Code
The default Engineer Code is 6789.
[color=\"black\"][size=\"1\"][size=\"2\"]In order to enable engineer Code without pressing F0, do the following
[/size][/size][/color][/color][/size] 1 Start Comfigurator
2 Select [Transfer] [Monitor I/O]   so that it is ticked.
3 Select [Transfer] [System Information]
4. If asked for a password enter a normal user code,   not the engineer code.
The system info window pops up, if it does not then your cannot do anything until that issue is resolved.
5 Click [OK] on the system info window to get rid of it.
6 Now in the long one line ( command line field of Comfigurator) type DA5C01 followed by carriage return. (This means Do Action - Enable Engineer)

You should see the following in the log window.
Tx: DA5C01
Rx: PS01
Rx: RA00

The PS01 is the system reporting that engineer code is now enabled.
7 Now do a standard [Transfer] [Download PC> Comfort], and all should be well with the world.
[size=\"2\"][color=\"red\"]
[/color][/size]

Comfigurator 2.2.1

Sat, 28 Jul 2007 06:13:33 -0400

This fixes the known bugs in 2.2.0
Download from http://www.cytech-technology.com/temp/so...Single.zip

[size=\"3\"][color=\"red\"]Please note that Engineer Code is required for download and upload. First, press F0 to enable Engineer code
The default Engineer Code is 6789
[/color][/size] Comfigurator Version 2.2.1 June 2007
HISTORY
V2.2.1 25 July 2007
Bug fixes

Fix problem saving file with sensor register as feedback type
Fix problem saving file with sensor response
Fix crash when clicking outside Zone, Zone Type and Alarm Type dialogs
Fix incorrect values in Zone Type dialog
Retain sort order following response insertion
Append CR to Rako command
Fix problem in 2-byte response number allocation

V2.2.0 15 June 2007
Bug fixes

Fix problem with response compilation if response number = 255
Fix problem with erroneous values in event log listing
Save CCL values using English locale to avoid problem with comma as decimal point in Siren duration
Limit counter value in IF statement to 254 to avoid erroneous end of response detection
Fix incorrect values set for reminder message destinations
Support user-entered branch actions
Fix exception on incorrect user-entered action codes

New features

Hide ringer details for Comfort II
Remove licensing checks
Remove alpha pager
[color=\"red\"][size=\"2\"]Require engineer code for up/download. PRESS F0 to enable Engineer Code[/size][/color]
Disable UCM concatenate if not CBUS
Launch WizComfort
Edit zones, zone types and alarm types using popup dialogs
Right-click on zone type in zone popup to display/edit zone type
Add descriptions and enable editing of tuning parameters for Comfort II
Associate names with X10 transmitted codes (referenced within responses)
Support UCM type Rako
Support UCM type Lutron
Support UCM as target for reminder messages
Display some actions in more than one category in Response Wizard
Support Sunrise/Sunset times
Support firmware download
Support unknown action codes
Allow either IP address or hostname for network connection

[color=\"blue\"]Known Issues
[/color]

Dynalite UCM commands appear as SEND RS232 actions
Changing Alarm Names in the Alarm Types popup window may corrupt NonDetector alarms. DO NOT change the Alarm Names using the pop up window
Problem when spaces are entered in the popup windows for Alarm Types, Zones, and Zone Types
Some ULTI command descriptions are not correct eg ALL OFF
Executing very long Responses directly from Comfigurator Responses window could crash the program
Sensor Feedback is not downloaded/uploaded correctly for the Control Menu
Some actions for Cbus after uploading get changed
When file system is converted to one with fewer responses, eg File System 34 (Ultra) to 31 (Optimum), the Responses which are fixed and over the limit for the new file system remain displayed without errors. If unfixed these Responses will be renumbered to a lower number or they will appear with a strike-out
Closing the Monitor I/O window after downloading or uploading may cause th software to hang.
Upload Event Log for Comfort Ultra II may show the wrong percentage > 100%, but the event log will still be uploaded correctly
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

Comfigurator 2.2.0 - Security Type Settings - Zone Type bug?

Sun, 22 Jul 2007 12:11:04 -0400

I have installed comfigurator 2.2.0 and am using it with Comfort Ultra II.

When I go into Security Type Settings / Zone Type and click on one of the Zone Types, the dialog box for that Zone Type opens up (new to 2.2.0).

However, while it gives the current settings for most of the parameters for that Zone Type, for both \"Night\" and \"Sensitivity\" it gives the settings as \"Perimeter\" and \"10\" respectively. If you save then these \"wrong\" settings are also saved.

Has anyone else this problem?

Comfigurator 220 - BUG

Sat, 21 Jul 2007 04:29:32 -0400

I\'ve just made some simple changes to my last config - and now when I press a CBUS button, the alarm sproutes out \"security off\"

The simple changes I made do no show any links into whatever the hell it\'s doing.

Any known issues ? If not where can I send this config to.

Storing IR Codes With CCL File

Sat, 14 Jul 2007 08:20:03 -0400

This has been asked of Cytech recently. But I would like others to add their views as to wether this is a much desired enhancement.

The request is that any IR codes used on a site is stored with ( ie ) in the CCL file. This ensures that any codes you have learnt for a job, ( which can often require a huge investment of your time ) are stored with the CCL file. This prevents the following issue with has caused a major hassle with one of our local integrators.

The Laptop that had the IR code file on it had a disc crash. There was not a backup available so the several hours invested to get the codes was lost.

It also prevents the following happening. You email the CCL file to another team member that does not the IR code file on the laptop that uses on site. It may be a new laptop. He does the download after making any required changes to the last file, and does not realise that he has just creamed the IR codes in the panel, and disabled the customers IR functions. Of course this sort of thing only happens at 4:00pm on a Friday on a job that is 2 hours traveling time from the office, and as it is a new site that does not have internet access. I a situation like this, how much would the function of having the IR codes stored in the CCL file be worth to your company.

The basic concept is that the CCL file should have all the required info you need for the site.

If you think this is a good idea, please feed this back to Cytech.

Regards Ian Clarke

iQhome[color=\"#aa0000\"]

This has already been implemented in Comfigurator 3[/color]

Does Comfigurator 2.2.0 work with Comfort 1?

Mon, 09 Jul 2007 04:20:16 -0400

Sorry for the silly question but before I attempt to use this new version with my Comfort 1 system I would like to confirm that Comfort 1 is still supported in this 2.2.0 release.

Thanks