Building Automation Knowledge Base

Issue Copying the SHTTXT.REC file back onto a Sigma system into its correct location.. Environment Sigma server all version 4 releases. Cause Copying the SHTTXT.REC file into the incorrect location will prevent the short texts from being shown when an object is displayed. Resolution In the later versions of Sigma 4.0? there are two copies of the SHTTXT.REC file. The first SHTTXT.REC is located in the C:/Sigma/Data/Locality/English United_Kingdom (IF UK)/ folder and is used by Sigma. The second SHTTXT.REC file is located in the C:/Sigma/Data/ folder and is a copy used by SigmaX. When copying the SHTTXT.REC file back onto a Sigma system, it should be copied to both locations.

Issue What versions of Visio are required for WorkPlace Tech? Product Line TAC IA Series Environment WorkPlace Tech Microsoft Office Visio (32-bit version only on WPT versions 5.10 and earlier ) Microsoft Office Visio (64-bit version only on WPT versions 5.11 and later) Cause Software requirement - Microsoft Office Visio must be installed on the computer before beginning the installation of WorkPlace Tech. Resolution Below is a list of the WorkPlace Tech revisions and compatible Microsoft Visio versions.  The "Pro" versions are not required.  The "standard" versions of Microsoft Visio are typically recommended.  Only the 32-bit versions of Visio are supported in WPT 5.10 and earlier and only 64-bit versions are supported in WPT 5.11 and later. WPT Visio 3.1 Visio 5 Technical Plus 3.2 2000 SP1 4.0 2000 SP1, 2002 SP1 5.0 2002 SP1, 2003 SP1 5.1 2002 SP1, 2003 SP1 5.2 2002 SP2, 2003 SP1 or SP2 5.3 2002 SP2, 2003 SP1 or SP2 5.4 2002 SP2, 2003 SP1 or SP2 5.5 2002 SP2, 2003 SP1 or SP2 5.6 2002 SP2, 2003 SP1 or SP2 5.7 2003 SP3, 2007 SP1 5.8.0 to 5.8.5 ** 2003 SP3, 2007 SP1 or SP2, 2010 SP1 5.8.6 2007 SP1 or SP2, 2010 SP1 5.8.7 2007 SP3, 2010 SP2 5.9.1 to 5.9.4 2010 SP2, 2013 SP1, 2016 5.10.0 to 5.10.4 2016, 2019, 2021 Office (Visio) 365 Subscription Plans 5.11 2019 64-bit, 2021 64-bit, Office (Visio) 365 Subscription Plans 64-bit ** Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WorkPlace Tech 5.8.0 and 5.8.1, no known issues with 5.8.2 through 5.8.5)

Issue Some actuator datasheets do not specify the impedance of the 0-10V control signal, this is required to determine fan out from a controller. Product Line Field Devices Environment MB3 Range - MB3-24M, MB3-SO-24M, MB3-SC-24M MZ20 Range - MZ20A, MZ20A-R MVT56 Range Cause Information not defined on the specification sheet. Resolution MB3 Range 0-10V control signal input impedance = 200K Ohms. MZ20 and MVT56 Ranges 0-10V control signal input impedance = 32K Ohms.

Issue MNL-800 ramp object step change does not function if time value set greater than 164 seconds. Environment MNL-800 Cause The ramp object configured as "step change" incrementally increases or decreases the output at the level and rate defined by the step level and time values. The ramp will not perform the "step change" function if the time value setting is greater than 164 seconds. Resolution The workaround involves decreasing both the step level and time values by a common factor to obtain the overall result in the original timeframe required. For example, a step change of 1 every 1000 seconds can be performed with the same results if using a step change of 0.1 every 100 seconds.

Issue MNB controllers wired to the MSTP trunk of a MNB-1000 do not show up in the WorkPlace Commissioning Tool when connected via BACnet/IP. Environment MNB-1000 WorkPlace Commissioning Tool Cause Settings and configuration on the MNB-1000 and WorkPlace Commissioning Tool. Resolution Ensure that the MNB-1000’s MS/TP trunk is enabled. Ensure that the MNB-1000's MS/TP network number is entered.  Ensure that the Max Master count under the MSTP tab of the MNB-1000 is set with a number that is two more than the total number of controllers on the MSTP trunk. The MSTP addressing should have no gaps. Also, set the “Browse Settings” to Global. The setting is located under File > Connect > Advanced menu of the WorkPlace Commissioning Tool. When the browse setting is configured for local, not all devices on all BACnet networks will display.

