TechnicalBuildingSystems · GeorgPessler · Oct 4, 2017 · Oct 2, 2017
diff --git a/...ingControl/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorDamperPosition.mo b/...ingControl/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorDamperPosition.mo
@@ -40,7 +40,7 @@ equation
 <p>&QUOT; <i>Control drive actuators</i> (RA-FL section 3, column 3; informative function block Figure 14) operate valves, air dampers, fans or other control devices based on input information received from operator or application functions for, e. g., the control of room temperature or air quality. The function is also used, e. g., for controlling the opening angle of windows. Control is by percent (closed = 0 &percnt;; open = 100 &percnt;). The actually achievable positioning accuracy depends on the drive units used and on the overall mechanical system. Using the actuator function for window control requires additional input information that will allow immediate stopping by means of an operator function. It must furthermore be ensured in this case that the response time of the actuator following receipt of input information for positioning is less than 200 ms so as to exclude any operating errors. The function is allocated to the room shell (fixed rooms) or the segment shell (flexible room layout). &QUOT;<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.4, p. 21 - 22]</a> </p>
 <p>The positions are per cent values between 0 and 1 as it is mentioned in the standard <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 4, p. 4 - 6]</a>.</p>
 <h4><span style=\"color: #008000\">Concept</span></h4>
-<p>The simulation contains a signal source to immitate a new value command for the control drive actuator of damper flaps. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_DP). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_DP). The V_STA_DP output should be similar to the V_SET_DP input, beside of the different data types. If V_SET_DP is greater than zero, Y should become TRUE.</p>
+<p>The simulation contains a signal source to imitate a new value command for the control drive actuator of damper flaps. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_DP). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_DP). The V_STA_DP output should be similar to the V_SET_DP input, beside of the different data types. If V_SET_DP is greater than zero, Y should become TRUE.</p>
 </html>", revisions="<html>
 <ul>
 <li>March 07, 2017&nbsp; by Georg Ferdinand Schneider &amp; Georg Ambrosius Pe&szlig;ler:<br>Implemented.</li>

diff --git a/.../BuildingControl/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorFanSpeed.mo b/.../BuildingControl/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorFanSpeed.mo
@@ -40,7 +40,7 @@ equation
 <p>&QUOT; <i>Control drive actuators</i> (RA-FL section 3, column 3; informative function block Figure 14) operate valves, air dampers, fans or other control devices based on input information received from operator or application functions for, e. g., the control of room temperature or air quality. The function is also used, e. g., for controlling the opening angle of windows. Control is by percent (closed = 0 &percnt;; open = 100 &percnt;). The actually achievable positioning accuracy depends on the drive units used and on the overall mechanical system. Using the actuator function for window control requires additional input information that will allow immediate stopping by means of an operator function. It must furthermore be ensured in this case that the response time of the actuator following receipt of input information for positioning is less than 200 ms so as to exclude any operating errors. The function is allocated to the room shell (fixed rooms) or the segment shell (flexible room layout). &QUOT;<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.4, p. 21 - 22]</a> </p>
 <p>The positions are per cent values between 0 and 1 as it is mentioned in the standard <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 4, p. 4 - 6]</a>.</p>
 <h4><span style=\"color: #008000\">Concept</span></h4>
-<p>The simulation contains a signal source to immitate a new value command for the control drive actuator of fans. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_FS). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_FS). The V_STA_FS output should be similar to the V_SET_FS input, beside of the different data types. If V_SET_FS is greater than zero, Y should become TRUE.</p>
+<p>The simulation contains a signal source to imitate a new value command for the control drive actuator of fans. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_FS). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_FS). The V_STA_FS output should be similar to the V_SET_FS input, beside of the different data types. If V_SET_FS is greater than zero, Y should become TRUE.</p>
 </html>", revisions="<html>
 <ul>
 <li>March 07, 2017&nbsp; by Georg Ferdinand Schneider &amp; Georg Ambrosius Pe&szlig;ler:<br>Implemented.</li>

diff --git a/...Control/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorLockValvePosition.mo b/...Control/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorLockValvePosition.mo
@@ -40,7 +40,7 @@ equation
 <p>&QUOT; <i>Control drive actuators</i> (RA-FL section 3, column 3; informative function block Figure 14) operate valves, air dampers, fans or other control devices based on input information received from operator or application functions for, e. g., the control of room temperature or air quality. The function is also used, e. g., for controlling the opening angle of windows. Control is by percent (closed = 0 &percnt;; open = 100 &percnt;). The actually achievable positioning accuracy depends on the drive units used and on the overall mechanical system. Using the actuator function for window control requires additional input information that will allow immediate stopping by means of an operator function. It must furthermore be ensured in this case that the response time of the actuator following receipt of input information for positioning is less than 200 ms so as to exclude any operating errors. The function is allocated to the room shell (fixed rooms) or the segment shell (flexible room layout). &QUOT;<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.4, p. 21 - 22]</a> </p>
 <p>The positions are per cent values between 0 and 1 as it is mentioned in the standard <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 4, p. 4 - 6]</a>.</p>
 <h4><span style=\"color: #008000\">Concept</span></h4>
