Building Automation Knowledge Base

Issue When sharing the domain with the AS under an ES, the domain object appears but includes no Users or User Groups. Environment Domains Users User Groups Permissions Cause Need an efficient way to distribute and administer permissions to all Automation Servers. Resolution When you share a domain in the ES with an Automation Server, the Users and User Group properties apply to the AS However, the Users and User groups will not appear as objects under the domain in the Automation server as they do in the ES. Only the domain object will appears under the AS.  Nevertheless the permissions will be extended to the AS.

Issue Unable to use "Object" as a keyword in SmartStruxure Script program.  Environment SmartStruxure Script Object Keywords Cause The Object keyword is not supported in SmartStruxure script language because the binding structure cannot accommodate this function. Resolution The Object keyword is not available nor is any compatible function. 

Issue I/NET Host Tool with StruxureWare Building Operation Environment I/NET Site StruxureWare Building Operation Site Cause I/NET Host Tool support with StruxureWare Building Operation Resolution With the current release of Building Operation, I/NET Host Tool is not supported. Licensing of the Host Tool comes from a TAC Vista server and the graphics converter is not in the I/NET Host Tool. 

Issue Explanation and detail required for Client Access License (CAL). Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET Environment Windows  SQL Server Cause Information on Client Access License (CAL). Resolution Server licensing and Client Access Licenses (CALs) for the MS Server or MS SQL can become complex. It may be worthwhile to research further through Microsoft resources. SQL Server 2008 is available under three licensing models: Server plus device client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each client device. Server plus user client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each user. Processor license. Requires a single license for each CPU in the operating system environment running SQL Server. This license includes unlimited client device access. SQL Standard will normally come with 5 CALs. If more than 5 connections exist, then ore SQL CALs need to be purchased. See Microsoft Volume Licensing for more information. Note: MS Server CALs are separate and are also required. EcoStruxure Building Operation does not check CAL Client Access Licensing. EcoStruxure Building Operation Reports Server can be run using Microsoft SQL Express.  

Issue The IO Module does not report input signals and all physical outputs are turned off. The IO module status LED blinks at a rate of one blink per second. Product Line EcoStruxure Building Operation Environment I/O Module Cause The IO module has been placed into Low Power Mode. Resolution  I/O Module Low Power Mode In order to save energy, an I/O module can be placed in low power. When an I/O module is in low power, the following conditions apply: The I/O module does not report input signals and all physical outputs are turned off. The Module status reports low power. The I/O module's LED pattern indicates low power (the slowest green LED blink pattern, approximately once every 3 seconds). When you set an I/O module to low power, the software turns off all outputs. When you want to recover an I/O module from low power, there are several points to consider: Make sure all I/O module Output values are set to a safe level before a return to normal power conditions. This prevents "power surge" conditions. After normal power resumes, the Output values set are reached immediately after any timing delay occurs. Setting and Recovering an I/O Module from Low Power Place an I/O module in low power mode in order to save energy and then recover that module later.   To set and recover an I/O module from low power In WorkStation, in the System Tree pane, expand the IO Bus. Click the I/O module that you want to put in Low power mode. Click File and then Properties. Under Configuration Settings, in the Low power box, select True. Click OK to change the value and close the Properties tab. If the physical I/O module, shown in the System Hardware folder, matches the logical I/O module defined in the I/O Bus, the I/O module goes into Low power. After the physical module enters low power, the Module status attribute in the Status Information area displays Low power.  To set and recover an I/O module from low power In the System Tree pane, expand the IO Bus to recover from low power mode. Click the I/O module to recover. Click File and then Properties. Under Configuration Settings, in the Low power box, select False. Click OK to change the value and close the Properties pane. If the physical I/O module, shown in the System Hardware folder, matches the logical I/O module defined in the I/O Bus folder, the I/O module exits from low power. After the module resumes operation from low power, the Module status returns to the status it had before it went into Low power. NOTE: If unable to change the Low Power property: Export the contents of the I/O module Deleted it from the AS Re-add it to the AS Import the XML back into the module

Issue What properties of a signal is exposed in SmartStruxure via TAC Vista SmartStruxure Interface? Environment TAC Vista SmartStruxure Interface SmartStruxure Cause What properties of a signal from TAC Vista can be seen in SmartStruxure? Resolution Value (read/write) Unit (read only) Description (read only)

Issue How does TAC Vista SmartStruxure Interface affect the field bus traffic under TAC Vista? Environment TAC Vista SmartStruxure interface SmartStruxure TAC Vista Cause Does the TAC Vista SmartStruxure Interface ask for all values that are hosted and how often? Resolution TAC Vista SmartStruxure Interface creates subscriptions to the TAC Vista server and only asks for values that are being used. When you set up the EcoStruxure web service interface, you also set up how often the values get polled in the "value poll interval."

