Building Automation Knowledge Base

Issue AS-P is restarting on its own intermittently. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (All Versions) Cause Log entries found within the system_log.txt file confirm that the intermittent restart issue is caused by power interruption. See the below example of what to look for: Apr 08 19:03:34 AS-P-04619A kernel: pmem: shutdown interrupt: pid=0, comm=swapper/0 Apr 08 19:03:34 AS-P-04619A kernel: [<80013920>] (unwind_backtrace+0x0/0xe0) from [<801f569c>] (pmem_shutdown_irq+0x54/0x74) Apr 08 19:03:34 AS-P-04619A systemd-journal[1360]: Journal stopped -- Reboot -- Apr 08 19:03:54 cpud pmem_util[656]: Found SyncBlock Partition at sector 0x5dc00, 192000 sectors long. pmem_util[656]: ---------------------------------------------------- pmem_util[656]: SyncBlock Header summary (from previous power fail): pmem_util[656]: Sequence number:             94 pmem_util[656]: Exit critical regions:       0ms pmem_util[656]: SyncBlock file systems sync: 20ms pmem_util[656]: SyncBlock write map:         0ms pmem_util[656]: SyncBlock write speed:       6399kB/s (Wrote 128kB) pmem_util[656]: Total power fail time:      ~130ms pmem_util[656]: ---------------------------------------------------- pmem_util[656]: Finished moving 240 sectors (120kB) pmem_util[656]: Exit Resolution When an AS-P detects a power outage, regardless of how brief, it will initiate the process to backup the run-time and configuration data from memory to storage and reboots itself.  Check the power source connected to the AS-P and take appropriate actions to improve uninterrupted power delivery. An example would be to deploy a UPS solution.

Issue Definition clarifications for Thermistor Type in Technical Reference Guide for StruxureWare Building Operation Environment StruxureWare Building Operation site with Thermistor temp sensors Cause In the image below of the technical reference guide for StruxureWare Building Operation on page 3164 the accuracy of the supported thermistors seems to be difficult to decipher or at least very hard to figure out what accuracy goes to what thermistor type. The issue is the input specifications does not clearly separate the Thermistor type (Continuum, I/NET, etc) with the accuracy. If there was a line or something to separate the accuracy definitions from each other that would help. What defines one set of values from the next? The ending of the parenthesis defines the end of the information for each sensor type, but this is not clear.  Resolution A defect has been recorded and it has been requested that in the next release of the Technical Reference Guide for StruxureWare Building Operation, this be corrected and offer clarification as to the accuracy with a Hard Return. The lines are actually separated by the end of the parenthesis, but this is difficult to decipher.  

Issue What are the values named Temp_FBValue Environment StruxureWare Building Operation Site with Function Block Cause Site is wondering about the values named Temp_FBValue. What is the meaning and why you cannot bind them.   Resolution A function block variable with the name XXX_FBValue is an output variable from an Input block (e.g. RI- BI- II- PI- block). It’s an internal variable and ought to be hidden, but it’s not so today. It should not be possible to bind theses variables.

