Notifications

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "ecostruxure building operation"

View in: "Building Automation Knowledge Base" | Community

1823 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

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.

Issue What is the maximum character length a value (object) name can have? What is the maximum character length an alarm name can have? What is the maximum character limitation on the Description? What is the maximum character limitation on the Alarm and Reset messages? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation (all versions to 1.3 SP1 (1.3.0.10100)) Cause Require an understanding of what character limits are applied within Building Operation Workstation Resolution There is no documented limitation, the following numbers are those that have been tested: An object and alarm name: 1900 character limit. An object and alarm Description: No found limit here, either in entry or saving. An Alarm message and Reset message - no found limit here, either in entry or saving. It is important to note these are limitations on StruxureWare objects only, when the actual object is also represented in another device, like a BACnet or LON device, then there may be restrictions at that device. A b3 is an example of this where you can make the object name with 1900 characters but the BACnet name will be limited to 32. Also refer to StruxureWare Building Operation object names limitation on what characters are allowed to be used.

Issue Can the AS, work independently or together without an ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site, any version Cause Are bindings or other communication between two AS possible if there is no ES? Resolution The AS, is designed to work independently or in conjunction with others, or in conjunction with an ES. Points, Bindings, Schedules, etc. can be setup on the AS using the Workstation. With the ES service stopped, the Points, Bindings, etc. on the AS continue to reflect the values on themselves or if the Bindings interlink between multiple AS. For multiple AS configuration check the AS are listed in the Communication tab of each other. From your workstation highlight the AS and the tabs shown are List View, Device Discovery, Date & Time, Communication, and Properties. Under Communication the other AS devices should be listed as well as the ES. For information on a Automation Server alone at a site and licensing requirements, see License requirements for AS alone at a site

Issue When attempting to edit a graphic through WorkStation, the Graphic Editor crashes with the following message: "Font xxxxxx does not support style xxxxxx" Product Line EcoStruxure Building Operation Environment Building Operation Graphics Editor Font Cause When a Graphic object is edited, the editor does not open and an error message is presented, this error is caused because the font is missing. Resolution Dependant on the Windows operating system in use, the process for confirming that the "Tahoma Regular" font is missing will vary. Windows XP Open the Control Panel and select "Fonts" and confirm that the font is missing. Windows 7 Select the Windows button and then search for "Font". Choose "View Installed Fonts" and review the fonts to see if Tahoma - Regular is available. If this font is missing, then copy it from another PC, download it, or visit http://support.microsoft.com/kb/314960 which deals with adding / removing fonts. If Workstation is crashing when you see this error, please see WorkStation crashes when opening some TGML graphic pages following a Windows update.

Issue Missing "restore" option when right-clicking on my Enterprise Server even though logged in as admin user. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and above Cause The admin user is member of multiple groups. The software permissions within that group have deny access set to Server Restore as well as other commands. Resolution Move the 'admin' (or Administrator) user to only be a member of the Administrator group and not any other groups otherwise you need to ensure that the correct permissions are set to each group and the correct users are assigned to those groups. For further detail of User Permissions in SmartStruxure Solution refer to following How software permissions work in SmartStruxure.

Issue WorkStation crashes when opening some TGML graphic pages following a windows update Product Line EcoStruxure Building Operation Environment Windows 7 64 bit SBO v1.6.1.5000 with KB3045171 windows update Cause Windows Security update KB3045171 can cause WorkStation to crash if some fonts have been used within the TGML graphic The example seen was using font "Dotum" Security Update for Windows 7 for x64-based Systems (KB3045171) http://support.microsoft.com/kb/3045171 If this does not resolve your issue see Graphics Editor will not open and causes a font related error. Resolution Microsoft have produced a fix for this problem (KB3065979) see https://support.microsoft.com/en-us/kb/3065979 The PC must be rebooted following this update before the problem is corrected.

Issue 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 SQL Server Cause Each SQL express version has its own database size limit. Refer to SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL. 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 1. If the original I/NET server is still running, try to enable archive function to shrink the database in I/NET. And also follow Archiving and SQL database size keeps growing to set the database cap. 2. If the original I/NET server can't run, or the original database has been deleted, try to use SQL server version with higher size limit or full version SQL server which hasn't physical size limit. Like try to restore the backup from SQL 2005 Express (4GB limit) to SQL 2008 R2 Express (10 GB limit) or Full version of SQL 2005/2008. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Transitioning from Continuum to Struxureware Building Operation and replacing bCX's with Automation Servers. Product Line Andover Continuum, EcoStruxure Building Operation Environment b3865 Struxureware Building Operation Cause Unsure if the older belimo style VAV controllers are compatible with StruxureWare Building Operation. Resolution All of the b3xxx controllers (including both the -V and non -V) will work with the Automation Server under it's MSTP network. Also check out the b3 VAV Quick Start Video on the Community.

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 StruxureWare Building Operation Extended trend logs have an incorrect unit associated with the measured value. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3.x Cause It is possible to create extended trend logs by selecting multiple trend logs and using the right click option to create extended trend logs. The software incorrectly associates all of the created trend logs with the first trend log object's associated unit even if the other trend logs in the selection use different units. Resolution The cause of the problem is resolved in a forthcoming release (1.4.0) however if the system is in the state currently additional steps must be taken. The method to resolve this problem depends on the need to maintain the existing extended trend log data or not. 1. Accept loss of data Delete the extended trend logs that have incorrect units and create each extended trend log individually and avoid multiple selections. 2. Avoid loss of data Export the trend logs in StruxureWare Workstation. Modify the export file and edit the unit value for the Extended trend log The unit will need to be validated with another export that contains an object of the correct unit type. Example of Units % - 0x200001 F - 0x280003 no unit - 0x10001 inH20 - 0x230005 ppm - 0x200002 kW - 0x3210001 Import the modified file and when it detects a naming conflict allow it to rename the Trend log with a "2" notification. Stop the data collection on the original trend logs and once the retention levels of the new trend logs meets your site requirements delete the old trend logs with the incorrect data. Please be aware this issue could impact meter reports from WebReports detailed in Energy Reports not working in 1.3 and earlier

