Issue When a Zigbee device is imported into EcoStruxure Building Operation (EBO), many configuration objects and attributes appear under the device (for example, Thermostat, Power Configuration, Remote Sensing attributes, etc.). Users may not understand why these settings exist or where they come from. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RPC) Zigbee devices integrated through EBO Cause Zigbee devices describe their available functions using clusters, which are defined in the Zigbee Cluster Library (ZCL) Specification. Each cluster contains attributes, commands, and functional definitions for a specific feature such as thermostat control, power configuration, occupancy sensing, or diagnostics. When a Zigbee device joins the network, it announces the clusters and attributes it supports. For example, the "Remote sensing" attribute for the "Thermostat"   Looks like this in the "Zigbee Cluster Library Specification" EBO reads this information and uses it to automatically build the import structure. This is why you see objects such as “Thermostat”, “Power Configuration”, or specific attributes like “Remote Sensing”. EBO does not interpret or validate the functional purpose of these settings. It only exposes what the device reports through ZCL. Resolution EBO auto‑generates device objects and attributes based on the clusters reported by the Zigbee device during commissioning. To understand the meaning or operational behavior of individual attributes or configuration parameters, refer to: The Zigbee Cluster Library Specification, or The device manufacturer’s documentation, since functionality and attribute behavior vary by vendor. EBO’s responsibility is only to present the supported clusters in object form, enabling configuration pass‑through to the physical device.

Issue When logging into EcoStruxure Building Operation (EBO) WorkStation via HTTPS, a security certificate risk warning appears stating:   “There were errors validating the security certificate in use. This may pose a security risk to the system. The certificate presented by this server was issued for a different server's address.” Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation server  Building Operation Workstation  Cause EBO validates the identity of servers using SSL/TLS certificates. If a valid certificate is not installed or the certificate does not match the server’s IP/DNS name, the system displays a security warning. Common causes include: Missing SSL/TLS certificate Incorrect server name (e.g., using “localhost” instead of IP/DNS) Expired or improperly formatted certificate Communication using TCP port 4444 instead of HTTPS (443) Resolution Verify Communication Settings Ensure servers communicate over HTTPS (port 443) instead of TCP (port 4444). Navigate to Control Panel → Configure Communication Settings and update protocol to HTTPS Generate or Import Certificate In WorkStation Control Panel, go to Certificates settings. Select the server (e.g., ES) and click Manage Certificate. Choose one of the following: Generate Certificate (self-signed) Import Certificate (from a trusted CA, PEM format required) Enter details, enable Use IP/DNS, and set a valid expiration date (do not exceed year 2060). Save the certificate. Install Certificate Close WorkStation completely (logging out is not enough). Reopen WorkStation and log in using the IP address or DNS name (not “localhost”). Tick Always trust this certificate and click Trust Certificate. Confirm installation. Additional Notes If using external CA certificates, ensure they are in PEM format. If delivered in .pfx or other container formats, the PEM certificate should be extracted before use. If installation fails, manually select the physical storage for the certificate.

Issue LonWorks network communication can become unreliable or fail completely when wiring and topology guidelines are not followed during installation. Many issues are preventable with correct network design. Product Line Satchwell BAS & Sigma, TAC IA Series, TAC Vista, Satchwell MicroNet, EcoStruxure Building Operation Environment I/A Series MicroNet (LON) Controllers Satchwell MicroNet LON Controllers TAC Vista TAC Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) provides installation requirements for MNL‑100/200/VAV controllers and Satchwell MicroNet 440/620 devices. Misinterpretation or omission of these design rules leads to wiring errors, incorrect topology, improper termination, or device‑count issues that degrade network performance. Resolution Follow these FTT‑10 LONWorks design rules to ensure a stable and standards‑compliant network. 1. Approved Cable Types Use Echelon‑approved twisted‑pair cable. Most common: Category 4, unshielded, stranded twisted‑pair, 22 AWG (0.65 mm). Example: Connect-Air W221P / W222P. Use plenum‑rated or shielded versions when required by site specification. 2. Supported Topologies Bus Topology Daisy‑chain wiring, no branches or stubs. Install LON‑TERM‑2 terminators at each end of the bus. Maximum length using standard Cat 4 cable: 4593 ft (1400 m). MN‑Sx sensor bases must be in-line, not connected as stubs. Free Topology Flexible layout (stars, tees, mixed). Requires one terminator: LON‑TERM‑1. Maximum total cable length: 1641 ft (500 m). Maximum distance between any two controllers: 1312 ft (400 m). 3. Common Wiring Guidelines Do not run LON wiring in an active telephone trunk, even if Cat 4. Use shielded cable only in high EMI/RFI areas. Ground the shield at one end only through a shield terminator. Do not bundle LON wiring with controller I/O or power wiring. 4. Device Count & Segmentation Maximum 64 devices per LON segment, including: Controllers Network Interface Routers / Repeaters Split larger networks into segments using LonWorks repeaters or routers. Each segment must be terminated appropriately for its topology. 5. Addressing Guidelines LON controllers use Domain / Subnet / Node addressing. A single subnet supports up to 127 node addresses, including: Controllers Interfaces Routers / Repeaters Leave address space for commissioning tools when planning subnets.

