Building Automation Knowledge Base

Issue Instruction on how to use your Entitlement to rehost Vista 5 License onto a new host computer or dongle. Product Line TAC Vista Environment Vista 5 Dongle Host ID Flexnet Licensing Entitlement Vista Licensing website Cause Limited documentation exists for how to properly rehost a Vista license on the Vista licensing website Resolution NOTE: Please remember that 5.0.X license files are not backwards compatible with versions of Vista 5.1.X. If your current license files are 5.0.X you must install 5.0.3 or earlier to properly rehost your license. Log onto https://schneider-electric.flexnetoperations.com and enter your Entitlement or Activation ID. To obtain an unknown ID, follow instructions in Lost license Entitlement ID Vista 5.x. In the top corner of the Home Page Select LICENSE SUPPORT and List Licenses This Entitlements license(s) will be listed. Select the License you wish to rehost by checking the Tick box located just left of the License. In the Action Menu, Select Rehost. Select Add New Host. From the Server Host Dropdown, select either ETHERNET (MAC address) or VENDOR DEFINED (Dongle) depending on your site. Enter the Mac address or Dongle ID to be used in the textbox *note that a Dongle ID must be entered as "TAC_HL_ID=##########" Select OK The New Server Hosts will now be populated with the correct Host ID. Click Next. Select Verify to verify the Host ID is valid Select Rehost to generate the new License. From the main page, select the License you wish to retrieve by checking the Tickbox located just left of the License. Select View and Save To File or Email license to obtain the .lic file. It may be a good idea to compare the old .lic file with the new .lic file in Notepad to ensure they contain the same features. It is possible that the site license was a combined license generated from multiple Entitlements. If this is the case, repeat the steps above for each Entitlement then follow instructions in Manually Consolidating License Files.

Issue Support for OPC or DDE integration with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The OPC Server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. Resolution Neither the OPC server nor the DDE configuration is supported at this time. There is not currently a roadmap for direct OPC client or server capability within the EcoStruxure Building Operation. To avoid problems with OPC Integration (and lose a project), there are two options for OPC integeration: It is possibe to use a converter to convert OPC to/from one of EBO supported protocols.  For example, use a 3rd party software to translate all the OPC points into BACnet Objects, “OPC Server -> BACnet Server”, or translate all EBO BACnet points to OPC. Perhaps one of the software programs below will be of benefit. Take into consideration what specifically will the ES be doing. If it is exchanging point values then it should work fine. Kepware Matrikon SCADA engine Note: These are 3rd party products that are not supported by Shneider Electric.    Use a SmartConnector Extension to be a middleware between EBO and OPC cilent or server. Check available extenstions at Exchange shop and SmartConnector Server and refer to EBO SmartDriver and Smart Connector KB article for more information.

