[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TRNSYS-users] Creating a new type



Emmanuel,
  To add to what Matt said, the TRNDll in the ..\Trnsys17\Exe directory is either compiled in Debug or Release mode (a compiler project setting). By default it is compiled in release mode and looks for external DLLs in the ..Trnsys17\UserLib\ReleaseDLLs directory. Check all of the Notices in the log file from your simulation run. In addition to error message 105, you will find a number of messages telling you what Types were found in what DLLs and it will probably give you an indication if the problem is in finding the DLL or if it is finding the DLL but not finding your Type.
Best,
 David


On 8/18/2010 10:57, WATRINET, Emmanuel wrote:

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.
  
_______________________________________________ TRNSYS-users mailing list TRNSYS-users@cae.wisc.edu https://www-old.cae.wisc.edu/mailman/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
bradley@tess-inc.com

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