Send TRNSYS-users mailing list submissions to
trnsys-users@cae.wisc.edu
To subscribe or unsubscribe via the World Wide Web, visit
https://www-old.cae.wisc.edu/mailman/listinfo/trnsys-users
or, via email, send a message with subject or body 'help' to
trnsys-users-request@cae.wisc.edu
You can reach the person managing the list at
trnsys-users-owner@cae.wisc.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of TRNSYS-users digest..."
Dear all
I'm receiving following error:
Specific fluid mass flow of active layer in surface 5 below minimum value of 10.04 kg/m^2*h. Please increase the minimum mass flow rate or use the autosegmentation feature of ...
I saw that this error was already reported in '08 (https://www-old.cae.wisc.edu/pipermail/trnsys-users/2008/003947.html), but apparently the cause wasn't really known.
Anyway the strange thing is that TrnBuild, in the "Definition Active Layer" says that the "min allowed inlet mass flowrate" is 10.79 kg/h. Trnsys in its error message says 10.04 kg/m^2*h. The real minimal mass flowrate that ever under all possible conditions happens in my simulation is 12 kg/m^2*h, but most time it's 18.75 kg/m^2*h (that's for sure, I did some experiments, outputting the mass flow rate)
So, I decided nevertheless to autosegment it, for fun I created 6 segments by choosing the "desired min. allo. in. mass flowrate" accordingly (e.g. 1 kg/m^2*h). Now the strange thing is that the simulation works for some time after eventually crashing down. But the super strange thing is that my "Entering load temperature (=Tel)" spikes from 25°C to 65°C in the first iteration, e.g. it = i-1, pump is not active, Tel = 20°C, then for it=i the HP goes on, and Tel is 65°C. Without segmenting the active layer it would be 25°C.
As far as I understand, segmenting shouldn't influence the entering load temperature, how and why does it spike this strong in the first iteration and why do I actually get this error ??? Am I getting something completely wrong ?
Thanks for any advice, help.
Philippe
Hi everyone,
I am currently using TRNSYS 17 / MS Visual Studio 2008 / IVF 11.1
As I was following the Programmer’ s Guide to create a new
component, I used the provided solution “Ivf111.sln” that includes 3 projects :
MyType, TRNDll and Type155.
Tell me if I am wrong : the MyType project is made to create new
types, since DLL settings are already set perfectly. Thus, I added the required
files (fortan code and some subroutines from the TESS source code file) and
rebuilt the whole solution (including the 3 projects) : it seems to work pretty
well (MyType.dll is sent to …Trnsys17\UserLib\ReleaseDLLs, I can see it)
But when I launched TRNSYS simulation, I got the following error
:
“TRNSYS Message 105 :
A TYPE was called in the TRNSYS input file but was either not
linked into trndll.dll or was not found in an external dll. A dummy subroutine
was called in its place. Please link the TYPE or remove it from the input file
Reported information : Type999 could not be located in either
the trndll.dll or in an external dll. Please relink the TRNDll.dll including
this Type or make sure that an external DLL in the \UserLib\DebugDLLs and
\UserLib\ReleaseDLLs folders contain the Type.”
How can it be ? It looks like the external MyType.dll does
not include my Type 999.
My fortran code (enclosed Type999.for) is mainly based on
Type559.for from the TESS library, I only changed some equations in the
appropriate area.
Does it sound familiar to anyone ?
Thank you very much for your time.
--------------------------------------------
Emmanuel
Watrinet
Pôle Construction Durable
Bouygues Construction SA
Tél : 06 . 42 . 76 . 17 . 63
e.watrinet@bouygues-construction.com
--------------------------------------------
--
Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et secrets. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee. Si vous n'etes pas le bon destinataire, nous vous demandons de ne pas lire, copier, utiliser ou divulguer cette communication. Nous vous prions de notifier cette erreur a l'expediteur et d'effacer immediatement cette communication de votre systeme.
Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized. If you are not the right addressee, we ask you not to read, copy, use or disclose this communication. Please notify this error to the sender and erase at once this communication from your system.