Building Automation Knowledge Base

Issue Questions regarding specifications of SmartStruxure Hardware Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H UI-8-AO-V-4, UI-8-AO-V-4-H UI-8-DO-FC-4, UI-8-DO-FC-4-H UI-16 Cause Different I/O modules have different electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs. Voltage Input Specifications: Range - 0 to 10 VDC Resolution - 12 bit Accuracy - ±(0.7mV + 0.2% of reading) Current Input Specifications: Range - 0 to 20 mA Resolution - 12 bit Accuracy - ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range - -50 to 150° C (-58 to 302° F) Thermistors: 10k Type I (Continuum), 10k Type II (I/NET), 10k Type III (Satchwell), 10k Type IV (FD), 1.8k (Xenta), 10k Linearized (Satchwell DRT), 10k Type V (FD w/ 11k shunt), 1k (Balco), 20k (Honeywell), 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminal - Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 3 A Form A Relay: Terminals - Common (C), Normally Open (NO) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 2 A LED Specifications: LED Polarity - Represents the actual state of the output; ON if the output is active, OFF if the output is inactive LED Color - Green Analog Output Specifications Analog outputs can be configured as voltage or current. Module Voltage Output: Range - 0 to 10 VDC Resolution - 50 mV Accuracy - ±100 mV Terminals - Voltage (V), Return Minimum Load - Source, 2 mA; Sink, -1mA Current Output: Range - 0 to 20 mA Resolution - 0.1 mA Accuracy - ±0.2 mA Terminals - Current (I), Return Maximum Load - Output load should not exceed 650 Ohms Supervised Input Specifications Supervised inputs can be used to detect sabotage. Detected resistor values - Open circuit, short circuit, contact open, and contact closed. 5 volt circuit, 1 or 2 resistors, monitored - Series only, parallel only and series and switch combinations. For a 2-resistor configuration, each parallel. Resistor value range - 1k to 10 k resistors should have the same value. The selected resistor value needs to be defined in the system. RTD Input Specifications The specifications of the RTD-DI-16 are extensive and thus are best viewed directly in the data sheet available on the Buildings Download Center: RTD-DI-16 Specification Sheet You can also download the specification sheet here: IO Module RTD-DI-16 Specification Sheet (July 2014).pdf.

Issue Control Valve Sizing Environment Control valves Cause Selecting the wrong control valves can cause improper control operation  Resolution Refer the Application Note CA-28, Control Valve Sizing. This is a good reference document for sizing a control valve. 

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue Alarms about BACnet devices with duplicate names These are not required on the site Product Line EcoStruxure Building Operation Environment Third Party BACnet Devices Building Operation Enterprise Server Cause In EBO, BACnet device name uniqueness enforcement has been removed but an alarm is sent regardless to alert of the problem. Resolution Disable the alarm if it is not require in the alarm view. This is achieved by right clicking on the alarm in the Alarm Pane and 'Disable Alarm'

Issue After rebooting the PC, TAC Vista Server (TACOS) doesn't get a license. You need to restart TACOS after each reboot to get a license. Product Line TAC Vista Environment TAC Vista License Server TAC Vista Server Cause TAC Vista Server (TACOS) starts up before the license system is ready to serve licenses, and therefore everything is offline until you restart TACOS. Resolution Download these tools TAC Vista Run Mode TACLicenseServer Settings (only for TAC Vista 5.1.8 and later) First of all, make sure that you have a system that is working normally and has the appropriate default settings. For more information, watch this video on YouTube Make the following setting in TACLicenseServer Settings [1] Set the startup type to "Automatic" and the taclic port to 2170 [2] Click the "License Setup" button, and write the name or IP address of the local PC. Don't use "localhost" or 127.0.0.1 but the actual name or IP.   [3] Click the "License Files" button, and check that only valid license file(s) is present in the license files folder - no other files can be in this folder. [4] Start the license server Make the following setting in TAC Vista Run Mode [1] Enter the username and password of a user with local administrator rights that have at some point been logged in on the PC. LocalSystem can be used, but it is not recommended. [2] Set TACOS to run as a service [3] In "Service Tools" set the service to start type "Automatic Delayed" [4] Start the service Now reboot the PC If TACOS still doesn't get a license after a reboot, try making this additional setting in TAC Vista Run Mode [1] Stop the service [2] Make the service depend on the license server, and also the Loytec driver if it is used in the system. Now reboot the PC If TACOS still doesn't get a license after a reboot, try adding this environment variable to Windows [1] Open the properties for the computer (Click the Windows start button, right-click "Computer", click "Properties") [2] Click on "Advanced system settings" [3] Add a new system variable called "TCP_NODELAY" and give it the value 1 Now reboot the PC If TACOS still doesn't get a license after a reboot, contact Product Support Services and reference this article Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode

