Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

eQuest standard file writing errors encountered

asked 2019-01-18 12:05:41 -0500

knud.hermansen's avatar

updated 2019-01-18 15:02:07 -0500

I am reviewing a eQuest model built with eQUEST 3.65.7158 (which I can't even find on the doe2 website). I was given the pd2 and inp files. A few weeks ago I was able to load this model and run the building simulation. I am able to load the model that I've run before; but, now when I attempt to run the model I get:

Error: -1 standard file writing errors encountered

I've tried using both eQuest 3.65 builds 7173 & 7175.

I have already checked out the following threads without success:

There are no errors or issues with the .bdl file and indeed it ran just fine a few weeks ago.

Any ideas as to what my issues could be?

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2019-01-21 11:49:24 -0500

Try loading only the inp file: When you open eQUEST, click on "Select and Existing Project to Open". Then, in the dropdown box located at the bottom right corner select "DOE-2.2 BDL Input Files" and point to your inp file. Once the model has been loaded, change the weather file in the project properties if you haven't done it when you loaded your inp file.

By doing that you'll loose everything that was in you pd2 file, however, the pd2 file contains pretty much only information about what was selected in the Wizard. If you are reviewing the model in the detail interface, you probably don't need to know what was selected in the Wizard.

edit flag offensive delete link more


Thanks for the suggestion. I'll give this a try and let you know if it worked.

knud.hermansen's avatar knud.hermansen  ( 2019-01-21 17:30:55 -0500 )edit

This did ultimately help me. When I tried to load the input file eQuest gave me a hard time because there was also a pd2 file. But as I was trying to reassign the file path I realized that the path name was too long. When I moved the pd2 and inp files to the desktop things ran fine.

knud.hermansen's avatar knud.hermansen  ( 2019-02-05 16:29:40 -0500 )edit

answered 2019-01-18 14:07:29 -0500

Here is what someone else has recommended:

edit flag offensive delete link more


I looked at this one and there are no errors in the .bdl file. As I mentioned the model ran perfectly a few weeks ago. Sorry, I should have mentioned some of the sites I already Googled.

knud.hermansen's avatar knud.hermansen  ( 2019-01-18 14:58:33 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer


Question Tools

1 follower


Asked: 2019-01-18 12:05:41 -0500

Seen: 1,576 times

Last updated: Jan 21 '19