Building Automation Knowledge Base

Issue Unit Conversion Exceptions Unit selection of 'bar' defaults to N/m 2 unit Units are not displaying unit as selected in the properties Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and above Cause Building Operation supports both the SI metric system and the US Customary System for units of measurement. The operating system regional settings on which WorkStation is installed determine whether SI units or US Imperial units are displayed. The conversion between the two measurement systems is managed automatically. For example, the temperature 42,82 °C is stored in Building Operation. A WorkStation on an operating system with the US Customary System converts the temperature and displays it as 109.08 °F. To display the original unit of a value in WorkStation, open the Properties pane for the value and go to the Unit selection dialog box. As part of this process some units selected, default to a default display unit, and not what was originally selected.  For example, selecting the pressure unit 'bar' when configured in a SI regional setting will display by default the unit 'N/m 2 ' and not 'bar' as selected.  This functionality is as per design but can be altered by using the Unit Conversion Exceptions feature. Resolution First reference Adding a Unit Conversion Exception on the Building Management WebHelp site.    In the release version 1.2 and above there is a feature that allows the operator to create unit exceptions, called Unit Conversion Exceptions.  This is located under the Domain folder and allows various conversions for different domains.  The steps below indicate how this is achieved. Locate the Unit Conversion Exceptions under the required Domain The Unit Conversion exceptions are now displayed in the Workspace.  The Add remove buttons are located at the bottom of this workspace Add the Configured unit, which is the selected unit for the variable you wish to be converted Then change the SI Display Unit and / or US Display Unit to the desired unit you wish the configured unit to be displayed / converted too Save these changes and confirm that it is now displayed in the desired unit.  In some cases you may need to log out and then back in for the changes to be applied. Online Web Help is also available here: If your system is based in US region then you can default you measurement system to US as per Metric vs. English (Imperial) Operating System.

