Building Automation Knowledge Base

Issue In for example TAC Vista it was possible to specify the subnet/node address when adding a Lon device, is it possible to do this in any way in StruxureWare Building Operation(SBO)? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.6.1 and earlier Cause In version 1.6.1, this is not possible. Resolution The plan is to add this functionality to SBO version 1.7.

Issue When using the SmartStruxure Interface, is it necessary to configure any DCOM or firewall settings to run TAC Vista and SmartStruxure on different computers? What protocol is used for communication between the SmartStruxure interface for TAC Vista and the ES? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista server TAC Vista SmartStruxure Interface SmartStruxure Enterprise Server (ES) Cause Communication issues between interface and SBO Resolution Only HTTP/HTTPS are used. You can configure the interface to use only one of the protocols. You can also configure what ports to use.

Issue Tips to speed up saved searches in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Workstation Cause Searches take a large set of objects and check them against text matching and then against conditions. The more you can eliminate before checking text or conditions the better. Resolution Whenever possible use the following methods to speed up searches Use the 'In folder' field to avoid searching too large a section of the system Do not include properties or sub-servers when they are not needed Specify the smallest subset of type you are able to. For example, if you only want Extended Trend Logs, do not use the Base Trend Log object.

Issue When installing SE7000/SE8000 Room Controllers to connect them to a BACnet MS/TP network, multiple issues can arise: Leaving the Room Controller's COM address at 254 (default value out of the box) will make the room controller undiscoverable by the front end. Choosing a Com address value between 128 to 253 will cause the front end system to convert the com address to 127, causing duplicates when working with multiple Room Controllers. Room controllers with COM address set to 0 will prevent the front end from discovering any devices Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Other Environment SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350, SE8600 Viconics branding VT8000 Series SE7000 Series Controllers, VT7000 Series Controllers, 7600, 7300, 7200 Cause Master devices, those who participate in the token-passing protocol, must be addressed from 1 to 127. Addresses from 128 to 253 are reserved for slaves who do not participate in the token passing; however, they can occupy lower addresses as well. Resolution COM address must be changed to a value in the range of 1-127.

Issue Unable to control an I/NET DO object from a TGML graphic in HTML5, works in Workstation and Java based webstation Environment WebStation Cause The data type may not be correct.  The value should be written to PvControl as either a 0 or a 1.  If this is set as a string data type, Workstation can correct for this error, but HTML5 is less forgiving. Resolution locate the line of javascript where you write the value to the bind. this is typically a setValue(bind, value) function. bind = the full bind name of the pvControl binding. value = the value that is intended to be written to the pvControl bind. One line before the setValue command, enter the line " parseFloat(value)"  - This will convert that value to float. If the value is a 0 or a 1, the setValue command will now correctly set the I/NET value.

Issue Is it supported to do an export from for example StruxureWare Building Operation version1.4 and import into version 1.6? Environment StruxureWare Building Operation Cause It is always allowed to export from an earlier version and import to a later version but not the opposite way. With one exception in StruxureWare Building Operation version 1.7 exports from version 1.0, 1.1 and 1.2 will not be supported. The workaround if having a export file this old is to import it in version 1.6 and then export from there to 1.7. Resolution It is allowed to export from an earlier version and import to a later version but not the opposite way

Issue When trying to upgrade the database, the following error occurs: ESDatabaseUpgradePrepare returned: -1 Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause There is an issue with System default workspace_copy in StruxureWare Building Operation v1.4 that can cause an upgrade to fail. When the ES Installer fails  ("ESDatabaseUpgradePrepare returned: -1"), you have to localize the "dump.log" file on disk: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.5\Enterprise Server\db_backup\dump\dump.log and check if this file contains an error message in this style: WARNING:　Error: Type_Error (0xd001a), module Impex(57), moduleCode 0, dispString "~/System/Domains/Builders/Workspaces/System default workspace_copy", techString "Cannot find declared instance in parents type." and then this: ERROR: Exception encountered while reading db objects or writing objects to dump file: RecoverableException: d:\dev\rb-dev-dbexport142-system\source\packages\commons\components\C3Po\utilities\impex\source\ImpexContext.cpp(248) Error: Type_Error (0xd001a), module Impex(57), moduleCode 0, dispString "~/System/Domains/Builders/Workspaces/System default workspace_copy", techString "Object is not populated with a declared instance template!" NOTE: In this example we use the domain name "Builders" and workspace name "System default workspace_copy" in your case this names can be different since it is a user that creates and names this instance. Resolution As you can see in the Error above ""~/System/Domains/Builders/Workspaces/System default workspace_copy"," the issue lies with System default workspace_copy that is related to the domain "Builders".   The copy paste issue has corrupted the workspace and only way is to remove the whole domain "Builders" and then upgrade. In your case the domain name and the workspace name can be something different since this is a name you choose when creating a domain and/or a workspace. For now we do not have a fix for this defect but the above workaround is valid.

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 How do I put a different application in an existing MNL controller under an AS? Environment AS with MNL controllers Cause An incorrect application has been installed in a device. Resolution First, the correct application must exist in the WorkPlace Tech editor list.   Expand the System Tree to expose the MNL device to be changed and the Application file under it.  Right click on Application and select delete.  Now right click on the MNL controller select MNL and Assign application and assign the correct application from the list. Once assigned right click on the controller select MNL and select Download application.

