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.
In want to share information how to use the Calling Python from TRNSYS18 with CFFI Type 3157 in 32-bit .
For correct installation, the DLL needs to be recompiled using the original source code without modification. Therefore, an appropriate Python 32-bit version needs to be installed. For me it worked using the version python-3.10.0rc2 and installing as described in section 2 of the Type 3157 documentation. I also tried to recompiled with newer Python 32-bit versions but got an error message.
After compilation, the DLL needs to be placed in the ReleaseDLL folder and the python interface needs to be rebuilt as described in section 4. If you get an error message when executing PythonInterfaceTester.exe, you should proceed testing the example files in the Simulation studio, anyway. At least for me it worked despite the error when executing PythonInterfaceTester.exe.
It needs to be mentioned that some packages (e.g. tensorflow) are unavailable in Python 32-bit. So if you need packages, that can be installed in 32-bit, you should consider to switch to 64-bit.