Issue On two occasions all of the scheduled periods disappear from the schedule. Environment AS Schedules Exception Schedules Cause Weekly scheduled times were entered as exception schedules. Resolution Recurring periodic scheduled event which occur week after week should be programmed as weekly schedules.  Exception schedules are used to override weekly scheduled events.

Issue After changing the engineering and electric scale with the spreadsheet the implicit logs stopped working Environment StruxureWare version 1.3 Cause It is not possible to recreate this problem in version 1.3 SP1. Resolution Upgrade to version 1.3 SP1 will solve the problem.

Issue Unable to Bind to an I/NET Point Command Error Alarm after Binding to an I/NET Value Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Workstation Cause As of version 1.4, I/NET input points can not be bound to SmartStruxure outputs. A Command Error Alarm will occur when attempting to bind to an I/NET controller that does not have the current bin file Resolution If needed create an additional I/NET output point and use that to control the I/Net input point via a Calculation Point Extension. In I/NET, connect to the controller. Select Edit > Controller > Configuration If the Build Date is older than April of 2012, you will need to upgrade the controller. In StruxureWare, when setting up the bind to the I/NET point, be sure to edit the I/NET point objects bindings, if that is what is being controlled. Bind the desired StruxureWare value to Control Value (DO) or Value (AO) property of the point for I/NET.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Environment Remote Control Software. Cause Not all features are seen when a BMS platform is viewed using remote control software. One example is: When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. Resolution When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. The above example is one scenario. There are a number of other remote control software applications where similar instances may occur. If such an issue occurs, check that the BMS software is functioning correctly by both being viewed and ran in the same environment. Because of the number of different remote control software options that are available, anomalies will prevail.

Issue When a download is performed on a BACnet controller does SmartStruxure overwrite the entire contents of the controller? Environment SmartStruxure 1.4 Download Cause Wish to replace the entire contents of a BACnet controller Resolution When downloading a BACnet controller from an Enterprise Server or an Automation Server the following takes place... StruxureWare downloads the configuration properties of the device proxy to the BACnet device. StruxureWare updates the object list of the BACnet device with the object list of the device proxy. StruxureWare writes the properties of the object proxies to the objects in the BACnet device. Following the download the contents of the BACnet device match the contents of the device proxy.  If there are objects in an external BACnet device that do not have corresponding object proxies in StruxureWare, the Download operation deletes those objects in the device.  The Download command does not delete vendor proprietary BACnet objects or properties as described by the ASHREA standard.

Issue After an upgrades to 1.4, units for temperature inputs on Central IO are not configurable. Affected programs no longer work correctly. When there is no client activity to convert to the locale of the client (there is not with the Script engine), the input is assumed to have the number that corresponds to degrees Centigrade. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.4 Central IO Inputs PE Script Cause Units must be set  in the variables window of the affected script program. Resolution The following program would work fine in 1.3 if the temperature that is bound to the SpaceT input was configured to have units of Deg. F. When the user of this program upgrades to 1.4, this program will no longer work correctly. The input is assumed to have the number that corresponds to Deg. C. You can see it in the variable value listing block: 22.4°C is compared to the setpoint of 70°F and it does not work right. The units MUST be set within the Script program as below: Now it will work.

Issue Cannot import lon Lon Device template. Field stays red after browsing in the correct XIF file. Import button does still grayed out after browsing the correct XIF file. Environment StruxureWare Building Operation 1.3 and earlier Cause There is a problem with some regional settings. We have seen this using Turkish regional settings so far but the are probably other languages that will also cause the issue. Resolution Stop Workstation Open control panel Go to Regional and Language Options Change standards and formats to English. Click ok Start workstation again and import the file. Add your devices Close workstation Open Regional and Language settings and change back to your language Open workstation

Issue Eventlist in StruxureWare workstation is filled very rapidly with the following messages: - * Modbus group re-factorized - * Modbus group factorized - * Modbus illegal data address Environment StruxureWare Building Operation 1.4.818 Cause The problem is that it is illegal registers in the Modbus register group or groups. Modbus is trying to resolve this by refactoring the factoring and refactoring but is not successful. Resolution The possible solutions are: Identify the illegal Modbus point in SmartStruxure and remove from the subscription. Solution Split the group in to two so that the illegal Modbus point is left out of the groups. Disable group poll and Force individual point polling by setting incorrect function code for the group.   If it is difficult to identify the illegal Modbus point then you can use solution 3 to do this.

Issue b3 controllers in StruxureWare Building Operation do not seem to support Counter inputs. Environment Counter Inputs b3 Cause SmartStruxure does support the creation of Counter inputs within b3 controllers. Resolution Counter inputs are Analog Inputs.  When the Object Creation wizard is used to create an Analog input the user is prompted to select the electric type.  At this point select Counter.