Issue Webstation TGML links used to navigate between Graphics pages do not work. These TGML page links work in workstation Product Line EcoStruxure Building Operation Environment SmartStruxure Cause The name of the Enterprise Server database has an illegal character. A sample of this would be if the Enterprise Server is named "Server'1"  The ( ') affects the HTTP application and prevents the page links from working. Although the name is accepted and works in Workstation, WebStation does not allow this character. This will be corrected in a later revision. Resolution The only resolution at this stage is to rename the Enterprise Server to a name with valid characters. If there are Automation Servers already installed under the Enterprise Server then there is a major issue with renaming the Enterprise Server and we would not recommend renaming you servers unless you are in the early stages of your project. You will need to detach and delete all of the Automation Servers and then Rename the Enterprise Server. Bindings will be lost in this process and will need to be recreated when the Automation Servers are added back in. See Illegal object name characters in StruxureWare Building Operation.

Issue Using I/NET trends in StruxureWare Building Operation Product Line EcoStruxure Building Operation, TAC INET Environment I/NET StruxureWare Building Operation 1.3 Cause Ideally trends should reside in the controller rather than at the sever level as this prevents sample data loss due to communication errors. Resolution Before you begin, ensure that all I/NET trends are set up correctly and trend data is visible. For assistance with this see Setting Up I/NET Seven Trends. Ensure that messaging is working so that SmartStruxure receives I/NET messages, and ensure that all controls have points to be trended, are already added to the I/NET Interface. NOTE: For the Enterprise Server level integration, the I/NET Trend Object must be configured as a Seven Trend. For the Automation Server level integration, this is not required, therefore skip to step 3. In I/NET, Select Trends>Data Inquiry/Edit View the trend you wish to see in SmartStruxure and verify that it has data. Open StruxureWare Workstation Refresh the system tree and upload any I/NET controllers that do not show a green dot. Right click on the I/NET Interface and select New>Value When the "Create Object" Window appears, name the value and click "Create" The Value will appear in the I/NET Interface Right Click on the newly created Value and select "Properties" Locate the "Point to Trend" Field Click on the "..." and select the point object you wish to trend Click the select button Verify that the Point to Trend field is correct and Click OK Wait enough time for several samples to populate. Right click on the Value object in the I/NET interface and select View>Trend log lists>New Trend log list The New Trend log List should open and values should visible. The Trend Value object under the I/NET interface will now function the same as a trend object in StruxureWare. If you wish for the I/NET trend to show up as part of an Energy Report, you will need to Ensure that the Extended Trend Log is referenced in a Meter's "Meter Trend Log" property NOTE: For the Enterprise Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven Trend to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must have a current save file The Controller with the I/NET point being trended must be online The I/NET workstation located on the Enterprise Server must be masked to receive data from the trend log on the controller to the Seven Trends Definition For the Automation Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven trend extension to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must be online The I/NET trend object and point object must have some level of masking so that the data will leave the controller.

Issue After updating Java, webstation doesn't show graphics. The window is blank/white. If the error you get is "Error. Click for details" and not a blank window, please refer to Webstation graphics not working after Java updated to Java 7 update 51. Product Line EcoStruxure Building Operation, TAC Vista Environment Java Webstation Cause There's an issue with Java and Webstation in SmartStruxure 1.5 when using panels. There's a hotfix available (1.5.0.2307) correcting this issue. Either Contact Product Support for this hotfix or download it on The Exchange Download Center. If panels are not used or the SmartStruxure version is lower than 1.5 or you are working with another product line such as TAC Vista, this article might help. This issue is usually only seen when updating an existing Java installation. If no version of Java has been installed previously, the issues doesn't seem to appear. According to Sun, there's an issue with the deployment.properties file. Read this article for further information. Resolution First try to install the newest version of Java. Version 1.7u67 has just been released, and is supposed to solve the issue. If you are using a x64 operating system, make sure you install both the x86 and the x64 version of Java in order to support both 32 bit and 64 bit browsers installed. If that doesn't work, try the procedure below. 1: Make sure all browsers are closed 2: Uninstall all Java versions 3: Make a copy of the file C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites (replace user_name with the profile name of the user logged into Windows) 4: Delete the folder C:\Users\%username%\AppData\LocalLow\Sun (replace user_name with the profile name of the user logged into Windows) 5: Install the latest version of Java (https://java.com/en/download/manual.jsp) - if you are using a x64 operating system, make sure you install both the x86 and the x64 version 6: Verify that you have the latest Java version and that you don't have older versions using the Java uninstall applet: https://java.com/en/download/uninstallapplet.jsp 7: Move the exception.sites file back into C:\Users\user_name\AppData\LocalLow\Sun\Java\Deployment\security (replace user_name with the profile name of the user logged into Windows) - if the directory doesn't exist, make the directories missing to complete the path 8: Try viewing TGML graphics again

Issue When a XIF file contains NCI's (SCPT's and UCPT's) default values (NVVAL) must be described in the XIF file. In some cases if NCI's are present, but some or all NVVAL initializers are missing commissioning the device will fail. For information regarding NCI's that are part of a FILE definition, please refer to Understanding the FILE part of a XIF file. Product Line EcoStruxure Building Operation, TAC Vista Environment LonWorks XIF Cause When commissioning a device default values to configuration variables must be assigned. If the tool (TAC Vista, SmartStruxure, LonMaker, NL220) does not know what default value to assign, it can cause an error. Resolution Make sure all NCI's have proper initializers defined. Read XIF file - NVVAL initializers.pdf guide as reference. Here is an example of a NVVAL section: VAR nciHrtBtRcv 2 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,48; 107 * 1 4 0 2 0 0 VAR nciHrtBtSnd 3 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,49; 107 * 1 4 0 2 0 0 VAR nciLocation 4 0 0 0 1 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,17; 36 * 1 4 0 31 0 0 VAR nciDeviceName 5 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,6\x80,3; 36 * 1 4 0 31 0 0 NVVAL #VAR nciHrtBtRcv \x00,\x00 #VAR nciHrtBtSnd \x00,\x00 #VAR nciLocation = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00 #VAR nciDeviceName = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00

Issue Difference in Triggered time and Timestamp Product Line EcoStruxure Building Operation Environment SBO Alarm view Cause In alarm view there, there are two timefields: "triggered time" and "time stamp." Resolution The Timestamp is the time at which the most recent state change occurred to the alarm. It is when the AS or ES received/detected the state and logged the alarm. The Triggered time is the first occurrence of this alarm. It could be when the alarm was originally detected, before possibly going in/ out of alarm several times. It could also be the time stamp when detected by a field controller. Triggered Time Stamp behavior also clarifies a few things on when they are updated.

Issue Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network. Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconics Cause Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network. Resolution By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115. The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs. The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat. One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system. For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009. A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility. For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Issue Need to bring Continuum system into SmartStruxure. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3, Continuum v1.94 system with BACnet bCX and b3 devices Cause b3 devices under the bCX become BACnet devices as if they were 3rd party BACnet devices. Resolution Test Environment: Cyberstation 1.94, SmartStruxure 1.3 Released, (1) AS-B, (2) bCX4040, one bCX hosting (2) B3 devices. Do BACnet discovery from SmartStruxure. Both bCX's and the b3 devices can be seen From the Hardware\BACnet devices folder, multi-select both bCXs and drag them into the BACnet Interface\IP Network. Upload their BACnet objects to SmartStruxure. From the Hardware\BACnet devices folder, multi-select both B3 controllers and copy/paste them into the BACnet Interface\IP Network. The B3 devices are hosted as, and look like, generic BACnet devices. Once the two B3s have been copied to the IP Network, an upload to SmartStruxure can be done. BACnet Digital Values and BACnet Analog Values on the b3 devices can be seen updating on a SmartStruxure listview. Note: Currently in SmartStruxure v1.3 there is no method to multi-select and host B3 Devices, within an MS/TP network. This functionality is part of the Continuum Migration project (a future version). Also check out the b3 VAV Quick Start Video on the Exchange.

Issue References Guide and changes from release 1.3 to release 1.4.x and forward Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with regards of release 1.3 to release 1.4.x Cause In release 1.3 and earlier the reference system was relaxed allowing for bindings to be created in ways that made the applications error prone. In release 1.4 this is now being more strictly controlled, which will allow the system to: Help the user to not unintentionally create faulty combinations of references, resulting in bad/unpredictable application behavior and last man win situations Better understand and control how references will behave in copy/paste/move/delete situations. Improve performance in the system, e.g. the limitation of variable connectors is removed. For the complete Reference Guide, please download the pdf from the Download Center For instructions on how to upgrade an Automation Server and how to get the conversion log, See Upgrading Automation Servers from 1.3 to 1.4. For explanations of the entries found in the conversion log, See AS Conversion Log Analysis. Resolution What has changed There are 2 areas which have changed:   1. Rules Programmatic control: A reference means that data is sent from A to B. In Release 1.3 it was possible to send data from A to B and from C to B. This gave a "last man win" situation. In Release 1.4 it is only possible to send data from exactly one source to a recipient. This means A to B and C to B is no longer allowed. User control: This is where properties are displayed in graphics, watch windows and other client components. In release 1.3 it was possible to change a property that was programmatically controlled. This gave a "last man win" situation. In release 1.4 it is not possible to change a property as a user if this property is programmatically controlled by something else. The property will automatically be read only for the user.   Public signals: In release 1.3 and earlier, it was possible to programmatically control a public value in programs. Public signals are intended to be used for user control, while inputs are intended for programmatic control. In release 1.4 this is now changed to the following: Public signals in programs (FB/Script/Menta) can be referenced by user control - NOT by programmatic control Public signals intended for programmatic control must be changed to inputs and rebound. This will give the following benefits: Public signals cannot be forced, while inputs can. If a user needs to take control of a programmatically controlled input, via e.g. graphics or watch window", he will force the signal and there will be no risk of a program overwriting the user value. As stated above - if an input is programmatically controlled, this will for the user be read only. However, force is still possible. There is no more risk for "last man wins" situation between user control and programmatic control. The system will remove any ambiguity with these new sets of rules. Update: Release 1.4.1 and later version add the feature of binding to PVB/PVI/PVR back. But for Script, it still keeps the same. LonWorks Local Node nvis: In release 1.3 it was possible to programmatically write to local node NVIs. These NVIs exist to receive data from the LonWorks network. This gave a "last man win" situation. In release 1.4 it is no longer possible to programmatically control local node NVIs.   2. Definitions In release 1.3 a reference could be a) relative b) system absolute c) server absolute In release 1.4 a reference will be a) "normal" b) Locked A reference created by the user will always be normal (which means relative). In the bindings view the user can then choose to "lock" a reference (which means server absolute). The references will behave identically until a copy/paste (or import/export)  operation is done.         Upgrade Upgrading from release 1.3 to release 1.4 will apply the new sets of rules. It is there for very important to read the log to understand if any existing references in release 1.3 will be impacted during the upgrade For AS: In the Device Administrator the logs are available before the upgraded DB is deployed to the AS. It is up to the user to either examine the upgrade log, make changes in running release 1.3 and rerun the upgrade, or to make the changes after upgrade. It is recommended to do changes prior to upgrade to ensure a fully functional system directly after upgrade. Some warnings are benign and can be disregarded, please refer to release notes for more information. IF an upgrade detects that references will be impacted, the user will be informed about this with a orange progress bar indication and a written information that the upgrade succeeded with warnings. After upgrade, all invalid or unresolved references will be visible from WorkStation for further examination if needed.

Issue What is the unit load of SE8300 that will help me to count how many SE8300 controllers that can be added on AS ComA and ComB Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SER8300 room controller SE8300 room controller Automation Server Cause Documentation does not state the unit load of the SE8000 range Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SE8000 range use the ADM4850A transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/8 UL load. In addition the 100K local bias resistors have been eliminated and therefore the 1/8 UL of the transceiver would be the total UL presented to the bus by the SE8000.   Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus ADM 4850A0 0.125 Yes None None 0.125 Yes** ** Unlike the normally recommended interconnection of the communication common/reference (ground) terminal on all bus devices such as documented in the generic application note for the isolated RS485 bus interfaces, the Viconics bus should be operated with the communications REF (reference) terminal open on each SE8000 and not connected to the bus shield wire, or to any other circuit. Based on the above the total number of devices can be calculated as 32/0.125 = 256 The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore an Automation Server is limited to 127 devices per com port (254 total per AS) so this should effectively be the limiting factor.   Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

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 Alarm Control Panel items created within the Enterprise Server are not been pushed down to the Automation Server. Product Line EcoStruxure Building Operation Environment StruxureWare Buildings Operation 1.3 SP1 Cause There seems to be a corrupt entry in the Automation servers Resolution Log into each Automation server and remove the Lead object from the Alarm panel. Refresh the automation server and the categories are now editable. Delete all user created categories leaving the default Energy Exceptions. Delete all the Cause Notes, Action notes and Check lists. Do the same procedure on all Automation Servers. Log back into the Enterprise Server and then on each Automation server add the Lead object back into the Alarm Control Panel that was removed in step 1. The Enterprise Server will now distribute the entries to the Automation server. If this fails, ensure that all firewalls are open between the AS and the ES. You may want to use the SBO Firewall Config Tool.

Issue Archiving historical information Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Serve Workstation Cause Options for archiving historical information Resolution Archiving of historical data is available via WorkStation and Enterprise Server or WebReports Server. (Archiving is not available via Automation Server or WebStation, also the IE built in option to "Export to Microsoft Excel" has not been implemented) The Archive options on the ES are shown below. A manual archive can be forced by right clicking on "Archive Settings" and choosing "Actions" then "Create archive(s) now" NOTE1 - CSV option currently produces a Semicolon Separated Value file. NOTE2 - Individual logs can be saved to a CSV or XML file from an AS or ES within WorkStation only, see How to Export a Trend Log List as a .csv File.   The .CSV file that is used by SBO to export logs uses a semi colon to separate the fields. This makes it suitable for use in all countries around the world. Some countries use the comma to signify decimal places, so they would show a temperature of 22.5 DegC as 22,5 DegC which would confuse a CSV import with Comma delimiters. CSV files can have many delimiter characters not just commas. To show the formatted data in Microsoft Excel the following options can be used: One option is to rename the SBO log file as a .TXT file, then from Microsoft Excel, go to Open a file and select the type from the drop down list a "Text file". Browse to your log file and press Open. It will then start the Text Import Wizard. Choose the "Delimited" option and go to the next page. Here select the "Semicolon" option, select next, choose a date format and press finish. This will show the data formatted in columns as shown in the manual.   A second way to show the data is to open the .csv file in Microsoft Excel where all the data will be shown as text in the first column as per your description. Select the first column. Then go to the "Data" tab and start the "Text to Columns" Wizard. Select "Delimited" Original Data Type. Press Next. Select the "Semicolon" as the delimiter. Press Next. Change the date format if required and press Finish. This will also show the data in individual cells. Also other vendors Open Office applications may be used that unlike Microsoft Excel will allow semicolon delimited files to be opened directly.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue Upgrading an AS results in an empty database. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 StruxureWare Building Operation 1.1.0.362 to 1.2.0.767  Cause When upgrading the database, the Enterprise Server (ES) upgrades without error, but when upgrading the AS, the result is an empty database. Resolution StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 The problem is caused by the initial engineering of the system being carried out on an old AS that was not LON or BACnet specific, copying into new hardware at R1.0 then when upgraded to R1.1 the upgrade fails due to the wrong type of AS being used (LON or BACnet). This practice is not common place and rather rare. When the trace log is examined, they find that the upgrade fails due to the fact that an illegal object type is attempted to be created – a BACnet interface. This is not legal in an AS-L. The reason that this occurs is that the backup file is from an AS-L that had been restored from a 1.0 AS-B backup file. Check New Release or Upgrade StruxureWare Building Operation Site Software. The issue you face could possibly be a procedural one and this article clearly defines the steps. StruxureWare Building Operation 1.1.0.362 to 1.2.0.767 The solution is identifying problems with a period, space, or other character in names. Placing a period at the end of a name or accidentally having a space at the end is suggesting something is following or further action. If using BACnet, please see the note below. Problems with bindings which were still in tact when values were removed also are a potential issue and not properly removed.    Work Around: Backup AS Upgrade PC to 1.2 Open Device Administrator Upgrade AS to 1.2 DO NOT close Device Administrator Open StruxureWare Workstation Log into AS If Database is Blank go back to Web Browser Connect to AS Log in In the top right hand corner of the screen select Setting>Device Configuration Select the Server Log tab Click “Get all log files” Once downloaded, open “trace” using Notepad Click Edit>Find Type the word “nsp.csc.UpgradeManager ERROR:” The error lines run from date stamp to date stamp so isolate the line beginning with the year and ending with the next instance of the year. Here is an example: 2012-08-29 16:39:32.990 [32] nsp.csc.UpgradeManager ERROR:    Error Parsing Dump Objects:  RecoverableException: source/Path.cppy) ) Error: Invalid_Path (0x10001), module Coml(11), moduleCode 0, dispString "Heatsink Temp.", techString "Path& Path::Append(const UTF8String& name)"  The “dispString “_______”” section of this line will give you the object name that contains an illegal character. Downgrade the AS back to 1.1 Locate the dispString object and change the name so that it does not contain any illegal characters. This is typically a name ending in a period. NOTE: when the rename dialogue pops up, it will indicate that an illegal character is present to confirm you are modifying the right object. Backup the AS Re-Upgrade the AS to 1.2 If the upgrade fails, repeat steps 9-20 or call product support. Be prepared to provide a Db backup at 1.1 as well as the trace file from the 1.2 failed upgrade. BACnet Note: A BACnet device including an object name "East Duct Max." is no longer valid because of the illegal character at the end of the name. Before upgrading the ES from 1.1 to 1.2, remove any full stops/periods from any object names. "East Duct Max." is changed to "East Duct Max"  Other illegal characters include *°?|/"<> or ~ and an object cannot begin or end with a white space or period. Select TPA-SBO-12-0008.00 - ES upgraded from 1.1 to 1.2 loses database to review this TPA.

