Building Automation Knowledge Base

Issue The EcoStruxure Web Services Interface has been successfully setup in a Enterprise Server but cannot see the Vista objects / points in Workstation Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation 1.4.x TAC Vista SmartStruxure Interface TAC Vista 5 and above Cause The Web Services interface hosts the Vista objects in the System / Hardware / EcoStruxure Web Services / TAC Vista folder, these must be hosted to the Server to become visible within Workstation.  Resolution Once you have navigated to the System / Hardware / EcoStruxure Web Services / TAC Vista folder you will see the list of objects available associated with the TAC Vista user name setup in the TAC Vista SmartStruxure Interface. From the list of Vista objects select the required ones you wish to use within the Enterprise Server database. The right click on the selected folder and select the Host EWS Objects... option. The next option is to select the Vista EcoStruxure Web Service interface that will host these objects. The objects will now be visible within the Enterprise Server / Workstation.   For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure. For additional details see Creating an EcoStruxure Web Service Object on the SBO WebHelp site. 

Issue IP address using DHCP Product Line EcoStruxure Building Operation Environment IP network Cause Bacnet or Modbus IP loses communication Resolution The AS or ES may be configured using DHCP (Dynamic Host Configuration Protocol), this is usually set up using "Device Manager" See Troubleshooting AS configuration issues with IP address. However many other systems use fixed IP address and use the IP address to specify the controller or server. Thus it is usually best to use fixed IP addresses for the Automation Server and Enterprise Server, especially if using Bacnet or Modbus over IP NOTE When the IP address of an AS is manually changed, the IP address of the Bacnet or Modbus IP interface needs also to be manually changed

Issue The Automation Server is constantly using 100% CPU causing a slow operation Product Line EcoStruxure Building Operation Environment Automation Server Cause Check which process is taking the CPU. Cause 1: The cause was found to be a Function Block Program which was corrupt in some way. When trying to edit, open properties or do anything with this Function Block Program Workstation just hang. The root cause of the problem with the Function Block Program was never found. Cause 2: Some schedules have more than one entry for the same time stamp (likely if the process "CScanner" is taken the CPU) Resolution Solution 1: After deleting the particular Function Block Program (which took over 2 hours) the CPU usage was directly down to 20%. Another solution for an AS with the same symptoms: After downloading a new database to the automation server and then restoring a backup the CPU usage went down to normal levels.  Solution 2: Check all schedules for duplicate entries, especially around the time where the CPU goes to 100%. Also check out the SmartStruxure Quick Help - AS CPU and Memory Loading Quick-Help video on the Exchange.

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

Issue When trying to commission a controller into a LonWorks network in SmartStruxure you get a DST error. Product Line EcoStruxure Building Operation Environment WorkStation LonWorks Interface Cause The DST error occurs during the commissioning of the controller when the DST settings are attempted to be downloaded. Resolution TAC Xenta 280 and 300 series Controllers If the DST error occurs when commissioning a Xenta 280 or 300 series controller then check the label on the side of the controller. If there is no /N/P after the model number then it is not a network presentation controller and can not be commissioned in SmartStruxure. For more information see Xenta 280/300 without /N/P designation cannot communicate in a Network.

