Building Automation Knowledge Base

Issue Various problems with converted TGML graphics Bindings of the I/NET objects within Building Operations have wrong and / or illegal point address. Environment I/NET integration with SmartStruxure Cause Improper preparation before converting graphics may cause nuisance issues. Resolution Ensure the following is done when converting a sites I/NET graphics to TGML Before converting the graphics to TGML Ensure all save files are current Ensure the I/NET network configuration is current Before importing the graphics to StruxureWare Ensure that all affected controllers are imported.  Do not change any names or descriptions before importing graphics Upload any controller which indicates it is required. This will ensure that point names for graphic bindings are correct. In the INET Interface path box, enter the path to where the INET interface is located in WorkStation. This setting affects the bindings that get defined for objects in the resulting TGML file(s). If you accepted the default name when you created the I/NET interface in WorkStation, this path is typically /Server 1/INET Interface/.  Make sure this matches the installed system details.   Click Here to get more detail from the Online Web Help. Check out the I/Net Transition: Graphics Conversion video on the Community website.

Issue What are the product certifications? Product Line EcoStruxure Building Operation Environment SmartStruxure for Buildings AS ES Cause Standards documentation required. Resolution Click here for the CE Declaration of Conformity Click Here for the WSPCert For  BACnet BTL Testing see the PICs statements or the BTL Website: http://www.bacnetinternational.net/btl/ For UL and Country of Origin certification, please refer to PSS for this.

Issue When trying to add an automation server underneath an enterprise server the following error is given. Product Line EcoStruxure Building Operation Environment Workstation  Automation Server Cause Something has been left behind in the automation server that causes a conflict. Resolution Reformat the automation server by performing a New database download. Create a backup of the automation server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Launch Device Administrator and add the automation server. Select the automation server and click on the Upgrade Device button in the top left corner.  In the Upgrade device window, choose "New database" in the Type of upgrade field. Click OK. Once the download is complete, log into the automation server and restore the database. See How to restore a StruxureWare Building Operation server backup set. Now add the automation server underneath the enterprise server.

Issue Host conflict window always pops up, and cleaning routing table doesn't help. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause Host conflict is a normal issue happening in I/NET. It is usually caused by the duplicated host ID setting on different servers, or an engineer laptop is inserted into the network with the same host ID setting with some server. And the routing table will be messed up since all the IP related information will be recorded in the routing table and it will be distributed to all the network devices, including all the servers and NPRs. The usual solution is to clear all the routing tables on all the network devices, . Refer to How to Remove the Routing Tables in a Device or PC about how to clear the routing tables. But if the routing table is cross referred, like Server 1 adding NPR 1 and NPR 2 as reference hosts, while NPR1 adding Server 1 and NPR 2 as reference host, the routing table will never be cleaned out since when you clean the routing table for Server 1, NPR1 and NPR 2 will still try to send their wrong routing table to Server 1. Unless all the network devices are disconnected and the routing tables are cleaned one by one, or disable the 50069 port for the whole network, which is used by the communication between network devices, there is no other way to clean them out. And these two method are not applicable sometimes. Resolution If the routing table can be managed well, such kind of issue will never happen. The best practice on adding reference host and creating routing table is: On the servers: Choose one server as the master reference host. All the other servers add this server as reference host. Don't add NPR as reference host. All the NPRs can be added into the master server by clicking on the NPR button in I/NET configuration and added one by one manually. By this way, the master server can build its own routing table without impacted by other devices. And this one is the only routing table in the whole network. On NPRs. If NPR doesn't need to talk to other NPRs, like transferring indirect points, there is no need to add reference host for NPR. If indirect points are needed, just add the master server as the reference host. Then this NPR will be able to see all the other NPRs based on the routing table on the master server. If the master server is not equipped with UPS, or not always promises to be online, another master NPR can be chosen as a secondary reference host. Add this NPR as a reference host to all the servers and other NPRs. Under this scenario. if the routing table needs to be cleaned, only the master server and the secondary reference host need to be cleaned. It will be more easier to clean all the routing table and get rid of the host conflict error.