Issue Links not working after TGML conversion Converting I/NET graphics to TGML using the "Create Source Tree" option Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.44 Cause I/NET stored graphics on the hard disk and allowed for complex folder structures to be used in organizing those graphics. When these graphics are converted to TGML, this structure may need to be preserved in order to prevent duplicate graphic names. Resolution For this example I have created a site with 3 buildings containing Identical I/NET graphics. Each Building has a summary page and a VAV page. All pages link back to a home page. In I/NET select System>Export Graphics to TGML(you can also right click on the I/NET interface in StruxureWare Workstation) Set your Source and Destination Path and click All Yes.  When you set your destination path, it must point to a folder that already exists in Windows.  The Export INET Graphics to TGML tool does not create this directory Notice that the default setting is to "Use destination path" If we click convert with that option, we will get only 3 graphics.  The graphics from other folders with the same name are over-written. Select the "Create Source Tree" option, ensure the correct graphics are scheduled to convert and click convert. Notice that In Windows Explorer a new folder structure is created that is identical to the original folder structure. Open StruxureWare Workstation. Create a folder system that matches what is on the Hard disk. Drag and drop the TGML files from Windows explorer to the corresponding folders in StruxureWare Workstation. Test you graphic links to ensure everything is functional. Note: Once the graphics are imported, StruxureWare will allow you to move them freely without breaking the binding between pages. There is another way to import all the I/NET graphic folders in one time. Refer to Import all converted I/NET graphic folders into EcoStruxure at one time.

