Issue How long does PSS support a product after it is released? Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment All Schneider Electric Buildings Business software platforms Cause After a few years, the majority of issues with a release product are documented in the Knowledge Base.  At this point, if the customer is having issues requiring Product Support, we ask that they upgrade to the current version. Resolution Please read the following Product Announcements: PA_00271 Software Support Policy - General Overview.pdf PA_00272 Software Support Policy - Supplementary info for_Andover_Continuum.pdf PA_00274 Software Support Policy - Supplementary info for TAC Vista.pdf PA_00279 Software Support Policy - Supplementary info for TAC INET.pdf PA_00280 Software Support Policy - Supplementary info for TAC IA Series.pdf

Issue I/A Series MNL version 3 controller profiles are not shown in the list when adding a new LON device to a SmartStruxure Automation Server.  How do I add the template for one of those controllers to the Automation Server? Environment SmartStruxure 1.3 or newer Automation Server I/A Series MNL version 3 or earlier controllers. Cause Templates are not provided in SmartStruxure 1.3 for the older families of I/A Series MNL controllers Resolution Import a device template per StruxureWare Building Operation release 1.3 Technical Reference Guide section 40.14. This procedure is used any time the device template was not pre-defined or has not been imported into the AS. The templates for the older MNL family of controllers can be downloaded from the Download Center. You should also download the associated readme file so that you understand the arrangement of the files in the folders of the zip file. We suggest that you download and unzip the entire file to your computer using the folder structure contained in the zip file. The readme file lists the xif files contained in each of the xif folders. The xif files contained in the xif_40 folder are already contained in the SmartStruxure 1.3 system. When importing these templates into StruxureWare 1.3, you may get some warnings about SelfDoc strings and possibly errors about missing DRF types. Both issues can be ignored. If errors are reported regarding missing DRF types, click the [No] button to continue the import process.   After importing the template, you can then create the device under the LonWorks network as defined in the StruxureWare Building Operation Technical Reference Guide section 40.2. The template that you imported will be listed based on the name and profile of the device. You can assign a name of your choice (or use the default) for the created device. After device NeuronID or using the service pin process to send it from the controller, you then commission the added device. You should select the option "Keep current configuration in the device". Do not check the "Device application file" because the I/A Series MNL controllers do not use loadable executable files.

Issue Use of the Building Operation Script editor and general Script programming is covered in the Training courses and technical reference guide, what other techniques can be used to debug a program? Product Line EcoStruxure Building Operation Environment  Building Operation Script editor. Cause Often additional techniques are required to debug Script programs, especially when attempting to analyze, modify or fault find other people's code. Resolution Some techniques you can use for debugging your program and isolating problems are: Add in additional line labels to the program to isolate where the program is disabling or failing, if it disables you will be able to see the "CurrentLine" it has failed on and therefore know which line of code is causing the problem. Use the Trace feature to step through a program and monitor the binding variables, stepping through each line of code to ensure the values are all set as expected. Even if a program does not disable you can use the "Stop" keyword in the program, it will act as a break in the code and you can look at the values of the various variables, this may be a useful alternative to the Trace feature. Use the Watch window and the Binding Variables window to show the values of the various objects, when used with the above two techniques it allows you to accurately trace a program flow. Ensure all of the code used is compatible with the Script programming rules and that Continuum Plain English programs are not just used without conversion. Check the Plain English and Script Difference Guide. For programs in an i2 or b3 controller, ensure none of the Program size limitations are exceeded, see Plain English program limitations on number of characters in program and line labels.  