Issue Even though the correct settings are defined in Device Administrator, the Automation Server will appear red indicating that it is not possible to connect to it. Product Line EcoStruxure Building Operation Environment AS Device Administrator Cause Some special characters are not supported in some positions before version 1.6.0. For example, the password admi$n would work in Workstation, but not in Device Administrator. The password admin$ would however work. Furthermore, after 3 login attempts the account will be blocked. Resolution Change the admin password to something simple like "admin" or "password" Reboot the AS, or wait 30 minutes Connect with Device Administrator

Issue When editing a Script program, it seems that the Script editor is opening and the Script editor icon is shown in the task bar, but the editor is not visible Product Line EcoStruxure Building Operation Environment Script editor Cause At some point, the Script editor has been opened on a secondary monitor connected to the PC. The last location of the editor is saved in a setting file, and when opening the editor at a later stage not having the secondary monitor, the editor will open outside the visible area. Resolution With a text editor, edit the user.settings file located in: %appdata%\Schneider Electric StruxureWare\Script Editor\1.6.1.5000 (In this case it's for version 1.6.1.5000) In the top, locate the entry "Left" and change what ever value is written to 0 In the top, locate the entry "Top" and change what ever value is written to 0 Save the file

Issue In the conversion log when upgrading database, the following warning is logged: Invalid value for ProgramID in the object, "~/LonWorks Local FT-10 Interface/Your Network/Controller Name/IO/IO Module Name". The default value has been applied. Product Line EcoStruxure Building Operation Environment AS Device administrator Cause TAC Xenta IO modules of the model 411/421 does not have an application ID populated in the properties. All other IO modules do. The upgrade sees this as missing information. Resolution You can ignore this if the module is a TAC Xenta IO 411/412.

Issue When editing a TGML error A generic error occurred in GDI+ appears Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista StruxureWare Building Operation TGML Graphic editor Cause This issue occurs after you install security update 3045171. You experience a crash when you use Windows GDI+ to create text outline-based path objects on a computer that is running Windows 7 Service Pack 1 (SP1) or an earlier version of Windows. Resolution Download the patch below from Microsoft https://support.microsoft.com/en-us/kb/3065979 It has been noted that this patch do not solves all the issues, if you still have issues with other applications uninstall the security update KB3045171.

Issue Logging on to IPM from the web and the default password is not recognized. An error comes up saying Invalid user. Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Building Operation, I/Net Cause The default password can be used on the I/Net side but it is not being recognized when logging in from the StruxureWare IPM. Resolution To resolve this issue, the following step needs to be followed: From the original installation folder, find and unzip the Sboscripts.zip from ‘\InetWeb\UpdateScript' folder. Follow the SQL patch delivery process of I/Net. Run 'Sboscripts.exe' on a DOS prompt. Enter the SQL Server Instance name and login credentials for the script to run If the SQL Serve Instance name is not known, open up DBCreate and it would be displayed on the editor, more than likely it would be 'SQLEXPRESS" or blank per the INetDB Configuration. Once the script is complete, launch StruxureWare and enter the default passwords again and it should allow you to successfully log into the program.

Issue Is there a way to restrict user access to WebStation but still allow access to the system through Workstation? Environment Workstation WebStation StruxureWare Building Operation v1.6.1 Cause Requirement to limit access to Enterprise or Automation Servers through Workstation only and to stop users from being able to access the system through WebStation. Resolution User or Group security does not allow for this type of restriction. One method may be to use a Firewall in front of the AS to restrict what/who is able to connect.

Issue After upgrading, the AS is offline in LonMaker. An attempt to commission the AS results in an error shown: "The new program interface does not match the previously defined program interface". Product Line EcoStruxure Building Operation Environment Automation Server Externally Managed LonWorks Network LonMaker Cause There has previously been issues with the structure of the XIF created by the AS. This is corrected in newer versions, but as a result the XIF previously loaded in LonMaker will be different from the actual content in the AS. Resolution Replace the AS in LonMaker uploading the XIF file again from the AS.

Issue Windows installer fails to install an application Environment Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows XP Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 8 Windows 8.1 Windows Server 2012 editions Windows Server 2012 R2 Cause Errors with the Windows Operating system are preventing the installation from completing. Resolution Run the file at the link below on the affected PC:   https://support.microsoft.com/en-us/mats/program_install_and_uninstall

Issue Correct Boot Up sequence for I/NET Enterprise Server Level Integration to StruxureWare. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET to StruxureWare Enterprise Server Level Integration Cause Sites which are recovering from a power failure are are using Remote Client with I/O may have certain failures within the system. A site where I/NET works on the local PC but devices seem offline from the Enterprise server may have had the Enterprise Server Start before the I/Net I/O Server A site where I/NET points can be controlled from the ES, but messages are not received by either the ES or I/NET AMT may have had the SQL server start after the ES or I/NET IO Server started. Resolution Restart the SQL Server or Server PC Restart the I/NET I/O Server and ensure it is running as a service Restart the Enterprise Server In order to add the I/NET I/O Server as a dependency for the Enterprise Server use the command prompt line below. Be sure to change the 1.X to reflect the current version of SBO installed. Open the Command prompt Enter the command: sc config "Building Operation 1.X Enterprise Server" depend= inet7iosrv

Issue Moving a Converted I/NET graphic for the ES level integration of I/NET to the AS level of Integration to I/NET Environment StruxureWare TGML I/NET Cause As sites expand, controllers that are currently integrated to StruxureWare using the Enterprise server may be connected to the USB interface to the Automation Server.  It is possible for these relocated controllers to continue to use the same graphics. Resolution Recreate the exact folder location of the graphic on the AS. For Example, if the graphic is currently on the ES\INET Interface\INET Graphics folder, the user should create an INET Interface\INET Graphics Folder on the AS Copy the Graphic on the ES Paste the Graphic on the AS Clean up any bindings.  Any I/NET objects that were re-named after the initial conversion may need to be manually re-bound. Links between graphics may also need to be re-bound.

Issue Looking for more information on the Schneider Electric Advanced Display offering from the Smart X family of controllers. Product Line EcoStruxure Building Operation Environment SmartStruxure SmartX Controller Advanced Display Technician Tool Mobile App Cause Unsure where to locate more detail about the Advanced Display and do not know the part numbers to order the products. Resolution The Advanced Display is a convenient option for users to access, monitor, and service their SmartStruxure system. For additional information please reference the SmartX Controller - Advanced Display documents found on the The Exchange. Applications The Advanced Display comes with the SmartXKiosk application already installed on it. This app, when launched, limits which other applications may be accessed on the tablet. The only way to exit the Kiosk mode is to enter a six character PIN. Any of the available Schneider Electric apps found on the Google Play Store can be added to the SmartXKisok. Technician Tool mobile app AdaptiApps custom user apps WebStation The Technician Tool provides a simplified user interface for operation and maintenance of the SmartStruxure solution.   Communications and Wiring Options Communication Options Available Availability Wi-Fi to the BMS network (requires straight USB cable) All SmartStruxure versions USB direct communication to the Automation Server (requires Y-shaped USB cable) Versions 1.7 and newer Wi-Fi or USB direct communication to the Automation Server Premium (requires straight USB cable) Versions 1.7 and newer   The Advanced Display communicates with the SmartStruxure servers through an access point or starting in version 1.7 directly to the Automation Server via the USB port with the application named SmartX-Ad Link. If using an Automation server, the Y-shaped cable must be used to connect to a locally sourced power supply as well as to the Automation Server. The power required is 5 VDC with a minimum of 500 mA up to 1.3 A. The USB port on the Automation Server Premium (AS-P) has the ability to power the tablet directly thus only requiring a straight USB cable.    Ordering Part number Description SXWADTAB410001 Advanced Display 7 - inch - - No longer available! SXWADBUND10002 Advanced Display 10 - inch Bundle Includes Advanced Display tablet unit, mounting frame, bezel, and Micro USB 2.0 data cable 1 m (3 ft) SXWADUSBA10001 USB cable, Straight 1.5 m (5 ft) for connection to AS-P or AS-B SXWADUSBA10002 USB cable, Straight 3.0 m (10 ft) for connection to AS-P or AS-B SXWADUSBB10001 USB cable, Y-shaped 1.5 m (5 ft) for connection to Automation Server SXWADUSBB10002 USB cable, Y-shaped 3.0 m (10 ft) for connection to Automation Server   Note: The Advanced Display 10 - inch Bundle does not include a power adapter.  For configurations where the external power adapter is required the appropriate power adapter must be ordered separately for the country in which it will be installed.

Issue Multiple issues caused by changing the link after discovering devices. Duplicate entries of MCU devices under a sub LAN interface Deleting duplicate MCUs causes MCU devices to be removed from I/NET Environment Automation Server integrated to I/NET Cause Changing the link address of the I/NET Interface should not be done after devices are discovered. If you must change the link address, do so before you have added devices to the I/NET interface. Resolution Option 1 -  Remove all controllers from the I/NET interface. Change the link to the correct setting Re-discover the devices Option 2 - Determine whether the AS or the I/NET controller has the correct information. (This will require I/NET software) If the AS is more correct, perform a download to the controller if the I/NET controller is more correct, perform an upload to the AS