Issue Not all 3rd party manufacturers use the same Modbus addressing. Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RTU X Driver bCX1, CX controllers, NC2 Building Operation Enterprise Server Building Operation Automation Server Cause Not all manufacturers use the same Modbus addressing. Resolution Many manufacturers have put their own slant on the "Modbus Standard" for addressing and number formats. The standard only defines 16 bit integer and binary data, but many manufacturers needed to use long integers (or swapped) and floating point numbers. They will transmit them as 2 integers over the protocol, then the receiving system needs to interpret them accordingly. To cope with this, special function codes were added which cover most formats. There are various interpretations by different 3rd party systems on addressing. Some number from 0 and others starting at 1. Some require a 30000 or 40000 offset including in the address, depending on I/O type. What is implemented in the X Driver is that whatever decimal address you enter in the X Driver point is what is sent down the bus. If the other system supplier is asked exactly what address they want sent down the bus, that is what is required in the X Driver point. Sometimes this is not the address that is on their datasheets. Sometimes there may be a need to add or subtract a value of 1, 30000 or 40000. This article was written for Continuum, but is still relevant to EBO Also see Helpful Modbus register Information for further information on Modbus registers.  

Issue When adding Shadow Schedule in AS, it isn't synchronized with the Lead Schedule in ES. This issue only happens when  there is an Exception schedule assigned with another Calendar added to the Lead Schedule in ES. Error: "cannot verify lead object status" Product Line EcoStruxure Building Operation Environment SmartStruxure Lead and Shadow Cause If a Lead Schedule contains an Exception with another Calendar assigned in ES, and a Shadow Schedule needs to be pointed to this Lead Schedule in AS, both the Shadow Calendar and Shadow Schedule need to be created and pointed to corresponding Lead Calendar and Lead Schedule. If only Shadow Schedule is created, it will fail to update to Lead Schedule, or even wipe the original setting with a blank schedule. When involving Calendars the following should be considered: The only way that the lead and shadow relationship can be maintained where calendars are concerned is where the calendar has the same name and is at THE SAME RELATIVE PATH as it does with respect to the lead schedule. Consider the following examples: Example 1 - Lead Schedule is at Root and Shadow Schedule is at root and Referenced Calendar is at root. - under these conditions there is only a need for one Calendar object. The Lead Schedule has an exception that references the calendar at the root and everything works great. Example 2 - Lead Schedule and Referenced Calendar are in Folder 1 and Shadow Schedule is in Folder 2. This will not work because the Shadow Schedule is trying to reference a calendar at the same relative path, i.e., in Folder 2, and there is none there. Example 3 - Lead Schedule and LEAD Referenced Calendar are in Folder 1 and Shadow Schedule AND SHADOW CALENDAR are in Folder 2. This will work fine. In simple terms keep the names and paths within the ES and AS consistent (the same) to avoid issues. Resolution Before the steps below, ensure the communication between AS and ES is OK. Refer to Binding between ES and AS or two AS shows Unresolved and Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server. If the communication is fine, continue to the following steps: Create Lead Calendar and Lead Schedule in ES, and assign the Lead Calendar to the Exception of Lead Schedule (Should already done before). Create Shadow Calendar and Shadow Schedule in AS, and point them to corresponding Lead Calendar and Lead Schedule in ES. Now the Shadow Calendar should be able to synchronized with the Lead Calendar after changes have been made to the Lead Schedule.