Issue Certificate for FDA regulations in the manufacturing of pharmaceuticals, 21 CFR Part 11 "Electronic Records / Electronic Signatures." Can Building Operation incorporate a comment section to capture a reason for change made by an operator/user? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Building Operation site in need of the compliance certificate for 21 CFR Part 11 "Electronic Records / Electronic Signatures." Usually, these are pharmaceutical manufacturing sites, and the full FDA document PRT11Elect.pdf is attached to this article. Resolution EcoStruxure Building Operation 3.2 and higher Compliance Pack enables 21 CFR Part 11 compliance for regulated industries. The Compliance Pack is an add-on module to EcoStruxure Building to help regulated industries meet the compliance requirements for Electronic Signatures & Electronic Records that are in place in the region.   This feature in our EcoStruxure Building Operation software provides facility-wide accountability and traceability of the environmental conditions that can impact the quality and safety of products developed in controlled environments in line with the 21CFR Part 11 regulation.   Compliance Pack is a licensed feature and compatible with EcoStruxure Building Operation V3.2.1 and later. Part Number Description SXWSWCMPLPK001 Compliance Pack – includes TimescaleDB, Digital PDF Signing, Change Control, For one Enterprise Server or one Enterprise Central For technical documentation and sales enablement tools for the Compliance Pack, please visit The Exchange Building & Power Extranet and use the search keyword: 21cfr ebo   EcoStruxure Building Operation 3.1 and below EcoStruxure Building Operation V3.1 and below has not addressed the pharmaceutical market and there is no electronic signature feature set that meets the FDA regulations 21 CFR part 11.   For sales issues surrounding FDA regulations, please contact through your sales channel to the local Category Manager. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue After performing an Export special of an object in SmartStruxure and then importing it into a database, the output bindings of the object are no longer there. Environment Export and Import Workstation Automation Server Enterprise Server Cause Performing an export special and then importing that xml file into another database or the same database after the object has been deleted will no longer have the output bindings of that object. Resolution This behavior functions as designed. See Section 20.31 of the StruxureWare Building Operation: Technical Reference Guide. The documentation states that: "Objects or properties with bindings where the bound objects are in separate import files. To preserve bindings during an import, import the references objects to the targeted server prior to importing the actual objects or programs that refer to these objects. For example, import any referenced I/O points before importing the programs that read and write the I/O points. No matter what order of import is used, the import process will restore the bindings if they are valid at the time of import."

Issue Unable to login to Workstation. Getting error "Requested license is not available on the license Server" even though the license for the StruxureWare Enterprise Server is valid. License server does not support this feature (Error code: -18) Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3/1.4 WorkStation Enterprise Server License Server Cause When using Network Licenses this possibly indicates there was no valid WorkStation license. The Enterprise Server license does not also provide a Workstation license to run Workstation. If using Local Licenses, such as the Evaluation / Demo license and you are attempting to connect to an Enterprise Server from a separate WorkStation, the License server and the demo license file must be installed on both the Enterprise Server and each Workstation since the local license can not be shared between computers. Check Online help for additional detail. Resolution Network License: A new WorkStation license is required to use WorkStation. This would need to be acquired and added to the license Server. The part numbers for these are below. WorkStation software (including editors) Part number Product name Description SXWSWWORK00001 SW-STATION-STD-0 WorkStation Standard, 1 concurrent user license, (no maintenance subscription included) SXWSWWORK00002 SW-STATION-PRO-0 WorkStation Professional, 1 concurrent user license, Professional WorkStation version includes Editor licensing, (includes TGML Graphics editor, Function Block & Script Programming, no maintenance subscription included) Depending on what your requirements are, it may be possible to use the WebStation instead of a dedicated WorkStation for light monitoring duties. 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) in v1.3. Details on the WebStation and WorkStation can be found at the below links. WorkStation WebStation Local License: If using Local Licenses, such the Evaluation/Demo license and you are attempting to connect to an Enterprise Server from a separate WorkStation, the License server and the demo license file must be installed on both the Enterprise Server and each Workstation since the local license can not be shared between computers. Check Online help for additional detail.

