Building Automation Knowledge Base

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue A warning banner is displayed at the top of the Workstation window that states "A license violation has been detected." even though a valid evaluation license has been activated on the machine or site. The user will also find another warning message on the LicenseManager screen, under the System folder, that provides greater detail. This message will state specifically what is missing, for example "An additional X automation server license(s) are required. Please purchase the required licenses." Product Line EcoStruxure Building Operation Environment EBO Enterprise Server 2.X and newer EBO Workstation 2.x and newer Cause The new scalable licensing structure established in version 2.0 requires licenses for each automation server device (and field devices if the system is a new database). The evaluation (demo) license will account for the required licenses as long as it is valid but sometimes can be stuck in a state where it has not been validated.  Resolution In the majority of situations, simply rebooting or performing a warm start of the Enterprise Server will clear this warning as long as there is a valid evaluation (temporary) license hosted in the license administrator the ES is referencing. Troubleshooting Steps: Restart the Enterprise Server. Restart the License Server (if on a different machine as the ES). If required, restart the ES again. Check for any errors in the License Server and verify that the Vendor Daemon is up and running. See Unable to log into WorkStation due to license error codes -12, -15, -18 or -97 for more details around this troubleshooting step. If these steps have not resolved the issue, then open a support case with your local country support organization.  For more information about the enforcement of licenses see the EcoStruxure Building Management WebHelp article, Licensing Enforcement. 

Issue Integration to the Cummins ModLon 2 gateway with the Xenta 500 / Xenta 700 / Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Cummins ModLon 2 Gateway Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev files as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes. One generator: .dev file Two generators: .dev file   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Documentation supplied with new UNC, ENC, or Jace 8000 was discarded.  Is there a way to determine the default, the factory-defined IP address, for the Ethernet port on the controller? Product Line TAC IA Series Environment I/A Series (Niagara) R2 UNC I/A Series (Niagara) G3 ENC Niagara N4 or G3 Jace 8000 Cause Lost or discarded document, shipped with the controller, that contained the configured IP address. Resolution The default Ethernet IP address for an I/A Series (Niagara) UNC or ENC is based on the serial number and type of device. For a UNC or ENC, the default address is 192.168.1.14X where X is the last digit of the device serial number.  The default serial number is found on a sticker on the controller circuit board.  This sticker has the full model number, date code, and the serial number of the controller.  The serial number is preceded with S/N:.The subnet mask is 255.255.255.0 in all UNCs, ENCs, and Jace 8000 The default address base address (192.168.1.140) is the same for all UNC-410, UNC-510, UNC-520, ENC-410, and ENC-520 controllers. The default IP address of a Jace 8000 for PRI (LAN1) is 192.168.1.140.  SEC (LAN2) is by default disabled.

Issue After 2000 backups an attempt to perform a backup to flash results in the error 'Flash backup for this controller has been disabled.' Product Line EcoStruxure Building Operation, Andover Continuum Environment b3 controller i2 controller Cause Flash memory has a limited write count; Controllers implement a flash circuit breaker that trips after 2000 backup operations in order to protect the flash device from damage. Resolution (Applies to all b3 and i2 controllers) EcoStruxure Building Operation In EBO, a command has been added that will re-enable backup to flash after the circuit breaker has been tripped (2000 backups) From Workstation, in the object tree, right-click the i2/b3 device. From the context menu select, DEVICE->ENABLE BACKUP TO FLASH     Andover Continuum From CyberStation command line set the ACCStatusBackup system variable of the device to ACCBackupEnable. NOTE: The flash circuit breaker CANNOT be reset from Script/Plain English.  This is by design as it was deemed too risky to allow resetting it programmatically.  A poorly written program could very quickly cause damage to the flash device.

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue What is the difference between an EBO SmartDriver and Smart Connector? Product Line EcoStruxure Building Operation Environment Building Operation SmartDriver Cause SmartDriver and Smart Connector enhance the openness for the EcoStruxure Building Operation, EBO, BMS system. They enable integration between EBO and 3rd party systems, even via not supported or nonstandard protocols. Resolution SmartDriver: SmartDriver enables you to create a customized interface to monitor and control 3rd party devices from the EBO server. The following block diagram shows a SmartDriver Interface and a SmartDriver Driver. The SmartDriver Interface (similar in concept to other protocol interfaces such as Modbus and BACnet) is part of EcoStruxure Building Operation software and enables you to create SmartDriver objects in the System Tree pane. The SmartDriver Driver is installed on the server drive and provides the network communications control. More information at Web Help SmartDriver Overview. Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions that extend and enhance EcoStruxure Building solutions. The Smart Connector itself runs outside the EBO server and consume or server data to EBO server via the EcoStruxure web services "EWS". Watch short explainer video for more information: https://www.youtube.com/embed/DXHvRRL4ycY   For more information, visit the Smart Connector Developer Community on the Exchange: https://community.se.com/t5/SmartConnector/ct-p/smart-connector   For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com   Smart Connector shop at Exchange:  https://shop.exchange.se.com/en-US/home 