Issue When upgrading to 1.4, the reference system will be changed to follow newer more strict rules. Product Line EcoStruxure Building Operation Environment Device Administrator Cause With the release of 1.4, StruxureWare now has a tighter control on bindings. This is to prevent users from creating bindings which hinder system communication. When a system is upgraded from 1.3, to 1.4 any bindings that do not follow the new rule set will be dropped. Here are the 3 major items for this new rule set. See Reference Guide and References beginning with 1.4.x for a full explanation. Public Signal bindings will be dropped Multiple bindings will be restricted to one Bindings to Local Node NVIs will be dropped during the upgrade. Resolution To upgrade the Automation Servers, follow these steps: NOTE: You will need to have a copy of Workstation at 1.3 in order to make changes to the Automation Server during the upgrade process. Use 1.4 Workstation after you have completed Perform a Manual Backup of the Automation Server. This backup must include historic data. Ensure that a copy of that backup is saved to an external disk as a recovery option. Open Device Administrator 1.4 Connect to and Select an Automation Server Click Upgrade Device. Please Read the warning in this pop up message. This will upgrade the most recent backup of the Automation Server. Any changes to the system made since the last backup will be lost at the end of this process. Note that the yellow Progress bar means that you MUST review warning in the conversion log. If the progress bar is Yellow or Red, proceeding may result in irreversible system changes. Click "Open" under the conversion log column. This is very difficult to read in Notepad. Perform a Save as .txt and open this file in either Word Pad or NotePad++ for easier reading Notice the Change in display when the information is viewed in WordPad Use the notes from Reference Guide and References beginning with 1.4.x and the conversion log analysis from AS Conversion Log Analysis to make sure that all objects with WARNINGS meet the new rules. This will require making changes to the system via workstation. Repeat steps 1-8 until you are happy with the conversion log. Please note, that you must perform a new backup to get an updated log. Click on "Download updated database to devices" Click Okay in the pop up Wait for the Installation to finish successfully. If any errors occur, be sure to get a screen shot and contact Product Support Note: If the upgrade doesn't complete correctly on one of the AS, cycle power on the AS, go back to the previous version and perform the upgrade again.

