Issue References Guide and changes from release 1.3 to release 1.4.x and forward Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with regards of release 1.3 to release 1.4.x Cause In release 1.3 and earlier the reference system was relaxed allowing for bindings to be created in ways that made the applications error prone. In release 1.4 this is now being more strictly controlled, which will allow the system to: Help the user to not unintentionally create faulty combinations of references, resulting in bad/unpredictable application behavior and last man win situations Better understand and control how references will behave in copy/paste/move/delete situations. Improve performance in the system, e.g. the limitation of variable connectors is removed. For the complete Reference Guide, please download the pdf from the Download Center For instructions on how to upgrade an Automation Server and how to get the conversion log, See Upgrading Automation Servers from 1.3 to 1.4. For explanations of the entries found in the conversion log, See AS Conversion Log Analysis. Resolution What has changed There are 2 areas which have changed:   1. Rules Programmatic control: A reference means that data is sent from A to B. In Release 1.3 it was possible to send data from A to B and from C to B. This gave a "last man win" situation. In Release 1.4 it is only possible to send data from exactly one source to a recipient. This means A to B and C to B is no longer allowed. User control: This is where properties are displayed in graphics, watch windows and other client components. In release 1.3 it was possible to change a property that was programmatically controlled. This gave a "last man win" situation. In release 1.4 it is not possible to change a property as a user if this property is programmatically controlled by something else. The property will automatically be read only for the user.   Public signals: In release 1.3 and earlier, it was possible to programmatically control a public value in programs. Public signals are intended to be used for user control, while inputs are intended for programmatic control. In release 1.4 this is now changed to the following: Public signals in programs (FB/Script/Menta) can be referenced by user control - NOT by programmatic control Public signals intended for programmatic control must be changed to inputs and rebound. This will give the following benefits: Public signals cannot be forced, while inputs can. If a user needs to take control of a programmatically controlled input, via e.g. graphics or watch window", he will force the signal and there will be no risk of a program overwriting the user value. As stated above - if an input is programmatically controlled, this will for the user be read only. However, force is still possible. There is no more risk for "last man wins" situation between user control and programmatic control. The system will remove any ambiguity with these new sets of rules. Update: Release 1.4.1 and later version add the feature of binding to PVB/PVI/PVR back. But for Script, it still keeps the same. LonWorks Local Node nvis: In release 1.3 it was possible to programmatically write to local node NVIs. These NVIs exist to receive data from the LonWorks network. This gave a "last man win" situation. In release 1.4 it is no longer possible to programmatically control local node NVIs.   2. Definitions In release 1.3 a reference could be a) relative b) system absolute c) server absolute In release 1.4 a reference will be a) "normal" b) Locked A reference created by the user will always be normal (which means relative). In the bindings view the user can then choose to "lock" a reference (which means server absolute). The references will behave identically until a copy/paste (or import/export)  operation is done.         Upgrade Upgrading from release 1.3 to release 1.4 will apply the new sets of rules. It is there for very important to read the log to understand if any existing references in release 1.3 will be impacted during the upgrade For AS: In the Device Administrator the logs are available before the upgraded DB is deployed to the AS. It is up to the user to either examine the upgrade log, make changes in running release 1.3 and rerun the upgrade, or to make the changes after upgrade. It is recommended to do changes prior to upgrade to ensure a fully functional system directly after upgrade. Some warnings are benign and can be disregarded, please refer to release notes for more information. IF an upgrade detects that references will be impacted, the user will be informed about this with a orange progress bar indication and a written information that the upgrade succeeded with warnings. After upgrade, all invalid or unresolved references will be visible from WorkStation for further examination if needed.

Issue Where can I find information on EWS? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled SmartConnector Cause Documentation required Resolution Documents can be downloaded from The Exchange Download Center - EcoStruxure Web Services EcoStruxure Web Services Specification can be found at: SmartConnector Server

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.

