Sign In Help
Schneider Electric
HelpSign In
Schneider Electric Exchange
  • Home
  • Collaborate
  • Develop
  • Shop
Home Collaborate Develop Shop Log in or Register Help

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
  • Collaborate
  • Exchange Community
  • :
  • Knowledge Center
  • :
  • Building Automation Knowledge Base
Community Menu
  • Forums
    • By Topic
        • 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
          • Форум по промышленной автоматизации СНГ
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Forum
          • SCADA and Telemetry Devices Forum
        • Power Distribution IEC
          • Power Distribution and Digital
          • Power Standards & Regulations
          • Paneelbouw & Energie Distributie
        • Power Distribution Softwares
          • EcoStruxure Power Design Forum
          • SEE Electrical Building+ Forum
          • LayoutFAST User Group Forum
        • 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 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
        • Форум по промышленной автоматизации СНГ
      • SCADA & Telemetry Solutions
        • Geo SCADA Expert Forum
        • SCADA and Telemetry Devices Forum
      • Power Distribution IEC
        • Power Distribution and Digital
        • Power Standards & Regulations
        • Paneelbouw & Energie Distributie
      • Power Distribution Softwares
        • EcoStruxure Power Design Forum
        • SEE Electrical Building+ Forum
        • LayoutFAST User Group Forum
      • 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
        • Industrial Automation
          • Industrial Edge Computing Blog
          • Industry 4.0 Blog
          • Industrie du Futur France
        • SCADA & Telemetry Solutions
          • SCADA and Telemetry Blog
        • Power Distribution IEC
          • Power Events & Webinars
          • Power Foundations Blog
        • Power Distribution NEMA
          • NEMA Power Foundations Blog
        • Power Distribution Softwares
          • EcoStruxure Power Design Blog
          • SEE Electrical Building+ Blog
        • Solutions for your Business
          • Solutions for Food & Beverage Blog
          • Solutions for Healthcare Blog
          • Solutions for Retail Blog
        • Community experts & publishers
          • Publishers Community
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Blog
        • Healthcare
          • Solutions for Healthcare Blog
        • Retail
          • Solutions for Retail Blog
      • Industrial Automation
        • Industrial Edge Computing Blog
        • Industry 4.0 Blog
        • Industrie du Futur France
      • SCADA & Telemetry Solutions
        • SCADA and Telemetry Blog
      • Power Distribution IEC
        • Power Events & Webinars
        • Power Foundations Blog
      • Power Distribution NEMA
        • NEMA Power Foundations Blog
      • Power Distribution Softwares
        • EcoStruxure Power Design Blog
        • SEE Electrical Building+ Blog
      • Solutions for your Business
        • Solutions for Food & Beverage Blog
        • Solutions for Healthcare Blog
        • Solutions for Retail Blog
      • Community experts & publishers
        • Publishers Community
      • Food & Beverage
        • Solutions for Food & Beverage Blog
      • Healthcare
        • Solutions for Healthcare Blog
      • Retail
        • Solutions for Retail Blog
  • 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 How-to videos
    • Ask Exchange
    • Digital E-books
    • Success Stories Corner
    • Power Talks
  • Events & Webinars
  • Support
    • User Guide
    • Leaderboard
    • Releases Notes
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: 
49594members
Join Now
242977posts
Join Now

Building Automation Knowledge Base

  • « Previous
    • 1
    • 2
    • 3
    • …
    • 74
  • Next »
1465 posts
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 74
  • Next »
Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Subscribe to RSS Feed
  • Invite a Friend
  • Print Knowledge Base
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 74
  • Next »
Showing articles with label EcoStruxure Building Operation. Show all articles

When logging in to an AS or ES, SBO WorkStation freezes or it takes a very long time to log in

