Building Automation Knowledge Base

Issue During communication issues with a Continuum BACnet controller, a large amount of the following error messages are seen in the controllers' error log. 0x8000001e 0x00236400 0x08023a50 0x4c000000 0x00000000 BACnet request timeout 0x00001408 0x0023a600 0x080af632 0x000000bc 0x00000284 Not enough memory Product Line Andover Continuum Environment BACnet Controllers Cause Most likely due to incorrect configuration or excessive BACnet traffic..... or both. Resolution Check the following: What is the version of Controller Firmware being used in each controller? This needs to be checked against the Continuum Compatibility Matrix to ensure that it is compliant with the version of Continuum being used on the SQL Server Are BBMDs configured on this site? If so, where are they located and how are they configured? Confirm the "maxinfoframes" value currently set for all controllers. By default, a bCX for example should be set to 8 By default, b3 controller should be set to 2. If these are different from the default then why this has been changed? Confirm the BACtMaxMaster value in each is set to the maximum b3 NodeID + 1. This defaults to 127 but can cause comms delays on a smaller network. Confirm that all controllers on the MSTP are configured for the same Baud Rate. Any talking at a different baud rate would seem like noise on the network and disrupt communications, resulting in many 1408 error messages. Check the COV increment on points. The default of 0 can cause too much traffic on the bus and should never be left at Zero

Issue Replacement for defective controller is unable to be brought online in Security Expert. The online status is offline and last download shows as failed. controller status A review of the event server diagnostic window shows it is full of "Unencrypted event packet received" messages. event server diagnostics window Product Line EcoStruxure Security Expert Environment Security Expert Client Security Expert controller (SP-C, SP-AC1, SP-ACX) Cause The previous failed controller had been setup for encrypted communications with the Security Expert server. Since the newly installed replacement controller did not have the encryption keys to be able to decode the packets from the server it was not able to be brought online. Resolution On the controllers Configuration tab press the Disable controller encryption, then Yes to confirm. Wait for communications to be established with the controller, review the controller health status and update any modules that require it. To re-initialize encrypted communications with the controller press the Initialize controller encryption button to establish a new encryption key with the new controller. controller encryption buttons

Issue Troubleshoot Security Expert Controllers showing offline in the client. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require some common troubleshooting steps to help determine why controllers may be offline to the client. Resolution The main items to check are: Refer to the Troubleshooting Security Expert Controller Connectivity - Application Note on Exchange. If a controller has failed and the Replacement controller unable to be brought online then check if controller encryption had been enabled on the replaced controller. Restart the client software. Power restart the controller. Remove power Wait for all LED's on the controller to go completely off Apply power to the controller. In the controller web interface, on the Settings page, check that Event Server 1 has the correct IP address. Check that the Firewall is disabled. Check any Anti-Virus Firewalls/settings as well. If the Firewall cannot be disabled, ensure that all required ports are open between devices. See SX-SRVR Security Expert - Network Administrators - Installation Guide for details. Restart the Security Expert services under the PC's Services option in Control Panel. These need to be restarted when any changes are made. Confirm that the User Interface, Data Server, Event Server and Download Server module versions are all the same. Go to About  > Version and check there. If the database has not been upgraded to the same version as the client software, then this can cause communications issues. On the Security Expert Server check that MSMQ is installed as this is now a requirement   Security Expert MSMQ is required (Not showing live point status / shows "Unknown Status" error)   If MSMQ was installed after Security Expert, you'd need to reinstall Security Expert to allow it to run correctly. If MSMQ is installed and controllers are still not coming online (or the controllers are "bouncing" offline/online) then anecdotal evidence suggests enabling Windows 8 Compatibility Mode may help especially for Windows Server 2016 and Server 2019. Set the Windows 8 Compatibility Mode checkbox in the Properties page for C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertEvtSvr.exe   Also, note that if a database backup has been imported, then there is a need to check/change some other settings as well to ensure everything is set up for the specific server and controller.   Under Global > Download Server confirm that your computer name is the name of the PC where the download server service is running. Under Global > Event Servers ensure that the computer name is the name of the PC where the event server service is running. Under Sites > Controllers confirm the Serial number, IP Address, Download Port, Download Server and Control and Status Request Port match what is set in the controller's configuration web page (browse to the controllers IP Address to view). On that same General tab go to Diagnostic Windows and open the download and event server windows. Review the information contained and if there are any errors shown. Right click the controller and select Get Health Status. Review the status messages displayed.