Issue Enterprise Server and the B-OWS capability Environment SmartStruxure site Cause Enterprise Server and the B-OWS capability for viewing BACnet Operator Workstation Resolution The Enterprise Server is a native BACnet/IP protocol operator workstation and controller with a built-in web server. The Enterprise Server also serves as a BACnet/IP Broadcast Management Device (BBMD). The Protocol Implementation Conformance Statement (PICS) document details the BACnet Interoperability Building Blocks that are supported in StruxureWare Building Operation. The PICS are available from the BACnet International labs for BACnet Operator Workstation (B-OWS) Continuum 1.9x The below screenshot is of a StruxureWare Building Operation 1.3 Release and the desired connection using B-OWS to a Continuum 1.94 Release. Workaround is on the BACnet Interface of the ES, highlight the IP Network then Add New BACnet Device. 1. Suggested name would be the Cyberstation Name 2. Upload from BACnet device 3. Instance ID is the Device Node ID (Right-click/Edit on the Cyberstation) 4. Create Then perform an Upload from the newly created Cyberstation. Resulting View from the Enterprise Server: (Note that Cyberstation owned objects are not available in the Enterprise Server) There is an “official” document on Continuum and StruxureWare Building Operation BACnet communication that was produced specifically for this issue. It is a TVDA produced by the Buildings StruxureLab and it is Andover Continuum BACnet with StruxureWare TVDA 1.02

Issue Getting an Error 1001 near the end of the EcoStruxure WebReports Installation Reports not functional from WebReports Product Line EcoStruxure Building Operation Environment Web Reports SQL 2008 R2 Windows Server 2008 Windows Server 2012 Cause This error is caused when the WebReports installer is unable to reach SQL Server Reporting Services to configure the WebReports Interface Resolution After a failed install of WebReports you will need to follow the general workflow:   Clean of the Pieces of the failed install. Use the uninstall process listed in the WebReports Reference Guide or Uninstall Process for Web Reports. Correct all possible causes of the failed install Verify that you can connect to the ES using http from the Reports Server PC Verify that you can connect to http://localhost/Reports_SQLInstanceName  Re-install WebReports. NOTE: You may be able to correct the issue without having to remove and re-install WebReports. Possible Issue: The Microsoft Reporting Service SQL databases are not registered Check through SQL Management Studio that the 2 databases "ReportServer$instance" and "ReportServer$instanceTempDB" are registered. If not, the SBO Web Reports installed have nowhere to place the report pack files. If they are not there, you need to add them through "Reporting Services Configuration Manager". Click "Database" and then "Change Database". Here you can chose to create new databases. Possible Issue: Insufficient User Access Log out of Windows and Log back in using a PC admin account. The account logged in for the installation should have full access to Windows and be a DB admin in the SQL Server. Set the User Account Control Settings to Never notify. Possible Issue: PC Configured as a Domain Server In the Server Manager, check that the IIS Role is configured and that there are no Domain Roles assigned to this PC Possible Issue: Another Application is using a Required SQL function Uninstall any application which use SQL on this PC. (The Enterprise Server does not Use SQL) As a Best Practice, the Reports Server should be installed on its own, dedicated PC. Possible Issue: Incorrect Version of SQL Server or Windows Server Check the Reports Server Specification Sheet for your build and verify that you are on the Correct Version of Windows and SQL. Possible Issue: Secure Connection Level set too high This issue typically also results in not being able to log into http://localhost/Reports_SQLExpress. Log into the Reporting Agent Configuration Manager Application Click on the Report Manager URL on the left-hand column Click on the HTTP URL This will give you the correct URL for your installation of SQL If this fails, browse to C:\ProgramFiles\Microsoft SQL Server\MSRS10_50.SQLEXPRESS\Reporting Services\ReportServer (this may vary based on SQL Installation)   Modify the CONFIG file "rsreportserver" Change the Secure ConnectionLevel to "0" Save the file and attempt to log into http://localhost/Reports_SQLExpress again. For more details on this property see: http://technet.microsoft.com/en-us/library/aa179559(v=sql.80).aspx Possible Issue: .NET Framework is not operating correctly. Download the correct version of .NET framework for your version of EBO (The correct required version can be found on WebHelp Reports Server under EcoStruxure Building Operation Software Requirements) Run the installer in "Repair" mode Possible Issue: The Windows account "appuser" is not created because the default password does not meet password policy requirements Temporarily disable password policy on the server and try reinstalling. For clarification of the use of 'appuser', refer to the following article, Report Server "appuser" clarification 

