Welcome to the TRNSYS Users Forum.
The forum is a place where people can interact and have discussions about different topics involving the use of the TRNSYS software package. Here you can post topics for discussion or questions on using TRNSYS and get advice from other users or TRNSYS experts. This forum is not intended for detailed technical support. Users should contact their distributor’s hotline for such assistance.
Some tips for success on using the forum:
- Follow the Forum Rules posted in Forum Administration.
- There are categories for different types of topics and questions. Post your topic or question into the proper category.
- Before posting a topic or question search the existing topics (and the TRNSYS Users listserv archive or Post archive) to see if a similar topic or question has already been answered.
- Use a descriptive topic name. Don’t use attention getting subjects, they don’t get attention and only annoy people.
- State the version of TRNSYS and which add-ons your are using.
- Include enough specific details for your topic of question to be answered. Just posting “Why am I getting an error?” without describing the specific error and what you are trying to do when you get the error will not receive a response that fixes your issue.
- Remember when people help you, they are doing you a favor. Be patient, help people out by posting good descriptions of what you need help with, and be polite even if a response does not solve your issue.
- Moderators may edit your post for clarity or move your topic to a more appropriate category.
Dear TRNSYS Users,
I experienced a problem with Type390 from Transsolar. I am using TRNSYS 18.04 32 bits, and I downloaded the Type390 from Transolar. Since, there was only a 64 bit version, I tried to compile a 32 bit version, using Visual Studio 2019 and Intel Fortran Compiler 2022. Everything was fine, and the Type390.dll was build, both as Release and Debug version. They are located in their respective directory C:\TRNSYS18\UserLib\ReleaseDLLs and C:\TRNSYS18\UserLib\DebugsDLLs.
Nevertheless, when I tried to use Type390 in my project using Simulation Studio, I have an error "Type390 could not be located in either the trndll.dll or in an external dll". I found also in the listing file "Type390.dll was found but did not contain any components from the input file."
Can somebody tell me what mistake I have make ?
Thanks
Philippe
Hello @papillon,
I'm not sure what might have gone wrong, but I don't see any issue with the software you're using or the steps you followed. Thank you for the thorough documentation of what you've tried so far!
The fact that it found the Type390.dll means the issue isn't the folder location of the .dll's. Unfortunately TRNSYS sometimes throws that "Type XXX could not be located" error when it has trouble reading from a .dll as well as when it can't find the .dll.
You could try compiling a 32-bit version of the Type390 source code with the TypeStudio included with Trnsys18. I have used TypeStudio in a pinch sometimes to create standalone .dll's when Visual Studio has failed me for unknown reasons. It uses a different Fortran compiler than Intel's compiler, so sometimes it works when Visual Studio fails.
Just out of curiosity, is there a specific reason you are not using the 64-bit version of TRNSYS? I think many softwares have retired their 32-bit version, so I'd be interested to know what use cases there are for maintaining a 32-bit version.
Hello,
Many thanks for your answer.
Regarding TypeStudio, I tried yesterday and didn't succeed with the error mentioned in the enclosed file.
I tried again today, and in a first attempt, I get the same error, and in a second attempt it works ... I don't know why ...
Now, Type390.dll is found by TRNSYS kernel, and it seems to work fine ...
I am using 32 bit version, since I have TRNSYS types I made in the past, and I lost my old fortran source code when I changed my computer ...
Sunny regards
Philippe