Issue How does the controller determine which workstation will log the alarm into the SQL database when using "Enhanced Alarm logging"? Product Line Andover Continuum Environment Workstation Enhanced Alarm Logging Cause Alarms will be delivered by a NetController to all Workstations that have Ids between 191 and 254 assuming a teach was done. The first Workstation to receive the Alarm will log it in the Database. There is a ratcheting algorithm that is used by the NetController to determine which Workstation will be the first one to receive Alarms. In many applications, it is necessary to control which workstation will be the first to receive the alarm and log it in the Database. Knowing how the algorithm works provides the ability to design a system with a designated alarm logging workstation. Resolution The algorithm is as follows: The Netcontroller will take its own AccNetid and mask it with 63 stripping off the 2 high bits of its id leaving a result in the range of 1 to 63. Further explanation of the binary masking: NetControllers with Ids between 1 and 63, result is their ID. NetControllers with Ids between 64 and 127, result is their ID - 64 (ID range of 0 to 63). NetControllers with Ids between 128 and 190, result is their ID - 128 (ID range of 0 to 62). That result is then added to 190 and that is the ID of the first Workstation to get the Alarm and Log it in the Database. If there is not a Workstation with that ID (or the workstation with that ID is offline), the NetController will send the alarm to the Workstation with the next highest ID above the one calculated by the ratcheting algorithm. If none of the Workstation Ids are higher than the one calculated, the routine will loop around and use the lowest Workstation ID to send to the first. Example 1: NC1, id1 NC2, id2 NC3, id3 WS1, id191 WS2, id192 WS3, id193 Result of ratcheting routine: NC1 sends to WS1 first NC2 sends to WS2 first NC3 sends to WS3 first Example 2: NC1, id1 1+190=191 NC2, id2 2+190=192 NC3, id3 3+190+193 WS1, id201 WS2, id202 WS3, id203 Result of ratcheting routine: NC1 sends to WS1 first NC2 sends to WS1 first NC3 sends to WS1 first Example 3: NC1, id101 101-64=37, 37+190=227 NC2, id102 102-64=38, 38+190=228 NC3, id103 103-64=39, 39+190=229 WS1, id191 WS2, id192 WS3, id193 Result of ratcheting routine: NC1 sends to WS1 first NC2 sends to WS1 first NC3 sends to WS1 first

Issue When attempting to log into a server, the error message "Failed to establish connection with server" appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Servers Cause WorkStation is unable to make a connection to the desired server for one of several reasons. Resolution Unable to log into the Enterprise Server Verify that the Enterprise Server is running Go to Start Software Administrator Verify that the Server Status is Running. If it is stopped, then click the Start Service button, and click OK. Log into the server through Workstation. Lockout after restoring a backup set If an enterprise server backup set has just been restored, it may take several minutes for the server to return online, depending on the database size. Wait for the server to come back online and try logging in again. Unable to log into the Automation Server Verify the Ethernet connection Go to Run > cmd. Ping the IP address of the automation server. If it fails to communicate to the controller, verify that the ethernet connections are good and that there are no IT issues. Lockout after restoring a backup set If an automation server backup set has just been restored, it may take several minutes for the server to return online, depending on the database size. Wait for the server to come back online and try logging in again. Verify the IP address Go to Device Administrator  Connect to the Automation Server with a USB cable. Select the automation server once it is visible in the Device Administrator window and click on its name. Note: If the device indicates "Password Required," - Login into the automation server (default login is admin, and password is admin). Once the details open - Select the Ethernet 1 Configuration option and verify or enter the IP address details. After applying the information, enter this IP Address in WorkStation "Server" option to log on.  For further troubleshooting help see the following online help topic: Failed to Establish Connection