-<p>The simulation contains a signal source to immitate a new value command for the control drive actuator of fans. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_LCK). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_LCK). The V_STA_LCK output should be similar to the V_SET_LCK input, beside of the different data types. If V_SET_LCK is greater than zero, Y should become TRUE.</p>
+<p>The simulation contains a signal source to imitate a new value command for the control drive actuator of fans. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_LCK). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_LCK). The V_STA_LCK output should be similar to the V_SET_LCK input, beside of the different data types. If V_SET_LCK is greater than zero, Y should become TRUE.</p>
 </html>", revisions="<html>
 <ul>
 <li>March 07, 2017&nbsp; by Georg Ferdinand Schneider &amp; Georg Ambrosius Pe&szlig;ler:<br>Implemented.</li>

diff --git a/...dingControl/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorValvePosition.mo b/...dingControl/VDI3813/ActuatorFunctions/Examples/TesterControlDriveActuatorValvePosition.mo
@@ -41,7 +41,7 @@ equation
 <p>&QUOT; <i>Control drive actuators</i> (RA-FL section 3, column 3; informative function block Figure 14) operate valves, air dampers, fans or other control devices based on input information received from operator or application functions for, e. g., the control of room temperature or air quality. The function is also used, e. g., for controlling the opening angle of windows. Control is by percent (closed = 0 &percnt;; open = 100 &percnt;). The actually achievable positioning accuracy depends on the drive units used and on the overall mechanical system. Using the actuator function for window control requires additional input information that will allow immediate stopping by means of an operator function. It must furthermore be ensured in this case that the response time of the actuator following receipt of input information for positioning is less than 200 ms so as to exclude any operating errors. The function is allocated to the room shell (fixed rooms) or the segment shell (flexible room layout). &QUOT;<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.4, p. 21 - 22]</a> </p>
 <p>The positions are per cent values between 0 and 1 as it is mentioned in the standard <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 4, p. 4 - 6]</a>.</p>
 <h4><span style=\"color: #008000\">Concept</span></h4>
-<p>The simulation contains a signal source to immitate a new value command for the control drive actuator of valves. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_VP). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_VP). The V_STA_VP output should be similar to the V_SET_VP input, beside of the different data types. If V_SET_VP is greater than zero, Y should become TRUE.</p>
+<p>The simulation contains a signal source to imitate a new value command for the control drive actuator of valves. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (V_SET_VP). From there the signal goes to the actuator function, which generates a motor control signal (Y) and a signal for further processing or display of the information (V_STA_VP). The V_STA_VP output should be similar to the V_SET_VP input, beside of the different data types. If V_SET_VP is greater than zero, Y should become TRUE.</p>
 </html>", revisions="<html>
 <ul>
 <li>March 07, 2017&nbsp; by Georg Ferdinand Schneider &amp; Georg Ambrosius Pe&szlig;ler:<br>Implemented.</li>

diff --git a/...ngControlLib/BuildingControl/VDI3813/ActuatorFunctions/Examples/TesterSunshadeActuator.mo b/...ngControlLib/BuildingControl/VDI3813/ActuatorFunctions/Examples/TesterSunshadeActuator.mo
@@ -40,7 +40,7 @@ equation
 <p>&QUOT;Sunshade actuators position shading devices based on input information received from, e. g., weather protection, application (e. g. anti-glare) and operator functions. Each protective element is represented as a <i>Sunshade actuator</i> function (RA-FL section 3, column 2; informative function block Figure 13). The sunshade must be controllable by percent for the position (open position = 0 &percnt;; closed position = 100 &percnt;) and additionally, in the case of adjustable slats, by degrees of slat tilt (e. g. slat angles between &ndash;80&deg; and 40&deg;), i. e. the actuator function must be capable of moving the sunshade to any mechanically reachable position. The maximum and minimum slat angles and the total runtime of the sunshade must be adjustable. The current shade position and slat tilt are available as output information for display functions. It must be ensured that the response time of the actuator following receipt of input information for positioning is less than 200 ms so as to avoid any delay perceivable to the operator. For a definite position to be assumed in case of voltage recovery, parameterisation of this position value is required. The function is allocated to the room shell (fixed rooms) or the segment shell (flexible room layout).&QUOT; <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.3, p. 20 - 21]</a></p>
 <p>In the standard it is mentioned for the sunshade signal that it should contain two values when the sunshade contains slats, whereas the sunshade position should be a per cent value and the slat position should be a angle <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 4, p. 4 - 6]</a>. Because these two values could not be bundled in an array, in this implementation every sunshade connector has two variables with different data types inside. </p>
 <h4><span style=\"color: #008000\">Concept</span></h4>
