[TRNSYS-users] Two instances of a type in one simulation

[David BRADLEY via TRNSYS-users]

Christian,

  Make sure that the new dll they gave you is in both the 
..\Trnsys17\UserLib\ReleaseDLLs\ and in the 
..\Trnsys17\UserLib\DebugDLLs\ directories. If you still get error 105 
then check the *.f90 code (you can open it with a text editor). There 
should be a line near the top that says:

!DEC$ATTRIBUTES DLLEXPORT :: TYPE3399

the name on that line is the important one for loading the DLL. The name 
of the file is not relevant. If the number in the DLLEXPORT line is 
wrong then the author should be able to make a quick fix and give you 
another compiled version of it.

kind regards,

  David



On 05/24/2016 09:52, Christian Herløv Krintel via TRNSYS-users wrote:
> David,
> Thank you for your reply. I have been in contact with the author of 
> Type399, as you suggested, who sent a recompiled .dll file with a new 
> type number.
> However, when running the simulation, TRNSYS cannot find the new type 
> in the dll libraries (error message 105).
> I also tried to rename the dll file to "Type3399.dll", which is the 
> new type name.
>
> I suspect that the source code was not adapted properly to the new 
> type number. I have the .f90 source code. Is there any way for me to 
> compile it myself? I tried using the following guide with the free g95 
> compiler, but I get errors. Maybe this guide is only for fixed format 
> .for files?
>
> http://sel.me.wisc.edu/trnsys/downloads/tutorials_and_examples/tutex17.htm 
>
>
> Any help would be greatly appreciated :)
>
> Best Regards
> Christian Krintel
> Technical University of Denmark
>
>
> David BRADLEY skrev den 2016-05-20 18:16:
>> Christain and Maroun,
>>  I would be very careful about workarounds. If you run a simulation
>> that has one instance of a component in it, then drag out a second
>> instance and the results of the first change then it is almost certain
>> that the Type was not programmed in such a way as to allow there to be
>> multiple instances in a simulation. They are sharing some data
>> structures internally and there isn't really any way of getting around
>> that except if you use a compiler to make a copy of the Type, give it
>> a new Type number, then recompile and link it into its own DLL.
>>  In general the better solution is to be in contact with the author of
>> Type399 (or with the distributor from whom you purchased it) and see
>> if they can assist.
>> kind regards,
>>  David
>>
>> On 05/20/2016 11:02, NEMAR Maroun via TRNSYS-users wrote:
>>
>>> ​Christian,
>>> I met almost the same problem two months ago, and I have solved
>>> hardly. I don't know how can I show you through email, if you could
>>> mail me your project and your PCM components to compare it with mine
>>> then to fix it for you. If there any problem with you PCM component,
>>> I'll make you know, if not I'll fix the problem the same way I've
>>> done.
>>>
>>> Best regards,
>>> MAROUN NEMAR
>>> Building performance engineer
>>> BUILDING ENERGY ANALYSIS & ENGINEERING
>>> T: 0620548116
>>> E: maroun.nemar at gmail.com
>>> web site : www.bureauveritas.fr [1]
>>>
>>> 2016-05-20 16:38 GMT+01:00 Christian Herløv Krintel
>>> <trnsys-users at lists.onebuilding.org>:
>>>
>>>> Dear TRNSYS users,
>>>> I have a multizone building model, where I want to use two PCM
>>>> components (Type 399) to model the ceilings of two adjacent rooms.
>>>> When I run the simulation I noticed that the two components
>>>> somehow share information. The PCM temperature is the same in both
>>>> components.
>>>>
>>>> I tried to switch the component order in the Control Cards, which
>>>> changes the PCM temperature, but they are still equal.
>>>> How can I run two instances of a type side-by-side? Is this a
>>>> limitation in how Type 399 was programmed?
>>>>
>>>> Best Regards
>>>> Christian
>>>> _______________________________________________
>>>> TRNSYS-users mailing list
>>>> TRNSYS-users at lists.onebuilding.org
>>>>
>>>
>> http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org
>>>
>>> _______________________________________________
>>> TRNSYS-users mailing list
>>> TRNSYS-users at lists.onebuilding.org
>>>
>> http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org
>>
>> -- 
>> ***************************
>> 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 at tess-inc.com
>>
>> http://www.tess-inc.com
>> http://www.trnsys.com
>>
>>
>> Links:
>> ------
>> [1] http://www.bureauveritas.fr/
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users at lists.onebuilding.org
> http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org

-- 
***************************
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 at tess-inc.com

http://www.tess-inc.com
http://www.trnsys.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20160525/7cc6e567/attachment.htm>