Sign In Help
Schneider Electric
HelpLogin / Register

Invite a Co-worker

Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel

Invitation Sent

Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
  • Home
  • Communities
  • :
  • Knowledge Center
  • :
  • Building Automation Knowledge Base
Community Menu
  • Forums
    • By Topic
        • EcoStruxure Building
          • Field Devices Forum
        • EcoStruxure Power & Grid
          • Metering & Power Quality
        • EcoStruxure IT
          • EcoStruxure IT forum
        • Industrial Automation
          • Industry Automation and Control Forum
          • Alliance System Integrators Forum
          • Machine Solutions in the Digital Transformation
          • EcoStruxure Automation Expert / IEC 61499 Forum
          • Industrial Edge Computing Forum
          • Level and Pressure Instrumentation Forum
          • Modicon User Group
          • PLC Club Indonesia
          • SEE Automation Club Forum
          • Fabrika ve Makina Otomasyonu Çözümleri
          • Форум по промышленной автоматизации СНГ
          • Motorabgangstechnik & Antriebstechnik Forum
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Forum
          • SCADA and Telemetry Devices Forum
        • Power Distribution IEC
          • Power Distribution and Digital
          • Power Standards & Regulations
          • Solutions for Motor Management
          • Paneelbouw & Energie Distributie
          • Eldistribution & Fastighetsautomation
          • Elektrik Tasarım Dağıtım ve Uygulama Çözümleri
        • Power Distribution NEMA
          • US Utility Forum
        • Power Distribution Softwares
          • EcoStruxure Power Design Forum
          • LayoutFAST User Group Forum
        • Wireless Information Network Solutions
          • Instrument Area Network
          • Remote Monitoring
          • Tank Level Monitoring
          • Remote Data Collection
        • Solutions for your Business
          • Solutions for Food & Beverage Forum
          • Solutions for Healthcare Forum
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Forum
        • Healthcare
          • Solutions for Healthcare Forum
      • EcoStruxure Building
        • Field Devices Forum
      • EcoStruxure Power & Grid
        • Metering & Power Quality
      • EcoStruxure IT
        • EcoStruxure IT forum
      • Industrial Automation
        • Industry Automation and Control Forum
        • Alliance System Integrators Forum
        • Machine Solutions in the Digital Transformation
        • EcoStruxure Automation Expert / IEC 61499 Forum
        • Industrial Edge Computing Forum
        • Level and Pressure Instrumentation Forum
        • Modicon User Group
        • PLC Club Indonesia
        • SEE Automation Club Forum
        • Fabrika ve Makina Otomasyonu Çözümleri
        • Форум по промышленной автоматизации СНГ
        • Motorabgangstechnik & Antriebstechnik Forum
      • SCADA & Telemetry Solutions
        • Geo SCADA Expert Forum
        • SCADA and Telemetry Devices Forum
      • Power Distribution IEC
        • Power Distribution and Digital
        • Power Standards & Regulations
        • Solutions for Motor Management
        • Paneelbouw & Energie Distributie
        • Eldistribution & Fastighetsautomation
        • Elektrik Tasarım Dağıtım ve Uygulama Çözümleri
      • Power Distribution NEMA
        • US Utility Forum
      • Power Distribution Softwares
        • EcoStruxure Power Design Forum
        • LayoutFAST User Group Forum
      • Wireless Information Network Solutions
        • Instrument Area Network
        • Remote Monitoring
        • Tank Level Monitoring
        • Remote Data Collection
      • Solutions for your Business
        • Solutions for Food & Beverage Forum
        • Solutions for Healthcare Forum
      • Food & Beverage
        • Solutions for Food & Beverage Forum
      • Healthcare
        • Solutions for Healthcare Forum
  • Blogs
    • By Topic
        • EcoStruxure Power & Grid
          • Backstage Access Resources
        • Industrial Automation
          • Industry 4.0 Blog
          • Industrie du Futur France
        • SCADA & Telemetry Solutions
          • SCADA and Telemetry Blog
        • Power Distribution IEC
          • Power Events & Webinars
          • Power Foundations Blog
          • UK&I Residential and Commercial Electrical Distribution
        • Power Distribution NEMA
          • NEMA Power Foundations Blog
        • Power Distribution Softwares
          • EcoStruxure Power Design Blog
        • Solutions for your Business
          • Solutions for Food & Beverage Blog
          • Solutions for Healthcare Blog
          • Solutions for Retail Blog
          • Solutions for eMobility
          • Digital Hospital Solutions – UK&I
        • Knowledge Center
          • Industrial Automation How-to videos
          • Digital E-books
          • Success Stories Corner
        • Community experts & publishers
          • Publishers Community
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Blog
        • Healthcare
          • Solutions for Healthcare Blog
        • Retail
          • Solutions for Retail Blog
        • Retail
          • Solutions for eMobility
        • Retail
          • Digital Hospital Solutions – UK&I
      • EcoStruxure Power & Grid
        • Backstage Access Resources
      • Industrial Automation
        • Industry 4.0 Blog
        • Industrie du Futur France
      • SCADA & Telemetry Solutions
        • SCADA and Telemetry Blog
      • Power Distribution IEC
        • Power Events & Webinars
        • Power Foundations Blog
        • UK&I Residential and Commercial Electrical Distribution
      • Power Distribution NEMA
        • NEMA Power Foundations Blog
      • Power Distribution Softwares
        • EcoStruxure Power Design Blog
      • Solutions for your Business
        • Solutions for Food & Beverage Blog
        • Solutions for Healthcare Blog
        • Solutions for Retail Blog
        • Solutions for eMobility
        • Digital Hospital Solutions – UK&I
      • Knowledge Center
        • Industrial Automation How-to videos
        • Digital E-books
        • Success Stories Corner
      • Community experts & publishers
        • Publishers Community
      • Food & Beverage
        • Solutions for Food & Beverage Blog
      • Healthcare
        • Solutions for Healthcare Blog
      • Retail
        • Solutions for Retail Blog
      • Retail
        • Solutions for eMobility
      • Retail
        • Digital Hospital Solutions – UK&I
  • Ideas
        • Industrial Automation
          • Modicon Ideas & new features
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Ideas
          • SCADA and Telemetry Devices Ideas
  • Knowledge Center
    • Building Automation Knowledge Base
    • Industrial Automation Knowledge Base
    • Industrial Automation How-to videos
    • SCADA & Telemetry Solutions Knowledge Base
    • Digital E-books
    • Success Stories Corner
    • Power Talks
  • Events & Webinars
    • Innovation Talks
    • Innovation Summit
    • Let's Exchange Series
    • Technology Partners
  • Support
    • Ask Exchange
    • Leaderboard
    • Our Community Guidelines
    • Community User Guide
    • How-To & Best Practices
    • More