Issue It is not clear how to register a SmartStruxure system, and what information to write in case it's not a customer site (For example a test bench/controller or engineering PC). Product Line EcoStruxure Building Operation Environment S2Connect Workstation Cause Guidelines are needed regarding how to properly register a system. Resolution Starting in SmartStruxure 1.5, we have introduced a registration process to know more about SmartStruxure systems. In order to know our customer and/or partner better and provide better services we should register our SmartStruxure system with correct information. The SmartStruxure registration process requires a Buildings Exchange account. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Please make sure below points while registering SmartStruxure system. Test site: If you are registering a test site to test registration process, write "[Test]" keyword in Site note*. Demo site: If you are registering a site which is for demo, then write "[Demo]" keyword in Site note. Training site: If you are registering a site for training or you want to explore registration process, then write "[Training]" keyword in Site note Customer site: if you are installing an actual site for customer then DO NOT use above keywords in Site note field *Site note field can be found under Site Administrator tab (Shown below in screen shots) New system registration: If you are registering new system then you continue enter all information in Step 1 and continue to Step 2. In Step 2 you will find a Site note field. Fill the Site note field as explained above.  Already registered system: If you have registered your site without providing above explained details then you can browse to below website https://registration.smartstruxure.schneider-electric.com After successful login; Navigate to Systems -> Site Administrator and click on Edit button, now you can edit Site note field. Registration Process Does Not Complete In some cases after registering either the Enterprise or Automation server, it still prompts you to register when you log back in. There are two different procedures that can be taken to correct this issue. Procedure 1 - By editing the registration and clicking submit again, it can help the system complete the registration. Log into the sever again and either click Register now on the initial prompt or go to Help > Registration once you are in Workstation. Log into the Registration Portal. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Select the server that is experiencing the issue on the right side of the window. Click Edit. Click Submit. Procedure 2 - If procedure 1 still does not work, then the registration can be completed manually by entering the Registration code in the offline mode. Log in to the Registration portal directly through this link (registration.smartstruxure.schneider-electric.com). Select the server on the right hand side of the screen that has the registration issue. Take note of the Registration code. Insure that the Enterprise or Automation server does not have internet access and log into the server with Workstation (In the case of an Automation server you will need to connect directly to it via Ethernet). Click to Register now (Since the server does not have internet access, it will automatically launch the offline registration). Insert the Registration code the three fields provided and click Register now. Also check out the SmartStruxure Solution Connect (S2C) - SmartStruxure Product Registration Registration Quick-help video on the Exchange.

Issue After updating the computers Java version to Java 7 update 51, graphics are not displayed when using Webstation. Then a security warning is displayed. Missing required Permissions manifest attribute in main jar: http://xxx.xxx.xxx.xxx:/com.SE.webstation.Main/applet/applet-1.4.1.68.jar If you don't see the error above, but just get a blank window, please refer to Webstation graphics not working after updating to Java 7 Update 65. Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC Vista Environment Webstation Cause From Java 7 Update 51 and onwards, Java has enhanced the security model to make user system less vulnerable to the external exploits. The new version of Java does not allow users to run the applications that are not signed (Unsigned), Self signed (not signed by trusted authority) and the applications that are missing permission attributes. Risks involved in running each kind of applications: Unsigned applications An application without a certificate (i.e. unsigned apps), or missing application Name and Publisher information are blocked by default. Running this kind of application is potentially unsafe and present higher level of risk. Self signed application (Certificate not from trusted authority) An application with self-signed certificate is blocked by default. Applications of this type present the highest level of risk because publisher is not identified and the application may be granted access to personal data on your computer. Jar file missing Permission Attribute Permissions Attribute verifies that the application requests the permission level that developer specified. If this attribute is not present, it might be possible for an attacker to exploit a user by re-deploying an application that is signed with original certificate and running the application at a different privilege level. Resolution As a workaround, the user can use Exception Site list feature to run the applications blocked by security settings. By adding the URL of the blocked application to the Exception Site list allows it to run with some warnings. Steps to Add URL to the Exception Site list: In control panel go to the Java Control Panel Click on the Security tab Click on the Edit Site List button Enter your site details (This example http://www.SBO-Site.com) Click the Add in the Exception Site List window. Select continue Repeat the process until all the sites AS/ES have been added. Then select OK to complete and OK on the next window to exit the Java control panel. Next time you use Webstation to access the AS/ES you will be asked if you want to run the application. Tick the box so this is not displayed again. Then select Run. The graphics should now be displayed. You will need to repeat this process on any computer you which to use Webstation on.

Issue The License server cannot be seen by either the Workstation or Enterprise Server Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Workstation Building Operation Enterprise Server Cause When attempting to log onto a system using Workstation, or start an Enterprise Server, the license is not seen on a remote License Server. Resolution Make sure your firewall setting is not blocking the license system. For more information read SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96) The system consisted of a PC running the Building Operation License Server. The license on the PC had been generated from an entitlement for an Enterprise Server, Workstation and program editing tools. A second PC was running the Workstation and Enterprise Server programs. Confirming that the correct licenses are available on the License server. On the License Server, select Internet Explorer and enter http://localhost:8888 in the address bar. Select the "Concurrent View" Below shows the page displayed, confirm that the expected licenses are shown. Check that the License administrator has the correct address of the license server. Open the license administrator and select the "License Server Address" tab. NOTE: the @ symbol before the IP Address must be used.

