Unitary | Pre-APOGEE | APOGEE | BACnet | PXC.A |
|---|---|---|---|---|
| ● | ● | ● | ● |
Syntax
PDLMTR(area,hist,calc,window,plot,warning,mt1, def1,...,mt5,def5)
area | Meter area. - In order for the program to operate correctly, the same numeric value must be used for the meter area parameter in the PDLDPG, PDLMTR, and PDLSET statements. - This parameter can be an integer (1 to 32,767), a point name, or a local variable. |
Hist | Historical forecast weighting factor (in percent) for the sliding window predictions. - This parameter can be a decimal or integer. - The weighting factor should be less than 50% to anticipate demand. - The recommended value is 30%. |
calc | Interval (in minutes) for how often demand predictions are calculated. - This parameter is usually a decimal or integer, but can be a point name or a local variable. - The minimum time allowed is one minute. |
window | Predictions on the width of the sliding window interval (in minutes). - This parameter is usually a decimal or integer, but can be a point name or a local variable. - Up to 30 samples can be stored per window. |
plot | Maximum value for the Time versus Demand plot section of the PDL Activity Report. - This parameter can be a decimal, integer, point name, or a local variable. - This value should be greater than the highest setpoint used in PDLSET. |
warning | Determines if warning messages are issued as predicted demand nears or exceeds the setpoint. - Valid values are 0 and 1. 0 = Warning messages disabled 1 = Warning messages enabled |
mt1 through mt5 | Logical point names for demand consumption meters. - This parameter can be an LPACI or analog point. - When an LPACI points is used, the engineering units are kWH. - When an analog point is used, the engineering units are kW. |
def1 through def5 | The default values are used instead of the meter values (mt1 through mt5) when communication is lost or the meters cannot be read. - This parameter can be a decimal, integer, point name, or local variable. - For historical (latest, best) reading, enter -1 (default value), or enter a constant or a fixed default value. - Default values are expressed in kilowatts (demand) for both analog and pulse inputs. |
Use
The PDLMTR command is responsible for the following actions:
- Defining meters by point name.
- Monitoring meters.
- Making demand predictions that are used by the PDLDPG command.
- Updating report information pertaining to demand and consumption.
- Deciding when warning messages should be issued.
- Initializing a meter area.
- Defining default meter values.
Example
200 C
202 C PDLMTR COMMAND INFORMATION:
204 C
206 C - HISTORICAL WEIGHTING FACTOR - 30%
208 C - CALCULATION INTERVAL - 1 MINUTE
210 C - PREDICTION WINDOW - 15 MINUTES
212 C - THE TIME VERSUS DEMAND SECTION OF
214 C THE ACTIVITY REPORT PLOT HAS A
216 C FULL SCALE OF 500 KILOWATTS.
218 C - WARNING MESSAGES ARE ENABLED TO
220 C BE SENT TO ALARM DEVICES.
222 C - THE DEFAULT VALUES OF THE TWO
224 C METER POINTS (METER1 AND
226 C METER2) ARE 100 KILOWATTS AND
228 C 50 KILOWATTS RESPECTIVELY.
230 C
250 PDLMTR(1,30,1,15,500,1,METER1,100, METER2,50)
Notes
- Only one PDLMTR command can be defined per meter area.
- For APOGEE automation stations, one PDLMTR command can be defined per program.
- With pre-APOGEE firmware, one meter area can be defined in an automation station.
- If a LPACI point is used in a PDLMTR statement, then PDL should be restarted for that meter area after the LPACI is reset.