Issue When I/NET is running under Windows 7, there will be a display issue about alignment. The font size has been changed to smaller - 100%, but still no use.  Product Line EcoStruxure Building Operation, TAC INET Environment Windows 7 Cause Be sure to try I/NET Seven Windows fields not aligning correctly on workstation's display to change the font size first to see whether it can help. If not, continue to the next information. I/NET used the default MS Sans Serif font to display everything. But something has changed in Windows 7 about the font display.  Research showed that many users with high resolution monitors (particularly LCD flat screens) were running the monitors at lower resolutions than the native resolution of the screen. This was usually because at the native resolution, the fonts were becoming too small to read, so the users would decrease the resolution. Windows includes a facility to increase font and window sizes while keeping the screen at the native resolution.  This is a much better method of increasing the font size as it can produce much smoother images by using many more, smaller pixels. The really significant issue is, unlike CRT monitors, flat-panel LCD monitors have a fixed pixel size, or "resolution", and that when users change to a lower resolution (in order to increase text size) the system has to re-sample the lower-resolution display image into its fixed resolution causing a significant degradation in display quality: not just text looks worse, everything looks worse. A change was made for Windows 7, to set the screen resolution to the monitor's native resolution and if the screen is over a certain resolution to default the font size 120 DPI (dots per inch). This is approximately 125% of normal 96 DPI (100%). When the system defaults to 125% DPI it also adjusts the MS Sans Serif font to be bigger.  If the user then decides to set the DPI back to 100%, then TrueType fonts, which are scalable, adjust as expected. But the bitmap MS Sans Serif font does not: it remains at the larger size, hence this issue. This problem does not occur if Windows 7 keeps DPI at 100% when it is first installed. So anyway, when the default font size is Medium - 125% instead of smaller - 100%, probably the solution below is needed to solve it. Resolution Go to the Registry Editor, and find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. Find the entry MS Sans Serif 8,10,12,14,18,24. The original value is set to SSERIFF.FON on a system which started at 125% DPI. Set to SSERIFE.FON on a system which started at 100% DPI.  Notice that one character of the file name changes from F to E. Restart the computer, and make sure the font size is set to smaller - 100%. Refer to I/NET Seven Windows fields not aligning correctly on workstation's display about how to set font size. Then it should go back to work.

Issue Alarms being generated in I/Net are not showing up on the Enterprise Server. Product Line EcoStruxure Building Operation, TAC INET Environment SmartStruxure Integration with I/Net Alarms Cause Alarms generated in I/Net are not populating on the Alarms Window on the ES, all masking are set on both the AMT Configuration and Host Masks. When the point goes into Alarm, it populates the Alarm Window type, whether it is Priority or Critical with said point address. However, it does not show up on the Alarms page because the bin files on the controller needs to be updated to the latest version of software and all points need to be saved prior to integrating with SmartStruxure. Resolution When integrating with SmartStruxure, all controllers are supposed to be updated with the latest version of software as well as sav files, per Resetting a 7793 Controller and PCU (Applies to 7793, 7716, 7728, 7756). Once completed, recheck the points by putting them in Test mode so that they can generate the Alarm condition and it should show up in the ES Alarm now.