Issue In the download center there are up to four files for the same version of the IOU modules firmware, how do I know which is the right file for my IOU module? Product Line Andover Continuum Environment Continuum IOU Module Cause The Neuron chip used in the Continuum IOU modules can support two different transceivers which are FTT-10A and RS-485, each type requires a different FW file. Additionally, the IOU module originally used a Motorola Neuron Chip ***, in 2001 the Motorola Neuron chip had to be replaced with a Toshiba chip when Motorola ceased production of their Neuron chips. A 3rd chip was used after, the Cypress chip. *** The AC-1 Plus, VT-1, Infistat, and LC-1 were not affected by the chip change as they did not use the Motorola Neuron chip. So you will only find 2 FW files for the same version and model these modules. Resolution 1. When up revving Continuum IOU modules first determine if the module is FTT-10A or RS-485. To determine the type lift the door cover of the IOU module and check the model written on the label. FT appended at the end of the model is for FTT-10A, RS-485 will either have 485 appended or only the model name with nothing appended at the end. If the door cover is missing then remove the inner cover and take a look at the label on the chip itself. The picture below shows an AC1-Plus FTT-10A module indicated by the FT on the label. If the label is missing you can easily identify FTT versus 485 by removing the upper part of the enclosure and inspecting the components populated in the communication section of the circuit. On the Net Controller itself (99xx or 9680) there will be an ECHELON FT component similar to the one in the picture below located in the upper right corner of the board, the Net Controller's cover will need to be removed to see the component.  2. Verify which Neuron chip (Motorola or Toshiba) is installed in the IOU module. 3. Get the appropriate FW file from the download center. R&D had to recompile for the Toshiba chip. The 20 version is the same as the 10 version and the 21 version is the same as the 11 version. Download the IO module firmware Note:  Version 10,11 are the Motorola processors  Version 20 is the Toshiba processor  Version 21 is the Cypress processor

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 In some cases the event and trend database can grow really big although not all the space in the files is used Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Select the event.db or trend.db file from the "historical" folder of the SmartStruxure database folder Execute the following command: vacuum;

Issue Unable to see EWS objects/points under an EcoStruxure Web Services interface Product Line EcoStruxure Building Operation Environment EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause An EWS License may be needed to allow your ES/AS to use EcoStruxure Web Services Resolution Purchase and install an EWS License if required.     Note: The EWS option is NOT required when using EWS to integrate between two Schneider Electric systems or services. Refer to PA-00349 for details.   This includes the new Smart Connector by Schneider Electric which does not require an EWS License but does require a Smart Connector License as usual

Issue Java 8 is only supported together with TAC Vista 5.1.9 Product Line TAC Vista Environment Webstation Xenta Server web Cause The current version was developed and tested together with Java version 7, but not Java version 8 as Java 8 was released subsequently After the latest update of Java (Java 8u31) SSLv3 has been disabled by default in Java. If updating to that version of Java, the Xenta Server web (graphics and schedules) will not work, as the Xenta Server relies on SSLv3. Resolution Making the proper configurations has enabled a number of sites to use Java 8 with the TAC Vista product range. Java 8 is supported for TAC Vista 5.1.9 according to TPA-VSTA-15-0000.03 Refer to this video for settings required: Download video - View on YouTube   The proper settings in Java are: [1] Install the newest version of Java. If you are working on a 64 bit operating system, it's crucial that you install both the x86 and the x64 versions: https://java.com/en/download/manual.jsp [2] Make sure all older versions are removed: https://java.com/en/download/uninstallapplet.jsp [3] Make sure Java is enabled in your browser: https://java.com/en/download/help/enable_browser.xml [4] Add all addresses to the site exception list in the "Security" tab. Both http and https addresses are needed for Xenta Servers. If a special port is used (not 80 for http and 443 for https), the port needs to be entered, e.g. http://IP_ADDRESS:81 if port 81 is used for HTTP communication. [5] Click "Restore Security Prompts" in the "Security" tab. [6] In some cases you might need to add the IP address of the PC or Xenta Server to trusted sites in Internet Explorer   TAC Xenta Server web uses SSLv3 for Java if high security is set in XBuilder. The workaround for SSLv3 being disabled in Java 8u31 and above is: (read Java's own release note) [1] Edit the following two files: C:\Program Files (x86)\Java\jre1.8.0_31\lib\security\java.security C:\Program Files\Java\jre1.8.0_31\lib\security\java.security [2] Scroll down to the last line where it says: jdk.tls.disabledAlgorithms=SSLv3 In both files, comment that line so it says: #jdk.tls.disabledAlgorithms=SSLv3 [3] Edit the file: C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\deployment.properties [4] Add the following line: deployment.security.SSLv3=true