Issue After upgrading from EcoStruxure Energy Expert (formerly Power Manager) from version 1.0 to 1.x or newer, the licensing no longer works. Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Energy Expert (formerly Power Manager) License Administrator Power Monitoring Expert Cause There can be some confusion on what licenses are required to run Energy Expert. There are also differences between version 1.0 and 1.x or newer licensing.  Resolution EcoStruxure Energy Expert License In order to use Energy Expert, an Energy Expert license is needed to be purchased before the previous 90-day trail license expires.  The EcoStruxure temporary license (evaluation) is only for EcoStruxure Building Operation software and does not include Energy Expert   It is important to remember that EcoStruxure Building Operation licenses are needed to work along side Energy Expert (e.g. Workstation, Enterprise Server, etc). The EcoStruxure Building Operation licenses need to be activated separately.  How to activate, release and/or transfer a license in EcoStruxure.   Energy Expert Version 2 and 3 Licensing and Upgrading If upgrading from a previous Power Manager 1.x site to Energy Expert 2.x or 3.x a new license(s) will be required. In order to obtain your new license(s), please follow the procedure found in TPA-EBO-19-0001.00 - EcoStruxure Energy Expert v2.0 License Upgrade. (Full support ends 2022 and limited support ends 2024) Energy Expert Part numbers and Licensing The part numbers for version 1.x or newer are listed below. PSWPMNCZZSPEZZ -  Base Energy Expert license PSWDENCZZNPEZZ -  PME license entry range PSWDMNCZZNPEZZ - PME license mid range  PSWSANCZZSPEZZ -  Standard PME. license For a full list of both current date and obsolete part numbers please download the following spreadsheet https://ecoxpert.se.com/pme-digital-power-launch)   Activating a License Full guidance for activation of your licenses can be found on Page 55 of the Energy Expert 3.0 Solution Guide The Energy Expert 3.0 installer and documentation, can also be found here EE 3.0