Issue When logging in to an AS or ES, WorkStation freezes or it takes a very long time (>30 minutes) before the login process finishes. Building Operation WorkStation hangs on "Reading data..." when trying to login to an AS or ES Product Line EcoStruxure Building Operation Environment Building Operation WorkStation License Cause The problem is related to a delay when validating the license details. It only seems to happen when running a mixed EBO/SBO 1.9.3 system and after having EBO license administrator 2.0.1 previously installed. Resolution Run the SBO License Server Reset tool and perform Reset - Simple Log in to WorkStation, and if the hang or freezing is still present, then follow the next set of instructions. Run Diagnostics in the License Administrator and take note of all the ACT (Activation) and Entitlement IDs Return all the licenses Close all WorkStations and stop all SBO/EBO processes (whichever may be running) Uninstall all License Administrator and License Server Run the SBO License Server Reset tool and perform a Reset - Complete (you will get an output of the commands and result) Install the latest released version of License Administrator and License Server (the latest released version of License Administrator has fixes for virtual servers and some cyber security vulnerabilities, note that License Administrator is backward compatible with earlier SBO versions) Activate the licenses based on the info from step 3 Note: If running the demo license, steps 3 and 4 may be skipped. If problems continue to occur, then send the above details collated (in step 3) and email this/contact support.
View full article
Picard Product_Support
2 weeks ago

Labels:
  • EcoStruxure Building Operation
4077 Views

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 2 weeks ago

Labels:
  • EcoStruxure Building Operation
  • TAC Vista
5683 Views

Upgrade path from version 1.0 to current version

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2 Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016 1.9.1.95 Apr 2017 1.9.2.45 Maintenance Release Oct 2017 1.9.3.24 Maintenance Release April 2018 1.9.4.29 Maintenance Release April 2019 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) 2.0.2.67 Maintenance Release Sep 2018 2.0.3.45 Maintenance Release Dec 2018 2.0.4.83 Maintenance Release June 2019 3.0.1.104 May 2019 3.0.2.33 Maintenance Release July 2019 3.0.3.11 Maintenance Release Aug 2019 3.0.4.43 Maintenance Release Dec 2019 3.1.1.312 Dec 2019 3.1.2.29 Maintenance Release Mar 2020 3.2.1.630 Aug 2020 3.2.2.61 Maintenance Release Nov 2020 Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them
View full article
Picard Product_Support
2 weeks ago

Labels:
  • EcoStruxure Building Operation
2832 Views

Message sent from AS to Modbus device after online status is restored

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment Building Operation 1.5.x to 2.0.3 Modbus Device Socomec Power Meters Crompton Integra 1221 Power Meter Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this workaround is that the online detection for the device is turned off, so the device will never go offline in Building Operation. In some instances, the third-party Modbus device will need to be restarted to allow communication to resume.
View full article
Picard Product_Support
3 weeks ago

Labels:
  • EcoStruxure Building Operation
1227 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
4 weeks ago

Labels:
  • EcoStruxure Building Operation
1008 Views

EcoStruxure Energy Expert (formally Power Manager) Licensing

