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.
Hello, I'm trying to use Type 169 to utilize Python in Trnsys.As one of the input values of Type 169, we used Dry bulk temperature of Type 33c.
However, the following warning message appeared.
[TRNSYS Message 33: An inconsistent connection has been defined in the TRNSYS input file. ...]
I used weather data embedded in the TRNSYS file with type 15-2.
And what I don't understand is that when I changed other inputs (such as properties), the simulation worked.
Is there anything I should consider when I use Type33c with Type169?
Thank you for taking the time to read this question 🙂
Hyeontak, that warning is not something about which to be concerned. Many TRNSYS components set three letter codes (for instance a mass flow rate in kg/h has the unit code "MF1") that correspond to the units of their inputs and outputs so that the TRNSYS kernel can check for unit consistency in output-input connections. Since the Python communicator is generic its inputs and outputs don't have codes associated with them. Typically that means that the code is set to either "DM1" (for dimensionless) or sometimes "NAV." When you connect to that input or from that output the kernel flags the mismatch and generates a warning.
kind regards,
David