Issue The TGML page is dynamic but looks static. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista StruxureWare Interface Cause In the Release Note, page 30 says: It is possible to navigate to a TAC Vista Webstation TGML Graphic through a link in a SmartStruxure TGML Graphic. To achieve this connection a link object is created in the SmartStruxure TGML Graphic which is linked to a SmartStruxure hyperlink object that holds the TAC Vista Webstation TGML Graphic page address. Example of a hyperlink objects address in SmartStruxure that is linked to a TGML Graphic in TAC Vista: HTTP://ip_address/webstation/LoginPage.aspx?page=TgmlGraphicsPage.aspx?objectId=3074949137 Note: This will always require a login by a valid TAC Vista user, even if the TAC Vista Webstation auto login feature has been activated. Resolution The example link above is referring to a static page. For example, if the TGML page is dynamic, you will see the following in the copied link (see bold). HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 You can also read the following in the release note: In order to determine the TAC Vista Webstation URL for a TAC Vista Webstation TGML Graphic the following TAC Vista Web Setting configuration must be in place: Optimized TGML Loading is deactivated Folders pane is set to Standard HTML With these settings it is possible to right-click a TGML object in the folders pane and select "Copy Shortcut." This will copy the TAC Vista Webstation URL to the clipboard and it can then be pasted into a SmartStruxure hyperlink object address field. After the shortcut has been pasted, it will have to be modified in order for the TAC Vista TGML Graphic to be displayed properly in SmartStruxure. The modification is marked with bold in the example below: Copied: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 Modified: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 If the link you copied was a dynamic TGML the link will look like: HTTP://ip_address/webstation/TgmldynamicGraphicsPage.aspx?objectId=3074949137 and should be modified as this HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 Also reference the TAC Vista Webstation Graphics Links and SmartStruxure Integration tool on the Community.

Issue How to check the amount of used memory in a TAC Menta/TAC Xenta application. Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause When programming applications for TAC Xenta, you may want to be able to check the size of your application, to verify that it can be downloaded to the device. Resolution To be able to check how much memory an application is using, the application needs to generated. In TAC Menta, edit mode: Select Option, Simulate to enter Simulate mode. In Simulate Mode, select Commands, Generate, to generate the application. To be able to check the Memory usage, you have to return to Edit mode, Select Options, Edit. Now you can check the Memory usage by selecting Options, Memory Usage... As this calculation is done on your PC, and not in the device, and that the memory in the TAC Xenta device is dynamic allocated, it is a recommendation to have at least 10% free memory in each category to avoid future problems. For more information about the Advanced button, please see TAC Menta Advanced Memory Usage: BPR Size Calculator.

Issue In order to make page links between different I/NET graphic folders work fine, the same folder structure needs to be created manually in EcoStruxure / SmartStruxure. Refer to Converting I/NET graphics to TGML using the "Create Source Tree" option to realize this. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure / SmartStruxure 1.4 or higher I/NET Cause The I/NET graphic folder structure will not be created automatically before SmartStruxure 1.4.0. Resolution Starting in version 1.4.0, there was a new feature called Data import for I/NET graphic. Using this feature, all the converted I/NET graphic folders structure can be imported at one time without any need for manual work. Here are the steps to make it work: Convert the I/NET graphics according to Converting I/NET graphics to TGML using the "Create Source Tree" option, but do not create the folder structure manually in EcoStruxure / SmartStruxure. Create the default Inet Graphics folder by right clicking on I/NET Interface-->New. Right click on Data Import and choose the root folder of all of the I/NET graphics. Click OK. Data importer will check all the file names and bindings. If any error happens, check and fix it before importing again. (Currently apostrophe is not supported in SmartStruxure. Change the name and relative link and do it again. It may be fixed in later version) Check whether all the bindings and links work fine. Important: Currently this feature doesn't support export/import in SmartStruxure. It will fail to import if any sub folders are contained under INET interface. This may be fixed in later version. The workaround is to still create the whole structure according to Converting I/NET graphics to TGML using the "Create Source Tree" option.

Issue The TAC Xenta operator panel will not display controllers on the network even though it has the correct StruxureWare Domain ID entered and is set to manual mode. Product Line EcoStruxure Building Operation Environment TAC Xenta Operator Panel StruxureWare Cause StruxureWare Building Operation sets its LonWorks Domain ID to a decimal value. The TAC Xenta Operator Panel needs the hexadecimal value in order to operate properly. The decimal value must be converted to hexadecimal. Resolution In order to locate the domain ID of a LonWorks Network, see How to locate and change the LonWorks domain ID. Converting a decimal value to hexadecimal using a calculator Open the calculator on your computer. If Windows go to Start > All Programs > Accessories > Calculator. In the View menu, select Programmer. Enter in the decimal value of the domain ID. Select the Hex button on the left side of the calculator. The domain ID has been converted to hexadecimal. In the example, the domain ID 0B should be entered into the operator panel and set to manual mode.

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue Created a BACnet digital output under the BACnet Interface in the Automation Server but the Out of service property indicates 'True' and get the error 'Property value out of range' when attempting to set the out of service to false. Product Line EcoStruxure Building Operation Environment WorkStation Automation Server - AS BACnet Interface Cause BACnet output must be associated with an IO Bus output. Resolution See Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above for instructions on setting the associated value.

