Building Automation Knowledge Base

Issue When installing Enterprise Server an error is received at the end of the installation:  Clicking on the Details button the following error is shown:  -EnterpriseServer Service registration Starting Execute: "C:\Program Files\Schneider Electric\StruxureWare 1.2\Software Administrator\SE.SoftwareAdministrator.exe" ES /Install --DatabasePath="C:\Documents and Settings\All Users\Application Data\Schneider Electric\StruxureWare 1.2\Enterprise Server\db" --HTTPPort="80" --HTTPSPort="443" --TCPPort="4444" SE.SoftwareAdministrator.exe --install returned -532462766 -EnterpriseServer Service registration Leaving Completed In Software Administrator the Status of the Enterprise Server is indicated as Not Installed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause It appears that the installation package has an issue with the authority to create the Enterprise Server Service, below are some options to try to rectify this.  Resolution SmartStruxure version 1.4 running on Windows 7 If this problem is encountered in 1.4 try the following steps Uninstall Enterprise Server software Restart PC Run the Enterprise Server installation software.  Use the Right Click "Run as administrator" option to ensure correct authority. Download and unzip this batch file Run the .bat file on the affected PC. Check the Software Administrator and confirm that the Server Status has now changed to "Running"   NOTE:  This batch file is only valid for 1.4 and will not work for 1.2 or 1.3.  Resolution #1 (Typically seen with SmartStruxure version 1.2) Changing the DCOM setting as described below has shown to allow for the installation process to complete. From the Start - Search programs and files entry type "dcomcnfg" and then select the dcomcnfg.exe file. Expand Component Services and also expand Computers. Right mouse click My computer and select properties and then select COM Security tab. Select the edit limits button from the  "Launch and activation permissions"  section. Select / Add the Everyone user and make sure all the permissions are set to allow   Reboot the computer. Then reinstall the Enterprise Server. Resolution #2 (Typically seen with SmartStruxure version 1.3) If Resolution #1 does not work or is not possible then you can manually add the Enterprise Server application manually.   Download and unzip this batch file Run the .bat file on the affected PC. Check the Software Administrator and confirm that the Server Status has now changed to "Running" NOTE:  This batch file is only valid for 1.3 and will not work for 1.2.  Alternative Workaround: Should neither of these options work.  You can run the Enterprise Server manually.  To do this: Locate the path: C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\bin Double Click on the file name: SE.SBO.EnterpriseServer.exe A DOS Command prompt will open and display the Enterprise Server System log.  This window must stay open.  If you accidently close it, it will force the Enterprise Server to close and shutdown.

Issue How to add Basic Authentication header to SendWebRequest function in Script RESTful Web Services Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause A 3rd party web service requires basic authentication for HTTP requests to ensure that data is requested securely, otherwise, the request will be rejected with an "Authorization Error".   Resolution Basic Authentication is a type of Authorization Request Headers, which transmits credentials as user-id/ password pairs, encoded using Base64, as defined in RFC 7617 - The 'Basic' HTTP Authentication Scheme (ietf.org).  Follow the below steps to create a Basic Authentication header in Script RESTful Web Services: Combine the User ID and the Password with a colon ex. "aladdin:opensesame". Encode the resulting string in base64 using script function to base64 encode a string posted in the Community or using the online encoder as Base64 Encode and Decode - Online, ex.  "aladdin:opensesame" will be "YWxhZGRpbjpvcGVuc2VzYW1l" after Base64 encoding. Construct SendWebRequest header in the following format:  Authorization: Basic <credentials>, as below example:  Headers= "Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l"'User ID=alaadin Password=opensesame Resultstring= SendWebRequest(BaseUrl,Method,ContentType,Headers,Message) Note: Basic Authentication is not a secure method of user authentication unless used in conjunction with HTTPS/TLS, as the user ID and password are transmitted as clear text. User ID and Password are Base64 encoded but Base64 can be easily decoded.  For more information refer to Script RESTful Web Services WebHelp and Authorization - HTTP | MDN (mozilla.org)

Issue What are the recommendations/limitations around using RDM2 and mRDM2 Reader Expander Modules on SP-ACX and SP-AC1 controllers? Product Line Security Expert Environment SP-ACX SP-AC1 RDM Expander Modules Cause The number of RDM2 and mRDM2 modules which can/should be used on an SP-C/SP-C-Web is well documented, but it is not so clear what limitations exist when using these modules on other SP Controllers. Resolution While SP-ACXs and SP-AC1s have not historically supported SP_RDM2 modules in the past, it is now supported going forward, as detailed in Architectural Guide Lines Security Expert - 4.3.322 available on The Exchange.    This will also receive an official 'new feature' announcement for Security Expert 2023 when it is released later this year.  (Assume controller firmware of 2.08.1320 minimum)   Legacy Continuum AC1 Modules and Security Expert RDM modules have to be used on separate ports and care must be taken when adding new RDM modules as this runs the risk of overtasking the controller, especially when approaching maximum door limits.  SP-ACXs and SP-AC1s are primarily designed as transitional controllers to allow Continuum ACXs and Continuum NetControllers to be transitioned smoothly into a new Security Expert system.   

