Comfigurator 3.3.0 and 3.3.1 list of changes

[ident]

Comfigurator 3.3.0 will soon be available ([color=\"#0000ff\"]3.3.1 will be the next release, see later post)[/color]
The list of changes from 3.2.9 are

New Features

• Supports Firmware Upgrade by Comfort Bus of modules SEMs, UCMs connected to 3rd party systems (eg Comfort, KP06, KNX, CBus, Velbus, Universal, GSM). Modules with firmware 6.000 and above can be upgraded by Comfort Bus
  
• Prompts for \"Press F0 on Keypad\" when doing firmware upgrade by direct connection (ie to UCM or KT03) or by Comfort Bus
• Shows meaning of Error messages when any error encountered during Firmware upgrade
• CMS account codes allow Hex codes B to F as well as 0 to 9 (contact ID)
  
• Response wizard creating KNX commands are default 3 level format instead of 2 level format
• Number of retries for some commands in Comfigurator chaged from 3 to 1 to reduce delays when there is no reply
  

Bug Fixes

• Fixed BUG SCS/RIO ID could be set to 0
• Fixed BUG KP06 wrongly scanned as KP03
• Fixed BUG KT03 could not be used to Write to EEPROM for KNX and other modules if a UCM firmware was too old (which is not relevent because it is KT03 which is being used to write to the external UCMs EEPROM)
• Fixed BUG - Reading a ccl file with Siren Duration < 1 second caused the siren Duration to be 0 resulting in an indefinate siren duration
• new release of Comfort Bus Monitor fixed bugs
  

Known Issues

• Rs232 connection will not be able to connect  if \"Via USB\"  was checked in USB connection, then changed to RS232 connection
  
• When reading a .CCL file created by Comfigurator 2, the Modules tab shows 8 UCMs, although the number of UCMs in Configuration > Number of UCMs is 1. However if any of the UCM names is changed in the Modules tab, then the number of UCMs will become 8.
• If actions 12 (Exit if Z) and 13 (Exit if NZ) are manually entered by keypad or by editing action codes, Comfigurator creates the wrong action codes. Action 12 and 13 are older actions which are not created by the Response wizard but may be used in older systems
• If actions 69 (Skip if >= value ) and 70 (Skip if < value ) are manually entered by keypad or by editing action codes, Comfigurator creates the wrong action codes. Action 69 and 70 are older actions which are not created by the Response wizard but may be used in older systems
• Rs232 connection will not be able to connect  if \"Via USB\"  was checked in USB connection, then changed to RS232 connection
• IR learner checkbox for \"old UCM\" has not been implemented
• In the KT03 Configurator, when zones are selected, then the zone name or properties are changed in Security > Zones, the KT03 affected zone does not track the changes. eg zone 2 is called zone 2 but if you change zone 2 name to something else, in KT03, the zone 2 name and text is not changed
• Read Zones from Comfort may change the setting of Virtual Inputs incorrectly. Avoid reading from Comfort and writing back to Comfort for this reason as some normal zones may become Virtual and vice versa
• Bug in the sequence of If actons below

              If ........
                 action...
                 action...
              Else
                  If ...
                     action...
                     action ....
                  Endif
[color=\"#ff0000\"]                  If ...
                      action
                  Endif
[/color]               Endif

           Response wizard changes the position of the above actions in RED
              If ........
                 action...
                 action...
[color=\"#ff0000\"]                  If ...
                      action
                  Endif
[/color]              Else
                  If ...
                     action...
                     action ....
                  Endif
               Endif

• The sequence of If actions below causes Response Y not to be performed
  

[size=\"2\"][color=\"navy\"][font=\"Arial\"]          If Flag Tmr-Day <> 0 Then[/font][/color][/size][size=\"2\"][color=\"navy\"][font=\"Arial\"]
              Do Respinse X[/font][/color][/size][size=\"2\"][color=\"navy\"][font=\"Arial\"]
           End If[/font][/color][/size] [size=\"2\"][color=\"navy\"][font=\"Arial\"]          If Flag Tmr-Day <> 0 Then
              Do Response Y
          End If[/font][/color][/size]
[size=\"2\"][color=\"navy\"][font=\"Arial\"]       The workaround is to use the following actions instead, which is more efficient
[/font][/color][/size]
[size=\"2\"][color=\"navy\"][font=\"Arial\"]          If Flag Tmr-Day <> 0 Then[/font][/color][/size][size=\"2\"][color=\"navy\"][font=\"Arial\"]
              Do Respinse X[/font][/color][/size][size=\"2\"][color=\"navy\"][font=\"Arial\"]
              Do Response Y
          End If[/font][/color][/size]

[TheMax74]

Firmware update via bus is one of the best upgrade. Thanks!

[wexfordman]

Would it be possible to build into comfigurator some
Support for the iPhone app?

For example, can comfigurator be used to creat the iPhone output file instead of via the cytech uplod page?

Would be cool too if comfigurator could have entry for the additiOnal data required for the iPhone app, such as camera ip addresses, external ip
Address and LAN address and port numbers for iPhone app to access comfort etc!

Might be an avenue to start allowing more
Customised confuguration of the iPhone app also in the longer term (eg amending text for iPhone app home control
Menu etc, I did this myself by amending the output file
In notepad for example)

Regards
Eamon

[ident]

Getting info from a computer into iPhone is not straightforward. we decided that an email was the best and easiest way to do that.

[wexfordman]

Hi Ident,

I understnd the reasonn for using email to install the file into the iphone, but I was not suggesting to change this.

I was suggesting to  change the way the app file was generated,  using comfigurator to generate the iphone file, instead of the current method of upploading to cytech page. The installation of the file into iphone would remain as with the email method.

In addition , if comfigurator could used to generate the iphone app file, then the iphone app set up fields could also be entered into comfigurator:-
system name
 internet address and port number
lan address andport number
camera addresses etc

In this way, a fully configured iphone app file could be generated without requiring to update or configure within the iphone app.

Would make it very easy to install on multiple devices etc, and pretty much idiot proof to install for end users etc ?

[ident]

It should not make any difference whether Comfigurator were to generate the fields or a script as is being done now
The script parses the cclx file so  whatever is in the cclx file can be extracted, like the LAN setting

However Comfigurator does not have an Internet IP address setting (as that is not needed) so that could not be extracted.

[ident]

Comfigurator 3.3.1 will be released soon instead of 3.3.0 with the following fixes that were found in 3.3.0, and a few  interesting new features;
Bug Fixes:

1. When reading a .CCL file created by Comfigurator 2, the Modules tab showed 8 UCMs, although the number of UCMs in Configuration > Number of UCMs is 1.  Now the number of UCMs in the Modules tab will be that in Modules and Settings.
   
   
2. If actions 12 (Exit if Z) and 13 (Exit if NZ) are manually entered by keypad or by editing action codes, Comfigurator created the wrong action codes.
   
   
3. If actions 69 (Skip if >= value ) and 70 (Skip if < value ) are manually entered by keypad or by editing action codes, Comfigurator creates the wrong action codes. Action 69 and 70 are older actions which are not created by the Response wizard but may be used in older systems
   
4. Fixed problem with IF condition when it follows a previous IF statement or if it is nested within another IF statement
   
   
5. Time-out for commands have been increased to 6 seconds so that Firmware Upgrade commands will not time out
   
6. Fixed Bug in Bus Monitor, and add firmware upgrade command description.
   

New Features

1. Reading From Comfort had a problem then Responses Names and Descriptions had no information so it was difficult to work out what the Responses did. Now there is an option to \"Autogenerate Descriptions and Names\" from the actions where Comfigurator will try to generate meaningful Names and Descriptions for each Response. This will be a great help in trying to figure out how the system has been programmed if the original cclx file has been lost.
   
2. The \"Delete Unreferenced Responses\" function has been changed to  \"Delete Unreferenced and Unfixed\" Responses\". Unreferenced Responses may be used by third party devices via the Do Response command so Deleting Unreferenced Responses would have deleted these Responses. Responses which are used but not referenced can be \"fixed\" to avoid this. Fixed  Responses show in bold, and their Response number is changed when new responses are added or deleted.

Known Issues

1. Rs232 connection will not be able to connect  if \"Via USB\"  was checked in USB connection, then changed to RS232 connection
   
   
2. IR learner checkbox or old UCM has not been implemented

Comfigurator 3.3.1 beta can be downloaded from https://www.cytech.biz/comfigurator.html

[ident]

This may be a problem for Comfigurator 3.2.9i and above including 3.3.1

If a UCM with RS232 interface may have a problem to connect after 3.2.9, please use the following steps to correct the problem

1. Change the connection from Rs232 to USB
2. The checkbox \"Via KT03\" should be visible. Uncheck the checkbox to disable Via KT03
3. Change the connection back to Rs232

When the USB \"Via KT03\" box is checked it sets the baud rate of the USB connection to 38400 baud. However it does the same for Rs232 as well Hence if the connection is changed to Rs232, it will not be able to connect

This will be fixed in 3.3.2