Issue The following record is seen in trace logs of EBO servers that have a BACnet Interface:   nsp.pin.BACnet.VariableProperty PollingVariableProperty: variable is a zomby!! Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server Cause A zomby variable is the BACnet plugin coming across an object that will be deleted but has not yet. Resolution No further action is required.

Issue Connected to a remote site network via WorkPlace Tech and a VPN connection, but unable to see the sites BACnet devices. No I/A Series MNB-1000s, or any 3rd Party BACnet devices, are found in Workplace Tech or the Commissioning Tool. Product Line TAC I/A Series Environment MNB-1000 WorkPlace Tech (all versions) Cause The VPN does place the connecting WorkPlace Tech PC on the site network, but the BACnet/IP (MNB-1000 and 3rd Party) devices are on a different subnet then the subnet assigned to the WorkPlace Tech PC. Resolution When BACnet/IP devices are on different subnets, BBMD must be used in order for the BACnet/IP devices to communicate across IP subnets. Only one BACnet/IP device can be enabled as BBMD per subnet.   Setup the MNB-1000 as a BBMD device using the Commissioning Tool Open Device Properties of the MNB-1000 controller and select the IP tab. For Device Type select BBMD and save change. Setup WorkPlace Tech to connect to the BBMD device Select Tool from the WPT Select Configure Communication… Select BACnet and click on Change Select IP and click next Select Access a remote internetwork. For Host BBMD Address, enter the IP address of the MNB-1000 which was setup as a BBMD device. Click the Finish button to save changes. You should now be able to see and connect to the I/A Series and 3rd Party BACnet devices using WorkPlace Tech.

Issue All inputs on an Continuum Infinet controller read 999.99 when viewing the electrical value "elecvalue" Product Line Andover Continuum Environment Infinet Controller Cause This indicates that the internal voltage reference is "out of range". Resolution Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input.  Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded.  If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables.  If the interference is being caused by the end device such as an auxiliary contact from a high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation.  If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network.  This will eliminate this unit having a duplicate ID on the network and it will also run the power up diagnostics.  Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems.  The easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the powerstrip of the controller and the shield of the Infinet.  This method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Lastly, a board or controller replacement may be necessary

Issue There is a requirement to change the WebReport server name. Product Line EcoStruxure Building Operation Environment Building Operation Report Server Building Operation WebReports SQL Server Cause Changing the WebReports server name after the WebReports software has been installed, does not change the PC name references in the WebReports or the database. Resolution If possible, ensure that the PC name will not need to be changed after the PC has been configured for WebReports. If having configured a PC for WebReports, the PC name has to be changed, then backup all SQL data first then uninstall the WebReports software, ensuring that the following process is followed step by step. Below is an overview of the uninstall process, the exact details are shown in section 15.11 of the WebReports Reference Guide. 15.11 Uninstalling WebReports Complete the following tasks to uninstall WebReports and the WebReports database: Uninstall the WebReports application and services using Windows Control Panel Delete the WebReports database using Microsoft SQL Server Management Studio Delete the WebReports reports using SQL Server Reporting Services Report Manager Remove the virtual directories for WebReports and the WebReports service using Internet Information Services (IIS) Manager Remove the WebReports application pools using the Internet Information Services (IIS) Manager Delete the appuser and IUSR accounts (if they exist) using SQL Server Reporting Services Report Manager, Microsoft SQL Server Management Studio, and Windows Computer Manager. Please note that having uninstalled the WebReports software, follow the steps shown on the following Microsoft website: Rename a computer that hosts a stand-alone instance of SQL Server - SQL Server If this procedure fails then SQL Server should also be reinstalled after having changed the PC name first.