Issue Creating an Extended Trend Log for b3 (Infinet i1/i2) Point and Value Logs Product Line EcoStruxure Building Operation Environment b3 BACnet Controller Infinet i1 & i2 Controller Building Operation Automation Server, AS, ASP, ASB Extended Trend Logs (ETLs) Cause Using an extended trend log to store log records for long periods of time. The extended trend log is often saved on a higher-level server with more storage capacity. This extra storage capacity enables the server to store more records before overwriting the old ones. For more information, see WebHelp. Configure extended trend logs for b3/i1/i2 devices the same way as configuring extended trend logs in other Building Operation devices. There is one difference, however. do not use smart logs when configuring extended trend logs in b3 BACnet devices. Instead of using smart logs, use the Maximum Transfer Interval property to specify the transfer interval. Resolution In Listview, select the b3/Infinet Object (point or value), click Properties/Advanced Multiply the "Log records" by the "Log interval" to calculate the maximum transfer interval. The "maximum transfer interval" is the frequency at which the extended trend log will transfer log records from the b3/Infinet Object before any entries in the b3/Infinet controller log are overwritten Right click the object, choose New then "Extended Trend Log" In the Create Object box, set Smart Log to False, Set the "Maximum transfer interval" to less than that calculated above (2) Click Create For Infinet systems always refer to Infinet under the hood otherwise the creation is as the Webhelp for creating BACnet B3 Logs In theory it would be possible to create the Extended Trend Log in an ES (where there is more storage capacity), but this could introduce other timing and bandwidth issues, so it is usually best to keep the first Extended Trend Log in the AS, then extend this to a second Extended Trend Log in the ES, as shown. (the second ETL in the ES scan use smart logging in the usual way) If significant logging is required then External Log Storage should be considered. (the B3 or i1/i2 logs still need to be collected via Extended Trend Logs)    