Issue When a MPM is replaced on a BACnet IP network, a "Duplicate network identifier" alarm is generated Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment MPM Automation Server Cause If the BACnet name and instance number in the new controller is not exactly the same as the original MPM, the Automation Server will consider that an additional device has been installed and an alarm will be triggered stating that the new device has the same BACnet ID as an existing device. Resolution Steps to replacing a MPM to prevent the Duplicate ID alarm being triggered: When replacing the original MPM, note the BACnet name and Instance ID. Install the new MPM and enter the same BACnet name and Instance ID. Refer to BACnet device can't be discovered due to duplicate name for more information about duplicate BACnet names.

Issue Update to available documentation. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Windows 7 32/64 bit Cause Clarification of supported communication protocols and devices. Resolution Computer running Windows 7 32bit or 64bit. Visio software installed must be 32 bit version. VisiSat runs as a 32 bit application. SNP Via computers RS232 communications port. Via RS232 provided by USB to RS232 converter. Via RS232 provided by PCMCIA card to RS232 converter. Via RS232 provided by Express card to RS232 converter. IP tunneling through Xenta 555/731 AS/AS-P LAN network. Remote site connection. NCP Via computers RS232 communications port. Via RS232 provided by USB to RS232 converter. Via RS232 provided by PCMCIA card to RS232 converter. Via RS232 provided by Express card to RS232 converter. IP tunneling through LAN network. Remote site connection. ARCnet Via computers RS232 communications port connected through null modem lead to an MicroNet Interface Unit. (MN50-MI-ARC). Via PCI120U-485 PCI card  (This card was made by Contemporary controls but is no longer). The card was replaced by the USB22 Series. (USB 2.0 to ARCNET adapters) These USB22 adapters do not work with VisiSat. IP tunneling through LAN network. Remote site connection. LON Not supported with Windows 7 64bit or 32bit.  The latest documentation for VisiSat can be downloaded, see Download latest VisiSat Data Sheets, Engineering Guides, Installation and User Guides, and Release Notes.

Issue What are the limitations of Building Operation Web Services? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Version 1.3 Cause Due to the XML response rate (XML file information send to Building Operation), it has some limitations. Resolution General Guide in the Technical Reference Guide: The limit for the whole XML response is 100 kb, which includes manually created values. The limit for a string value is 10 kb, which includes manually created values. The maximum number of values created in the Web Server interface is 200. The recommended limit for XML elements in the Web Service interface is 100 The recommended number of Web Service interfaces in an Automation Server XML elements at a polling rate of 60 seconds. is 2. Additional Information: Maximum number of Web Services in an Automation Server Also refer to Architectural Guidelines for your respective version in use.

Issue CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output, but the Xenta 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller.  If replacing the sensors would be too costly and time consuming, this is a viable option that will allow you to drop the voltage output on the CO2 sensor using 1000 ohm resistors.  Product Line TAC Vista, EcoStruxure Building Operation Environment 102-AX Cause CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output but the 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. Resolution NOTE:  It is recommended that the incorrect sensors be removed and replaced with new sensors that have the proper specifications to match the 102-AX capabilities.  If the sensor replacement is not an option please follow the instructions below. Please see the image below: You will need (2) 1000 ohm (1k) resistors to complete this conversion. Wire one resistor directly to the output wire of the CO2 sensor Land that resistor to U3 on the 102-AX Jump a second resistor from U3 over to M on the 102-AX Land the other output wire from your CO2 sensor on M with the jumped resistor   Also see Using a 4-20mA CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 4-20mA CO 2 sensor input on Universal Input 3.  