Issue When trying to activate a license in an AS-P/B the following error message was shown and the activation failed: Online activation: 12:57:24: Executing licensing command 12:57:24: Executing embedded operation: Activate ActivationID: ACT-xxx 12:57:32: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: Z(BACK_OFFICE%DEBACK_OFFICE+']\dBl&%MSM230312018I|B}~%ACT-xxxxx/jlSkkj1%<K!,b7OnpUy7 zqDFG#I$QGGR0:SYWJVGIuW}+iea 0\wR/`;yX'HGX*;;nEl]d0I+nHWh(VD"+a uwpf%XF[N6~!,^?R]y?VPCw\gB{"dSy2K7ph;_=qw.|c]Vp;.nlMbLl-~Z!UY<:=TFZEL~h=\V)>ML)ld0g'PPcjrosy&]p9Y((?II#*B5/U16X;o- 12:57:32: Licensing command completed 12:57:34: Activating licenses failed   Offline activation: 12:56:02: Executing licensing command 12:56:02: Executing embedded operation: ProcessResponseFile ResponseFile: C:\Users\Mitthem\Desktop\Garage\response\xxxxxxx\8ba20b60-b19c-4a5d-8fea-693ef9282c8c.bin 12:56:03: Embedded operation: ProcessResponseFile failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information:  12:56:03: Licensing command completed 12:56:05: Activating licenses failed Product Line  EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Device Administrator (DA)  Embedded Licenses Cause The reason for the issue was that the number of available licenses for activation was 0, but the error message in DA was not indicating that. The Device Administrator (DA) showed that two licenses were available but were out of sync. Resolution When looking at the Entitlement in DA, it had a yellow dot on it, indicating that it was added offline. In DA version 5.0.2 and later, DA contacts the License server directly when adding an Entitlement in prior versions this was done through the AS-P. In DA version 5.0.2 and later, it is enough that the computer where DA is installed has an internet connection when adding an Entitlement online. After upgrading DA to version 5.0.2 and refreshing the Entitlement, the Device Administrator showed the correct number of available licenses.    If upgrading the site to this version is not possible, the Entitlement ID / Activation ID availability and device list can be verified by using the User Portal FlexNet Login (flexnetoperations.com) It is also possible to run Device Administrator version 5.0.2 with the concurrent site version used as long as the Servers are at 4.0.4 and above to check, verify and activate licenses.     Important Note: Device Administrator 5.0.3 and above will NOT support lower-version Automation Servers as 5.0.2 does.  This is due to new features of embedded licenses for servers as well as the handling of servers without internet connections.  In this case, ALL servers must run the same version as the Device Administrator version when handling licenses.         Further information on Automation Server Licensing Overview is available through the online WebHelp.  

Issue Are there any Example Reports for the new native Notification Reports which came out in EBO 3.2 to replace the now deprecated WebReports and Report Server? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause As of EBO 2022 (4.0) WebReports and the Report Server have now been deprecated and replaced by External Log Storage using Postgres SQL and Timescale DB, plus the new native Notification Reports which are now built into EBO 3.2 and above, but there are no examples to help new starters to get going. Resolution A Schneider-Electric Community page has been set up specifically for Notification Report users so that they can share their Reports and collaborate on Reporting ideas: https://community.se.com/t5/EcoStruxure-Building-Operation/Reports-showcase-share-your-reports/m-p/388619#M75732

Issue Scenario 1 Attempting to log in to Web Client you are presented with an error message "Error - SOAP connection failed". SOAP-ERROR: Parsing Schema: can't import schema from   Scenario 2 Upon successfully logging in to Web Client you are presented with "Thank you for logging in" and then immediately presented with another message saying "Log out successful".   This continues in a circuit until it may allow you in but displays a partially populated page with no data showing. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client   Cause The option "Use HTTPS to communicate with SOAP service" was enabled in the Web Client Installation Wizard and antivirus was dropping the connection because of this.   Resolution Uninstall and re-install Web Client without the  "Use HTTPS to communicate with SOAP service" enabled or Browse to the soap.connect.php located at C:\inetpub\wwwroot\SecurityExpertWebClient\include. Edit it using e.g. Notepad and change HTTPS to HTTP and change the port to 8030 so the Web Client uses HTTP to communicate with the SOAP service.

Issue An update from 1.94 to 1.94 SP1 will generate an "Installation error! Microsoft ODBC SQL Server Driver SQL Server Implicit conversion from data type datetime to int is not allowed. Use the CONVERT function to run this query." Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A column in the db doesn't get converted properly SQL Server Implicit conversion from data type datetime to int is not allowed Use the CONVERT function to run this query. Resolution To correct this issue apply the following hotfix AFTER installing 1.94 SP1 but BEFORE running the database update Hotfix for DataBase Update Error

Issue BACnet 3rd party controller will not respond to Find New BACnet Devices (Who-Is/I-Am), so will not come online to Continuum or EBO Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Continuum Cyberstation Continuum bCX4040 (BACnet) Cause BACnet MSTP device can be master or slave. BACnet MSTP slave will only respond to a request from a master device, and will not respond to the Who-Is broadcast so it can not be discovered. EBO: EBO does not support slave devices. EBO does not currently have a way to statically configure MAC addresses as it relies on dynamic discovery.   Continuum: Slave only devices cannot come online. Resolution Check 3rd party device documentation or contact 3rd party device vendor for Master/Slave settings and configure for Master to communicate on a MSTP network. Use 3rd party interface to convert to a protocol that can be directly supported by EBO or Continuum. Examples of BACnet MSTP Slaves that are known not to respond to EBO or Continuum Who-Is request and so not come online are: - The Babel Buster 485XM from Control Solutions Inc is BTL listed as a BACnet Slave device , their PICs statement can be seen Here. - Wilo pumps Interface Modules: IF-Modul BACnet & IF-Modul Stratos BACnet, their PICs statement can be seen Here.  