Issue Have lost disc to install RoamIO software for the version 1.0 RoamIO Environment Windows XP Continuum RoamIO 1.0 Cause Lost CD or CD broken for RoamIO  Resolution Below is the software / Drivers and install Guide for the RoamIO version 1.0 RoamIO User Guide.pdf RoamIO V1.0 Laptop.zip RoamIO V1.0 PPC.zip RoamIO V1.0 Driver.zip The latest RoamIO2 versions of the software can always be downloaded from The Exchange Download Center.

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 Contemporary Controls Skorpion Switch configuration setting for using RSP with MPX and RPX controllers Product Line EcoStruxure Building Operation Environment Contemporary Controls EISK8M-100T Skorpion Switch Building Operation Automation Server Premium Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room-purpose Controller Cause Contemporary Controls Skorpion switches have several caveats to consider before using them in a site design. Specific Skorpion switch configuration settings are needed in order for the RSTP protocol to work with MPX controllers.  Resolution *NOTE: This is only for Contemporary Controls Skorpion Switches*   Contermporary Controls EISK8m-100T switch documentation: https://www.ccontrols.com/ctrlink/eiskm.php    There are a number of configuration options available to use these switches and MPX/RPX controllers. This article is not meant to be a comprehensive guide.   Two caveats to consider before using these switches:  Contemporary Controls (CC) Support has indicated that these switches have a limitation to 39 devices (MPXs) per switch. Other vendor's switches do not have this limitation and allow 39 devices per RSTP loop. Multiple RSTP loops are not supported on a Skorpion switch. Multiple Skorpion switches may be used and daisy-chained to allow for greater than 39 devices. The 39 total number includes the switch itself, so effectively, 38 MPXs. A static IP address of the switch should not be in the same IP range (10.110.210.x) if the AS-P is being used as a DHCP server. Configuring the switch this way may cause the AS-P to assign a duplicate IP address to 1 of the MPXs in that range. The DHCP server in the AS-P is a very basic DHCP server to allow for quick IP assignments in a private network. There aren't any configuration options for designated exceptions in the AS-P. (Note: This may be a security concern for sites that do not want a switch on their main network. Setting the Skorpion switch to DHCP enable can allow the ASP to assign a non-static IP to the switch and not interfere with MPXs. RSTP enabled - the snapshot below shows the settings to enable RSTP o the switch Redundancy state: STP/RSTP STP State: Enable Hello Time: 2 Version: RSTP Max Age: 40 Forward Delay: 21                                       The Bridge Priority setting should be changed to 4096 to be a higher priority than the controllers. See the Priority setting in the snapshot above. Root ID: Self-populating field will indicate "Self" when set for a single root with 1 RSTP ring Rood ID "mac-address" may indicate a different switch that is the root switch Non-STP State Port Some ports must be set to not pass BPDU RSTP traffic,  i.e. the ASP, a PC used to configure the switch and connecting other network switches. 2 or more switches can be connected to allow for more devices to be connected (38 each) but RSTP traffic must be restricted to each switch. The ports connecting them need to be configured as Non-STP.   Note: Admin edge turns off almost all RSTP traffic, but not all Non-STP State ON disables the port from participating in the STP or RSTP ring The ports that are connecting the 1st, 2nd or 3rd switches need to have Auto-MDX set properly to behave as a cross-over cable. Either that or use a physical cross-over cable. In the Skorpion configuration page, click on the picture of the switch where the ports are showing "Auto-Mdix enable" on one switch and "Auto-Mdix disable" on the other switch. Click on the actual port from the main page to get to this setting. Example: Switch 1 port 8           Switch 2 port 1            General observations: Switch manufacturers have different limitations and options for configuration. Pay close attention to the Vender’s switch and MPX documentation. After a reconfiguration of the switch, give it several minutes for convergence to take place and to let the system settle. A flooding network traffic loop state may happen in several circumstances: a. RSTP not enabled on an MPX (factory default will reset RSTP to disabled) Note: The Device Report will extract information directly from the controller b. MPX not warm started after setting RSTP c. A switch misconfiguration (Ex. Port not set to Non-STP On) A restart (power off) of the switch may be necessary to recover d. Too many RSTP devices in a loop (>39 including the Skorpion switch) e. IP address conflict This state can be observed when all the controllers go offline and access to the switch config page isn’t possible. It’s best to get RSTP working with MPXs on each individual switch with separate rings and then daisy chain them after configuring Auto-Mdix first and finally plug in the ethernet cable into the next switch. Using 2 PCs can be helpful when setting these up so that 1 can be used to access the switch(s) on the 192.168.92.x network and the other with EBO running on the other network that the ASP is set to. Otherwise switching the NIC settings back and forth is cumbersome. Once both switches are configured and both are working with RSTP, controllers may still show offline. A power cycle can clear this up so that the ASP can reassign an IP with both switches connected. *** 1 MPX controller that has not been set to RSTP will throw the whole system into offline mode. Use the device report to ensure every single controller has been set to RSTP AND has been warm started.  ***   Using the Control Panel MP Series devices link, the Search feature and the Device report in EBO can be helpful to observe all the necessary settings for MPX and RSTP Control Panel MP Series devices link

Issue What should be considered when prepairing for upgrading to Niagara 4.10? What known issues should I be aware of when upgrading to Niagara 4.10 and how can I prepair for them? Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 Cause Define potential issues with an N4.10 upgrade Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.10. Please review prior to upgrading to Niagara 4.10. Niagara 4.10 and Default NRE Memory Changes: The increased size of some core libraries in Niagara 4.10 required changes to the default NRE Memory Pool settings for use on a JACE-8000. MetaSpace memory needed to be increased to allow applications to run without issue.   Note: any previous custom memory configuration applied to the JACE-8000 will be reset upon upgrade to 4.10. Prior to upgrading your JACE-8000, please review Default NRE Memory Pool Configuration Changes In 4.10.     Niagara 4.10 System DB Upgrade: In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10.   Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index is complete accordingly. Prior to upgrading your Supervisor, please review System DB Must Be Re-indexed for Upgrades to Niagara 4.10+ from Earlier Niagara.     Niagara 4.10 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.10, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised or derived from untrustworthy sources.   Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules.   Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.10, unsigned modules will not execute.   For more information, please review the Niagara documentation on Third Party Module Signing   Niagara 4.10 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide.   Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.10.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10)   As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward.   Using Web Launcher with Niagara 4.10 Web Launcher 20.4.2 was recently revamped for Niagara 4.10 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 275 and certificate management has been updated to work with Niagara 4.10 along with any legacy or prospective release.   Prior to using Web Launcher with Niagara 4.10, the customer should update Web Launcher accordingly (see steps below). Updating WebLauncher Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page.   Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version.

Issue The client is inquiring if SE7000 series controllers with LonWorks communications are compatible with TP/FT -10 channels Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause The datasheet indicate network compatibility with Echelon LonTalk but there is no mention of the compatibility with TP/FT-10 channels / networks. This may be unclear to some.  Resolution The SE7000 series is compatible with LonWorks TP/FT-10 channels. Refer to the datasheet for 14240R which is the free topology transceiver used in the SE7000.  capacitors, LPT-10 Link Power Transceivers Free Topology Transceivers, and, with suitable DC blocking capacitors, LPT-10 Link Power Transceivers FT 3120 / 3150 s mart Transceivers, FTT-10 and/or FTT-10A Free Topology Transceivers, and, with suitable DC blocking capacitors, LPT-10 Link Power Transceivers