-<p>The simulation contains a signal source to immitate a new value command for the sunshade actuator. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (S_SET). From there the signal goes to the actuator function, which generates a motor control signal (M) and a signal for further processing or display of the information (S_STA). The S_STA output should be similar to the S_SET input, beside of the different data types. If S_SET is greater than zero, M should become TRUE.</p>
+<p>The simulation contains a signal source to imitate a new value command for the sunshade actuator. The signal is passed to a converter for changing the signal type from Modelica standard type to VDI 3813 semantic type (S_SET). From there the signal goes to the actuator function, which generates a motor control signal (M) and a signal for further processing or display of the information (S_STA). The S_STA output should be similar to the S_SET input, beside of the different data types. If S_SET is greater than zero, M should become TRUE.</p>
 </html>", revisions="<html>
 <ul>
 <li>March 07, 2017&nbsp; by Georg Ferdinand Schneider &amp; Georg Ambrosius Pe&szlig;ler:<br>Implemented.</li>

diff --git a/BuildingControlLib/BuildingControl/VDI3813/ActuatorFunctions/package.mo b/BuildingControlLib/BuildingControl/VDI3813/ActuatorFunctions/package.mo
@@ -8,7 +8,7 @@ package ActuatorFunctions "Actuator functions referring to VDI3813 directive"
 
 
 annotation (preferredView="info",Documentation(info="<html>
-<p>This package contains actuator functions desribed in VDI 3813 <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1]</a>: </p>
+<p>This package contains actuator functions described in VDI 3813 <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1]</a>: </p>
 <p>&QUOT;<i>Actuator functions</i> (Figure 11) convert input information originating from operator or application functions to physical quantities appropriate to their output interface. They thus represent the physical outputs of the automation system to the environment. As is the case with sensors, the informative representation takes the form of function blocks showing the input information and the corresponding physical output. Additionally, actuator functions supply output information in terms of the current manipulated value of the physical interface.&QUOT; <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.1, p. 17]</a></p>
 <p><b>Fig. 1: </b>UML class diagramm of the <i>actuator functions</i> basic design idea.<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.2.1, p. 17]</a></p>
 <table cellspacing=\"0\" cellpadding=\"2\" border=\"0\"><tr>

diff --git a/...rolLib/BuildingControl/VDI3813/ApplicationFunctions/Examples/TesterOccupancyEvaluation.mo b/...rolLib/BuildingControl/VDI3813/ApplicationFunctions/Examples/TesterOccupancyEvaluation.mo
@@ -56,7 +56,7 @@ equation
 <h4><span style=\"color:#008000\">Functional Description</span></h4>
 <p>&QUOT;The function<i> Occupancy evaluation</i> (RA-FL section 6, column 1; informative function block Figure 23) evaluates the output information received from <i>Presence detection</i> and from operator functions (<i>Signal presence</i>) in order to determine the occupancy state in a room for all further application functions. Various options of room check-in and check-out can thus be implemented.&QUOT;<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.5.2, p. 32 - 33]</a></p>
 <h4><span style=\"color:#008000\">Concept</span></h4>
-<p>With this test case ist possible to check both evaluation methods. The method is choosen via the parameter of occupancy evaluation. Beside the application function there are two boolean signal sources. One presents an operator control and the other a sensor signal. The sensor signal is pre processed by the function presence detection. The activation times are different. The operator signal comes first.</p>
+<p>With this test case ist possible to check both evaluation methods. The method is chosen via the parameter of occupancy evaluation. Beside the application function there are two boolean signal sources. One presents an operator control and the other a sensor signal. The sensor signal is pre processed by the function presence detection. The activation times are different. The operator signal comes first.</p>
 <p>In case 1 only P_AUTO should be evaluated. Because of that the first signal change does not change anything. The second change that comes from the sensor triggers the change of the evaluated output signal.</p>
 <p>In case 2 both signals should be evalueated. But P_MAN is evaluated only if P_AUTO is TRUE. Because of this the output should be activated after both signals are active.</p>
 </html>"));

diff --git a/BuildingControlLib/BuildingControl/VDI3813/ApplicationFunctions/package.mo b/BuildingControlLib/BuildingControl/VDI3813/ApplicationFunctions/package.mo
@@ -9,7 +9,7 @@ package ApplicationFunctions "Application functions referring to VDI3813 directi
 
 
 annotation (preferredView="info",Documentation(info="<html>
-<p>This package contains application functions desribed in VDI 3813 <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1]</a>:</p>
+<p>This package contains application functions described in VDI 3813 <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1]</a>:</p>
 <p>&QUOT;Application functions of room control represent the functionality to be achieved by means of automation. They can, therefore, be generally regarded as the link between sensor functions or operator functions on the one hand and actuator functions on the other hand. The behaviour of the application function can often be influenced by means of parameters. The informative representation of an application function also takes the form of a function block. In contrast to sensor, actuator or operator and display functions, it has no physical interface as it merely processes one or several pieces of input information, supplying the result in terms of one or several pieces of output information (Figure 22).&QUOT; <a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.5.1, p. 31]</a></p>
 <p><b>Fig. 1: </b>UML class diagramm of the <i>application functions</i> basic design idea.<a href=\"modelica://BuildingControlLib.UsersGuide.References\">[1, section 6.5.1, p. 31]</a></p>
 <table cellspacing=\"0\" cellpadding=\"2\" border=\"0\"><tr>