Issue Databases often have to be moved around or upgraded, especially on engineers laptops where they may do offline engineering. What is the best tool to use for this? Product Line Andover Continuum Environment Continuum Single User (Standalone) Version 1.82 and above with SQL Express (2005) Stand alone DB SQL Server Management Studio Express Cause The WinSQL software as used with previous Continuum versions with MSDE (2000) does not operate with SQL2005 and another method of accessing the database is required. Resolution After installing Cyberstation with a blank database and verifying correct operation, the next thing to install is the “SQL Server Management Studio Express” software a free Microsoft download, see link below and use the 32 bit version: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796 This will provide the same user interface as provided on a full SQL2005 installation as used on a LAN system. For Continuum V2.0 and above SQL2012 Express is used, both 32 and 64 bit versions of this are available from the following Micosoft download: http://www.microsoft.com/en-us/download/details.aspx?id=35579 There are 2 methods to transfer your database from one system to another, using a. Backup/ Restore or b. Detach/ Attach, both options are covered below. Alternatively you may already have one or other formats on backup media. To use Backup or Detach you will also need to install SQL Server Management Studio Express as per 1. above on the original computer. Backup Method - you will need to perform a full backup and then restore of the ContinuumDB on the original computer: Using SQLE Management Studio, Right-click on ContinuumDB -> Tasks -> Backup, add a destination where you want to save the .BAK file, Click OK. Detach Method – Detach (or stop the SQL) to allow the files to be copied on the original computer: Using SQLE Management Studio, Right-click on ContinuumDB -> Tasks -> Detach, Click OK. On your new system, make sure you have already created a new ContinuumDB using Database Initialization. If not, do this now - this creates the Database, SQL jobs, stored procedures, adds Andover97 as an admin and a lot of behind the scenes security settings. Stop Cyberstation if it is running. If you are using the Detach / Attach method b. then: Using SQLE Management Studio on the new computer, Right-click on ContinuumDB -> Tasks -> Detach, Click OK. Copy the backed up files to the Data directory your new server. It is advisable to take a copy of the blank database first. Path: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data Using SQL Management Studio, now restore or attach the backed up database depending on which method is being used. Restore Method - Restore the backup over the top of the ContinuumDB on your new system: Right click on ContinuumDB -> Tasks -> Restore -> Database. Select "From device:" and add your Database file, making sure to tick the Restore checkbox to select the source. Next, go to the Options page and select "Overwrite the existing database" and press the "OK" button. Attach Method - Using SQLE Management Studio on the new computer, Right-click on Databases -> Attach, Press “Add” and select the ContinuumDev.mdf file, Press OK. The .mdf and .ldf files will be shown, press OK. The ContinuumDB will appear in the tree. Change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. use ContinuumDB go sp_changedbowner 'Andover97' go Run Database Initialization and update the newly restored database. Using Database Initialization from each Cyberstation, initialize your Workstations into the new Database. Run Cyberstation on all Workstations.

Issue PT1000 temperature sensors RTD Input Product Line EcoStruxure Building Operation Environment AS Classic, ASP  UI16, RTD-DI-16 - Central IO Module ASB, RPC, MPC Need for temperature to be extremely accurate PT1000 platinum resistance thermometer, RTD Resistance Temperature Detector Cause The AS Central IO Module Universal Inputs (UI16) were designed to interface to various thermistors that can have resistance values that are usually much higher than 1000 ohms. They were not designed to interface directly to a PT1000 RTD, and will not provide good accuracy when measuring these lower resistance sensors. The resistance input type was intended to allow for measuring the position of a 10K potentiometer that is used on some wall sensors. The accuracy specification for a resistance input is: +/-(7+0.004*R) ohms. This would result in an error of +/-11 ohms at 1000ohms – therefore a temperature measurement error approaching +/-3.0C. Resolution AS, ASP For RTD PT1000 (Pt100, Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) use RTD-DI-16 - Central IO Module, then choose 2 or 3 wire RTD Temperature Input ASB Choose 2-wire RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) RPC, MPC, MPV Choose RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000)   For more details see SpaceLogic Hardware Reference Guide