Issue Unable to log into WorkStation because the administrator password is unknown or forgotten. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P, or AS-B) Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Project Configuration Tool (PCT) Cause The password for an Automation Server, Enterprise Server or Enterprise Central has been forgotten. A Session ID is required to generate an unlock key from Schneider Electric Support. Resolution Important Notes The Session ID is unique to the current WorkStation session. Do not close WorkStation until the password reset is completed. For Automation Servers, USB connection to the PC is required (EBO 3.1 and later). For Enterprise Server or Enterprise Central, the server must be added to Device Administrator (password is not validated at this step). 1. Retrieve the Session ID EBO versions earlier than 3.1.x Open the WorkStation logon screen. Hold Shift and left‑click near the EcoStruxure Building Operation icon.   The Session ID appears. Copy it. EBO 3.1.x Open Device Administrator and select the required server. Tick the checkbox and click the hyperlink. From the toolbar, select Password Reset. When "Password reset token created" appears, click OK. In WorkStation, hold Shift and left‑click near the EcoStruxure Building Operation icon. Copy the Session ID. EBO 3.2.x and higher In Device Administrator, select the server. From the top bar, choose Edit Connection Password / Reset password, then click OK. In WorkStation, hold Shift and left‑click near the EcoStruxure Building Operation icon. Copy the Session ID. PCT 2.x Start the PCT server. Left click the Server Menu.   Select Set password reset mode. In WorkStation, hold Shift and left‑click near the EcoStruxure Building Operation icon. Copy the Session ID. 2. Submit Session ID and Receive Unlock Key Send the Session ID to your local Schneider Electric Product Support team. When you receive the unlock key, proceed to password reset. 3. Reset the Password Ensure the Session ID is still displayed in WorkStation. Log in using: User name: admin Password: unlock key provided by Product Support Domain: Local The Change Password window appears. Enter: Old Password: unlock key New Password: your chosen password (entered twice) Click OK. Troubleshooting Error: "Your account has insufficient permission to use the system. Contact your administrator." This indicates the admin account is locked. Contact your local Product Support group to request an account unlock. Additional References EBO Webhelp Password Reset topic The SBO Password Reset Quick-Help video shows the password reset procedure for EBO versions older than V3.1.X. It covers most of the important steps for newer versions.