Issue When TAC Vista and the SmartStruxure Enterprise server are installed on the same machine the EcoStruxure web service object will not connect to the Vista Server. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure Solution EcoStruxure Web Services TAC Vista SmartStruxure Interface 1.0 Cause The default ports used by the SmartStruxure Enterprise server are HTTP 80 and HTTPS 443. These are the exact same ports used for the communication between the TAC Vista SmartStruxure Interface and EcoStruxure Web Services Resolution TAC Vista SmartStruxure Interface settings change the HTTP and HTTPS ports to something that is available and not in use on the machine. In the example below HTTP 8181 and HTTPS 8191 are used. After these ports are changed click apply and stop and restart the TAC Vista SmartStruxure Interface service. After these port changes are made login to the Enterprise server and select properties on the TAC Vista web services object. Change the service URL to the localhost address and the proper port that was chosen in the TAC Vista SmartStruxure Interface settings. In the example below http://localhost:8181/EcoStruxure/DataExchange was used. The local IP address could also be used in place of the localhost if needed. Another point needs to be kept in mind is that only the user in the default System user group can be used. Don't try to create other System group. And all the letters in the password need to be in capital in the password field of the window above. This is a defect that will be addressed in the next release of TAC Vista to SmartStruxure interface. For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure.

Issue Setting up the override value to show the damper feedback on an i2/B3 866-v Product Line Andover Continuum, EcoStruxure Building Operation Environment i2/B3 866-V Plain English Script Cause Activate the damper position feature in the 866-V. Resolution SBO: See this video on creating a program that calculates damper feedback position.  Also reference the article How to show damper feedback for an i2/b3 866-V which describes what needs to be done to show damper position and calibrate the damper. Sample objects, code and images showing configuration are supplied.   Continuum: There is a description in the 866-V installation manual on how to activate the damper position feature, but there are some additional pieces of information that this article has been created to address. This was initially to just get the feature working as mentioned in the next section below. Getting the damper feedback operational: Once the end stops are determined initially during the Learn process, the controller can then determine the position of the damper. Create a PE program to set the DamperOutput LCDState = Disabled and back to Enabled in the next line. This will run through its stroke to determine the end stops. ‘Example program named "damperstate" Fall thru, auto start ‘a 2 line program to initialize the stops Line 1 Set damper LCDstate to disabled goto 2 Line 2 Set damper LCDstate to enabled stop To run from the command line Run damperstate Note that the Feedback will not start working until the Damper has gone full stroke in both directions. This will take several minutes. Set the damper point to on or –on depending on the position so it will move Print Damper OverrideValue from a command line or display it on a listview of the damper output after adding the overridevalue column Self Calibration - The LCDState toggle actually activates the "self calibrate" process. It doesn't just enable the feature. It is necessary to know this because you will need to activate the self calibration again whenever the damper is manually moved using the red actuator clutch release button. Using the clutch can cause the damper position to be reported incorrectly. Periodic re-calibration should be as a part of normal procedure for the controller. Once the clutch is used, the damper position will still report, but the value may be incorrect. Re-calibrate recommendation- Use a PE program that recalibrates the damper (i.e. LCDState as mentioned in Section A) on manual command by the service technician on a power cycle or at the end of an occupancy period. Note: For controlling the Damper motor output create an Infinity Output point of type Triac on Channel 1. It can then be opened / Closed like any other Triac output with the use of On, -On or Off commands