Issue Unable to send emails using Google's SMTP Server Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controllers (SP-C-WEB, SP-C) Google SMTP Server Cause SMTP server settings in Controller and/or Google account settings are incorrect. Resolution When configuring the Email SMTP settings under Global | Global settings confirm that the correct SMTP server address and settings are used: SMTP Mail Server: smtp.googlemail.com SMTP Port: 25 Use SSL: Enabled SMTP login: <your Google account> SMTP password: <the app password created in section below> Email SMTP settings Google has removed the "less secure app access" ability and replaced it with "app passwords" where you create a unique 16-digit passcode for each individual app requiring access. See details on how to Sign in with app passwords. To use app passwords Google requires the account to be setup for 2-Step Verification. If you do not see the App passwords item under your Google accounts Security section you can also find this by typing "app passwords" in the "Search Google Account" search bar at the top of the window, select the first item "App passwords". App passwords In App passwords press Select app and choose Other (Custom name). Add a descriptive name for the app and click GENERATE. Copy the resulting 16-digit passcode as this will be the passcode used for the SMTP server credentials. Add App password Ensure Firewall settings are not blocking access to the mail server, especially if the McAfee firewall is being used. If there is a Firewall try temporarily disabling this to test.

Issue Using a VPN with I/A Series Niagara Systems Product Line TAC IA Series Environment I/A Series Systems Cause A VPN's purpose is to provide a secure and reliable private connection between computer networks over an existing public network, typically the Internet. Resolution What is a VPN? "Virtual Private Network" or VPN is a mechanism to extend a private network across a public network such as the Internet. A VPN creates a point-to-point connection or "tunnel" across the Internet between two computers. The tunnel encrypts the data between VPN endpoints, preventing data from being deciphered without the required encryption keys. Why use a VPN? VPN provides an additional layer of security to your Niagara system without compromising your ability to access Niagara. A VPN can help protect your Niagara system from Internet-based attacks by requiring an additional layer of authentication to access Niagara resources. It can prevent automated Internet port scan tools from detecting the Niagara system. How can I set up a VPN? The following document describes how to use an Internet Security Gateway to provide VPN access to your ENC/JACE.  Click on the link to download Using a VPN with Niagara Systems for more details. In addition, the document describes setting up a VPN using a ZyWALL gateway.  The ZyWALL USG-20 unified security gateway (from ZyXEL) is a cost-effective device that you can add to an existing installation to provide VPN server capability. IMPORTANT NOTE: The information in this document is based on the assumption that the only IP devices on the network are Niagara devices. If Niagara devices share a network with other devices (such as a corporate LAN), DO NOT follow the approach described in the following pages. Instead, work with the customer’s IT department to determine the best method to protect both the Niagara and corporate systems while providing required access to the Niagara systems. In any scenario, if the VPN is installed or configured improperly, you can expose devices to the public Internet. If you are unsure about how to best configure and test your configuration, please consult an IT expert. Frequently Asked Questions I already use SSL, do I still need to use a VPN? The use of a VPN is still recommended as an additional layer of security. Attacks can come from both inside and outside of your network. Once I set up a VPN, do I still need to use SSL? Yes. The VPN only provides encryption between the VPN endpoints – the VPN client and server. Traffic from the VPN endpoint to and from the Niagara Station is not encrypted unless SSL is used. I’m running AX 3.6 or earlier without SSL support – should I still install a VPN? Yes. The VPN still helps protect against Internet-based attacks on your system. Do I still need a firewall? Yes. You should set up firewall rules to restrict Internet access to the VPN server port only. You should also consider setting up rules with the VPN server to restrict VPN access to only the required IP addresses and ports. For example, there may be non-Niagara devices on the LAN, but the VPN should be configured to only allow access to the Niagara systems. Additionally, you should only allow access to required Niagara services. Will a VPN affect LAN access to ENC/JACEs? No. LAN access to the Niagara devices remains the same as always. VPN only affects the ability to reach Niagara devices from external networks such as the Internet. If I use a VPN, will Niagara HTTP, Fox, and Platform tunneling work? Tunneling works normally over a VPN. You will need to update IP address assignments. What is the impact of VPN on Niagara Networking? Niagara Networking between systems on the LAN still functions the same whether or not there is a VPN installed. When I connect to a VPN, do I lose all other network connectivity? While your VPN client is connected to the remote VPN network, your Workbench (client) PC will have a new "Default Gateway" to allow you to make connections to stations on the VPN network. Typically, this happens without your knowledge and is mostly transparent. The change is undone after disconnecting from the VPN, and re-done when you reconnect. However (while you are connected to the VPN network) if your Workbench (client) PC tries to connect to sites on the [public] Internet or any other network through any router, you will find that you cannot reach those sites. If you must be able to reach those sites while connected to the VPN network, you will need to add static routes (temporary or permanent) to your Workbench PC’s TCP/IP configuration. The setting of those routes is beyond the scope of this document because they are specific to your PC’s network, your VPN network, and any other networks you try to reach. It is possible (but unlikely) that you cannot resolve these routing issues. This may happen if one or more of these networks have overlapping addresses. Consult with a TCP/IP expert if necessary. Likewise, if you use L2TP, PPOE, PPTP, or PPP for any part of your underlying network connection, the VPN client will probably conflict with it. Specifically, Windows only allows one connection of these four protocol types to be active at any given time. What is the impact on Single Sign On? You will need to define the SSO Domain and the hosts of the SSO Domain in your Workbench PC’s "hosts" file or default DNS server. The DNS server of the VPN will not be able to provide name services without changing your Workbench PC’s TCP/IP configuration. I use Dynamic DNS, can I still use a dynamic DNS provider with VPN? Yes. You will need to register the IP address of the VPN gateway and firewall with the DDNS provider. What is the impact of VPN on my system performance? Impact on performance should be minimal. It does take a little longer to set up the connection. References: Microsoft TechNet VPN Overview 

