Building Automation Knowledge Base

Issue Auxiliary I/O or inputs and outputs, allow a system to be expanded to include additional devices outside of standard door hardware such as sirens, panics buttons, or warning lights. Product Line Access Expert Environment Access Expert v3 Cause Lack of documentation on Auxiliary I/O Resolution Input Devices Inputs are also added to  Downstream (interfaces). Inputs are typically added automatically when used to support door contacts and REX but can be implemented to connect motion detectors, glass break detectors, and even panic buttons. Inputs in this section would be separate from those associated with the reader-controlled doors. Inputs can have cameras associated with them to associate alarm points.   Though you can assign multiple cameras to a single point the Assign Camera section will only present one camera at a time. The Assign View allows multiple cameras to be brought together in a single view. To add an Input: Open a downstream interface configuration Select the “Add Input” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. **Note: Take special care when setting the address as the value does not match the number labeled on the physical hardware. The first address is always 0 (not 1). Input Attributes: Display Name: This is the name of the input that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Behavior: The Normally Open or Normally Closed setting of the input. This is also where any custom EOL Tables are applied. Debounce: The amount of time required before registering the signal. Bouncing is the tendency of any two metal contacts in an electronic device to generate multiple signals as the contacts close or open. “Debouncing” is any kind of hardware or software that ensures that only a single signal will be acted upon for a single opening or closing of a contact. Latching Mode: This sets the type of latching used by the input. Normal Mode (No Entry or Exit Delay): This will cause the input to report an alarm immediately upon activation and deactivation. Non-latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires the alarm will be reported. If the input is not active when the Entry Delay expires, no alarm will be reported. Latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires AND the input has not been masked, the alarm will be reported. Entry Delay: The time before the input alarm will report. Exit Delay: This function is useful to secure a door when an individual is leaving.  When the ‘exit delay’ mode is set, the following shall occur.  The alarm will not be reported from an input activation until the exit delay expires.  If the input is still active upon exit delay expiry, the alarm will be reported.  If the input is not active upon exit delay expiry, the alarm will not be reported. Hold Time: This can be thought of as a Motion Detector Delay. This is the number of seconds that the change of state must be held before the input will be changed to a deactivated state. Attached: Sets the Attached status of the input. Input Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Input Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Outputs Outputs are also added downstream. Outputs are not only used to support strikes but can be implemented to connect sirens, strobes, and other signaling type devices. Outputs in this section would be separate from those associated with the reader-controlled doors. Outputs can also have cameras associated with them to associate alarm points.   To Add an Output: Open a downstream interface configuration Select the “Add Output” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. Output Attributes: Display Name: This is the name of the output that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Activation Time: This is the amount of time the output will be active when pulsed. Mode: This sets the output to be in a normal operating mode (normally un-energized) or inverted operating mode. Schedule: This sets the time during which an output will activate. Assign Camera/View: The associated cameras or views for the output. These will display in the Live Monitor/Event History for events associated with the output. Output Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Output Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Scheduling Outputs Outputs can be scheduled by clicking the schedule drop-down menu and selecting the desired schedule. The output will then Activate when the schedule activates, and deactivate when the schedule deactivates.

Issue The documentation shows how to set the CLOCK but the clock fails to work. The controller always displays the Alarm "SetClock" and the time at the default value " Monday" 12:00 AM Product Line EcoStruxure Building Expert, Field Devices Environment SE7000 Room Controller SE8000 Room Controller Cause The Real Time Clock in the SE7000 uses the 50/60hz AC frequency to operate, if the unit is powered from a DC power source the Real Time Clock will not function and the clock time will always display Monday 12:00. Resolution Power the SE7000 controller from an AC power source if the RTC is required. Note: SE8000 uses a different RTC chip and can be powered from either AC or DC and the time operates correctly.

Issue What virtual environments are supported for use with Security Expert? Product Line Security Expert Environment Security Expert Microsoft SQL Server Cause Which specific virtualization software has been qualified to work with Security Expert? Resolution No specific virtualization software has been qualified with Security Expert. The Security Expert Compatibility Matrix describes support for Virtual Environments as the following.   The Security Expert server is supported on Virtual Server Environments. However, Schneider Electric reserves the right to request customer replication of any errors in a non-virtual environment. When installing under virtual server environments special care must be taken to ensure that the system requirements are met by the virtualized hardware. The VM must be carefully reviewed with regard to resource and performance before completing any installation.

