Building Automation Knowledge Base

Issue Netcontroller is running slowly or occasionally goes offline (bCX NC2 ACX CX) Product Line Andover Continuum Environment Continuum Netcontroller, Net Controller, Infinet, MSTP, Bacnet, Xdriver, x-driver Cause There are various reasons why the operation of one or more Netcontrollers and or attached controllers is slow and/or goes offline occasionally.  This guide is primarily to help collate the right information which may identify the issues.  If the reason cannot be identify then this information can be provided to support for further analysis. Resolution General troubleshooting techniques should be used. Define the exact problem. What exactly is slow? eg. Sending to the controller or its connected devices, opening or refreshing graphics, opening or refreshing points, updating Xdriver points, saving programs, creating new points. Is the controller slow from all cyberstations? Is the controller always slow? If not then try to find what makes it go slow, it is time related? Can certain steps be taken to cause the slowness or offline to happen? Get a screen capture of any errors. Gather site information. Continuum version, Continuum hotfixes and service packs applied, number of Cyberstation. Cyberstation operating system, details of Ethernet network and subnets used, with BBMD information of Bacnet sites (Asbuilt or a spreadsheet with IPs, etc.) Continuum Analyzer report, site controller map or spreadsheet or text dump Check the PCs running Cyberstation, do they meet the system specifications? Gather controller information What is the Scan rate? Is the controller time sync. correct? How many objects are on the controller, how many programs are running? What is the firmware version of the netcontroller and b3 or i2 controllers? Ethernet connection - Is the controller on the same subnet as the Cyberstations? A wireshark trace may help to establish the quantity of traffic on the Ethernet (See Using WireShark to analyze communications on an Ethernet network) Comms Ports - XDriver being used? What is on the comms ports? Xdriver (how much communications, points etc) Comms Ports - Bacnet MSTP - How many b3 controllers? How much extended logging? How many alarms being sent? How many 3rd party devices? Look at bacnet settings, how many values are being sent across the network? Check COV settings. Try removing the MSTP cable from the bCX (there could be an issue with an MSTP device causing the bCX to go offline/go slow) Comms Port - Infinet - How many infinet controllers? How much extended logging? How many alarms being sent? Look at infinet settings, how many values are being sent across the network? Check port reconfigs and errors. Try removing the infinet cable from the NetController (there could be an issue with an infinet device causing the NetController to go offline/go slow) Comms Port - other. Again try removing the comms cable from the NetController (there could be an issue with a device on this network causing the NetController to go offline/go slow) Run the Controller error log tool to gather the controller errors See Gather Continuum Controller error logs if requested by Product Support for troubleshooting If the controller goes offline, run the alarm listview.  Does it line up with the Controller error log? Check the CPU LED flash rate on all connected devices (i1, i2, b3 etc) as Can't bring bCX online in Continuum but do get a response to pinging its IP address, also the RD and TD LEDs should be checked for anything unusual This guide is primarily to help the on site engineer by helping them to assess the site. If there is still a need to contact support, please review and record as many items above as possible and send them to the case owner.  Further tests can be carried out including an ACCtrace to determine if the restriction could be at the Cyberstation, See How to capture Continuum Cyberstation activity using ACCTrace NOTE: Ensure all Cyberstations, Controllers and other laptops used for logging are in time synchronization before recording any logs. If it is believed there is an issue with the Infinet or MSTP network see Infinet and mstp bus troubleshooting If it is believed the problem is with extended logging see Extended Logging gaps, performance and load balancing It is possible that something connected to the controller causes the controller to go offline, try disconnecting all other cables and connections to the controller and then re-testing Where a controller is offline when connected directly to a PC/Laptop, try resetting the IP address, otherwise the controller will probably need replacing. NOTE Disconnecting all networks from the NetController is often a good starting point (reconnected IP/Ethernet cable)  

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 Does EcoStruxure Building Operation support virtualization?  Can the Enterprise and Reports server be on a virtual machine? Can EcoStruxure Building Operation be installed in cloud environments? Product Line EcoStruxure Building Operation Environment VMWare Hyper-V Microsoft Azure Amazon Web Services EcoStruxure Building Operation 2.0 through current release. Cause Desire for virtualization or cloud environment. Resolution Emulating environments Virtualization has several interpretations. In this article, we'll specifically address running EcoStruxure Building Management software in emulating environments like VMware or Hyper-V. These emulating environment software packages replicate a physical PC environment, allowing multiple computers to operate on a single machine, hence the term "virtualization". Several software vendors offer emulating systems, with VMware and Hyper-V being the most prominent. The advantages of running an emulating environment include reduced physical machines, minimized space requirements, and lower maintenance costs.   It's important to note that other potential meanings of "virtualization" such as remote desktop, remote control software, terminal server environment, or cluster environment are not covered in this article.   EcoStruxure Building Management in emulating environments Currently, numerous installations are running EcoStruxure Building Management on VMware and Hyper-V without significant issues. Some challenges have been observed related to Veeam setup, which doesn't seem to integrate seamlessly with ES (and possibly EC).   VMware is utilized internally in R&D and Product Support teams with positive feedback on its performance. Users should have familiarity with the emulating product to configure settings correctly, ensuring network functionality. It's important to highlight that no specific efforts have been made to develop EcoStruxure Building Management to comply with emulating environments. Additionally, there are no specific tests to verify its functionality in emulating environments. Certain issues have been seen with the License system used by EcoStruxure Building Operation when running on specific emulating environments due to limitations in the license system's support for these environments.   Support for EcoStruxure Building Management installations running in emulating environments Product Support provides support for EcoStruxure Building Management software, irrespective of whether it runs on PC hardware or in an emulating environment. Support is provided for problems related to the EcoStruxure Building Management Software itself, but not for issues related to the environment it runs on. Except for approved operating systems and minimum memory requirements, Product Support does not offer guidance on configuring specific PC hardware or emulating environments. Cloud environments Cloud computing environments such as Microsoft Azure and Amazon Web Services provide on-demand availability of computer system resources without direct active management by the user. Cloud computing relies on sharing of resources and typically uses a pay-as-you-go model, which can help in reducing capital expenses.   One of the challenges of cloud computing is reduced visibility and control. Cloud users may not have full insight into how their cloud resources are managed, configured, or optimized by their providers. They may also have limited ability to customize or modify their cloud services according to their specific needs or preferences.   Support for EcoStruxure Building Management installations in Cloud environments EcoStruxure Building Operation has not been developed or tested with Cloud environments in mind and it is therefore not currently a supported environment.  