Issue The Drayton Theta YBM2 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBM2 Cause The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM2 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM2 Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  The YBM2 Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM2 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Satchwell ZKM series Rotary Actuator requires replacement due to obsolescence. Environment Satchwell ZKM Rotary Actuator installed on Satchwell MBF series Rotary Shoe Valve Body. Satchwell ZKM Rotary Actuator installed on Satchwell MZF series Plug and Seat Valve Body. Cause Obsolescence of Satchwell ZKM series Rotary Actuator Resolution OVERVIEW The Satchwell ZKM Actuator was compatible with both Satchwell MBF series Flanged Rotary Shoe Valve Bodies and Satchwell MZF series Flanged Plug and Seat Valve Bodies, subject to the installation of an appropriate Linkage Kit. Various models of the ZKM Actuator were available, each differing in the number and type of electrical interface provided, enabling the Actuator to be installed in a range of control applications. Interfaces included Transfer Switches, Auxiliary Switches and Feedback Potentiometers, thus resulting in differing wiring connection options between the ZKM Actuator and its associated Controller and other peripherals. Details of the numerous ZKM Actuator variations available may be viewed here. In view of the differing wiring connection options that may be found on site, it is intended to deal only with the most common 6-wire connection option here. Please therefore check the number of wires connected to the ZKM Actuator before proceeding, as this will assist in confirming the suitability of the ZKM Actuator 6-wire connection option replacement suggestion described here.   1. ACTUATOR REPLACEMENT The Actuator comprising a 6 wire electrical connection enabled it to be operated from a Satchwell Z Monotronic or CZT Climatronic Proportional Controller as follows :- Terminal 1 – Open signal Terminal 2 – Close signal Terminal 3 – Common Terminal A – 135 ohm Feedback Potentiometer – winding Terminal B – 135 ohm Feedback Potentiometer – wiper Terminal C – 135 ohm Feedback Potentiometer – winding If all 6 wires are connected then the ZKM Actuator may be replaced either by the Schneider Electric MD20A Actuator or the M800 Actuator, depending on the type of Valve Body to be controlled :- MBF ROTARY SHOE VALVE BODY APPLICATIONS :- MD20A-24 + Linkage Kit LMD-MBF (914-1070-000) Details of the MD20A Actuator may be viewed here Details of the LMD-MBF Linkage Kit may be viewed here N.B. Should the Satchwell ZKM series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E MD20A Actuator as appropriate :- MD-S2 - Two independent SPDT 1mA -- 3(0.5)A, 250 V AC Auxiliary Switches. (914-1061-000) Should the Satchwell ZKM series Actuator include a wired Transfer Switch then the following Accessory should also be installed on the S-E MD20A Actuator as appropriate :- MD-S2 - Two independent SPDT 1mA -- 3(0.5)A, 250 V AC Auxiliary Switches. (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here MZF PLUG AND SEAT VALVE BODY APPLICATIONS :- M800 + Linkage Kit L2SV (880-0124-000) Details of the M800 Actuator may be viewed here Details of the L2SV Linkage Kit may be viewed here N.B. Should the Satchwell ZKM series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :- S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000) Should the Satchwell ZKM series Actuator include a wired Transfer Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :- S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000) Particular care should be taken when selecting an S-E Forta M800 Actuator to replace an existing Satchwell ZKM series Actuator. The S-E Forta M800 Actuator may be used to replace an existing Satchwell ZKM series Actuator but it should be noted that where this is to be connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) compared to that available at the CZT Controller (10VA) will also be required. (e.g. S-E Transformer Type TR60) Details of the Schneider Electric TR60 Transformer may be viewed here In such installations not only will the ZKM need to be replaced but the associated Proportional Controller will also need to be replaced.   2. PROPORTIONAL CONTROLLER REPLACEMENT The ZKM Actuator was compatible with a number of Satchwell Proportional Controller types including Z Monotronic, CZT Series 1 and CZT Series 3 Z MONTRONIC CONTROLLER APPLICATIONS :- If the Proportional Controller is a Z Monotronic type then this should be replaced by the Satchwell CZT5305 Proportional Controller. The associated Satchwell 3 wire Sensor will also need to be replaced by a S-E 2 wire Sensor compatible with the CZT5305 Details of a compatible Room Temperature Sensor may be viewed here. Details of a compatible Duct Temperature Sensor may be viewed here. Details of a compatible Immersion Temperature Sensor may be viewed here. The replacement Immersion Temperature Sensor may be installed in the existing Immersion Temperature Sensor Pocket with the aid of an Adaptor DWA0001. Details of the DWA0001 Adaptor may be viewed here. Details of the CZT5305 may be viewed here.   CZT CONTROLLER APPLICATIONS :- If the Proportional Controller is a CZT Series 1 or CZT Series 3 type then this should be replaced by the Satchwell CZT5305 Proportional Controller. The associated Satchwell 2 wire Sensor may be retained if desired. Details of the CZT5305 may be viewed here.

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue Need to upgrade sites with Report Server to EBO 2022 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher. Resolution Since WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher, there is a Data Migration Assistant (DMA) tool available which read data from a WebReports 3.x and write it to External Log Storage. You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature.  When the External Log Storage feature is activated and configured, WorkStation and WebStation display the historical data in the event and trend views from the External Log Storage. Any server in the system can be configured to write historical data to the TimescaleDB database.   Data Migration Assistant (DMA) Tool can be downloaded from here. License required: External Log Storage requires license, refer to Software and Features that Require Licenses and Part Number Summary and Hardware Software Matrix  Hardware and Software requirement for External Log Storage: Ensure that the hardware and software requirements for TimescaleDB (www.timescale.com) and PostgreSQL (www.postgresql.org) are met. High-performance SSD storage is required and additional CPU/RAM capacity is required for larger EcoStruxure BMSs. As an example, at least 64 GB of RAM is recommended for systems with 100 EcoStruxure BMS servers. Refer to: Information Technology System Planning Guide (se.com) Merging Log data: External Log Storage decreases the amount of extended trend logs retained on the EcoStruxure BMS servers. You can merge log data from an extended trend log to the source log in External Log Storage. For more information, see Merging of Trend Log Data. Enhanced Reporting (XLSX Report Templates): The EcoStruxure BMS servers (3.2 or higher) provide built-in functionality for basic reporting that can deliver reports in any text format and XLSX, without any dependencies to other external software. Reports for XLSX can be enriched by using advanced functionality such as formulas, conditional formatting, charts and sparklines. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there. Refer to: Examples for the new native EBO Notification Reports - Communities (se.com)  