Issue When trying to create or update a Security Expert database the error 'Invalid Database Server is displayed Product Line EcoStruxure Security Expert  Environment EcoStruxure Security Expert  Microsoft SQL Server Cause The path to the SQL Server from the Client is incorrect or inaccessible and will not resolve Resolution There are a number of resolutions to this issue depending on the cause. This article mainly focuses on a configuration where the Security Expert and Microsoft SQL Server are on separate PCs. The error can happen locally also but is less likely. One or more of these resolutions may be required to fix the issue. 1. The Server / Instance name is incorrect when typing it into the Database Server dialogue box during installation. (Local SQL Server) Default Database Server Dialog Box    There can be some confusion on what to enter into the dialogue box because, by default, the instance name and the main database name are the same. Ex. Server Name\Instance Name    Database       localhost\SecurityExpert            Security Expert   (Remote SQL Server) Ex. Server Name\Instance Name    Database       SVR19SQL19\SecurityExpert     Security Expert Note: If just the ServerName SVR19SQL19 or SVR19SQL19\SecurityExpert\Security Expert The Invalid Database Server error would occur   Copy and Paste the Server and Instance Names using SQL Management Studio (SMSS) This method can help to avoid typing errors Install SMSS on the same PC that has Security Expert Installed or use SMSS on the SQL server with Remote Desktop From the Connect to Server dialog> Server name, select <browse for more...> Select Network Server and then select the remote SQL server and click OK Right Click> Copy on the blue highlighted server name and instance Paste into the Security Expert Database Server Dialog box   For a detailed description of Instanced and Database, click on the following link Microsoft Database and Instance Article  Note: Try using the IP address instead of the SQL server name. 2. Make sure SQL Server Service is running on the remote SQL server 3. If using a named instance, make sure the SQL Server Browser Service is running on the remote SQL Server 4. Ensure Firewalls have an open port for SQL server (default 1433) 5. Make sure the SQL Server is configured to allow remote connections 6. The Windows account being used to do the Security Expert Installation must have access to create the database on the remote SQL Server.  7. Check the Windows Application and System logs on the Security Expert and SQL Server for errors related to the Security Expert Install, DNS or Connection errors 8. Examine the SQL Server Log for error messages   Ex. If Active Directory is being used, the error “The SQL Server Network Interface library could not register the       Service Principal Name (SPN)” This issue can be fixed by giving the domain account the appropriate permissions in Active Directory. Permissions required are:  ServicePrincipalName: Read  ServicePrincipalName: Write   Log in to the server running your Active Directory service and execute the following steps: Run Adsiedit.msc In the ADSI Edit snap-in, expand Domain [YourDomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= [YourAccountName, and then click Properties. In the CN= AccountName Properties dialog box, click the Security tab. On the Security tab, click Advanced. In the Advanced Security Settings dialog box, select one (any) of "SELF"'s row Click Edit, Open Permission Entry dialog box. Make sure the Principal is "SELF", Type is "Allow" and "Applied to" is "This Object Only", in the Properties section, select the properties below: Read servicePrincipalName Write servicePrincipalName Click OK to apply all changes and exit the ADSI Edit snap-in Finally, you need to restart the SQL Service(s) that use the account in question.   9. If you are still unable to get passed the "Invalid Database Server' error, please open a case with Technical Support.

Issue Need to connect MicroNet system to EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Automation server Enterprise Server MicroNet interface Cause MN-Mi interfaces are obsolete, need to find another way to connect to EcoStruxure Building Operation system. Resolution A MicroNet system uses one of two communications protocols, Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet). If the protocol being used is NCP, the MicroNet LAN can be connected directly to the AS-P/ES, A MicroNet interface can be added and configured. If the protocol adopted is ARCnet, this does require the MN-Mi, to convert from RS 232 to ARCnet, the MN-Mi would be connected to the AS/ES using an RS232-485 converter. If the MicroNet controllers are the older 100 series version, it may be possible to remove the auxiliary ARCnet cards, and reconfigure the MicroNet controllers and LAN to use NCP protocol. If the MicroNet controllers are the 50 series type the cannot be re-confirmed as the communications components are on the main board. PA-00246 provides more information on the possible connections.

Issue With a Sigma 4.0.8 installation using a software license, when adding the entitlement ID to License administrator. The message “Unable to connect to "Server" is displayed. Product Line EcoStruxure Building Operation Environment Enterprise Server Sigma License administrator Cause When adding the Sigma entitlement ID to EBO License administrator, an internet connection is required to allow the license administrator to connect to the on-line licensing server. Resolution When a PC is not connected to the internet, and you need to activate a software license entitlement, an Offline Activation Tool is available, this can be downloaded here.