Issue No official internet download available unless you have user name and password access to Schneider Electric websites. Product Line Satchwell MicroNet Environment VisiSat Engineering Guide  Installation and User Guide 1.2 2.1  Cause Not available for download online Resolution Further information regarding this object can be found in the VisiSat help file and engineering guide. VisiSat V1.2 Engineering Guide This document provides details for IAC 400, IAC 420, IAC 600 and IAC Touchscreen configuration. VisiSat V2.1 (185) Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 (196) Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 Installation and User's Guide VisiSat V2.1 data sheet VisiSat V2.1 Release note Related Articles: MicroNet 100 series controller MLi's and Data sheets MicroNet 50 series controller MLi's and Data sheets Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue How to populate emailed event messages with specific event details. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Security Expert documentation is missing instructions on how to add specific object details to emailed event messages. Resolution 1. The following email tags can be inserted in the Message and Subject fields to dynamically populate the event email. <FIELDTIME> or <FIELD_TIME>   <EVENTID> or <EVENT_ID>   <LOGGEDTIME> or<LOGGED_TIME>   <FACILITYNUMBER> or <FACILITY_NUMBER>   <USERNAME> or <USER_NAME>   <CARDNUMBER> or <CARD_NUMBER>   <USERID> or <USER_ID>   <INSTRUCTIONS>   <DESCRIPTION>   <INSTRUCTIONS2> (second language)   <DESCRIPTION2> (second language)   <ALARM>   <COMMENTS>   <ACKNOWLEDGED>   <DOORNAME> or <DOOR_NAME>     2. Security Expert documentation is being modified to include this information on the email tags that can be used to populate email messages.

Issue I/A Series G3 Workbench unable to open platform for local host. Error indicates "Cannot display page. Workbench can only communicate with niagarad version 3 or higher." Environment I/A Series G3 Enterprise Network Server and Workbench (all versions) Cause The Niagara service for R2 is currently active. Resolution This error indicates the Niagara service for R2 is currently active. To correct, start the Niagara service for G3 by running the Install Niagara Daemon provided by the start menu for the G3 version required.