Issue How to associate BACnet IO points created under the BACnet Interface of the Automation Server with IO points on the Automation Server's IO bus. Product Line EcoStruxure Building Operation Environment Building Operation Servers 1.4 and above Building Operation Workstation Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Connect physical IO points to BACnet network controllers. Resolution BACnet Association Tool (EBO V3.0 or higher) BACnet Association Tool will map properties of a central IO point with corresponding properties of a BACnet point. The tool is capable of mapping a single IO point with a single BACnet point, optionally by also creating a BACnet point, and removing the association between IO and BACnet points. To open the BACnet Association Tool, Select the IO Bus or IO Module, BACnet Interface, Application Folder, or the BACnet point, then in the Actions menu, click BACnet Association Tool. Most useful is the ability to associate multiple IO points with their corresponding BACnet points in one operation. The tool can be run from a variety of different container types in the WorkStation Tree view, including an IO point, BACnet Point, CIO Module, or the entire IO Bus (as shown below). For more information refer to WebHelp articles: Creating and Associating BACnet Points to I/O Points (se.com) and Associating or Updating BACnet Point Associations to I/O Points (se.com) NOTE: Please be aware applying the BACnet Association Tool retrospectively, to an already configured site, can remove bindings to outputs.  For example output bindings in Script or Function Block programs.  As shown below, if the tool is used to create a BACnet Associated point for an output already bound to a program (1) the Requested Value will be replaced by the Associated Value of the BACnet point (2). This is due to how the BACnet Association Tool uses the bindings, where the newly created BACnet point should be used instead of the IO point.  The solution is to update the removed program binding (3) to use the BACnet Associated point value (4).   SBO 1.4 to 2.x To associate BACnet IO points created under the BACnet Interface of the Automation Server to points in the IO Bus in SBO 1.4 and above... The association is made via a read reference, so if we think of the two objects as one being the source and the other the destination you configure the association from the destination object so in the case of an output you configure the association from the BACnet object (in this example BO1). In the case of an input, you'd configure the association from the IO Bus input as that would be the destination object, in other words, the recipient of the value. (NOTE: for versions prior to 1.4 see Bacnet and StruxureWare Building Operation Central IO points) Create the points. In this example, we are associating an IO output point named 'Digital Output 1' with a BACnet Binary Output named BO1. From the properties page of the IO Bus point (Digital Output 1 in this example) click on the gear icon to the right of the 'Requested value' field. In the 'Requested value' editor click the navigation icon (...) to the right of the 'Reference' field and navigate to the 'Associated Value' of the BACnet point. Save the configuration changes. Now that the values have been associated setting the BACnet output value (BO1) will drive the IO Bus output (Digital Output 1)  

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 for assistance. Issue Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.    