Issue The ability and procedure to identify the version of Sigma software on a system. Product Line Satchwell Sigma Environment Release number: 1, 2, 3, 3.1, 3.3, 3.4, 3.6, 3.7, 3.7 SP2, 3.7 SP3, 3.10, 3.11, 4.00, 4.00 SP2, 4.00 SP4, 4.01, 4.01 SP1, 4.01 SP3, 4.01 SP4, 4.01 SP4a, 4.01 SP5, 4.02, 4.03, 4.03 SP1, 4.04, 4.04 SP1, 4.04 SP2, 4.04 SP3, 4.05, 4.05 SP1, 4.05 SP2, 4.05 SEB, 4.06, 4.07, 4.07 SP1, 4.07 SP2, 4.08 Build number: 1.52, 2.13, 3.12, 3.17, 3.3, 3.31.1, 3.32.10, 3.33.9, 3.33.11, 3.33.13, 3.34.11, 3.34.11, 3.36.11, 3.36.16, 3.36.20, 3.37.08, 3.37.09, 3.37.12, 3.37.13, 3.37.16, 3.37.18, 3.39.09, 3.40.06, 3.40.09, 3.41.14, 3.41.15, 3.41.16, 3.41.18, 3.41.19, 3.42.34, 3.42.43, 3.42.48, 3.43.18, 3.44.14, 3.44.16, 3.44.18, 3 45 48, 3 45 51, 3 45 58, 3.46.57, 3.46.62, 3.46.70, 3.46.72, 3.46.73, 3.46.79, 3.46.80 3.46.81, 3.46.85, 3.46.86, 3.46.89, 3.46.98, 3.46.104, 3.46.105, 3.46.107, 3.46.108, 3.46.110, 3.46.111 Cause Software installed is identified with a build number and not a release number. Resolution To view the Sigma build number, using a Sigma client running locally on the Sigma server, select About System Manager from the Help menu. The displayed window shows the Sigma release and build number Refer to the table below to find the Release No. Sigma Release No. Build No. Software/Firmware File Date   SigmaX   Release 1 1.52 Software/Firmware 22.06.2001 SigmaX 4.5 Release 2 2.13 Software/Firmware 14.02.2002 SigmaX 5.2 Release 2 3.12 Supplement 14.02.2002 SigmaX 5.2 Release 3 3.12 Software 31.07.2002 SigmaX 5.2 Release 3.1 3.17 Software 17.09.2002 SigmaX 5.2 Release 3.3 3.3 Software 30.07.2003 SigmaX 5.2 Release 3.4 3.31.1 Software 03.10.2003 SigmaX 5.2 Release 3.6 3.32.10 Software 19.11.2003 SigmaX 5.2 Release 3.7 3.33.9 Software 22.12.2003 SigmaX 5.2 Release 3.7 SP2 3.33.11 Software 27.01.2004 SigmaX 5.2 Release 3.7 SP3 3.33.13 Software 19.02.2004 SigmaX 5.2 Release 3.10 3.34.11 Software 21.04.2004 SigmaX 5.2 Release 3.11 3.34.11 Supplement 31.08.2004 SigmaX 5.2 Release 4.00 3.36.11 Software 16.12.2005 SigmaX 6.0.1 Release 4.00 SP2 3.36.16 Software 02 03 2006 SigmaX 6.0.1 Release 4.00 SP4 3.36.20 Software 23.05.2006 SigmaX 6.0.1 Release 4.01 3.37.08 Software 07.09.2006 SigmaX 6.0.1 Release 4.01 SP1 3.37.09 Software 26 09 2006 SigmaX 6.0.1 Release 4.01 SP3 3.37.12 Software 20 10 2006 SigmaX 6.0.1 Release 4.01 SP4 3.37.13 Software 13 08 2006 SigmaX 6.0.1 Release 4.01 SP4a 3.37.16 Software 17 11 2006 SigmaX 6.0.1 Release 4.01 SP5 3.37.18 Software 05 01 2007 SigmaX 6.0.1 Release 4.02 3.39.09 Software 26 01 2007 SigmaX 6.0.1 Release 4.03 3.40.06 Software 06 06 2007 SigmaX 6.0.1 Release 4.03 Sp1 3.40.09 Software 09 08 2007 SigmaX 6.0.1 Release 4.04 3.41.14 Software 27.02.2008 SigmaX 6.0.1 Release 4.04 SP1 3.41.15 Software 09.05.2008 SigmaX 6.0.1 Release 4.04 SP2 3.41.16 Software 15 09 2008 SigmaX 6.0.1 Release 4.04 SP3 3.41.18 Software 08 01 2009 SigmaX 6.0.1 Release 4.04 SP4 3.41.19 Software 08 01 2009 SigmaX 6.0.1 Release 4.05 3.42.34 Software 06 11 2009 SigmaX 6.0.1 Release 4.05 SP1 3.42.43 Software 22 03 2010 SigmaX 6.0.2 Release 4.05 SP2 3.42.48 Software 26.08.2010 SigmaX 6.0.2 Release 4.05 SEB 3.43.18 Software 08 12 2010 SigmaX 6.0.2 Release 4.06 3.44.14 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.16 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.18 Hotfix 01 02 2012 SigmaX 6.0.2 Release 4.07 3 45 48 Software 20 08 2012 SigmaX 7.0.6 Release 4.07 SP1 3 45 51 Service Pack 09 12 2012 SigmaX 7.0.6 Release 4.07 SP2 3 45 58 Service Pack 20 12 2013 SigmaX 7.0.6 Release 4.08 3.46.57 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.62 Hotfix 21.05.2014 SigmaX 7.0.7 Release 4.08 3.46.70 Hotfix 23 07 2014 SigmaX 7.0.7 Release 4.08 3.46.72 Hotfix 04 08 2014 SigmaX 7.0.7 Release 4.08 3.46.73 Hotfix 12 08 2014 SigmaX 7.0.7 Release 4.08 3.46.79 Hotfix 08 10 2014 SigmaX 7.0.7 Release 4.08 (**1) 3.46.80 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.81 Hotfix 17 02 2015 SigmaX 7.0.7 Release 4.08 3.46.85 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 3.46.86 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 (**2) 3.46.89 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.98 Hotfix 14 12 2016 SigmaX 7.0.7 Release 4.08 (**3) 3.46.104 Software 28 02 2017 SigmaX 7.0.9 Release 4.08 3.46.105 Hotfix 10 03 2017 SigmaX 7.0.9 Release 4.08 (**4) 3.46.106 Software 28 03 2017 SigmaX 7.0.9 Release 4.08 3.46.107 Hotfix 08 08 2017 SigmaX 7.0.9 Release 4.08 3.46.108 Hotfix 01 05 2018 SigmaX 7.0.9 Release 4.08 (**5) 3.46.110 Software 13 05 2019 SigmaX 7.0.9 Release 4.08 (**6) 3.46.111 Hotfix 15 11 2019 SigmaX 7.0.9 Release 4.08 (**7) 3.46.131 Software 29 01 2020 SigmaX 7.0.9 Notes:   **1 Sigma build 4.46.57 with StruxureWare Building Operation v1.5 or 1.6 transition support program installed. **2 Sigma build 4.46.57 with StruxureWare Building Operation v1.8 transition support program installed. **3 Sigma build 4.46.57 with StruxureWare Building Operation v1.9 transition support program installed. **4 Sigma build 3.46.57 with StruxureWare Building Operation v2.01 transition support program installed. **5 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.1, v3.0.2 and v3.0.3 transition support program installed.. **6 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.4, v3.1 and v3.2 transition support program installed. **7 Sigma build 3.46.57 with StruxureWare Building Operation v3.2 or later transition support program installed.   Notes: 1. SigmaX version 7.0.9 is now available and can be used on any Sigma version that supported SigmaX version 7.0.6. 2. This information can be downloaded as a PDF file: Sigma Build Numbers 2023 3. When SigmaX 6.0.2 is installed, the build information provided by Sigma (Help > About) can be wrong (later than the actual version). This arises because SigmaX installs a file with Build 3.42.47 in the c:\sigma\bin folder. This is only a problem prior to Sigma Release 4.05 SEB.

