![KMC Controls FlexStat BAC-12 Series Скачать руководство пользователя страница 32](http://html.mh-extra.com/html/kmc-controls/flexstat-bac-12-series/flexstat-bac-12-series_operation-manual_1979552032.webp)
FlexStat
32
Operation Guide, Rev. L
• Select Occupied mode from the Home Menu—
see
H/C, Fan, Occupancy, and Override on page 4
.
• Override the fan to On from the Home Menu—
see
H/C, Fan, Occupancy, and Override on page 4
.
• Check that the appropriate application is select-
ed—see
(Advanced) Application and Additional
Setup on page 7
.
• Check that room temperature is being sensed
correctly—see
Temperature Reading Is Incorrect
on page 31
.
• If space temperature is overshooting the set-
point, try changing the integral value to either
a
slightly higher value or to 0
. (The optimal
integral value is dependent on the characteristics
of the particular space and HVAC system.) See
(Advanced) PID Loop Configuration on page 17
.
Time and/or Date Are Incorrect
NOTE: When a FlexStat is powered up after
losing the RTC (Real Time Clock) time, it
will revert to the default time and date of
January 1, 2000, 12:00:00 AM.
• Set time and date in the menu. See
(Advanced)
Date/Time on page 15
.
• Using BACstage or TotalControl, send a time
synchronization command.
NOTE: An issue can occur if a FlexStat has been
unpowered long enough for it to lose
its RTC timekeeping during the period
DST (Daylight Saving Time) is in effect
(currently the second Sunday of March
through the first Sunday of November)
and
a time synchronization command is
sent from BACstage or TotalControl to
the FlexStat. The time will be restored to
the correct time and date. However, the
FlexStat will assume that this time is non-
DST. Within about one minute after the
initial time synchronization (during DST
months), the device time will reset to DST
mode, and the device time will move one
hour ahead. This will affect the displayed
time on the LCD display as well as any
schedules. This issue will not affect newly
powered FlexStats during non-DST periods
(e.g., most of November through February).
If the time has erroneously advanced one
hour after an initial time synch command,
the easiest solution is to simply send a
second time synch command. This will
correct the device time. Alternately, the
hour can be changed in the FlexStat’s menu.