Issue Do all b3 and i2 Controllers support  all PE commands Environment b3 i2 Controllers String Trig Cause Some PE commands can not be used on some b3 or i2 controllers Resolution The following Plain English system functions are not supported in the i2885, i2885-V, and i2887(L) controllers: (b3885,b3885-V, and b3887(L) controllers) ACOS, ARCCOSINE, ARCSINE, ARCTANGENT, ARCTANGENT2, ASC, ASIN, ATAN, ATAN2, CEILING, CHR, CLOSELIST, COS, COSINE, EXP, EXPONENTIAL, FACT, FACTORIAL, FIRST, FLOOR, GETOBJECT, LAST, LEFT, LEN, LENGTH, LN, LOG, MID, NUM_TO_STR, OPENLIST RANDOM, RIGHT, RND, ROUND, SD, SEARCH, SIN, SINE, STANDARD_DEVIATION, STR_TO_DATE, STR_TO_NUM, STR_TO_TIME, STRINGFILL TAB, TAN, TANGENT, VAL See - b3 technical data - i2 technical data - PE Programming guide

Issue Users or engineers may be unsure of how to obtain the Smart Connector itself, as they are not generally available for download from the Exchange Download Center or the Smart Connector Forum on the Community. Product Line EcoStruxure Building Operation Environment SBO/EBO and general integration projects SXWSWSCDL100001 Cause Smart Connectors are not freely available and will require a license obtaining in order to download and use them. As Smart Connectors can be developed by a number of teams around the world that are not part of R&D, these teams will define the costs and requirements for using their software. Resolution A Product Announcement PA-00546 is available that details the concept and use of Smart Connectors. To order the Smart Connector Framework for a project, use part number: SXWSWSCDL100001  Then go to the Smart Connector Server licensing portal to obtain your required license for the specific Smart Connector you require. The URL for the License Portal is: https://www.smartconnectorserver.com/ A login is required for this portal which can can be obtained through the "Sign Up" button. Once logged in the user may browse through the available Smart Connectors and request to download a license. For support information on Smart Connectors, see the article "Support route for Smart Connector Framework issues".

Issue Unable to add trend /extended trend logs after upgrading from SBO version 1.8 to 1.9 Product Line EcoStruxure Building Operation Environment Upgrade from v1.8 or below to v1.9 or above Cause The number of trend log records in the server have exceeded the limit. No new trend log or extended trend log can be added to the server. See Architectural Guidelines v1.8 and Architectural Guidelines v1.9, The maximum number of trend log records in an Enterprise Server is 2.5 billion, and  SmartStruxure server device (AS, ASP,ASB) is 10 million In v1.8 and before, these trend record limits were soft limits. From v1.9, these are now hard limits. Thus it is not possible to save more than these amounts.  Resolution The logging numbers should be reduced below these limits 

Issue An Energy Expert system is being moved to a new server and/or the virtual image is being upgraded. The historical records held in the SQL database of the Power Monitoring Expert (PME) system need to be backed up and properly restored on to the new server. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Power Monitoring Expert (PME) Enterprise Server 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. Cause The system administrator has deemed it necessary to upgrade the Windows server that the Energy Expert system is installed on for security and/or resource reasons. Resolution It is important to remember that an Energy Expert installation is really just two Schneider Electric offers, EcoStruxure Building Operation and Power Monitoring Expert, installed together and set up to pass information back and forth. This means that appropriate steps must be followed for each system to backup the historical data and properly restore it on the new server. For more detail regarding how the system is laid out, please see the Difference between EcoStruxure Energy Expert (Power Manager) and Power Monitoring Expert (PME). Steps to move an Energy Expert database Backup the Power Monitoring Expert (PME) SQL database, dashboards and reports. The Configuration Manager tool available on the Exchange can be used to back all of these items up automatically. Run the tool on the existing server and it will create a zip file to be used later on when restoring to the new server. See Migrating a PME 8.0 System to a New Server for more information. The Schneider Electric Technical FAQs website also contains many other helpful troubleshooting articles for PME including different versions of the product. Return the Energy Expert license(s) from the Floating License manager in order to move them to the new server. For more information see Video: Licensing Guide for Power Monitoring Expert (PME) 8.x and 7.2.x and ENM 8.3.x. If moving the Enterprise Server, make a historical backup of the EcoStruxure Building Operation (EBO) ES from the existing server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES for more information. If the Enterprise Server and other EBO licenses are installed on the existing server, then they may need to be returned as well so they can be moved to the new server. See Removing a Local License or Returning a Network License for more information. Next the ETL project files must be retrieved and saved so they can be moved to the new server (if using architecture 1 in the Energy Expert offer). Go to the file location below and save all ETL project files that are needed on the new server. C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs If moving the Enterprise Server, install the EBO software on the new server, rehost the EBO licenses, and restore the EBO server backup(s). See Restoring the EcoStruxure BMS Server for more information. Install the Energy Expert software (the software includes PME, ETL and the integration utility). The information on how to download the Energy Expert software can be found on the Exchange. Once the software has been installed, the Energy Expert license can be hosted to the new server in the Floating License manager. Next, install the PME Configuration Manager tool on the new server. The zip file from step 1 can be loaded using this tool to restore the SQL database, PME dashboards and PME reports. Add the previously saved ETL project files to the same location on the new server C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs Since the server has changed, the configuration settings must be updated in the ETL projects to reflect the new server name. The settings in the EWS interface on the EBO server will also need to be updated as well. Note: It may be easier to delete the existing EWS interface in EBO and then use the integration utility to create a new XML import file to simply rebuild the interface.

