Building Automation Knowledge Base

Issue ClimateMaster controllers are an OEM version(s) of the I/A MNL LON controllers and can only be added as third party devices in SmartStruxure.   Environment ClimateMaster controllers SmartStruxure Cause ClimateMaster is a channel locked product and will not permit  WorkPlaceTech or WorkPlace Tech Editor to have access to the application via upload or download. Resolution ClimateMaster controllers can only be added as third party devices. For help on adding third party devices consult the StruxureWare Building Operation Web Help. There are three web help topics on adding third party devices: Enterprise Server Automation Server Third-Party Licenses

Issue LonWorks on an AS and replacing the template without deleting devices Environment StruxureWare Building Operation site with LonWorks interface Cause Site would like to replace the XIF template without deleting devices Resolution Unfortunately there is no way to replace the template without removing all devices. Even if the site is fully commissioned and devices are installed, the site must be re-commission and bind everything again. The template cannot be replaced without deleting the devices installed.

Issue Menu options described in Web Reports Reference Guide are not available in the Web Reports Web Interface Environment Web Reports 1.2 Cause User is not part of the Reports Administrators Group Resolution Log into the ES In the system folder, locate the user logged into Web Reports (System>Domains>domain>Users>username) Select that Users "Group Membership" tab Add the user to the "Reports Administrators" Group

Issue What SNVT types are supported in the StruxureWare Building Operation ES and AS? Environment SNVT types ES AS Supported Cause Confirmation was required on what SNVT's are supported. Resolution The StruxureWare Building Operation ES and AS support the current published Echelon master SNVT list, to see the full list, please click HERE.

Issue WorkStation Portal Login Environment SBO Site Cause Will StruxureWare Building Operation include a feature in similar to TAC Vista's Portal Login. In other words, a way to make automated log in from another system (3rd party) and use this to create more and more cloud-like service currently used on TAC Vista Webstations Resolution Currently this is not a feature of the current release of StruxureWare Building Operation. 

Issue While email notifications for alarm conditions are being delivered promptly, Return to Normal notifications are not delivered until the notification is acknowledged at that the workstation. Environment AS ES Email Notification Cause Email Notification is not configured correctly. Resolution Select the Reset checkbox to have an email delivered when the alarm condition clears. The Normal box should read "Acknowledged Normal" since this delivers a notification that the Off Alarm notification has been acknowledged.

Issue What is included when the PIR option is ordered? Environment SE7300 series controllers Cause The SE7300 series controllers can be ordered both with and without the PIR option Resolution If the PIR sensor functionality is ordered as included from factory, code 55 (example: SE7600A5545E) should be used. If PIR functionality is not required, code 50 (example: SE7600A5045E) should be used. PIR functionality can be retrofit at any time. For details and part numbers, please see related documentation.

Issue StruxureWare Network 8000 conversion program is changing some "Logic" blocks to a block type called "Invert".   Could this be causing missing pointer issues? Environment SBO 1.2 and later Network 8000 conversion program with any Network 8000 GCM file. Cause This is as designed; see Resolution for explanation.   Resolution A Logic object is 'Migrated" as an Invert object if only used as a single invert gate. The other objects that reference that object as a pointer are changed also to reflect the block name 'Invert'. This is documented in the Technical Reference Guide in section 89.7.

Issue Upgrading the Automation Server firmware from version 1.0 to 1.2 or 1.3 fails Upgrading the Automation Server firmware from version 1.1 to 1.3 fails AS is going into failsafe when attempting to upgrade it to version 1.2 Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and 1.3 AS-L AS-B Cause It is not possible to upgrade an AS more than one version at a time. Resolution Upgrading from 1.0 to 1.3 should be done as follows:: Install Device Administrator version 1.1 (if not already done) and upgrade the AS to firmware version 1.1 After the upgrade has finished and the AS is ready, upgrade to version 1.2 from Device Administrator version 1.2 When the AS is ready again, upgrade to version 1.3 from Device Administrator version 1.3  

Issue When importing shortcuts the following warning/error occur WARNING: The property, Target, xxxxxxxx, which has been ignored. Binding Limitations across multi-server configurations Environment SmartStruxure 1.2 / 1.3 Cause Building Operation does not import bindings in a multi-server scenario. If bindings are included in an exported solution, Building Operation displays a warning that the references were not created during an import. Therefore, you must manually recreate referenced bindings: From the Enterprise Server to a value on an Automation Server From an Automation Server to a value on the Enterprise Server From an Automation Server to a value on another Automation Server As a shortcut is basically a binding between two objects, then this holds true in this instance. Resolution Although bindings can be created (hence shortcuts created) across multi-server environments once you export these objects and then attempt to import these at later time or import across a different server, these bindings will be removed. The import process will provide a message "WARNING: The property, Target, , which has been ignored"; these objects are listed in the warning box.  A "Copy to clipboard" option is available so that these can be copied to Notepad (or similar) and then manually re-entered. Refer to the following help topic (you will need to login to the Online help to view this information). http://help.sbo.schneider-electric.com/topics/show.castle?id=5528&locale=en-US&productversion=1.3&a=1  

Issue AS communicate to ES using Telephone line? Environment SmartStruxure site  Cause Allowing remote access where broadband/ethernet is not available. Plus redundant access when the LAN goes down. Resolution ES and AS communication with the current release requires Ethernet communication. The use of a modem or telephone lines for communication between AS and ES has not been developed. This however is on the roadmap and will be included in a future release. The AS does have USB ports facing down for future connection to external devices such as telephone modems, printers, memory expansion, and expansion modules.  

