<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=DE-CH link=blue vlink=purple> <div class=Section1> Hi Lukas<o:p></o:p> <o:p> </o:p> Recently (1.12.2009) there was a similar question on the forum, I think. Aizaz gave this answer:<o:p></o:p> <o:p> </o:p> ==<o:p></o:p> There has been an extension to day type facility recently and is available in the current version. One can define day types in addition to legacy week/sat/sunday from context>calendar>day types. This should ideally be done before defining controls and operations information. Once daytype "summerday" <o:p></o:p> and "winterday" are defined in the calendar (and associated with Julian days of the year), different control laws and schedules can be associated in the same control loop as with week/sat/sunday.<o:p></o:p> ==<o:p></o:p> <o:p> </o:p> Regards<o:p></o:p> Achim<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: esp-r-bounces@lists.strath.ac.uk [mailto:esp-r-bounces@lists.strath.ac.uk] On Behalf Of Lukas Swan (Dal) Sent: Donnerstag, 7. Januar 2010 22:00 To: esp-r@lists.strath.ac.uk Subject: [esp-r] Zone control sensors - cannot change with control law?<o:p></o:p> </div> </div> <o:p> </o:p> Hello-<o:p></o:p> <o:p> </o:p> I am modeling a house that has multiple zones and both heating and cooling.<o:p></o:p> Each zone has an independent electric baseboard convective heaters and independent thermostats (i.e. individual zone sensor and actuation).<o:p></o:p> There is also a central cooling system that distributes to each zone proportionally (volume based) and is controlled by a single thermostat on the first floor level (i.e. central sensor and distributed actuation).<o:p></o:p> <o:p> </o:p> I was planning on modeling this using zone control loops.<o:p></o:p> Heating during heating months would be completed using a basic controller for each zone with the sensor and actuator at that specific zone’s air point.<o:p></o:p> Cooling during other months would be completed using a master/slave scheme (Laws #1 and #21), where slave zones would then reference the master zone air point as the sensor.<o:p></o:p> <o:p> </o:p> However, it appears that the specification of the sensor and actuator are outside the scope of a particular period, and are fixed for a given control loop.<o:p></o:p> Also – it appears that each zone can only reference one control loop.<o:p></o:p> <o:p> </o:p> Does anyone have a solution to this problem?<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Lukas Swan<o:p></o:p> Dalhousie Univ.<o:p></o:p> Canada<o:p></o:p> </div> </body> </html>