Issue What is the Sigma SUM password to close the application? Environment Sigma SUM Cause What is the Sigma SUM password to close the application? When shutting down the PC Sigma SUM asks for a password. Resolution The password is SUM. Sigma SUM is normally allowed to start up when the PC starts and runs in the background. Therefore SUM should be added to the start up items.

Issue Field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Environment MNB-1000 with firmware 1.50E and earlier only. Cause Field office needs to access the Web Service page so that they can  perform an Ethernet network packet capture for communications troubleshooting purposes. Resolution The Web Service page has been removed from the MNB-1000 Plant Controller firmware effective with release version 1.510.  The user-name is user The password is mnb1000

Issue How to use AutoCAD layout in TGML Graphic Product Line TAC Vista Environment Vista 5.1.9 and earlier versions of Vista 5 TGML Graphic AutoCAD Cause Sometimes it is necessary to use the AutoCAD layout in TGML graphic, for example, to use the plant layout as a background. The official support for importing AutoCAD files was removed early in the life of TGML. It can’t be guaranteed that EVERY file will import without a problem, so it is an unsupported feature. Resolution The following steps need to be followed: Open the drawing in AutoCAD Save as .DXF Open TGML Editor File Open the .DXF A screen should pop up saying converting DXF to SVG followed by converting SVG to TGML It is recommended to use the "Create path" command in the Object window in TGML for the converted graphic. Because the response speed of the computer will be very slow if used without this action. Note: Line widths and text will be in disorder because they are not imported along with the object. If the DXF file fails to import, here are some steps to try: Move every object in AutoCAD to a single layer Delete all unused layers in AutoCAD "Explode" complex objects in AutoCAD

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 After installing WorkPlace Tech Tool software version 5.8, only version 5.0 is shown in the Purchase License program product list. Environment WorkPlace Tech Tool software release 5.7.6 and later, including release 5.8 Cause The displayed list of software products shown in the Products list does not show version 5.7 or 5.8 Resolution The Purchase WorkPlace Tech Software license request program has been updated to include some additional licensing options. The licensing program product Part Number list was also revised to eliminate some confusion that has occurred in the past regarding license upgrades. The license product list now contains entries only for the major releases (4.0, 5.0, etc) instead of indicating the version that was current at the time the license product file was last updated.   One intent in this change was to eliminate the confusion regarding the need to purchase a WorkPlace Tech Tool upgrade license. When the WorkPlace Tech Tool software versions 5.7.6, 5.7.7 or 5.8 (or later 5.x.x release) has been installed on the computer, the following list shows two of the products that appear in the Purchase WorkPlace Tech Software license package list screen: WP-TECH-50     WorkPlace Tech 5 WP-TECH-50U  Workplace Tech 5 Upgrade The product code "WP-TECH-50U" is used to request a WorkPlace Tech Tool software license upgrade from release 4.0.x to any 5.x.x release of the WorkPlace Tech Tool software.  As a reminder, when ordering an upgrade license, proof of purchase of WorkPlace Tech version 4.x.x must be included with the license request form.  Suggested proof of purchase is the license request form for the previous version that was sent to the customer showing the generated unlock code. The product code "WP-TECH-50" is used to order a new customer license for any 5.x.x release of the WorkPlace Tech Tool software. Remember that a license upgrade is not required when a minor WorkPlace Tech Tool software upgrade is installed.  The major version upgrades are designated by a change in the first field of the release number, i.e., 4.0.3 is a version of major release 4.x and 5.7.6 or 5.8 are both versions of major release 5.x.x.

Issue Instruction on how to use your Entitlement to rehost Vista 5 License onto a new host computer or dongle. Product Line TAC Vista Environment Vista 5 Dongle Host ID Flexnet Licensing Entitlement Vista Licensing website Cause Limited documentation exists for how to properly rehost a Vista license on the Vista licensing website Resolution NOTE: Please remember that 5.0.X license files are not backwards compatible with versions of Vista 5.1.X. If your current license files are 5.0.X you must install 5.0.3 or earlier to properly rehost your license. Log onto https://schneider-electric.flexnetoperations.com and enter your Entitlement or Activation ID. To obtain an unknown ID, follow instructions in Lost license Entitlement ID Vista 5.x. In the top corner of the Home Page Select LICENSE SUPPORT and List Licenses This Entitlements license(s) will be listed. Select the License you wish to rehost by checking the Tick box located just left of the License. In the Action Menu, Select Rehost. Select Add New Host. From the Server Host Dropdown, select either ETHERNET (MAC address) or VENDOR DEFINED (Dongle) depending on your site. Enter the Mac address or Dongle ID to be used in the textbox *note that a Dongle ID must be entered as "TAC_HL_ID=##########" Select OK The New Server Hosts will now be populated with the correct Host ID. Click Next. Select Verify to verify the Host ID is valid Select Rehost to generate the new License. From the main page, select the License you wish to retrieve by checking the Tickbox located just left of the License. Select View and Save To File or Email license to obtain the .lic file. It may be a good idea to compare the old .lic file with the new .lic file in Notepad to ensure they contain the same features. It is possible that the site license was a combined license generated from multiple Entitlements. If this is the case, repeat the steps above for each Entitlement then follow instructions in Manually Consolidating License Files.

