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.
Hi,
I have created a new component to connect with Type56 (Multizone building). After compiling the code and defining the variables properly in the proforma, I am still receiving Error 105, which indicates that it cannot link with trndll.dll or locate it in the external DLL.
I have double-checked, and the Release DLL folder does contain the generated file, but the error persists. I am attaching a screenshot for reference.
I would be very grateful if someone could help me identify the cause of this issue and suggest a solution.
Thank you in advance for your support.
coming. I am attaching the screenshot for your review. I would be thankful if someone could help me to figure it out this issue.
The problem may be identifiable by filtering the messages for notices (opposed to warnings and errors) and looking for a few scenarios.
1) There is no notice about the DLL your type was compiled in. If this is the case, check for another notice that indicates whether the TRNDll.dll was compiled in debug or release mode. If the TRNDll.dll is compiled in debug mode then external DLLs will be loaded from the \UserLib\DebugDLLs directory.
2) There is a notice about the DLL your type was compiled in but it does not contain your type. If this is the case, check the source code of your type for the line "!DEC$ATTRIBUTES DLLEXPORT :: TYPE205". Ensure that the type number is the same as subroutine name and proforma type number.
3) There is a notice about the DLL your type was compiled in and it does contain your type. This one would be rare but if your code loads some other DLL that is failing to load then you will still get the error you are seeing.
As a note, are you compiling your type in the Type Studio or are you using the Intel compiler in Visual Studio?
cheers,
John
kashif10 Topic starter
19/08/2025 5:16 pm
@johnsteinbergs Hi John, Thank you for your detailed response. I went through all of the points you mentioned, step by step, and I did not find any errors in compiling or naming the type. When I compile, both the Debug DLL and Release DLL are created with the correct type name. I took screenshots of the source code, proforma, and the compiled DLLs (in both DebugDLLs and ReleaseDLLs folders), and I am attaching them here for your review. The error message I continue to receive is that the new type was not linked into trndll.dll. I am also attaching the error message output for reference. Hopefully, by reviewing the screenshots, you might be able to identify where the problem is occurring. I would greatly appreciate your guidance
can you also please screenshot the list of all the notices that are displayed along with the error? I am not so interested in the error or in the warnings so you can filter those out and just screenshot the notices. If we aren't able to see what is going on from the notices then we'll probably need you to send some files to a techsupport hotline but let's hold on that for now.
~david
kashif10 Topic starter
19/08/2025 6:05 pm
@davidbradley
Thanks David. Please find the notices screenshots.
Notice 26 indicates that Type205 was found in Type205_x64.dll suggesting that there is an error somewhere in the source code of Type205. I would recommend you contact your distributor's technical support team with the Type205 source code and list file (.lst). It may be helpful to also attach your project (.tpf) and and any other files that are needed in order to run it.
The list of distributors and their contact information is found here https://sel.me.wisc.edu/trnsys/sales/distributors.html .
cheers,
John
kashif10 Topic starter
19/08/2025 9:23 pm
@johnsteinbergs
Thanks John. I will check the source code again.
kashif10 Topic starter
19/08/2025 11:26 pm
@johnsteinbergs
Hi John,
I am having an issue with my energy modeling other than this. Is there any possibility, if I can get the chance to take you online meeting for short time to figure it out the issue.
JohnSteinbergs 25/08/2025 9:29 pm
@kashif10
It would be a more effective use of time to contact your distributor's technical support team with your project file (.tpf), list file (.lst), and any other files that are needed in order to run it.
-John