Issue SE7000 Series RS-485 transceiver unit load Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SE7000 series room controllers Cause The room controller RS-485 transceiver unit load is not included in the data sheets. This information is needed to determine the number of BACnet MS/TP devices per RS-485 segment. Resolution Refer to Application Note AN05-RS485-VT7000 and Quick Guide RS485-VT7000. The links to these documents can be found in MS/TP and Modbus RS485 Communications on StruxureWare Automation Server

Issue How can you use Loytec's LPA software with the AS as the interface Product Line EcoStruxure Building Operation Environment Automation Server Loytec LPA Cause A Loytec LPA can be a valuable troubleshooting tool to diagnose communication problems on a LON Fieldbus. Resolution As the Automation Server uses Loytec's Lon chip, it is possible to use Loytec's LPA software over the Lon port on the AS. Some Prerequisites:   A license is required to use the LPA software. Either the "LPA-IP" or the "LPA-IP-SW" package depending on your setup. LPA (loytec.com) shows a product overview.   Downloads | Software - Device Firmware and Readme (loytec.com) to download the software. Create a free login in order to download software from Loytec's home page For additional help Buying and registering the LPA software read LonTalk Protocol Analyzer Software License and Registration Steps Lonworks troubleshooting read Troubleshooting LON Network Communication Troubleshooting Lon communication with TAC Xenta's read Actions for reducing Bandwidth in a Vista network There is a limitation when using LPA through an AS. Refer to Not all traffic on a segment is captured when using the LPA through an Automation Server Please make sure that you have a LonWorks interface configured in the Automation Server before proceeding. You will also need to add a Local Node to the interface and to commission it. Make sure to set the LPA state to Enabled under the Advanced tab in the properties for the LonWorks Interface: Once the above have been checked and understood the following steps can be performed:   Start the LPA software Click on "Profile -> Network Interface..." Click on "Remote LPA Assignment" Click on "Add Device" Enter the IP address of the Automation Server, click on "Get Info" and click on "Add Device and Restart Search" Select the Automation Server device and click on "Assign/Add" Select the interface you want to assign to the Automation Server, and click "Assign" With the interface assigned, click "OK" Select the Building Operation interface and click "OK" Now the LPA software is using the Automation Server as the interface Start a new LPA log