Issue Enterprise Server does not start when computer is started/rebooted or shuts down right after starting it StruxureWare Building Operation Software Administrator log shows the following error: nsp.NspServer The server has made too many unsuccessful attempts to start... Product Line EcoStruxure Building Operation Environment Software Administrator Enterprise Server Cause StruxureWare Building Operation is prohibiting the Enterprise Server from starting up because the ES has exceeded the number of startup retries defined in server_startup.properties. When the server_startup.properties file is opened in a text editor, the first line indicates a startup failure. NspServer.Startup.Service.Status: fail Resolution Windows XP: This is caused by a dependency, set in the registry, on the service netprofm (Network List Service), which exists on Windows Vista and later, but not on Windows XP. The error has been verified on a new installation of Windows XP. Steps 1 and 2 below help to resolve this on the XP operating system. Windows 7 and Windows Server 2008 R2 including Virtual: Start ES manually from the Software Administrator. If this fails, the log in the Software Administrator explains why. Start the ES manually from the Services listed in Services (Start, My Computer, right-click, Manage, Services click the + to find Services) find StruxureWare Enterprise Server Go to the Software Administrator and modify the HTTP, HTTPS, and TCP ports to available ports. (suggested: 81, 444, & 4444). The number of startup retries is defined in the following file: 1.2.0 and below : C:\Program Files\Schneider Electric\StruxureWare X.X\Enterprise Server\etc\server_startup.properties 1.3.0                  : C:\Program Files\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\etc\server_startup.properties 1.4.1 and above : C:\ProgramData\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\db\etc\server_startup.properties Increasing this threshold in server_startup.properties will allow the Enterprise Server to have a better chance of achieving a successful startup. server_startup.properties -- Original settings NspServer.Startup.Service.Status: fail NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 2 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 2 server_startup.properties -- Threshold increase to 10 retries. NspServer.Startup.Service.Status: success NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 0 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 10   Last option, and please go through all the previous steps mentioned before attempting: Open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Building Operation X.X Enterprise Server. Open the DependOnService and remove the first line (netprofm) and then reboot. The ES will now start automatically.     Alternative Workarounds Go to Computer Management by right clicking on Computer and going to Manage. In Computer Management, go to Services and Application > Services > Building Operation X.X Enterprise Server. Right click on Building Operation X.X Enterprise Server and go to properties. The two different settings that can be changed so that the Enterprise Server starts automatically as a service after a reboot are as follows. Under the General tab, change the Startup type from Automatic to Automatic (Delayed Start). Or under the Recovery tab, change the Restart service after to a value of 3 or more minutes.

Issue How to register LonTalk Protocol Analyzer Software Product Line EcoStruxure Building Operation, TAC Vista Environment Vista LPA Cause The LonTalk Protocol Analyzer software is a tool for LonWorks network troubleshooting. There are two kinds of LPA license. Some customers may be confused about it. Resolution To use the LPA, you need to purchase the software license. There are 4 kinds of LPA license. Refer to this page for further explanation. LPA-SW: This license is bound to NIC709-USB.  Need to use specific NIC709-USB to be the network interface of the software. LPA-IP-SW: This license is bound to NIC852. Need to use specific NIC852 to be the network interface of the software. LPA-IP: Same as the above, but includes a dongle.   The steps of registration for the current version of LPA using the current NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec's Website. Open the LPA program Click on "Help->Register Product"   Enter the Registration Code in the product package, and click Add.   The steps of registration for previous versions of LPA using the previous NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec Website. Open the LConfig program.   Click Register / Activate to open the registration window. Enter the Registration Code in the product package, and click Add. Then the registration is finished. Open the LPA software to test whether the license works fine.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue Clarity in protocols and capability from StruxureWare Building Operation's Normalization Layer and the integration of BACnet/IP for data out of StruxureWare Building Operation. Environment StruxureWare Building Operation Site Cause Protocols and desire to input/output point data from the Normalization Layer. Desire to pull point data into StruxureWare and then back out, via BACnet/IP.  Resolution The Normalization Layer in StruxureWare Building Operation is probably more of a design philosophy than a documented product feature, per se. It is StruxureWare’s attempt to present data (analog data, for example) to the user in a consistent manner, regardless of the protocol in which the data is natively encoded – BACnet, LON, Modbus, etc. This “data normalization” occurs automatically, although there may be some options for adjusting how certain values are presented. In other words, the  “Normalization Layer” is a term that was coined by the Product Marketing side of the use and has been embraced by  many to refer to the various parts of StruxureWare Building Operation that allow us to gather information from a wide variety of field protocols, such as BACnet, LON and Modbus today as well as being in a position to communicate with OBIX or OPC or any other protocol and to present it to the user in the same way as we present the other protocols. In other words, we make it “normalized” for the end user so that he or she does not need to know or care from what type of device the data comes. The StruxureWare Building Operation system can send point values or alarms to third-party system via BACnet/IP. StruxureWare can do this even in the present 1.0 release. The typical method to share point values would be to use either a Script or Function Block program to bind a StruxureWare point value to a third-party point value. To share alarm information just add the third-party device to the Recipient_List property of one of StruxureWare’s NotificationClass objects that is associated with an alarm.

