User Manual

BACnet Scheduler

Siemens Industry, Inc.

Application Note, App 14900

140-1231

2020-02-11

BACnet Scheduler

The thermostat’s Scheduler functionality can be manually configured using the P107

SCHEDULER in the Wizard/Installer menu. This parameter simplifies the task of

entering the local schedule using the touchscreen interface for cases where a day’s

schedule may be identical to another day’s schedule. The local schedule can be

disabled by setting P107 = OFF.

● By setting P107 = 1, all days will contain the same schedule.

● By setting P107 = 2, Monday through Friday will share a schedule and Saturday

through Sunday will share another schedule.

● By setting P107 = 3, Monday through Friday will share a schedule, Saturday and

Sunday will each have a unique schedule.

● By setting P107 = 7, all seven days of the week will have individual schedules.

When editing a schedule through the local touchscreen interface, up to six events can

be defined per schedule using the Scheduler menu. When editing a schedule over the

BACnet network, the client simply needs to write to the Weekly_Schedule property of

Schedule instance 0, WeeklySchedule_1.

NOTES:

1. When the schedule is edited using the BACnet network, P107 will be set to 7.

2. The local schedule will write to MultistateValue Instance 24, SchedMode.

This object may be overridden using the network to affect a “temporary exception

mode”. Valid states include: Comfort (1), Economy (2) and Protection (3). The

corresponding setpoints for each mode are set using AnalogValue instance 32,

ComfortClgSP, AnalogValue instance 33, ComfortHtgSP, AnalogValue instance 34,

EconClgSP, AnalogValue instance 35, EconHtgSP, AnalogValue instance 39,

ProtClgSP and AnalogValue instance 40, and ProtHtgSP. Local overrides will occur

for a user-defined duration using the thermostat’s touchscreen interface. The local

override will impact the effective runtime setpoints AnalogValue 30, HeatingSp and

AnalogValue 31, CoolingSp.

NOTES:

1. If an Occupancy sensor is configured, the Present_Value of the BinaryInput is

evaluated after SchedMode’s Priority_Array arbitration, so the effective runtime

operating mode MultistateValue 26, RM OP MODE, will ultimately indicate Comfort if

the BinaryInput is active; otherwise, the Present_Value of SchedMode will take

effect.

2. The RDY2000BN does not support BACnet schedule features such as exception

schedules. Tridium Niagara users must set those unsupported parameters to Skip

Write before importing the schedule objects from the unit for editing. After editing, the

parameters can be downloaded to the RDY2000BN. If Skip Write is not marked for

those unsupported parameters, an error message displays that the writing failed.