User Guide
Table Of Contents
- Table of Contents
- How to Use This Manual
- Chapter 1–Program Methodology
- Overview
- Introduction to PPCL
- PPCL Rules
- PPCL Program Design Guidelines
- Relational Operators
- Logical Operators
- Arithmetic Operators
- Arithmetic Functions
- Special Functions
- Order of Precedence
- Resident Points
- Local Variables
- Point Priority Overview
- At (@) Priority Status Indicators
- Point Status Indicators
- Converting a Sequence of Operation intoProgram Code
- Chapter 2–Control OptionComparisons
- Chapter 3–Command Syntax
- Overview
- ACT (Activate lines)
- ADAPTM (Adaptive control, multiple)
- ADAPTS (Adaptive control, single)
- ALARM (Alarm state)
- AUTO (Auto status)
- DAY (Day mode)
- DBSWIT (Dead band switch)
- DC (Duty cycle)
- DCR (Duty cycle routine)
- DEACT (Deactivate lines)
- DEFINE (Define abbreviation)
- DISABL (Disable lines)
- DISALM (Disable alarm)
- DISCOV (Disable COV)
- DPHONE (Disable phone)
- EMAUTO (Emergency, Auto status)
- EMFAST (Emergency, Fast status)
- EMOFF (Emergency, Off status)
- EMON (Emergency, On status)
- EMSET (Emergency, set value)
- EMSLOW (Emergency, Slow status)
- ENABLE (Enable lines)
- ENALM (Enable alarm)
- ENCOV (Enable COV)
- EPHONE (Enable phone)
- FAST (Fast status)
- GOSUB (Go to subroutine)
- GOTO (Go to line)
- HLIMIT (High limit)
- HOLIDA (Holiday)
- IF/THEN and IF/THEN/ELSE (Conditional control)
- INITTO (Initialize totalized value)
- LLIMIT (Low limit)
- LOCAL (Local variable)
- LOOP (Loop control)
- MAX (Maximum value)
- MIN (Minimum value)
- NIGHT (Night mode)
- NORMAL (Normal operating mode)
- OFF (Off status)
- OIP (Operator interface program)
- ON (On status)
- ONPWRT (On after power return)
- PDL (Peak demand limiting)
- PDLDAT (PDL, define load attributes)
- PDLDPG (PDL, digital point group)
- PDLMTR (PDL, meter monitor)
- PDLSET (PDL, setpoints)
- RELEAS (Release)
- RETURN (Return/end subroutine)
- SAMPLE (Sample a statement)
- SET (Set point value)
- SLOW (Slow status)
- SSTO (Start/stop time optimization)
- SSTOCO (SSTO coefficients)
- STATE (State text command)
- TABLE (Table of coordinates)
- TIMAVG (Average over time)
- TOD (Time of day, digital points)
- TODMOD (TOD modes)
- TODSET (Time of day, analog points)
- WAIT (Wait time)
- Overview
- Glossary
- Appendix A—PPCL Reserved WordList
- Index
Control Option Comparisons—Time-of-Day (TOD)
Siemens Building Technologies, Inc. 2-23
NOTE: Schedules can also be created using the Time-of-Day
(TOD) calendar that offers a menu-driven interface. For
complete information on defining and maintaining daily
operating schedules using the TOD calendar, see the
APOGEE Field Panel User’s Manual (125-3000) or the
Field Panel User’s Manual (125-1895) for pre-APOGEE
field panels.
Example 1: Holidays defined in PPCL, but not in the TOD calendar
The following example illustrates the results when defining holidays
using the PPCL HOLIDA command.
50 HOLIDA(5,3,9,8)
The following TOD commands are defined in the TOD database:
Monday – Sunday
07:00:00 OFF LITE1
18:00:00 ON FAN1
18:00:00 ON LITE1
19:00:00 OFF FAN1
Holiday
10:30:00 OFF LITE1
17:00:00 ON LITE1
Based on this schedule, the following will occur:
• Every day except May 3 and September 8, LITE1 will go ON at
18:00 and turn OFF at 07:00, and FAN1 will go ON at 18:00 and
turn OFF at 19:00.
• On May 3 and September 8, LITE1 will go ON at 17:00 and turn
OFF at 10:30, while FAN1 will not be commanded.
APOGEE PPCL User’s Manual
2-24 Siemens Building Technologies, Inc.
Example 2: Holidays defined in TOD calendar, but not in PPCL
The following example illustrates the results when defining holidays
using the TOD Calendar.
The TOD calendar has the following entries:
03-May-1994 Holiday
08-Sep-1994 Holiday
The program contains the following PPCL TOD commands:
100 TODMOD(1,1,1,1,1,1,1)
110 TOD(1,1,18:00,07:00,LITE1)
120 TOD(1,1,18:00,19:00,FAN1)
130 TOD(16,1,17:00,10:30,LITE1)
Based on this schedule, the following will occur:
• Every day except May 3 or September 8, LITE1 will go ON at
18:00 and turn OFF at 07:00, and FAN1 will go ON at 18:00 and
turn OFF at 19:00.
• On May 3 and September 8, LITE1 will go ON at 17:00 and turn
OFF at 10:30, while FAN1 will not be commanded.
Example 3: Holidays defined in both PPCL HOLIDA and the TOD
calendar
The following example illustrates the results when defining holidays
using both the PPCL HOLIDA statement and the TOD calendar.
NOTE: Problems can occur if different holiday schedules are
defined in the HOLIDA statement and in the TOD
calendar, and then both methods are used at the same
time. The equipment commanded by the PPCL TOD
command will not only execute the holidays defined in the
HOLIDA statement, but also those defined in the TOD
calendar.
If you choose to define a holiday using the PPCL
HOLIDA statement and the TOD calendar, make sure
that the holiday is defined the same in both places.