Issue EcoStruxure Building Operation Demo Database Package Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site Cause EcoStruxure Building Operation Demo Database Package and going between releases. Resolution All current and previous sales packages/demo databases can be found on the Exchange for download. Note: The Demo Database package is a sales and marketing tool for your use "as is." It is not supported through Product Support Services (PSS). If you have product specific technical issues such as installing the software applications (e.g. License Administrator, Enterprise Server) PSS may be able to help. However, PSS does not support the Demo Database contents or features. The Demo Database can be re-installed to return to its original state.

Issue EcoStruxure Building Operation different types of licenses and all features Version 1.9 and older: Difference between Workstation standard and Workstation professional Product Line EcoStruxure Building Operation Environment All versions Cause Due to different features of each license, customer may get confused which license to order. Resolution See the version of the latest EcoStruxure Building Operation Part Number Summary document on the Exchange for all license part numbers.   Versions 2.0 and Newer Note: The licensing part numbers and structure has vastly changed starting in version 2.0 and newer.  See the search query below on the Exchange for more detail regarding the Scalable Pricing Policy that started in version 2.0. EcoStruxure Building Operation Scalable Pricing Information   Versions 1.9 and Older Note: There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing)  

Issue Receive "Error 1606. Could not access network location\." when installing I/NET Seven Software with StruxureWare Building Operation Environment I/NET Seven SmartStruxure Solution 1.3 Cause When uninstalling / Installing I/NET with Building Operation software already installed the Enterprise Server and InetIoSrv service must be stopped.  In some situations when not installing the for site it may be best to set both the Enterprise Server and InetIoSrv services to manual avoiding this situation. Resolution To resolve this problem.  Stop the Building Operation Enterprise Server service, either from the Software Administrator application or from the Windows Services. It is also recommended to stop or remove the InetIoSrv service prior to any update of the I/NET Seven software.

Issue Is the use of Windows Server 2008 R2 64 bit Service Pack 1 supported when using release 1.3? Environment Release 1.3 Documentation Release notes Operating system Cause The release note for StruxureWare Building Operation 1.3 states that only Windows 2008 R2 64 bit is supported, but it also says that .Net 4.0 is required. When downloading .Net 4.0 from the following site,  http://www.microsoft.com/en-us/download/details.aspx?id=3556 you are advised in system requirements that Windows Server 2008 R2 64 bit SP1 is required. Is Windows Server 2008 R2 64 bit SP1 supported? Resolution When our software quality assurance teams tested and qualified 1.3.0  they all used SP1, so yes SP1 is officially supported.  

Issue Is it possible to use dynamic SNVTs in StruxureWare Building Operation? Environment StruxureWare Building Operation version 1.3. Cause A XIF file including Dynamic SNVTS is often created by a LNS plugin and depending on the settings in the LNS plugin the XIF file changes. Even when the Xif file changes the program ID in the XIF does not. And in SmartStruxure it is not possible to import two XIF files with the same program ID. Resolution Dynamic SNVT works but only for one device, if different devices have different settings in the LNS plugin only one can be imported.

Issue Sending a SNVT value from one local node to another local node in another Automation Server. Environment Automation Server Workstation Lon Interface Local Node Cause You can not bind directly between two lon devices under different AS. You cannot bind from one local node to another local node either.   Resolution Transfering SNVTs from one Automation Server to another Bind from SNVT_out on the lon controller to a SNVT_in in the local node on AS1. (Normal SNVT communication, send on change and period) Bind from local node SNVT_in on AS1 to a SmartStruxure value in AS1. Bind SmartStruxure value in AS1 to a SmartStruxure value in AS2. Bind from the SmartStruxure value in AS2 to a SNVT_out in the local node of AS2. Bind from SNVT_out in the local node of AS2 to the SNVT_in of a controller out on the FT-10 network. (Normal SNVT communication, send on change and period) NOTE:  When binding with a network variable you need to expand the SNVT and bind to the property contained within the SNVT. In version prior to 1.4 bindings could be made from one local node variable to another local node variable in another AS but this was an improper engineering method that is now illegal in SmartStruxure.

Issue Web Security. Environment http https Web Clients Cause http does not provide the same level of security as https. Resolution At SmartStruxure Building Operation 1.4, this is no way to force ES web clients to use https. The feature is supported from SmartStruxure 1.6.0 RC and up

Issue Access which allows a value to be changed, also allows other changes to be made. Environment Users User accounts Cause A user account is created to have read only access, but this user must also have access to view Graphics, and on these graphics, be able to change values. How can this be achieved without allowing the user access to delete or edit these objects?   Resolution At StruxureWare Building Operation release 1.3 there are no available options that will achieve this configuration, the most appropriate configuration is to create a Workspace for the user, in which they will see only the Graphics, the user would have Read/Write access to the values they are allowed to change.

Issue If creating a shortcut from an object the name of the shortcut does mirror the object. I can change the object name but the shortcuts does not reflect the change and the old name remains. Environment StruxureWare version 1.3 Cause The shortcut object doesn't need to have the same name as the original object. When the shortcut is created it gets the same name default but then you can change the names on booth the shortcut or the original object to anything you like. But the shortcut will still show the value from the original object. This is the same way as it working in Vista also Resolution That is the way it is designed to work.