<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>[TRNSYS-users] Type157 w/schedules</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText83790 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Dear Yoshihiko,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>When you are coupling an existing COMIS
project with a TRNSYS project, only the TRNSYS time loop is executed when the
simulation is run from the TRNSYS project. Therefore, schedules defined in COMIS
will not be executed. (They are only executed when you run the COMIS project
using 'Edit Air Flow network' when right-clicking on type 157). </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>If you wish to open and close windows in
the air flow network (or change fan speeds, etc.), you have to use and
additional input to type 157. These additional inputs already exist in your
project : they are called </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>'Actual Factor for links with
schedules-N'</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>(where N is the number of the link in the
COMIS air flow network definition).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>So now you only have to connect these
inputs to a schedule defined in TRNSYS (not in COMIS). For example, you can
use a forcing function (Utilities/Forcing Function/General/Type14h) to define
the schedule. Then connect the output of type 14 to the input of type 157.
</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>The meaning of the value depends of the
component used in the COMIS airflow network for link N : an opening factor
(0..1) for windows, a fan speed for fans, etc. (see COMIS User Guide in
</FONT></DIV>
<DIV dir=ltr>.\Trnsys16\Studio\Lib\comis-demo\Documentation</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>or if you have COMIS in </DIV>
<DIV dir=ltr>\comis32\Documentation</DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Hope this helps,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Werner </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>De:</B> AKAMINE Yoshihiko
[mailto:akamine@arch.t.u-tokyo.ac.jp]<BR><B>Date:</B> lun. 26/11/2007
21:41<BR><B>À:</B> trnsys-users@engr.wisc.edu<BR><B>Objet :</B> [TRNSYS-users]
Type157 w/schedules<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Dear TRNSYS Users,<BR><BR>I'm trying to simulate about
cross-ventilated building<BR>with TRNSYS 16.01.0003 and COMIS 3.2.<BR><BR>I
would like you to teach me how to set the opening and shutting schedule of
windows<BR>in the Coupled Project (TRNSYS-COMIS).<BR><BR>In the COMIS stand
alone, the schedule work normally.<BR>However, it does not work in the Coupled
Project, windows are always opened...<BR><BR>----<BR>Dr. Eng., Yoshihiko
Akamine, Proj. Assist. Prof.<BR>Grad. School of Eng., The Univ. of
Tokyo<BR>Hongo 8-3-1, Bunkyo-ku, Tokyo 113-8656 JAPAN<BR>Phone/Fax
+81-3-5841-6208<BR>E-mail:
akamine@arch.t.u-tokyo.ac.jp<BR><BR>_______________________________________________<BR>TRNSYS-users
mailing list<BR>TRNSYS-users@engr.wisc.edu<BR><A
href="https://www.cae.wisc.edu/mailman/listinfo/trnsys-users">https://www.cae.wisc.edu/mailman/listinfo/trnsys-users</A><BR><BR><BR><BR><BR><BR><BR>************************************************************************************<BR>This
footnote confirms that this email message has been scanned by<BR>PineApp
Mail-SeCure for the presence of malicious code, vandals & computer
viruses.<BR>************************************************************************************<BR><BR><BR></FONT></P></DIV>
</BODY>
</HTML>
<BR>
<BR>
<BR>
<BR>
************************************************************************************<BR>
This footnote confirms that this email message has been scanned by<BR>
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.<BR>
************************************************************************************<BR>
<BR>
<BR>