Issue Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert There are some best practices and tips that can be used to save engineering time when setting up a EcoStruxure Energy Expert (Formerly Power Manager) system. To find out the differences between Energy Expert and Power Monitoring Expert (PME) see Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Energy Expert EcoStruxure Power Monitoring Expert ETL Integration Tool Cause The following topics should be considered before and during the implementation of the EcoStruxure Energy Expert offering to achieve the cleanest and most effective database.    For more information on design considerations including IT considerations, software compatibility, server specification, hard drive space, etc; see Design Guide - EcoStruxure Energy Expert - formerly Power Manager. For more information on integration see Energy Expert with EcoStruxure Building Operation.  For more information regarding Power Monitoring Expert (PME) please visit the Solutions Expert Community. Here you can find documentation, content, and additional help.  Resolution You may get some benefit working thorough some older existing support material under Energy Expert's former name of Power Manager such as the Deploy Power Manager for SmartStruxure Solution in a Day document.  Also check out the Power Manager EWS Alarm Web Configuration Quick-Help video on the Exchange. General Always install the EcoStruxure Energy Expert software with full Windows administrative rights. Just logging in with a user that has admin rights may not be enough. If you are unable to save an ETL job or run as a service; close ETL, right click on ETL and select run as administrator.  Create one folder on the root level of the server that holds all of the extended trend logs you wish to transfer to EE. This folder can even be set up to be visible to only a designated admin account to prevent any changes to be made to the trends. If any other items like trend charts are in this folder, it will only slow down the process.  See StruxureWare ETL tool locks up or takes a long time while loading sources for information on how to improve the scan time of the ETL load sources function.    SQL Server It is not recommended to install EcoStruxure Energy Expert on a machine that has another instance of SQL already installed on it unless you have advanced SQL configuration skills. The default SQL instance name is ION and the system administrator password is ION!Everywhere. This should not be changed.   Selecting Between Architecture 1 and 2 The three items to consider when selecting an Architecture are device type, numbers of registers to be requested, and device location. The device type is the most important item to consider though. In order to get the most out of the high feature, more robust meters, Architecture 2 should be used. Architecture 2 should be used if the following features are present; ION meter, multi-address device, power quality functions, onboard logging, and/or onboard alarming. When low-end power meters, energy meters, or pulse meters are used, there is no difference between the two architectures in fulfilling the energy management requirement. Most of the Schneider Electric meters and circuit breakers are fully supported by EE. This means that EE has built-in drivers to utilize the full function of the device and the required commission time is minimized.   Architecture 1: Logging data in EcoStruxureWare Building Operation (EBO) It is recommended to use interval trend logs to log the raw data coming in from the meters.  The only durations that need to be set up in trend logs for ETL is the standard trend log duration. This is generally going to be 15 minutes as a industry standard. EE Dashboards and Reports have an aggregation mechanism to make use of the data. Thus durations such as day, week, or month do not need to be brought over into EcoStruxure Energy Expert (EE) as it can be calculated later based off of the 15 minute trend log value.  If both Trendlogs and Extended Trendlogs are used, it is recommended to send the data in the Trendlog to EE to avoid the lagging between Extended Trendlogs and Trendlogs.    ETL StruxureWare Building Operation version 1.6 RC EcoStruxure Web Services (EWS) do not support Secure Sockets Layer (SSL) URLs. For the ETL Extract task make sure to fill out the web service name (default is admin), web service password (default is admin), and web service URL (replace localhost:8080 with your web server address and port as needed) in the settings. For the ETL Load task make sure that the ION data database connection string and ION network database connection string are correct. Also change the field enable recorder and channel creation to True. The recommended naming convention for the Target Device field is [Group].[DeviceName] with no special characters such as \ * + = | : ; < > _. An example could be BuildingA.SubMeter1 where the building name is used as the group and the meter name is used as the device name. With this naming convention, all values brought in under this particular meter will have the same Target Device name.    The Target Measurement field is very important to set correctly as it will not bring the data over to EE correctly if the right unit has not been chosen. This is a process that will become easier with more experience but you can reference Section 6.9 Measurement mapping for ETL in the Power Manager for SmartStruxure Solution - Integration Manual. This chart can be used to search for the unit type you are dealing with and which corresponding Mapping should be use. 

Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue There have been questions about how the new EcoStruxure Building Operation 2.0 demo license works with the new scalable pricing structure. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and up All previous builds of SBO 1.9 and below Cause Understanding what the EcoStruxure Building Operation evaluation license will allow to function in the newer versions of the product.  Resolution The EcoStruxure Building Operation Evaluation License is a temporary license used when a database is being brought online before the permanent license has been deployed or on engineering laptops. All authorized Schneider Electric employees and partners can download the file from the Exchange Extranet. The file is updated every quarter as each one has an expiration date. The functionality of the demo license has not changed in version 2.0 and newer. This license file will still allow functionality and engineering of a database to take place as long as the file is valid. The only difference is the new warning banner that will be present until permanent licenses are installed.  Note: With the new scalable pricing starting in version 2.0, once the evaluation license is removed from the site, a license is needed for each Automation Server attached to the Enterprise Server.  More information on the Scalable Pricing structure can be found in EcoStruxure Building Operation Licensing and Scalable Pricing Info. 