Issue What badging or card creation software solutions do we support with Continuum? Product Line Andover Continuum Environment Continuum Access Control Cause Want to use a third-party badging or card creation system to create badges for a Continuum Access Control system. Resolution The only badging software that we support is EpiBuilder through the -B badging package we offer for Continuum Cyberstations. See the "Badge Manager" help topic in the Continuum on-line help for more information on EpiBuilder. See Devices that have been tested and approved by ImageWare for supported badge printers.

Issue When updating the Vista database in the TAC Vista System Pug-In an error message is displayed that says "Could not connect to Vista Server. Unable to request license." Product Line TAC Vista Environment TAC Vista System Plug-In Cause This error message is a result of not having the Vista Workstation license in the permanent license file. The licensing for the TAC Vista System Plug-In is included with the Workstation license. Resolution The license for Vista Workstation must be purchased in order for the system plug-in to work. For more information about the license packages see Vista 5.1 License Packages. 

Issue StruxureWare Building Operation Satchwell MicroNet Integration - Supported MicroNet devices Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment StruxureWare Building Operation 1.3, 1.4, 1.5, 1.6 Satchwell MicroNet devices Cause Not all variants of older Satchwell MicroNet devices that use the SNP protocol and IAC are supported by StruxureWare Building Operation.  Resolution Refer to MicroNet Devices on StruxureWare Building Operation Web Help (log on required) for a list of supported devices.  In Building Operation, MicroNet device is the family name for the following devices: Standard MicroNet devices: MN300, MN440, MN500, MN620, MN LCD, MN Touch Screen, and MicroNet Manager Interface MN 50 Series: MN350, MN450, MN550, MN650, MN LCD, MN Touch Screen, and MicroNet Manager Interface SNP and Intelligent Advanced Controller devices: MMC3601, MMC4601, IAC400, IAC420, IAC600, IAC Touch Screen, and Modem Interface Unit Unifact: URC2201, URC1201 Unifact Pro: URC-40N-100, URC-41N-10x, URC-50N-100, and URC-51N-10x All these devices are supported in Building Operation.

Issue There is a need to know if Continuum and/or EcoStruxure BACnet support NAT. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum EcoStruxure BACnet BBMD NAT Cause Many sites use NAT for security purposes.  Resolution NAT traversal is not supported in BBMD implementations (Continuum or EcoStruxure). It is an optional feature that has not been implemented. Requests to add this feature should be directed to Product Marketing to include on the backlog for prioritization. Related Continuum article: Can Continuum operate over a NAT Ethernet connection? Ashrae information: here

Issue If the AS is configured to get the time from an NTP server the customer need to know how often the AS will ask the NTP server for the time.    Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Central  EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server (AS/ASB/ASP) Cause In version 1.4, the AS asked the NTP server 1 time per minute. Starting in version 1.5, this was changed so the AS is using the standard solution for the NPT protocol. Resolution When using the standard solution in the NTP protocol as the AS does starting in version 1.5, it depends on how much the AS drifts from the NTP server. The faster the AS drifts, the more frequently the time is updated.   For more information regarding Network Time, please see WebHelp article 6370 and corresponding articles. 