Issue Infinet to MP or RP controller communications Product Line EcoStruxure Building Operation Environment Infinet Controller i2 i1 SmartX IP RPC RP-C, MPC, MP-C, MPV, MP-V Controller Cause The power cycle and bandwidth requirements need to be considered when setting the parameters for Infinet to MP/RP communication Resolution First ensure a good understanding of "Infinet Under the hood" article. A direct binding can easily be made between an Infinet controller object like an Analog Value and an MP/RP Controller object like an Analog Value. The whole communication path is not BACnet so a "Value transfer settings" window can be opened that controls part of the EBO communication process. This default configuration (Infinet to MP/RP) will usually result in the Infinet Value being collected every 10 seconds, this value will then only only be written to the MP/RP when the value changes. To ensure the value is correct following a power cycle either enable Guaranteed transfer and set to 1 minute, or use the retailed level on the MP/RP object   If there is a listview, graphic or watch window containing the Infinet Object, this causes the value to be collected every 500mS, as seen in the screenshot below   If the Infinet Object is "exported", (see "Infinet under the hood" for details) then the communication can be much more efficient as the values are only sent when there is a change (greater than the object threshold for analog inputs).   If the communication is from the MP/RP Object to the Infinet controller Object, then a BACnet COV subscription will be set up by the EBO server to the MP/RP Controller, this will be renewed if either is reset/power cycled. It needs to be remembered that the "Value Transfer settings" is an EBO property and in this case the communication is controlled by the EBO Server with Infinet in one direction and BACnet in the other. So the communication to the MP'/RP controllers will either be a write or a COV subscription from the EBO Server.

Issue The nvoEffectSetPt is different than the nviSetPoint The nvoEffectSetPt is different than the cooling or heating setpoint (SCPTsetPnts) Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The nvoEffectSetPt is calculated according to nviSetPoint, cooling or heating setpoints (SCPTsetPnts), nviStPointOffset, and thermostat offset. Resolution The nvoEffectSetPt is a SNVT network output in Xenta 102-AX and represents the current effective setpoint that the controller is utilizing in its control loop. nvoEffectSetPt can be configured to display in two different manners: Actual and Normalized. (As defined bynciVAVselctcCntl.oP.ESS (UCPTvavSelection)) Actual nvoEffectSetPt displays the setpoint that corresponds to the currently active application mode of the controller (occupied cooling, unoccupied cooling, standby cooling, occupied heating, unoccupied heating, and standby heating). Normalized nvoEffectSetPt displays the average of the cooling and heating setpoints for the currently active occupancy mode (occupied, unoccupied, standby). NOTE: Whether nvoEffectSetPt is set to Actual or Normalized only affects how the effective setpoint is displayed and does not affect how the application operates. The 102-AX application utilizes the setpoint that corresponds to the currently active mode (occupied cooling setpoint, etc.). In addition, the thermostat adjustment of the setpoint will not appear in any SNVT in Xenta 102-AX controller. This offset is captured in the Xenta 102-AX's memory, and although it is not displayed, it is utilized into the nvoEffectSetPt calculation. Also note that the below scenarios only apply to the occupied and standby modes since the unoccupied setpoints are unaffected by nviStPointOffset, nviSetPoint or by the thermostat offset. Scenario 1: nviSetpoint is unused 1.1 Actual nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the sum of one(1) of the four setpoints (occupied cooling, standby cooling, occupied heating and standby heating) plus the offsets (nviStPointOffset and thermostat offset). 1.2 Normalized nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the average of heating and cooling setpoints ( 1/2(Occupied Cooling Setpoint + Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint + Standby Heating Setpoint) ) plus the offsets (nviStPointOffset and thermostat offset).   Scenario 2: nviSetpoint is used 2.1 Actual nvoEffectSetPt calculation: In cooling mode, the nvoEffectSetPt is the nviSetPoint plus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint -Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ),  plus the offsets (nviStPointOffset and thermostat offset). In heating mode, the nvoEffectSetPt is the nviSetPoint minus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint - Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ), then plus the offsets (nviStPointOffset and thermostat offset). 2.2 Normalized nvoEffectSetPt calculation In this scenario, whether the application is in the cooling mode or the heating mode, the nvoEffectiveSetPt is the sum of the nviSetPoint and the offsets (nviStPointOffset and thermostat Offset). Therefore, when nviSetPoint is used and nvoEffectSetPt is to Normalized, the actual heating and cooling SCPT setpoints do not matter; only the difference between them is significant. For example, setting occupied cooling and heating setpoints to be 75°F (24°C) and 65 °F (18°C) will give the same resulting nvoEffectiveSetPt as setting occupied cooling and heating to be 45°F (7°C) and 35°F (1°C).   Example Occupied Cooling = 72°F (22°C), Occupied Heating = 68°F (20°C), nviSetPoint = 75°F (24°C), assuming the nviStPointOffset and thermostat offset are zero. nvoEffectSetPt in Occupied Cooling or Heating Mode   Scenario 1.1 Scenario 1.2 Scenario 2.1 Scenario 2.2 Cooling Mode 72°F (22°C) 70°F (21°C) 77°F (25°C) 75°F (24°C) Heating Mode 68°F (20°C) 70°F (21°C) 73°F (23°C) 75°F (24°C)

