Issue
How and when does a Xenta 102-AX resynchronize its damper floating output control?
Environment
Xenta 102-AX v2.17 and up
Cause
Documented reasons for a damper and floating output resynchronization on a Xenta 102-AX controller
Resolution
There are 5 events that cause a Xenta 102-AX to resynchronize its floating control logic for the damper and other outputs. These reasons are:
- At controller reset. (This could be a power cycle or reset command via TAC Vista/LNS)
- If the damper motor position command has been inside its "active zone" (5% - 95%) for an accumulated time of 24 hours, AND the motor position then goes to 0% or 100% (Note that the outputs and damper are timed and reset independent of each other)
- Indication of error in flow detection. This is if nvoFlowControlPt = 0 but nvoMotorPositn > 0 for 1 minute or more
-
If nviEmergCmd is set to any of the following modes:
- EMERG_PRESSURIZE
- EMERG_DEPRESSURIZE
- EMERG_PURGE
- EMERG_SHUTDOWN
- A controller reset via Lonmaker or NL220 will also cause a resynchronization of the damper and the other floating outputs. This is necessary if the stroke time (throttling range) or stroke direction is changed in the middle of a damper operation