Comfigurator 2.1.2 (Interim release)

[slychiu]

The new version of Comfigurator is available for download from the website 
Please note that this is beta software and has not been fully tested yet
This will support the changes required for EN50131/PD6662 when the firmware is released
[color=\"red\"][img]file:///C:/DOCUME%7E1/LUCHIU%7E1/LOCALS%7E1/Temp/moz-screenshot.jpg[/img]4 May 2006 - see Known Bugs below
[/color]
20/11/2006 Bug fixes

• Fix problem with incorrect references
• Allow 15 SCS/RIO
• Fix bug renaming output referenced in IR code response
• Fix problem with missing scrollbar in response wizard
• Sort all comboboxes
• Prevent comment stripping in configuration text fields
• Fix incorrect text in Response Wizard for Ulti
• Fix problems editing Ulti Set Remote Unit Id
• Fix problem when renaming then editing response
• Update print formats for Comfort II
• Increase delay after Vocab download before reset
• Limit to 10 control keys on Comfort II if maxsets=1
• Improve syntax checking for IF clause

New features

• Add \"Show Alarms\" configuration flag.
• Add \"Entry Dial Delay\" configuration flag.
• Add \"Allow Low Battery Arm\" configuration flag.
• Add \"Unused Bits 3-7\" configuration flags for future use.
• Use E? for Event Log upload.
• Add User Responses to Miscellaneous Responses View.
• Support Open Door action.
• Support Get Sensor Register action.
• Remove Alpha Pager phone type.
• Repeat V? request if 0 returned first time.
• Support user-defined default template.

Known Bugs

• Incorrect Locations for Access User Responses (For Fingerprint reader)
• Entering Incorrect Action Codes can cause Comfigurator to crash (eg 89, 69, 128, 255 )
• Branch action codes entered manually are not coded by Comfigurator eg: 113,3,128,1,1,128,2,1,255.
• Voice download sometimes has an error causing no voice on system. Need to resend last line eg v!05FF1A010103, after the reset.
• Reminder Message has incorrect values for All Keypads/doorstations
• SMS phone type is not downloaded
• Error with response compilation if response number = 255
• Erroneous values in event log listing
• Problem with comma as decimal point in Siren duration (European Languages)
• IF statement with value 255 will cauuse end of Response
• incorrect values set for reminder message destinations

[Home]

When is this version likely to go \'live\'

 

 

[slychiu]

This version is quite stable after using it for several months. There are some minor bugs which we will document shortly
There is another release in several months time with more major changes, so I am not sure if we will designate this as \"released\" yet

[garym999]

I know I and others posted requests for new features etc. It might be nice to acknowledge any of these that get added.

Helps to encourage people to continue providing feedback and hence help develop the product.

http://www.comfortforums.com/forum20/213.html

Apprciate that this takes time and effort but now that we have this forum it should make that easier to manage. Can see that some of these have been addressed.

 

[slychiu]

Thanks for the suggestions from you and others. We have incoporated many suggestions from users over the years.

This release was focussed mainly on the forthcoming compliance with EN50131 (which I personally believe is a giant step backwards) and to fix some bugs with the firmware, so I am afraid that we have not had much chance to implement many  improvements

[garym999]

[size=3][font=\"Times New Roman\"]Agree with that! But what do us mere mortals, using common sense, know when up against the bureaucracy of government think tanks and European standards :X
[/size][/font]

[slychiu]

Known Bugs in Comfigurator 2.1.2 (beta)

Incorrect Locations for Access User Response

The locations for the Access User Responses are incorrect. The responses should be programmed into 2 locations and not one, e.g. for the User Response for User1 should be from location 744 and 745, and not from 744 alone.

Keying of Incorrect Action Codes may cause Comfigurator to Crash

This can be seen by keying in 89, 69, 128, 255 (which is wrong as the 2nd parameter after action 89 should be from 1 to 64). This causes Comfigurator to crash



Branch Actions

Branch action codes generate error, even with correct responses using the following string: 113,3,128,1,1,128,2,1,255.

Comfigurator \"Hangs\"

This happens occasionally when trying to close the Monitor I/O screen. For instance, get the system information for a few times and close the Monitor I/O screen every time. It may be able to generate the scenario where the program hangs.

Voice Download Problem

Voice download still seems to have problem. The last line is still needed to be resent, e.g. v!05FF1A010103, after the reset.

[Home]

V2.1.2

What do the user responses (misc events) allow you to do - can you give an example?

[garym999]

For example when you sign in a response can be linked to the user. Eg Works with the fingerprint reader to sign off the alarm depending on the user

[Home]

So this response is activated every time the user signs in..

There are many different occasions when the user may sign in, from comfigurator for example!