Issue Once the occupied cooling and heating setpoints are written from a BMS, the user is not able to change the setpoint from the room controller Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Series Room controller Viconics branding VT8000 Series Multi Purpose Manager (MPM) BACnet Cause By default, the occupied setpoint value is written to Room Controller with priority level 16 by the BACnet front end. Attempting to change the setpoint locally using the up and down arrows on the SE8000 Room controller will not be allowed since the Room controller uses the relinquish value internally (priority 17) which will be automatically overwritten by the BACnet front-end. Resolution The work around is to release the BACnet front-end control over the BACnet object using a LUA4RC script. The script can be uploaded using one of the following two methods: 1 - Uploader Tool A USB cable is required to upload the script. The uploader tool can be downloaded from the Exchange Download Script Download Uploader Tool   2 - BACnet The script can also be directly uploaded via BACnet using the "Description" field as shown in the image below if (ME.AV92 == 6 or ME.AV92 == 7) then ME.AV39_PV[16] =nil ME.AV39_PV[10] =nil ME.AV40_PV[16] =nil ME.AV40_PV[10] = nil ME.AV92_PV[17] =0 end Where, ME.AV92 is the Keyboard value ME.AV39 is the Occupied Heating Setpoint ME.AV40 is the Occupied Cooling Setpoint Using this method, the script can be uploaded to multiple SE8000 Room Controllers by following the steps in Bulk Lua4RC upload via BACnet (Mass upload) For more information about Lua4RC, refer to the Lua4RC Programming Guide

Issue Language Packs are required for each new release of SmartStruxure Environment EcoStruxure Building Operation Cause On each Change of revision, Maintenance, Service Pack, Hotfix or New Release requires the need for new Language Package Resolution The Language Pack is built for each specific version of Building Operation. There must be a language pack specifically built for each build, i.e., for 1.5.0.3003 you need a language pack built for that specific hotfix 1.5.0.3003 version. Example: One language pack is needed for Building Operation 1.5 and another language pack is required for Building Operation 1.5.1. Language Packs are available on the Exchange Extranet   For further information on Language Packages and how to install then refer to the Online Help Topic; Language Packages For more information on creating specific Language packages, please contact your corresponding regional category manager via the following email addresses: Americas: Americas.EcoStruxureBuilding@schneider-electric.com  EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com  Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue Missing LNS plugins for  EcoStruxure Buildings Operation Workstation Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Cause Plugins for EcoStruxure Buildings Operation are not included in these releases. Resolution Download the TAC Vista 5.1.9 tool pack and this will install the 100 series controller plugin and Z-Builder programming tool. Once this is installed EBO will be able to access these plugin when used with Open LNS. Download the TAC Vista 5.1.9 Toolpack - Software from Exchange Extranet. Direct Download also provided. 