Issue Solid red light Blinking red light Blinking green light Product Line TAC Vista Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The indicator lights on the face of the Xenta controllers can help explain the state of the controller with different actions.  Resolution There are two LED indicators – one red and one green on the Xenta programmable controllers.   The red service diode is primarily an error indication. It also lights up if the Service pin is activated. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below. Use a reset dongle to wipe the controller then reinstall the firmware and menta program. If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing. NOTE: The hardware may need to be replaced if the solid red light continues after these steps. If the red indicator light is blinking once per second this will indicate a non-configured node. If the controller has been commissioned you might try to decommission the controller and try again. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly. The green status diode blinks once per second to indicate that the program is running properly.

Issue Unable to locate data sheet for the MD-S1 and MD-S2 auxiliary switch Product Line Field Devices Environment MD-S1 auxiliary switch MD-S2 auxiliary switch Cause No data sheets can to be found. Resolution Data sheets for the MD-S1 and MD-S2 auxiliary switches are not available. To review the MD-S Auxiliary Switch Installation Sheet, please click HERE.

Issue BACnet COV subscription system Product Line EcoStruxure Building Operation Environment BACnet Settings COV subscriptions v1.7 and earlier Cause A site will have a problem with the amount of traffic because of misconfigured COV Increments. The problem is that Building Operation, the  ES and AS resubscribes to values every 10 seconds and one by one. So for example: hh:mm:ss 00:00:00 Value1 00:00:10 Value2 00:00:20 Value3 00:00:30 Value4 ... 05:00:00 Value1800 If you have more than 1800 subscriptions the ES or AS is not able to do all subscriptions in 5 hours.   5 hours is used because Building Operation subscribes to the values with a lifetime of 5 hours.   Resolution BACnet COV subscription system is not influenced by the requested transfer rate in the edit bindings system (Subscriptions using BACnet). That is used in the case where the external device does not support COV, and read-property must be used instead. The design in 1.4 and 1.5 simply did not anticipate such large numbers of COV subscriptions. Workaround: 1.Exit Workstation 2. Stop the Enterprise Server Edit using notepad the server.properties file located in "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\ Find at the bottom: # Set GenericConsume communication defaults Add the two following lines: NspServer.BACnetPlugIn.COVSubscriptionLifetime entry = 28800 NspServer.BACnetPlugIn.COVTimerPeriod entry = 5 Save your changes and close the server.properties file. This changes the default values from 5 hours to 8 hours and 10 seconds to 5 seconds. NOTE From version 1.8 the BACnet Interface manager (/Server 1/System/Interface Manager/BACnet) provides access to these settings (COV subscription lifetime (default 8 hours) and Server COV renew rate(default 5 seconds)) The settings will be controlled via the Enterprise Server if connected.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue SQL Database is full, or the partition the SQL is installed is full Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause If a site is using SQL Express 2008, the limit is 10 GB. If using the full version(s), it is unlimited. If the database or the partition where the Reports Server resides is full, here are some steps to reduce the SQL table volume and offer a short-term solution. Resolution Before continuing, make sure there is a good backup of the database. Using SQL Server Management Studio, highlight the StruxureWareReportsDB and select New Query Use the following Script in that Query: SELECT t.NAME AS TableName, s.Name AS SchemaName, p.rows AS RowCounts, SUM(a.total_pages) * 8 AS TotalSpaceKB, SUM(a.used_pages) * 8 AS UsedSpaceKB, (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB FROM sys.tables t INNER JOIN sys.indexes i ON t.OBJECT_ID = i.object_id INNER JOIN sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id LEFT OUTER JOIN sys.schemas s ON t.schema_id = s.schema_id WHERE t.NAME NOT LIKE 'dt%' AND t.is_ms_shipped = 0 AND i.OBJECT_ID > 255 GROUP BY t.Name, s.Name, p.Rows ORDER BY t.Name Select Execute to run that Query as shown in the screen capture below: The Results show each of the tables and the size of those tables as shown in the screen capture below: Purely for example purposes, a script to reduce the number of Events would be delete from tbEvents where DATEDIFF(day, datetimestamp, getdate()) > 180 To gain back the space after deleting rows, right-click on StruxureWareReportsdb > Tasks > Shrink > Database