Join Now
How can we help?
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
52690members
Join Now
247923posts
Join Now

Building Automation Knowledge Base

Access this self-service resource 24/7 and post your questions or scroll through forums for answers on building automation.

Subscribe
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 100
  • Next »
9542 posts
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 100
  • Next »
Sort by:
Likes
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Subscribe to RSS Feed
  • Invite a Friend
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 100
  • Next »

Supplemental Documentation on the Menta/Function Block PID blocks

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.
View full article
Picard Product_Support
‎2018-09-07 03:05 AM

Last Updated: Administrator DavidFisher Administrator ‎2021-01-11 10:30 AM

Labels:
  • EcoStruxure Building Operation
  • TAC Vista
6592 Views

Unable to upgrade AS-P to 3.2.x using USB

Issue AS-B/P is unable to upgrade to EcoStruxure Building Operation 3.2.x from out-of-the-box or DFU mode. When checking the upgrade file you receive the following error: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In 3.2.1, the change was made to use IP-over-USB as a way to communicate faster through the USB. Due to this, IPv4 and IPv6 need to be enabled on the connected device running Device Administrator. Resolution Check to make sure IPv6 is enabled on your machine. Open a Command Prompt window and run the "route print -6" command If it only shows two IPv6 addresses then IPv6 is disabled and you will need to enable it To enable IPv6 Open Registry Editor on your Windows Machine Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Double-click on  DisabledComponents to edit Change value from "FF" (IPv6 disabled) to "00" (IPv6 enabled) Note: The Disabled Components registry value does not affect the state of the check box. Therefore, even if the Disabled Components registry key is set to disable IPv6, the check box in the Networking tab for each interface can still be checked. This is the expected behavior. Note: You must restart your computer for these changes to take effect.  
View full article
Commander JonGreen Commander
‎2020-11-24 09:31 AM

Last Updated: Janeway RobertAndriolo Janeway 4 weeks ago

Labels:
  • EcoStruxure Building Operation
868 Views

Modbus IP Multiple Queries and Multiple Query Packets (Async) explanation