Issue When deploying Automation Server or Enterprise Server from Workstation for Projects under PCS, it will fail. The error shown in the Progress view window is "The live server is not empty." Product Line EcoStruxure Building Operation Environment SmartStruxure Project Configuration Server Workstation for Projects Enterprise Server (ES) Automation Server (AS) Cause A project can only be deployed to a server when the server has an empty database and not has been part of a multi-server system. A server is considered empty when it does not contain any user-created objects, such as programs and graphics. Resolution The server database can be emptied in different ways depending on if it is an Automation Server or an Enterprise Server: Reinstall the Enterprise Server. Upgrade the Automation Server with a new database. For more detail about how to deploy AS or ES, refer to Offline Engineering with Project Configuration Server (PCS).

Issue When trying to log into SBO Workstation receive the following error: Invalid returned data from license server system. (Error code: -12) Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Cause This error has been caused when a Workstation license is present but no Enterprise Server license is present. Resolution An Enterprise Server license must be purchased and added. Please see EcoStruxure Building Operation License types for license options and part numbers.

Issue When there are dual NICs on the computer, you will get host number conflicting error. The IP address causes this conflict is just the local IP address. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET prior to Version 2.44a Win 7 or higher OS Cause When there are two NICs on the computer, I/NET needs to know which NIC is used for communication. I/NET support for dual Network Interface Cards (NIC) can be used for dual NIC configuration for I/NET. But under Win 7 and higher OS, wireless NIC can't be recognized in I/NET, which makes it impossible to choose wireless NIC to be used for I/NET. In the I/NET configuration, it just shows 0.0.0.0. Resolution I/NET will fix this issue in the new release. For I/NET prior to version 2.44a, there are two workarounds for this issue currently: Refer to I/NET support for dual Network Interface Cards (NIC) to choose onboard NIC to be used for I/NET communication. Disable onboard NIC or just disconnect it from the network. Then you will see the option for choose NIC for I/NET communication will be grayed out. That will force I/NET to communicate with wireless NIC. Remember to reboot I/NET I/O server after this to make it take effect.

Issue When using SQL 2008 or SQL 2008 R2, I/NET will crash randomly. Referring to the system Event Log, you can see a SQL error happened just before I/NET crashed, called "There is insufficient system memory in resource pool 'internal' to run this query." Product Line EcoStruxure Building Operation,TAC INET Environment I/NET SmartStruxure Cause According to Microsoft Knowledge Base, this problem occurs for all the following reasons: There is a bug in the code that is used to evaluate how many rowsets are required to perform a sorting operation. Therefore, the code greatly overestimates the numbers of rowsets. The required grant estimate in full-text is 64 pages for each rowset that is required to sort. There is a large request that blocks the system from using the memory that is reserved for the full-text query. Resolution Install the newest SP to the SQL 2008 or SQL 2008 R2 being used. Download Microsoft SQL Server 2008 SP3 Express Edition or Microsoft SQL Server 2008 R2 SP2 Express Edition from the Microsoft website. If this doesn't help, please follow Create Error Log for I/NET to turn on the error log for I/NET and then send the log in to your local country product support group for further troubleshooting.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Supported communications options when running VisiSat software on Windows 7

StruxureWare for Building Operation Web Services Limitations

Using a 0-10 volt CO2 sensor with a Xenta 102-AX

Can 2 MSTP Networks be connected to the same Automation Server?

Adding an object to an already opened Trend chart does not work correctly in Webstation

Time Synchronization of Xenta programmable controllers under Automation Server

Using a 4-20mA CO2 sensor with a Xenta 102-AX

Character limitation within StruxureWare Building Operation

Automation Server independent of Enterprise Server

Graphics Editor will not open and causes a font related error

Missing menu items (commands) from Enterprise / Automation Server

WorkStation crashes when opening some TGML graphic pages following a Windows update

Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached

Transitioning Belimo Bacnet b3865 VAV controllers to an Automation Server

Extended trend logs have incorrect units

Deploy to ES or AS from PCS failed

Unable to remove duplicate id alarms from controllers that are no longer online

Invalid returned data from license server system. (Error code: -12)

Host number conflict on a computer with dual Network Interface Cards (NIC)

I/NET Crashes Randomly with SQL 2008/SQL 2008 R2