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
Program Methodology—Point Priority Overview
Siemens Building Technologies, Inc. 1-67
Table 1-7. APOGEE to BACnet Point Priority Reference.
APOGEE Point Priority
BACnet
Priority
Slot BACnet Name
BN01 Manual Life Safety
BN02 Automatic Life Safety
BN03 Available
BN04 Available
BN05 Critical Equipment Control
BN06 Minimum On/Off
BN07 Available
OPER (Operator) BN08 Manual Operator
BN09 Available
SMOK (Smoke) BN10 Available
BN11 Available
EMER (Emergency) BN12 Available
BN13 Available
PDL (Peak Demand Limiting) BN14 Available
BN15 Available
Sched, PPCL, TEC tool* BN16 Available
Initial value of the point; TEC
Application
NONE Relinquish Default
* The TEC Tool can command Priority slot 16 only if it is not being commanded by PPCL.
APOGEE PPCL User’s Manual
1-68 Siemens Building Technologies, Inc.
At (@) Priority Status Indicators
At (@) priority indicators are used to monitor the priority status on
points defined in a device. They can also be used to test if a point is
at a specific priority or to command a point to a specific priority.
• The priority level defined in a statement occupies one of the
parameters.
• Statements such as ON, OFF, RELEAS, and SET allow you to
define a total of 16 parameters in one statement.
• When using an @ priority indicator within PPCL statements, the
@ priority indicator occupies the first parameter location. This
decreases the total number of points you can define in a
statement to 15.
• When the @ priority is not used, the default priority is EMER.
Testing Point Priorities
Programs sometimes fail because a command outside the operation
being performed interferes with a point inside the operation. Testing
the priority of a point helps prevent this from happening.
If numerous tasks are being performed in the program, testing point
priority levels is one method of preventing those tasks from
interfering with each other.
Example
200 IF (SFAN.EQ.@EMER) THEN ON(@EMER,RFAN)
This statement tests SFAN to determine if it's at EMER priority
before turning ON RFAN. If SFAN is at EMER priority, RFAN will be
command ON.
Commanding Points to a Specific Priority
Points can be commanded to a specific priority, as well as a specific
status, by placing the at (@) symbol before the priority syntax (see
Table 1-8).