[TRNSYS-users] Strange error with self-created components

[David BRADLEY]

There is actually not much more that TRNSYS can report. The Windows API 
call that TRNSYS uses to try and load the Type basically returns a 
"succeed" or "fail" flag. There is very little information in the "fail" 
flag that can be interpreted in any useful way to then be reported on to 
the *.lst file.
Regards,
  David


On 10/24/2013 04:38, Soppelsa Anton wrote:
> Dear Mr. Lee,
>
> In order for a programmers user's community to provide appropriate answers, it is always recommended to describe carefully the boundary conditions of the problem: (OS), version of the program, type and version of compiler used, version of eventually used external libraries, etc.
>   
> Having said this, I probably ran into the very same or similar problem trying to integrate a custom TRNSYS type I made myself with a third-party produced DLL.
>
> After careful analysis I have concluded that this problem arises when the dynamic loader finds the TYPE DLL (the file exists), but the chain loading process fails (This can happen, in my case this was due to a problem in the third-party library linked to the type DLL).
>
> It would be interesting to know if this is also your case.
>
> Essentially this is a case of poor error reporting by TRNSYS: it could give to the user a more specific error message.
>
> Sincerely,
>
> _ _
>
> Anton Soppelsa, Ph.D.
>
> EURAC research
> Institute for Renewable Energy
> Via Luis-Zuegg 11, I-39100 Bolzano
> t +39 0471 055 623
> f +39 0471 055 699
> anton.soppelsa @eurac.edu
> www.eurac.edu
>
> EURAC research
> Legal Seat
> Viale Druso 1, I-39100 Bolzano
>
> This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information.
> If you receive this transmission by error, please notify the author immediately by mail and delete all copies of this transmission and any attachments.
> Any use or dissemination of this communication is strictly prohibited by the "Privacy-Code", D.Lgs. 196/2003 and may lead to penal prosecution and liability for damages.
>
>  Think before you print
>
>
>
>
>    
>
> -----Original Message-----
> From: trnsys-users-bounces at cae.wisc.edu [mailto:trnsys-users-bounces at cae.wisc.edu] On Behalf Of C K Lee
> Sent: Thursday, 24 October, 2013 10:24
> To: Trnsys discussion group
> Subject: [TRNSYS-users] Strange error with self-created components
>
> Hello.
>
> When I run a simulation with self-created component (Type237), I receive very strange error message (see attached file).  Message 49 says that
> Type237 was found, but Message 73 says that Type237 could not be found.
> Can anyone advise how I can rectify the error?  Thank you!
>
> Best Regards
> LEE, Chun Kwong
> City University of Hong Kong
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users at cae.wisc.edu
> https://mailman.cae.wisc.edu/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
d.bradley at tess-inc.com

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