[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TRNSYS-users] Type157 w/schedules
Sorry, as I see your question has already been answered. (CSTB currently has some email problems).
Werner
-----Message d'origine-----
De : keilholz, werner
Envoyé : mardi 4 décembre 2007 15:30
À : AKAMINE Yoshihiko; trnsys-users@engr.wisc.edu
Objet : RE: [TRNSYS-users] Type157 w/schedules
Dear Yoshihiko,
Unfortunately I am not an expert in air flow modelling. If you have questions about the physics of COMIS, you should consider discussing them in the COMIS mailing list at http://tech.groups.yahoo.com/group/comis/
Sincerely,
Werner Keilholz
-----Message d'origine-----
De : AKAMINE Yoshihiko [mailto:akamine@arch.t.u-tokyo.ac.jp]
Envoyé : mercredi 28 novembre 2007 17:44
À : keilholz, werner; trnsys-users@engr.wisc.edu
Objet : Re: [TRNSYS-users] Type157 w/schedules
Dear Werner
Thank you very much for your kind help.
I tried to use type-14h, but there were some gaps at time.
So, I used type-9a.
In this schedule, I set the opening factors; 0 to 1 each time step.
If opening factor was 0, out put data of zone-ventilation-supply (ach/hr) was 0.
So, I think that opening and closing windows schedules seem to work correctly.
But, if opening factor was not 0, out put data of zone-ventilation-supply were too much.
And they were not changed acording to the time step.
For example, zone-ventilation-supply (ach/hr) were 250 to 765 ach/hr.
I may misunderstand the way of setting the schedules.
If you have an experience like above-mentioned,
please give me some advices.
Sincerely.
----- Original Message -----
From: "keilholz, werner" <werner.keilholz@cstb.fr>
To: "AKAMINE Yoshihiko" <akamine@arch.t.u-tokyo.ac.jp>; <trnsys-users@engr.wisc.edu>
Sent: Tuesday, November 27, 2007 10:36 PM
Subject: RE : [TRNSYS-users] Type157 w/schedules
Dear Yoshihiko,
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).
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
'Actual Factor for links with schedules-N'
(where N is the number of the link in the COMIS air flow network definition).
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.
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
.\Trnsys16\Studio\Lib\comis-demo\Documentation
or if you have COMIS in
\comis32\Documentation
Hope this helps,
Werner
________________________________
De: AKAMINE Yoshihiko [mailto:akamine@arch.t.u-tokyo.ac.jp]
Date: lun. 26/11/2007 21:41
À: trnsys-users@engr.wisc.edu
Objet : [TRNSYS-users] Type157 w/schedules
Dear TRNSYS Users,
I'm trying to simulate about cross-ventilated building
with TRNSYS 16.01.0003 and COMIS 3.2.
I would like you to teach me how to set the opening and shutting schedule of windows
in the Coupled Project (TRNSYS-COMIS).
In the COMIS stand alone, the schedule work normally.
However, it does not work in the Coupled Project, windows are always opened...
----
Dr. Eng., Yoshihiko Akamine, Proj. Assist. Prof.
Grad. School of Eng., The Univ. of Tokyo
Hongo 8-3-1, Bunkyo-ku, Tokyo 113-8656 JAPAN
Phone/Fax +81-3-5841-6208
E-mail: akamine@arch.t.u-tokyo.ac.jp
_______________________________________________
TRNSYS-users mailing list
TRNSYS-users@engr.wisc.edu
https://www.cae.wisc.edu/mailman/listinfo/trnsys-users
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************