Issue ES connect to 3rd party BACnet devices in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Enterprise Server. Connection to BACnet devices such as ACX. Cause Desire to use ES rather than AS Resolution As of StruxureWare Building Operation 1.1 the ACX with BACnet I/P xDriver with the ES, we can see the points, load them into the BACnet interface, and view them in tgml. The BACnet IP xDriver and User Guide is available on The Exchange Download Center. The following screen captures are from the ACX where a simple Infinity Numeric is setup called ACXdevice:   Next the xDriver for the ACX is loaded and setup as Server with the following settings: (Note the IP Address references the IP of the ACX controller)   Next a simple Numeric is setup called BacTest1 with the following settings: (Note the IP Address is left blank)   Next another Numeric is created called CocaCola1 with the following settings:   Next from the Enterprise Server, a 'Find New BACnet devices' is done to find the ACX and the two Numerics created:  

Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Where can I download SmartStruxure V1.5 software and manuals? Product Line EcoStruxure Building Operation Environment SBO version 1.50 software Cause Download location required. Resolution The following link is to all documents and software associated with V1.50 release. Or go to The Exchange Download Center and search on the tag: relsbov1.5 (short for: Release SBO V1.5).

Issue In rare occurrences, technicians may remove the bottom terminal from the AS or I/O Baseplate so that a power supply can fit. The backplanes inside the baseplates are not all the same and this will not work. Visually determine which baseplate is for each module. Product Line EcoStruxure Building Operation Environment SmartStruxure Power Supply SmartStruxure Automation Server SmartStruxure I/O module Cause Incorrect baseplate will not work on the SmartStruxure modules. Resolution See picture for representation of Power Supply backplane, the other configuration is for Automation Server (and I/O modules). For more detailed information please see the Hardware Reference Guide.

Issue Device Manager Upgrade and Hard Drive Requirements Environment StruxureWare Building Operation using Device Administrator for upgrade of Automation Server Cause A question has been raised following the training regarding the ability to upgrade 32 AS databases simultaneously, what storage space does the off server upgrade need, since it is now possible to upgrade 32 AS databases at once this could impact HDD space required, what about RAM, what about bandwidth requirements when downloading the converted DB to the AS? Device Administrator 1.3.0 Update (12 Mb) was available Feb 1, 2013. This add-on significantly reduces the time it takes to upgrade an Automation Server from 1.2 to v1.3. It cannot be used for any other upgrade paths. For more information, please read Product Announcement PA-00249, and Release notes StruxureWare Building Operation v1.3 - UPDATE which is available on The Exchange Download Center.   Resolution Please take into consideration the number of Automation Servers to be upgraded and count 200 Mb of disk space on the Computer Hard Drive per Automation Server.