Issue Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), while Reports from within Workstation work fine.  Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), and get no Reports folder within Workstation. Login Screen appears as expected, but when attempting to log in with the user name/password; It times out and comes with the message 'Failed to establish connection with server.' Product Line EcoStruxure Building Operation Environment Building Operation WebReports 1.1 / 1.2 Cause The error is most likely due to ports been blocked and/or the incorrect port settings entered during the WebReports installation process. When installing (or upgrading) WebReports, you must enter this information on each occasion as this information is not retained from previous installations. If you need to change these settings, then you should follow the procedure detailed below. Resolution If installed on separate machines, then check the firewall settings and ensure the ports used for the Enterprise Server and the Report Server are not blocked.  If this does not resolve the issue or if you are running both the Enterprise Server and Report Server on the same PC, then the Enterprise Server port configuration during the WebReports installation may need to be changed.  This is achieved as follows: this, and follow these key steps: Run the WebReports Installation setup program, and at the Setup Type prompt, select Upgrade from... Proceed through the other options as normal. Once you reach the Reporting Agent setup, make sure you enter the correct URL (path and port number - this is unique for each installation) used during the Enterprise Server setup. Continue through the other settings as required - Ensure that any Path and URL ports are set correctly.  Once you complete these settings, the WebReports Installer package then goes through the following checks and installation: Checking Installation Requirements Pre-upgrade Configuration Installation of Reporting Agent, WebReports, and WebReports Service Post-Installation Configuration Installation PublishedReports After the above steps, the upgrade is completed. This will now allow login to the WebReports URL using your web browser. For additional assistance in installing/upgrading WebReports, refer to the online help website. 