Issue A site is required to store Extended Trend Log historical data for an extended period of time, in order to make sure the system has enough capacity for all the data  it is necessary to calculate the storage needed ahead of time Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Cause Understanding the storage requirements for long term trend storage Resolution Formula to calculate the storage capacity needed for Extended Trend Log data. Storage in bytes (S)  = Number Of Records (N) x 70 bytes. EXAMPLE: Consider a trend log of 1000 records with a 10-minute interval, if the requirement is to keep 5 years of data, how much storage capacity will be required? The number of records would (N)  be... 6 records per hour times 24 hours per day times 365 days per year*** times 5 years (*** leap years must be taken into account) N =  6 X 24 X 365 X 5 = 262800 bytes This equates to: S = N X 70 S = 262800 X 70 S = 18396000 bytes or approximately 18 megabytes   Note - The calculations above are for the native SQLite database used by EBO. There are two alternatives to using the ES database for long-term trend storage. Report Server - See the WebReports Database Usage Calculator Knowledge base article for storage calculations External Log Storage is possible from EBO v3.0 using TimescaleDB database - The EBO External Log Storage Installer tool from the community provides a databases size estimator located under the Tools menu item

Issue The Niagara G3 platform daemon will not run using an administrator account in Windows. Product Line TAC IA Series Environment Niagara G3 Cause Possible causes: The niagara service is not started IIS is running on the computer Port 3011 is blocked Authentication Resolution There are a number of possible causes: The niagara service is not started. Run Platform Daemon (Start > Programs > Vykon AX Supervisor > Install Platform Daemon) IIS is running on the computer.  Disable IIS in Control Panel > Administrative Tools > Services Port 3011 is blocked. Ensure there are no firewall, antivirus, or remote access software blocking port 3011 There are two types of platform authentication: Basic platform authentication (the default for a Windows-based host) provides integration with existing Windows installations, and provides two levels of platform access, which are determined by a user’s group membership(s). The levels of platform access are: User - Platform access at this level allows full use of most Workbench platform views. This includes the ability to install or delete licenses and stations (including the one running), also to install, reinstall, or upgrade the platform dist file and/or modules, and to start, re-start, or stop a station. Admin - Full access. This includes all user-level platform operations, plus the ability to configure host TCP/IP settings and dial-up configuration, change platform authentication, change platform daemon HTTP port, change host date/time settings, use the File Transfer Client, and reboot the host. Digest platform authentication provides only full level platform login access, using a single platform user account. With Digest platform authentication, there is no linkage between Windows OS user accounts and the platform administrator. If Basic authentication does not work, then Digest authentication must be used. To enable digest authentication, do the following: Using Notepad or WordPad, open the daemon.properties file located in C:\niagara\[release]\daemon folder Add the following lines to the end of the file: installFlag=doc authtype=digest/file user=[username] (where you select the username) password=[password] (where you select the password) stationIsAdmin=true Save, then close the file Restart the platform daemon (Start > Programs > Vykon AX Supervisor > Install Platform Daemon) Launch Workbench AX, then open the platform using the username and password you provided in step 2. Consult the Niagara AX Platform Guide for more information.