Issue Audible alarms and the DefaultAlarmView vs. new workspace with new alarmview Environment StruxureWare Building Operation site Cause Audible alarms and alarmview, Using the predefined alarmview we get the audible alert for this alarm. Create a new workspace with an alarmpane with a self defined alarmview we do not get the audible alert. Steps to reproduce problem: I created a digital value and one alarm connected with this digital value. I the settings of this alarm I checked the box audible. Then created a new alarmview without any filter. I created a new workspace (named ws01) with a system tree and one alarmpane. For the alarmpane I selected my created alarmview. Selected the workspace Engineering and triggered the alarm. Expected result: Alarm is in the alarmview Audible alarm This works Then logout of the workstation and login again. Now using the workspace ws01: trigger the alarm Expected: Alarm is in the alarmview Audible alarm Actual result: Alarm is in the alarmview No audible alarm.   Resolution Audible alert, works only in the DefaultAlarmView. Expected fix to be in 1.3 release of StruxureWare Building Operation. Work-around: None known

Issue A floating-point value is displayed incorrectly in a TGML graphic. The presentation field appears to show random numbers. The example shows how the value 11.60 is represented in a TGML graphic. 11.60 is actually stored as 11.600000381469727. In format presentation mode: In none presentation mode: The last 6 digits of the stored floating-point value are seen! Product Line TAC Vista Environment TAC Vista 5.1.X TGML editor 5.1.X A presentation text bound to a floating-point value. Cause Vista uses the PC's default settings for number of decimals, when presenting values in TGML graphics. Resolution To resolve the issue, either set the format property to "Presentation" for the binding object or change the PC's settings to view fewer decimal places eg. 2.

Issue Need to purchase and replace the battery for the IAC-TS and IAC-600. Product Line Satchwell MicroNet Environment IAC-600 IAC-TS Cause The battery has failed and requires replacement. Resolution The battery is a lithium crystal SNAPHAT M4T28-BR12SH1 These are available from RS Components. The RS Components stock number is 189-1239. Manufacturer name: STMicroelectronics Manufacturer's part number: M4T28-BR12SH1 Specifications Category Detachable Lithium Power Source Maximum Operating Temperature 70°C Minimum Operating Temperature 0°C Mounting Through Hole Pin Count 4 Product Height 8mm Product Length 21.84mm Product Width 18.03mm Supplier Package SNAPHAT   Documentation M4T28-BR12SH M4T32-BR12SH TIMEKEEPER SNAPHAT (battery and crystal) Data Sheet.pdf Statement of conformity.pdf

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

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

Issue Users or engineers may be unsure of how to access the best support for issues with EBO Smart Connectors, especially where site specific Smart Connectors have been developed, or believe the issue is with the underlying framework. Product Line EcoStruxure Building Operation Environment Integration Cause Unlike EBO, which is a standard EcoStruxure product that falls under normal R&D, the Smart Connector (formerly known as Mongoose) was developed by Schneider Electric Buildings Labs and a separate R&D Team.   Resolution If using a Smart Connector developed specifically for a project by a separate Integration Team within Schneider-Electric, then it is always best to go back to that team with your technical issues. In all other cases, the Smart Connector Framework is now supported via normal Product Support channels by raising a support case with your local Customer Care Centre, just as you would for any other EcoStruxure Issue.   The  SmartConnector Developer Forum: can still also still be found on the community.  