Issue Supplemental Documentation on the Menta OPT block for optimized start and stop. Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The document below is intended to clarify the inputs and configuration parameters of the Menta OPT block and when/how to use them. Resolution Click here to download the example Menta macro A Brief Overview of Optimized Control Optimal Start Optimal Start measures how long it takes a room temperature to reach setpoint each morning when the air-handling unit is enabled. These measurements are then used to predict how long it will take the next time. As time goes on, the predictive algorithm is refined until it becomes quite accurate. An optimally started unit saves energy by only starting as early as is needed, not just an arbitrary hour or two before occupancy. Optimal Stop Optimal Stop is less common. An optimally stopped unit stops running prior to the end of the day. It measures how long it takes before the measured room temperature drifts outside of an acceptable range around the setpoint. This saves energy on cooling a building until 5:00pm (for example) when the occupants are just about to walk out the door. The example in this document will not implement Optimal Stop. Inputs to the OPT Block RoT Room Temperature. If there is just one room temperature sensor being served by the optimally started unit, then this is where it would be used. However, if the unit has several room temperatures or serves many VAV terminal units, consider the following options: Average all temperatures Pick one interior zone Highest room temperature for cooling/lowest room temperature for heating Use return air temperature In all of these scenarios, some consideration should be made for if the input sensors fail: Averaging all temperatures is the most robust method. However, if SNVT inputs are used, it may be necessary to discard invalid values (621.8°F) from the averaging calculation. If one interior zone is used and the temperature sensor fails, the unit will eventually revert to starting as early as is allowed every day. The default value for this is 12 hours early; the example in this document uses 2 hours. If the primary sensor fails, use a secondary, or disable optimal start on a failed condition. Instead of the highest and lowest room temperatures, it may be wise to use the second highest and the second lowest room temperature. This allows for one failed sensor in each direction before the Optimal Start calculation is affected. Using return air theoretically is a lot like using the average of all room temperatures. Adjusting the setpoint to get the desired result might be required. A failed sensor input should disable the Optimal Start calculation. SP Setpoint. Using two OPT blocks – one for Optimal Start cooling, one for Optimal Start heating – allows each to be fine tuned. If there is a morning warm-up sequence, then the heating Optimal Start may be much quicker than the cooling. Using one block requires the internal calculation to adjust as the needs change from cooling to heating, and can be less agile when switching from cooling to heating requirements. OuT Outdoor Temperature. Resets to the curve occur based on the outside air temperature. If it is very cold or very hot outside, the unit will start sooner. This curve is reset automatically as time goes on to better predict the effect outside air temperature has on the controlled space (if AutoAdjust > 0). OpI Operation Indication. In the example of an air-handling unit, OpI would be the fan status. If the configuration parameter OperIndicF is set to 1, then this will be used for internal calculations. Otherwise, it will just use the command as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. TmL Time left. A time schedule (TSCH) input goes here. This tells the calculation how much time is left before the unit is scheduled to turn on (or off). The OPT block then starts the unit early based on this number. It also ensures that the unit always runs during the scheduled occupied time. Mode Mode is for heating/cooling or enabled/disabled. It is advantageous to always program in a method for disabling Optimal Start through a public variable (PVB). Many times the seeming complexity of Optimal Start is found to be undesirable by building operators and they will ask to have it disabled. Mode could be programmatically set for heating/cooling based on outside air temperature (or some other factor), but in the example in this document, two separate OPT blocks are used and are hard-coded for their respective modes. Configuration Parameters of the OPT Block AutoAdjust AutoAdjust refers to whether or not the OPT block gets smarter by adjusting the curves set initially on the first download. If AutoAdjust is set to 0, then the OPT block will still adjust the start time every day based on the room temperature and outside air temperature, but it will not adjust those early start times based on past experience. Set the AutoAdjust to 1, and the curves will adjust a little every day. Set AutoAdjust to 2 and the OPT block will also adjust the holiday compensation (the unit will start a little earlier after a 3-day weekend, but may need to learn exactly how much as time goes by). To maximize the potential of the OPT block, it is suggested to set this value to 2. RoomTempF Room Temperature Flag. Is a room temperature sensor present? Without a room temperature sensor, it is not possible for the OPT block to adjust its curves. It is guessing at that point based on pre-determined curves. It is not recommended to use OPT without a room temperature sensor. OperIndicF Operation Indication Flag. If OperIndicF is set to 1, then the OpI input will be used for internal calculations. Otherwise, the OpI input is ignored and the command is used as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. StartTimeLo Start Time at Low Outside Air Temperatures. When it is cold outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust as needed each day, but a good default value is important. StartTimeHi Start Time at High Outside Air Temperatures. When it is hot outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. HolidayComp Holiday Compensation. This is the default compensation for a holiday (longer than 48 hours of continuous unoccupied time). The value is a percentage. If there is a 3-day weekend, how much earlier should the unit start on the following Tuesday? If AutoAdjust is set to 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. MaxStartTi Maximum Start Time. This is the maximum amount of hours the unit is permitted to start prior to the occupied time. The default value is 12 hours. The first time the unit is downloaded, it will start this early and measure how long it takes to achieve setpoint. 12 hours is very early. The example in this document uses 2 hours. Even if something goes wrong with the internal calculation (failed sensor input, for example) the earliest it could start would be 2 hours early. ETol Error Tolerance. How close to the desired setpoint does the temperature sensor need to be to be considered at setpoint? An error tolerance of 0.5°F is default and is usually acceptable. StopLoTemp, StopTimeLo, StopHiTemp, StopTimeHi, StopTimeErr All of these parameters refer to the Optimal Stop portion of the OPT block. Setting them to 0 disables the Optimal Stop functionality. Output of a OPT Block There are three possible output values of an OPT block: 0 = The unit is off, unoccupied 1 = The unit is on, occupied 2 = The unit is on, optimally started Putting It Into Practice The example below is a Menta Hierarchy Function Block (HFB) and shows HFB inputs to the blocks. The top OPT block is set to heat mode and looks to a heating setpoint. The bottom OPT block is set to cool mode and looks to a cooling setpoint.   OPT_START_HEAT OPT_START_COOL AutoAdjust 2 2 RoomTempF 1 1 OperIndicF 1 1 StartTimeLo 60 0 StartTimeHi 0 60 HolidayComp 0 0 MaxStartTi 2 2 Etol 0.5 0.5 StopLoTemp 0 0 StopTimeLo 0 0 StopHiTemp 0 0 StopTimeHi 0 0 StopTimeErr 0 0 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.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.   Issue On a new installation of SmartConnector, the service is not able to start. The log shows a SQL server authenticate error. Product Line EcoStruxure Building Operation Environment SmartConnector Cause For some countries, the administrator account has been localized. (List available here: If the operating system is using one of these localized languages, the Windows administrator account may not be recognized by the SmartConnector service, https://social.technet.microsoft.com/wiki/contents/articles/13813.localized-names-for-administrator-account-in-windows.aspx ) Resolution Workaround 1:  Reinstall a non-localized version of Windows.   Workaround 2: Create a new user in the SQL database.   Workaround 3: Open Microsoft SQL Server Management Studio and connect to the SQL instance the SmartConnector will use. Using the Object Explorer menu, navigate to the logins folder: 'Machine-name > Security > Logins' Right-click on the Logins folder, and select 'New login' A window will appear, to configure the new user account. Provide a Login name: this is the log-in the SmartConnector will use. Then select 'SQL Server Authentication', fill in the password field, and type it a second time in the 'Confirm password' field. Select 'Server Roles' from the menu on the left side of the account windows. Check both 'public' and 'sysadmin' if not already checked. Move to the next page: 'User Mapping' Select 'SmartConnector.Service' row, update 'User' and 'Default Schema' with 'dbo' value. Check the 'Map' box, then in the bottom list check the 'db_owner' box. Repeat steps 10 & 11 for 'SmartConnector.User' entry. Click 'OK'  Now that the user is created Uninstall the SmartConnector and restart the machine Reinstall the SmartConnector, and select 'SQL authentication' when requested Provide the newly created login with the associated password. Complete the SmartConnector installation. Validate the service is running without error.  

Issue Viewing Script time from the editor can show incorrect time Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB, AS Classic Building Operation Enterprise Server Building Operation WorkStation Script Program Editor Cause Scripts use Local Server time, but the Clients like Script Editor or WorkStation expecting a server to be UTC. The result is that during Daylight Saving Time, the time seen in the script editor may appear an hour out. Resolution During debugging of Times or Dates or DateTime Values, it is helpful to "Print" the Datetime to a string as this will show actual time being used rather than the Clients interpretation of the time (See script below).The client will take the Server time as UTC and apply offsets to achieve its "Local" time, which can give an incorrect time. The UTCOffset property can be used to correct for time zones but there is no DST(Daylight Saving Time) offset available until v4.0.

Issue What is the b2 and i2 Controller Object Format property used for? Product Line EcoStruxure Building Operation Environment Continuum Conversion i2 Controller objects b3 controller objects Cause i2 and b3 Controller objects include a a Format field for objects created using the Continuum Conversion tool. What is this used for and how does the value effect the operation?     Resolution These Format values are propagated through the Continuum Conversion Tool for reference only and have no impact on operation in EBO. The values cannot be modified. In EBO there are two ways to configure numeric display formats. -In WorkStation property pane and watch window, the number of decimals displayed to the right of the decimal point is inherited from the WorkStation PC's regional settings. This setting applies to all values displayed in WorkStation except for values in graphics. -In graphics, the number decimals displayed to the right of the decimal point is configured value-by-value in the Graphics Editor.   The format value is not stored in an EBO export and if objects are manually created, then standard formats are used for the type of object created .

Issue Deleting logs from External Log Storage takes a very long time. Workstation becomes unresponsive when deleting trends from External Log Storage. Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause The deletion process can take a long time on large PostgrSQL databases, sometimes as much as an hour.   Workstation must complete the deletion process before it becomes available for other tasks.   When logged into Enterprise Server to delete a trend that was hosted by a child server (Automation Server), Workstation tags the log for deletion.  The AS that held the original log, will survey the trend_meta table every hour to check for pending flags, and will then delete logs that are flagged.  This can cause the deletion to be delayed by as much as an hour.   Resolution The following method should be used when deleting trends from External Log Storage: The trend must no longer exist in EBO. Log on locally to the server that hosted the associated trend.  Then deleted the trend from the System\External Log Storage folder. Indexing the trend_data table can improve the speed of deletion dramatically in large PostgreSQL databases (1 TB or larger).

Issue The SmartX Controller Advanced Display requires internet access in order to activate the Kiosk Mode on initial startup. Product Line EcoStruxure Building Operation Environment SmartX Controller Advanced Display v2 and v3 SmartXKiosk Cause The SmartX Controller Advanced Display requires internet access in order to be activated on initial startup, site IT departments may need to allow access for activation to proceed. Resolution Internet access is required only once during initial installation to activate the Samsung license If you are in the Americas, enable access to these servers:  Server Port gslb.secb2b.com 443 us-prod-klm.secb2b.com 443 us-elm.secb2b.com 443 If you are in China, enable access to these servers:  Server Port china-gslb.secb2b.com.cn 443 china-klm.secb2b.com.cn 443 china-elm.secb2b.com.cn 443 If you are in Asia, Africa, Europe, or other regions, enable access to these servers:  Server Port gslb.secb2b.com 443 eu-prod-klm.secb2b.com 443 eu-elm.secb2b.com 443   For additional communication paths, refer to the online help topic Information Technology System Planning Guide

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.   Issue ES takes up to 30 minutes to perform a shutdown. Trace log contains multiple entries indicating "Subscription service forcefully shutting down; [sub-server name]"  "Subscription service forcefully shut down; [sub-server name]"   A secondary issue - When performing Windows Updates automatically, Windows attempts to shut down all running services within one minute which can end the Enterprise Server service prematurely Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server 3.1.x and below Large Multi-server installation  Cause During a shutdown procedure of the Enterprise Server a call to every sub server is made to remove subscriptions. However, the thread pool that executes these commands may already be stopped and the server then waits the 15 seconds timeout period prior to moving to the next item.  On a large 100+ multi-server installation, this 15 second delay can accumulate to a lengthy shutdown period.     The trace log will contain the messages shown  in the issue and the 15-second delay between each server  Enterprise Server Trace log messages seen during shutdown showing the 15-second timeout delay. Resolution Upgrading to 3.2.2 (and above) will rectify the timeout issue provided that the subscription thread pool has already stopped.  These versions now ignore the 15-second timeout for each sub-server if the thread pool has already stopped.   It is possible to extend the Windows service shutdown time by adding or adjusting a registry entry called WaitToKillServiceTimeout .   To change the timeout: Start the registry editor (“Regedit”) In the tree on the left, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control In the right panel, find the WaitToKillServiceTimeout value. If you don’t see it, create it by: Selecting Control on the left Choosing Edit > New > String Value (not DWORD) from the menu Naming the new value WaitToKillServiceTimeout. Double-click the WaitToKillServiceTimeout entry to bring up the Edit String window. Enter a numeric value (e.g. 60000) in the Value data field in milliseconds and click OK to save your change. Reboot your computer. The new timeout setting will not take effect until Windows restarts. Note that this modification will not make Windows wait indefinitely for your service to finish. If your service takes longer than the entered time (in this example 60 seconds), it will still be terminated. Be sure to choose a timeout value that is long enough to cover your scenario, but not too long to make shutdown time intolerable.

Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.