Issue Attempting to log in with WorkStation and receive the following license error: No license available. Error -83: Version of vendor daemon is too old The following error is seen in System Log / Trace log:  Error Code: -83 Error message: Version of vendor daemon is too old Building Operation Software Administrator Product Line EcoStruxure Building Operation. Environment Building Operation License Administrator Building Operation License Server Cause The most common cause is that the License Server is older than the current release of Building Operation software.  This occurs during upgrades and if the License Server used for the product has not been upgraded.  Ensure both components of the License Administrator are selected (as shown below) when performing the upgrade/installation.     Resolution To confirm the issue open the Windows Services and check that the version shown in the services is valid for the products installed.  The version shown should be at the same version or higher than the other Building Operation software installed.     To resolve the issue, upgrade the License Server component of the License Administrator installation software. 

Issue When being discovered by a 3rd party system what names will be seen? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS-P, AS-B, AS) Cause How is an Enterprise Server or Automation seen by a 3rd party system? Resolution The Enterprise Server (ES) and Automation Server (AS) conform to a specific BACnet Protocol Revision depending on version and firmware and the capabilities of a particular BACnet implementation are described in the Protocol Implementation Conformance Statement (PICS).  The PICS contains, amongst other details, a list of all standard and proprietary object types that are supported.  Please see BACnet Testing Laboratories (BTL) for a Listing of Tested Products.    For each object type supported the PICS describes: any optional properties that are supported which properties can be written-to using BACnet services if the objects can be dynamically created or deleted using BACnet services any restrictions on the range of data values for properties For a third party to discover an ES or AS it needs to be a BACnet Operator Workstation (BOWS).  Please see BACnet Testing Laboratories (BTL) for a list of tested BACnet Operator Workstation (B-OWS) and BACnet Advanced Operator Workstation (B-AWS)   Of the objects types detailed in the PICS the specific BOWS will determine what properties are shown.  An application such as YABE can provide an indication of these properties.  For example with a device the Vendor Name (1), Protocol Revision (2), Object Name (3),  Model Name (4) and Firmware Revision (5) are amongst the properties available. For an object such as an analog point the Object Name (6), Present Value (7) and Object Identifier (8) are examples of what will be seen.    Every BACnet device contains a device object that defines certain device information, including the device object identifier or instance number.  For additional information please see Introduction to BACnet.  

