![]() |
|
Comfigurator 2.9.9 - 2.9.11 Beta - 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 2.9.9 - 2.9.11 Beta (/thread-1304.html) |
- slychiu - 01-20-2009 The Show status for Sensor should be avaiable in the release version the s?nn command to the UCM will return the value of the addressed sensor nn in hexadecimal We do have plans for Wizcomfort to be updated after the Comfigurator 3 is released. I dont know if open source is viable, but if any software developer would like to create their own version, let us know [user=876]juwi_uk[/user] wrote: Quote:Would it be possible to have the \"Show Status\" checkbox in the control menu when the \"feedback Type\" is \"Sensor\". Been trying to check the Temp of SCS 1 in basically anything! - wexfordman - 01-20-2009 [user=1]slychiu[/user] wrote: Quote:Can you send your cclx file to support@cytech.biz so we can check if it is a bug or due to something in your programming? Hi, Will send on the file, but just thinking and a few other queries come up. Sorry again if they are basic, but thinking on my feet at the moment, as I am in work. Can you explain the difference between cclx and ccl fiel format ? 2.9x gives you the option to save as either I think. I am also getting the cwm02, so was playing cwm designer software , and this would not recognise cclx I think, so I tried to save my files as ccl in comfigurator to use. Sorry, as you said also, the sunset flag is one I created manually, I will be using an external x10 device to detect sunset/sunrise and change flag status. Now that comfort II is on the way, I\'ve got that expensive feeling that I want to change out my x10 network to cbus, but going into a whole different price bracket now :-0 I have din rail x10 modules, so the wiring should be very similar, might try and do it gradually!! Regards, Eamon - slychiu - 01-20-2009 ccl files are the format used in Comfigurator 2 cclx are the native format for 2.9.x (eventualy to be released as version 3). cclx files are in xml format You are correct, only ccl files can be used in CWM for now Send the file in the format in which you found the problem reported - wexfordman - 01-20-2009 Hi, I was editing my previous post as you were replying to it ![]() I was using the cclx format, but last night when I noticed that the cwm design application needed ccl, I just converted to ccl using the 2.9 beta (save as .ccl). Is this okay to do ? Eamon - slychiu - 01-20-2009 We found a problem in the conversion to ccl All the zone types have Night Mode disabled. You can edit the night mode setting in the zone types manually - wexfordman - 01-20-2009 Thanks, I will check and update when I get home tonight. Will also send you both config files, ccl and ccxl fyi, but I am now using ccl only. Regards, Eamon - juwi_uk - 01-26-2009 Should the s?nn work at the moment? Is the temp sensor on SCS1 then s?08 If so what response should I expect back as I dont think it does anything right now (but difficult to tell as incoming messages on the bus might be masking it) Also is there a Comfigurator build after 2.9.10 yet (posted 10 days ago) as I\'m keen to see if Smartfit errors fixed yet (ie 2.9.11?). Currently following errors still present in 2.9.10 after opening my live 2.2.3 CCL file: 1 - \"Get NightTime\" - wizard now creates \"GetParameterValue NightTime\" but it doesnt convert this on opening CCL file. 2 - Any Smartfit command of type \"Smartfit OverrideSchedule...\" 3 - \"Get SensorRegister n\" in 2.2.3 \"n\" was the name whereas now it is back to the sensor number so convert of CCL fails. As and observation seems to be a bit inconsistent when the name versus sensor number is used!! Hope this is useful. Regards Julian - slychiu - 01-27-2009 The new version 2.9.11 is available from http://www.cytech-technology.com/temp/software/Comfigurator2.9.11.zip The problems mentioned should be fixed However the known bugs still present in this (and previous) versions are
- wexfordman - 01-28-2009 Hi, I am getting the following exception when trying to download to comfort Unhandled exception: System.ArgumentOutOfRangeException: Index and length must refer to a location within the string. Parameter name: length at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at Comfort.ComfortPanel.GetPanelInfo() at Comfort.Form1.Login(Boolean needEngineer, Boolean getInfo) at Comfort.Form1.downloadPCComfortToolStripMenuItem_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Using windows vista home premium with cwm02 regards, eamon - slychiu - 01-29-2009 This and previous versions of 2.9.x are not able to download or upload to UCMs [color=\"#ff0000\"]with firmware 5.159 and below. This will be fixed in the next Comfigurator beta[/color] |