Building Automation Knowledge Base

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue What utility in Windows XP can disable items in Startup? Environment Windows XP Cause Items that run on startup can sometimes make the boot up process for a PC very slow. Depending on which applications have been added to start automatically on startup, it can also cause problems if things load in the incorrect order. Resolution Click the Start button in Windows XP Select Run Type msconfig and click OK.

Issue How to find the IP address information on a PC? Environment Windows Operating Systems Cause Need to identify the IP address of the workstation (PC). Resolution For a Windows 95/98 PC, go to a DOS screen and run WINIPCFG. For a Windows NT / XP / Windows7 / Server 2008 PC, run a CMD window and run IPCONFIG.

Issue When opening (pull up) sunblind, it stops at the end of runtime and then rolls back down. When closing (pull down) sunblind, it stops at the end of runtime and then rolls back up. Environment Lonworks devices including REG-N MSE4 (SVEA 32237-346) Sunblind actuators Cause The sunblinds only have UP/DOWN functions, and there is no panel angle setting. The sunblinds are not venetian, just simple sunblinds. The sunblind actuator is preconfigured for use with venetian blinds. For example when driving down completely first the motor is energised for the time configured in UCPTdownDriveTime, then stops a short moment and then turns the angle of the lamella by energising the motor for the time configured in UCPTpanelTurnTime (dependent on the value of parameter UCPTdownPanelAngle). Resolution When not  using venetian blinds the parameters UCPTdownPanelAngle, UCPTupPanelAngle, UCPTpanelTurnTime and UCPTpanelTurnTimeBottom should be set to zero. Commands to the sunblind actuator then should as well have the value of zero in the rotation part of the SNVTsetting command.

Issue Change an IP address on Windows 8 to a static address. Product Line Other Environment Windows 8 Cause Changing the IP address of a PC is often done to ensure it resides on the same subnet and network as the system or devices it is trying to communicate with. Resolution From the Start Menu (Tiles), open the Charms bar by moving the mouse to the right bottom corner of the screen or press the Windows Key + C and click on Search. Highlight Settings. In the Search box type Network to search for any network related options From the list options choose Network and Sharing Center. From the View Your Active Networks section, select Local Area Connection. Go to Properties. Result: The Local Area Connection Properties screen appears. Highlight Internet Protocol Version 4 (TCP/IPv4) and click on Properties. Result: The Internet Protocol Version 4 (TCP/IPv4) Properties screen appears. Click Use the following IP address. Complete the configuration fields as shown below. This part of the configuration requires attention to detail, because one error will prevent you from getting on the network. Be sure you have this information at hand when you start to configure the TCP/IP protocol: IP Address: x.x.x.x Subnet mask: 255.255.255.0 Default gateway: x.x.x.x  Enter these numbers in the appropriate fields and click OK. Continue to click OK or Close as appropriate until you return to the Network Connections screen. The Local Area Connection icon text should now say "Enabled". To test the new IP address: Open a command prompt in Windows 8 Swipe to show apps screen Scroll down and locate Windows system section heading Under Windows system, press or click on Command Prompt (a new Command Prompt window will open up on the Desktop.) You then can type in IPCONFIG then hit Enter and look for the new IPV4 address. You can also try to type in PING (IP ADDRESS) that should reply with the new IPV4 address if set correctly.

Issue Some helpful basic IP commands. Product Line Other Environment Computer with IP NIC or Network Cause Need for basic IP configuration or IP address Resolution Go to start, click run and type in "cmd". This takes you to the command prompt. Type in: "ping xxx.xxx.xxx.xxx" to see if your device is online and its response time. Make sure you put the space between "ping" and "xxx". "ipconfig" and hit enter to get the info of the computer you are currently using. You'll get the IP address, subnet mask and the gateway. "ipconfig/all" and hit enter to get more info on the machine your using. It will give you all the above and then some including the DNS server addresses. "tracert xxx.xxx.xxx.xxx" and hit enter and you can see the servers that you are going through to get to your destination. This can be used when connecting to a Loytec or a iLon and the IP address is being presented to the L-IP or iLon is unknown. Connecting through a firewall/gateway/NAT server, you are not presenting the PC's address - when you do the tracert you will go through your gateway and the next address will be the IP you are presenting- Use this in the iLon as the LNS server address.

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 Import Vista Alarms and Events into an Excel file Product Line TAC Vista Environment Vista 5 SQL 2005 Cause Unable to import Vista Alarms and Events in to excel file from Vista Resolution Select Data > Import External Data > Import Data as shown in below screen capture.   Select New SQL server connection as shown in below screen capture.   Enter Vista SQL Server instance name as shown in below screen capture.   Select taclogdata from dropdown menu as shown in the below screen capture.   Select Event table as shown in the below screen capture.   Rename .odc as .dsn as shown in below screen captures.   Click finish button.   Select Edit Query as shown in below screen capture.   Select SQL as shown in below screen capture.   Paste the Query as shown in below screen capture. Click OK button to apply the query.   Click OK button as shown in below screen.   Click OK button as shown in below screen.   Events are imported in to Excel   Query for Events based on dates: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN '10/12/2009' AND '10/12/2009 23:59:59.997') Query for One Day Events: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE()) Query for Alarm based on dates: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (Event.EventDatetime BETWEEN '08/24/2010' AND '08/25/2010 23:59:59.997') Query for One Day Alarm: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE())