Issue Details on how Modbus IP Multiple Queries and Multiple Query Packets work Product Line EcoStruxure Building Operation. Environment Building Operation SmartX Servers Modbus IP Cause Understanding of how the Modbus synchronous and asynchronous transport layers differ. Resolution By default, the Multiple queries is Disabled, this is the synchronous transport layer. To enable the asynchronous transport layer the Multiple queries must be Enabled within the Modbus TCP Network properties as shown below. Setting to "Enabled" allows multiple queries (packets) to be sent to multiple Modbus devices, thus reducing wait times.  It also enables further settings in the Modbus Device properties "Maximum concurrent queries" and "Multi-query packets".   The maximum concurrent queries and multiple-query packets as shown below are configurations for the Modbus asynchronous transport layer. The Maximum concurrent queries setting is only enabled if the "Multiple queries" is enabled in the Network Properties. When enabled, this allows the "concurrent queries" to be sent as a single packet.     Modbus Synchronous Transport Layer Each Modbus query is sent out one after the other. Before sending out the next query the transport layer waits for a specified period for the previous query. Example Poll Sequence Device No. Objects 1 2 2 1 D=Device, Q=Query, R=Reply D1 Q1 Send D1 R1 Receive  D2 Q1 Send D2 R1 Receive  D1 Q2 Send D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 3 seconds. Modbus Asynchronous Transport Layer With the asynchronous transport layer enabled, the queries are transmitted to multiple devices at the same time. The maximum number of queries that are transmitted to that one device is controlled by the “Maximum concurrent queries” setting. The “Multiple-query packet” specifies whether the queries are transmitted in one TCP frame or not. Simple Example Poll Sequence Device No. Objects Maximum concurrent queries Multiple-query packet 1 2 False 1 2 1 False 1 D=Device, Q=Query, R=Reply D1 Q1 Send D2 Q1 Send D1 Q2 Send D1 R1 Receive  D2 R1 Receive  D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 1 second Complex Example Poll Sequence Device No. Objects Maximum concurrent queries Multiple-query packet 1 10 True 5 2 4 False 2 D=Device, Q=Query, R=Reply D1 Q1, Q2, Q3, Q4, Q5 Send D2 Q1 Send D2 Q2 Send D1 R1, R2, R3, R4, R5 Receive  D2 R1 Receive  D2 R2 Receive  D1 Q6, Q7, Q8, Q9, Q10 Send D2 Q3 Send D2 Q4 Send D1 R6, R7, R8, R9, R10 Receive  D2 R1 Receive  D2 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 2 seconds   NOTES The use of this feature should be avoided before EBO v3.1 Some Modbus devices do not support multiple queries or multiple query packets, so the feature should be tested on an individual basis. (Some devices may even go offline until manually reset) This feature will increase the CPU usage on the EBO server. It should be avoided on EBO Servers that are already heavily loaded
View full article
Janeway RobertAndriolo Janeway
‎2020-11-11 03:47 AM

on ‎2020-11-11 03:47 AM

Labels:
  • EcoStruxure Building Operation
249 Views

Energy Expert Compatibility Matrix

Issue There is a need for a single Compatibility Matrix that shows EBO, PME, Energy Expert and relevant software versions all in the same location. Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert  Power Manager for SmartStruxure ETL tool Cause Energy Expert version compatibility information is currently available but is stored in many different places such as release notes and online documentation, rather than one single matrix. Resolution The full ETL for EBO compatibility matrix is shown in the following table. Energy Expert  PME EBO ETL Integration Utility .NET Framework Power Manager 1.0 7.2 .3 1.6.1 3 1.0.14304.2 4.5 Power Manager 1.1 8 1.6, 1.7.1 4.1 1.0.15306.1 4.5 Power Manager 1.2 8.1 1.6.1  1.7.1, 1.8.1 4.3 2.1.16081.1 4.6 Power Manager 1.3 8.2 1.8.1,  1.9.X,  4.6 2.2.17056.2 4.6 Energy expert 2.0 9 2 5 3.0.18215.3 4.6 Energy expert 3.0 2020 3.0,3.1,3.2 6 3.1.19319.1 4.6   Great care must be taken when choosing the correct version of ETL to use when integrating Energy Expert and EBO, as there are actually two families of ETL in production.  One ETL designed and tested for PME use only and ETL for EBO designed and tested with an EBO Extract Task specifically for integrating the two systems. (For example, a version of ETL 4.7 exists, but this is not ETL for EBO and therefore does NOT contain an EBO Extract Task, even though it is a valid version of ETL for the Power Community)
View full article
Lieutenant JG Robert_Davis Lieutenant JG
‎2020-12-29 10:10 AM

on ‎2020-12-29 10:10 AM

Labels:
  • EcoStruxure Building Operation
1206 Views

Workstation error when logging into a remote Enterprise Server 'No valid client license available. (Error -5: No such feature exists.)'

Issue Workstation error when logging into a remote Enterprise Server. Enterprise Server has available client licenses. 'No valid client license available. (Error -5: No such feature exists.)' Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation  EcoStruxure Building Operation License Administrator Cause Workstation is trying to check out a license from the local computer. The License Server is on the Enterprise Server computer and the Enterprise Server license has been activated on the Enterprise Server computer.  Resolution On the Workstation computer, run the License Administrator and change the License server address from the default '@localhost' to the IP address of the Enterprise Server. Refer to License Server Address on Web Help. License server address default: Change to License Server IP address (example below):
View full article
Admiral RyanSuar Admiral
‎2019-09-16 08:38 AM

