Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Comfigurator 4.0.x
#1
The new Version of Comfigurator 4.03  has the following changes
Comfigurator 4 can be installed with  Comfigurator 3.x.x in the PC, This allows  the old comfigurator 3 to be used eg with old cclx files if necessary due to compatibility problems

Known Bugs
  • when  upgrading firmware ;after logging in and right clicking on Controller to  "upgrade firmware from local file" and selecting the cbf file, the message "CBF file not compatible with the firmware to be upgraded" is seen, but after a scan for modules  then it can upgrade. Also if start a new template, an  upgrade can be done without any error message.
  • if comfort is Optimum firmware, opening ULT or EMS file system and connecting and logging in to the system will get exception. This will not happen for EMS or ULT. Normally iComfigurator should warn that the file system is not matched to the firmware
  • When  firmware upgrade fails, for any reason and there is an attempt to upgrade again,  Comfigurator log in fails because many commands are sent at log in while UCM in bootmode can only reply to 1 command at a time.
  • After log in if ther eis no  scan for modules, download firmware upgrade will select the non-arm firmware
  • Scan for Modules sometimes gets error "Scan for Modules failed"
Bugs Fixed
  • Corrupted cclx files were sometimes scanned wrongly as ARM
  • Phone numbers screen  does not show sms permissions when 1st phone is not Voice or SMS (eg phone is is CMS)
  • HIO could not be detected after scan for modules
  • fixed bugs with multiple repeated outputs in responses or displayed Outputs in Comfort register
  • fixed bug with UCM ID 0 or 1  wrongly detected when there is a plug in ETH03 in CM9001
Changes
  • In Zones "Duplicate EOL settings" checkbox shows a warning message before confirming so the box is not checked by mistake
  • supports new  gsm5 module
#2
(10-14-2025, 07:19 AM)slychiu Wrote: The new Version of Comfigurator has the following changes
Comfigurator 4 can be installed with  Comfigurator 3.x.x in the PC, This allows  the old comfigurator 32 to be used eg with old cclx files if necessary due to compatibility problems
Are cclx files backward compatible with Comfigurator 3.x.x? Will they upload correctly to the UCM/Pi?
#3
Are cclx files backward compatible with Comfigurator 3.x.x? Will they upload correctly to the UCM/Pi? 


yes cclx files are compatible with Comfigurator 3. Note that Comfigurator 3 is not uninstalled when you install Comfigurator 4. You can use Comfigurator 3 if you encounter any problems
\

UCM/Pi write and read should not be affected by the new Comfigurator
#4
Comfigurator 4.0.4

Bugs fixed
  1.  When upgrading firmware after logging in and  after right clicking "upgrade firmware from local file", the message CBF file not compatible with the firmware to be upgraded, but after a scan then it can upgrade. aso if start a new template and do upgrade there is no message This is a bug from Comfigurator 4
  2.  If comfort is OPTIMUM, opening ULT or EMS file system and connecting to the system will show an  exception. This will not happen for EMS or ULT
  3.  When firmware upgrade fails,  and there is an attempt to upgrade again in boot mode, comfigurator log in fails because many commands are sent at log in while bootmode can only reply to 1 command at a time at the same time.
  4. After log in if dont scan for modules, download firmware upgrade will select the old Toshiba firmware instead of ARM
  5.  Scan for Modules sometimes gets error "Scan for Modules failed"
  6.   Sunset Response for EMS in Comfigurator is incorrect


Forum Jump:


Users browsing this thread: 1 Guest(s)