Issue Unable to determine whether the Enocean device in hand is compatible with MPM controllers Unable to add more devices to a MPM controller Product Line EcoStruxure Building Expert Environment Multi-Purpose Manager Cause Some pre-configured icons in the "Add Devices" list have a name but do not have a specified Enocean profile or vice versa. Resolution The Following devices are embedded in the MPM firmware and require no scripts to integrate with an MPM. All Devices in the below list (except for Enocean relay) are outbound devices (i.e. devices that are only able to send telegrams to other devices) MPM Sub-device list Description Compatible Schneider-Electric Products CO2 Sensor A5-09-04 CO2 Sensor SR04 CO2 (LSS442510) (868MHz) Door/Window Sensor D5-00-01 Single Input Contact SED-WDS-U-5045 (902MHz) 10020032 (LSS10020032) 10020042 (LSS10020042) 10020047 (LSS10020047) Double Rocker Switch F6-02-01 Light and Blind Control – Application Style 1 EDRPU-W-EO (902MHz) 10020048 (LSS10020048) (868MHz) Enocean Relay Inbound profile   Enocean Switch Light and Blind Control – Application Style 2 ESRPU-W-EO (902MHz) 10020049 (LSS10020049) (868MHz) Enocean Thermostat Obsolete   KeyCard Switch F6-04-01 Key Card Activated Switch SED-KCS-U-5045 (902MHz) Light Sensor A5-06-01 Light Sensor Range 300lx to 60.000lx 10020047 (LSS10020052) Light Sensor A5-06-02 Light Sensor Range 0lx to 1.020lx SED-LLS-U-5045 (902MHz) LSS10020053 (868MHz) Motion Sensor A5-07-01 Occupancy Sensor with Supply Voltage monitor SR-MDS Bat SED_CMS_U_5045 (902MHz) Thermostat A5-02-05 Temperature sensor Range 0°C to +40°C SED-T00-U-5045 (902MHz) 10020046 (LSS10020046) 10020033 (LSS10020033) Thermostat A5-04-01 Temperature & Humidity sensor Range 0°C to +40°C and 0% to 100% SED-TH0-U-5045 (902MHz) 10020041 (LSS10020041) SR04 rH Thermostat A5-08-01 Light, Temperature and Occupancy sensor Range 0lx to 510lx, 0°C to +51°C and Occupancy Button SR-MDS Thermostat A5-10-03 Room Operating Panel: Temperature Sensor and Set Point Control SR04 P (LSS226172) Thermostat A5-10-05 Room Operating Panel: Temperature Sensor, Set Point and Occupancy Control SED-TS0-U-5045 (902MHz) Thermostat A5-10-10 Room Operating Panel: Temperature and Humidity Sensor, Set Point and Occupancy Control SED-THS-U-5045 (902MHz) Thermostat A5-10-12 Room Operating Panel: Temperature and Humidity Sensor and Set Point SR04P rH(LSS252331) Thermostat A5-10-19 Room Operating Panel: Humidity, Temperature Set Point, Temperature Sensor, Fan Speed and Occupancy Control   -The maximum number of devices added to each MPM is 49 -The maximum number of EnOcean devices added to each MPM is 49 -The maximum number of EnOcean devices with the same EEP added to each MPM is 49 .This only applies to firmware 2.13.1 and later, the limit for previous firmwares is 20. An Exception is the following limits for devices/widgets per MPM 20 EnOcean Switches 20 EnOcean Relays 4 EnOcean Thermostats The Devices in the next table do not have a pre-configured icon in the devices list, however, scripts can be used instead and can be found below (Please read PDF first) Enocean Scanner Enocean device driver Valve driver Enocean profiles supported in script EnOcean Equipment Profile (EEP) Description Example of Compatible Devices (EEP A5-38-08) Central Command Gateway Plug-in 15 Amp 120V 902Mhz 5-Wire 6A Relay 24V 902Mhz 3-Wire 6A Relay 120/240/277V 902Mhz (EEP A5-11-01) Lighting Controller 15A-20A 120/277/347V 902Mhz (inbound profile: A5-11-01) 15A 120-277V 902Mhz (inbound profile: A5-11-01) (EEP A5-10-04) Temperature Sensor, Set Point and Fan Speed Control Thermokon SR04PS (EEP A5-02-14) Temperature Sensor Range -20°C to +60°C Thermokon SR65TF (EEP F6-03-01) 2 to 4 Rocker Switch (Light and Blind Control) Push-button, 2-gang (EEP A5-20-1) Battery Powered Actuator Thermokon SAB02/SAB05     Din Relay 1 channel (inbound profile: F6-02-02)     PWM 230V valve driver (inbound profile: A5-02-05) PWM 24V valve driver (inbound profile: A5-02-05)