Issue If one Input is required to activate an Output and another Input to de-activate the Output, this Output can be defined by Input Types. The below is a simple scenario where when the first Input turns ON the Control Output turns ON, when the second Input turns ON the Control Output turns OFF. In this scenario we are activating a Duress alarm when an Input goes on and resetting that Alarm when the reset Input is triggered. Product Line Security Expert Environment Security Expert SP-C Cause Require detailed instructions on how to program a latching duress alarm scenario. Resolution Objects required:   1x Area - "Duress_Area" 2x Input Types - "Duress Enable", "Duress Reset" 2x Inputs - "VI Duress Trigger", "VI Duress Reset" 1x Output - "VO Duress Alarm"   Note: The above object names are what is used in this example, you can set these to whatever you require.     Instructions:   Creating the Area 1. Navigate to Programming > Areas. Add a new area (Duress Area), set the Entry and Exit Delay Times to 0. All other settings can be left default.   Creating the Input Types 1. Navigate to Programming > Input Types. Create a new Input Type (Duress Enable) 2. Set the Control Output to your Output (VO Duress Alarm). 3. Under Options 1 enable Generate Alarms. 4. Under Options 2 enable Activate Control Output on Alarm . 5. Set any other options that may be required. 6. Create a new Input Type (Duress Reset) and redo steps 2 - 5 above except under Options 2 enable Deactivate Control Output On Alarm.   Configuring the Inputs 1. Navigate to Programming > Inputs select the Input (VI Duress Trigger) and set the following: 2. Set the Area to the Dummy Area (Duress_Area) created earlier. 3. Set the Input Type to the Input Type (Duress Enable). 4. select the Input (VI Duress Reset) and set the following: 5. Set the Area to the Dummy Area (Duress_Area) created earlier. 6. Set the Input Type to the Input Type (Duress Reset).   Testing 1. Arm both portions of the Area 2. Activate the Input (VI Duress Trigger) to confirm Alarm is generated and Output Activates. 3. Activate the Input (VI Duress Reset) to confirm Alarm is generated and Output Deactivates. 

Issue Access Expert On-Premise setup needs procedures and tools to backup and restore the database Product Line Access Expert Environment Access Expert Premise Software V3 MongoDB Cause The procedures for backing up and restoring the MongoDB is documented online at the link below. https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/ However, these instructions do not outline how to use the commands (mongodump and mongorestore) within the Windows OS environment using specific examples. Resolution The following procedures are designed to fill in the gap for Access Expert administrators who need to do manual MongoDB Backup and Restore. These procedures assume that Access Expert V3 has been installed and is functioning normally. You will need 2 separate Command Prompts, run as Administrator, open for these procedures. Mongo DOS Shell to attach to and run commands within MongoDB environment Standard DOS Shell to run the Mongo backup and restore commands MongoDB Backup Ensure MongoDB service is running (Start> Run> services.msc) Open a Command Prompt as Administrator (referred to as the Mongo DOS Shell) Type mongo(command) Type show dbs (command) - shown above, to give a list of the dbs available) If the MongoDB service is "Running," but the client cannot connect when typing mongo, it's probably because the path to the mongo bin folder hasn't been added to the PC's environment. To Add a local path locations variable to a PC environment https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ee537574(v%3Doffice.14) Ex. C:\Program Files\MongoDB\Server\3.6\bin (This will vary based on the version of Mongo) Open another Command Prompt as Administrator (Standard DOS Shell) Use the CD command to navigate to where you would like the backup files to be created Ex. C:\Data mongodump (command) The mongodump command creates the dump folder with admin, Keep, Signalr subfolders MongoDB Restore In the (Mongo DOS Shell) Prompt show dbs (command) use Keep (command) (Case sensitive) db.dropDatabase() (command) Use the Command Prompt as Administrator (Standard DOS Shell) mongorestore (command) The window should indicate "Finished Restoring Keep.Events," "done" and RESTORE COMPLETE If there are “E11000 duplicate key error collection” Keep.Events errors, it’s because the collection events are already in the folder and need to be deleted first.   Steps to correct the E11000 duplicate issue: (Stop the service, delete and recreate the DB folder, restart service) Right-click on the MongoDB service and Stop (you can’t delete files while the service is running) Delete C:\Data\db folder (not the Data, only DB) MANUALLY CREATE THE DB FOLDER - Right Click > New Folder and name it DB Restart the MongoDB service - this creates the necessary files in the DB folder Once these steps have been done, rerun the mongorestore command mongorestore (command) Verify that users can log into Access Expert with this database