Issue Automation Servers are being connected to an IT managed network. The network requires that devices broadcast their MAC address in order to be added to the network switch. Automation Servers are not broadcasting their MAC address to the switch  and cannot be added to the network Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause A stand alone AS-P server with a fixed IP address does not send out anything on the IP network. Resolution If you need the AS-P server to send out some traffic, you could define an NTP server that generates traffic when synchronizing the time.

Issue When opening a dashboard graphic, the system operates very slowly.  Navigation to other links with the Dashboard displayed, and clicking on a linked graphic does not display immediately.  Product Line EcoStruxure Building Operation Environment Building Operation 3.2.3 and higher Building Operation Automation Server Bundles (AS-B) Building Operation WebStation  Cause Typically when a large number of stored values (100,000 per trend log) is needed to be displayed within the Dashboard widget (e.g., Period Chart) with a significant number of trend logs to be displayed (five or more) in the Dashboard, this will put excessive load on the AS-B and hence stops any or all navigation thereafter.   Dashboard widgets typically continue to read data required to be displayed after closing (or navigating away). This is to keep those logs cached for a few minutes after the dashboard is closed, so if the same logs are loaded again, then the data is available. Any calculations are always done on the client, regardless of whether a chart, dashboard, or trend list is shown. The same is also true for WorkStation. Resolution Below are some considerations to look at improving the overall performance when dealing with this issue: Reducing the number of storage records from 100,000 to something more reasonable for the dashboard to display (5,000 - 8,000) Having these logs stored on the Enterprise Server and Dashboard operated from the Enterprise Server.    If large storage is necessary, then create or use different logs for display within the Dashboards widgets.  If the intention is always to show calculated values, use log processor trend logs. Log Processing Trend Log. These can be pre-calculated and thus contain only a fraction of the full source log's data amount. Upgrade to the later version (EBO 2023) as many optimizations have been made for Dashboards since 3.2.        