Issue Unable to download MP-V Flow Balance Data object to a controller using download all Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose VAV Cause The inability to use download all is a protection added to prevent overwriting any flow balance data inadvertently Resolution All Flow Balance Data Object properties are downloaded by explicitly downloading the Flow Balance Data Object as shown in the video below    

Issue Set up a MR-VAV-AX (ASC) as Standalone Product Line TAC INET Environment MR-VAV-AX Cause Air balance must be done to calibrate the airflow sensor on the MR-VAV-AX. Resolution Download Tech Tip 072   Equipment: Air Balancing Hood or Manometer and Digital Thermometer.   Assumptions: The MR is powered up. An I/STAT, or an M/STAT is plugged into the service port of a S/STAT or W/STAT, which is plugged into the MR-VAV-AX. The AHU is running. The Space sensor is installed. The Duct static pressure is constant. The dip switches are set properly for the desired VAV configuration. (See TCON 147) You have a Pocket Reference Card (TCON 149). You are familiar with the use and operation of the I/STAT / M/STAT with respect to navigating the Service mode to various mnemonics’ menus. (See TCON 147)   Initial Setup You should notice that two things have already happened: The MR is in the unoccupied mode. The setpoint adjust has defaulted to "-5", making the setpoint display appear low. For the MR to work in a Standalone mode the use of an off-board time clock for the occupied and unoccupied times is recommended. It should be connected to the "Local Occ" point(TB5 input #2 to TB5 ground.) The "Occ" mnemonic under Unit Parameters must be set to ONE for the "Local Occ" point to be used. If the MRs are to be left in the occupied mode indefinitely, install a jumper across the "Local Occ" point instead of using the time clock contacts. Connect the jumper to (TB5 input #2 to TB5 ground.) Using the I/STAT or M/STAT go to Set Temp and increase the value by 5°. This will get the Setpoint Adj. back to zero.   "Cooling Low Flow" (CLF - min. CFM) and "Cooling High Flow" (CHF - max. CFM) Setup Put the I/STAT or M/STAT into the Service Mode. Go to "AP", select "CLF", (the value displayed is "multiplied by" 1000 so 0.24 is 240). Enter the minimum CFM by using the arrow keys to position the LED for the digit to be changed and enter the value by using the "+" and "-" keys. Notice the decimal position will not move. You are entering the value "multiplied by" 1000. Refer to the Pocket Reference Card (TCON 149), paragraph 5. Usually the minimum air flow value can be found on the Mechanical box schedule drawings. The lowest reading that the ASC’s sensor can sense is about .03" to .05" of Water Column(W.C.) Therefore, the "CLF" must be set above this level. If the ASC is required to control in that range, it will tend to oscillate. Select "CHF" and enter the maximum CFM for this box at 1" W.C., this can be found on the DeltaP to CFM graph that is associated with this VAV box’s pickup device, or the box schedule may also provide the maximum cfm value.   Central Plant Heat "Heating Low Flow" (HLF) and "Heating High Flow" (HHF) Setup Use only if Central Plant Heat is required and setup Unit Parameter’s(UP) CPH set to "1". An open contact at Input 3 will indicate that the Central Plant Heat mode is on. A closed contact indicates CPH is off. Using the procedure described above for "CLF" and "CHF" instead select "HLF" and "HHF" and enter the desired Low and High Flow CFM values for the Heating Mode. Otherwise go to the next section. NOTE: If you have a auxiliary stage of heat, it will not be energized unless the CFM input is reading at least 80% of the "HLF" setting.   Calibrate the flow pickup: Go to Unit Parameter "UP", select "dd" (duct diameter). Enter the duct diameter this will enable the MR to calculate the Pickup Factor "PF" for us. NOTE: It is recommended that you begin with the value provided by the VAV Manufacturer for the pickup factor. Then calibrate if necessary using the following procedure. Go to "AP", select "PPF" (pickup factor calibration). The MR will drive the box open and modulate the damper to maintain the "CHF" level. This may take 5 - 10 minutes. NOTE: The stroke time is defined using the Damper Stroke (ds) parameter. The ASC provides several means of synchronizing the point with the physical damper position. 1. When this point is controlled to a value of 0, the decrease pulse will be on for 125% of the damper stroke. 2. When this point is controlled to a value of 100, the increase pulse will be on for 125% of the damper stroke. 3. When the damper stroke duration is modified, the decrease pulse will be on for 125% of the damper stroke. 4. When the power is cycled on the ASC, the decrease pulse will be on for 125% of the damper stroke. 5. Any time the ASC is the target of an Update_ASC or a Copy_Parms, the decrease pulse will be on for 125% of the damper stroke. After the reading has settled out, take a reading with a Hood or Manometer, which has been setup, and measure the actual CFM and enter that value now into the I/STAT-M/STAT using the Select and change buttons. The software has entered a unique Pick-up Factor "PF" in the MR for this box.   Calibrate space temperature (if necessary): To calibrate the Space Sensor while in the Service Mode, go to "oP" Operational Parameters. Select "CSS" (calibrate space sensor). Measure the actual temperature with a digital thermometer and enter the value. If your box has no heat or has a fan with electric heat. You’re finished. Go to the next box.   Hot water coil: If you have a hot water valve on your box and the stroke time is not 600 seconds: Go to "UP" (Unit Parameters) and select "Ho", Heating Output. Select1 for 1-OutPWM, 2 for 2 Out-PWM(Floating), or 3 for Duty Cycle 1 output. Go to "UP" Unit Parameters and select "HS" (heating stroke) and enter the actual stroke time in seconds.   Air Balance: If you require closely calibrated CFM readings proceed with the following steps: Go to "AP" (Airflow Parameters) Select "CPL" (calibrate low flow) and the damper will begin to close. Remember, the damper motor may take 3 minutes to get to the Cooling Low Flow setpoint. With a Hood, measure the total air flow and enter the measured CFM value. Select "CPH" (calibrate high flow). The damper will drive open to the Cooling High Flow setpoint. (remember the damper motor has a 185 sec stroke). When the reading stabilizes, take your measured CFM reading and enter it now. This procedure will de-calibrate the CFM input from the 0-1"readings to compensate for box, pickup, or hood irregularities/errors. Caution: When the decision is made to connect the MR-VAV-AX to a MRI or MCI please note the following: Avoid updating the MCI or ASC after initial setup as this will delete any MCI resident calculations, ATS, etc. that you may have added off-line that are residing at the same point addresses that the MR-VAV-AX is using. There are a variety of box types and a variety of other things that can be change if your application requires it. (Refer to TCON147)

Issue How do I set up a Continuum system to do automatic log truncation to save database space? Product Line Andover Continuum Environment Continuum Trend logs Cause Database maintenance. Resolution Setting up Automatic Log Truncation with SQL Server and MSDE Database  MSDE Engine For MSDE, you can download the Stand Alone MSDE Database Utilities from Buildings Download Center.  These utilities are capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc.  SQL Server For full SQL Server, you can easily create a scheduled Job. Details are described below.   To create a scheduled Job that will truncate the Continuum logs in the SQL Server: Open up SQL Enterprise Manager  (Note that the SQL Server Agent service must be running in order to create a Job) Highlight the Continuum database From the Menu, select Tools \ Job Scheduling A wizard opens: "Welcome to the Create Job Wizard." Click Next Select Transact-SQL Command,  Click Next For the Database Name, select ContinuumDB (or whatever the name of the DB is) In the large white space for the Transact-SQL Command, cut and paste the code from our web site: ****** Replace 90 with the number of days to maintain in each log ******** delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 Click Next On the next screen, you are asked when you do want to run this job Select "On a recurring basis" and hit the Schedule button On the Schedule page, set up whatever schedule you desire Click OK to close the Schedule Page • Click Next On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional • Click Next In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.

Issue In a Niagara G3 station, what is the difference between a Station Save and Backup Station? Product Line TAC IA Series Environment Niagara G3 (AX) Jace/ENC Niagara G3 (AX) Enterprise Server (ENS)  Cause Help determine which feature (Station Save and Backup Station) meet the requirement. Resolution A Station Save only saves the config.bog file to the local device (if an ENC, it will save the file on the ENC; if an ENS, it will save it on the ENS computer).  The Backup Station function performs a complete backup of the connected ENC or ENS station, saved as a dist file on the Workbench computer. The backup dist contains the entire station folder plus the specific NRE config used by that ENC or ENS platform, including license(s) and certificate(s). The dist also contains pointers to the appropriate NRE core, Java VM, modules, and OS. If ever needed, you can restore a backup dist using the platform Distribution File Installer view. The backup dist file also contains the TCP/IP configuration of the host when it is backed up. When restoring the backup, the choice to restore these settings, or retain the TCP/IP settings currently in use by the target host is available.

Issue TS-8XXX and TS-9XXX 1,1000 Ohm Balco sensor, Fahrenheit resistance table. Product Line Field Devices Environment Field devices Balco temperature sensors Cause Reference for integration and calibration Resolution Download spreadsheet file of chart below.     Temp (°F) Resistance (Ohms) Temp (°F) Resistance (Ohms) Temp (°F) Resistance (Ohms) -50 760.816 50 956.9 150 1185.2 -49 762.6 51 959 151 1187.7 -48 764.4 52 961.2 152 1190.1 -47 766.2 53 963.3 153 1192.6 -46 768 54 965.4 154 1195 -45 769.9 55 967.6 155 1197.5 -44 771.7 56 969.7 156 1199.9 -43 773.5 57 971.8 157 1202.4 -42 775.3 58 974 158 1204.9 -41 777.1 59 976.1 159 1207.3 -40 779 60 978.3 160 1209.8 -39 780.8 61 980.5 161 1212.3 -38 782.6 62 982.6 162 1214.8 -37 784.5 63 984.8 163 1217.3 -36 786.3 64 986.9 164 1219.7 -35 788.2 65 989.1 165 1222.2 -34 790 66 991.3 166 1224.7 -33 791.9 67 993.5 167 1227.2 -32 793.7 68 995.6 168 1229.7 -31 795.6 69 997.8 169 1232.2 -30 797.5 70 1000 170 1234.7 -29 799.3 71 1002.2 171 1237.3 -28 801.2 72 1004.4 172 1239.8 -27 803.1 73 1006.6 173 1242.3 -26 804.9 74 1008.8 174 1244.8 -25 806.8 75 1011 175 1247.3 -24 808.7 76 1013.2 176 1249.8 -23 810.6 77 1015.4 177 1252.4 -22 812.5 78 1017.6 178 1254.9 -21 814.4 79 1019.8 179 1257.4 -20 816.3 80 1022 180 1260 -19 818.2 81 1024.2 181 1262.5 -18 820.1 82 1026.5 182 1265.1 -17 822 83 1028.7 183 1267.6 -16 823.9 84 1030.9 184 1270.2 -15 825.8 85 1033.2 185 1272.7 -14 827.7 86 1035.4 186 1275.3 -13 829.6 87 1037.6 187 1277.8 -12 831.5 88 1039.9 188 1280.4 -11 833.5 89 1042.1 189 1283 -10 835.4 90 1044.4 190 1285.6 -9 837.3 91 1046.6 191 1288.1 -8 839.3 92 1048.9 192 1290.7 -7 841.2 93 1051.1 193 1293.3 -6 843.1 94 1053.4 194 1295.9 -5 845.1 95 1055.7 195 1298.5 -4 847 96 1057.9 196 1301 -3 849 97 1060.2 197 1303.6 -2 850.9 98 1062.5 198 1306.2 -1 852.9 99 1064.8 199 1308.8 0 854.8 100 1067 200 1311.4 1 856.8 101 1069.3 201 1314 2 858.8 102 1071.6 202 1316.7 3 860.7 103 1073.9 203 1319.3 4 862.7 104 1076.2 204 1321.9 5 864.7 105 1078.5 205 1324.5 6 866.7 106 1080.8 206 1327.1 7 868.6 107 1083.1 207 1329.8 8 870.6 108 1085.4 208 1332.4 9 872.6 109 1087.7 209 1335 10 874.6 110 1090 210 1337.7 11 876.6 111 1092.3 211 1340.3 12 878.6 112 1094.7 212 1342.9 13 880.6 113 1097 213 1345.6 14 882.6 114 1099.3 214 1348.2 15 884.6 115 1101.6 215 1350.9 16 886.6 116 1104 216 1353.5 17 888.6 117 1106.3 217 1356.2 18 890.7 118 1108.7 218 1358.9 19 892.7 119 1111 219 1361.5 20 894.7 120 1113.3 220 1364.2 21 896.7 121 1115.7 221 1366.9 22 898.8 122 1118 222 1369.5 23 900.8 123 1120.4 223 1372.2 24 902.8 124 1122.8 224 1374.9 25 904.9 125 1125.1 225 1377.6 26 906.9 126 1127.5 226 1380.3 27 909 127 1129.9 227 1382.9 28 911 128 1132.2 228 1385.6 29 913.1 129 1134.6 229 1388.3 30 915.1 130 1137 230 1391 31 917.2 131 1139.4 231 1393.7 32 919.2 132 1141.7 232 1396.4 33 921.3 133 1144.1 233 1399.2 34 923.4 134 1146.5 234 1401.9 35 925.4 135 1148.9 235 1404.6 36 927.5 136 1151.3 236 1407.3 37 929.6 137 1153.7 237 1410 38 931.7 138 1156.1 238 1412.8 39 933.8 139 1158.5 239 1415.5 40 935.9 140 1160.9 240 1418.2 41 937.9 141 1163.4 241 1421 42 940 142 1165.8 242 1423.7 43 942.1 143 1168.2 243 1426.4 44 944.2 144 1170.6 244 1429.2 45 946.3 145 1173 245 1431.9 46 948.5 146 1175.5 246 1434.7 47 950.6 147 1177.9 247 1437.4 48 952.7 148 1180.3 248 1440.2 49 954.8 149 1182.8 249 1443         250 1445.7