Issue Files required to install EcoStruxure Building Operation Web Reports Server Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Tutorial for configuring Web Reports Resolution EcoStruxure Building Operation WEB Reports Server Release To start installation, download WebReports Operating Guide and WebReports Reference Guide Installation Outline: The WebReports Reference Guide provides detail information about hardware, software requirements, and steps required to configure the applications. The following steps are an overview of the complete installation. Points 1-4 are easily and/or automatically done using "SBO Reports Preparation" available from the Buildings Community. This tool is not officially supported, but has proven to be helpful in many cases. Install and Configured required Windows applications, roles, and features. Outlined in Sections 3.4 of the WebReports Reference Guide Download and install SQL Server 2008 R2 Standard with Advanced Services it requires version 10.5 or later. Follow configuration steps found in Section 3.5-3.6 of the WebReports Reference Guide SQL 2008 R2 Standard with Advanced Services file name SQLEXPRADV_x64_ENU.exe Install .NET framework 4 per WebReports Reference Guide section 3.7 Ensure that the Enterprise server is running on another machine, or at this point install and configure it on the local machine Install WebReports Server using the processes defined in WebReports Reference Guide section 3.9 and 3.10 The online help guide for EcoStruxure has a tutorial which will walk you through configuring the report Server, and running reports: WebReports Overview  If you wish to create custom reports. Please follow the instructions as outlined in How to create custom reports in Building Operation WebReports APPENDIX A: Verifying system is ready for reports installation Before installing WebReports, but after configuring Windows Roles and Features, SQL and install .NET 4.0,(SBO 1.5 uses .NET 4.5) the user should always: Check to see that SQL Server is up and running Check that the user you are planning on installing WebReports with can connect to SQL and Microsoft Reporting Services. Log into SQL using SQL Server Management Studio User should be able to connect and view databases. Connect to the MS Reporting Services URL You can obtain the URL by: Start->All Programs-> Microsoft SQL Server 2008 R2->Configuration Tools->Reporting Services Configuration Manager. Once logged into Reporting Services Configuration Manager click on “Report Manager URL” and click the URL Verify that Reporting Services Manager page loads without error. If you run into issues with the above, a possible solution is to turn of User Account Control Settings. This can be disabled by going to the Windows Control Panel, selecting User Accounts, selecting "Change User Account Control Settings" and moving the slider all the way down. You must restart the PC for this change to take affect. Repeat the above steps and contact PSS if you are still unable to validate the system. APPENDIX B: Upgrading a report server installation As described in appendix A, the logged in Windows user is used to install the report server, and this user must have access to the SQL database. That is also true when upgrading the report server installation, so make sure you are logged into Windows with the correct user. Another option is to SHIFT + right click the installer, and select "Run as other user".

Issue Import/ Export functions of Tree Tech 3.2 on Windows XP SP3 were disabled by recent Microsoft update. No .GDF file exported, no error message displayed. Environment Tree Tech revision 3.2 installed on Windows XP SP3 computer Cause Believed to have been caused by a recent Microsoft update.  Resolution There are two work-around options: Run Tree Tech 3.2 on Windows 7 , 32-bit machine If the project database is backed up from the Windows XP computer, it can be reloaded on the Windows 7 computer. The project database path on the Windows XP computer is: c:\Documents and Settings\All Users\Schneider Electric\TreeTech\Jobs\Projects\  On a Windows 7 computer, the file path for the TreeTech database is c:\Program Data\Schneider Electric\TreeTech\Jobs\Projects\    Un-install Tree Tech 3.2, install Tree Tech 3.1 on Win XP SP3 machine if no Win 7 machine available. Tree Tech 3.1.exe is available on The Exchange Download Center Run the WIBs purchase, generate license request for IV-DEMO-CDE, send file to us to create a license. OK to export GCM database already uploaded in 3.2 

