Excel 10 fcu controller lns plug-ins user guide – Honeywell EXCEL 10 W7752D User Manual

Page 51

Advertising
background image

EXCEL 10 FCU CONTROLLER LNS PLUG-INS USER GUIDE

49 EN2B-0285GE51

R0909

Table C3. Input Variables for Excel 10 FCU Controllers

NV name

field name

engineering units:

English (metric) or states plus

range

digital

state

or

value

default comments

nviReheatRelay value

SNVT_switch
0 to 100%

0 (at application restart)

This input variable is used to control the reheat relay via the
network. This permits use of the relay as an auxiliary output in
applications where reheat is not required as well master/slave
applications where the reheat output is controlled by another
controller acting as master.

nviReheatRelay state

SNVT_switch
OFF
ON
NUL


0
1
255

OFF (at application restart) See above.



nviRequest object_id

SNVT_obj_request
UWORD
0=Node Object
1=Fan Coil Object

This input variable belongs to the Node Object and provides the
mechanism to request a particular mode for a particular object
within a node.

nviRequest object_request object_request_t

Enum from Echelon defined
RQ_NORMAL
RQ_UPDATE_STATUS
RQ_UPDATE_ALARM
RQ_REPORT_MASK



0
2
4
5

See above. Commanding any modes other the ones listed will
result in an “invalid_request” when reading nvoStatus.



nviSensorOcc

SNVT_occupancy
OC_OCCUPIED
OC_UNOCCUPIED
OC_BYPASS
OC_NUL


0
1
2
255

OC_NUL
(if bound but fails to be
received or at application
restart)

This input variable allows an occupancy sensor of another Excel
10 controller to be used to indicate the sensed occupancy state of
the space. OC_NUL means no input is available because it is not
bound, bound but not received periodically, or not configured by
nciFcuConfig.DI1_config. More than one occupancy sensor may
be bound to nviSensorOcc. If any one sensor detects occupancy,
the controller considers the space occupied.

nviSetPoint

SNVT_temp_p
50 to 95°F (10 to 35°C)
327.67°C = INVALID




INVALID

(at application restart)

This input variable is used for binding third party nodes to
authorize them for setpoint modifications. When this has been
bound and a valid update is received, the local configured set-
points will no longer be directly used to determine the current
occupancy setpoint. For OCCUPIED and STANDBY modes, this
is used with the appropriate ZEB (derived from the configured
setpoints), for UNOCCUPIED mode the setpoint does not depend
upon this input, but upon nciTempSetPts.unoccupied_cool/_heat
only. nviSetpoint is stored in RAM and gets lost after power
failure. In this case, the setpoints of nciTempSetPts will be used
until a valid nviSetpoint is received.

Advertising