Issue Technicians need accurate resistance‑to‑temperature references for legacy and current sensors during BMS upgrades or service. Field users typically know the system in use rather than the thermistor bead type, which makes it difficult to pick the correct resistance table. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment HVAC and BMS installations using NTC thermistors or RTDs Retrofit projects where existing field sensors are retained EBO controllers and I/O modules that require correct thermistor curve selection for accurate engineering units Cause If the controller is configured with a thermistor curve that does not match the actual sensor element, the temperature reading will be offset or incorrect. Lack of documentation for legacy sensors or mixed‑vendor estates makes curve identification difficult. Note:  In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO. Resolution Use the mapping guide below to start from the product range you are servicing, then identify the thermistor or RTD curve, and finally open the correct attachment/table to obtain R–T values. Attachments available All sensors.pdf – multi‑vendor thermistor and RTD tables including 1.8K A1, 2.2K3A1, 3K3A1, 5K3A1, 10K3A1, 10K4A1, 20K6A, 30K6A1, 100K6A1, PT100A, PT1000A, Satchwell T‑range, DD/DR, DO. USSensorTypeG.pdf – complete R–T curve for US Sensor 10K “Curve G” Thermistor types‑tables.pdf – comparative tables for 2.2k, 3k, 10K Type II, Type III, Dale, US “G”, 20k, 100k, plus RTDs. Thermistortempresistchart.pdf – PreCon Type II, Type III, Type IV, Model 3 (10k), Model 42 (20k). RS‑03 NTC10K (3950) chart.pdf – generic NTC10K B=3950 curve. 1k Balco.pdf – 1 kΩ Balco RTD chart. A. Product range to thermistor curve mapping Schneider Electric legacy families System / Family Typical sensor family in field Thermistor or RTD curve to use Open this table Andover Continuum ACC Temp, legacy room and duct sensors 10K4A1 (NTC 10k class as listed; reference points: 25 °C (77 °F), 40 °C (104 °F)) All sensors.pdf → 10K4A1 table TAC Vista Vista 1.8K A1 sensors 1.8K A1 curve (reference points often shown around 25 °C (77 °F), 50 °C (122 °F)) All sensors.pdf → 1.8K A1 table TAC INET INET 10K2A1 (Dale) 10K Dale / Type 9 class (e.g., 25 °C (77 °F) = 10 kΩ) All sensors.pdf → 10K2A1 table; Thermistor types‑tables.pdf for Dale column TAC I/A Series (MNL/MNB) Commonly paired with US Sensor “Type G” elements with 11k ± 0.1% 1/8 watt resistor wired in parallel with the sensor US Sensor 10K “Curve G” (e.g., 25 °C (77 °F) = 10 kΩ (5,238Ω with shunt ; 40 °C (104 °F) ≈ 5.592 kΩ (3,707Ω with shunt) USSensorTypeG.pdf   TS‑57XX‑85X / TS‑67XX‑85X 10K Thermistor with 11K Shunt Resistance Table Satchwell MicroNet or Sigma Satchwell T‑range, DD/DR, DO sensors Use the dataset for the specific Satchwell family (e.g., tables include 0 °C (32 °F), 25 °C (77 °F), 50 °C (122 °F) points) All sensors.pdf → Satchwell T‑range, DD/DR, DO tables Field Devices TC900 RS03 Generic NTC10K elements (use 25 °C (77 °F) = 10 kΩ; 0 °C (32 °F) ≈ 31.77 kΩ) RS-03 NTC10K (3950) chart.pdf   Other common manufacturer mappings Vendor / Product Thermistor curve Open this table Honeywell Aquatrol, Trend, Ambiflex, York 10K3A1 (e.g., 25 °C (77 °F) = 10 kΩ; 50 °C (122 °F) ≈ 3.601 kΩ) All sensors.pdf → 10K3A1 table Allerton 3K3A1 (check typical points like 25 °C (77 °F), 50 °C (122 °F)) All sensors.pdf → 3K3A1 table Ambiflex 2040 2.2K3A1 All sensors.pdf → 2.2K3A1 table Honeywell 20K6A NTC 20k (e.g., 0 °C (32 °F) ≈ 70.204 kΩ; 25 °C (77 °F) = 20 kΩ) All sensors.pdf → 20K6A table Drayton DC1000 / DC1100 30K6A1 (e.g., 0 °C (32 °F) ≈ 105.305 kΩ; 25 °C (77 °F) = 30 kΩ) All sensors.pdf → 30K6A1 table Schlumberger (air) 5K3A1 All sensors.pdf → 5K3A1 table Schlumberger (immersion) 100K6A1 All sensors.pdf → 100K6A1 table   Generic curves frequently seen on retrofits Curve When you might see it Open this table NTC 10k, B=3950 Generic NTC10K elements in third‑party or OEM sensors (use 25 °C (77 °F) = 10 kΩ; 0 °C (32 °F) ≈ 31.77 kΩ as spot checks) RS‑03 NTC10K (3950) chart.pdf US Sensor 10K “Curve G” Many commercial 10k sensors and I/A Series integrations (25 °C (77 °F) = 10 kΩ; 40 °C (104 °F) ≈ 5.592 kΩ) USSensorTypeG.pdf PreCon 10k (Model 3) PreCon‑sourced 10k elements at 77 °F (25 °C (77 °F) = 10 kΩ) Thermistortempresistchart.pdf → Model 3 [Thermistor...esistchart | PDF] PreCon 20k (Model 42) PreCon‑sourced 20k elements (25 °C (77 °F) = 20 kΩ) Thermistortempresistchart.pdf → Model 42 PreCon Type II / Type III / Type IV 2252 Ω, 3k, and 100k families (77 °F reference; common checks at 25 °C (77 °F)) Thermistortempresistchart.pdf 1 kΩ Balco RTD Legacy RTD elements in some estates (e.g., 20 °C (68 °F) ≈ 997 Ω) 1k Balco.pdf    RTD sensors RTD Open this table PT100A All sensors.pdf → PT100A table PT1000A (common checks at 0 °C (32 °F), 25 °C (77 °F)) All sensors.pdf → PT1000A table   B. Quick verification points for spot‑checks Use these values to sanity‑check field readings after selecting the correct curve. US Sensor 10K “Curve G”: 25 °C (77 °F) = 10,000 Ω; 40 °C (104 °F) ≈ 5,592 Ω.  10K4A1: 25 °C (77 °F) = 10,000 Ω; 40 °C (104 °F) ≈ 5,594 Ω. 10K3A1: 25 °C (77 °F) = 10,000 Ω; 50 °C (122 °F) ≈ 3,601 Ω. 20K6A: 0 °C (32 °F) ≈ 70,204 Ω; 25 °C (77 °F) = 20,000 Ω. 30K6A1: 0 °C (32 °F) ≈ 105,305 Ω; 25 °C (77 °F) = 30,000 Ω. PT100A: 0 °C (32 °F) ≈ 100.8 Ω. 1 kΩ Balco: 20 °C (68 °F) ≈ 997 Ω. NTC 10k B=3950: 25 °C (77 °F) = 10,000 Ω; 0 °C (32 °F) ≈ 31.77 kΩ.  PreCon Model 3 (10k): 25 °C (77 °F) = 10,000 Ω. C. Technician workflow Identify the system on site and open the corresponding row in the mapping table. Note the thermistor or RTD curve indicated. Open the attachment listed and use the R–T table to configure the controller and validate readings.

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

Issue Intermittent or unstable LON network communication such as high bandwidth utilization, communication errors, packet loss, or noise on the LON bus. Product Line EcoStruxure Building Operation, TAC Vista, TAC IA Series Environment Xenta Controllers MNL I/A Controllers EcoStruxure Building Operation AS-P LPA Protocol Analyzer Cause LON communication issues are commonly caused by: Electrical noise on LON wiring Excessive bandwidth usage Faulty or miswired network segments Poor grounding or shielding Failing devices generating corrupt packets Line reflections or improper termination These issues can be difficult to identify without proper diagnostic tools. Resolution Review LON Physical Layer and Noise Causes Use the attached Loytec documentation: Loytec Network Training (LON wiring and noise fundamentals) Loytec Network Troubleshooting White Paper (procedures for analyzing and resolving issues) Use an LPA Protocol Analyzer With an LPA tool, you can: Identify excessive bandwidth usage Locate devices generating errors Analyze packet flow and timing Detect noise-induced corruption If LPA is not available – enable LON communication logging Adjust the debug level on the ES/AS-P/AS-B: /Automation Server/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon/nsp.pin.lon.comm Change log level from Information to Trace Reproduce the issue Collect logs for analysis Important: Return the level to Information after capturing data Use SBO Lon Decoder Tool This tool can decode and analyze LonWorks communication logs when an LPA analyzer is not available. Additional References For Vista systems: Actions for reducing Bandwidth in a Vista network For EBO systems: Bandwidth Throttling guidance

Issue Understanding how the EcoStruxure Building Operation (EBO) Evaluation License operates in versions 2.0 and later, particularly in relation to scalable licensing requirements. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and newer (Context only) SmartStruxure/SBO 1.9 and earlier Cause The introduction of scalable licensing in EBO 2.0 changes how permanent licenses are validated once an Evaluation License is removed, creating uncertainty about system behaviour. Resolution The Evaluation License continues to provide temporary engineering and commissioning capability in EBO 2.0 and later. Its core functionality remains unchanged from earlier versions. Evaluation License Behaviour in EBO 2.0+ Enables full engineering and database configuration. Displays a warning banner until permanent licensing is installed. Allows engineering to proceed as long as the license remains valid. Impact of Scalable Licensing (introduced in EBO 2.0) Once the Evaluation License expires or is removed: From EBO 2022 (4.0) onwards Each Automation Server (AS) connected to an Enterprise Server (ES) must have an individual commercial license. System operation follows scalable licensing enforcement rules. A valid commercial licensing structure is required for runtime stability and long-term operation. More information on the Scalable Pricing structure can be found in EcoStruxure Building Operation Licensing and Scalable Pricing Info.  Intended Use of the Evaluation License The Evaluation License is designed for: Engineering laptops Database staging and configuration Commissioning prior to permanent licensing Pre-handover workflow It is not intended as a replacement for commercial licenses. Reference — Where to Obtain Evaluation or Engineering Licenses The location for obtaining the correct license files depends on the EBO version in use. See the dedicated article: Where to Obtain Evaluation or Engineering Licenses for EcoStruxure Building Operation (EBO) This article provides authoritative and up-to-date information on license acquisition.

Issue Building Management System (BMS) equipment may malfunction due to electromagnetic interference (EMI) from nearby electrical devices. Diagnosing and resolving such issues can be complex and costly, making preventive installation practices essential. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Improper installation can lead to the generation or exposure to high- and low-frequency EMI, which may disrupt system performance or cause equipment failure. Resolution To ensure reliable operation and minimize EMI-related issues, follow these key EMC installation practices: Key EMC Practices Follow Manufacturer Recommendations Always adhere to the installation guidelines provided by equipment manufacturers, as they are tailored to the specific EMC requirements of each product. Proper Cable Routing Separate power and signal cables. Avoid parallel runs near high-interference sources (e.g., motors, transformers). Shielding Use shielded cables for sensitive signals. Ground shields correctly—typically at one end to prevent ground loops. Grounding and Bonding Establish a low-impedance ground path. Bond all equipment to a common ground reference. Surge Protection Install surge protection on power and communication lines. Protect against lightning and switching transients. Filtering Use EMI filters on power inputs. Apply ferrite beads or chokes on signal lines where needed. Physical Separation Maintain spacing between high-voltage and low-voltage components. Isolate noisy equipment from sensitive electronics. Enclosure Design Use metal enclosures for shielding. Ensure proper sealing and grounding of enclosure panels. Installation Environment Avoid placing equipment near strong EMI sources (e.g., radio transmitters, welding equipment). Maintain clean, dry conditions to prevent corrosion and poor connections. Compliance Testing Verify installations against relevant EMC standards (e.g., IEC, EN). Conduct site surveys if persistent issues arise. Reference Document: Practical Installation Guidelines for Electromagnetic Compatibility

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. NOTE: It is best to only use the Domain (Netbios) name (as shown above) when adding the Windows Domain name to this property.  Using the full DNS Domain name, for example, eur.gad.schneider-electric.com will cause issues when utilizing other features that require active directory authentication.  One example where this has been identified is with Change Control.   Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials. When logged on to the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log-on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites that have restricted this in some way that may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account that has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. Must use HTTPS. Must enter your Windows username and password. Must enter the domain as the Windows domain as defined within Building Operation.  See below: An example log-on format is shown below when using the above configuration when using WebStation:    Alternatively, if the following is configured in Building Operation: WebStation log-on will look as follows:  Download a TVDA for Single Sign-On Instructions

Issue Cannot find documentation on how to use the new Graphic components release with EBO 2.0 Getting the following errors when previewing my graphic page: "Script error in function "onLoad" .... ReferenceError: "_firstRun" is not defined "Script error in function "onChange" ... ReferenceError: "_setVisuals" is not defined The component added to the graphic shows no binding label in the WorkStations edit bindings window Product Line EcoStruxure Building Operation. Environment Building Operation Graphic Editor 2.0 and above GlobalScripts V2.0.0262 and above Cause With the release of EBO 2.0, a set of new components/snippets have been released, which are different from those issued in earlier releases, although there is very little change visually. The scripting, in most cases but not all, has been removed from the components themselves and put into single scripts. This means we can take advantage of the functionality of the global script. This requires the user to set the UseGlobalScripts attribute to True within the TGML graphic editor, which can be on a per-graphic basis and ensures that existing graphics will still function. Once turned to True, all components with scripts and requirements for other global scripts to function correctly can function as designed. For example, the setpoint box requires global scripts to ensure units and decimal places are displayed as designed/required due to the scripts. There are also two binds available on the box, one for reading and one for writing. Both need to be bound to enable the component to function correctly.  The components are designed this way to allow use in BACnet, where it may require reading the resultant Value but Writing at a specific Priority. Without the scripts added to the graphic, the component cannot function. For further details/questions, refer to the following Community Posts, which also include the current PDF documentation: Help-with-an-EBO-2-0-component EcoStruxure-Building-Operation/Graphic-Component-Library-Rev-AB1-002-pdf NAM Standards Team TGML Component Library - Communities (se.com) This article provides the necessary steps required to enable and get these new components working and does not provide in-depth functionality. Resolution Within Graphics Editor, enable UseGlobalScripts. To do this: Select the -Tgml object shown in the Objects pane In the Properties pane Change the UseGlobalScripts from False to True In the Global Graphic Snippets: Drag the GlobalScripts V2.0.xxxx onto the -Tgml object.  GlobalScripts then appends as shown below. Note: This must be done before adding any components and ONLY once on each Graphic page. Add a Component by dragging it into the Design window. Example showing the Component: Analogue Single Line Text, 100W Add Snippets to allow the relevant Bindings to be added to this component.  To do this: Select the Snippets tab, Select Select Global Bind Snippets Drag the appropriate snippet onto the Component. EcoStruxure Analog Value bind snippet is added to the Analogue Value component Save the graphic Preview - no errors should appear.  If there are errors: Ensure that the scripts/components have been added in the correct order Ensure the correct Snippet has been added to the correct Component.  Refer to the Graphic-Component-Library-Rev-AB1-002-pdf documentation for the tested snippets/component combinations. Open WorkStation and Edit Bindings on the saved graphic page Note: The default binding name displayed View the graphic page   Example: Showing forced value      

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 Building Operation Enterprise Server Building Operation WorkStation Cause There are two different ways to activate a license and different types of licenses that can be purchased. Resolution This article discusses Building Operation Software licenses applied to software platforms such as EC, ES, and Workstation. For details on applying licenses on SmartX Server devices, refer to the Automation Server Licensing Workflow Webhelp topic and/or the Offline activation of embedded licenses Knowledge Base article.   Purchasing a License The licenses that can be purchased are listed in the Part Number Summary. After an order is placed, you will receive an email with an Entitlement ID certificate attached. For further details, see the Order Information Request Webhelp topic.   Evaluation Licenses Evaluation licenses are used for demonstration purposes, training, or site engineering. The evaluation license is a file that can be downloaded from the Exchange and is valid for up to 3 months. Refer to the Activating an EcoStruxure Building Operation Demo License webhelp topic for the activation process.   Activating an Entitlement ID Entitlements can be activated online or offline; however, the online method is far simpler and is preferred. The online method requires the computer that the License Administrator resides on have an internet connection. Online Activation If the computer that the License Administrator is installed on has an internet connection, then refer to the Activating EcoStruxure Building Operation Software Licenses Webhelp topic for the activation process. Offline Activation If the computer that the License Administrator is installed on does not have an internet connection and one can not be temporarily arranged, then refer to the License activation or repair without Internet access Knowledge base article. 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 re-hosted after an upgrade and will remain on the computer if the Building Operation Software is uninstalled and reinstalled. 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 navigating to localhost:8888 in a web browser. The licensing system is the same as used in TAC Vista, which can be seen in License troubleshooting in Vista 5.1.8 or greater.   Returning an Entitlement ID License If the computer on which the License Administrator is being replaced, or it has major operating system changes. In that case, licenses may become invalid and should be returned before those changes. Entitlements can be returned online or offline; however, the online method is far simpler and is preferred. The online method requires the computer that the License Administrator resides on have an internet connection. Online License Return If the computer that the License Administrator is installed on has an internet connection, then refer to the Returning an EcoStruxure Building Operation Software License Webhelp topic for the return process. Offline License return If the computer that the License Administrator is installed on does not have an internet connection and one can not be temporarily arranged, then refer to the License activation or repair without Internet access Knowledge base article. 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, activate this same License on the new system as detailed earlier.   Note: Releasing and reactivating licenses can only be carried out a finite number of times per year (4 license returns each year) to prevent misuse of the licensing system.

Issue Bindings between: Enterprise Server and Automation Server, or Two Automation Servers ...appear as "Unresolved" in the system. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Binding Diagnostics Cause This issue is typically caused by: Incorrect communication configuration Firewall or antivirus blocking communication Port conflicts or usage by other applications Network adapter misconfiguration Unsupported architecture (e.g., EC and ES on the same PC) Resolution 🔒 1. Firewall Configuration Ensure Windows Firewall is correctly configured: Use the Firewall Config Tool to set inbound/outbound rules. Refer to: Creating Windows Firewall Rules for Building Operation. If unsure, temporarily disable the firewall to test connectivity. Watch for network profile switching (Private ↔ Public) during commissioning. ⚠️ Even if ASs appear online, unresolved bindings may still occur due to firewall issues. 🧩 2. Special Character in Server Name For v1.4 or v1.5 servers with an ampersand (&) in the name: Request hotfix: v1.4: R1.4.1.16201 or later v1.5: R1.5.0.1601 or later 🌐 3. Network & IP Configuration Confirm ES IP address matches the PC’s active NIC IP. If not, follow: How to Set the Enterprise Server IP Address. Use an IP address instead of a domain name if DNS resolution is unreliable. Ensure all required ports are open and configured correctly between ES and AS. Automation Server Ports are set and must be changed through WebStation - see Changing the Automation Server HTTP / HTTPS ports  Refer to: Information Technology System Planning Guide → Search “Network Ports”. Disable unused network adapters (e.g., Wi-Fi, VMware, VirtualBox). ES should use the primary NIC. 🔄 4. Repair Communication Right-click the ES → Advanced > Repair Server Communication This refreshes the communication tables. Detach and re-add ASs to the ES if needed. See: Unable to Add an Automation Server Underneath an Enterprise Server. 🛡️ 5. Antivirus & Security Software Disable network monitoring features in antivirus software. For Schneider laptops: Right-click Trellix in system tray → Enable Firewall Timed Groups. ⚠️ 6. Unsupported Architecture Enterprise Central (EC) and Enterprise Server (ES) should not run on the same PC with default ports. If testing: Stop EC service or Reconfigure ports to avoid conflicts. 🔍 Additional Tips Use the Communication tab on each server to verify peer visibility. Example of mis-configured IP Port settings Configuration after IP Port change on Automation Server

Issue Cannot change the IP address or host a SpaceLogic IP device, MP or RP controllers, or IP-IO modules in a second EBO Server. Product Line EcoStruxure Building Operation Environment IP address BACnet Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller  Building Operation IP-IO Building Commission Application Cause 1. IP settings are saved (eg in Building Commission), but the IP address of the Controller does not change. (Option to change most settings is grayed out from Building Commission for hosted SpaceLogic IP devices) 2. The Controller is already hosted by an EBO server and cannot be hosted by a second EBO server, thus data objects cannot be read. 3. Rehosting an SpaceLogic IP device to a different EBO server Resolution 1. Changing the IP address "settings" can be done with Building Commission application, formely know as eCommission Tool, in some earlier versions but if the SpaceLogic IP device, formely known as SmartX IP device, is already fully hosted by an EBO Server, then a warm start from the Building Commission is inhibited. (Option to change most settings is grayed out from Building Commission for hosted SpaceLogic IP devices) Without the hosting Server initiated warm start the new IP setting will not be used. If the SpaceLogic IP device is not hosted then the IP address can be changed from the Building Commission, using the warm start option. Notes A local warm start initiated at the SpaceLogic IP device(manually with the reset button) will not force the SpaceLogic IP device to use these new settings. See BACnet/IP Controller Commissioning Scenarios The IP address of a Hosted SpaceLogic IP device cannot be modified from eCommission Tool A factory reset will force the SpaceLogic IP device to return to AutoIP and DHCP, the BACnet Id will generally be retained see Automatic Association after a Factory Reset in a BACnet Controller or IO Module 2. When a SpaceLogic IP device is fully hosted by an EBO Server, it can be BACnet hosted by a second EBO Server, but this will only contain the standard BACnet Applications folder. This hosted BACnet Device needs to be manually created using the SpaceLogic IP device instance Id.  Below, it can be seen that the fully hosted SpaceLogic IP device and the BACnet only hosting under ASP_22   3. When a SpaceLogic IP device is configured or programmed via the hosting EBO Serving using WorkStation, some of the objects (eg. Scripts or Function Block) data is not fully contained within the SpaceLogic IP device. Thus if the hosting EBO server is changed, some of the configuration data will be lost and a simple upload to the new hosting EBO Server will not upload all the data required to recreated these objects. In such a case, an export from the original hosting EBO Server should be imported into the new hosting EBO Server to ensure no data is lost.

Issue Continuum i2 and b3 devices share the same hardware platform, however, power consumption on the devices IO Expansion Port differs depending on the communication protocol firmware (Infinet or BACnet) running in the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment All i2 devices All b3 devices Cause Even though the hardware of an i2 device is identical to that of its counterpart b3 device, the difference in firmware causes variation in power consumption on the device's Expansion IO port, specifically, it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  Now that conversion of devices from one protocol to another is occurring in the field, it has become evident that there are cases where the 180 mA limit is exceeded in an i2 device without any negative results, but once the i2 device is converted to a b3 device, all IO on the expansion port stop working. Resolution Before converting an i2 device to a b3 device in the field, it is crucial to review the Expansion IO Datasheet (attached) to ensure that the configuration does not exceed the specified power consumption limit. If the configuration exceeds the 180 mA limit, take the following steps: Remove any additional xP module causing the limit to be exceeded. Reconfigure the xP modules to ensure that the configuration does not consume more than 180 mA.

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue When logging into Workstation one of the following error codes is given.  Invalid returned data from license server system. (Error code: -12) Cannot connect to license server system. (Error code: -15) License server system does not support this feature (Error code: -18) The desired vendor daemon is down. (Error code: -97) Product Line EcoStruxure Building Operation Environment Workstation License Server Cause These type of issues are contributed to the License Server, Vender Daemon being down or not having a valid license for the application which is used. Here is a complete list of error codes Resolution If Workstation is installed on a different PC than the license server, refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96). If you get license error -18 refer to Error "Requested license is not available on the license Server" even though the license for the StruxureWare Building Operation is valid. Start by working through the troubleshooting steps below. In some cases the Building Operation License Server was unable to start due to antivirus programs on the computer.    Cannot connect to FlexNet License Admin Using your internet browser and go to localhost:8888. If you are unable to connect to this address then the License Server is not running.  Ensure that the Building Operation X.X License Server is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services.  Scroll through the list and select Building Operation X.X License Server. Click start in the top left corner of the window. Some times the following Windows Error 1067 is given when trying to start the License Server. Note: In the past this error has been caused by antivirus software on the computer. In this situation the antivirus program had to be uninstalled in order to allow the License Server to start.    If the Building Operation License Server will not start then it may be due to another program using TCP port 8888. Use TCPView to search for programs running on local port 8888 and stop the other program.      Vendor Daemon is Down Note: If working with a 32 bit PC, replace "Program Files (x86)" with "Program Files" in the file paths below. Using your internet browser go to the address localhost:8888. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password.  Click on the Vendor Daemon Configuration tab and then select the taclic daemon.  Verify that the path in the License File or Directory field matches the location of the taclic.lic file. The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start.    Vendor Daemon is Down issue caused by ipv6 Cases have been seen where having ipv6 enabled on the same computer where the license server is running causes the Daemon is down error.  Often there will be entries in the license server logs that are similar to: 17:46:44 (demo) Lost connection to lmgrd, heartbeat timeout expired, exiting. 17:46:44 (demo) EXITING DUE TO SIGNAL 37 Exit reason 5 17:46:44 (demo) IN: "f1" user1@host1 (SHUTDOWN) 17:46:44 (lmgrd) demo exited with status 37 (Communications error) To confirm whether this is the issue ask the site if it is OK to disable ipv6 on the machine temporarily. In Windows control panel disable ipv6 Reboot the computer. In some cases, it might be needed to disable IPv6 completely in the registry: https://tweaks.com/windows/40099/how-to-properly-disable-ipv6/ If the issue is resolved then inquire with the site if it is OK to leave ipv6 disabled. If SIGNAL 37 errors are seen in the license server logs, these can be caused by having the localhost name associated with the IPv6 loopback address in the hosts file. This can cause communication problems between the license server daemon (lmgrd) and the vendor daemon, resulting in shutdown of the latter. If you have a line like the following in the /etc/hosts file: ::1 localhost ip6-localhost ip6-loopback please change it to ::1 localhost6 ip6-localhost ip6-loopback so that the localhost name is associated only with the IPv4 127.0.0.1 address. Please note that modifying this file requires Windows administrative privileges.  

Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) 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. Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT NOTES: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    If the device you are converting is of model i2/b3 865/866/885 STOP First confirm that the device is NOT a -V device, this is accomplished by editing the device and inspecting its version number, -V devices have a "1" embedded in the second part (after the ".") of the version number   A non -v device will show the above version number as follow,,, 3.500027   To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue When PC based firewall's are used, some configuration in the license system and in the firewall are required to be made. In some cases, the error below when logging into Workstation appears: License server machine is down or not responding (Error code -15 or -96) Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC license (taclic) vendor daemon by default uses a random port each time it's started. This setting makes it difficult to handle in a firewall. Also the various EcoStruxure programs using the license system needs to be allowed in the firewall, as well as the ports used by the license system. Here is a simple explanation of how the license request from a client is made. Resolution Make sure there is a valid license installed on the license server. For more information read Requested license not available for Enterprise Server, Workstation or editors The easiest way to configure Windows firewall, is to run the SBO Firewall Config tool on all PC's having EcoStruxure software installed. For any questions regarding the use of this tool please contact the developer, details in the tool. In order to manually make the configuration follow the steps below. For more information on how to create Windows firewall rules, read Creating Inbound and Outbound Windows Firewall Rules.   On the server PC Make the port used by the vendor daemon fixed. Follow Define the port used by the taclic vendor daemon guide to do that. On the PC having the license server installed, open the following TCP ports in the firewall both inbound and outbound.  80 443 4444 2170 27000 through 27009 (If a user defined defined port has been used other than 2170 for the vendor daemon then use that instead of 2170)   On the client PC On the PC having EcoStruxure software installed using the license server on a remote PC, make these exceptions in the firewall: Allow ports TCP 80, 443, 4444, 2170 and TCP 27000 through 27009 both inbound and outbound. (If you defined a port other than 2170 for the vendor daemon then use that instead of 2170) Allow the following programs: SE.Graphics.Editor.exe SE.SBO.Script.Editor.Proxy.exe SE.SBO.ScriptEditor.exe SE.SBO.WorkStation.exe SE.WorkStation.IA.WptEd.exe tam32.exe They are typically located here: On 32 bit OS: C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.X\WorkStation On 64 bit OS: C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation 1.X\WorkStation