Issue Managing communication between I/NET and StruxureWare Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Enterprise server level integration I/NET Automation server level integration StruxureWare Building Operation 1.6.1.5000 and above. Cause Users should manage data flow on the controller LAN in order to maintain efficient communication. Any binds to objects under the I/NET interface follow the settings for the INET Global device scan rate (min) and the INET Global point scan rate (s). By default, this is set to 60 minutes for device status and 5 seconds for point bindings. The INET Global device scan rate (min)  is used to monitor online devices. A device will show offline sooner than the configured setting as all points would show offline.  The  INET Global point scan rate (s) is applied to all binds between StruxureWare and I/NET.  Opening a graphic or watch window will ignore this rule and immediately request values. After that, the scan will update according to the configured setting. A controller can either follow the Global scan rates as by default or use its own setting.  When a controller has the property DCU scan rate or point scan rate set to 0, it will follow the scan rate configured for the I/NET interface. An I/NET 19200 speed Controller LAN will handle a maximum of 10 token cycles per second. Each cycle allows a single packet of information to be passed from a single controller to the server. 1 Packet can contain all data for up to 18 points on a single controller. This means binding to manual, value, and PvControl for 18 points on a single 7718 will take one packet. Binding only the value of 5 points on 5 different controllers will take 5 packets. Adding devices to the controller LAN and adding additional polling will slow down the number of cycles per second on the controller LAN. Resolution All active binds will poll every scan interval. Graphic binds are only active when the graphic is open. Trend Logs will poll every scan interval regardless of the log configuration options.  Whenever possible, use the I/Net Alarm and Trend objects rather than creating separate StruxureWare alarm and trend objects. Trend Log Best Practices: Use the I/NET Trend Extension as outlined in Using I/NET trends in StruxureWare Building Operation please refer to the online help guide for complete information. Create Extended Trend Logs of this information for long term storage. I/Net Alarm Best Practices: Use the I/NET point extension to configure the alarm to be triggered by logic within the I/NET controller. I/NET Alarms have 3 priority options which are Routine, Priority, and Critical. This can be globally assigned to any priority using the I/NET interface messages tab. Other StruxureWare Alarm enhancements are available to I/NET objects as well. Scheduling and programming I/NET from StruxureWare Whenever possible, bind values to a single I/NET controller per controller LAN and then create I/NET Global/Indirect point relationships to distribute this value to other devices on the controller LAN. Using a single controller allows more information to be sent per packet. I/NET Global points will only broadcast on change. In this scenario, the server is polling a single controller ever scan interval and then on change all other controllers are updated. Increase the Point scan rate Using the information above you should be able to calculate how many packets are required for your system for each token pass. If this number increases to the point that more packets are required than are possible in the default 5 seconds, increase the scan rate. You can increase it on specific over loaded controllers or on all controllers together.