Issue GSM modems that can be used with the Remote Alarm Manager. Product Line Satchwell BAS & Sigma,Satchwell MicroNet,TAC Vista Environment Remote Alarm Manager. BAS Sigma Micronet Vista  GSM RAM Siemens TC35i Siemens MC52i Multi-Tech MTCBA-G-F4-GB/IE Cinterion MTX-65+G-V53 Cause Not all GSM modems will allow the full functionality of message acceptance in the Remote Alarm Manager. Resolution The following GSM modems are known to provide the full message acceptance of the Remote Alarm Manager. Siemens TC35i GSM modem terminal. In the Remote Alarm Manager configuration select the C35i driver. This modem is now being replaced be the Cinterion (Siemens) MC52i GSM/GPRS Dual band modem terminal, which has not been tested, but appears to be a direct replacement with added functionality. TC35i GSM/GPRS modem terminal data sheet MC52i GSM/GPRS modem terminal data sheet Multi-Tech MultiModem MTCBA-G-F4-GB/IE modem terminal. In the Remote Alarm Manager configuration select the Brodersen UCM 91/92. This modem is still available, but seems expensive and difficult to source. MultiTech MultiModems MTCBA-G-F4 data sheet Cinterion MTX-65+G-V53 modem terminal.In the Remote Alarm Manager configuration, allow the software to locate the modem and use a generic driver. Cinterion MTX-65+G-V53 modem terminal data sheet   Remote Alarm Manger is no longer a support solution, it is recommended transitioning or upgrading to EcoStruxure Building Operation.

