KMC Controls FlexStat Operation Guide - Manual (Page 30)

FlexStat 30 Operation Guide, Rev. R
Troubleshooting
Alarm Issues
Alarm, (False) Fan Fail
• Check configuration. Be sure the Fan Status
option is not selected when there is no sensor/
switch for it.
• Check that the IN2 (fan status) input pull-up
resistor switches are fully latched in the correct
positions. Any passive, dry contact should use
the 10K Ohm setting. (See the Connections and
Wiring section of the relevant FlexStat Installa-
tion Guide.)
• Check IN2 (fan status) input wiring.
• Check the connected fan status sensor/switch.
• Using BACstage or TotalControl, check that AI2
(fan status) is not configured as “Out Of Service.”
Alarm, (False) Low Limit (Freeze Stat)
• Check the Low Limit Alarm setting—see Damper
Setup on page 7 .
• Check configuration. Be sure the Economizer
option is not selected when there is no mixed air
temperature sensor.
• Check that the IN3 (mixed air temp.) input
pull-up resistor switches are fully latched in the
correct positions (see the Connections and Wir-
ing section of the relevant FlexStat Installation
Guide).
• Check IN3 (mixed air temperature) input wiring.
• Check the connected mixed air temperature sensor.
• Using BACstage or TotalControl, check that AI3
(mixed air temp.) is not configured as “Out Of
Service.”
NOTE: After a low limit alarm is generated, the
fan will not run until after the FlexStat is
restarted. (See Resetting the FlexStat on
page 26 .)
Alarm, (False) Space Temp. or Humidity
• See Alarms on page 23 .
• See Temperature Reading Is Incorrect on page 34 .
• See Temperature Setpoint Is Not Maintained on
page 35 .
• Using TotalControl, adjust the limits or time
delay.
Back-Up Issues
NOTE: Backing up the existing settings and
firmware image before or during the
upgrade process (using the Firmware
Upgrade Tool, TotalControl, or BACstage)
is recommended practice.
• See the documentation for the program used to
back-up the FlexStat.
• See service bulletin SB1111A Back-up and
Restore Issues, concerning unconfigured event
enrollment objects and checksum errors on NIC
cards.
• For HTO-1103 FlexStat Firmware Upgrade Kits
received prior to Feb. 7, 2012 that have Rev. D
(on the silver label) of the programming pod, see
service bulletin SB0212A FlexStat Programming
Pod Jumper Position.
• See also Firmware Upgrade Failures on page 37 .
Communication Issues
NOTE: For a “COMM ERROR” on the display, see
(Advanced) CO2 Sensor (and DCV) on page 11 .
Ethernet/IP Network Communication Issues
• Check communication settings—see (Advanced)
Communications (BACnet) on page 14
KMD-5576 (Data Port) Communication Issues
• For Ethernet-enabled models, a FlexStat in one of
the Ethernet or IP modes must (temporarily) be
set for MS/TP mode (and restarted) to commu-
nicate through the data port at the bottom of the
cover. See (Advanced) Communications (BACnet)
on page 14 and Resetting the FlexStat on page 26 .
• Upgrade to the latest version of BACstage (ver.
2.4.0.25 or later required).
• Check the settings for the USB port on the com-
puter (Device Manager > Ports) and the MS/TP port
in BACstage (Access > Connection Parameters).