Issue Trouble synchronizing the time of the Automation Server or Enterprise Server to a NTP server or between each other Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server Cause The Enterprise Server and the Automation Server (ASP/ASB) do not synchronize time to each other, they must use an NTP server for synchronization Resolution The information below is mainly concerned with synchronizing the time setting but not the actual time.   Overview To synchronize the server times an NTP Server will be required, they do not synchronize time with each other. A common misconception is that the Automation Servers sync time with the Enterprise Server via server-to-server communications. To find an external NTP server consult support.ntp.org . Alternatively, an existing internal NTP server can be used or consult Setting up a Local / Internal NTP Server to configure the Enterprise Server computer as a time server The time settings on the Enterprise Server are configured through the operating system settings on the computer where Enterprise Central is installed.  EcoStruxure Building Operation cannot be used to configure the NTP server for the Enterprise Server. Please refer to Network Time on WorkStation, Enterprise Server, and Enterprise Central To find the Network Time Protocol (NTP) configured on a WorkStation, Enterprise Server, or Enterprise Central computer open a command prompt and enter w32tm /query /peers. If configured the peer NTP server(s) will be listed If you need to ensure an NTP server is actually running on certain IP or DNS address, please reference Ensure IP or DNS address is valid NTP server The time settings on the Automation Servers can only be configured via the Workstation. As per the image they can be configured to look at an NTP server (1) or set manually (2). For synchronization, they must use an NTP Server. Please refer to  Network Time Server on an Automation Server on Webhelp Starting in version 1.5, the time adjustment depends on how much the Automation Server drifts from the NTP server. The faster the Automation Server drifts, the more frequently the time is updated.  Please refer to How often will an Automation Server ask the NTP server for the time?  If the time server is a URL, such as time.nist.gov, then it is critical that a Primary DNS is set for each Automation Server, and possibly a Secondary DNS via Device Administrator. Without a DNS, the Automation Server will be unable to resolve the URL to an IP address. Please refer to Configuring the Automation Server IP Address on Webhelp The time displayed for a server in Workstation (Properties -> Basic) will reflect the time zone of the local computer that Workstation is installed on. All events and alarms will be automatically modified to match the time of the workstation that was used to log into the server. The "Server time" will represent the date and time of the server adjusted to client local time zone, while the fields below "Server time" represent the settings of the Automation Server.   How to synchronize date and time settings on multiple Automation Servers   IMPORTANT: Only the time settings are synchronized via the Lead/Shadow configuration, the time itself IS NOT synchronized via the Lead/Shadow but rather by all servers synchronizing with the configured timer server.   The synchronizing of multiple Automation servers can be achieved with a lead/shadow relationship. The primary and secondary network time server settings for connected shadow Automation servers are defined on the Enterprise server. Setting up the Primary and secondary time servers in the Enterprise Server only passes those configuration settings to the AS controllers, it does not send the actual time and date value.   Select the Enterprise server (1), click the Date & Time tab (2), select Enable (3) and enter the Primary time server (4) and, if used, the Secondary time server (5) the Automations Servers will use. Ensutre the time zone for the Enterprise Server is set correctly (6).   Save the settings  From EBO version 2.0 all Automations Servers are automatically configured to shadow the date and time settings configured in the Enterprise Server. To verify this expand the System folder of an Automation Server and select Time Settings -> Date and Time (1). Observe the Date and Time are Shadow-Read only (2), replicating the Enterprise Server settings. Attempting to change any of the settings, other than the Lead object (3), will result in an error. All the Automation Servers will be 'looking' to the same Primary (4) and Secondary time servers, i.e. they will all receive the same time and be synchronized Similarly, select the Time Zone (1) of the Automation Server in the System Tree; this will also be shadow-read only (2). The lead object is set to the Time Zone on the Enterprise Server (3) Before EBO version 2.0 the Automation Servers were not automatically set to shadow the Enterprise Server settings but this could easily be achieved en masse using Search . In the Search box in the top right corner of the Workstation, type "Date and Time" and click Search (1) to find the date and time object of all connected servers. In the Search view select the servers (2) that require their Date and Time settings synchronized to the Enterprise Server, the Enterprise Server does not need selecting. Select the Time tab (3) and then click the triple dots (4) to navigate to and select the Date and Time object on the Enterprise Server (5)   You may need to stop and start the Enterprise server to get the configuration settings to pass down to the shadow Automation servers Note: To set up synchronization of the time zone settings follow the above search steps for date and time but search on Time Zone Tip/Tricks To see the time of on the Enterprise Server and multiple Automation Servers use the Search to find the Date and Time object (1). Individually select each server (2) and then drag the Date and Time object (3) into the Watch Window (4) It is the Automation Server that initiates the synchronization. To check the Automation Server communication settings select the Automation Server (1) and in the Communication tab (2) select the Enterprise Server (3) and make sure the Automation Server has the correct IP address (4) To check the Enterprise Server communication settings select the Enterprise Server (1) and in the Communication tab (2) select each Automation Server (3) and make sure the correct IP address is specified for each Automation Server (4).  If a firewall exists ensure that the ports are open so the Automation Server can connect to the Enterprise Server. Please search for the EcoStruxure Building Operation IT Reference Guide on Exchange for details Further Information Release 1.2.0 and higher Until the time is set, b3 data will not update in the Watch Window Until the time is set, BACnet COV will not be functional Automation Server time does not synchronize directly with the Enterprise Server. Instead, all servers can synchronize to the same accessible time server To adjust the Automation Server time, time zone, and DST, access to the Automation Server is through a WorkStation