The new beta version of Comfigurator, 2.9.12 is now available for download here

Bugs fixes

1. Saved IR Codes in Responses were incorrect
2. Sunrise/Sunset City saved file always to Algiers
3. Transfer System Information from UCM firmware  < 5.160 caused exception, hence  all transfer read and write using old UCM firmware caused exception

New Features

1. Support for USB in Options > Connections for new UCM/USB
2. Control Menu - Menu items can be dragged and dropped, and also supports Copy/Cut/Paste
3. Support for new UCM/Zwave

Known Bugs

1. Counter References in Control Menu feedback not updated when Counter name is changed
2. If condition causing branch causes error when the number of bytes is > 127. This affects If conditions where the number of actions within the IF loop are too large

The new version is almost ready for release. It is fully functional except for the known bugs

Get attached when clicking on OPTIONS in 2.9.12.

Is this file missed from the installer?

 

J

Also in 2.9.12

Under Sensor Responses section the \"Show References\" features is not working correctly.  

(a) It\'s not showing my use of the sensor response as a feedback item in the control menu.

(b) It doesnt highlight in blue but I assume that\'s a result of (a).

J

 

 

You got this just by clicking on options without selecting USB, Serial or Ethernet?

[user=876]juwi_uk[/user] wrote:

Quote:Get attached when clicking on OPTIONS in 2.9.12.

Is this file missed from the installer?

 

J

No I\'m setup and using Ethernet for comms with comfort.

But get this when I click the button.

have sent AVI to support@cytech.biz

J

 

update:  I think it\'s because I\'m on vista Ultimate x64? 

Hi,

I got the same message, and I am using win2k

Regards,
Eamon

[user=876]juwi_uk[/user] wrote:

Quote:Get attached when clicking on OPTIONS in 2.9.12.

Is this file missed from the installer?

  Failed to Load FTD2XXX.dll

The DLL is supplied but it’s in the USB Drivers\\i386 folder under the installation folder.  If you copy it to the installation folder the problem should disappear. The DLL shall be included in the installation folder for the next version.
 

Sorry,

Could you confirm the exact path with which we need to copy the dll file to ?


DOH!!! Sorted, finger trouble, had not copied it to the comfigurator beta folder properly, all done now, thanks!!

Thanks,
Eamon

Regarding our previous discussion ie

\".....

Congratulations, You have found a bug in the creation of the action code because of the length of the branch if not Night. The code is asked to branch over too many actions

The workaround is to reduce the  branch by breaking up the code into several If Not Night ie
.....\"

I\'ve found that using the response with the smaller branches as per your edited version works fine when the system calls it as an Hourly Response.

However when I manually call it through Comfigurator either via the EXECUTE on the \"Responses\" or \"Control Menu\" areas the system seems to loop. Instead of Announcing once on the keypads (as it does as an Hourly Response) it does it 3 times and the cursor always stays as busy (hourglass or rotating circle in my Vista case) until I exit and re-enter Comfigurator. Control seems to be passsed back to the UI but the cursor still busy!

Why should this be? Bug?

Have attached the response.

Oh I\'m on 2.9.12 by the way but otherwise working really cool.  I wont move back to 2.2.3 now!

Regards

Julian

 

 

 

 

A couple of observations on the Control Menu in 2.9.x:

(1) When \"Show Status\" is checked, the frequency at which the values are refreshed seems to depend on the feedback type?  For \"flags\" it seems to do every 3 secs,  for Counters it seems to only do once and you have to uncheck/check \"Show Status\" to force a refresh.  Is the referesh interval for each type documented anywhere?

(2) Why does \"X10Status\" not expose the show status checkbox and value.  Surely it can be made to show status of the device? Appreciate this is more or an Enhancement request than a bug as I guess it didnt do this in early versions either.

Also any idea when there will be the new UCM firmware to support sensor responses ie s?nn return value which is currently broke?

J