Issue Does the entire SBO system need to be upgraded to 1.5.0.171xx, 1.6.2.12xxx or 1.7.2.111xx before upgrading to 1.9.1 if the network includes LON devices? Can SBO be upgraded directly to 1.9.1 from 1.5.X, 1.6.X or 1.7.X? Product Line EcoStruxure Building Operation Environment SBO Workstation 1.5.0/1.6.1/1.7.1 SBO ES 1.5.0/1.6.1/1.7.1 SBO AS 1.5.0/1.6.1/1.7.1 SBO AS-P 1.7.1 Cause In systems that have SBO servers that already are hosting LON devices based on LonWorks imported device templates (.XIF) or resource kits (.DRF), the servers need to be prepared before an upgrade from versions 1.5/1.6/1.7 to version 1.9.1. Even servers where device templates (.XIF) or resource kits (.DRF) are just imported, and no devices or network variables are created yet, the servers have to be prepared before the upgrade. Resolution Please see section 9.2.3 of SBO 1.9.1 Release Notes. Although it says "Steps to upgrade a 1.6.2/1.7.2 multi-server system" you don't have to upgrade the AS or ES etc, even if they run 1.6.1/1.7.1, it's only SBO Workstation that need to be hotfixed. Links to the different Workstation hotfixes can be found Server with LonWorks devices - TPA-SBO-17-0002.00 - Links to hot fixes. If there are no LON devices in the system, you may upgrade directly to 1.9.1 from 1.5.X/1.6.X/1.7.X

Issue What configuration is required for a Multical BACnet heat meter Environment Schneider Electric (Kamstrup) heat meter connected to a Continuum or SmartStruxure system on MS/TP. Multical 61/62/601/602/801 Cause Setup information required Resolution With the BACnet interface card fitted in the Multical meter it is a native BACnet MS/TP device. Connect it to the AS or bCX1 depending on your system and Learn/ find BACnet devices. It should appear online and allow the objects to be uploaded. A typical unit like the Multical 602 will contain 12 Analog Inputs for all of the information from the meter. The Meter will operate at 9600, 19200, 38400, 57600 and 76800 Baud rates and autobaud to the connected system. For the Datasheet  Click Here. For the BACnet PICs statement Click Here. For help with Heat meter selection see the online selection tool: Online Heat Meter Selection Tool - PA-00216

Issue How to change the IP address in the EC/ES software when it is grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central (EC) and Enterprise Server (ES) Building Operation WorkStation Cause The EC/ES IP address is grayed out in the Network Tab of the Server Properties and cannot be changed.  This setting is only used to view the IP address that the server is currently using - typically the IP of the network interface card of the PC running this.  To change this setting it must be done through the Communications TAB of the server as detailed in the resolution.  Resolution EcoStruxure Building Operation 2.0 and above EBO 2.0 and above now supports multiple NIC configurations, see 2.0.1 Release Notes for details, in particular, the following note.   Note: That from 2.0 the server will still listen for incoming requests on all network adapters so this setting is only used for choosing which communication settings that the server will use to communicate with child servers. This allows other IP protocols on different networks, e.g. BACnet, Modbus, etc. to communicate with the Server.    It is now possible to select which network adapter the Enterprise Central and the Enterprise Server use.  See the following WebHelp Topic Configuring Network Interface Card for an Enterprise Server or for an Enterprise Central StruxureWare Building Operation 1.9 and below  When the IP address of the computer changes the ES will automatically update the "IP/DNS Address" in the Properties, Network tab. If your computer has multiple network connections, ensure that the Network Interface Card (NIC) to be used for the SmartStruxure network is set to be at the top of the list in the Adapters and Bindings. Go to the computer's Control Panel > Network Connections Select "Advanced, Advanced Settings... " from the menu. In the "Connections:" section, select the Network Connection to be used and press the up arrow to move it to the top of the list. For Windows 7 / Server 2008 See the following link on how to change the order of protocol bindings: How to change the network connection priority in Windows 7 For Windows 8 and beyond, please refer to Adapter priority setting unavailable in Windows 10 In addition to the ES Network Properties, there is also the Communication tab in the ES that lists all of the Server IP addresses in the system. If these need to be changed this can be done by selecting the server and clicking on the "Show/ Hide Communication settings" button circled in red below.

