Hannah,
Georgios's comment is a valid solution to the problem that you are
facing (i.e. make multiple copies of your component, each with a
different Type number). Since it can become difficult to manage code
fixes in multiple copies of the Type, another solution is discussed
in section 7.3.16 of the Trnsys17 Programmer's Guide manual.
Kind regards,
David
Dear all,
I have a problem with a TRNSYS
type
that I have written myself.
In a new model I am using this
type
twice. The two identical types are not connected to each other
and they
have different input values.
But still the two types are
influencing
each other. After the first time step the input mass flow of the
first
type is used in the second type.
Does anyone have any idea what
the problem
could be and how I can solve it?
Thanks and best regards,
Hannah
--
Dipl.-Ing. (FH) Hannah Neumann
Division Thermal Systems and
Buildings
Fraunhofer Institut für Solare
Energiesysteme
ISE
Heidenhofstraße 2, 79110
Freiburg,
Germany
Phone: +49 (0) 7 61/ 45 88 - 54
31 Fax: +49 (0) 7 61/ 45 88 - 91 32
hannah.neumann@ise.fraunhofer.de
www.ise.fraunhofer.de
_______________________________________________
TRNSYS-users mailing list
TRNSYS-users@cae.wisc.edu
https://mailman.cae.wisc.edu/listinfo/trnsys-users
--
***************************
David BRADLEY
Principal
Thermal Energy Systems Specialists, LLC
22 North Carroll Street - suite 370
Madison, WI 53703 USA
P:+1.608.274.2577
F:+1.608.278.1475
d.bradley@tess-inc.com
http://www.tess-inc.com
http://www.trnsys.com
|