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.
Is it possible to run real time simulations longer than 24 hours?
Setting the Pacemaker Input Delay to -1 to indicate 'real time' causes my simulation to get stuck and stop responding after 24 hours. I have to use Windows Task Manager to close TRNExe (Status Not Responding).
Using a Delay of 12 seconds with the same time step of 1 minute, my one week simulation (168 hours) completes after the expected 33.6 hours without problems.
I am using Trnsys 17. The problem also occures after removing custom types, building and weather data, reproduced with the attached simplified *.dck/*.tpf. I also tried different simulation start and stop times, as well as a shorter timestep 0.15 minutes with the same result: After 24 hours Trnsys is not responding.
Edit: Can not attach zip/dck/tpf file
A_Weiss 19/04/2023 8:50 pm
@hilcontroller I put a Pacemaker and plotter in their own project in Trnsys18 and have it running right now. I'll let you know in 24 hours if it becomes unresponsive in Trnsys18 as well. I don't see any revision notes that suggest any changes with the pacemaker between Trnsys17 and Trnsys18. If it doesn't work in Trnsys18 either, I would email the issue and the simplified .tpf to your distributor for tech support. Unfortunately Trnsys17 is no longer (officially) supported, but your distributor may still be able to take a look if their availability allows.
Update April 20, 2023: My project is at 25.02 hours and still running. Either there was a bug fix between Trnsys17 and Trnsys18 that fixed the problem, or the problem is influenced by some component or simulation setting other than the pacemaker and online plotter.
HILcontroller Topic starter
25/04/2023 1:34 pm
Thank you for testing it. Did you use the 32-bit or 64-bit Version of Trnsys 18?
I have also installed and tested it with the Trnsys 18 Demo Version (64-bit) and it did run longer than 24 hours. But after installing the full version of Trnsys 18 (32-bit) the simulation gets stuck at 24 hours again.
Trnexe not responding and I have to use the task manager to close it. I contacted the support.