Issue Are the Network 8000, DMS, and Signal manuals available in an electronic format? Environment Network 8000 DMS Signal Cause Option to view Network 8000, DMS, and Signal manuals in electronic format. Resolution The Network 8000, DMS, and Signal manuals are available from the Publication Zone via iPortal. They are, also, available on a CD. The "Legacy zip" link downloads and extract the files, if running the program from a computer or creating the CD. When running the program from a computer, launch "index.html" located in the extracted bin folder. Email legacy product documentation requests to be added to the Legacy CD, to Product Support.

Issue BACnet Programs Disable on a Reload This is an issue that will be addressed, but in the meantime an explanation of how this happens and a workaround is provided below. Environment Infinity Program in a Continuum Bacnet controller Cause How this happens: Create an Infinity Program in a Continuum Bacnet controller and then right click on the folder directory located under the controller you just created it under on the Infinity side. Now make sure there are two columns in the listview named State. You will most likely have to add one or both of these columns and make one of the columns source LIVE and the others source Database Notice when you run the listview both State columns will reflect Enabled for your running program. Now, perform a find new bacnet devices if you haven't already and then perform a send to database on the controller you just created the Infinity Program under. At this point go back and either run or refresh your listview we ran earlier and notice the Infinity Programs State attribute is set to disabled in the database view. At this point if you reload your controller in the Infinity side it will disable the program. Resolution Workaround on how to avoid this issue After a newly created program has been sent to the database on the Bacnet side, immediately run the listview we created earlier and Highlight either all or only the programs that are set to disable for the State attribute where the source is set to Database. Once you have selected the rows of the programs you want to set to enable, select the Edit menu item in the listview. Now select set attributes.. and in the drop down select State for the name and enter Enabled for the value and select OK. This will allow the program's to be reloaded without being disabled.  Most sites will never see this issue, since most will load up their controllers and back up the flash on the controller before performing a find new bacnet devices and send to DB on the bacnet side After controllers repower or reset the programs are just loaded back from flash. But the sites that reload their controllers will see the reload and programs disable issue. But like any reloading, you should always check your programs and alarms before leaving the site.

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 The new program interface does not match the previously defined program interface. (Subsystem: NS, #59) Product Line TAC Vista Environment LonMaker 3.1 LNS Version <3.2 Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 104-A Square D Altivar 61 Xenta 102-AX Cause The steps defined in this article only relate to the NS #59 error when it is received on an attempt to commission a controller in an LNS environment. It does not cover when this error is shown as a result of a download attempt in the TAC Vista System Plug-in. For information on the download error, see NS Errors #59, #64, #51 in a row on download attempt through System Plug-In. The new program interface does not match the previously defined program interface; i.e., the number of network variables, message tags, or the structure of self identification data is inconsistent even though the Program IDs match. This generally happens when a newer firmware of a controller is introduced that uses the same SNVT inputs and outputs as the old controller, and therefore shares a device template even though something below the surface may be different. Resolution The appropriate resolution to the NS, #59 error depends on the LNS version and type of controller that is failing to commission. Select from the categories below which best describes the situation. LNS Version <3.2 Check the existing Version of LNS. Open the Echelon® LonMaker™ Design Manager Right-click on the title bar of the Design Manager and select "About Echelon LonMaker..." In the About Echelon® LonMaker™ Design Manager Professional Edition window, look under Additional Information.   If the LNS Version is below 3.2, then upgrading the LNS to 3.2 or later (also referred to as LNS Turbo, not to be confused with LonMaker Turbo) may fix the error. The later LNS versions are less sensitive to program interfaces not matching. Navigate to Echelon Downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks. If you cannot install the LNS update, proceed to the following solutions organized by controller type. Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) You get this error when two controllers share a device template (XIF file) if one has a system program version (.MOT) below 3.5 and the other has a system program version above 3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and its own template. Open the application from the System Plug-in by right clicking on the controller and selecting Configure>Edit. To give the application a new XIF, either add a dummy SNVT or go to Device Configuration and uncheck the box for "XIF header generated according to LonMark standard." Go to Options>Simulate (F12), select Commands>Generate. Options>Edit (F12) and save the application to the hard drive by selecting File>Save as. In the System Plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and Vista Database. If you are asked to resynchronize, do so. Download Applications and Parameters. Commission in LonMaker. Another cause of the error for a Xenta programmable is if the system program version (.MOT) is newer than the version of Vista System Plug-In being used. For example, if visiting a 4.2.5 Vista site and attempting to add a much newer 3.8 firmware Xenta programmable. It will fail on attempts to commission. The firmware must be downgraded to a version that is compatible with the older Vista system. See Download an .MOT file into a Xenta Programmable controller for information on loading a different .MOT file. Xenta 104-A (follow steps below) If there are TAC Xenta 104-A v1.10 (or older) commissioned in an LNS database, it is not possible to add a TAC Xenta 104-A v1.20 or newer in the same database. Nor is it possible to do a replace. This is due to a change of size of the SNVT declaration area residing in the device memory. For the same Program ID, LNS requires this size to be identical as previously commissioned devices. Download NXE v1.20A from The Exchange Download Center. This is an NXE file which should be used to upgrade v1.20 to be able to coexist with v1.10. (It is not possible to upgrade 1.10 to 1.20/1.2A, due to memory configuration.) The download of v1.2A to the device is selected in the “New device wizard” in LonMaker. Check the “Load application image” and browse in the NXE as the image file. Note : The same process must be performed while dealing with the 104-A v1.21. In addition to the same issues above, v1.20A will not be compatible with v1.21. For more information on the Xenta 104-A firmware versions see Xenta 104-A firmware version compatibility. Square D Altivar 61 (choose an option below) Square D Altivar 61 drives have undergone a similar update of the firmware. Newer LON drives cannot reside concurrently on a network with older drives. A new NXE must be loaded into the newer drives so they can coexist with the older drives. This NXE file is on the Product Support SharePoint, or can be obtained by contacting Square D drive support directly at drive.products.support@schneider-electric.com. Xenta 102-AX Two Xenta 102-AXs, one that is hardware version 1, and one that is hardware version 2, cannot co-exist on the same LNS network. Whichever one is commissioned first will work fine, the second will result in an NS, #59 error.

Issue [Invalid Address] Product Line TAC Vista Environment Vista Workstation Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Invalidate Resolved Addresses Cause If you view a controller in Vista Workstation and point values read [Invalid Address] instead of showing values, there are a number of troubleshooting techniques to rectify this. Unfortunately, [Invalid Address] is a bit of a "catch-all" error code. Since it can be difficult to determine the cause of the error, these troubleshooting suggestions will have varying degrees of success. The best course of action is to try each of these methods in the order of least to most disruptive. As new techniques and procedures are discovered, they will be documented here. Resolution Check the label for N/P Designation If a programmable controller has read [Invalid Address] on every point since it was installed (it has never worked properly) then there is a chance that this is not a Network Presentation controller. These are referred to as stand-alone controllers and each of the 280 and 300 series have a non-network presentation variety. Check the label on the controller to make sure it says "302/N/P" or "282/N/P." If it just says "302" or "282" then this controller cannot communicate on a network and will never report values to a front end. Also see Xenta 280 or 300 Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. In the Vista Workstation Right-click on the controller and choose Advanced Operations > Invalidate Resolved Addresses Proceed? Select Yes. Right-click on the controller and choose Advanced Operations > Read Address Proceed? Select Yes. Wait up to about 30 seconds for the values to populate. Download the Controller In the System Plug-in, Download Applications and Parameters to the controller Recommission the controller In the System Plug-in, TAC Network > Commence Communication (skip to this step for LON controllers) You may want to follow this action with another attempt at the steps outlined in the section above "In the Vista Workstation" Repair or recommission the Routers in the NL220 or Lonmaker database repair or recommission the Routers. Re-Do Group Bindings & Commence Communication: In the System Plug-in, LNS network > Create Group Bindings In the System Pug-In right click on the TAC Network and commence communication Re-doing group bindings ensures that the LNS network interface, and LON to IP routers receive message can 0 for the main xenta address broadcast in the network. Monitor Sets If your monitor sets have become corrupted, then every controller you download from that point on will say [Invalid Address] on every point. Monitor sets are actually stored on the hard drive of the PC, not in the LNS database. If you have made backups and passed them back and forth between PCs, as you often do during the commissioning phase, this invites corruption of monitor sets. There were some known issues with monitor sets in LNS version 3.24 that have since been corrected in LNS version 3.26. This can be downloaded from Echelon's website in LNS Server/Turbo Edition Service Pack 7. Go to http://www.echelon.com Navigate to Support > Support Resources > Downloads Log in with a user name and password. If this is the first time logging in, register for a free user name and password. Search for software in the Recommended Downloads category Find LNS Server/Turbo Edition Service Pack 7 (this is the latest at the time of this article, a newer one may exist and should be downloaded) Prior to restoring a backup, you may want to resynchronize the drawing making sure to check the option for "Sync monitor sets between drawing and database." Usually restoring the last good backup will fix up the monitor sets. If you do not have a recent backup, there are a couple of procedures that may help resolve the corrupted monitor sets issue.   Note: Viewing and altering monitor sets is only available in Echelon LonMaker. There is no analogous menu item in Newron's NL220. Do not download any more controllers. Check your monitor sets in LonMaker by navigating to LonMaker > Network Service Devices Click on the NSS which should have the same name as the network Select the Monitor Sets button If you get "Monitor set cannot be found. (Subsystem: NS, #160)" then your monitor sets are corrupt. Close down Vista Server & LonMaker (if you don't you will get an error when you try to validate that says "The Network Interface, database directory, or NSS type, conflicts with the already active network. (Subsystem: NS, #149)") Navigate to Start > Programs > Echelon LNS Utilities > LNS Database Validator Navigate to the LNS Network to Validate Check the Repair Database checkbox Hit the Validate button If that does not find and repair the monitor sets, the following steps may help. Make backup of the LNS database. Start LonMaker. Do not start Vista Server. Go to the monitor sets (LonMaker > Network Service Devices > NSS > Monitor Sets) and right-click and delete the monitor sets Run the System Plug-in and create a brand new Vista database in a different location than your current database. Stop the Vista Server and start it again Check the monitor sets again, they should be right now Stop the server again and change back to your original Vista database Non-Latin Characters If you use a signal name or description in the XBuilder Device Editor with non-Latin characters (like Swedish åäöÅÄÖ) you will get [Invalid Address] when you view the signal in Vista. Value pages are displayed correctly. Do not use non-Latin characters for signal name or description. This issue has been confirmed in versions 5.1.2 - 5.1.4, and will be fixed in a future release. Classic Networks View the Address Tab under the controller's properties in Vista Workstation Check Address Table slots 0 and 1. If the "Domain Index" and "Member or Node" have been manually altered, set them back to 0. An applicationless controller will display [Invalid Address] in a classic network, whereas in an LNS network, it would simply fail to commission due to its applicationless state.  Direct download the controller through the Menta serial cable to see if it resolves the error. Xenta 700 Menta values See Xenta 700 Menta Object Values report [Invalid Address] in Workstation, Read operation failed. Delete, Destroy, Redo This is your last resort. If you have tried everything else possible, it is time to remove this controller from the database and start from scratch. The exact steps and methodologies may change based on your network and controllers, but basically you need to remove any mention of this controller and add it back in as though it were a brand new device. Decommission the controller Delete the device Delete the device template In the System Plug-in, remove the device from the TAC Network Update the Vista Database Create a new controller Browse in a Menta file Update Vista and download

Issue During a Vista 5.x.x installation, failure can occur during the SQL installation portion of the install. This solution could encompass many different SQL installation errors; however, one that is known and verified is shown below: Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) Here is another common one:   Failed to create or configure database in SQL Server ([1802] CREATE DATABASE failed. Some file names listed could not be created. Check related errors.) If you have previously uninstalled Microsoft SQL Server, data files for the database may still exist in the SQL Server data directory. Remove the files manually and click Retry or click Cancel to abort installation. Product Line TAC Vista Environment TAC Vista Server 5.x.x Cause Uninstalling and reinstalling the software can leave pieces of SQL behind. Even if you try to uninstall everything in Add/Remove Programs, left over portions may cause the TAC Vista installation not to be successfully installed. The Program Files\SQL Server directory is flagged for compression or encryption. Installing Vista version below 5.1.5 on a Windows 7 64bit machine will cause this error. Resolution Please check the Windows Event log for the specific installation error. See Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes for information on viewing the Windows Event Log. Consult Log file of SQL installation when installing Vista Server for information on viewing the SQL Server installation log. If the Event log reveals Error 28001, the sa password must meet SQL Server password policy requirements, please refer to the solution provided in Error 28001 - sa password complexity error when installing TAC Vista 5. If not, then please proceed with the resolution below: If the SQL Server installation log file complains that the Program Files\SQL Server\ directory is flagged for encryption or compression then right click on the directory and select properties. The advanced option exposes the check boxes for compression and encryption. If the folder is flagged for compression the it will be visible in blue instead of black font. Remove the encryption or compression flags and apply then reinstall. If the PC operating system is Windows 7 64-bit, install Vista 5.1.5 or higher. Resolution below will not solve the issue. In most cases this is caused by MSXML 6.0 parser. This software is commonly installed by programs using SQL, and also during the TAC Vista installation. If this can't be removed using Add/Remove Programs, you can download a program from Microsoft that cleans up and removes this software (and others). It is called Windows Installer Cleanup. Link to download: msicuu2.exe. NOTE: Microsoft recently removed this utility from the downloads section of their support site. They have this to say about the utility: While the Windows Installer Cleanup utility resolved some installation problems, it sometimes damaged other components installed on the computer. Because of this, the tool has been removed from the Microsoft Download Center. Use this utility with care at your own risk.   In most cases TAC Vista will install successfully after removing MSXML 6.0 parser. For alternative solutions see SQL Express install fails on MSXML 6 and Error when installing SQL 2005 Express on a machine that had previously had MSDE installed .

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.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

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 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 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 Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Troubleshooting LON Network communications. Product Line EcoStruxure Building Operation, TAC Vista, TAC IA Series Environment Xenta Controllers MNL I/A Controllers EcoStruxure Building Operation AS-P LPA Protocol Analyzer Cause Intermittent communication failures, high bandwidth, error packages, noise on the line -- these can be difficult to pin down and identify. Resolution These two documents attached produced by Loytec are invaluable resources in troubleshooting a LON network.  The first deals with common causes of noise on LON Wires.  The second details what to do once you've procured an LPA protocol analyzer -- how to use it and interpret data.   For a Vista system, also see Actions for reducing Bandwidth in a Vista network. For an EcoStruxure Building Operation system, also see Bandwidth Throttling.    If an LPA protocol analyzer is not available there is also an option to log the Lon communication to and from the ES, AS-P, or AS-B. To do that you change the debug level from "Information" to "Trace" for: /Automation Server/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon/nsp.pin.lon.comm After the investigation make sure to set the debug level back to "Information" again. For debugging assistance a Tool called SBO Lon Decoder can be used.

Issue Sigma parallel port dongle or USB dongle upgrade to software license Product Line Satchwell Sigma Environment Sigma version 4.08 Cause It is difficult to purchase computers with parallel ports. With the use of virtual computer operating systems, USB ports may not be available either. ∴ A different type of Sigma licensing will be required. Resolution Please note: EBO 3.x has now entered into its limited support period with Sigma support coming to an end, this free of charge service, provided by PSS in good faith, will no longer be available from the 1st May 2024. Any remaining Sigma systems will need to continue to use their current licensing method or be upgraded to EBO.   Product Support can arrange for an upgrade from your existing parallel port or USB type Sigma dongle to a Building Operation software license entitlement for Sigma 4.0.8. Sites running Sigma software 4.07 or older where support for software licensing isn't available need to be upgraded to Sigma version 4.08.57 or later to use the software option. Sigma Software license type availability is documented on page 8 in the Sigma 4.08 release note.   For engineers using Sigma 4.08: The Building Operation Evaluation License, available from the Schneider Electric Download Center, will unlock the Sigma 4.08 for testing etc for the period of the Evaluation License (maximum 3 months or until the expiry of the downloaded license).   Unlock Sigma software using the Building Operation Evaluation License. To install the software licensing option for Evaluation License: - Stop the Sigma server service. Install Building Operation License Administrator. Add Evaluation License file to the Building Operation License Server. Start the Sigma server service. Sigma should now be licensed. For customer sites using Sigma 4.08: To reduce the Sigma system downtime, Install the Building Operation License Server version 1.6 or later. (it is recommended that the latest available version of the Building Operation License Server compatible with the computer's operating system is used). Dongle Upgrade Procedure: Download the Sigma Dongle Replacement - Required Data 2020 form. Complete the cells that are highlighted/filled in blue. Open a case with your local support team.. Supply the completed spreadsheet. The Product Support representative that is assisting you with your license upgrade, will contact you and provide the address and details where to send the site's Sigma dongle. Once the dongle has been received a software license will be ordered and then the software license entitlement for Sigma will be sent to you. If the site is a standalone Sigma site, Product Support will need to get approval from the regional category manager before escalating for the software license.   To install the software licensing option for Sigma 4.08: - Stop the Sigma server service. Install Building Operation License Administrator. Add the entitlement to the Building Operation License Server. Start the Sigma server service. Sigma should now be licensed.   Note: If your current Sigma dongle contains Remote Alarm Manager licensing, Remote Alarm Manager does not support the Building Operation license server option. The USB dongle can still be used or a TAC license server type license can be used instead of the dongle.