Issue General questions and best practices for RS-485 protocol including cable length and terminating resistors Product Line Andover Continuum, EcoStruxure Building Operation Environment MSTP Cause Understanding best practices for installing, cabling, and terminating RS-485 networks can avoid a lot of problems with communication and hours of troubleshooting communication problems. Resolution MS/TP MS/TP stands for Master Slave Token Passing. Each device on the link is considered the master when it has the token. If it does not have immediate need to use the token, it is required to pass the token along to the next device. This is the token passing part. All devices on the link which do not currently have the token are regarded as slaves, and are expected to listen to any messages the current master may have for it. Because all devices take turns being master, the link is effectively peer to peer. Electrically, MS/TP adheres to standard RS-485, physically wired using two-conductor shielded twisted pair cable. RS-485 Cable Specifications Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Velocity of propagation: 78% Capacitance: <12.5 pF/ft between conductors and <22 pF/ft between the conductor connected to ground and the next conductor. Topology Daisy chain bus topology. Star topology can be achieved using Infilink/B-Link repeaters. Maximum Cable Length Cable lengths of up to 4000 ft (1220m) daisy chained from controller to controller on one arm of a star are supported. After 4000 ft (1220m), a signal repeater (b-Link) is required to add more nodes to the network or further extend the cabling. Using a b-Link fiber repeater allows you to extend the length of RS-485 with fiber optic cable, recommended for running cable between buildings and through noisy environments. Maximum Number of Devices TAC's MS/TP RS-485 supports a maximum of 127 nodes overall. Each controller represents a single node on the network. RS-485 Termination The MS/TP field bus requires a 120 ohm terminator resistor at both ends of a daisy chain segment. The following diagram illustrates the connection of the terminator: Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue Can the red crosses (that indicate that a signal is offline) in Vista or SmartStruxure Workstation/Webstation be disabled? Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure TGML Graphics (Workstation, Webstation) Vista TGML Graphics (Workstation 5.X, Webstation 5.X) Cause When a signal which is bound to an object in a TGML graphic is offline, this is indicated by a red cross when viewing the graphic in Vista or SmartStruxure Workstation or Webstation. Resolution This can easily be disabled in TGML by adding a script to the OnSignalChange event: function signal(evt){   evt.preventDefault(); }  Note, this script will only disable the red X when a point is offline. This does not address any issue that might cause points to be offline. A short video is available on this process, to review, please see SmartStruxure - Graphics - Removing Red Crosses.mp4.

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 An Energy Expert system is being moved to a new server and/or the virtual image is being upgraded. The historical records held in the SQL database of the Power Monitoring Expert (PME) system need to be backed up and properly restored on to the new server. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Power Monitoring Expert (PME) Enterprise Server Cause The system administrator has deemed it necessary to upgrade the Windows server that the Energy Expert system is installed on for security and/or resource reasons. Resolution It is important to remember that an Energy Expert installation is really just two Schneider Electric offers, EcoStruxure Building Operation and Power Monitoring Expert, installed together and set up to pass information back and forth. This means that appropriate steps must be followed for each system to backup the historical data and properly restore it on the new server. For more detail regarding how the system is laid out, please see the Difference between EcoStruxure Energy Expert (Power Manager) and Power Monitoring Expert (PME). Steps to move an Energy Expert database Backup the Power Monitoring Expert (PME) SQL database, dashboards and reports. The Configuration Manager tool available on the Exchange can be used to back all of these items up automatically. Run the tool on the existing server and it will create a zip file to be used later on when restoring to the new server. See Migrating a PME 8.0 System to a New Server for more information. The Schneider Electric Technical FAQs website also contains many other helpful troubleshooting articles for PME including different versions of the product. Return the Energy Expert license(s) from the Floating License manager in order to move them to the new server. For more information see Video: Licensing Guide for Power Monitoring Expert (PME) 8.x and 7.2.x and ENM 8.3.x. If moving the Enterprise Server, make a historical backup of the EcoStruxure Building Operation (EBO) ES from the existing server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES for more information. If the Enterprise Server and other EBO licenses are installed on the existing server, then they may need to be returned as well so they can be moved to the new server. See Removing a Local License or Returning a Network License for more information. Next the ETL project files must be retrieved and saved so they can be moved to the new server (if using architecture 1 in the Energy Expert offer). Go to the file location below and save all ETL project files that are needed on the new server. C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs If moving the Enterprise Server, install the EBO software on the new server, rehost the EBO licenses, and restore the EBO server backup(s). See Restoring the EcoStruxure BMS Server for more information. Install the Energy Expert software (the software includes PME, ETL and the integration utility). The information on how to download the Energy Expert software can be found on the Exchange. Once the software has been installed, the Energy Expert license can be hosted to the new server in the Floating License manager. Next, install the PME Configuration Manager tool on the new server. The zip file from step 1 can be loaded using this tool to restore the SQL database, PME dashboards and PME reports. Add the previously saved ETL project files to the same location on the new server C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs Since the server has changed, the configuration settings must be updated in the ETL projects to reflect the new server name. The settings in the EWS interface on the EBO server will also need to be updated as well. Note: It may be easier to delete the existing EWS interface in EBO and then use the integration utility to create a new XML import file to simply rebuild the interface.

Issue Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 SP1 Cause Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Resolution Setup of the NIC852 network interface for the ES is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.9 L-IP router setup is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.10   Here are some additional points not covered in the Reference Guide: To use the NIC852 as a network interface for the ES, you must configure the Loytec LConfig software to run as a service.  See Not able to get Service pin from LON devices connected with Loytec NIC from ES for more details. The L-IPs must be used in Smart Switch mode in StruxureWare.  There are two Smart Switch modes: 1.  Smart Switch Mode 2.  Smart Switch mode with No Subnet Broadcast Flooding. Only use the first of these modes.  This should be the default, out of the box.  See the L-IP User Manual for details of the DIP switch positions for each mode. The ES version 1.3 can host up to 100 Xenta devices + 100 LON devices in total. These can be divided across 5 logical networks (different domains). It is possible to have multiple L-IPs in the same network if needed - but the limit of 100+100 is per ES, not per network or L-IP. Loytec recommend that in Smart Switch mode an IP channel should have no more than 10 L-IPs and packet rates no more than 500 packets/s. If additional Xenta/LON devices are needed you can add them to one or more AS, below the ES. Observe the standard Lonworks guidelines when creating your network topology e.g. maximum number of devices per network segment, maximum length of runs for the chosen cable type.  Group your devices so that network traffic across channels is minimized. StruxureWare is unaware of your physical network topology - it just sees it as one big channel.  It will reserve a different subnet for each Xenta group you create, starting at subnet 253, but each Lonworks device you create will just be assigned the next available subnet/node address, starting at subnet 254 node 1.  This means that devices with the same subnet address will most likely appear on multiple physical channels. The Loytec L-IP in Smart Switch Mode can still provide effective routing in this situation as it builds its routing table based on the physical location of subnet/node addresses, not just subnets.  Other manufacturers' routers, even in learning mode, may not be so forgiving.

