Comfort Automation/ Security System Forums
Comfigurator 3.6.4 - Printable Version

+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html)
+--- Forum: Comfigurator (https://www.comfortforums.com/forum-20.html)
+---- Forum: Comfigurator 3.x Old Versions (Archive) (https://www.comfortforums.com/forum-87.html)
+---- Thread: Comfigurator 3.6.4 (/thread-3261.html)

Pages: 1 2 3

- ident - 01-22-2013

The new version of Comfigurator has been released after much  testing. This can be downloaded from https://www.cytech.biz/comfigurator.html?category_id=98

There are many major improvements from the last version 3.5.6

Known Bugs
  1. In KT03  adding a clock element causes an exception
  2. Read from Comfort with the option \"Auto-generate Names\" will cause an exception. Workaround is to select Option \"Keep Names from cclx fle\"
  3. When the cursor is in the Modules Tab and the UCM connections in Options > settings is changed, the screen jumps back to the Comfort Tab although the Modules Tab is still selected
  4. Write to KT03 may not work in some situations This was a  bug fixed in 3.6.4  but it may still occur but less often. The I/O monitor shows RS4x where 4x is the ID of the KT03- still investigating
  5. Bus Monitor has exception in some circumstances and wrong messages about illegal commands are shown
  6. In KT03 selecting all buttons on a page and Copying may cause exceptions
  7. Minimising Comfigurator during a firmware upgrade prevents going bac to Comfigurator until the upgrade ends
  8. If firmware upgrade stops due to no reply from Comfort, a dialog contiinue from last address appears, but if UCM/ETH02 is used, and connetion is lost, Comfigurator does not try to reconnnect before continuing the upgrade
  9. KT03 schedules - If Days of the week are checked the file saved and reopened, the days of week become unchecked. This is a problem with older versions as well
  10. Selective Write does not select Control Menu when Responses change which are assigned to the Control Menu. To workaround, please use Full WRITE. This may be a bug from older versions
The changes from 3.5.6 version are;

UCM Connection
The selection of UCM Connection has been further improved. Go to Options > Settings. The Saved Connection Settings are now here (instead of Configuration > System Information). If \"Override Saved Connection Settings\" is unchecked the Saved Connection settings for Local Network and Remote Network are shown. The saved connection settings are saved in the cclx file which is useful when UCM/Ethernet is used for Local and Remote connections. The saved connection settings for Local and Internet IP address and Port are exported to iPhone and Android apps


The actual connection setting is displayed in the Status bar at the bottom


The difference from 3.5 is that the Saved Connection settings are not entered in Configuration > System Information which is only shows the Connection settings (Read Only).

Modules Tab
Changes described in a later post

Changing IDs for Module Firmware version 7
Modules with firmware version 7 can have their IDs changed by dragging and dropping the IDs on the Modules Tab. This changes the IDs of 2 modules, eg UCM #1 can be dragged to UCM #2 position which causes the two modules at ID1 and 2 to swap their IDs

Sunrise/Sunset Times
The date of  Monday of each week is shown so it is easier to know which week is current


New Actions
Reset Module action 118 resets the module at specified ID (firmware 5.222)
Save to Event Log Action 119 saves to Event Log - can be used to save any event to the event log

Log in /Log Out
Comfigurator does not log out automatically after any operation which cause it to log in eg Write, Read, Execute, Scan etc. This allows information in Monitor I/O to be seen after certain actions


Check for Comfigurator Update
Comfigurator will check automatically for a new version every time it is started and gives an option to upgrade the software

Also, in Help Check for Update will update Comfigurator if a new version is available.


Firmware Upgrades
The method for Firmware upgrades has been simplified and improved. See the next post for details

KT03 Default Template
When a new KT03 is added, the kt03 default template kt03def.kt3x is loaded automatically instead of blank pages


IR Leaner
For ETH02, Increased buffer size to handle long IR codes or due to IR button pressed to long, so that this does not case an exception. Do NOT press and hold the IR button when learning IR codes

Bus Monitor
  • Bus Monitor will use the current UCM Connection Setting depending on whether Saved Connection Settings or Override Saved Connection settings is selected
  • Fixed bug Bus Monitor  changed the working folder for Comfigurator when a bus log is saved
  • Fixed Bug Bus Monitor exception when 2 modules have the same ID
  • New RS485 commands are support
  • Errors due to collision of messages are handled better
UCM Configurator changes
  • Zwave
  • Universal UCM
  • Velbus
Bugs Fixed

  1. Velbus unknown module causes cannot write to Comfort error
  2. Response numbers > max causes Alarm Type names to have FF in front so SMS alarm Names are blank
  3. When Bus Monitor file is saved, it changes the working folder for comfigurator and exception will occur when going back to Comfigurator
  4. Bus Monitor has exception when running Bus Analyse with 2 modules having the same IDs
  5. During Firmware Upgrade by Bus, UBF6 error message did not end the upgrade operation.
  6. DAC5 send command in Zwave does not use escape character 15
  7. Virtual Inputs for KNX cannot select zones 65 to 96 created in old version
  8. Setting Zone Types to Null in Security > Zones caused Zone Type (0) to be displayed. Not a real problem but has been fixed


- ident - 01-22-2013

Modules Tab and Scanning for Modules

The Modules Tab has a number of enhancements in the way the information is presented, making use of different colours for modules status

[color=\"#550000\"]GREY: [/color]Indicates that the module has not been found by Scanning yet, eg when the file has just been opened
BLACK: Indicates that the module has been discovered by scanning
[color=\"#ff0000\"]RED[/color]: Means that the module has not been discovered by a module Scan
[color=\"#00ff00\"][color=\"#000000\"]GREEN[/color]: [/color]Modules that have their ID changed but before the modules are reset  to activate the ID change. This applies to modules with firmware version 7 and above
BLUE: After scanning, a new module has been discovered but the number of Modules has not been written to Comfort yet so Comfort does not know about the new module ID


If a file has been opened with existing modules before a module scan has been done, the modules are shown in Gray



Scanning for Modules is done by Right-clicking on Modules and selecting Scan for all  Modules. This will discover all the modules that are connected to Comfort, which have their IDs set correctly without having duplicate IDs with other modules of the same type


Note that Modules discovered by the scanning may not be recognised by Comfort. In order for Comfort to recognise and poll for the new module, select \"Write Modules and Settings to Comfort\" as shown above (by right click)

After the scan, the modules will be in black


If a module in the configuration is NOT found by the scan, it will be shown in RED

The Status column in the middle pane also shows information like Scanned, Not Scanned, or Not Found

Hence if a module has been removed from the network perhaps temporarily, and thus was not found during the scan, it is not deleted but is shown in red. If the module was a KT03 or UCM/KNX where many hours of  programming work has been put in, the absence of the module during scanning will not cause the module with all its properties to disappear. It remains in the file and is not lost.

If you really want to delete the  module, then right click on it and select Delete Module.  However it is not possible to delete a module that is referenced by Responses or other elements.

There are also improvements  in the handling of modules that have changed IDs

Modules may have their IDs changed manually due to rearrangement or reconfiguration
If a Scan for modules finds that a module say UCM/KNX, has changed IDs say from ID 2 to ID 5 since the last saved configuration, Comfigurator will assign the module properties to the new ID. Hence the  KNX configuration that has been programmed will not be lost.

If there is an additional module of the same type compared to original configuration, the new module will have a blank configuration eg UCM/Zwave or UCM/Universal.


- ident - 01-22-2013

Firmware Upgrades

After scanning for Modules, the latest firmware for each module will be shown so you do not have to check for updates for every module like in 3.6.0


The Latest Version is shown next to the Current version as shown in the above screenshot.
Note that the screenshot shows some \"Current\" versions as higher than \"latest\" versions (eg GSM) because of beta firmware that have been installed.

Firmware Upgrades can now be done by checking for updates over the Internet (applies to modules with  firmware version 6 and above)

This is done in the Modules Tab. Right click on the desired module


Select \"Check for Firmware Updates\"
If the firmware of the module is lower than the current firmware on the Cytech server, the firmware wil be upgraded. After confirmation that the firmware should be upgraded, the progress bar will be seen



The Firmware can also be upgraded from a local file if you have already downloaded the cbf file from the Cytech Server at https://www.cytech.biz/firmware.html

To do this, select \"Upgrade Firmware from Local File\" after right clicking on the module as shown in the first screenshot above. Then browse to the location of the file

[color=\"#0055aa\"]Unlike the previous Comfigurator versions, you do not have to specify whether the firmware upgrade is \"By Direct Connection to PC\" or by \"Comfort Bus\" Comfigurator will know what method to use.
[/color]

In Comfigurator 3.6.x, Transfer > Upgrade, the only option is Upgrade Firmware by Programming Cable

The other options \"By Direct Connection\" and \"By Comfort Bus\" have been removed as they are replaced by the new method of right clicking on the module



- ident - 01-22-2013

Zwave Configurator (May require Zwave Firmware 7.xxx required)

  1. \"Get Status\" button will not log out after the status is obtained, Comfigurator will remain logged in to continue receiving status. Zwave 7.xxx will send status when there is any change, and not just when Get Status button is pressed.
  2. Colour Codes in Zwave Mapping  help to identify  various types of Nodes: Controllers (gray), UCM/Zwave (Blue), Virtual Node (Green), Slave Nodes (Black)
  3. After Virtual Node operations Comfigurator will automaticallly read EEPROM when required.
  4. Zwave Response Wizard supports a new Multilevel Dimming function
  5. If the Response sends commands to a Virtual Node a warning message  pops up \"Sending Zwave commands to Virtual Nodes is not recommended as it is not guaranteed to work”
  6. In Response Wizard. \"Basic Command\" renamed to \"Basic Set Command\". \"Status Request\" renamed  to \"Basic get Commands\", to comply with standard Zwave terminology
  7. UCM/Zwave will update Comfort counters and sensors from Zwave commands even when the counter value has not changed. This allows status of Zwave devices controlled by Comfort and other Zwave nodes to be synchronised
  8. Help Text for Zwave commands has been improved
The status messages show the status of the UCMs which were formerly available only by seeing the state of the LEds BUSY1, BUSY2, ERROR eg for Zwave

Normal/No error
EEPROM missing/faulty
EEPROM insufficent capacity
EEPROM data invalid
Communication error between UCM baseboard and Z-wave sub-module
UCM/Z-Wave not in any network
Waiting to receive network data. (Learn process)
Receiving network data. (Learn process)
Writing EEPROM. (Learn process)
Learn process success
Learn process completed with errors
Command transmitted.  Waiting for ACK
Z-Wave network busy/jammed (RF transmit error)
Unknown transmit error


Velbus Configurator (may require UCM/Velbus 7.xxx)
  1. Added Get Status Command, also status messages will update automatically (requires Velbus 7.xxx)
  2. Added support in Learn Mode for new Velbus Modules VMBDMI, VMB8PBU, VMB6PBN, VMB2PBN, VMB6PBB (requires Velbus 7.xxx)
  3. Write and Read EEPROM times reduced
  4. Counter will be updated from Velbus even if the value does not change.This allows status of Velbus  devices controlled by Comfort and other velbus modules  to be synchronised
The status messages show the status of the UCMs which were formerly available only by seeing the state of the LEds BUSY1, BUSY2, ERROR
eg for Velbus
Normal/No error
EEPROM missing/faulty
EEPROM insufficent capacity
EEPROM data invalid
Communication error between UCM baseboard and sub-module

These are the status formerly only seen by reading the LEDs on the UCM/Velbus




- Home - 01-22-2013

This is all great news thanks


We have carried out and continue to carry out services and upgrades additions etc to C1 boards and associated equipment.

I suspect that the C1 firmware is unable to provide any information about the status or version of individual components _ BUT i have noticed that when converting ccl files to .cclx that the number of modules etc NEVER translates correctly ( well at all !) so basically I import a ccl file - I get a message saying modules incompatible or similar then have to add the correct number of modules (which can be found from the modules and setting page) and save file.

- wexfordman - 01-22-2013

Hi Ident,

could you elaborate on the velbus get status command ? Could this be used after a restart to get velbus status ?

- ident - 01-23-2013

Get Status in this context does not mean the Velbus relay etc status

It is the status of the UCM/Velbus which is shown in the status line
eg

Normal/No error
EEPROM missing/faulty
EEPROM insufficent capacity
EEPROM data invalid
Communication error between UCM baseboard and sub-module


These are the status formerly only seen by reading the LEDs on the UCM/Velbus




- ident - 01-23-2013

[user=41]Home[/user] wrote:
Quote:This is all great news thanks


We have carried out and continue to carry out services and upgrades additions etc to C1 boards and associated equipment.

I suspect that the C1 firmware is unable to provide any information about the status or version of individual components _ BUT i have noticed that when converting ccl files to .cclx that the number of modules etc NEVER translates correctly ( well at all !) so basically I import a ccl file - I get a message saying modules incompatible or similar then have to add the correct number of modules (which can be found from the modules and setting page) and save file.

The message you get after you convert to cclx is
\"The Modules in Modules tab does not correspond to the modules in Configuration > Modules and Settings\"

This is a warning means that you have not done a Scan for Modules
It is not an error in translation of the file or an error in comfigurator

For Comfort 1, you can still scan for Modules. The information about Firmware number is not available but the presence of the modules can be discovered

After you scan for modules, the number of modules in Modules and Settings will be updated and you will no longer get this message



- ident - 01-27-2013

Comfigurator 3.6.4 is officially released
Everyone is encouraged to upgrade from the link in the 1st post as soon as possible


- Home - 01-27-2013

Ah yes

The situation arises BECAUSE when we go to an old C1 install with the old .ccl file we will have converted and cleaned up the file BEFORE visiting site.

I just wondered why the n of modules could not be taken from the list as a start! And then use a comments box something along the lines of \"we recommend a scan for modules \".