Issue Internet Explorer on Windows Server 2008 (R2) gets "Incorrect User or Password, please try again" or "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. Product Line Andover Continuum Environment Webclient 2.0 Windows Server 2008 / 2008R2 Internet Explorer 9, 10, 11 Cause Internet Explorer security issue and the compatibility issue. Resolution Change the setting of the IE 11 on Server2008 as below: When Webclient logon from IE gets error "Incorrect User or Password, please try again": Set the Webclient server a Trusted site : From IE menu, select Tools -> Internet Options -> Security tab -> select the Trusted sites and click the Sites button -> add the Webclient to the Trusted Sites list. When Webclient logon from IE gets error "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" : Set the Compatibility View: From IE menu, select Tools -> Cmpatibility View settings -> add the Webclient name or IP address to the Compatibility View list. Also refer to:  Do we support 64-bit Internet Explorer for use with WebClient? HTTP Error 500.21 Internal Server Error logging into WebClient. or ASP.NET setup custom has stopped working when trying to register .NET 2 using aspnet_regiis.exe Invalid user name or password dialog when logging into webclient with acc that works in Continuum Error: "Unable to load the .Net control for this page." when trying to open a schedule or trend log in WebClient

Issue What register type should be used for the type called INT64 in the documentation Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Modbus PM Energy meter Cause It is not clear what  Modbus register type should be configured for INT64 Resolution For reading the INT64 on this range of power meters the register definition you need to apply is the "64 bit signed swapped".   Note that this register type is not available in Building Operation versions earlier than 1.5. For further information on Modbus Register Types see the Point and Value Configuration EBO Webhelp topic

Issue There is no full end to end description on how to test SNMP alarms in SmartStruxure 1.6.1 and later Product Line EcoStruxure Building Operation Environment SNMP Alarms Cause Only a guide on how to create the SNMP alarms is available, but there is no guide available on how to test them. For general information regarding SNMP traps, refer to the following Web Help links: Versions 1.6 and 1.7 SNMP Notification Properties Create SNMP Notification Wizard – SNMP Notification Page SNMP Notification View Version 1.8 and later SNMP Notification Distribution Method Create Notification Wizard - Configure SNMP Page Resolution Download and install "MIB Browser" from iReasoning Download the mib file for SmartStruxure Load the SmartStruxure mib file into the MIB Browser through "File"-->"Load MIBs", and select the SmartStruxure mib file Create a simple alarm in SmartStruxure and make it trigger on a digital point Create a SNMP notification with the following settings. To get to the conditions/filter, open (double click on it or hit enter) the SNMP notification. Only showing the properties of it will not show the filter settings. "Address" is the address of the SNMP manager that receives the SNMP notification, in this test "localhost" since the SNMP manager is installed locally. "User name" is the user name of the user on the SNMP manager that receives the notification. In filter settings, select normal and alarm state, and add "Source server = *" as a condition In the MIB browser, select "Tools"-->"Trap Receiver" Trigger the alarm in SmartStruxure An alarm will now be seen in the MIB browsers trap receiver window

Issue Sigma Transition in StruxureWare Building Operation, where the Sigma controllers and the ES are on different subnets. Globals are not being passed to or from the Sigma system. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Globals Global values Link addressing Cause This issue is being caused because the Sigma controllers are on a different subnet to the Enterprise server. Sigma global data is passed between controllers using "Broadcast" messages, 192.168.1.255 for instance. These messages are normally stopped by network switches/routers, and are not passed between different subnets. To overcome this, Sigma employs "Link Addressing". For further information on this please review Link Addressing on a Sigma System Resolution As Sigma servers do not make use of the global broadcasts, on a current Sigma system there may not be any Link Addressing in place for the Server subnet, and this will mean that if an ES is placed on that subnet, it will not see any global broadcasts either. When carrying out a Sigma Transition consider if there is a need to pass global data to or from the Sigma system, and if so, add a DNN3 to the subnet and Link Address it..

