Comfort Automation/ Security System Forums > Software Applications > Comfigurator > Comfigurator 3.x Old Versions (Archive) > Comfigurator 3.6.4 |
Moderated by: admin | Topic closed |
Author | Post | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
ident Administrator ![]()
|
The new version of Comfigurator has been released after much testing. This can be downloaded from http://www.cytech.biz/comfigurator.html?category_id=98 There are many major improvements from the last version 3.5.6 Known Bugs
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
Last edited on Sunday Sep 29th, 2013 07:58 am by |
|||||||||
ident Administrator ![]()
|
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 GREY: 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 RED: Means that the module has not been discovered by a module Scan GREEN: 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. Last edited on Tuesday Jan 22nd, 2013 07:15 am by ident |
|||||||||
ident Administrator ![]()
|
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 http://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 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. 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 Administrator ![]()
|
Zwave Configurator (May require Zwave Firmware 7.xxx required)
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)
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 Last edited on Wednesday Jan 23rd, 2013 03:26 am by ident |
|||||||||
Home Comfort Distributors
|
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 UCM Pi Users
|
Hi Ident, could you elaborate on the velbus get status command ? Could this be used after a restart to get velbus status ? |
|||||||||
ident Administrator ![]()
|
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 Administrator ![]()
|
Home wrote: This is all great news thanks 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 Administrator ![]()
|
Comfigurator 3.6.4 is officially released Everyone is encouraged to upgrade from the link in the 1st post as soon as possible |
|||||||||
Home Comfort Distributors
|
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 ". |
|||||||||
ident Administrator ![]()
|
Either way should not cause any problem I prefer the stronger warning to scan for Modules to make sure that the user does do it. Scanning for modules is a much better way of getting the required info into Comfigurator for the new method of upgrading and other features |
|||||||||
Ian Member
|
Hi - I have a Comfort 1 and seem unable to scan for modules. Attachment: Scan fail.PNG (Downloaded 118 times) |
|||||||||
ident Administrator ![]()
|
What is the firmware version of your Comfort I? If is too old it may not be able to support Scan and you have to manuallly add the modules |
|||||||||
Ian Member
|
4.209 according to Wizcomfort |
|||||||||
ident Administrator ![]()
|
That version is probably to support the scan commands You will have to manually add the modules in Comfigurator > Modules Tab Better still, it may be time to upgrade to Comfort 2, as firmware 4.204 was released in 2004 |
|||||||||
Ian Member
|
Thank you for getting back to me. I would love to upgrade to Comfort 2 but at this moment can't afford to. :-( If you are having a sale on upgrade kits - let me know :-) |
|||||||||
ident Administrator ![]()
|
There is a config file which is not updated in Comfigurator 3.6.4 idstatus.cfg should be copied into the ComfiguratorConfig folder This file contains the status infiormation in the UCMs for Zwave, velbus and Universal UCM when the Get Status function is used. This UCM status is displayed in the status bar. Formerly the status could only be seen on the UCM Leds which is not convenient unless the case is open Last edited on Saturday Feb 2nd, 2013 01:06 am by ident |
|||||||||
ident Administrator ![]()
|
Sorry the idstatus.cfg file in the last post was not the correct one. That was actually the same file as in Comfigurator 3.6.4. Please use the attached file instead Attachment: idstatus.cfg (Downloaded 6 times) |
|||||||||
ident Administrator ![]()
|
Known Bugs found in Comfigurator 3.6.4
Last edited on Saturday Sep 28th, 2013 03:33 am by |
|||||||||
juwi_uk Member ![]()
|
I've noticed that if you minimise Comfigurator during a firmware update then you cant maximise it again and the firmware upgrade doesn't finish. I had to abort the process and start again. Julian |
|||||||||
ident Administrator ![]()
|
That is correct, you cannot open the window again until the upgrade is finished However the upgrade is still working in the background, and it will finish if you leave it. |
|||||||||
juwi_uk Member ![]()
|
I left it for a while but it never finished. |
|||||||||
ident Administrator ![]()
|
Unless Comfigurator hangs, then either the upgrade completes or there is an error, in both cases the upgrade process ends and you should be able to switch back to Comfigurator. Does this happen every time you upgrade fiirmware? |
|||||||||
ident Administrator ![]()
|
while comfigurator is minimised you can tell if the upgrade is still going on by loooking at the D11/D12 leds on the UCM. They keep flashing constantly and stop after the upgrade ends |
|||||||||
Ian Member
|
I am still having issues with the scan function. I have added modules manually as suggested but still get the error message Comfort or UCM firmware does not support scan function. Can I turn scanning off? |
|||||||||
ident Administrator ![]()
|
Have you upgraded Comfigurator to the latest 3.6.8? You should upgrade your UCM and Comfort firmware to the latest version Comfigurator 3.6.8 allows you to upgrade from the server by right cllicking on the module and selecting check for updates Scanning is a very important part of Comfigurator and cannot be disabled After upgrading firmware and Comfigurator let us know if there are any modules which cannot be scanned and show a screenshot But please start a new topic as this topic is to do with Comfigurator 3.6.4 only, and wil be closed |