Issue   An error occurred while setting the system language property. Please validate that your language resource files are valid. Invalid format. (Subsystem: LNS, #40) Product Line TAC Vista Environment LonMaker Cause Resource File Languages have become corrupt. Resolution Restore the Resource File Languages:  Shut down LonMaker. Go to http://www.lonmark.org/technical_resources/resource_files/ At the time of this article, the latest version is LonMarkResourceFiles1304.exe.  Download this file.  If a later version exists, download the latest file. Run the executable. Restart LonMaker.

Issue In the event of a lost or broken connection between the Vista Server and SQL server, the Vista Server will begin to queue up its events and log values in the $queues\insertevents and $queues\insertlogvalues directories. Once your connection has been re-established those queued files will then be written to the Vista DB, however this process can take an extremely long time,  and possibly cause the Vista server to hang at start up and even crash.  Product Line TAC Vista Environment Vista 4.3.0 or higher with SQL  Cause Broken SQL connection between Vista and local or remote SQL server. Resolution If you are not in the need to this queued event and log data you can manually delete all of these queued files. Opening this directory with Windows, highlighting all files and deleting them usually does not work, because of the enormous amount of files that may be stored in their respective directories. The best way to delete these files is to use DOS. Remember stopping both TAC Vista Server and the DSS Writer service before deleting the files.   Method 1: The proper steps to delete these files with DOS using the "rmdir" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues Type "rmdir /S /Q insertevents" - all files and folders including the "insertevents" folder will be deleted Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5.   Method 2: The proper steps to delete these files with DOS using the "del" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues C:\Projects\School\VistaDB\$queues>cd insertevents C:\Projects\School\VistaDB\$queues\insertevents> Type "del *.*" and then "Y" to confirm that all files on that directory will be deleted. C:\Projects\School\VistaDB\$queues\insertevents>del *.* C:\Projects\School\VistaDB\$queues\insertevents\*.*, Are you sure (Y/N)? y Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5. Now both of these directories should be emptied and if your SQL connection issue has been rectified your events and logs will write as normal to SQL.     Alternatively, this utility will split the queued files into folders of 4,000 files each.  Windows can handle each of these folders and make the task of deleting the queued files more manageable.  Click the screen capture below to download the utility.  

Issue All values in the Xenta 102-AX Plug-in are blank. Product Line TAC Vista Environment Xenta 102-AX Plug-In LonMaker Cause If the Resource File Languages have become corrupted on your PC, then the plug-in will not know how to display the required data. Go to LonMaker > Network Properties > Resource File Languages.   If the only Language listed is "ENU," then the language files are corrupted. ENU is the default language and will display all data in the LNS environment -- plug-ins, browser, get values -- in an enumerated format that is not usable. Everything will continue to work, but monitoring data in the LNS environment and configuring ASCs via plug-ins will be impossible. Resolution Restore the Resource File Languages: Shut down LonMaker Go to http://www.lonmark.org/technical_resources/resource_files/ Download LonMarkResourceFiles1300.exe Run the executable Restart LonMaker Check Network Properties again. US English should be listed and the plug-in should populate with data. Note: There may be Beta versions 13.04 and 13.10 on this website. Do not use these LonMark resource files. The newer versions cause errors in the 102-AX plug-in. For more information see Opening the Xenta 102-AX plug-in results in "request for LonMark Object status" error .

Issue Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the 102-AX shows a value, but the inbound SNVT on another controller is invalid or a default value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX LNS SNVT bindings LonMaker NL220 Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All 102-AXs come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution Open the Xenta 102-AX device Plug-in Go to the Node Configuration Tab Set the Node Minimum Send Time (SCPTminSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoSpaceTemp nvoStatOccBtn nvoSetPtOffset nvoLocalOccLatch nvoEmergCmd nvoUnitStatus nvoBoxFlow nvoTerminalLoad nvoEffectSetPt nvoFlowControlPt nvoOccpncyStatus Set the Node Send Heartbeat (SCPTmaxSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoAirFlow nvoAuxTemp1 nvoAuxTemp2 nvoUnvInput1 nvoUnvInput2 nvoUnvInput3 nvoUnvInput4 nvoCO2sensor nvoFanLoad nvoHeat1Load nvoHeat2Load nvoMotorPositn nvoActualValue nvoOAirFlowRatio nvoAirPressure It is typical to set the Node Minimum Send Time and the Node Send Heartbeat to 60 seconds and the Node Receive Heartbeat to 0 seconds.  

Issue How to find a dongle ID (PSU ID) if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista IV TAC Dongle Utility Cause The dongle ID (PSU ID) can be found printed on the side of a Vista IV licensing dongle. However, on older dongles, this number can rub off. It is still possible to extract the dongle ID using the TAC Dongle Utility. Resolution Download the TAC Dongle Utility Install TAC Dongle Utility and run the program. Start > Programs > T A C > TAC Tools > TAC DongleUtil Plug in a valid Vista IV end user dongle. Hit Refresh on the Dongle Utility PSU ID is displayed. This is the ID required to add new licensing to an existing dongle. ReadFind a Vista 5 dongle ID for how to find a Vista 5 dongle ID.

Issue Plug-in 'TACZBuilderPlugIn.Application' launch failure. Unspecified error Product Line TAC Vista Environment LonMaker 3.X TAC ZBuilder Plug-in Cause An unspecified error in the launching of the TAC ZBuilder Plug-in is either caused by a faulty installation or registration of the plug-in. Resolution Check under Start > Settings > Control Panel > Add or Remove Programs. Look for TAC ToolPack 5.X.X. Make sure the version number 5.X.X matches the current Vista installation. If it does not, uninstall the current version of the ToolPack and install the correct version. If it is the correct version, proceed. Check the plug-in registration. In LonMaker go to LonMaker > Network Properties > Plug-in Registration. Look for TAC Vista System Plug-In (Version 5.X.X) Make sure the version number 5.X.X matches the current Vista installation. If it does not, unregister the current version of the Plug-in and register the correct version. If everything appears to be installed and registered correctly, but the error persists, uninstall and reinstall the correct ToolPack. Reboot the PC, reregister the plug-in, and try to launch it again.

Issue   The requested information is not available from the device. (Subsystem: NS, #28) Product Line TAC Vista Environment LonMaker 3.2 (Turbo) Cause The requested information is not available from an application node. For example, transceiver status, SI/SD data, and the network variable names are not always stored in the node. This error is a known issue with LonMaker 3.2 (Turbo). Resolution Navigate to http://www.echelon.com/support A username and password are required to access the download section, but it is free to register. Download LonMaker Turbo Service Pack 2 Install LonMaker Turbo Service Pack 2.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Product Line TAC Vista Environment LonWorks Network Cause A LonWorks network test and diagnostic tool are needed. Resolution NodeUtil is a Windows console application that can be used with Echelon’s family of network interfaces (including the PCLTA-20, PCLTA-21, PCC-10, i.LON® 10, i.LON 100, i.LON 600, Loytec Devices, SmartServer, SLTA-10, U10, and U20 network interfaces) to diagnose and configure LonWorks® network interfaces, routers, and devices. NodeUtil is a test and diagnostic tool - it is not a network management tool.  It will not assign destination addresses or bind network variables. Nor will it format LonMark® interoperable device information. This tool can be used in the following conditions: The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Other network test and diagnostic need This software can be downloaded at http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0373-01A The username and password are needed. This site is opened to the public for registration, so everyone can obtain it. Once you are logged in by default "Recommended Downloads" will be selected. Select "Development Tools" instead to locate the NodeUtil software.

Issue Error when commissioning a Xenta 5/7/9xx indicates an out-dated or mismatched XIF (device template). Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) on a Xenta 5/7/9xx LON device   If this error occurs on any other device besides a Xenta 5/7/9xx, please reference Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) for resolution. Product Line TAC Vista Environment LonMaker 3.X Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Cause The Program ID inside the controller does not match the Program ID specified for that controller inside the LNS environment resulting in a Program ID mismatch. Program IDs are unique identifiers created for use in device templates and are based on the XIF. Resolution Resolve the Program ID mismatch by making the Program ID in the controller match that in the LNS environment. Download the controller using XBuilder. Send project to target. Generate the latest XIF for the XBuilder project. In the Network Pane, right-click on the root (TAC_Xenta_511 in this example) Select Generate XIF File   Find the new XIF that has been generated in the XBuilder Project directory: targetimage\configdb\lon\TAC_Xenta_511.xif Default XBuilder locations XBuilder 5.1.3 and prior: C:\Documents and Settings\All Users\Application Data\TAC\TAC XBuilder Projects XBuilder 5.1.4 and later: C:\Documents and Settings\All Users\Application Data\Schneider Electric\TAC XBuilder Projects Windows 7: C:\ProgramData\Schneider Electric\TAC XBuilder Projects A good practice is to view details of the folder to confirm the time stamp of the XIF file. It should match the time that the file was generated in XBuilder. This file will be selected later, so another good practice is to rename the file to something more meaningful -- the name does not matter. "WebServer.xif" may be easier to find later and confirm it is the correct file. It is also perfectly acceptable to move this file to a new location -- Device Files of your overall project, for example. That can also help in later steps, especially if the default XBuilder Project location is used. In LonMaker, right-click on the device, and choose "Replace" (Not in System Plug-In)   Browse to the newly generated XIF file. Give the new device template a name. Select Finish. Commission the Xenta 5/7/9xx into the network. The Program IDs now match and the error is cleared.

Issue Troubleshooting 2-Output PWM on a Xenta 102-AX Floating actuator for heating applications (hot water valve) Product Line TAC Vista Environment Xenta 102-AX PWM_2 floating hot water valve actuator Cause Multiple causes legitimately keep the hot water valve two-out floating control from stroking. Resolution The Xenta 102-AX controller supports auxiliary heat with two outputs. Both outputs can be utilized in a 2-output pulse width modulated (PWM) signal for control of floating actuators. This document suggests troubleshooting techniques to help narrow down the cause of improper operation of these hot water valve outputs. Start with Universal Output #2 On the Status tab of the 102-AX Plug-in, each of the universal outputs are listed under the “Network Bound Inputs” column. In the 102-AX Plug-in version 5.1.4, this column has been erroneously omitted. Download TAC Toolpack version 5.1.4 Hotfix 72 from the Buildings Business Extranet to resolve the issue. The output that represents the 2-output PWM is Universal Output #2 only. Even though output #3 is involved in the process, only #2 in the Plug-in represents the actuator position. The first thing to do is override the output to three different positions: 0, 50 and 100%. Cycling between three different values ensures the actuator is actively stroking. Forcing the valve to 100% will cause the open signal to energize for the full stroke time (throttling range) of the actuator, after which it will be de-energized. Wiring problems discovered after this time period has elapsed would require the output to be forced to 0% and then back to 100% to energize the open signal for the full stroke time again.   Figure 1. Network Bound Inputs If the valve strokes correctly, then the unit parameters, wiring, and actuator are all correctly configured. Skip directly to the chapter entitled “Overriding the Output Successfully Stroked the Actuator.” If the valve did not successfully stroke, proceed to the next chapter where three possible problems are addressed. Overriding the Output Failed to Stroke the Actuator There are three main reasons why overriding the output would fail to stroke the actuator. Unit Parameters The Unit Parameters tab of the 102-AX Plug-in is where Universal Outputs #2 and #3 are configured to work in tandem to accomplish 2-Output PWM control of a floating actuator. Heat 1 configures both outputs when OUTPUT_PWM_2 is selected. There is no need to configure Heat 2. Changes to Heat 2 will have no effect on the heating operation.   Figure 2. Heat 1 Unit Parameters Make sure the output type is set for OUTPUT_PWM_2. The stroke time should match the manufacturer’s documented stroke time of the actuator. Delay on start and stop are dictated by user preference or customer specifications. Normal Stroke should be set for normally closed. Wiring Check the wiring of the actuator to the 102-AX. It should be wired as follows: Point Label Terminal Actuator Universal Output #2 V2 15 OPEN Universal Output #3 V3 16 CLOSE Ground G0 13 COM Actuator The last step to troubleshoot an issue with the actuator not moving is to test the actuator itself. This can be done by jumping out the open or close leg of the actuator to 24Vac power. If the actuator still does not move then it is faulty and should be replaced. Overriding the Output Successfully Stroked the Actuator If overriding the output causes the valve to move accordingly, then the configuration of the output and the physical configuration are all correct. The 102-AX controller logic is not calling for the valve to open. There are a number of reasons why this might be occurring. The Basics The 102-AX must be in a heating mode to open the valve (cooling mode will close the actuator). It may be displaying either HVAC_HEAT or HVAC_MRNG_WARMUP. The space temperature must be below the effective setpoint to be in heat mode and will generate a negative terminal load down to -100%. The terminal load will equal the heating valve position. Check that the heating/cooling setpoints and heating/cooling bands are set such that no overlap in the two modes occurs. Heating/cooling bands must be greater than 0°. Hardware Configuration If the 102-AX is not configured for a sufficient number of stages of heat, it will not cycle the valve. If there is no fan, then only one stage of heat needs to be defined. However, if a fan is defined, then there needs to be at least two stages of heat, because the fan is considered the first stage.   Figure 3. Fan Type and Heat Stage If the heating valve is to be utilized in morning warm up mode (when the duct inlet temperature indicates that the air handling unit is providing central plant heat), then the hardware configuration must state that supplemental heat is allowed during warm up.   Figure 4. Enable Heat on Warm Up If a supply temperature sensor is wired to Universal Input #1, it could be that it is sending the VAV into morning warm up mode when the heat is enabled, and thus, disabling the heat. If this is the case, there are two options. Universal Input #3 can be used instead and set as an outside air temperature. Alternatively, Universal Input #1 can be configured as "None."   Figure 5. Input 1 Selection Setting Input 1 Selection to "None" will not disable the reading of the sensor. UnivIn1_Sense.nvoAuxTemp1 will continue to report the duct supply temperature. Setting it to "None" disables the signal from affecting the internal logic – preventing the 102-AX from entering morning warm up mode. Note: If the VAV is already in morning warm up mode when the input is set to "None," the box will remain in morning warm up mode. Override the input temperature to something below room temperature prior to changing the input selection. Application Mode The SNVT input VAV_Controller.nviApplicMode can allow a supervisory controller to override the current mode of the VAV. Upon receipt of a new application mode, the 102-AX will encounter a brief synchronization period where the terminal load is held to 0%. If the SNVT is being sent from a data manager, and the period on the output SNVT in Menta is set to 60 seconds, then the 102-AX will zero out the terminal load every 60 seconds, preventing proper operation. Set the SNVT output to a period of 0 seconds, and it will only write a new value on change and allow proper external control of the mode. Airflow Setpoint The Warm up Maximum airflow setpoint must be greater than or equal to the Heating Minimum airflow setpoint.  If this is not the case, then the airflow setpoint will default to the unoccupied flow setpoint (typically 0 CFM) any time the VAV is in heat mode, and the heating output will not be utilized.  This can be easily overlooked in applications where Warm up Mode is not being used, but this one parameter must still be set. This is fixed in the Xenta 102-AX firmware v2.18.   Figure 6. Airflow Setpoint Actual Airflow In order for the heating outputs to be energized, the airflow must be at least 80% of the minimum heating airflow setpoint. This is hard coded into the controller and cannot be disabled. The only way to remove the interlock is to set the minimum heating airflow setpoint to 0 CFM; however, in this situation, the VAV will close the damper in an attempt to provide 0 CFM of airflow. The heating will modulate without any airflow at that point.   Figure 7. VAV Status not providing 80% Airflow Check on the VAV Status tab of the 102-AX plug-in to compare the airflow to the airflow setpoint. If the box cannot provide the necessary 80% of setpoint or there is no airflow available during the commissioning stage, lowering the airflow setpoint can allow checkout to continue. This 80% airflow requirement is looking at the on-board flow sensor of the Xenta 102-AX. If the flow value is coming from another controller on the network via the nviBoxFlow SNVT, the heat will be disabled. The nviBoxFlow input will override flow values for damper control, but heating outputs will ignore it. In this situation, setting the pressure offset (UCPToffsetPress) to 1” will bypass the limitation. This will be fixed in the Xenta 102-AX firmware v2.18. Wrap Up If everything is configured properly physically and in the 102-AX Plug-in, then the box should be stroking the valve to maintain the space temperature setpoint. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta 102-AX. If further assistance is required, or if you would like to add to steps suggested here, call or email Schneider Electric Product Support.