Issue How to read individual bits from a Modbus Holding Register that holds a 16-Bit Word and represent each Bit as a separate Digital point Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B) Modbus TCP/IP Modbus RTU (RS485) Cause There is a requirement for a Modbus Holding Register that is a 16-bit unsigned value, each bit represents a digital state in the Modbus device and to replicate this as 16 separate digital states in EBO. The 16-bit unsigned value is an integer with a range of 0 to 65,535 and needs to be converted into 16 digital values. Resolution Use a Modbus Digital Input point for each bit required. Each object will be configured to read the same Modbus register address, but with a different bitmask value applied prior to evaluating the value. For example: Read Modbus Holding Register 40123 with a value of 32769 (16-bit unsigned) and decode bits 0, 8, and 15 as three separate Digital points Since the actual Value of 32769 being read at address 40123 is shown in Binary as 1000000000000001 it can be seen that Bit 0 and Bit 15 should return TRUE while Bit 8 should return FALSE Configure each point as follows: Modbus Digital Input Point 40123 bit 0 Register number 123 Register type 16 bit unsigned Read function code 03 Bit mask - enable only Bit 0   Modbus Digital Input Point 40123 bit 8 Register number 123 Register type 16 bit unsigned Read function code 03 Bit mask - enable only Bit 8   Modbus Digital Input Point 40123 bit 15 Register number 123 Register type 16 bit unsigned Read function code 03 Bit mask - enable only Bit 15   Additional information can be found in the EcoStruxure Building Operation - Technical Reference Guide - Search for Bitmask.   If you need to break this bit information out for programming this can be done with a FB application and just binding the full 16 bits to the FB as shown here.

Issue Some sensors such as the SCR110-H CO2 produce a noisy signal even when wired according to the documented instructions. The following is a trend chart of the unfiltered raw signal from the sensor. Environment Automation Server Continuum controllers TAC Xenta Cause Noisy signal is typically caused by common ground wiring of AC power. Resolution SOLUTION #1 Signal noise can usually be eliminated by using an isolated transformer to power the sensor separately as opposed to using a common transformer that powers up several pieces of equipment. SOLUTION #2 For sensors that support  AC and DC input voltage, signal noise can usually be eliminated by using DC instead of AC power source to power the sensor. SOLUTION #3 Implement a Slew Rate to filter out the noise. As of version 1.7.1, StruxureWare Building Operation does not have a built-in slew rate functionality. Nevertheless, a custom slew rate can be implemented using Script programming. See HowToDebounceANoisySensorSignal.pdf SOLUTION #4 Add a filter (FILT) in a Function Block program after the signal input Description: The function block is a discrete time first order software filter. The filter time constant is specified in seconds with the Time Const parameter. The initial block output value is zero. The filter algorithm is y(k) = y(k-1) + 1 / 1+T/h (u(k)-y(k-1)) where y(k) and u(k) are the filtered and unfiltered values at time k, respectively,h is the sampling interval (i.e. the application program cycle time), and T is the filter time constant. If the time constant is less than or equal to zero, no filtering is done. To obtain a good filter function, the time constant should be set significantly greater than the application program cycle time. This filter algorithm is based on a straightforward backward difference approximation of the continuous time derivative operator. SOLUTION #5 Ensure you are not using older versions of the IO Firmware. As detailed in TPA-SBO-17-0006.00 the firmware should be at least V2.015 in the modules and is available on the Download Center.

Issue Need the pinout for the righthand side connector on the PS-24 to troubleshoot. it. Environment PS-24, AS, IO Modules Cause PS-24 had failed with no output to the AS and IO Modules. The pinout for the PS-24 is not documented so was unsure if it was the PS-24 or the AS that failed. Resolution The top row left and second row left are nominal +24VDC and the top row right and second row right are -24VDC. See also Automation Server Family Hardware Reference Guide p/n 04-13001-03-en, page 33 for more information.  

