eQuest fan/exhaust static pressure units

I am trying to model a sewage detention facility using eQuest, which includes a odor control system. In the Air-Side HVAC, when I try to input 20 inch WG static pressure for fan (large head loss when pushing odorous gas through carbon chamber. ~16 in WG), eQuest is not allowing to do that because the maximum value allowed is 15 inch WG. Also try to input 20 inch WG in the exhaust fan, but the maximum value allowed is 10 in WG. I am wondering why eQuest has this limitation? Is there any way I can input more than 15 in WG static pressure for fan or exhaust?

XiaoLin

asked 2017-07-17 16:12:12 -0500

4.4k

__AmirRoth__

updated 2017-07-18 12:47:16 -0500

edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

3 Answers

Sort by

oldest

newest

most voted

Interesting project. Alternatively, you could try using the peak of 15 inches w.c. and adjusting fan system efficiency downwards to achieve the correct full-load fan power.

516

Nick Caton

answered 2017-07-19 21:04:21 -0500

edit flag offensive 0 remove flag delete link

Comments

To be more specific, you can simply multiply the overall efficiency for the fan by 15/20 to get the same full-load fan power.

Daniel (2017-07-20 05:27:25 -0500) edit

add a comment see more comments

You could try following the advice here to use a text editor to edit the text in your inp file.

I think you will still not be able to edit your value from the graphical user interface outside the allowable ranges. But you can edit your .inp file (open in a text editor and search for the keyword "SUPPLY-STATIC"), save the file and reopen it in eQuest.

I think it will then simulate with your out of allowed range value. You should confirm, by producing an hourly report on the system fan power, that the fan power result is really as you expect.

1.3k

Molly Curtz

answered 2017-07-19 16:33:28 -0500

edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

The eQuest interface enforces the DOE2.2 limits on various inputs. You can try using DIAGNOSTIC NO-LIMITS ..

But even that workaround is not enough for some inputs. @Daniel's comment about lowering the fan efficiency to achieve the desired fan kW is likely the best alternative.