Issue Synchronizing time across many networks and multiple time zones Product Line Andover Continuum Environment Continuum Cyberstation Cause Guidelines for implementing an efficient yet compact Cyberstation PE program to synchronize time on large installations consisting of many Continuum networks across multiple time zones. Resolution The solution presented here requires that in each network the time master (controller with the lowest ACCNetId) is identified by setting its description to PTM. (Primary Time Master) It is also recommended that the controller with the second-lowest ID is identified as the STM. Obviously, the program itself could identify the time master for each Network but doing this outside of the program makes for a simpler, more robust implementation. To implement the solution, simply create a program in one of the Continuum Cyberstations and insert the code provided below. Configured the HOUR System Variable in the Cyberstation to trigger the program. The program, as written, will sync the time once a day at 3:00 AM There is a local variable (Verbose) that controls the level of information the program prints to the message window, recommends this be set to print everything when the implementation is first put in place to ensure it is operating as expected, then print only errors afterward. 'This program synchronizes time between Cyberstation and controllers across Networks and time zones. 'Program is triggered by the HOUR system variable 'SETUP 'In each network, the controller with the lowest ACCNetID must be identified as the Primary Time Master ' by setting its description to PTM 'Optionally, the controller with the second-lowest ACCNetID can be identified as the Secondary Time Master ' by setting its description to STM 'v1.0 SE PSS 1010 1011 1110 - FOR PROOF OF CONCEPT PURPOSE ONLY '-------------------------------------------------------------------------------------------------- Object theCX Object theNetwork Object theWS 'The Workstation where the program is running Number WS_UTCOffset 'The UTC Offset of theWS Number syncDone Number Verbose 'Prints to theWS message window. Set to 1 to print errors only, set to 2 to print synchronization information. Line INIT If Hour <> 3 then Stop 'sync time once a day at 3am theWS = CurWorkstation() 'get the name of the Cyberstation where the program is running WS_UTCOffset = getname("root\" ; theWS Alias ; " UTCOffset") 'and theWS UTC Offset Verbose = 0 'default to silent operation Goto SynchronizeTime Line SynchronizeTime If OpenList("Network", theNetwork) is Success then While GetObject(theNetwork) is Success 'for each Network... If Verbose = 2 then Print "Syncronizing time on NETWORK: " ; theNetwork Alias If OpenList("InfinityController", theCX, theNetwork) is Success then While GetObject(theCX) is Success 'for each CX controller in the network... syncDone = False 'reset the sync done flag 'Print theCX alias REMOVE COMMENT TO PRINT CX NAME, HELPFUL WHEN DEBUGGING THIS PROGRAM If theCX Description = "PTM" and theCX CommStatus = OnLine then 'is this controller the time master and if so, is it ONLINE? If Verbose = 2 then Print "Time syncronized on NETWORK: " ; theNetwork Alias ; ", CONTROLLER: " ; theCX Alias ; " (Primary Time Master)" getname(theNetwork Alias ; "\" ; theCX Alias ; "\Date") = Date + ((theNetwork UTCOffset - Cyber221 UTCOffset) * 60) 'synchronize its time syncDone = True 'we're done with this network... Break '...so break out of the inner while loop Endif If theCX Description = "STM" and theCX CommStatus = OffLine then 'look for a secondary time master if primary not online If Verbose = 2 then Print "Time syncronized on NETWORK: " ; theNetwork Alias ; ", CONTROLLER: " ; theCX Alias ; " Secondary Time Master" getname(theNetwork Alias ; "\" ; theCX Alias ; "\Date") = Date + ((theNetwork UTCOffset - Cyber221 UTCOffset) * 60) 'synchronize its time syncDone = True 'we're done with this network... Break '...so break out of the inner while loop Endif Endwhile CloseList(theCX) If syncDone = False and Verbose > 0 then Print "No time master found online for NETWORK: " ; theNetwork Alias ; "," ; Date Else If Verbose > 0 then Print "ERROR, can't open Controller list " ; Date Endif Endwhile CloseList(theNetwork) Else If Verbose > 0 then Print "ERROR, can't open Network list " ; Date Endif Stop Line E If Verbose > 0 then Print "Program hit ERROR line, " ; Date Stop

Issue After upgrading SP-C to firmware 2.0.8.921, could not locate the OS version anymore Product Line Security Expert Environment SP-C Firmware 2.0.8.921 and above Cause The web interface has significantly changed in these later builds; as such, it was not intuitive where this information had been moved too.  Resolution To see the OS version of the SP-C. Navigate to the Application Software page Under Controller Software heading Click on Current Version Four additional items will now appear below the displayed current version. One is the OS version.

Issue Supplemental Documentation on the Menta/Function Block PID simple blocks Product Line TAC Vista, EcoStruxure Building Operation Environment Menta/Function Block editor Cause The document below is intended to clarify some of the more subtle aspects of the Menta/Function Block PID blocks and when/how to use them. Resolution A Brief Overview of PID Control Proportional-integral-derivative (PID) control is a generic feedback control loop algorithm. A PID controller calculates the error from the desired setpoint of a measured variable. It then adjusts the control output accordingly to try and minimize this error. Parameters used in the calculation must be tuned according to the system they are employed to control. The three prominent parameters are the proportional, integral, and derivative values. The proportional value affects the change in the output signal based upon the current error from setpoint. The integral value works based on the sum of the most recent errors. The derivative value reacts based on the rate at which the error has been changing. The weighted sum of these three actions is used to adjust the control output. The most typical application used in HVAC controls is actually a proportional-integral control with no derivative influence (PI). Derivative action is very sensitive to measurement noise, and generally considered too complex for the relatively limited benefit to slower, more easily controlled loops.   Three Types of PID Blocks in Menta Menta has three different simple blocks for PID control. They are: PIDI, PIDP, and PIDA (links to Web Help). PIDI PIDI is a PID controller with an incremental output. It is designed to be used together with two digital pulse output (DOPU) blocks in control loops with increase/decrease actuators. Input parameters to the PIDI will influence the operation of the controlled output in the same way as the analog PID blocks. The output, however, will not show a percentage. The end user will only be able to force an “open” or “close” command to the actuator – not set it to a desired percentage. Examples of how to use PIDI are explored later in the document. PIDP PIDP is the newer of the two analog output PID controllers in Menta. Because of this, it can only be used in Xenta controllers with a system program version of 3.6 or later. In Menta, under Options > Device Specification, it may be necessary to set the file to system version 3.6 or later during the programming phase. PIDP differs from PIDA in 4 distinct ways: PIDP will remain in saturation for a longer time than PIDA. The integral portion of the calculation keeps a running sum of previous error adjustments. Because of this, it can “wind up” a stored integral response. There is an anti-wind up mechanism to combat the effect, but PIDA has no wind up at all. In PIDP, a change in the setpoint value will not cause a step change when using PI or PID control. The measured error is not from the setpoint input, but rather from the last sampled measured value. The PID block samples a measured variable any time it is inside the deadzone. The allows for the calculation’s setpoint to equal the edge of the deadzone and have a less dramatic response to exiting the deadzone. The other time it will sample a new measured variable is any time a control coefficient is changed. This is an important distinction to be aware of during tuning operations. It may be useful to force the measured variable equal to setpoint after altering tuning parameters. The tracking of the tracking signal is not instantaneous in PIDP, as opposed to PIDA. Looping back the output to the TSg tracking signal feedback input will not cause the PID to stay synched with an overridden output. Additional logic is needed to switch the Mode to 0 for one program cycle in order to lock in the feedback signal any time it does not equal the output signal. The D-part is not as sensitive to measurement noise in PIDP as in PIDA. PIDA PIDA uses the following equation to calculate its output: where e is the control error, y is the measured value (MV), G is the controller Gain, Ti is the integral time, Td is the derivative time and h is the Control Interval (ControlInt), i.e. the time between two successive updates of the controller output signal. While analyzing and understanding this formula is beneficial to fully understanding the PID simple block, do not get too mired in the details. This document will help to demystify input parameters to make the PID work in a number of situations. For the purpose of this document, a PIDA will be assumed for all applications.   Inputs to the PIDA Block MV Measured value is the process variable for the PID controller. It is an input value of type Real. Examples of this would be a room temperature, a return air CO2 level, or a hot water differential pressure. SP Setpoint is the desired value of the measured value. It is an input value of type Real. It could be a static value (Operator “Real const”), adjustable from the front end (Simple Block “PVR”), a stepping value, or a modulating value. If the setpoint is likely to change often, it is recommended to use the PIDA block as opposed to PIDP. Mod The mode input to the PID block will control its action and enable or disable the control output. It is an input value of type Integer. There are four possible modes: Mode = 0 Web Help lists this mode as, “Off, controller stopped.” A more accurate description would be, “The value present at the TSg input will pass through to the output.” If the looped back output value is not changing, then the PID output will freeze. Mode = 1 Normal control. A new output value will be calculated on every Control Interval. Mode = 2 Controller output forced to UMax. This could be used on a hot water valve when freeze protection is enabled. Mode = 3 Controller output forced to UMin. This typically represents the “off” position of a PID. G Gain is the proportional parameter of the PID control. It is an input value of type Real. It is represented by the following equation: To arrive at an appropriate default value for Gain, three parameters must be considered: UMax, UMin, and proportional band. In typical applications, UMin and UMax will be 0% and 100%, respectively. This is because most valve or damper actuators are going to control between 0-100%. For the following examples, this will be assumed, but do not discount the effect it will have on default Gain parameters if these values change (such as in a cascade control application). Appropriate default parameters are merely in the same mathematical order of magnitude as the final tuned value. Rarely will the default parameter result in perfect operation of the control loop. It is only intended to get close enough to provide decently steady control until proper tuning can take place. It is usually easier to think in terms of proportional band than proportional Gain. Consider a room temperature. What would be an appropriate band around the setpoint to maintain? Perhaps ±5°F. If ±5°F is selected, that would result in a 10°F proportional band. Plug that into the equation along with the assumed UMin and UMax values: This would result in a default Gain of 10. It is important to remember that Gain is a unit-less value. A Gain of 10 is neither large nor small – merely relative to the process variable and anticipated error from setpoint. Consider a PID controlling an outside air damper to maintain an outside air flow of 1000cfm. Would a proportional band of 10cfm make sense in this situation? Probably not. A more appropriate value might be a band of 500cfm. Plug this into the same equation as before: In the case of air flow control, because the process variable and anticipated error from setpoint are so much larger than in temperature control, a more appropriate default Gain would be 0.2. In a third situation, consider a PID controlling static air pressure in a supply duct by modulating a variable speed fan. A proportional band of 500”wc would not make sense. A band of 0.8”wc might be more appropriate. In the instance of static air pressure, a default Gain of 125 would be suitable. Comparing these three situations with Gains of 0.2, 10, and 125, they will all have relatively similar speeds in the control loop. Just by glancing at these values alone, it cannot be said that any of them are “bigger” or “faster” than the others without a more in depth mathematical analysis. In addition to the value of the Gain, the sign is also important. Positive values represent reverse acting PIDs like a hot water valve where the signal to the valve will decrease as the room temperature increases. Negative values represent direct acting PIDs like a chilled water valve where the signal to the valve will increase as the room temperature increases. To avoid confusion at the front end, and reduce the possibility that end users will accidentally reverse the action of a PID, it is best practice to always use a positive value PVR to represent the value of the Gain. Then use an Expression absolute value operator “ABS()” to remove any sign and apply a negative value when necessary. Using this method, the Gain from the front end will always appear as a positive value and no consideration for the proper action of the PID will need to be taken after the programming phase is complete. Ti Ti is the integral time, or the integral portion of the PID control. It is an input value of type Real. Adding integral control to a straight proportional algorithm helps to avoid “controlling to an offset.” It is theoretically possible that a chilled water valve at 40% is exactly the amount of chilled water required to maintain a supply air temperature of 58°F, even if the setpoint is 55°F. If the error in the signal never changes, then the proportional algorithm will not change the output signal. And an offset has been achieved and will now be maintained indefinitely. Integral time will eliminate this possibility. Every Control Interval that the temperature remains above the setpoint, integral control will add a little more to the control output. This will cause the measured variable to always approach the setpoint. Because this value does have units (seconds) it is possible to compare one integral time value to the next. Ti is inversely proportional to the integral effect in the formulation of the next control output. In general, the smaller the Ti value, the more integral control will affect the control output. A value of 50 seconds would have a very large impact on the output. A value of 2500 seconds would hardly affect the control output at all. The exception to this rule is that a value of 0 seconds will disable integral control. Typical default values fall anywhere between 250-1000 seconds. Some PID solutions may be susceptible to “integral wind up” where the internal calculation desires and integral response beyond the output limits. When the control signal reverses, the integral wind up must be reversed before the output sees the change. In the PIDA algorithm, integral wind up is not a concern. Td Derivative time is also measured in seconds and represents the D portion of the PID. It is an input value of type Real. Derivative control is generally considered too complex and sensitive to measurement noise to be of sufficient benefit to HVAC control. A Simple Block “PVR” set to a value of 0 seconds will disable derivative control, but allow the tuner to add derivative control if desired. DZ Dead zone refers to the amount above and below the desired setpoint that will result in no change to the control output. It is an input value of type Real. This differs from the concept of a proportional band in that it is not centered around the value. While a proportional band of 10°F represents ±5°F around setpoint, a dead zone of 10°F would represent ±10°F around setpoint. A dead zone is helpful to reduce “hunting” of the control output where it repeatedly rises and falls when a steady output would cause the control variable to steady out. Typical values depend on the process variable. For a supply air temperature, anywhere from 0.25°F to 0.5°F would suffice. For outside air flow, anywhere from 50cfm to 100cfm might be appropriate. In a supply air static pressure control loop, limiting the dead zone to 0.1”wc would suffice. TSg TSg is short for tracking signal. It is an input value of type Real. The internal equation uses this as the value of the previous control signal. It should be looped back to the PID from the output signal. This might be directly from the output of the PID, or it may be after some external logic. The TSg input can be used in another way as well. When the PID is in Mode 0, the TSg value passes directly through to the output signal. By setting the PID to Mode 0 for the first second of a control period, initial positions other than UMin or UMax can be achieved. It can also be used to keep a PID in synch with an output that has been overridden by the front end. If the PID is controlling a physical output AO, then the output of the AO should be looped back to the PID.   Configuration Parameters of the PIDA Block ControlInt The Control Interval represents the number of seconds in between each successive calculation of outputs. If this value is set to 0 seconds, then the Control Interval will match the cycle time of the application. The Control Interval should be thought of in terms of how long a change in the control output will take before the impact is realized on the measured variable. Consider three scenarios: Scenario 1: A variable speed drive modulates a pump speed to maintain chilled water differential pressure. Because water is incompressible, a change in the pump speed results in an almost immediate change in the pressure. A Control Interval of 1 second is appropriate in this scenario. Scenario 2: A chilled water valve modulates to maintain a supply air temperature setpoint. The supply air temperature sensor is a few feet down the duct from the chilled water coil. A PID controller moves the chilled water valve from 0% to 10%. How long will it take before the supply air temperature starts to fall? Granted, there are several X factors in this equation, but a good guess might be around 20 seconds. A Control Interval of 20 seconds is appropriate in this scenario. Scenario 3: A supply air temperature setpoint modulates to maintain a large auditorium's temperature setpoint in a classic cascade control configuration. A chilled water valve then modulates to maintain the supply air temperature setpoint. Room temperature dictates that the supply air temperature setpoint should drop from 60°F to 55°F. How long will it take before this change in setpoint causes the room temperature to fall? It may take a full minute, perhaps even several minutes before that change has an affect at the room temperature sensor. A Control Interval of 80 seconds, while seeming very slow, is perfectly appropriate here. Correctly configured Control Intervals will allow one change in position to have an effect on the measured variable before a second (or third, or fourth...) change is made. A proper Control Interval will stop the valve from overshooting unnecessarily. UMin UMin is the minimum possible output of a PID controller. In most applications (valve and damper actuators) this will be set to 0%. In the case of a cascade control supply air setpoint PID, it might be set to 50°F. If the hardware output has a minimum position (say on an outside air damper), it is best to accomplish this with secondary logic as opposed to using the PID UMin. Otherwise if the PID is made public to the front end, the user will never see this value drop to 0, even if the control output is at 0. UMax UMax is the maximum possible output of a PID controller. In most applications (valve and damper actuators) this will be set to 100%. In the case of a cascade control supply air setpoint PID, it might be set to 90°F. StrokeTime The name Stroke Time refers to the manufacturer specified stroke time of a physical actuator. By setting the PID to the same stroke time as the valve it is controlling, it is guaranteed not to “wind up” faster than it is possible for the valve to react. Whenever possible, set the stroke time to match the physical stroke time of the actuator it is controlling. However, stroke time can be thought of in another way. It is used to calculate DuMax, the maximum rate of change of the controller output during one Control Interval. In the case of a chilled water valve that modulates between 0% and 100% with a Control Interval of 20 seconds, see how a stroke time of 180 seconds affects the DuMax: A stroke time of 0 seconds will not limit the rate of change at all in the controller. Based on the error and the Gain, it could potentially jump the full 100% stroke at once. By setting the stroke time to 180 seconds, the amount that the control signal can move every 20 seconds is now limited to 11.11%. It is not proper practice to employ stroke time as a tuning mechanism of a PID. It should be set prior to and independent from the tuning process.   Output of a PIDA Block The output of a PIDA block will usually control a hardware output from a Xenta controller. Because of this, it is typically connected to a Menta Simple Block “AO.” In Function Block it may be output to an analog value or hardware output.   Output of a PIDI Block A PIDI controls a floating actuator using two Simple Block “DOPU” digital pulse outputs. The PIDI will output a value between -1 and 1, which the DOPU block converts into the appropriate pulse lengths. Inverting the decrease signal will pulse the actuator closed when the output of the PIDI is negative.   The downside to PIDI control is that there is no percentage value to report to the front end about the position of the actuator. This is why use of the PIDI is somewhat rare. The same control can be accomplished using a PIDA with some external logic to pulse the floating actuator open and closed. Using a “virtual feedback” signal to mathematically monitor the assumed position of the floating actuator allows the end-user to view a percentage open signal for the actuator. It also allows them to override the Not-Connected AO to a certain position and have the floating actuator travel to that position just as an analog output would. The following example converts a Not-Connected AO from a PIDA into pulse output DOs from the controller. Public Signals and Public Constants All of the parameters that go into the operation of a PID need to be considered when tuning its operation. Eventually, one will come to the question of what parameters need to be made available from the front end. While some thoughts might end up on the well-meaning, under-trained end-user who could potentially wreak havoc by adjusting values, it is more important to consider the startup technician. If a value is not public from the front end, then a download must be performed to make any changes to any values. By making every parameters public by default (and only selectively removing certain parameters during exceptions) less time will be spent in the field during start up. After the PIDs have been tuned, it is always possible to remove certain values from being public. The exceptions are UMin and UMax, which when controlling a valve or a damper are almost always 0% and 100%. If desired, these can usually be hard-coded into the PID with little consideration. However, they can also be made available from the front end with little or no ill effects. Floating, PID, or Cascade Control There are three main control loop algorithms to consider when programming. Which one best suits the application is really a factor of the control loop speed. Consider the three options: Floating Floating control (also called bump control) involves making small, measured adjustments to the control signal on specified intervals. This is usually the best option any time a variable speed drive is involved. This is because these drives typically control supply fan static pressure or hot/cold water pump differential pressure. Both of these are very fast control loops. A slight change in the speed of the drive results in an almost instantaneous change in the measured variable. Floating control reacts more gradually to these quick changes. It compares the measured variable to the setpoint, and if it is too high, it bumps the control signal down a little bit. If the measured variable is too low, it bumps the control signal up a little bit. PIDs can (and often have been) used successfully to control very fast control loops. However, they are typically tuned to closely resemble floating control – low Control Interval, very little proportional control, very high integral control. In the end, it may be easier for a technician to understand and adjust “1% every 5 seconds” than “a Gain of 125 and an integral time of 175 seconds.” The other advantage to floating control is its adaptability. When tuning a PID, it is tuned to one exact set of circumstances – a certain load on the building, a certain volume of piping, etc. If enough of those conditions change by enough, the PID can be sent into oscillations. Floating control will not be affected by these changes. Consider a PID tuned to control a chilled water pump, which maintains differential pressure during the winter when loads are low. During the summer, a manual valve is opened to provide cooling to the athletics storage shed that was unoccupied all winter. This will increase both the demand for cooling and the volume of the pipe. This could potentially render the PID useless. However, a floating control will not react any differently. It will simply increase and decrease the speed as needed. See an example of floating control: The downside to floating control is that there is no proportional control. It will not take a bigger step size when the error is high. To combat this, and especially to aid during startup of equipment, this floating control macro utilizes two different step sizes – one for when error is low, and one for when error is high. By setting the threshold sufficiently high, this will cause more rapid acceleration during startup, and then quickly revert back to normal control during normal operation. This same code will also work relatively well for any size or nature of supply fan or supply pump. Minor adjustment of the parameters may be needed, but it will give a very decent starting point. PID PID control is for control loops of moderate speed. It can be thought of as the "valves and dampers" control method. A chilled water valve modulating to control supply air temperature or a damper modulating to control outside air flow are two examples of when PID control is appropriate. It is a source of debate whether PID control is appropriate in different situations. Some attest that a PID loop can be tuned to accurately control in any situation, including those where this document recommends either floating or cascade control. While this is certainly true, just because a PID can be used, does not mean that it is always the most appropriate solution, or that it will continue to work even as conditions change. Cascade Control Cascade control is used in very slow control loops. It is called cascade because two PIDs are used in a cascading arrangement – the output of the first is the setpoint of the second. An example of when to use cascade control is to modulate a chilled water valve to maintain the space temperature in a very large gym or auditorium. A small change in the chilled water valve position could take a very long time to have an effect at the sensor. If a regular PID is used, it is likely that the PID will wind up all the way to 100% output before the sensor ever experiences the first adjustment's effect. Then it will stay at 100% until it over-cools the space and starts decreasing the call for cooling. The same thing will happen on the reverse side as it modulates all the way to 0% and under-cools the space. And the cycle will continue indefinitely. In this cascade configuration, the supply air temperature setpoint is modulated based on the room temperature and setpoint. The chilled water valve PID then maintains the supply temperature. This will allow control that is more accurate and prevent the oscillation sometimes seen by inappropriate use of a single PID.   Putting It Into Practice There are college courses devoted entirely to the subject of PID control. The subjects covered in this document have barely scratched the surface of the topic. The intent is to give the average Menta/Function Block programmer and field technician the information needed to get a system up and running in as little time as possible with the most satisfied customer possible. Understanding when and why to use PID control will increase accuracy and efficiency of control loops and decrease wasteful overshoot, hunting, and oscillation. Tuning efforts will also be accelerated when the default parameters only require minor tweaking instead of calculation and trial and error. Using the hints and tips suggested will allow not only for proper programming techniques, but also for creation of macro libraries that can be reused and shared to improve effectiveness across business units.

Issue Windows Authentication must be applied consistently for Security Expert, SOAP, and Data Sync Service to work. Product Line Security Expert Environment Security Expert Microsoft Windows Cause If Windows Authentication is enabled in Security Expert (this is done during installation with a checkbox) then it must also be enabled in SOAP and Data Sync Service. Resolution Windows authentication is NOT enabled by default in Security Expert. This is a tick box on Security Expert installation. When you install SOAP you also need to select this (another tick box). However, Data Sync Service (DSS) is created with no options during installation. To enable or check the Windows Authentication setting for Data Sync Service, see below. If installation has already been completed and you need to verify if Windows Authentication is enabled for each component you must follow the steps below.   1. Security Expert Thick Client/Server   There are two options for setting Windows Authentication for Security Expert Thick Client/Server. Option 1. Edit the Security Expert Data Service config file “SecurityExpertSV.exe.config” using a text editor. This file is located in C:\Program Files (x86)\Schneider Electric\Security Expert. Locate this line: <netTcpBinding> <binding name="Binding1" openTimeout="00:10:00" receiveTimeout="00:21:00" sendTimeout="00:21:00" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"><security mode="None"/> <readerQuotas maxDepth="32" maxStringContentLength="90000000" maxArrayLength="90000000" maxBytesPerRead="90000000" maxNameTableCharCount="90000000" /> </binding> </netTcpBinding> security mode= “None” denotes that Windows Authentication is not enabled. If Windows authentication has been enabled during installation then this entry will be missing. Option 2. Rerun the installation process and select “Modify” and then set the enabled flag tick-box or make sure the tick-box is not checked, depending on what is required.   2. Security Expert SOAP   There are also two options for setting Windows Authentication in SOAP. Option 1. Edit the SOAP service “Web.config” file located in C:\inetpub\wwwroot\SecurityExpertSOAPService with a text editor. Locate this line: <netTcpBinding> <binding name="Binding1" openTimeout="00:10:00" receiveTimeout="00:21:00" sendTimeout="00:21:00" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"><security mode="None" /> <readerQuotas maxDepth="2000000" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> </binding> </netTcpBinding> Again, security mode = “None” denotes that Windows Authentication is not enabled. If Windows authentication has been enabled during installation then this entry will be missing. Option 2. For SOAP you also have the option of uninstalling and reinstalling and selecting the check box (or not) to enable Windows Authentication during the install process. The installer for SOAP currently does not support “modify” or “change” operations.   3. Data Sync Service   Edit two config files using a text editor. Both files are located in C:\Program Files (x86)\Schneider Electric\Data Sync Service. In “DataSyncServiceConfig.exe.config” locate this line: <netTcpBinding> <binding name="NetTcpBinding_IService" openTimeout="00:10:00" receiveTimeout="00:21:00" sendTimeout="00:21:00" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"> <readerQuotas maxDepth="2000000" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> <security mode="None" /> </binding> </netTcpBinding> Again, security mode= “None” denotes that Windows Authentication is not enabled. If Windows authentication has been enabled during installation then this entry will be missing.   4. Summary   In order to properly run SOAP and Data Sync Service with a Security Expert system, there are four config files that must be consistent. SecurityExpertSV.exe.config Web.config DataSyncServiceConfig.exe.config DataSyncService.exe.config All four must either contain the text <security mode="None" /> or all four must NOT contain that text.

Issue When a user attempts to connect to the Sigma 4.08 (3.46.57) Server using a WebClient, the client connects, but the screen remains blank. Product Line Satchwell Sigma Environment Sigma WebClient 4.08 (3.46.57) Cause When Sigma 4.08 is installed, the installed version of LogonSE.swc is blank. Resolution Download the correct version of LogonSE.swc. Shutdown the Sigma client and server. Navigate to Sigma/Data/Graphics/Drawings and delete LogonSE.swc. Copy the downloaded version of LogonSE.swc to Sigma/Data/Graphics/Drawings. Restart the Sigma client and server, and then test the Web Client.

Issue Is there a way to specify the priority that the system should use by default when writing to the value of BACnet objects in EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation BACnet Cause It may be necessary, especially in a legacy b3 environment, or third party BACnet network integration, to write by default to a priority other than 16 in the Command Priority stack. Resolution The default Command Priorities within a system used when writing to BACnet objects are governed by the Interface Manager in the ES.  These settings are then inherited to all AS. Command Priority 16 is used by default writing to the Value Property of a BACnet Object Command Priority 8 (Manual Operator) is used by default when Forcing the Value BACnet Object in EBO. Both defaults can be changed but care should but be taken here as any changes will ripple through the entire system and may have unforeseen consequences. Script programs created in a b3 will still use Command Priority 10 by default. It is still possible to write at any other priority in EBO by Binding directly to the desired command priority.

Issue Need an alert message sent out to notify when a controller disconnects from the network Product Line Access Expert Environment Access Expert Controller Access Expert Premise Software Access Expert Hosted software Cause Controllers can potentially disconnect from the network. Knowing when can help troubleshoot the cause. Resolution Having an alert based on a long time disconnect event can help to prompt an investigation. The time considered for this disconnect event is adjustable within the instance settings. Right-click the event "Controller Disconnected (Long Time) in event definitions and select view event history Right-click any of the events and select add Email template Create an email template using the pre-canned expressions and plain text Create an Alarm Action, select Notification when adding the action Fill out the template with the Email Template and who the recipients should be Create an Alarm Definition Assign Event type: Controller Disconnect (Long Time) Assign Alarm Action: Alarm action created in step 5

Issue If a SmartX Server is using External Log Storage how often are new trend log data and events sent to the TimescaleDB? Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When a SmartX server is using External Log Storage many of the trend logs and all new event records are sent to a TimescaleDB for storage. Resolution New event records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them. Some records as "Edit" and "Comment" are sent immediately. New trend log records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them.

Issue Need an alert message sent out to notify when a controller disconnects from the network Product Line Access Expert Environment Access Expert Controller Access Expert Premise Software Access Expert Hosted software Cause Controllers can potentially disconnect from the network. Knowing when can help troubleshoot the cause. Resolution Having an alert based on a long time disconnect event can help to prompt an investigation. The time considered for this disconnect event is adjustable within the instance settings. Right-click the event "Controller Disconnected (Long Time) in event definitions and select view event history Right-click any of the events and select add Email template Create an email template using the pre-canned expressions and plain text Create an Alarm Action, select Notification when adding the action Fill out the template with the Email Template and who the recipients should be Create an Alarm Definition Assign Event type: Controller Disconnect (Long Time) Assign Alarm Action: Alarm action created in step 5

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

Issue When mapping the EcoStruxure Building Operation (EBO) Trend Logs to EcoStruxure Energy Expert, not all trend logs are visible in the ETL Tool 'Load Sources'. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Energy Expert Cause The EBO user credentials entered into ETL for connect to the EBO Database must have access to BOTH the trend log itself, and the point which the trend log is logging. Resolution Edit the EBO user which the ETL is using to connect to EBO and give a minimum of Read Only access to both the Trend Log in question and the Point being logged  and then in the ETL re-run 'Load Sources'.  The additional points which were missing before should now be available for mapping

Issue Where Sigma utilizes the site Ethernet network, and that the network consists of multiple subnets, or is using Sigma DNN's with ARCnet or ethernet secondary LANs. Global object values are not received at the receiving controller when it is on a different subnet to the sending controller. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,

Issue Duplicated SFE Short Form Edit graphics Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Sigma Cause A duplicated set of Short Form Edit graphics are created but are in a different language appear along side the original SFE graphics when using Data Import with a Sigma transition into EBO The example below shows the original DataImport was completed in English, the second DataImport was completed in Danish. Resolution Before a Sigma DataImport is undertaken, ensure that the correct language is set in EBO. Delete the Sigma Interface, set the correct language and start the transition again. Note: By deleting the Sigma Interface, this will delete all the SFE graphic links on the objects and a clean set of SFE graphics will be created on all the objects.

Issue Is it possible to include the Comments field from Extended Logs into Report Server Reports? Product Line EcoStruxure Building Operation Environment Building Operation Reports Server Cause Regardless of the new Reporting Features in EcoStruxure Building operation (EBO) 3.2, users of existing systems up to and including EBO 3.1 are asking if it is possible to include the Comments field in Extended Logs within the Enterprise Sever to enhance the data in RS Reports? Resolution Extended Log Comments within the ES are not available to Report Server reports today and given the move to new Reporting Features now available in EBO 3.2 it is unlikely that an Enhancement Request for such a feature would be implemented quickly. Therefore, the suggestion here would be to migrate the Extended Logs to External Storage via TimeScaleDB where all the Extended Log data (including the comments) can be freely manipulated by 3rd party Reporting Products.

Issue Following a successful configuration of the Continuum Transition Tool (CTT) it has been noted that some ongoing changes in Continuum do not seem to then be migrated through to the Security Expert database. Product Line Andover Continuum Security Expert Environment Continuum Transition Tool Security Expert Data Sync Cause It would appear that on occasion, some changes made to Continuum Areas after the initial CTT Transition is completed, fail to be exported from the Continuum DB by the CTT in its periodic update, This can be verified by examining the actual CSV output and seeing that certain known changes to Areas  are simply not present.  The actual Security Expert Data Sync is working correctly but if the changes are not exported by the CTT then they cannot then be imported by the Data Sync Service Resolution Although this is not currently resolved, it is documented as a limitation of the Andover Continuum System. Page 21 of the Transition Guide Security Expert - Continuum Database - Transition Quick Start Guide states that the Last Changed field of an Area object is only updated if the object is edited in a specific way. Since the CTT uses the Last Change field to decide what new object changes need to be exported, this legacy issue in Continuum directly affects the update to Security Expert if the changes are not made as advised above.

Issue From a legal Microsoft Licensing point of view, it is important to be clear how many Client Access Licenses (CALs) are required when using a Report Server with SQL in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause While Microsoft Client Access Licenses are not required to make a Report Server installation function, ANY system which makes use of Microsoft SQL must consider the provision of sufficient purchased CALs to remain legally compliant and avoid potential fines. Resolution The Report Server Reporting Agent Service which is responsible for reading the data from the Enterprise Server (ES) and storing it the Microsoft SQL Server Database, will use one connection to the SQL Server. and therefore, requires one CAL. 

Issue On occasion IT Professionals may wish to know if Continuum can be installed/deployed via Microsoft System Centre Configuration Manager (SCCM). Product Line Andover Continuum Environment IT Installation/Deployment Cause Microsoft SCCM is a well-established platform for the deployment and management of installed software in an IT Environment, but since Continuum is now an older Legacy Schneider product it is unclear if it supports being deployed in this way. Resolution While Continuum 'may' work when deployed via SCCM, it is untried and untested at this time. Also given that Continuum is a Legacy product, there are no plans to test and support SCCM in the future.