Issue What are the intervals for Trends when using StruxureWare Building Operations Product Line EcoStruxure Building Operation Environment Enterprise Server or Automation Server Cause Questions regarding what the interval in time is for trending Resolution Intervals can be in Days, Hours, Minutes, Seconds, and Milliseconds. . Trend logs can be of different types and used for different purposes. All logs in StruxureWare use circular storage. The interval trend log collects data at a specific time interval. Each logged value is stored as a record in the trend log. Use this trend log when the logging interval is less than 1 hour. You create interval trend logs using WorkStation or WebStation. In WorkStation, you configure the properties of the interval trend log to meet the specific needs of your site. The interval trend log does not record the values between the intervals. An interval log checks the monitored value at each interval and records the new value if it differs from the previously recorded value by more than the delta. Delta is the difference between the current variable value and the last log value. To log a variable according to the time interval, use a delta of zero. You use an extended trend log to transfer records from a trend log. An extended trend log can be connected to a trend log or connected in a series to another extended trend log. Only one extended trend log can be connected to a trend log. You create and configure extended trend logs using WorkStation. The extended trend log is often saved on a higher server level with more storage capacity than the server of an ordinary trend log. This extra storage capacity enables the server to store more records before it overwrites old ones. The extended trend log can be viewed in a trend log list or a trend chart. Trend log lists and records can be exported in two different formats: CSV (Comma separated values) is a standard file format for digital storage of data structured in a table of lists form. The CSV format can be used by Excel and in databases such as SQL. XML (Extensible Markup Language) is a standard file format for structured data and can be use with a lot of different tools. One last suggestion is the number of records, depending on how many records you want to store is important. For example: a single one minute interval Trend Log, and for 66 day, that would be 99,792 records. The maximum is 100,000 on an AS, so take this into account when configuring. This is why Extended Trend Logging is important. Check out Maximum number using StruxureWare Building Operation (Scalability and Capacity) for information on trends and extended trendlogs.

Issue During the installation of Workstation on a PC that didn't previously had any SmartStruxure software installed, you can get the message: "Failed to install XXXX redist, error: 3010" Product Line EcoStruxure Building Operation Environment Workstation Cause One of the build in Microsoft Visual C++ Redistributeable (VCRedist) installers (2008, 2010, 2012) is failing for some reason. Resolution Restart the PC and start the installer again Note: There is a similar issue but with error 1603, if you get this please see Getting the error "Failed to install XXXX redist, error: 1603" during installation.

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 While upgrading a database from 1.7.1 to 1.8.1 that has already been prepared, the upgrade log states that a MAP file is missing (similar to one shown below), and the upgrade is cancelled and reports "Database upgrade failed!" MAP file is required for upgrading the type public.lon2.devicetemplates.pidxxxxxxxxxxxxxxxx but none could be found Product Line EcoStruxure Building Operation Environment Upgrade LonWorks Pre-upgrade add-on Observed in version 1.7.1 and 1.7.2 Cause At some point in a previous version of StruxureWare Building Operation, the import of a device template has gone wrong in the sense, that the XIF has been imported and parsed correctly, but stored incorrectly. That means that we have cases where the actual content of the XIF stored in the database, can either be another completely different XIF, or even in some cases just random files. The issue can be verified by performing a "Content Analysis" using the "SBO xbk Analyzer" version 1.0.9 and above. You'll get a message like this: Error in XIF file: Mismatching program ID (SBO: 90001347000604A0 - XIF: 90:00:13:47:00:06:04:3C) This means that Building Operation has a device template with PID 90:00:13:47:00:06:04:A0 but that the actual file this device template points to is 90:00:13:47:00:06:04:3C Resolution A hotfix has been produced to allow replacing the wrong XIF with the correct one. With the following procedure you can manually fix the issue if you don't have the hotfix: Firstly ensure you have run the Pre-Lonworks upgrade configuration and try the upgrade again. Check if the template is in use by searching the specific template while logged in directly to the server Once the device has been identified, proceed with the following steps: Record Neuron ID(s) - this is required since the Export Process does not retain this information. Export device(s) If you have multiple devices you can Export the folder containing these devices, it is not critical to export the devices individually. Delete device(s) remembering to keep references. Import latest XIF for device From WorkStation select: File > LonWorks > Device Template Browse in the correct XIF. Import exported device(s) in step 2 Commission device(s) Run the Pre-Lonworks upgrade configuration The database should now successfully upgrade.

