blockTimeProgramEnergyMode

Model that contains time schedules for the energy mode of the controlled area

Extends from BuildingControlLib.BuildingControl.VDI3813.Interfaces.Partial.PartialFunction (Superclass for all function blocks to provide graphics and enforce implementation of functionality).

Information

Overview

Block that implements function of "Time program" from VDI 3813 [1, section 6.5.4, p. 35 - 37].

Functional Description

"The function Time program (RA-FL section 6, column 3; informative function block Figure 25) allows time-controlled generation of output information, thus influencing or controlling application functions or actuator functions.The time program contains the time and date functions as well as calendar entries including exception days (e. g. holidays). The respective switching operations are generated via a default week schedule and exception day schedules with switching point/value pairs. Such a time program can be implemented and maintained either directly via an interaction interface, or it is transferred by a management communication function to an operating device or external system."[1, section 6.5.4, p. 35 - 37]

The block checks execptionCalendar if there is an execption case. If true then the time/value pair from the exception schedule is chosen. If false then time/value pair from the normal weekly schedule is chosen. Note time/value pairs need to be entered following the convention {{days,hours,minutes,seconds,value}}.

Fig. 1: "Informative representation of the application function Time program", [1, section 6.5.4, Figure 25, p. 36]

docVDI3813_TimeProgram.PNG

Parameters

TypeNameDefaultDescription
Real[:]offset{0.0}Offset of output signal
Real[5]startTimeWSCH{0, 0, 0, 0, 3.0}Array with start time and value format: {{days,hours,minutes,seconds,startValue}}
Real[:,5]PAR_WSCH{functionality.weeklySchedule.startTime, {0, 7, 30, 0, 3.0}, {0, 7, 30, 0, 2.0}, {0, 8, 0, 0, 2.0}, {0, 8, 0, 0, 1.0}, {0, 18, 0, 0, 1.0}, {0, 18, 0, 0, 3.0}, {1, 7, 30, 0, 3.0}, {1, 7, 30, 0, 2.0}, {1, 8, 0, 0, 2.0}, {1, 8, 0, 0, 1.0}, {1, 18, 0, 0, 1.0}, {1, 18, 0, 0, 3.0}, {2, 7, 30, 0, 3.0}, {2, 7, 30, 0, 2.0}, {2, 8, 0, 0, 2.0}, {2, 8, 0, 0, 1.0}, {2, 18, 0, 0, 1.0}, {2, 18, 0, 0, 3.0}, {3, 7, 30, 0, 3.0}, {3, 7, 30, 0, 2.0}, {3, 8, 0, 0, 2.0}, {3, 8, 0, 0, 1.0}, {3, 18, 0, 0, 1.0}, {3, 18, 0, 0, 3.0}, {4, 7, 30, 0, 3.0}, {4, 7, 30, 0, 2.0}, {4, 8, 0, 0, 2.0}, {4, 8, 0, 0, 1.0}, {4, 18, 0, 0, 1.0}, {4, 18, 0, 0, 3.0}, functionality.weeklySchedule.endValue}Time/value pairs of weekly schedule in regular operation. Format: {{days,hours,minutes,seconds,value}}. Need to leave endValue parameter as last item. Discontinuities allowed by introducing values in table twice
Real[5]startTimeESCH{0, 0, 0, 0, 3.0}Array with start time and value format: {{days,hours,minutes,seconds,startValue}}
Real[:,5]PAR_ESCH{functionality.exceptionSchedule.startTime, {0, 9, 30, 0, 3.0}, {0, 9, 30, 0, 2.0}, {0, 10, 0, 0, 2.0}, {0, 10, 0, 0, 1.0}, {0, 13, 0, 0, 1.0}, {0, 13, 0, 0, 3.0}, functionality.exceptionSchedule.endValue}Time/value pairs of exception schedule. Format: {{days,hours,minutes,seconds,value}}. Need to leave endValue parameter as last item. Discontinuities allowed by introducing values in table twice
Real[5]startTimeCAL{0, 0, 0, 0, -1.0}Array with start time and value format: {{days,hours,minutes,seconds,startValue}}
Real[:,5]PAR_CAL{functionality.exceptionCalendar.startTime, {5, 0, 0, 0, -1.0}, {5, 0, 0, 0, 1.0}, {6, 0, 0, 0, 1.0}, {6, 0, 0, 0, -1.0}, functionality.exceptionCalendar.endValue}Time/value pairs of of yearly exception calendar. Format: {{days,hours,minutes,seconds,value}}. Need to leave endValue parameter as last item. Discontinuities allowed by introducing values in table twice

Connectors

TypeNameDefaultDescription
BuildingControlLib.BuildingControl.VDI3813.Interfaces.RealInputD_ACTCurrent date and time.
BuildingControlLib.BuildingControl.VDI3813.Interfaces.EnergyModeOutputM_BMSValid energy mode for the current time (defined in schedules by operator).

Components

TypeNameDefaultDescription
PartialFunctionalityfunctionality (from PartialFunction)

Revisions

  • March 07, 2017  by Georg Ferdinand Schneider & Georg Ambrosius Peßler:
    Implemented.