Issue There can be confusion on the differences between EcoStruxure Energy Expert (formerly Power Manager) and EcoStruxure Power Monitoring Expert (PME)  Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Building Operation  EcoStruxure Energy Expert (formerly Power Manager) EcoStruxure Power Monitoring Expert Cause Power Monitoring Expert (PME) is a long-established product in the Schneider Power (EMS) offer and so its place in the market is well known and its support path is very clear. Energy Expert is a much newer offering that intentionally sits nearer to EcoStruxure Building Operation (EBO) in the BMS community, while still remaining an EMS product and so its place in the market and support path is more easily confused. Resolution Definitions   EcoStruxure Power Monitoring Expert (PME) Schneider Electric's supervisory software dedicated to power monitoring that enables you to maximize operational efficiency, optimize your power distribution system, and improve bottom-line performance   EcoStruxure Building Operation (EBO)  Schneider Electric's premier building management system (BMS) providing integrated monitoring, control, and management of energy, lighting, HVAC, and fire safety.   EcoStruxure Energy Expert (EE)                                                    Designed to offer Power Monitoring Expert (PME) features to new and existing EcoStruxure Building Operation (EBO) projects, giving extra capabilities to manage power utilization in a BMS environment.   It utilizes EcoStruxure Web Services (EWS) to be able it to share data between the two EcoStruxure software platforms. (EBO and EE) and applications such as the ETL Tool and the Integration Utility in the integration process.   EcoStruxure Web Services (EWS) The Schneider Electric standard for sharing data among various Schneider software platforms to facilitate the creation of EcoStruxure Solutions. Based on conventional Web Services technology (SOAP, WSDL)   ETL Tool The function of the ETL is to extract select historical data (Trend logs) from EBO, and load that data into the Energy Expert SQL database for use in Dashboard and Reports etc.   Integration Utility The function of the Integration Utility is to export Energy Expert Dashboards, Reports and Alarms for import into EBO to enhance its Power Offer to the customer   Product Support Path: PME, Energy Expert, ETL and the Integration Utility are are all fundamentally Power Products and so should always be raised through your local Product Support Team (via your Customer Care Center (CCC)) under an EMS commercial reference. However in cases where an Energy Expert project needs specific assistance with the EBO side of the integration then a BMS commercial reference should be used instead.

Issue During Energy Expert installation an error is shown, and the floating license manager is never installed Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert (formerly Power Manager) Installation Cause "Error 1722" occurs due to a conflict between the version of Java installed on the PC and the version included in the EE installation package Resolution Uninstall all versions of Java from the PC Install the JavaRuntime manually from the install media "..\setup\SetupSupport\Licensing\JavaRuntime\x86\jre1.7.0_02.msi" Run the complete installation again

Issue How is the Real Time Clock (RTC) maintained when a Automation Server loses power since there is no battery on the AS. Product Line EcoStruxure Building Operation Environment Automation Server (AS-P, AS-B, AS) Real-time clock Cause Documentation Resolution Each Automation Server has a dedicated capacitor that backs up the RTC chip.  Please consult the tables below or use the Webhelp links and search for 'Real-time clock':-   AS-P Real-time clock Accuracy in runtime mode NTP server Accuracy in backup mode, at 25 °C (77 °F) +/-52 seconds per month Backup time, at 25 °C (77 °F) 10 days   AS-B Real-time clock Accuracy in runtime mode NTP server Accuracy in backup mode, at 25 °C (77 °F) +/-52 seconds per month Backup time, at 25 °C (77 °F) 10 days   AS Real-time clock Accuracy, at 25 °C (77 °F) 47 to +73 seconds per month Backup time, at 25 °C (77 °F) 30 days