Issue The process of acquiring a license Entitlement ID and how to activate, release and/or transfer a license in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Enterprise Server Building Operation WorkStation Cause There are two different ways to activate a license and different types of licenses that can be purchased. Resolution This article discusses Building Operation Software licenses applied to software platforms such as EC, ES, and Workstation. For details on applying licenses on SmartX Server devices, refer to the Automation Server Licensing Workflow Webhelp topic and/or the Offline activation of embedded licenses Knowledge Base article.   Purchasing a License The licenses that can be purchased are listed in the Part Number Summary. After an order is placed, you will receive an email with an Entitlement ID certificate attached. For further details, see the Order Information Request Webhelp topic.   Evaluation Licenses Evaluation licenses are used for demonstration purposes, training, or site engineering. The evaluation license is a file that can be downloaded from the Exchange and is valid for up to 3 months. Refer to the Activating an EcoStruxure Building Operation Demo License webhelp topic for the activation process.   Activating an Entitlement ID Entitlements can be activated online or offline; however, the online method is far simpler and is preferred. The online method requires the computer that the License Administrator resides on have an internet connection. Online Activation If the computer that the License Administrator is installed on has an internet connection, then refer to the Activating EcoStruxure Building Operation Software Licenses Webhelp topic for the activation process. Offline Activation If the computer that the License Administrator is installed on does not have an internet connection and one can not be temporarily arranged, then refer to the License activation or repair without Internet access Knowledge base article. Once a license file or Entitlement ID has been activated, and the Status reads "Valid" in the License Administrator, the activation process has been completed. The license does not need to be re-hosted after an upgrade and will remain on the computer if the Building Operation Software is uninstalled and reinstalled. To check the status of the license server and licenses that have been activated on the local machine, the Flexnet License Administrator can be accessed by navigating to localhost:8888 in a web browser. The licensing system is the same as used in TAC Vista, which can be seen in License troubleshooting in Vista 5.1.8 or greater.   Returning an Entitlement ID License If the computer on which the License Administrator is being replaced, or it has major operating system changes. In that case, licenses may become invalid and should be returned before those changes. Entitlements can be returned online or offline; however, the online method is far simpler and is preferred. The online method requires the computer that the License Administrator resides on have an internet connection. Online License Return If the computer that the License Administrator is installed on has an internet connection, then refer to the Returning an EcoStruxure Building Operation Software License Webhelp topic for the return process. Offline License return If the computer that the License Administrator is installed on does not have an internet connection and one can not be temporarily arranged, then refer to the License activation or repair without Internet access Knowledge base article. Transferring an Entitlement ID License There is no separate process when transferring a license from one system to another.  Simply return the License from the current system as indicated above and then check that the available seat count has increased by one via the original Entitlement ID. Once returned, activate this same License on the new system as detailed earlier.   Note: Releasing and reactivating licenses can only be carried out a finite number of times per year (4 license returns each year) to prevent misuse of the licensing system.

Issue How to transfer data from TAC Vista to EBO(EcoStruxure Building Operation) as a temporarily solution while a transition between TAC Vista and EBO is done?    Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure Solution EcoStruxure Web Services TAC Vista SmartStruxure Interface 1.5 Cause If EBO need data from TAC Vista during a transition period the TAC Vista SmartStruxure interface can be used.   Resolution Please see the video or follow the instructions below:   On the Vista server(s) install the TAC Vista SmartStruxure Interface first. Refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if there are any issues installing or getting the two programs to communicate when on the same PC. In StruxureWare Workstation, on the Enterprise server object or the Automation server object right click and create new interface, and select the EcoStruxure Web Service interface in Workstation. Click next. In the Server, enter the IP address of Vista server. If it is local, just use localhost. Enter the username and password of Vista Server. Pay attention that only the user in the default System user group can be used. Don't try to create other System group. And all the letters in the password field need to be in capital letters. This is a defect that will be addressed in the next release of TAC Vista to SmartStruxure interface. Please be selective with the port that you are using. If the Vista to SmartStruxure Interface program is on the same PC as the Enterprise server than a different port other than 80 or 443 will have to be used. Please refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if the two softwares need to be on the same machine. Click Create. The next step is to Host TAC Vista objects into SmartStruxure. Refer to How to host TAC Vista objects using Web Services in StruxureWare Building Operation for the guide of how to host Vista objects into SmartStruxure. NOTE: There is a defect for Version 1.0 of TAC Vista to SmartStruxure interface under Non-English operation system. The EcoStruxure Web Services interface will not come online in SmartStruxure. Refer to TAC Vista to SmartStruxure Interface does not connect in non-English Operation System for solution.