[TRNSYS-users] file close error
Diego A. Arias
daarias at wisc.edu
Thu Dec 15 16:13:41 PST 2005
I think that this problem is caused by a type that is reading something
at the end of the simulation, maybe a temporary file like a summary
created during the simulation, and finds a conflict. I had seen a
similar problem when a simulation was stopped before the end of the
simulation, the temporary file was created but was not deleted, and then
the next time that the project was run it caused a conflict.
I would recommend deleting the summary files that are created in your
simulation, and try running the simulation again.
If this does not work, please feel free to send me your project files
and I will be glad to take a look at them.
Bharath Krishna Karambakkam wrote:
> Hi Michaël and Rémi,
> Thank you for your responce. Getting rid of the Type155.dll from my
> UserLib direcoty did solve my problem with the libmx.dll not found. But I
> still get the file close error at the end of the simulation.Could you
> let me know what could be causing this. Please find attached the error
> message in my previsous mail.
> Thank you,
> ----- Original Message ----- From: "Michaël Kummert"
> <michael.kummert at gmail.com>
> To: <trnsys-users at engr.wisc.edu>
> Sent: Thursday, December 15, 2005 1:30 PM
> Subject: Re: [TRNSYS-users] libmx and file close error
>> Krishna, Rémi,
>>> I experienced this problem as well. The file libmx.dll is
>>> associated with the Type 155 that helps trnsys communicate with
>>> matlab. For some reason, the the .dll file that is for Type 155
>>> calls this libmx.dll even if you don't have any reference to matlab
>>> in your program. The only way I managed to eliminate the error is
>>> by removing the Type155 .dll from my program files.
>> I believe that what you see is one of the problems that happens when
>> you update to 16.00.0038 without uninstalling your previous version
>> I also believe the setup program prominently displays a warning about
>> that, but of course who reads warnings anyway?
>> If that is the case you may end up with 2 versions of Type155.dll:
>> one in /Exe, the other one in /UserLib. You should delete the one in
>> Loading Type155.dll is only possible if Matlab is installed on the
>> machine. For that reason, TRNSYS will only load Type155.dll if
>> Type155 is used in the deck. But in order to do that it has to know
>> where to find Type155.dll and handle it in a special way. If you have
>> an extra copy of Type155.dll in UserLib, TRNSYS will do what it does
>> with any DLL there: it first loads it to know which Types are in it,
>> then it possibly unloads it if the Types are not used in the deck.
>> But if Matlab is not installed, it fails at the first step.
>> While we are at it, I also believe you will have an extra copy of
>> Type62.dll left in UserLib if you have updated to 16.00.0038
>> "improperly". You should also delete that one if present. And if
>> anyone still using 16.00.0037 or an older version reads this, do not
>> delete anything!
>> Kind regards,
>> Michaël Kummert
>> Michaël Kummert
>> École Polytechnique de Montréal - Génie Mécanique
>> Case Postale 6079, succursale Centre-Ville
>> Montréal QC H3C 3A7
>> Tel: +1 (514) 340-4711, Ext. 3367
>> Fax: +1 (514) 340-5917
>> Email : michael.kummert à polymtl.ca
>> TRNSYS-users mailing list
>> TRNSYS-users at engr.wisc.edu
> TRNSYS-users mailing list
> TRNSYS-users at engr.wisc.edu
Diego A. Arias
Solar Energy Laboratory
University of Wisconsin - Madison
1500 Engineering Drive
Madison, WI 53706
More information about the TRNSYS-users