[TRNSYS-users] Problems using several types in a project

David Bradley bradley at tess-inc.com
Tue May 29 07:42:34 PDT 2007


Kevyn,
   This is a fairly common problem but unfortunately, one for which 
there is no single answer. Essentially what is happening is that the 
Type is reusing some previously calculated values each time it 
executes instead of recalculating everything. Most likely there are 
some items that are not being placed into the STORAGE() array but 
which are being used again. To get an idea what I mean, look at the 
code for Type34; not only does is reread the parameters whenever 
INFO(1) has changed but it also recalculates a number of values based 
on those parameter values.

   The simplest way to solve the problem is by cheating a little bit. 
You can copy the *.for file for your PCM component, give it a 
different Type number, compile, and link it into the DLL; that way 
there will be no reuse of calculated variables. Otherwise, the best 
method is by using the debugger to step one line at a time through 
the code and see where the results start to differ when you have one 
versus two instances of the Type.
Cheers,
  David


At 05:05 5/29/2007, JOHANNES Kevyn wrote:
>Dear TRNSys users,
>
>We developed a new TYPE to simulated PCMs behaviour coupled with 
>TYPE 56. Unfortunately, there are problems when more than 1 PCM TYPE 
>is introduced into the project. The TYPE is dynamically design 
>(number of nodes within the PCM layer, number of layer on both side 
>of the PCMs layer the STORAGE vector, etc.), the parameter, as well 
>as the inputs are read at each time step (the IUNIT is forced at 
>each type read: IUNIT=INFO(1)) and as well as the STORAGE vector.
>
>No problems are identified using only one TYPE in a project but when 
>more than one TYPE is used (we just copy and paste the first type 
>and we change an input), the PCMs TYPES inputs seem to be mixed. The 
>time step used has also an influence on the results.
>
>We might think that the state of the nodes at each time step from 
>several PCMs TYPES is mixed from one unit to another (e.g. within 
>the STORAGE vector). But we think we have followed the documentation 
>on the use of several TYPEs within the same project.
>
>Does any one have an idea?
>
>
>
>
>************************************************************************************
>This footnote confirms that this email message has been scanned by
>PineApp Mail-SeCure for the presence of malicious code, vandals & 
>computer viruses.
>************************************************************************************
>
>
>
>_______________________________________________
>TRNSYS-users mailing list
>TRNSYS-users at engr.wisc.edu
>https://www.cae.wisc.edu/mailman/listinfo/trnsys-users

****************************************************************************************
Thermal Energy System Specialists (TESS), LLC
David BRADLEY                           2916 Marketplace Drive - Suite 104
Partner                                        Madison, WI 53719
Phone: (608) 274-2577 USA
Fax: (608) 278-1475
E-mail: bradley at tess-inc.com
Web Pages:  http://www.tess-inc.com     and      http://www.trnsys.com

"Providing software solutions for today's energy engineering projects"
****************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20070529/894087d4/attachment-0005.htm>


More information about the TRNSYS-users mailing list