on ‎2019-09-16 08:38 AM

Labels:
  • EcoStruxure Building Operation
1546 Views

Extended Elevator control (Step by step instructions)

Issue Extended Elevator control (Step by step instructions) Product Line TAC INET Environment I/NET Seven DPU Firmware 3.20 or above. (DPU7920 with 48k MIP or SCU1284) Cause Extended elevator control allows support up to 79 floors and easier programming methodology than the traditional method.  This has been added to I/NET Seven software and DPUs as detailed in the environment.  Resolution To use any of these features requires that the DPU be a 7920 w/ MIP board or the new SCU1284. 7910 and 7920 w/o MIP board will still work with the I/Net system but they cannot use these functions. The host prevents the download of these features to any DPU revision prior to 3.10.   Extended Elevator Control Setup Example This is based impart on basic prior knowledge of InetSeven Host software setup and configuration to include but not limited to Controller Station Parameters, Resident I/O, Point Extensions, Operations of Network Configuration, and Access Configurations (Doors, Tenants, Groups, Individuals and Personnel Schedules). Hardware required: DPU 7920 48k (The following control will only apply to the 7920 48k) Please follow these steps to configure extended elevator control. Resident I/O Editor Edit / Controller / Resident I/O – Add the following Internal DO Door Reader point Internal DI point for each Floor DO External DO point for each Floor button DI Note – Save Door in the Network Configuration editor. Controller Door Editor Edit / Controller / Door Editor Select Door to add Elevator Control Modify – check Elevator Control box Select “Message type” Alarm / Transaction Note – Ensure a Schedule (s) has been assigned to the Door reader point. Controller Elevator Parameter Edit / Controller / Elevator Add Elevator Extension to reader point. Add Floor parameters. Complete the following; Floor Index Selection Floor designation Button Enable (DO) Button Selection (DI) Note – When finished “STOP” Do not select floors, Select OK and Close. Network Configuration  Edit / Host Computer / Network Configuration. Penetrate down to the DPU (Door Read Point) with Elevator Control Penetrate one more level and SAVE all your floor extensions. Tenants Access / Tenants Select Tenant Locate Door Reader point – Remove “X” (Unselect). Place an “X” next to all floors that tenant will have access to – Select Ok At this time I would suggest performing a save function followed by an SLI and DPU restore. Individual Editor You are now ready to add individuals or assign individuals access to floors.
View full article
Picard Product_Support
‎2018-09-07 01:13 AM

Labels:
  • TAC INET
768 Views

Recovery of XBuilder project if no copy is saved and backup was not sent to target

Issue If there is no saved copy of an XBuilder project and the backup was not sent to target it may still be possible to recover some of the data to be able to reconstruct the project Product Line TAC INET, TAC Vista Environment Xenta 5xx / 7xx / 9xx Cause Lost XBuilder project and backup was not sent to target Resolution With XBuilder 1.5.0 or later connect to the Xenta controller through the web interface and use the Utilities > Project Tree to view the project information. Use this information as a blueprint to rebuild the XBuilder project. If an older version of XBuilder was used then can connect to the Xenta Server with FTP. The OGC graphic files as well as the CFG files which configure the linking of points and signals can be obtained through the FTP. These files can then be imported into a new XBuilder project which can be sent to the Xenta Server.
View full article
Picard Product_Support
‎2018-09-06 03:05 PM

Last Updated: Administrator DavidFisher Administrator ‎2019-05-28 06:43 AM

Labels:
  • TAC INET
  • TAC Vista
552 Views

What versions of Visio are required for WorkPlace Tech?

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) 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. 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 SP 2 , 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 2016, 2019, Office (Visio) 365 Subscription Plans ** 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)
View full article
Picard Product_Support
‎2020-12-15 09:38 AM

on ‎2020-12-15 09:38 AM

Labels:
  • TAC IA Series
2287 Views

Epibuilder Dynamic Text fields not displaying in a badge layout, error encountered while trying to update custom attributes or Error Opening EpiDesigner Configuration Database