Issue After upgrading from EcoStruxure Energy Expert (formerly Power Manager) version 1.0 to 1.1 or newer, the licensing no longer works. Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Energy Expert (Power Manager) License Administrator Power Monitoring Expert Cause There can be some confusion on what licenses are required to run Energy Expert. There are also differences between version 1.0 and 1.1 or newer licensing.  Resolution EcoStruxure Energy Expert License In order to use Energy Expert, an Energy Expert license is needed to be purchased before the previous Power Monitoring Expert (PME) 90-day trail license expires. It is important to remember that EcoStruxure Building Operation licenses are needed to work along side Energy Expert (e.g. Workstation, Enterprise Server, etc). The EcoStruxure Building Operation licenses need to be activated in the EcoStruxure Building Operation License Administrator (How to activate, release and/or transfer a license in EcoStruxure). Note: The EcoStruxure temporary license (evaluation) is only for EcoStruxure Building Operation software and does not include Energy Expert Energy Expert Version 2.0 Licensing and Upgrading If upgrading from a previous Power Manager 1.X site to Energy Expert 2.X, a new license(s) will be required. In order to obtain your new license(s), please follow the procedure found in TPA-EBO-19-0001.00 - EcoStruxure Energy Expert v2.0 License Upgrade.  Version 1.1 to 1.3 Licensing The part numbers for version 1.1 or newer are listed below. PSWPMNCZZSPEZZ - Base Power Manager license. PSWDENCZZNPEZZ - Power Manager entry range device license (to add devices to PME). PSWDMNCZZNPEZZ - Power Manager mid range device license (to add devices to PME). PSWSANPAZSPEZZ - Upgrade from Power Manager to full Power Monitoring Expert. Upgrading from version 1.0 up to 1.3 Acquire a new 1.X license by filling out the Power Manager 1.1 Upgrade Request form (same form used for a 1.0 upgrade to any version 1.1 or newer). This is a free upgrade.   After submitting the upgrade request, you will receive an email with your new activation ID(s) within a couple of days.  Once the new activation ID(s) have been received, the software upgrade can take place. Simply follow the "Upgrading..." section of the Power Manager Integration Manual. Version 1.0 Licensing The part number for this license was SXWSWSPMUL0001. This license will allow the use all of the Power Manager features and no additional EWS licenses need to be purchased. Activating a License Once the Activation ID has been received for a Power Manager license, it can be activated in the Floating License Manager. For more detail on license activation see the Power Manager Integration Manual. Go to the Start menu, Schneider Electric > Floating License Manager Click Activate to open the Activation Method dialog. Select By web and click Next. Enter the Activation ID value, select Specify from the dropdown list for Seats, and then enter 1 for Count, and click Next. Specify your email address, choose a location where the request file can be saved, and then click Next. Click Yes if none of the software products are controlling your production systems. Click Finish.
View full article
Picard Product_Support
‎2020-12-17 05:51 AM

Last Updated: Admiral DavidChild Admiral ‎2020-12-17 08:07 AM

Labels:
  • EcoStruxure Building Operation
  • OTHER
2041 Views

Understanding BACnet BBMD Distribution Mask.

Issue When configuring BBMD what is the Broadcast Distribution Mask and what are the valid setting for the field. Product Line EcoStruxure Building Operation Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution Read: UndestandingBACnetBBMD_DistributionMasks.pdf  
View full article
Picard Product_Support
‎2020-12-17 06:47 AM

on ‎2020-12-17 06:47 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1185 Views

Define the default BACnet Priority Level in EcoStruxure Building Operation

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

on ‎2020-12-17 06:20 AM

Labels:
  • EcoStruxure Building Operation
934 Views

BACnet device Instance Number (Instance ID) in EcoStruxure Building Operation

Issue What are the rules governing the BACnet device Instance ID in EBO Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (all) BACnet Cause The BACnet device Instance ID must be unique within a BACnet  system. There may be a need to find out or change the device Instance ID to ensure there are not duplicates.  Resolution When a BACnet Interface is added to an AS or ES , the AS or ES will become a BACnet device and it will have an Instance ID (automatically generated or manually assigned).  To check an ES or AS BACnet device instance ID go to the properties of the BACnet Interface and then the Advanced tab. The device instance ID is defined as the Object ID. To check other  BACnet device, go to the properties of the BACnet Device and then the Advanced tab. The device instance ID once again is defined as the Object ID.  No 2 BACnet devices in any system may have the same Instance ID/Object ID The valid range of Instance Numbers for a BACnet device is 0 to 4194302
View full article
Picard Product_Support
‎2020-12-17 06:13 AM

on ‎2020-12-17 06:13 AM

Labels:
  • EcoStruxure Building Operation
1307 Views