Issue Directions on how to commission an SSC and Mercury Controllers right out of the box. Product Line Access Expert Environment Windows 7 Windows 8 Windows Server 2012 Windows Server 2014 Version 2 Version 3 Cause No directions on setting up an SSC and Mercury Controllers to get it online. Resolution Commissioning the AX-SSC Here is a link to a video that describes how this should be done as well that can be accessed from the following link: Commissioning a new SSC 1. Connect the Access Expert Device Administrator to the SSC using USB cable then go to ‘Network settings’ to configure the device’s IP address etc. 2. In the ‘Ethernet 1 Configuration’ tab, configure the IP settings (In this example, we are using a static IP address). Make sure to configure the DNS so that the URL of your hosted instance can be resolved. Take note of the SSC’s MAC address which will have to be entered when adding the SSC in Access Expert. 3. Enable the default user in the SSC in order to be able to login with a web browser to configure additional communication parameters. NOTE: The default user will stay enabled for 5 minutes then the checkbox will automatically deselect. Once logged into the SSC you can create a new level 1 user so you don’t have to rely on the default user again. 4. Point a web browser to the SSC's IP address and login using the default user (admin/password). After logon, verify the IP settings configured from the Device Administrator, you can edit the settings here if necessary. 5. If using a Mercury EP1501 or EP1502 Controller, use the MAC address and connect to the device. Once logged in, go on to the next step 6. Go to the ‘Host Comm’ page. This is where you will configure the SSC to be able to communicate to the Access Expert database instance in the cloud. 7. Configure the connection type for ‘IP Client’. Enter the URL for your DB server instance or the hosted cloud server as shown in the above example. 8. For V3, the Host Name would be us.accessxpert.com (ax.accessxpert.com also works). If premise, then it would be the IP of the Server. 9. Note the port number used for communications and make sure this port is open; you can also configure an alternate host port as a backup. 10. Usually it is 3001, if that is blocked by the clients Network, then use Port 443. 11. Click Accept then ‘Apply Settings’ followed by ‘Apply Settings Reboot’.