Control following a connection failure depends on where the failure occurs, and which input device has been used.
Between Unit Controller and LonTalk Module
Lennox
1−
During the 5 minutes following a failure, the unit controller cycles
Zone
on last setpoint.
Sensor
2−
Unit controller resets. No heating or cooling during 2 minutes
(ECTO 5.25) following reset.
3−
Unit controller cycles based on ECTO backup setpoints.
4−
Occupancy is determined by hardware input at TB1 ( for M1), or
Prodigy setup (for M2).
LonTalk
1−
During 5 minutes following failure, the unit controller continues cur-
Zone
rent operation: heat, cool, or off.
Sensor
2−
Unit controller resets. No heating or cooling during 5 minutes fol-
lowing reset.
3−
Unit controller uses ECTO backup setpoints.
4−
Unit controller attempts to use Lennox zone sensor as backup. If
this fails, Unit controller uses return air sensor backup.
5−
Occupancy is determined by hardware input at TB1 ( for M1), or
Prodigy setup (for M2).
Alarm Codes
Connection Failure
Network Variables −
See the Unit Controller user guide for a list of alarm codes.
LonWorks Network
1−
2 − Last occupancy input is used.
1−
2−
3−
4 − Last occupancy input is used.
See BACnet Module Service Literature.
Page 8
Unit controller cycles on last setpoint.
During 5 minutes following failure, Unit con-
troller continues current operation: heat,
cool, or off.
Unit controller uses ECTO backup set-
points.
Unit controller attempts to use Lennox zone
sensor as backup. If this fails, Unit controller
uses return−air−sensor backup.