Issue Accessing WebPinpoint graphics from a web browser causes one of the following errors…   Failed CreateDNWACServer. Cause:Object reference not set to an instance of an object. URL:HTTP://eceheatsrvr/DNWACServerFactory DNWACServerFactory /WACServerFactory.soap   Failed creating remote objects. DotNet framework is missing.      Product Line Andover Continuum Environment Continuum webClient Server MicroSoft Windows XP MicroSoft Windows Vista MicroSoft Windows 7 MicroSoft Windows 10 MicroSoft Windows Server 2003 MicroSoft Windows Server 2008 Cause User Account Control redirects files to a different folder than expected by WebClient. User permissions are interfering with the WebClient. A variety of other configuration issues may cause this problem. Resolution User Account Controls Redirection The WebClient installation guide goes into detail about why MicroSoft Windows includes User Account Controls redirection. Follow the procedure outlined below.   Give "Everyone" permissions to the C:\Program Files\Continuum and C:\Program Files\Continuum\DNWACServerFactory folders In Windows Control Panel > User Accounts and Family Safety > User Accounts, select an Administrator user on the PC and select User Account Control Settings. Move the slider all the way to the bottom to Never Notify and select Ok. Follow the instructions in the webClient Installation guide section called "Configuring Graphics for webClient: Windows Server 2008, Windows Vista and Windows 7". Site may be setting User Account Control with group policy and setting it upon reboot of the PC to a setting other than Never notify. A batch file may be used to turn User Account Control off before launching WebClient. A Google search for doing this would be needed and is beyond the scope of this article. Each host that will be running a web browser WebClient session should have also have User Account Control settings set to minimum.       Web.config has not been correctly modified   Using Windows Notepad as an Admin user, modify the web.config file which is located in the c:\program files\continuum\dnwacserverfactory folder. Delete the text and replace with the text below, replacing WORKSTATION1 with the host name of the host computer.  This must be done on all hosts which will run WebClient browser sessions. <configuration> <system.runtime.remoting> <application> <service> <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap" /> </service> <channels> <channel ref="http" machineName="WORKSTATION1"> </channel> </channels> </application> </system.runtime.remoting> <system.webServer> <security> <requestFiltering allowDoubleEscaping="True"/> </security> <directoryBrowse enabled="true" /> </system.webServer> </configuration>     Allow Double Escaping   If for some reason editing this file is still not working. Try the following: In Start >Control Panel > System and Security > Administrative Tools > IIS Manager (Not IIS6) Expand the tree on the left for the webserver name. ie. Webclient1 Expand Sites Expand Default Web Site Click DNWACServerFactory Double Click Request Filtering In the right-hand column select Edit Feature Settings Check Allow Double Escaping and click OK Click on the Default web site and in the far right column click Restart     Test Authentication pass-through for SOAP errors   In IIS Manager; Expand Server> Sites> Default Web Site Left-click on the DNWACServerFactory, on the far right column Select the Basic Settings link Click the Test Settings button. If Authentication pass-through is showing red follow this procedure Click Close Click Connect As> Add a windows user and password that will be used for WebClient Click the Test Settings button Authentication pass through again and it should now show green Perform a local reboot on the WebClient server Test Webclient Graphics     Make sure that the browser PCs are logged in as a Local Administrator for the WebPinpoint and ActiveX installation   Internet Explorer>Tools>Internet Options>Security>(select Zone i.e. TrustedSites)>Custom Level button Make sure that 'Download signed Activex controls' and 'Download unsigned Activex controls is set to prompt or Enable, since the default setting on many web browsers is Disabled.       Add the Webclient PC as a trusted site to the browser PCs   In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. In Internet Explorer: Select Tools > Internet Options > Security > Click Trusted sites > Click Sites Type in http://yourservername/WebClient and click Add (Ex. http://tacweb/WebClient) Deselect the checkbox for Require server verification (https:) for all sites in this zone.  Click OK and then OK again Close Internet Explorer and retry accessing WebPinpoint     Be sure to configure the application pool for 32-bit applications on 64-bit operating systems.   On 64-bit Operating Systems perform the following steps: Open IIS Manager. Expand the computer name in the left-hand pane and click on Application Pools in the system tree view. Select DefaultAppPool and click Advanced Settings. In the Advanced Settings dialog box, change the Enable 32-bit Applications option to True. ** When using 1.94 SP1 and above, check the application pools .net version selected and make sure that the Identity is set to "Network Service" Name                           .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic  4.0 Classic .NET AppPool  2.0 Default AppPool   2.0 WebClient 4.0       DNS issues   Even when you may not be seeing red x’s in Pinpoint View>Options>Web locations and you are able to browse to pin files though IE, WebPinpoint may be giving you a graphic URL error. Try entering using the IP of the WebClient server in place of its DNS name for Pinpoint View>Options>Web locations. Also try using the WebClient Servers IP address in places of the its DNS name and also for accessing WebClient through the browser. For example http://10.159.100.125/WebClient       WebPinpoint fails to register the DNWACClientProxy.dll and tlb files when installed.   On the from the client (web browser) host, perform the steps below:  Close WebClient browser if it is running. Open command line in Administrator mode. Run the batch file C:\Programs Files (x86)\WebClientPinpoint\WPPRegistrationClient.bat     Other items to check:   Disable Windows Defender Turn off all 3 firewalls Shut off SPS software protection service when installing. Run Internet Explorer as an Administrator to make sure the ActiveX controls are being installed

Issue Unable to send out emails using Gmail SMTP server (smtp.gmail.com) with the following error messages in the station's standard output. "javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first." Authentication has been enabled in the system.properties file as per Mail Service in a Niagara R2 UNC station configured correctly but e-mails not being sent to the SMTP server. Product Line TAC IA Series Environment I/A Series R2 Cause As with most public SMTP servers, like Gmail, the outgoing mail SMTP server requires TLS (Transport Layer Security) or SSL (Secure Sockets Layer) which I/A Series R2 does not support. Resolution Use an SMTP server that does not require TLS or SSL.