Upgrading Power Manager 1.0 to EcoStruxure Energy Expert 2.0 (PME 7.0 to PME 9.0)

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 for assistance. Issue When upgrading EcoStruxure Building Operation to version 2.0 or newer, the existing Power Manager software should also be upgraded to EcoStruxure Energy Expert to maintain compatibility Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Power Monitoring Expert (PME) Power Manager Cause The proper procedure is required when upgrading from older versions of Power Manager to the latest Energy Expert version. Guidance and best practices are needed for upgrading a PME server from PME 7.2 to PME 9.0. Resolution A Power Manager 1.0 site should be taken to 1.1 first, then upgraded to Energy Expert 2.0 Below are the recommendations for a side-by-side upgrade from PME 7.2 to PME 9.0: On the old server: Run the PME_8.2.iso file to do an in-place upgrade from PME 7.2.3 to PME 8.2 After completing that upgrade, the system will default to using a PME 8.2 trial license Install and run the PME 8.2 CM 2.1.0 Tool which will perform necessary actions for the side-by-side upgrade; we will use it to create a .zip file containing configuration components such as reports, dashboards, diagrams, users, devices, etc. Transfer this .zip file from the CM Tool to the new server On the new server: Run the PME_8.2.iso file to install PME 8.2 (this can be done while the above steps are performed on the old server) After transferring the .zip file from the old server, install and run the PME 8.2 CM 2.1.0 Tool on the new server and have it load the archived data from the .zip file into the program, and then write it to the system (essentially performing a PME 8.2 server to server migration) After that finishes, we can run the PME_9.0.iso file to upgrade from PME 8.2 to PME 9.0 After PME 9.0 is installed, we can activate the PME 9.0 license(s) in the Floating License Manager using the activation ID(s) that were already acquired, then remove the PME 9.0 trial license using License Manager (different from Floating License Manager) Running into issues with the install? Receiving error messages related to PME? Check out the Technical FAQ for a solution to your problem.  Links to relevant documentation and files: Where can I find documentation for Power Monitoring Expert 8.2 (PME 8.2)? Where can I download Power Monitoring Expert 8.2 installation files? Where can I find documentation for Power Monitoring Expert 9.0 (PME 9.0)? Where can I download Power Monitoring Expert 9 installation file? CM Tool Overview (Box link) CM Tool Demo Video (Box link) PME 8.2 CM Tool Download (Box link) PME 8.2 CM Tool Exchange Community post  PME 9.0 CM Tool Exchange Community link  
View full article
Lieutenant JG Robert_Davis Lieutenant JG
‎2020-12-17 06:03 AM

on ‎2020-12-17 06:03 AM

Labels:
  • EcoStruxure Building Operation
1265 Views

How to activate, release and/or transfer a license in EcoStruxure Building Operation

Issue The process of acquiring a license Entitlement ID and how to activate, release and/or transfer a license in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation License Administrator up to and including version 1.9.x Cause There are two different ways to activate a license as well as different types of licenses that can be purchased. Resolution Once a license file or Entitlement ID has been activated and the Status reads "Valid" in the License Administrator, the activation process has been completed. The license does not need to be rehosted after an upgrade and will even remain on the computer if EBO is uninstalled and reinstalled using the wizard. In order to check the status of the license server and licenses that have been activated on the local machine, the Flexnet License Administrator can be accessed by going to localhost:8888 in Internet Explorer. The licensing system is the same as the one used for Vista which can be seen in License troubleshooting in Vista 5.1.8 or greater . Purchasing a License The different licenses that you can purchase are found in the Part Number Summary PDF found on the extranet. The following basic licenses are available for purchase. For additional add-ons and extra features such as the Technician Tool, Web Services, and even a registration key for OpenLNS please refer to the Part Number Summary PDF. Once you have placed your order through iPortal or your regional sales manager, then you will eventually receive an email with an Entitlement ID certificate attached. Power Manager Part # SXWSWSPMUL0001 (For more info see EcoStruxure Energy Expert (formally Power Manager) Licensing) Note: There is NO part number for Webstation; it is a default feature of the Automation Server and Enterprise Server with no need for additional licensing. (up to and including 1.9.x) Activating a License File Launch Building Operation License Administrator. Click on the License tab. To the right of the green plus sign, click on the small black arrow pointing down. Select "Add license from file". (Normally used when applying an Evaluation License) Browse to the license file.  The temporary license file can be downloaded from the extranet at the link  Evaluation license for StruxureWare Building Operation . Once the activation of the license file has completed click "Close". Click "Restart now" to restart the license server with the newly added license file. Activating an Entitlement ID Note: In order to activate a license with an Entitlement ID in the following manner, the computer that the License Administrator resides on must have an internet connection. If you do not have an internet connection and can not acquire it temporarily then see License activation or repair without Internet access. Launch Building Operation License Administrator. Click on the License tab. To the right of the green plus sign, click on the small black arrow pointing down. Select "Add license from entitlement ID". In the Add license window, enter the Entitlement ID into the field and click "OK". Note: Sometimes copying and pasting the Entitlement ID from the certificate can cause issues and it must be typed manually.  Once the Entitlement ID has been located, the type of licenses and the number of seats associated with that Entitlement ID will be listed in the window. Select the number of seats of each license that are to be activated on this computer and click "Activate". Once all licenses have been Activated, click "Close". Click "Restart now" to restart the license server with the newly added license files. Returning an Entitlement ID License Launch Building Operation License Administrator. Click on the License tab. Select the License you wish to return and then click on the red "X". For the License to correctly return an internet connection is once again required but can also be accomplished without, see License activation or repair without Internet access Transferring an Entitlement ID License There is no separate process when transferring a license from one system to another.  Simply return the License from the current system as indicated above and then check that the available seat count has increased by one via the original Entitlement ID. Once returned you can then activate this same License on the new system as detailed earlier.   Note: Releasing and reactivation of licenses can only be carried out a finite number of times per year to prevent misuse of the licensing system.
View full article
Picard Product_Support
‎2020-12-17 05:57 AM