Issue How many MSTP networks can you connect to an Automation Server (AS or AS-B)? Product Line EcoStruxure Building Operation Environment Version 1.3 and newer MSTP Network on an StruxureWare Building Operation Automation Server (AS or AS-B) BACnet MSTP Devices Cause Require 2 separate MSTP networks, either to use 2 different Baud rates or to speed up the network and split the devices across the 2 ports. Resolution You can create 2 separate MSTP networks under the BACnet interface of an AS-B or AS (version 1.3 or higher), one on Comm A the other Comm B. Each can run at different Baud rates if required. For the number of supported devices please reference, Maximum number using StruxureWare Building Operation (Scalability and Capacity). Please be aware that the listed maximum is for the Automation Server allowing you to distribute between the two comm ports.

Issue Adding an object to an already opened Trend chart does not work correctly. Product Line EcoStruxure Building Operation Environment Webstation Open chart Adding objects Cause An AS or ES is logged into using a Webstation, and an existing Trend chart is opened. An object is then selected in the System Tree, and then using the right-hand menu, the "Open Chart" and "Add to already open chart" is selected. Values are not added to the already opened chart. This issue is caused by a Java 7 update 51 a specific fix is not available. Resolution Possible workarounds; Use an earlier version of Java. Change Java security level to Medium. Add site to the exception list For further details on "adding to the exception list", refer to Webstation graphics not working after Java updated to Java 7 update 51.

Issue How is the time synchronized between the Automation Server and Xenta Programmable Controllers? If the time synchronization is offline, what can be done to correct this? Product Line EcoStruxure Building Operation Environment Automation Server Building Operation Workstation Cause Time Synchronization occurs between the Automation Server and the Xenta Programmable controllers during two events: When the Xenta programmable controller is commissioned. Periodically the time is synchronized (default 10 minutes, but configurable). For the time synchronization to work properly it is critical to ensure that the time zone of the automation server is correct and the date/time of the automation server is correct. Resolution Walk through these steps to troubleshoot the synchronization of the Automation Server and Xenta controllers.   Check that all Xenta devices are at software revision 3.74 or higher Check the local time of the Xenta programmable controller by accessing the properties of the programmable controller and using the "Xenta" property tab group. The local time is listed there. Check the time zone of the automation server. By default the "Factory time zone" needs to be changed for proper operation. Check the server time of the Automation Server in the Basic property tab of the Automation Server. Check Time Synchronization Interval setting of the LonWorks Network object under the advanced tab in the Xenta General section. Default is 10 minutes. Either wait for the interval to elapse or manually commission the controller to synchronize the time and check the local time of the controller to ensure it completed properly.   Note: Keep in mind that the time displayed time in Workstation reflects the time zone of the local machine. If you are logging into an Automation Server in a different time zone, the alarms and events will be displayed in your local time, not the time of the Automation Server's time zone. For more information on Time settings and Synchronization see Time Synchronization of the ES and AS.

Issue Configuring the Xenta 102-AX to accept a 4-20mA CO₂ sensor input on Universal Input 3. A negative value is required on the CO₂ offset value, but it is not possible to enter a negative value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX 4-20mA output CO₂ sensor Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input. The best option is to always buy a CO₂ sensor that is compatible. However, if 4-20mA CO₂ sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20mA CO₂ sensor with a 0-2000ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to CO₂ Sensor Wire a 250Ω resistor across U3 and M. This converts the 4-20mA signal to 1-5V. In Vista Workstation, navigate to the 102-AX > UnivIn3_Sense. Open SCPToffsetCO2. This value needs to be -500, but negative values cannot be entered. To get around this: Change Value to 0 Change Scaling > Offset to 500. This alters the display of the offset value. Click OK. Open SCPToffsetCO2 a second time. The value is still 0, but it is being displayed as 500, due to the scaling offset. Change the value to 0 (because of the offset, 0 represents -500). Click OK Open SCPTgain. Set multiplier to 2444 Set divisor to 1000 Click OK. This value comes from 2000 (range of sensor) + 500 (offset) / 1023 Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid). Also see Using a 0-10 volt CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 0-10 volt CO₂ sensor input on Universal Input 3.