Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infer supply air temperatures for equipment #55

Open
pflaumingo opened this issue Nov 16, 2018 · 5 comments
Open

Infer supply air temperatures for equipment #55

pflaumingo opened this issue Nov 16, 2018 · 5 comments

Comments

@pflaumingo
Copy link
Contributor

The supply air temperature needs to be inferred based on the type of equipment that is present in a zone.

  1. Discuss in this thread the proposed logic
  2. Create an implementation design in the code
  3. Write tests
  4. Write code
@pflaumingo
Copy link
Contributor Author

Some of this will be dependent on #27.

@mdahlhausen
Copy link
Contributor

mdahlhausen commented Nov 26, 2018

See the standard_design_sizing_temperatures method in openstudio-standards.

Does this include what setpoint managers to assume as well? (scheduled, warmest reset, oat reset?)

I propose:

Does this include what setpoint managers to assume as well? (scheduled, warmest reset, oat reset?)

I propose:

  • Air-based VAV and zone cooling systems: 55°F.
    • Air loops have warmest reset to 65F (or we could use EMS code to implement ASHRAE Guideline 36).
    • Zone equipment is a fixed set 55°F
  • Air-based VAV and zone heating systems: 104°F (matches openstudio-standards). We could drop this to 95°F, as that is typically the maximum reheat temperature.
  • DOAS systems: 70°F +-2°F deadband, and ability to drop to 65°F in peak cooling condition. Or base this on an OAT reset. At IG, we also implemented a 'searching' scheme that would update the neutral SAT point every day to minimize fan energy.

I'll read through ASHRAE G36 and see if I can formalize that here.

@pflaumingo
Copy link
Contributor Author

pflaumingo commented Nov 26, 2018

What's most critical is ensuring sizing is appropriate for sensible and latent loads. I'm pretty sure EnergyPlus ignores setpoint managers and such during sizing so we shouldn't have issue there. The UI for finer tuning of energy models won't be there so as long as we're applying something appropriate it'll be fine. Resetting temperatures is fine provided we don't fail to account for appropriate latent loads. For systems used for total load that reset, how should we control for latent loads? We can use humidistats for some objects, but DX coils don't allow for humidity control. EMS?

For the DOAS system, should we control humidity more appropriately than just a 70F supply temp?

@mdahlhausen
Copy link
Contributor

You are right about sizing not accounting for setpoint managers.

I suppose there could be conditions where latent load drives the sizing instead of sensible load. For the vast majority of systems, 55F cooling supply temperature at design is enough to handle all latent loads.

For DOAS systems, I've seen a 60F dewpoint design temperature. I think I can set controller right after the controller to make sure it hits that dewpoint?

@pflaumingo
Copy link
Contributor Author

This sounds good to me. Yeh, try with a controller for the dewpoint control as I'm not sure it's doable with a DX coil. I think it may be possible by wrapping a DX:TwoStageWithHumidityControlMode in a coil system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants