Reply to Thread

exactly... I did have an "overzealous energy saver" who when they left early one thursday, pressed the temp not-occupied button. Needless to say the next day following that was miserably cold for them, as the not-occ button puts the system into temp unocc for 24 hours not the inverse 2 hrs from the temp occ button. I got a laugh out of that!

Oh, but they learn quick when you start 'tightening' the schedule.

I bet 1 of 5 occupants know about the function of the override button.

Hey crab, I did this about 3 weeks ago on a few sites out of my paranoia, but haven't seen any one hit the temp-occ button yet, I am going to set up an extra 7350h this weekend and test this myself so I'll know what happens.

What do your trend logs show?

Trend occupancy if you haven't already and try to coordinate that trend in a zone(s) that the override button is likely to be hit.

These questions are just paranoia, I have configured and installed these about 3 mos ago, and started thinking-hey, what if- I have had no complaints or issues but I also want them to be right, ya know. This project involves so many buildings, I just don't want to have to go back and alter configs on every building!

Covering ALL the bases aren't you knottyjabe? I don't blame you! I agree with ControlsInMt, don't know for sure in this instance but logic says...

I can't find anything that actually answers that. Logic would think it would go back to last known state, which would have been unocc, but I couldn't verify it.

Thanks to all for your help, my last issue with this is; if it is saturday(schedule is set as un-configured but in un-occupied, looking for a change of state on monday at 0600), and someone comes in to do some weekend work, and presses the "temporary occupied" button, the stat will go temp occupied for a set amount of time, when this override time expires does the stat go back to un-occupied or does it stop all control and wait for monday at 0600 when it will return to occupied mode?

Yea, agreed, but you can't talk those people into anything different, like you said spec's spec!

Originally Posted by knottyjabe

That is what this project is...

Wow. There are a lot less expensive and flexible ways than using those, but if that's what's spec'd....

Originally Posted by ControlsInMT

They don't have a base-wide EMCS?

That is what this project is...

I just got an anwser back from Honeywell and they said it will follow the current state until the next change of state, so weekends set for un-configured preceded by an un-occupied will remain un-occupied for the whole weekend. Thanx RAD1

Third!

Loytec can do it.

They don't have a base-wide EMCS?

I believe un-configured time slots will follow the mode of the last configured time slot.

Honeywell T-Stat Spec Software

I have a large project at Fort Leonard Wood involving Honeywell T7350A’s and T7350H’s. I have configured these with the T-Stat Spec software I downloaded off Honeywell’s website. My question is, when you are configuring the schedules, say if you have a building occupied Mon-Fri 0600-1730 with Sat and Sun un-occupied, do I leave Sat and Sun “un-configured”? Does the un-configured setting on those days make the space run off the un-occupied setpoints or is there a way to make those two days un-occupied all day without making them occupied for one minute a day then returning to un-occupied. I just don’t want the stat to go through optimal start/stop for 3 hours previous to a one minute occupied period during weekend days.

This is a very large project involving hundreds of buildings, sold to the Gov't to conserve energy, so as much as I can conserve the better for them and me!