Issue After installed I/NET, DBCreate will never pop up to create a new database, which will cause I/NET never launches. Backup and Restore button are greyed out when opening DBCreate, which also will cause I/NET fails to launch. When restoring database, an error will show up, saying that version is incompatible with this server. When restoring the database, an access deny error will show up. Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause SQL default instance is not created correctly. SQL2005 BCM is not installed correctly if SQL2008 is used, or there is a database version mismatch for I/NET. This is usually caused by restoring new SQL database to old version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Windows permissions are not enough to do the restoring Functionality of the host pc and the database seems to be inconsistent. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution If you are using I/NET 2.4x, and already have a named SQL instance on the computer (for example, TAC Vista 5.1.7 or higher has been installed, with a named instance installed called TACVista), I/NET may fail to recognize it, while also fail to create a default instance. Similar kind of warning will pop up during the I/NET installation: Under this condition, use your current SQL server installer or browse to /SQLExpress folder of I/NET installation CD, to manually create a new default instance. You can refer to the guide within the /SQLExpress folder about how to create it. As long as the default instance is created, DBCreate will pop up immediately and a new database can be created. If 64 bit Operation System is used, refer to Installing I/NET Seven on a 64-bit operating system for the detailed guide. Also refer to Installation guidelines for installing I/NET and Vista on the same PC for more details about installing I/NET and TAC Vista on one computer. If SQL 2008 or SQL 2008 R2 is used, be sure to follow the correct steps about how to install them: I/NET Seven with SQL 2008: I/NET Seven with SQL 2008 Installing I/NET Seven on a 64-bit operating system: Installing I/NET Seven 2.42 or higher on a 64-bit operating system If SQL 2008 is installed correctly, please refer to Data Base maintenance before performing an upgradeto perform a forced upgrade for the database. Refer to Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate: Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate Refer to DBCreate backup access denied using Windows Server 2008 R2 Standard and Microsoft SQL 2008 R2: DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2. Refer to Unable to Create a backup in DBCreate: Unable to Create a backup in DBCreate. Refer to Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached: Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached.

Issue The built in logs for troubleshooting communications from SmartStruxure ES/AS to SmartStruxure ES/AS remove the need for network captures for SmartStruxure communications. However, SmartStruxure to BACnet continues to be ideal for traditional means of network captures. The most common capture method is Wireshark when dealing with BACnet device to BACnet device communication. Product Line EcoStruxure Building Operation Environment SmartStruxure BACnet ES AS Cause The need to troubleshoot communications issues from device to device whether this is ES to AS or vice versa. The need to troubleshoot BACnet communications Resolution Network captures are beneficial in troubleshooting the following cases: Connection issues between SmartStruxure client and AS/ES. If customers complain their client cannot connect to an AS/ES, a capture run from the client PC can be very useful. However, SmartStruxure uses TCP/HTTP and the payload is not easy to decode. There are no Wireshark decoders to help out, but the good news is that there is in communication logging built in to SmartStruxure that can replace the need for network captures. (See Error logs from the Enterprise Server for ES and see Error logs from an Automation Server and Enterprise Server for AS) Communication Status problems between servers and controllers (for example BACnet controllers). The location of where the captures is taken can be very important. The best place to capture is at a switch directly connected to the controller. This may be difficult because it will require putting a “dumb” hub between the switch and the controller or finding a port mirroring switch. When you are not receiving BACnet alarms when expected. When you are not receiving COV notifications when expected When a trendlog is trending external point To evaluate the health of a network. ARP broadcast traffic can flood networks and can create connectivity problems on BACnet/IP networks. If this is the case then a customer can take action by segmenting their BMS to a VLAN. Performance problems on graphics where a large number of the point displayed are BACnet MS/TP bus performance is poor or MS/TP device is offline Using a USB RS-485 adapter can permit the capture of packets on an MS/TP bus. Wireshark can then be used to decode the packet captures. This can show token passing problems as well as traffic loads. Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.