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) 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 all,
I'm currently working on a model that requires the usage of a multi-dimensional data interpolation, in my particular case with 1 independent variable.
For this purpose I've been using type 581 and so far we had no issues. However, when upgrading our TESS library to 18 version, it stopped working. When running a model including this type (or even the example found in ...\Tess Models\Examples\Utility Library\Multi-dimension Data Readers_5VAR_v2a.tpf) the trnexe fails showing a fortran error stating "file not found".
I replicated this issue on one of my colleagues laptops with also TESS 18 library installed.
Is this a known issue? Is there a possibility that we might have something not properlly installed?
I'd like to get some help regarding this. In the meantime we substituted type 581 for type 42c, however, it only allows for a maximum of 10 "number of values of independent variable" and our performance map has 22.
Kind regards,
Santiago.
Researcher
Institut de Recerca en Energia de Catalunya (IREC)
- 933 562 615
A_Weiss 20/10/2023 5:02 pm
@sescuder I confirmed the same behavior with the v18 TESS Utility library. It's not immediately clear what the problem is, but I'll get back to you if/when I learn more.
In the meantime, if you have an archived v17 version of the TESS Utility library, you could continue using the v17 version instead of the v18 version. All you have to do is go to your Trnsys18/UserLib/ReleaseDLLs folder, and replace the v18 Utility library (should be TESS_UT_v18_0_64.dll) with the v17 version (should be something like TESS_Utility_v17.x.0x_64.dll). The proforma for Type 581 changed as well between v17 and v18, so you'll also have to either use the v17 proforma or modify the v18 proforma to remove the 'interpolation code' parameters that were added with v18.
DavidBradley 23/10/2023 6:26 pm
@sescuder and @A_Weiss This is definitely a bug in the v18 libraries. We'll get a fix released with the next update. The three possible workarounds are 1. use the v17 version of the library as Angie suggested. 2. there is a similar (but somewhat less flexible) Type in the standard library (Type42). It is listed as HVAC: Conditioning Equipment. 3. if you are comfortable recompiling the TRNDll yourself you can build Type581 into the TRNDll as though it were a standard component.
kind regards,
David
SEscuder Topic starter
24/10/2023 6:46 am
@A_Weiss and @DavidBradley, thank you for your fast response. In the meantime we will work using the Type 42 or the type 581 from v17 library.
We will wait for the fix in the next update.
Kind regards,
Santiago.
