![]() |
|
WizComfort 1.9.3 Beta - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html) +--- Forum: WizComfort (https://www.comfortforums.com/forum-21.html) +--- Thread: WizComfort 1.9.3 Beta (/thread-3037.html) |
- ident - 08-25-2012 After a long time on other projects, we are finally working on WizComfort again WizComfort 1.9.3 Beta is now available for download from https://www.cytech.biz/wizcomfort.html?category_id=98 The purpose of the Wizcomfort is
Saved UCM Connection Settings
Bugs Fixed
- juwi_uk - 08-25-2012 A few quick observations: - Module scan needs to be aligned with that in configurator; see attached screenshot of before and after. - The \"Communication\" tab is greyed out; is this still work in progress? - Should (this is a question)the \"E?\" be suppressed from the monitor window when reading the Event log? These really bloat out the results and duplicating that on the Event Log window? - I hope (requested also for sake of my ComfortClient app too) comfort will allow WizComfort to one day to read existing reminder settings directly from Comfort rather than(could be out of date) entries from the CCLX file. - Could we have \"Read Configuration from CCLX\" option too on settings as I guess at the moment you have to restart Wizcomfort again to re-fetch? - Holidays. If you change these then I guess these can be written back to the CCLX. Question is can they be written to Comfort too then as there is no function in the Comfort Protocol to do this specifically; are you using some sort of direct register read/writes to do this? Interested so I can do in ComfortClient too! Julian - juwi_uk - 08-25-2012 Sorry, my mistake, I see this is enabled/disabled by the \"Audio on Keypad\" property in Wizcomfort settings. Quote:- The \"Communication\" tab is greyed out; is this still work in progress? Julian - slychiu - 08-26-2012 Quote:- Module scan needs to be aligned with that in configurator; see attached screenshot of before and after.Yes will align Quote:Should (this is a question)the \"E?\" be suppressed from the monitor window when reading the Event log? These really bloat out the results and duplicating that on the Event Log window?The Monitor should show exactly the communications between the UCM and PC. Supressing any message will hinder troubleshoooting Quote:- I hope (requested also for sake of my ComfortClient app too) comfort will allow WizComfort to one day to read existing reminder settings directly from Comfort rather than(could be out of date) entries from the CCLX file.Reminder settings can be read from Comfort using the UL (upload ) command. ComfortClient can do the same using the information on addresses from iomap.cym Quote:- Could we have \"Read Configuration from CCLX\" option too on settings as I guess at the moment you have to restart Wizcomfort again to re-fetch?That should not be a problem, but I dont understand why the cclx file would change while Wizcomfort is open? Quote:- Holidays. If you change these then I guess these can be written back to the CCLX. Question is can they be written to Comfort too then as there is no function in the Comfort Protocol to do this specifically; are you using some sort of direct register read/writes to do this? Interested so I can do in ComfortClient too!Comfigurator uses only the Comfort protocol, no hidden commands The DL command writes to comfort using locations, and so could ComfortCleint - juwi_uk - 08-26-2012 Quote:That should not be a problem, but I dont understand why the cclx file would change while Wizcomfort is openYou\'ve been in Wizcomfort for a while, made a number of changes, but now had second thoughts and easier to re-read the config than to undo all of your singular changes. - juwi_uk - 08-26-2012 I\'ve noticed that if you Change the holidays and write to Comfort then the values don\'t get updated to Comfort. Address 0x288 is the DL address I was looking for in the Monitor log trace. Also seems Holidays (and presumably other data too) is read from the CCLX on start-up. Given this is aimed at end users and you give them the ability to write settings back to Comfort then surely on start-up you should also be reading from Comfort too rather than the CCLX data; unless of course you need the latter to overlay more descriptive labels. That way the user changed data starting point is that currently running in the Comfort system and not whatever the engineer last uploaded via Comfigurator. Minor bug BTW; use the \"Update Comfort\" action and the popup window displayed is titled \"FormProgress1\". Julian |