Issue Federal Information Processing Standard (FIPS) Compliance Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Cause Is the Automation Server or Enterprise Server FIPS compliant? Resolution There is not Federal Information Processing Standard (FIPS) Compliance with the current release of Building Operation.

Issue Is it supported to access an Automation Server 1.4.0 with the Workstation 1.4.1? Are there any problems and what features are supported when accessing a 1.4.0 Automation Server with WorkStation 1.4.1? Environment Enterprise Server / Workstation 1.4.1 Automation Servers 1.4.0, 1.3 with SP1 and SP2 Cause Understanding of the new Runtime Compatibility mode available in 1.4.1 available during system upgrades Resolution Building Operation supports runtime compatibility between servers running two versions on a single system, during an upgrade process. Version 1.4.1 servers are runtime compatible with version 1.3 SP1 and 1.3 SP2 servers. The system is able to exchange runtime information between 1.4.1 servers and 1.3 SP1 or 1.3 SP2 servers. However, configuration changes cannot be made from an upgraded WorkStation via an upgraded Enterprise Server to a non upgraded Automation Server, such as creating, configuring, and deleting objects. There is also no runtime compatibility for WebStation. Runtime compatibility means you can delay the upgrade of some Automation Servers running version 1.3 SP1 or 1.3 SP2 while upgrading the Enterprise Server, WorkStation, Reports Server, and some Automation Servers to version 1.4.1. You cannot make any configuration changes on an Automation Server running the 1.3 SP1 or 1.3 SP2 version with WorkStation and Enterprise Server running the 1.4.1 version. However, you can make the changes using a parallel WorkStation running a 1.3 SP1 or 1.3 SP2 version that is connected to the Automation Server running the 1.3 SP1 or 1.3 SP2 version. Full compatibility is supported on Automation Servers running the 1.4.0 version   Additional detail is available on the Online Help http://help.sbo.schneider-electric.com/topics/show.castle?id=9807&locale=en-US&productversion=1.4&a=1 Supported Features: Navigate You can navigate in the system tree of an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, object and property types removed in the 1.4.1 version compared to the 1.3 SP1 or 1.3 SP2 version are not be displayed in the system tree. Search You can perform an object or property search on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, object and property types removed in the 1.4.1 version compared to the 1.3 SP1 or 1.3 SP2 version are not be displayed in the search list. View Events You can view detailed information and perform commands on events on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. The 1.4.1 Enterprise Server will also store events from an Automation Server running 1.3 SP1 or 1.3 SP2 version. View Trend Logs and Trend Charts You can view trend log lists and trend charts on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Extended trend log lists in the server running 1.4.1 version are functional and be able to retrieve values from a server running the 1.3 SP1 or 1.3 SP2 version. View Graphics You can navigate to and view a graphic on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server at 1.4.1 version. Graphic variable values can be changed with Graphics Editor, but configuration data cannot be changed. View Alarms You can view detailed alarm information from an Automation Server running the 1.3 SP1 and 1.3 SP2 version, with WorkStation and Enterprise Server at 1.4.1 version. Also actions on alarms can be performed, such as assigning or disabling an alarm and enabling a Change-state logging. View Dynamic Values You can navigate to and view dynamic values in the Watch pane from an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, because there is no way to navigate to and view objects or properties that have been removed in the 1.4.1 version, such dynamic values cannot be viewed. Transfer Values You can transfer values from an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with an Enterprise Server or Automation Server running the 1.4.1 version and the other way around. Change and Force Variables You can change and force variables using properties on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Lead and Shadow relationships Lead and Shadow relationships work for all objects with the runtime compatibility support. Backup You can make a backup of an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Log on to the Enterprise Server and then make a backup of the Automation Server running the 1.3 SP1 or 1.3 SP2 version. You can also log on directly to the Automation Server running the 1.3 SP1 or 1.3 SP2 version with WorkStation running the same 1.3 SP1 or 1.3 SP2 version, and then make a backup of the Automation Server.

Issue The Triac (V) outputs on the TAC Xenta 120-FC device goes ON, but never OFF. In this case, it can open the valve, but the device could not close the valve. Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause If the device is powered with 24 VDC, the Triac will not work properly. According to the datasheet, the TAC Xenta 121-device should always be powered by AC, not DC. Triac is an acronym for Triode for Alternating Current, and could only be working with AC power supply. Resolution Correct the power supply to the device to use AC, not DC.

Issue A Plain English program is becoming disabled.  The controller error log logs the following error. 0x01402 (Reached end of the list). Environment Continuum Plain English Error b3 i2 Cause 0x00001402 (Reached end of the list) is a Plain English error.  This error most often occurs when a program is calling a Plain English Function that contains no byte code.. Resolution Edit each InfinityFunction in the controller to determine which function is empty (contains no programming).