#700 Modeling deadbands

Cory Mosiman Tue 7 May

Hey Haystack community,

Given an effective zone temperature setpoint, with an effective heating and effective cooling setpoint (which I believe just represents effective SP +- deadband), is there a standardized way to model this?

How do people handle modeling deadbands in general?


Paul Bergquist Tue 7 May

Laurie Reynolds Wed 8 May

The Zone model doesnt apear to reference a db but is essential in any control loop.

As a control specialist, I would like to see Proportional, Integral and Derivative terms added too. (p, i, d). However, as I thought about this further, the db, p, i, and d terms are properties of the control loop not the Zone.

The link provided was to a set of terms separated by spaces, am I right to understand that in a haystack ontolgy, a property would be named as zone.air.temp.sensor, ie dot notation?

I'm a newbie to Haystack but have been working with semantics for several years. I'm interested to know how a recommendation to include db is incorporated into the base standard.

Cory Mosiman Thu 16 May

Hey Paul - thanks for the info. So if I am to understand correctly:

zone air temp occ cooling sp = 70

zone air temp unocc cooling sp = 75

So when the zone is occupied and in cooling mode:

zone air temp effective sp == zone air temp occ cooling sp == 70

How does it work if the zone has a heating and cooling setpoint, as in the case of a water source heat pump in a residential context, where the unit can cycle between heating and cooling mode?

Can you have effective setpoints for both heating and cooling? Or I guess in that case, the unitary equipment is really cycling between heating and cooling mode, so your effective sp is just cycling between the heating and cooling sp?

Thanks for any insight in advance, Cory

Paul Bergquist Thu 16 May

Yes, you can have both heating and cooling effective setpoints. The effective setpoints are generally calculated values that are manufacturer and product dependent. They take into account things like effective occupancy, setpoint from wall module or network, schedule next state, override state and cool or heat ramp.

Login or Signup to reply.