Issue Includes PSI Error Messages and Device Error Messages Environment PSI Microzone II Network 8000 Cause Quick reference Resolution The error codes are listed in the PSI MicroZone II Operator's Manual.  The full document is available here:  F-23058. Just the error codes are available here:  Pages 59-61.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue When running TAC Vista in a Network environment, there are several ways of setting up the license system. Sometimes, TAC Vista nodes (Vista users) "steal" license modules for each other. Environment Vista in network Flexnet license Cause When various TAC Vista systems are pointed to the same license server, one server can take or "steal" e.g. an OPC Client license which another server should use. Resolution For a complete explanation about the license system and how to setup the system and control licenses, refer to this video. A useful tool to use is the Options file, with the .opt file extension. Located in the License files folder, its easily monitored in a text editor, and could be used for Reserving or Excluding license modules for other TAC Vista nodes. Other features available for the Options file can be found in the Flexnet Licensing End User Guide. 1: Make a file called taclic.opt and place it in the same directory as the license files. 2: Edit the file with notepad and make the reservations you need. The syntax for each line in the file is "command amount feature HOST host". The feature names can be seen in the license files. Here is an example on how to reserve an OPC Client license for a PC called "BMS_SERVER_1" RESERVE 1 Vista.Server.OPCClient HOST BMS_SERVER_1 3: Restart the license server.

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 Access Control Spec for Tender Offer which usually comes from the Product Marketing Division Environment I/NET Site with Access Control Cause Bidding a job and requests for Access Control Spec or Specification Requests for: General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Security Management System (SMS) specified For the Access/Security Control Contractor. Typically the SMS provides and explanation and integration for:   • Integrated Access Control • Alarm Monitoring • Integrated Digital Video Management • Interactive Alarm/Facility Graphics Display • Wireless Alarm and Video Transmission • Associated Access Control and Alarm Equipment Control • Multiple Language Operation • Multiple Tenant Operation • Access Initiated and Event Initiated Control  • Elevator Control • Workstation and associated equipment General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Resolution I/NET Seven Access Control Specification (Available in a MSWord format)  

Issue When attempting to downgrade an AS / ASP over IP or the direct connect USB cable, the new firmware fails to complete the install. Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (ASP),  Cause When installing a a "New Database" in to an AS or ASP, it first needs to clear out what is in the controller and then load the firmware with a blank database. This process may require DFU mode to achieve the install.  Resolution To downgrade an Automation Server or Automation Server Premium to an older version of software, put the controller in to DFU mode before beginning the direct USB download of a new database. To put controller in DFU mode, attach the Device Administrator to the AS via USB and press the reset button on the front of the controller 3 times in rapid succession. Note: The IP address of the controller will be reset to default. (192.168.1.99) Changing the version between v1.8 and the current version can often be achieved with a DFU reset, however the DFU reset clears out the history of the device which can be an advantage.

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

Issue There are BACnet/IP devices on several different IP subnets. Each subnet has one BACnet/IP device setup as a BBMD, however when doing a discover, no BACnet/IP devices from the different subnets are not being discovered. Environment Niagara G3, ENC-520 Cause Setting up the BBMD in the ENC-520 is as simple as Changing its “Ip Device Property Type” from its default of “standard” to “Bbmd”. Once the ENC is configured as a BBMD device, then the BBMD’s required Broadcast Distribution Table (BDT) is automatically created. The ENC’s BDT includes its own IP address and Broadcast Distribution Mask (BDM), as well as the IP address and BDM of all other BBMD devices on the other IP subnets. The BDT allows for manual editing. We have found in some cases that the BDMs were being confused with the IP address subnet mask. The BDMs were being changed to reflect devices’ IP address subnet mask, which were something other that the standard BDM of 255.255.255.255. BBMD devices’ BDM must be set to 255.255.255.255. Resolution The Broadcast Distribution Mask must be set to “255.255.255.255” for each BACnet /IP Address listed in the ENC’s Broadcast Distribution Table. This is also true for other BACnet/IP devices configured as BBMDs on the other subnets. 1. Expand the ENC’s BACnetNetwork 2. Expand Bacnet Comm and then expand Network 3. Expand Ip Port and then expand Link 4. Expand the Broadcast Distribution Table 5. Expand any devices listed and set their Broadcast Distribution Mask to 255.255.255.255 for any one not listed as such. Save changes. Try and discover again.