Hi Group,
Has anyone run into this error? See attached.
I have a chiller staging control in place that works great. When I click to add another control, I can give it a name, type (heating in this case), and method. When I click OK, it?s a crash. It doesn?t matter if I try to create from scratch, copy another control, or link to another control.
For a long, long time I have had eQuest configured for compatibility mode XP Service Pack 3 and Run as Administrator. No problems at all for over a year. I?ve never seen this AppCrash error before... OS is Windows 7.
Anyone have an insight or a hint?
Thanks!
David R. Weigel, PE
David,
I have experienced this is the past when adding chiller controls. From
what I remember, it also occurred when using XP. Assuming it is not a
Windows 7 problem, I believe that these errors occur when eQuest is
creating BDL tables in response to your input. Unlike past interfaces to
DOE-2, eQuest actually runs some (all?) of the BDL step as you enter data
in the interface, not when you click the calculate button. There are then
two possible reasons for the crash:
1. You are attempting to create a control that is not allowed in DOE-2, and
the BDL code doesn't know how to handle this, so it crashes. Check the
DOE-2 manual to ensure that what you are entering is allowed by DOE-2.
2. There is a bug in the BDL processor that causes a crash when your
specific combination of equipment control is entered.
When these crashes occurred, I didn't have the time to run tests to see
which actions cause a crash and which are allowed. If you can run a few
tests by incrementally changing a few inputs here and there and seeing
which cause a crash, you can determine if you are in case 1 or case 2 above
and act accordingly.
You also have the option of creating the control manually in the .inp file,
saving, and then opening in eQuest. However, I believe that this will have
a low probability of success since eQuest will run the .inp through the BDL
processor on opening the file which will likely cause a crash again.
Aaron.
Hi Group,
Has anyone run into this error? See attached.
I have a chiller staging control in place that works great. When I click to
add another control, I can give it a name, type (heating in this case), and
method. When I click OK, it?s a crash. It doesn?t matter if I try to
create from scratch, copy another control, or link to another control.
For a long, long time I have had eQuest configured for compatibility mode
XP Service Pack 3 and Run as Administrator. No problems at all for over a
year. I?ve never seen this AppCrash error before... OS is Windows 7.
Anyone have an insight or a hint?
Thanks!
*David R. Weigel, PE*
Thank you Aaron!
Good call. I verified it?s a bit of a rare bug, number 2 in your list. Adding my controls and systems to the .inp file with WordPad did nicely. It runs with no problems after inserting the new stuff that way.
The eQuest folks at Hirsch are looking into it.
Dave