Last Updated: Admiral DavidChild Admiral ‎2020-12-17 05:58 AM

Labels:
  • EcoStruxure Building Operation
5327 Views

Frequency new events and trend log records are sent to an External Log storage

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

on ‎2020-12-15 11:40 AM

Labels:
  • EcoStruxure Building Operation
50 Views

Workplace Tech 5.10 and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. Following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016,(.msi install) Visio 2019 is not supported in 5.9.4 or EBO versions.  Visio 2019 is supported when using Workplace Tech 5.10 only. Visio 2013, 2016, 2019 (subscription "Click to Run", Plan 1 or 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run" , Plan 1 or 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Security Bulletin MS-16-70 Visio 2010 32 bit KB3114872       Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020       Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan1 or 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message
View full article
Picard Product_Support
‎2020-12-15 09:58 AM

on ‎2020-12-15 09:58 AM

Labels:
  • EcoStruxure Building Operation
  • TAC IA Series
3828 Views

Sigma controllers fail to cold start correctly from the Sigma Server when transitioned into EBO

Issue Sigma controllers that have been cold started do not recover correctly. Product Line EcoStruxure Building Operation, Sigma Environment Sigma Server Building Operation Enterprise Server Cause Having imported a Sigma database into the Sigma Interface on the Enterprise Server, and following a controller cold start, Sigma controllers fail to fully recover. The controller correctly receives the Backup server number, but fails to request the data from the Sigma Server. Resolution This issue is resolved as follows; Data Import the Sigma Data. Stop and restart the Enterprise Server using the Software Administrator Cold start a controller to confirm that it fully recovers. Note: A  restart of the Enterprise Server will be required again if any new additional controllers are to be added to the Enterprise Server. This workaround only works for ARM7 controllers, for V53 devices, the Sigma 4.08 (3.46.79) Hot Fix is available on the Download Centre and needs to be installed at the Sigma Server machine. Note; this hotfix is a separate item to any other Sigma hotfix and the correct Sigma Transition Tool version needs to be installed.
View full article
Picard Product_Support
‎2018-09-11 03:12 PM

Last Updated: Admiral DavidChild Admiral ‎2020-12-09 06:59 AM

Labels:
  • EcoStruxure Building Operation
697 Views

EcoStruxure Energy Expert (Formerly Power Manager): Integration Utility Error

Issue When trying to launch the Energy Expert Integration Utility (formerly the Power Manger Integration Utility) the following error is given. Product Line EcoStruxure Building Operation Environment Energy Expert Power Manager for SmartStruxure Integration Utility Cause This error message can be the result of different causes. Check the IntegrationUtility.log file found in the same location as the Integration Utility for more information.  Example of Integration Utility Log error: ERROR: Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "IntegrationUtility.Shell", name = "(none)". Exception occurred while: Calling constructor IntegrationUtility.Pme.Services.PmeUserDataStore(). Exception is: ConfigurationProviderException - Could not locate a connection string provider. Resolution NOTE: If you have already downloaded the software, you must first delete the folder you unzipped before doing the process below.  Unblock the Zip file The first thing that MUST be done after downloading the Power Manager software from the Exchange is to unblock the zip file. Right click on the zip file and select Properties. Under the General tab, towards the bottom click Unblock. Click Apply and close the properties window.  You can now unzip the software and use it as normal.  Compatible .Net Framework Versions Different versions of the Power Manager / Energy Expert Integration Utility require certain versions of Microsoft .Net Framework. Note: Having multiple versions of .Net Framework installed may cause issues.    Pease refer to the Energy Expert Compatibility Matrix for further detail.
View full article
Picard Product_Support
‎2020-12-09 06:06 AM

Last Updated: Admiral DavidChild Admiral ‎2020-12-09 06:07 AM

Labels:
  • EcoStruxure Building Operation
1095 Views

EcoStruxure Trend Log is not visible to EcoStruxure Energy Expert (formerly Power Manger) ETL Tool

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

on ‎2020-12-09 05:55 AM

Labels:
  • EcoStruxure Building Operation
842 Views

EcoStruxure Energy Expert (Formerly Power Manager): Best Practices

Issue Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert There are some best practices and tips that can be used to save engineering time when setting up a EcoStruxure Energy Expert (Formerly Power Manager) system. To find out the differences between Energy Expert and Power Monitoring Expert (PME) see Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Energy Expert EcoStruxure Power Monitoring Expert ETL Integration Tool Cause The following topics should be considered before and during the implementation of the EcoStruxure Energy Expert offering to achieve the cleanest and most effective database.    For more information on design considerations including IT considerations, software compatibility, server specification, hard drive space, etc; see Design Guide - EcoStruxure Energy Expert - formerly Power Manager. For more information on integration see Energy Expert with EcoStruxure Building Operation.  For more information regarding Power Monitoring Expert (PME) please visit the Solutions Expert Community. Here you can find documentation, content, and additional help.  Resolution You may get some benefit working thorough some older existing support material under Energy Expert's former name of Power Manager such as the Deploy Power Manager for SmartStruxure Solution in a Day document.  Also check out the Power Manager EWS Alarm Web Configuration Quick-Help video on the Exchange. General Always install the EcoStruxure Energy Expert software with full Windows administrative rights. Just logging in with a user that has admin rights may not be enough. If you are unable to save an ETL job or run as a service; close ETL, right click on ETL and select run as administrator.  Create one folder on the root level of the server that holds all of the extended trend logs you wish to transfer to EE. This folder can even be set up to be visible to only a designated admin account to prevent any changes to be made to the trends. If any other items like trend charts are in this folder, it will only slow down the process.  See StruxureWare ETL tool locks up or takes a long time while loading sources for information on how to improve the scan time of the ETL load sources function.    SQL Server It is not recommended to install EcoStruxure Energy Expert on a machine that has another instance of SQL already installed on it unless you have advanced SQL configuration skills. The default SQL instance name is ION and the system administrator password is ION!Everywhere. This should not be changed.   Selecting Between Architecture 1 and 2 The three items to consider when selecting an Architecture are device type, numbers of registers to be requested, and device location. The device type is the most important item to consider though. In order to get the most out of the high feature, more robust meters, Architecture 2 should be used. Architecture 2 should be used if the following features are present; ION meter, multi-address device, power quality functions, onboard logging, and/or onboard alarming. When low-end power meters, energy meters, or pulse meters are used, there is no difference between the two architectures in fulfilling the energy management requirement. Most of the Schneider Electric meters and circuit breakers are fully supported by EE. This means that EE has built-in drivers to utilize the full function of the device and the required commission time is minimized.   Architecture 1: Logging data in EcoStruxureWare Building Operation (EBO) It is recommended to use interval trend logs to log the raw data coming in from the meters.  The only durations that need to be set up in trend logs for ETL is the standard trend log duration. This is generally going to be 15 minutes as a industry standard. EE Dashboards and Reports have an aggregation mechanism to make use of the data. Thus durations such as day, week, or month do not need to be brought over into EcoStruxure Energy Expert (EE) as it can be calculated later based off of the 15 minute trend log value.  If both Trendlogs and Extended Trendlogs are used, it is recommended to send the data in the Trendlog to EE to avoid the lagging between Extended Trendlogs and Trendlogs.    ETL StruxureWare Building Operation version 1.6 RC EcoStruxure Web Services (EWS) do not support Secure Sockets Layer (SSL) URLs. For the ETL Extract task make sure to fill out the web service name (default is admin), web service password (default is admin), and web service URL (replace localhost:8080 with your web server address and port as needed) in the settings. For the ETL Load task make sure that the ION data database connection string and ION network database connection string are correct. Also change the field enable recorder and channel creation to True. The recommended naming convention for the Target Device field is [Group].[DeviceName] with no special characters such as \ * + = | : ; < > _. An example could be BuildingA.SubMeter1 where the building name is used as the group and the meter name is used as the device name. With this naming convention, all values brought in under this particular meter will have the same Target Device name.    The Target Measurement field is very important to set correctly as it will not bring the data over to EE correctly if the right unit has not been chosen. This is a process that will become easier with more experience but you can reference Section 6.9 Measurement mapping for ETL in the Power Manager for SmartStruxure Solution - Integration Manual. This chart can be used to search for the unit type you are dealing with and which corresponding Mapping should be use. 
View full article
Picard Product_Support
‎2020-12-09 05:51 AM

on ‎2020-12-09 05:51 AM

Labels:
  • EcoStruxure Building Operation
3294 Views

EcoStruxure Energy Expert. (Formerly Power Manager) licensing access issue

Issue When attempting to access the dashboard URL via the web browser or in SBO Workstation, the following message is displayed. Product Line EcoStruxure Building Operation, EcoStruxure Energy Expert Environment Power Manager 1.2 and newer Power Manager Expert 8.1 and newer Building Operation Workstation Cause A Power Manager 1.2 or newer system running a permanent license allows the user to a log into the Management Console, manual authentication URL, and through the EWS interface in SmartStruxure Workstation. After upgrading to the latest version of Power Manager this access no longer works. The Ports match in License Manager and FlexNet and this site has previously worked. The cause to this issue is that the URL being used has changed starting in PME 8.1. Resolution This issue is due to a change made in the dashboards URL starting in Power Manager 1.2 / Power Manager Expert 8.1. The URL needs to be changed by replacing "Web" with "Dashboards" in the URL found in the EWS link settings or when logging in directly with a web browser.    Example: http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fWeb%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324... http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fDashboards%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324...   Also in the newer versions of Power Manager, there is a limit regarding what can be accessed in PME when using a Power Manager license. In Power Manager 1.2 and on you can access: /Reporter /Dashboards /Trends /HierarchyManager /RateEditor and use the integration toolkit to get into SBO if necessary. Power Manager is now known as EcoStruxure Energy Expert.
View full article
Picard Product_Support
‎2020-12-09 05:45 AM

Last Updated: Admiral DavidChild Admiral ‎2020-12-09 05:47 AM

Labels:
  • EcoStruxure Building Operation
903 Views

Sigma Transition - duplicated SFE graphics but in a different language.

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

on ‎2020-12-07 01:49 AM

Labels:
  • EcoStruxure Building Operation
  • Satchwell Sigma
579 Views

Can Extended Log comments be included in Report Server Reports

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

Last Updated: Admiral DavidChild Admiral ‎2020-12-07 12:30 AM

Labels:
  • EcoStruxure Building Operation
42 Views
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 74
  • Next »
Labels
  • Access Expert 81
  • Andover Continuum 2,168
  • Automated Engineering Tool 3
  • CCTV 53
  • EcoStruxure Building Expert 216
  • EcoStruxure Building Operation 1,465
  • EcoStruxure Workplace Advisor 1
  • Field Devices 690
  • OTHER 197
  • Pelco 1
  • Project Configuration Tool 19
  • Satchwell MicroNet 251
  • Satchwell Sigma 448
  • Security Expert 187
  • TAC IA Series 1,778
  • TAC INET 1,451
  • TAC Vista 2,040
  • « Previous
  • Next »
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
©2020, Schneider Electric