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
How to Use This Manual
Siemens Building Technologies, Inc. XI
Compatibility bar
The compatibility bar indicates if the command can be used with a
specific type of firmware.
• The symbol
indicates that the command is available in all
supported revisions of that type of firmware.
• A firmware revision number indicates the earliest firmware
revision that supports the command.
• No symbol or firmware revision number indicates the command is
not available in any revision of that type of firmware.
Figure 1 shows the command can be used in APOGEE Firmware
Revision 2.4 and later, as well as all revisions of BACnet Firmware.
The command is not available in Unitary or pre-APOGEE firmware.
Unitary pre-APOGEE APOGEE BACnet
2.4 and later
Figure 1. Symbols Used in the Compatibility Bar.
Types of Firmware
The following types of firmware are currently available:
• Unitary firmware uses a subset of PPCL commands found in
pre-APOGEE firmware.
• Pre-APOGEE Firmware (Revisions 12.5/1.5 and 12.51/1.51) are
mainly used in Controller Modules and early revisions of Open
Processors.
• APOGEE Firmware (Revision 2.x) is used in APOGEE field
panels.
• BACnet firmware uses most of the PPCL commands found in
APOGEE firmware.
The main differences between these types of firmware are how point
priority indicators and point status indicators are used. For more
information, see Chapter 2 – Control Option Comparisons.
APOGEE PPCL User’s Manual
XII Siemens Building Technologies, Inc.
Syntax
The Syntax section provides the command format. You’ll also find a
description for each parameter in the command, as well as the valid
inputs and any calculations you may need.
Use
The Use section describes what function the command performs.
Examples of program code are provided to show you how
parameters and values are defined.
Truth Tables
Truth tables help explain conditional and comparison logic. Inputs
are defined in the truth table, and then they are logically compared to
produce outputs (results). See following example to better
understand the concept of truth tables.
Example
To use a truth table, first identify the objects you want to compare. In
this example, a comparison will be made between an object selected
with you’re the your left and an object selected with your right hand.
Imagine that you have a barrel of apples and oranges. You reach
into the barrel and randomly select one piece of fruit with each hand.
Table 1 shows the possible conclusions you can reach.
Table 1. Comparing Apples to Oranges.
Items Right hand
orange
Right hand
apple
Left hand orange
Same Different
Left hand apple
Different Same
Let’s say you are holding an orange in your left hand and an apple in
your right hand. Locate the first input, Left hand orange, in the
heading along the left side of the table. Locate the second input,
Right hand apple, in the heading across the top of the table. The box
where the vertical and horizontal rows intersect is the output (result)
of the comparison. In this case, the objects in your left hand and right
hand are different.