Issue Lost MPM IP address Product Line EcoStruxure Building Expert Environment SmartStruxure Lite MPM Cause Forgotten IP address Resolution 1. Connect your PC directly to your MPMs Ethernet port and set your computer network configuration to access the MPM at the default address of 10.50.80.3 (example, set your PC to use address 10.50.80.99). 2. Disconnect and re-connect power to MPM. 3. The MPM goes to Bootloader mode for approximately 10 seconds at start-up. You will see Blue and Green indicators (UN2/VA2 MPMs) alternate steadily during that time according to the following. a. While the MPM is in Bootloader mode, you can access your config.db file at 10.50.80.2/root/ config.db. b. Enter address in browser window before you restore power to not to miss the 10 second window. It may require more than one refresh attempt before you enter Bootloader. 4. The browser prompts you to open or save config.db file once successful connection is made. 5. Open file using text editor. 6. Search “ETH1_ip” field for IP address of your MPM to right side of “ETH1_ip”. 7. Enter IP address to browser address bar to access your MPM.

Issue MicroNet Heat Pump / Fan Coil Controller Diagnostic Table Environment MicroNet 2000 MN-HPFC Cause Quick reference table with corrective action Resolution This table is an excerpt from the MicroNet Heat Pump / Fan Coil Controller Reference Manual (F-26174):

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue What ground connections are required when wiring a voltage input? Product Line EcoStruxure Building Operation Environment AS/ AS-P Power Supply AS-B Universal Input Modules 0-10V, 0-5V sensors Cause The required connections are different for isolated and non isolated voltage inputs. Consideration of the system grounding is also required. Resolution If your input sensor is isolated it can be directly connected to the UI and RET terminals of the Universal Input module. An isolated sensor will have 4 terminals (2 power terminals G0 and G, 2 output terminals M and X) the power ground G0 is not directly connected to the output ground M terminal. However for non isolated sensors (usually 3 terminal devices) the signal terminal X will be wired to the UI input, but the sensors signal common G0 should be wired directly to the Signal Ground for the installation, not to the RET terminal of the IO Module. On every Input modules ensure that one RET terminal from the IO Module is wired directly to the Signal Ground. Full details of the required wiring and an example wiring drawing showing isolated and non-isolated voltage inputs can be found in "Wiring" section of the Hardware Reference Guide available on the Download Center or in WebHelp: Wiring.

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 Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

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 AS status LED solid red for a few seconds followed by a quick blink. Device administrator and/or event log shows system alarm ..."Error - Upgrade using DFU mode"  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB Building Operation Device Administrator Building Operation WorkStation Cause The indication of "Error – Upgrade using DFU mode" occurs due to the fact that a possible problem with writing to the file system has been detected when booting the system. This error can be seen in WorkStation as an Alarm Event, in the Server Logs, or in Device Administrator. Nosync errors are usually seen in the system log. The configuration of the system could have been compromised as a result, although the issue is not necessarily fatal and therefore the AS is allowed to run and the situation is indicated via the red status light. A system alarm is also generated as a warning as seen in the screenshot above. Resolution Since the AS file system could have been compromised, it must be re-initialized from scratch. To clear the red light: Make sure a backup of the AS is available. Attach the Device Administrator to the AS via USB and put the AS in DFU mode (press the reset button 3 times in rapid succession) Install a new database Once the AS has had its FW and database reinstalled, restore the backup using Workstation. NOTES See Error – Upgrade Using DFU Mode  If this error occurs, especially if it occurs multiple times on the same server, check the site installation include Grounding/Earthing and power supplies and for possible EMC issues (Electromagnetic Compatibility)

Issue What are the measures in the AS to protect the system in cases of network broadcast storm or Denial of Service attacks? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Cause Offline alarms received after excessive network traffic observed. Resolution The firmware in the AS will temporarily shut down its Ethernet connection when exposed to a broadcast storm or DoS attack in order to protect the application in terms of control programs and IO. A side effect of this is that the communication to external IP devices is temporarily unavailable during the storm/attack. The Automation Server will log the network storm event in its log journal file. (see screenshot below)