Difference btw no fan schedule and fan schedule set to 0

2 posts / 0 new
Last post

Hell all,

I have a residential building where each suite has a PSZ (constant volume)
system (hot water heating from boiler, DX cooling). I'm trying to
understand the difference as far as eQuest is concerned between specifying *a
fan schedule whose values are set to 0* (i.e. OFF for all hours) and *not
specifying any fan schedule* (i.e. undefined). In both cases, I've set the
indoor fan mode to *Intermittent* and I've set the Night Cycle control
to *Cycle
On Any*.

For the most part, it doesn't change the heating, cooling, or fan power
that much (about 10%) but it does significantly change the number of hours
my fans are running as well as the hourly profiles (airflow, as well as
heating and cooling load profiles). Evaluating one residential unit for
comparison purposes, I've noticed that running with a zero fan schedule
reduces the fan hours by about half compared to running with no assigned
schedule.

The graph below is what I get when I don't specify any fan schedule
(undefined). You will note the airflows go from very small values (less
than 100 cfm) to a max of 675 cfm.
[image: image.png]

The graph below is what I get when I specify a fan schedule whose values
are set to 0. You will note the airflows range from a min of 225 cfm to 700
cfm. If you remove the hours with less than 225 cfm from the above graph,
you more or less end up with the below graph.
[image: image.png]

Is anybody able to explain why eQuest treats these two different fan
control scenarios differently...ultimately I'm trying to understand which
is more accurate from a real life perspective.

Thanks,
Chris

Chris Hadlock's picture
Offline
Joined: 2012-01-23
Reputation: 0

Hi Chris,

I have checked out something over this and shall try to help you with.

The case that you are considering which is undefined or not setting any
schedule is the case where there is 24 hour working schedule considered.

The thing that eQUEST considers when there is no schedule is it would
automatically will consider the case of 24 hour working.

The case that you are inferring as with set 0 for unoccupied hours is the
correct way to model the building in eQUEST rather if you would try to have
undefined schedule or with not any schedule then you might land with the
incorrect results as it is not the liking way to model the building in
eQUEST. It would rather the undefined schedule will show 24 hour working
fan which is as per proper result getting is totally wrong.

So to mode lit correctly you are required to have the proper schedule to
have a work with.
Hope this might help.

*Thanks and Regards,*
Sharad.Kumar
Freelancer
Energy Simulation and Day-lighting
India.

----------------------------------------------------------------------------------------------------------------------------.

1. Difference btw no fan schedule and fan schedule set to 0
(Chris Hadlock)

---------- Forwarded message ----------
From: Chris Hadlock
To: equest-users at lists.onebuilding.org
Cc:
Bcc:
Date: Tue, 29 Oct 2019 10:56:50 -0400
Subject: [Equest-users] Difference btw no fan schedule and fan schedule set
to 0
Hell all,

I have a residential building where each suite has a PSZ (constant volume)
system (hot water heating from boiler, DX cooling). I'm trying to
understand the difference as far as eQuest is concerned between specifying *a
fan schedule whose values are set to 0* (i.e. OFF for all hours) and *not
specifying any fan schedule* (i.e. undefined). In both cases, I've set the
indoor fan mode to *Intermittent* and I've set the Night Cycle control
to *Cycle
On Any*.

For the most part, it doesn't change the heating, cooling, or fan power
that much (about 10%) but it does significantly change the number of hours
my fans are running as well as the hourly profiles (airflow, as well as
heating and cooling load profiles). Evaluating one residential unit for
comparison purposes, I've noticed that running with a zero fan schedule
reduces the fan hours by about half compared to running with no assigned
schedule.

The graph below is what I get when I don't specify any fan schedule
(undefined). You will note the airflows go from very small values (less
than 100 cfm) to a max of 675 cfm.
[image: image.png]

The graph below is what I get when I specify a fan schedule whose values
are set to 0. You will note the airflows range from a min of 225 cfm to 700
cfm. If you remove the hours with less than 225 cfm from the above graph,
you more or less end up with the below graph.
[image: image.png]

Is anybody able to explain why eQuest treats these two different fan
control scenarios differently...ultimately I'm trying to understand which
is more accurate from a real life perspective.

Thanks,
Chris
_______________________________________________
Equest-users mailing list
Equest-users at lists.onebuilding.org
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org

Sharad Kumar2's picture
Offline
Joined: 2015-05-21
Reputation: 0