Issue Device ID / Device Instance of SE8000 series BACnet controllers Duplicate BACnet Network Address alarms How to have 254 SSL Room Controllers on an Automation Server (AS) as shown in the SBO Automation Server and SE7000 and SE8000 - Architectural Guidelines Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Room Controller BACnet Cause There can be confusion from the difference in naming between SmartStruxure Lite(SSL) Room Controller(RC), SmartStruxure Building Operation and even Niagara(JACE). Bacnet Instance number in SSL = Object ID in SmartStruxure Building Operation COM Address in SSL = MAC Address in SmartStruxure Building Operation Resolution On the AS, considered is the Object ID of the two Comm Ports (as with all object IDs) they need to be unique across the system. A common ID is 1001 for CommA and 1002 for CommB of the first AS, then on the second AS CommA 2001, CommB 2002 etc. The key thing with BACnet is that every object (point, device, program, port etc) must have a unique Object ID. The SE8000 uses the Com Address referred to as the BACnet MAC Address in the AS. This, as detailed in BACnet COM Address of Room Controller SE7000 and SE8000, is the address range on just that one MS/TP bus. 1 – 127 are valid addresses, the AS (or bus master) will be address 0. If a second AS is on the same system this could use 83001 – 83127 for CommA, 84001 – 84127 CommB etc. Also SE8000 uses the BACnet Instance number which is called the BACnet Object ID in the AS. (This is the ID which must be unique across the whole system) So if you have the 2 ports used on one AS all 254 devices must have unique ID’s. When changing the Comm address in the SSL SE8000 to any value between 1 and 127, the Instance number will change as well. For example Comm address 9 would result in an Instance number of 83009. These will cover 127 stats that will go on CommA, and result in Instance numbers between 83001 and 83127. Any value above 127 will keep the Instance number unchanged. For CommB however, a site would need to change the Instance number manually. For example the first RC connected to CommB would be the 128th and would default to address 83127. So it is required to manually change the Instance number to 1083001 (up to 1083127). This defines unique Comm Addresses for ComB on the remaining 127 RC. When using an Automation Server (AS) you can find the Object ID and MAC address for devices on MSTP by using WorkStation and going to AS > System > Hardware > BACnet devices > Network_xxxx. A screen shot is below with the added columns Status, System Status, Object ID, and MAC address. In this first example, b3 controllers use the Object ID or Device ID of their serial numbers so each b3 is unique across the network. B3 controllers with serial numbers greater than 4194302 (the maximum allowed Object ID in BACnet) will be assigned a Device Object ID using a hashing algorithm to ensure it is unique. From an SE8000 series RC, BACnet network set-up screen shows when BACnet is detected in models. Select desired parameter and use up or down arrow to set parameter to desired value. The default BACnet instance number is generated by the model number and COM address of the controller. For example, The instance number of a SE8300A5B00 with a COM address of 57 is generated as "83057." The default instance number appears first. To change the instance number, use number pad and press Accept and Save. Below is a screenshot of the WorkStation logged into an AS, with the BACnet Interface and the MSTP network. The added columns show the Object ID and MAC address. Below is a screen shot of the WorkStation logged into the AS, with the System > Hardware Devices > Network_xxxx. The added columns show the Object ID and MAC address.  The screen shot below is the AS > BACnet Interface > MSTP Network > Configuration Settings.

Issue Using the Xenta 421A, 422A, 451A or 452A I/O modules as a stand alone Lonworks node and all values are reading the default 0. Product Line EcoStruxure Building Operation, Field Devices, TAC Vista Environment Xenta I/O Modules Xenta 400, 421A, 422A, 451A, 452A as stand alone LON nodes Cause The Xenta 421A and Xenta 451A as stand alone Lonworks node require the UCPTConfiguration to be set to the necessary integer value for the required input. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network management software (Lonmaker, NL220, Tridium, Etc.) Browse / Edit the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the UCPTConfigInput variable within that module Set this UCPTConfigInput variable to one of the following: 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication NOTE: This is normally done in Menta when you are using these controllers as I/O modules to a Xenta 401, Xenta 301, Xenta 302 base unit.  The scan time of all inputs is (200ms * number of inputs used).  So if there are 3 inputs, the complete module will have been scanned every 600ms.

Issue How to connect and configure current inputs to a UI module? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch UI (UI-16) Building Operation I/O Module 8 Ch UI/4 Ch DO (Form C) (UI8-DO-FC-4) Building Operation I/O Module 8 Ch UI/4 Ch AO (UI8-AO-4, UI-8/AO-V-4) Building Operation MP-C, MP-V, RP-C, IP-IO Cause How are Current inputs connected and configured? Resolution To connect and configure a current input to a SmartX device no additional external resistors are required, the internal resistor in the SmartX device is automatically put into the circuit by selecting "Current Input" when creating the input object, there are no DIP switches to change as in some other products. An external Power supply will be required to provide the current in the circuit through the sensor and into the UI input. 24V DC supplies are usually used to power the sensor & provide the current drive. Further information regarding the SmartX device's internal resistor can be found in the Hardware Reference Guide. Example Circuit: The input point configuration allows you to define the top and bottom or the current scale (usually 4-20mA or 0-20mA) and the engineering units this corresponds to i.e. 0-100% or 0 - 400 DegC. The following screen shot example shows the configuration for a 4-20mA input signal represented as 0-100%