Issue Epibuilder Dynamic Text fields are not displaying in a badge layout or Errors related to EpiBuilder or EPIDesigner Product Line Andover Continuum Environment EpiBuilder Badge Layout Cyberstation Cause Install didn't make the connection properly or badging wasn't enabled during the initial Continuum installation or Windows permission restrictions  Resolution From Make Edit badge in Continuum, Open Badge layout in EpiBuilder (If you have a problem opening Badge Layout see Note #2 below) View Options> Data Fields Select Use the data fields defined in a database If nothing is there, click the Other Database button Select Use an ODBC database Select the Data Source button Select System DSN tab and then select EPISDK then OK Click the Select button add the path to SDKNoDB.mdb (C:\Program Files\Continuum\EpiBuilder\Data) Click Open, Click OK All fields should now be available or the error should no longer happen on startup If receiving: ** Error Opening EpiDesigner Configuration Database error when selecting MakeEdit Badge,    Note #1: Permissions can affect the configuration of the Data Sources. If some options aren't configurable or have been changed from the default like buffers are not set to 2047 then try the configuration with increased permissions. Start>run odbc32.exe and check that the System DSN had EPISDK, If not, add it and then follow the instructions able to set the SDKNoDB.mdb  If the site is utilizing hard drive encryption on the hard drive.  Move the sdknodb.mdb to an unencrypted network share to correct the errors after updating the episdk datasource.  Note #2:  If you cannot perform step #1 from above check the following: On a 32 bit system run the following command from either the run window:  odbcad32.exe and check that the User DSN has an EPISDK entry with the datasource set to SDKNoDB.mdb .  The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\ On a 64 bit system run the following command from either the run/search window:  C:\Windows\SysWOW64\odbc32.exe and check that the User DSN has an EPISDK  entry with the datasource set to SDKNoDB.mdb . The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\
View full article
Picard Product_Support
‎2018-09-07 03:20 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-19 07:09 AM

Labels:
  • Andover Continuum
1021 Views

Setting up an SSC (System Security Controller), EP1501 and EP1502 Mercury Controllers

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’.  
View full article
Picard Product_Support
‎2018-09-10 10:46 AM

Labels:
  • EcoStruxure Access Expert
2489 Views

Change CX level controllers message count to improve I2 communications

Issue How to change the CX level controllers message count to improve I2 Infinet communications. Throttling adjustments using accinfoframe1 and accinfoframe2. Product Line Andover Continuum Environment accinfoframe, accinfoframes, acc info frame Continuum Cyberstation CX 9680 Infinet I2 bus Cause Improve I2 communications on the infinet bus. Changing the CX level controller's message count on the Infinet bus to improve alarm delivery and exported data times when heavy polling is occurring. Resolution TPA-BOST-00-0004.00 describes several fixes, including one that improves field bus with heavy traffic. One of the fixes speeds up graphics and field bus reloads. With the latest version of the firmware the ability to throttle the number of messages during token passing has been added. This will allow a variable to adjust an Infinet bus based on the amount of traffic a particular bus is experiencing. With the latest firmware versions 2.100028, 2.000030 for the Netcontroller 9680 there are variables that can be used to adjust the number of messages per token pass. This is very similar to the MaxInfoFrames setting on Bacnet the devices; we'll call them “accinfoframe” for this document and examples. The value can be adjusted for values of 1-128. Since the TPA was issued, the value is defaulted to 128 and if no accinfoframe variable is created the default value is 128. In order to have the ability to adjust the number of messages in the supported controllers, an infinity numeric needs to be created in the CX/BCX. The name of the variable has to be correctly spelled but is case insensitive. The names are accinfoframe1 and accinfoframe2. Accinfoframe1 will be the setting for comm1 one and accinfoframe2 will control the setting for comm2. When configuring accinfoframe1 or accinfoframe2, make sure to select the SetPoint and back up the flash on your controller, so that you retain the settings in case of power failure. Example of when to use throttling: There will be instances where the accinfoframe variables will need to be throttled. For instance, lets theorize a site “ChillerPlant” and the ChillerPlantCX(9680) has 100 infinet controllers located on Comm1. In our scenario we have 3 workstations each running a graphic polling 2 points(200 points) from each Infinet controller and we are running listviews of infinitynumerics on 8 of the Infinets controllers or perhaps hundreds of points that are being collected for extended logging. As one might think, communications would begin to slow down when polling for values on approx 600 points not to mention the point to point communications of the listviews and extended logs. With all of this traffic, the CX will dominate the network token. Since it can do 128 messages when it receives the token and it receives the token between every Infinet, the token round time can go into minutes. This means that the Infinet controllers can take minutes to deliver alarms and exported data. Another potential scenario is if one selected 4 Infinet controllers to reload, the bus may very well be overloaded at this time and may be receiving errors on the reloads in the distribution window. One of the error messages that could be expected is “Unable to reload object CarlNet\My_9680\My_I2_814\Num_1. An invalid response was received from a remote service request.” In this example we could create a infinity numeric on the CX named accinfoframe1(for Comm1) and start to reduce the number of messages CX would generate before passing the token. On the other extreme, if the ACCInfoFrame setting is set too low, such as to 1 as in the earlier versions of Netcontroller II firmware, this extreme traffic could cause such issues as extreme slowness of graphics and listview updates, Extended logging not being capable of retrieving the required data at the required intervals, and possibly the Infinet controllers randomly appearing to be offline to the system. In the example above the question is “What value should the accinfoframe1 be set to?” The answer entirely depends on how much traffic is on the Infinet bus. How many extended logs, how many listviews, how many graphics, alarms and Plain English programs are creating traffic on the bus? The quick way out here would be set the accinfoframe1 to a value of 1. We know for a fact that this would slow the bus down, and you might want to increase the number to 5. As mentioned this is all dependent on the amount of traffic on the Infinet bus. Or we could take a more in depth approach and find out what the token round time is on the bus and adjust our accinfoframe1 based on token round time. We could create the following points. TOKEN ROUND TIMER PROGRAM InfinityNumeric MaxTokenItem InfinityNumeric MaxTokenRound InfinityNumeric TokenRoundTime Logsize:100 Logtype: LogMaximum InfinityProgram TokenRoundCalc InfinityDateTime LastDateExport Program code: Initialise: LastDateExport = PointMapsTests\Infinity2\i2_851\Date Goto DoTokenRoundCalc DoTokenRoundCalc: If LastDateExport <> PointMapsTests\Infinity2\i2_851\Date then TokenRoundTime = (PointMapsTests\Infinity2\i2_851\Date - LastDateExport) – 1 LastDateExport = PointMapsTests\Infinity2\i2_851\Date Endif MaxTokenRound = maximum(TokenRoundTime) MaxTokenItem = maxitem(TokenRoundTime) E: If TS >= 5 then Goto Initialise The program and points above created in the CX will allow the token round time to be captured and one could essentially get very creative and change the accinfoframe value dynamically through Plain English programming. For these examples we just want to find out the token round time and manually adjust the accinfoframe1 variable to avoid any reload errors. The TokenRoundTime, MaxTokenRound and MaxTokenItem numerics can be added to a watch window or a graphic to visually monitor the TokenRoundTime. If you see that your TokenRoundTime is 5, 10 15 seconds, this is an indication you need to reduce the accinfoframe1 value. As a rule of thumb a TokenRoundTime of less then 2 seconds is acceptable, while keeping the TokenRoundTime below 0.7 seconds is ideal.
View full article
Picard Product_Support
‎2018-09-07 05:18 AM

Last Updated: Administrator DavidFisher Administrator ‎2019-07-09 09:00 AM

Labels:
  • Andover Continuum
1400 Views

License activation stops at 80% or License Administrator crash

Issue Two related issues are covered in this article While attempting to activate a customer or demo license, the activation process stops at around 80%. When clicking the "Diagnostics" tab in the License Administrator it crashes with a "System.DllNotFoundException" error. System.DllNotFoundException: Unable to load DLL (Tac.Nsp.Archive.Licensing.Client.dll) Product Line EcoStruxure Building Operation Environment First detected in Windows 10 First detected with Microsoft Visual C++ Redistributable 2012 (VC++ 2012) License Administrator Cause There can be two reasons why this happens If the activation process stops at around 80%, but the License Administrator does not crash when the "Diagnostics" tab is selected, the license system needs to be completely reset. If the activation process stops at around 80%, and the License Administrator crashes when the "Diagnostics" tab is selected, Microsoft Visual C++ components need to be repaired. Refer to solutions below depending on the issue detected. Resolution Solution 1: Resetting the license system The process to reset the license server system is covered in WebHelp article 6003. In some cases, a deeper reset can be required. For that, a tool called "SBO License Server Reset" can be downloaded from the Community. Solution 2: Repairing Microsoft Visual C++ components Method 1 In Control Panel, click Uninstall a program in the Programs group. In the programs list, locate Microsoft Visual C++ 2012 Redistributable (X64) - 11.0.61030 or Microsoft Visual C++ 2012 Redistributable (X86) - 11.0.61030, depending on your system architecture. Right-click the entry name, and then click Change. In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this. Method 2 Run the Modify Setup repair functionality for Microsoft Visual C++ Redistributable by starting the installer. VC++ installers In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this.
View full article
Picard Product_Support
‎2018-09-06 07:54 AM

Last Updated: Janeway RobertAndriolo Janeway ‎2019-09-26 10:12 PM

Labels:
  • EcoStruxure Building Operation
1496 Views

Xenta Server "Run" light is solid red with no communication via Ethernet

Issue Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.
View full article
Picard Product_Support
‎2018-09-07 12:34 PM

Labels:
  • Satchwell MicroNet
  • TAC INET
  • TAC Vista
1882 Views

What cable type should be used for BACnet MS/TP communications?

Issue What specification should the Continuum BACnet MS/TP cable meet? Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation Environment Systems using BACnet MS/TP comm's, with b3 controllers and 3rd party MS/TP devices. MSTP Cable type Spec Cause Often an incorrect cable type is used when wiring MS/TP devices, unless the correct cable specification is used it is unlikely you will get reliable communications. Resolution The BACnet Controller Technical Reference defines the following cable specification for a MS/TP (MSTP) cable: RS-485 Cable Specifications: Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Ohms Velocity of propagation: 78% Capacitance: <12.5 pF/ft (~ 41pF/M) between conductors and < 22 pF/ft (~72pF/M) between the conductor connected to ground and the next conductor. An example of a cable that meets this specification is Belden 3105A. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.
View full article
Picard Product_Support
‎2018-09-07 02:08 PM

Labels:
  • Andover Continuum
  • EcoStruxure Building Expert
  • EcoStruxure Building Operation
9187 Views

Continuum Software Download

Issue Can the Continuum Software be downloaded from the web, or ordered on CD? Product Line Andover Continuum Environment Continuum Cyberstation software Cause Download of Continuum Cyberstation software Resolution The Continuum Cyberstation software is available for download from The Exchange Download Center. The link below will direct you to the Cyberstation software. CyberStation Software If specific older versions of software are required see Older CyberStation versions not found on the Extranet (Exchange Online). If a customer specifically requests the software on a CD, then these can be ordered through the regular Order Entry channel specifying the version required.
View full article
Picard Product_Support
‎2018-09-07 02:31 PM

Labels:
  • Andover Continuum
2886 Views

Unable to login to Security Expert using Windows Authentication

Issue Windows authentication is not working with Security Expert once configured. Environment Security Expert Windows Authentication Cause Windows authentication was not installed or configured properly during initial install/setup of Security Expert. Resolution 1. Install the Security Expert Server, and any Security Expert Clients, with the "Use Windows Authentication" option enabled during the installation process. If this was not initially done at install then you will need to backup your SecurityExpert and SecurityExpertEvents databases, uninstall Security Expert (installing overtop or repairing install may not work) and then re-install Security Expert with the "Use Windows Authentication" option enabled.   2. Go to Global | Operators and create a new operator. The Name can be anything you want. The User Name must be the domain name and domain username you want to have access to Security Expert. This is in the form of "domain\username" as shown in the example image. Set a Role for this operator. And then enable the "Use Windows Authentication" checkbox and save the changes.   3. Go to Global | Home and logout of Security Expert. 4. On the login page select the "Use Windows Authentication" checkbox, set the Server to your Security Expert Server machine name (or blank if it is the local machine) and press Logon.   5. You should now be logged into Security Expert with your Windows username being used.   If you receive an "Access Denied" or other error then confirm the following before contacting Product Support for further help. Security Expert Client and Server were installed with "Use Windows Authentication" option enabled. There is an operator object created in Security Expert with the same domain and user name as the domain user you are trying to login with. The "Use Windows Authentication" option is enabled on this operator object. At the login screen you have enabled "Use Windows Authentication" and set the Server correctly.
View full article
Picard Product_Support
‎2018-09-10 10:19 AM

Labels:
  • EcoStruxure Security Expert
1081 Views

Temperature Sensor Resistance Charts

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded here. The devices covered are Schneider-Electric's range including Andover, TAC and Satchwell and other manufacturers temperature sensors. All are detailed below. For the standard thermistor, tables click here, where the INET, I/A, and BALCO resistance tables are detailed. This is the chart for the Precon Thermistors - ACCTemp 10K Type III thermistor also known as the 10K4A1 Thermistor. For EcoStruxure I/O Module universal inputs, the type of thermistor bead is classed as a: "10k Type I (Continuum)" Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers include: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series. Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here. Please note that the controller may not be able to use the full temperature range shown in the table.  
View full article
Picard Product_Support
‎2020-12-02 06:46 AM

on ‎2020-12-02 06:46 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • Field Devices
  • Satchwell BAS & Sigma
  • Satchwell MicroNet
  • TAC IA Series
  • TAC INET
  • TAC Vista
7502 Views

PCT Installation Issue Error:1722, Error:1603, "The setup has detected no version of SBO Project Configuration Tool is installed."

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 During certain situations, it may be required to remove and re-install PCT to address software conflicts with other software applications. While trying to remove/install PCT you may receive an error preventing you from completing the installation. The setup had detected that no version of SBO Project Configuration Tool is installed.  The specific command-line options require that the application be installed to continue. The setup will now terminate. Error: -1603 Fatal error during installation. Consult Windows Installer help(Msi.chm)or MSDN for more information. Error 1722. There is a problem with this Windows Installer... Product Line EcoStruxure Building Operation Environment Client versions (64 Bit Only): Editions: Pro, Home, Enterprise Windows 10 Windows 8.1 Windows 8 Windows 7       Server versions (64 Bit Only): Editions: Standard, Enterprise Server 2008 R2 Server 2012 Server 2012 R2  PCT versions (64 Bit OS Only): SBO Project Configuration Tool v 1.0.0.487 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.0.0.510 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.0.47 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.1.49 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.2.57 - SmartStruxure Solution - Software Cause In order to get past a possible installation loop, you will need to locate and delete the following Windows registry key: [HKEY_CLASSES_ROOT\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B] Resolution Note: Always make a backup of your registry before making any modifications.   Run regedit.exe Locate/Search: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Delete Registry Key entry: B2A4F0AEC8BB0E2438706F07E2E2560B  
View full article
Picard Product_Support
‎2018-09-10 07:24 AM

Last Updated: Janeway RobertAndriolo Janeway ‎2020-11-29 02:46 PM

Labels:
  • EcoStruxure Building Operation
  • Project Configuration Tool
2151 Views

Xenta Server (Xenta 5/7/913) serial cable guide

Issue If the Xenta Server IP address is unknown or lost, how can the user retrieve or reset the IP address? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Once the Xenta Server IP address is lost, the user has to use a serial connection cable to connect the Xenta Server to the HyperTerminal in order to retrieve the IP address. The serial cable is a RS-232 to RJ10 cable which can be purchase from Schneider Electric order entry (Part number: 00730920). For some reason, if the cable need to be home made, please follow the steps below to connect correct pins. Note: some third party IP search/scan software can be used to search all IP addresses in a range. User can also use this type of software to retrieve Xenta Server’s IP addresses. Resolution Xenta Server serial cable guide: Connect RJ10 pin 1 to RS232 pin 2. Connect RJ10 pin 2 to RS232 pin 3. Connect RJ10 pin 4 to RS232 pin 5. Connect RS232 pin 1, 6, 4 together. Refer to IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for how to set up HyperTerminal in order to retrieve/setup Xenta Server IP address.
View full article
Picard Product_Support
‎2018-09-10 05:15 AM

Labels:
  • Satchwell MicroNet
  • TAC INET
  • TAC Vista
1539 Views

Modbus basics

Issue Understanding and Troubleshooting Modbus Product Line EcoStruxure Building Operation, TAC IA Series, Other  Environment All Modbus environments. Cause Modicon first introduced Modbus in 1979. Modbus is an open standard,and it is the most widely used in the industrial environment. Modbus is publicly available and,due to its simplicity, many manufacturers use Modbus as a solution for integration in their own products. Many commercial products and systems support the Modbus RTU and Modbus TCP protocols. For further information, visit the Modbus website at http://www.modbus.org. Resolution For a brief understanding on Modbus and how to troubleshoot Modbus: Modbus Troubleshooting.pdf
View full article
Picard Product_Support
‎2018-09-10 05:07 AM

Last Updated: Admiral DavidChild Admiral ‎2021-01-28 07:10 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
  • TAC IA Series
  • TAC Vista
3601 Views
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 100
  • Next »
Labels
  • Andover Continuum 2,188
  • Automated Engineering Tool 3
  • CCTV 54
  • EcoStruxure Access Expert 90
  • EcoStruxure Building Expert 224
  • EcoStruxure Building Operation 1,502
  • EcoStruxure Security Expert 204
  • EcoStruxure Workplace Advisor 1
  • Field Devices 694
  • Project Configuration Tool 22
  • Satchwell BAS & Sigma 472
  • Satchwell MicroNet 259
  • TAC IA Series 1,789
  • TAC INET 1,462
  • TAC Vista 2,051
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Schneider Electric
EcoStruxure™ Building Operation
1
Support

Have a question? Please contact us with details, and we will respond.

Contact Us
FAQ

Look through existing questions to find popular answers.

Learn More
About

Want to know more about Exchange and its possibilities?

Learn More

Full access is just steps away!

Join Exchange for FREE and get unlimited access to our global community of experts.

Connect with Peers & Experts

Discuss challenges in energy and automation with 30,000+ experts and peers.

Get Support in Our Knowledge Base

Find answers in 10,000+ support articles to help solve your product and business challenges.

Ask Questions. Give Solutions

Find peer based solutions to your questions. Provide answers for fellow community members!

Register today for FREE

Register Now

Already have an account?Log in

About Us FAQ Terms & Conditions Privacy Notice Change your cookie settings
©2021, Schneider Electric