Building Automation Knowledge Base

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network Cause A better understanding of the I/NET network architecture and communication components can help to avoid the need to troubleshoot issues later. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others including resistor termination. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN Wiring Specifications are available here as a PDF document. Selecting the link Network Definition CLAN SubLAN downloads and opens the pdf document shown below.

Issue How to exchange EBO data via a SmartConnector enabled REST endpoint. 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 Need to serve EBO data in a RESTful manner. Resolution The following video will illustrate how to: Create user account group and user with permissions required for web service client access. Enable the EcoStruxure Web Service server in the EBO server. Create and configure REST endpoint in SmartConnector framework. Use Swagger interface to review the API documentation. Test the Web service using a 3rd party testing tool. Things you need: Software EBO server with valid license (Enterprise Central, Enterprise Server or Automation server) EBO WorkStation. SmartConnector with valid license Tools SoapUI (to be used for testing)   For more information check "SmartConnector RESTful EWS Gateway" document at SmartConnector Server download center, and Troubleshooting Smart Connector SoapEwsRestProvider connection with EBO - Communities (se.com)

Issue Factors to consider using oBIX vs. BACnet IP to exchange data between Niagara R2 and G3 systems Product Line TAC IA Series Environment Niagara R2 version 522 and later Niagara G3 version 3.4 and later Cause Planning factors to consider as to which method is better suited for the customer Resolution Either solution has pros and cons regarding implementation. One needs to think about what fits and how much engineering is required.  If the R2 UNCs (Jaces) are nearly full (CPU and/or memory or less than 40% idle time), then oBIX probably can't be used. It requires some resources to drop in the oBIX service. But if their CPU usage is good (> 40% idle time) and the resource count isn't near the limit, the oBIX service should fit into the UNC. With oBIX, one has access to much more information in the R2 station than with BACnet. BACnet just gives access to its standard objects (BV, BO, AV, AO, etc). oBIX would provide access to just about anything in the station, though some things might be in a string format. One could get trend logs and such using oBIX.  Please also note that R2 oBIX is server only - no R2 "shadow objects" exist to obtain remote oBIX data (e.g. from a G3 station). For additional details, refer to the following documents: Niagara AX-3.x oBIX Guide Niagara R2 to Niagara AX via oBIX Engineering Notes   With BACnet IP, one would need to set all the R2 points 'Foreign Address' field for any point to be available to the G3 station.  Then, configure the G3 BACnet network, and discover the R2 devices and points (Note that if the G3 station is a supervisor, or Enterprise Server, a BACnet license feature with the appropriate number of BACnet points must be purchased).   A G3 supervisor PC should handle 5000 oBIX or BACnet points, provided the station is properly licensed.  

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 What are the basic steps when doing a conversion from TAC Vista to EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Vista Server Cause When doing a conversion from TAC Vista to EcoStruxure Building Operation (EBO), a tool called TAC Vista Conversion tool is used to build the EBO database using an export file from TAC Vista. Resolution This video shows a basic conversion of a TAC Vista database to EBO, and the steps that needs to be taken for a successful conversion.

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

Issue Automation Servers go OFFLINE Alarms received about duplicate device name and/or duplicate network identifier. Product Line EcoStruxure Building Operation Environment Enterprise Server, ES Automation Server, AS, AS-P, AS-B BACnet Cause In the BACnet interface duplicate information has been entered for the BACnet IP network for 2 or more Automation Servers. Resolution Make sure the BACnet IP network and broadcast address in the BACnet interface of the ES and all the Automation Servers  are set to a unique value and they match the IP address of the Server (AS, ES) You may have to physically disconnect the units from the network and then connect one at a time in order for Workstation to be able to communicate with the AS and change the configuration of the BACnet IP network.  

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue Satchwell AR Series 7 Rotary Actuator requires replacement Product Line Field Devices Environment Satchwell AR Series 7 Rotary Actuators installed on Air Dampers, Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Actuator types :- ARE ARM ARX Cause Obsolescence of Satchwell AR Series 7 Rotary Actuators Resolution Replace Satchwell AR Series 7 Rotary Actuators with appropriate Schneider Electric MD Series Rotary Actuators and Linkage Kits selected from the following :- Satchwell AR Series 7 Rotary Actuators installed on Air Dampers. ARE Series 7 = MD20A-24 ARM Series 7 = MD20B-230 ARX Series 7 = MD20B-24 N.B. Schneider Electric MD20 Series Actuators are supplied with a Direct Damper Mounting Kit enabling the Actuator to be installed direct on to an Air Damper Spindle. Should the Actuator be required to operate an Air Damper remotely by means of a Damper Crank Arm and associated Connecting Rod and Universal Connectors, then this may be achieved through the installation of the following Linkage Kit :- ZG-MD20 Damper Linkage Kit (914-1063-000) Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies. ARE Series 7 = MD10A-24 + Linkage Kit 914-1071-000 ARM Series 7 = MD10B-230 + Linkage Kit 914-1071-000 ARX Series 7 = MD10B-24 + Linkage Kit 914-1071-000 N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE Series 7 = MD20A-24 + Linkage Kit 914-1070-000 ARM Series 7 = MD20B-230 + Linkage Kit 914-1070-000 ARX Series 7 = MD20B-24 + Linkage Kit 914-1070-000 N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Product information. For details of MD10A please see here For details of MD10B please see here For details of MD20A please see here For details of MD20B please see here For details of MD-S1 please see here For details of MD-S2 please see here For details of Linkage Kit ZG-MD20 please see here For details of Linkage Kit 914-1070-000 please see here For details of Linkage Kit 914-1071-000 please see here

Issue Common card vendors, types and formats commonly used by Continuum Product Line Andover Continuum Environment Continuum HID Indala Corporate 1000 Cause There is a wide range of card formats available. It's necessary to understand the most commonly used options for Continuum. Resolution Credential Card Format H50932 - Schneider Corporate 1000(35) Format A10202 - Andover 37-bit Wiegand Format 4041X (ASP-ANDINF) - Andover 37-bit Indala Format 40045 (ASP-CSI) - CSI Indala Format Indala Reader Format (FP3511A, FP3521A) 10723 (ASP-ANDINF-1L) - Andover 37-bit Indala Format 1009X (ASP-CSI-2L) - CSI Indala Format 10022 (ASP 26-bit Wiegand-1L) - 26-bit Indala Format HID MultiCLASS Reader (9xx Series) 4041X (ASP-ANDINF) - Andover 37-bit Indalat Format For additional  information on other HID formats, see the following article: Which HID card formats are supported by Continuum?

Issue Sometimes just looking at the error message you get from e.g. TAC Vista or SmartStruxure when you try to send an email and it fails can lack information. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure WireShark Cause It is not necessarily all SMTP error messages and their explanation that are implemented in the software. Resolution For general information on WireShark usage read Using WireShark to analyse communications on an Ethernet network. If McAfee antivirus with HIPS is installed on the PC, use RawCap to capture the communication, as you will not see traffic originating from your PC online in WireShark. Additional reference for this article: Enhanced SMTP status codes   First of all when working with WireShark logs, it's a good idea to filter and focus the communication type you want to look at. In this case it's SMTP, so simply type smtp in the display filter and hit enter.   The easiest way to isolate a single smtp "conversation" between client and server, is to find one of the packets in the conversation, and in the "Analyze" menu click on "Follow TCP Stream".   This will give you the complete conversation in a separate window.   When you have used "Follow TCP Stream" be sure to set the display filter to "smtp" again when closing the window.   This is what happens if authentication is needed by the SMTP server but the client is not using authentication.   Here is the same attempt to send an email, but this time the client has enabled authentication   A little trick when using authentication is that WireShark can actually decrypt the Base64 encoded username and password. Simply right click on any SMTP packet, click "Protocol Preferences" and click "Decrypt AUTH parameters".   He are the packets decrypted   An error not easily detected by e.g. TAC Vista is error 535 "Incorrect authentication data". As stated in the enhanced status code table linked above, it simply means that either username, password or both is incorrect.   Though the product used may not have support for SSL and TLS, you can encounter SMTP server requiring it. Here is an example of a SMTP requesting SSL     For further info on troubleshooting sending emails from TAC Vista, please read Troubleshooting Sending Emails from a Vista Server.

Issue How do I locate the consolidated patch files (modules) for the I/A Series G3 maintenance builds (3.6.406, 3.7.106, 3.8.37).  Please note:  I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center and include all updates for the previous builds. Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.406, 3.7.106, and 3.8.37 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution Please note:  New I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center.  The new builds already include the consolidated patches listed below. Below the latest consolidated patch files for I/A Series G3 maintenance builds 3.6.406, 3.7.106, 3.8.37 are listed.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.406_SE_05272015.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.10 bajaui 3.6.406.3 control 3.6.406.1 docMbus 3.6.406.5 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 kitLon 3.6.406.1 lonworks 3.6.406.5 mbus 3.6.406.5 modbusCore 3.6.406.3 modbusSlave 3.6.406.2 modbusTcp 3.6.406.2 modbusTcpSlave 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 obixDriver 3.6.406.1 opc 3.6.406.1 pdf 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 report 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.9 workbench 3.6.406.3 Consolidated_Patches_3.7.106_SE_07242015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.10 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.3 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5       Consolidated_Patches_3.8.37_SE_07242015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.10 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.39 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.3 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.11 workbench 3.8.38.5 zwave 3.8.38.1   ********* Previous Release History ********* Consolidated_Patches_3.6.406_SE_09112014.zip  ...  Click here for Release Notes alarm 3.6.406.2 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2 Consolidated_Patches_3.6.406_SE_11112014.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2   Consolidated_Patches_3.7.106_SE_09112014.zip   ...  Click here for Release Notes alarm 3.7.106.5 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_11112014.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_01222015.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.14 baja 3.7.106.8 bajaui 3.7.106.5 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 hx 3.7.106.2 kitControl 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.3 mbus 3.7.106.4 modbusCore 3.7.106.1 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.3 weather 3.7.106.1 web 3.7.106.16 workbench 3.7.106.5   Consolidated_Patches_3.7.106_SE_05272015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.9 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5         Consolidated_Patches_3.8.37_SE_09112014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.6 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_10012014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1       Consolidated_Patches_3.8.37_SE_11112014.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.6 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_01222015.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.9 baja 3.8.38.6 bajaui 3.8.38.2 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 hx 3.8.38.3 kitControl 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.3 mbus 3.8.38.4 modbusCore 3.8.38.1 modbusTcp 3.8.38.2 nDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.3 web 3.8.38.7 workbench 3.8.38.2 zwave 3.8.38.1 Consolidated_Patches_3.8.37_SE_05272015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.9 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.38.1 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.2 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.10 workbench 3.8.38.4 zwave 3.8.38.1 bajaui 3.8.38.2 bajaui 3.8.38.2 baja 3.8.38.6 baja 3.8.38.6               obixDriver 3.7.106.4 alarm 3.7.106.5 alarm 3.7.106.5 alarmOrion 3.7.106.2 hx 3.8.38.3 hx 3.8.38.3 hx 3.8.38.3   gx 3.8.38.1 gx 3.8.38.1 gx 3.8.38.1   hx 3.8.38.3   kitLon 3.8.38.1 kitLon 3.8.38.1   nDriver 3.8.38.1   nDriver 3.8.38.1

Issue When accessing an I/A Series R2 or I/A Series G3 station web page, a popup window is displayed warning of a possible security vulnerability. The popup warning is displayed differently depending on the browser version and Java version installed on the computer used for viewing the graphics. -------------------------------------------------------------------------- With Java 7 update 11 or newer, and Internet Explorer 8 or 9, the following popup windows is displayed (location string will vary):   Note that even if you check the "Do not show" checkbox, you will receive additional prompts because the prompt is displayed for each Java applet encountered in the current browsing session.  Likewise, if you close the browser and reopen it, navigating to the same site, the prompts will again be displayed. If accessing I/A Series G3 graphics, the following screen may be displayed: A variant of this message is as follows: --------------------------------------------------------------------------- If using a recent version of the Firefox web browser, the following message is shown in the graphic applet window: "This plugin has security vulnerabilities.  Click here to activate the Java(TM) Platform SE 7 U Plugin."   --------------------------------------------------------------------- When using the Mozilla Firefox browser to access I/A Series G3 graphics, the following security warning may be displayed (Click "I Understand the Risks" and follow prompts to continue):   Environment Windows computer Internet 9 or Firefox web browser Cause Known security vulnerabilities with the Java JRE software Resolution Since the issue is being reported by the Java software or the Java plugin in the browser, there is nothing we can do to directly resolve the issue. There are several workarounds possible, depending on how the site deals with browser security issues. The most secure approach is to allow the applet to be run each time you are prompted. If using Internet Explorer, click the [Run] button on the security warning popup window. If using Firefox, two actions may be needed.  First if the warning "This connection is untrusted" is displayed, click the "I Understand the Risks" Unfortunately, this is a Java issue, not an I/A Series R2 software issue. Oracle has added this popup to its browser plugin to warn the user that a downloaded Java applet may be unsafe to execute. According to information published by Oracle, it may take them up to two years to correct all the known security issues in the Java-JRE. Many of the known issues date back to before Oracle assumed ownership of Java. The only workaround at this time is to downgrade the Java-JRE to a version that does not notify its user that the Java applet to be executed may pose a security risk. We did some testing on Windows 7 with IE9 and found that Java 1.7.0.9 (Java 7 update 9) does not cause the prompt to be displayed. In addition, we found that in some cases we were able to greatly reduce the number of times the prompt appears in Java 1.7.0.17 by setting its security setting to Low (Java control panel applet, Security tab). On one of the virtual machines that we tested this on, the prompt would be displayed the first time you accessed the site and would not be displayed again until you closed the browser and reopened it. On a second computer, the prompt would be displayed each time you accessed a new site or re-opened the connection to the same site but not on multiple screen accesses from the same site. We are not sure at this time why some systems exhibit this different behavior. Note that when using Firefox 19.0.2 and Java 7 update 9 or earlier, a different message is displayed when the web page attempts to open a java window. This window is not displayed when using any version of Java that includes its own security warning popup. The security warning popup I am referring to is the same one displayed when using Java 7 update 17 and other recent versions on Internet Explorer 9 or Firefox 19. This message is designed to notify the user that there is a known security vulnerability with the addon being used, in this case, the out-of-date Java plug-in. There is a workaround published on the mozilla support site that documents a procedure for disabling these warnings when using the earlier versions of Java 7. This workaround does not solve the Java popup warning issue for the Firefox 19.0.2 / Java 1.7 update 17 combination. I did not test it with other combinations other than Firefox 19.0.2 / Java 7 update 9. Here is the configuration change for Firefox 19: Open Firefox Open a New tab Browse to about:config i.e., enter the string in the browser address bar Accept the security warning In the displayed list, right click on extensions.blocklist.enabled In the selection window, click Toggle to change the entry to false Close and reopen the browser. This will disable the security warning for all browser plugin applets, including Java 7 update 11 and earlier, Java 6 Updates 31-38, Adobe Flash Player 10.2.*, 10.3 or 11.0-11.4, Microsoft Silverlight 4.1 and earlier or 5.0/5.1, and about two dozen other plugins that have known security issues. At this time we have not found any workarounds for disabling the Java security warning popup that occurs with Java 7 update 12 and newer with either Internet Explorer or Firefox. As additional information regarding this issue becomes available regarding Java and Internet browser updates, this article will be updated as required.  Depending on site security restrictions, it may be necessary to disable Java when not using it for accessing I/A Series R2 or G3 systems.  See the following instructions from the Java web site: To disable Java - http://java.com/en/download/help/disable_browser.xml To enable Java  - http://java.com/en/download/help/enable_browser.xml In some cases, you may be able to bypass the warning but all your graphics pages do not  load.  This issue is sometimes caused by a security issue with some of the cached java temporary files.  There is a workaround, as follows: In the Windows Control Panel, open the Java applet. Under the "General" tab, "Temporary Internet Files"  section, click [Settings] Uncheck the box "Keep temporary files on my computer" Click [Ok] to save the change then click [OK] to exit the Java control panel.

Issue How to remove unwanted entries from the Alarm log, Access Event log, Error log, and Activity log automatically. Product Line Andover Continuum Environment Continuum SQL Server MSDE, 2000, 2005, 2008 Cause Want to setup automatic truncation of event logs and unsure how to do this in an SQL Server environment. Resolution MSDE Engine For MSDE, you can go to our Exchange online site and download the Standalone MSDE Database Utilities from the Tools, Utilities and Service Packs section of the Continuum part of our Exchange online web site. This is capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc. SQL Server 2000, SQL Server 2005 For full-blown SQL Server, you can easily create a scheduled Job. Details are described below. To create a scheduled Job that will truncate the Continuum logs in the SQL Server: 1. Open up SQL Enterprise Manager. Note that the SQL Server Agent service must be running in order to create a Job. 2. Highlight the Continuum database 3. From the Menu, select Tools \ Job Scheduling A wizard opens; "Welcome to the Create Job Wizard" Hit Next 4. Select Transact-SQL Command 5. Hit Next 6. For the Database Name, select ContinuumDB (or whatever the name of the DB is) 7. In the large white space for the Transact-SQL Command, cut and paste the code from our web site: /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 8. Hit Next 9. On the next screen, you are asked when you do want to run this job. Select "On a recurring basis" and hit the Schedule button. 10. On the Schedule page, set up whatever schedule you desire 11. Hit OK to close the Schedule Page 12. Hit Next 13. On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional 14. Hit Next 15. In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" 16. Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.   SQL Server 2008 1. Run Mgmt Studio and login as sa. 2. Make sure SQL Server Agent is running. Would expect it is by default. 3. Right-click on Jobs (under SQL Server Agent). Select New Job... 4. General tab - Name: TrimLogs // Owner: sa // Category: Database Maintenance // Enabled checkbox 5. Steps tab - New... // Step name: DateDiff // Type Transact-SQL script (T-SQL) // Run as: [null] // Database: ContinuumDB //Command: [pasted in code below]. Press OK. delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90   6. Schedules tab - New... // Name: Weekly // Schedule type: Recurring & Enabled // Occurs: Weekly // Recurs every: 1 week(s) on [whatever date and time]. Press OK. 7. Did not set up Alerts, Notifications or Targets. 8. Press OK. 9. Set it up to run a few minutes after creation. 10. After time passed, opened Mgmt Studio and double-clicked Job Activity Monitor. Saw TrimLogs had successfully run. 11. Ran query: Select count(*) from ActivityEvent to verify count went down.  

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Replace Invensys Actuator Model MA5-419-500-0-3 Environment Damper Control Actuator site Cause Replacement Specifications for Obsolete Invensys MA5-419-500 which is a Two Position Damper Actuator, SR, 240V, 50 Hz, 60 lb-in, w/SPDT Aux. Switch Resolution The closest replacement would be the MD5B-24(-S)/-230(-S) On/Off or 3-point 24 V AC/230 V AC Damper Actuator 5 Nm (45 in-lb). Note: This is a Rockford, Illinois offering, which we would not normally have offered this in Europe in the past. There is a range of Non-Spring Return Damper Actuators detailed in Pages 54 and 55 of the below Schneider Electric Catalogue. Similarly there is a range of Spring Return Damper Actuators detailed in Pages 56 through 58 of the below Schneider Electric Catalogue. Damper Actuator Accessories are shown on Page 59 of the below Schneider Electric Catalogue. Schneider Electric HVAC Valve and Actuator Catalogue  

Issue What is the process to replace a CX9400 with a CX9680 NC2? Product Line Andover Continuum Environment Upgrading a CX9200, CX9400 Eclipse, CX9900, CX9940 to a NCII Netcontroller. CMX9924. Model Number, Type change. Cause Where can I get the process to upgrade my obsolete CX controller. Resolution Cyberstation V1.74 SP2 or above is required to support the upgrading process of a CX9200, CX9900 and CX9940 up to a Netcontroller 2. The upgrade process for this is detailed in Appendix B or the NetController II Operating and Technical Reference Guide. For the CX9400 Eclipse controller they require a minimum of V1.91 to support the upgrade. For the older versions of Cyberstation that do not support direct upgrading of a model number, you will need to bring the Netcontroller II on line as a new controller, then in offline editing copy /paste (or Drag /Drop) all objects over to the Netcontroller II. Then go online and fully reload the Netcontroller II and any connected Infinet controllers. The old controller can then be deleted from the system. The objects could also be copied over using edited ASCII dump files if you prefer that method, but either way you may still have to re-animate your Pinpoint graphics unless you upgrade to a version that supports the Netcontroller II replacement. NOTE ACC-LON RS-485 and ACC-LON FTT-10A protocol options A CX9900 may be labeled CPU-8M and a CX9940 labeled CPU-4M. Later CX99 models may have FT added, eg. CPU-8M-FT When replacing a CX9900 or CX9940 it is vital to know if it requires an RS485 or FTT10 IOU module port (if this port is being used) as this CANNOT be modified on site. See article titled No response from I/O module when learning in an IOU This process cannot be used to upgrade the CMX9924 controllers.  The available range of Netcontroller II controllers available has recently been reduced, see PA-00535 "Andover Continuum Offer Optimization"

Issue How to connect a SpaceLogic IP Controller via MSTP Product Line EcoStruxure Building Operation Environment Workstation Automation Server (ASP/ASB) Space Logic IP Controller RS-485 Adapter Cause Only certain SpaceLogic IP Controller models and versions support the new BACnet MSTP Adaptor and details are required on how to configure these controllers for BACnet MSTP. Resolution The following video will illustrate how to: Configure ASP/ASB for BACnet MSTP Communication. Configure a SpaceLogic IP Controller as a BACnet MSTP device. Discover the SpaceLogic IP Controller on the BACnet MSTP network. Things you need: Software EcoStruxure Building Operation Workstation 2022 Building Commission Application (available from Google Play, Apple Store, or Microsoft Store) Hardware ASP/ASB version 4.0 or higher RP controller (hardware version 10 ) RS-485 Adaptor (Isolating or Non-Isolating) RJ45 UTP Straight Through Cable (12"/300mm or less) Note: - if the RP controller does not show MSTP settings check the Space Logic IP controller firmware release notes and install firmware corresponding to the EBO version.  For example firmware versions 3 and below do not have settings for MSTP configuration. Before attempting to install a SpaceLogic controller on MSTP consult the following: Isolated RS-485 Adapter and Non-isolated RS-485 Adapter for SpaceLogic IP controller types supporting the RS-485 MSTP adapter RP-C BACnet MS/TP Support for RP models supporting BACnet MS/TP Installing an RS-485 Adapter for information on installing the BACnet MSTP adapter Connecting an Isolated RS-485 Adapter and Connecting a Non-isolated RS-485 Adapter for port usage and CAT 5 UTP connection cable Allocating Flexible Ports for additional considerations on port usage Enabling the BACnet/IP Controller to Communicate on an MS/TP Network Please see the video below:

Issue Basic Modbus RTU configuration to read a register from PM800 Power Meter. Product Line EcoStruxure Building Operation Environment Automation Server Modbus RTU PM800 Power Meter Cause Integrate power meters to a Building Operation front end for the user to view data and trend logs. Resolution Here are the steps to Configure a ModBus RTU interface in Building Operation to read the Line Voltage register from a PM800 Power Meter. (Assuming meter has already been properly wired to one of the serial ports on the AS) Create the Modbus Interface, in this case a Modbus Master Network.   Link the interface to a serial port in the AS in the Port Reference field, in this example to RTU device is wired to RS485-COMB   2. Under the interface create the RTU device. In this example the device id is 11, enter the appropriate id for the device. Once the device object is saved, the status should show 'Online' unless there is a communications issue. This is provided you have the online poll interval set. If this is disabled the device will stay offline until a Modbus register is polled and a valid response is received.    You can confirm that Building Operation is able to correctly detect the communications status of the device by disconnecting it from the commport and observing the status change to 'Offline', upon re-connection the status should once again display 'Online'   3. Under the device create a Modbus Point of type AnalogInput to get the value of the Line Voltage from the device. According to the documentation for the PM800 the register holding the line voltage is Function Code 3  and register  1124 The value of the point should now correspond to the line voltage in this case 125 volts.

Issue Need information on how exactly SmartStruxure checks whether BACnet devices are still online or have gone offline. Product Line EcoStruxure Building Operation Environment Enterprise Server - ES Automation Server - AS BACnet devices Cause Understanding how communication status is verified can help with troubleshooting comm loss issues. Resolution After a device is discovered via the WHO-IS/I-AM service and moved into the SmartStruxure database, SmartStruxure uses the following scheme to check on the communication status of the device. For IP Device The server will send a Read Property message to read the devices's system status*** every minute, as long as a reply is received the device is deemed to be ONLINE. If no reply is received by the APDU Timeout the server will retry up to 3 times, if there is no response the device will be considered to be OFFLINE. For MSTP Device The server listens as the token is being passed around the bus and if a device fails to get the token it will be tagged OFFLINE. For both IP and MSTP Device Once the device is tagged OFFLINE, the server will check on the device once a minute by sending a WHO-IS message with the ID of the device, if an I am is received the device will be considered back ONLINE and the ReadProperty 'probe' check (for IP) or token pass check (for MSTP) will resume once a minute. ***In version 1.4 and below the ReadProperty will read the name property of the device. See sample Wireshark capture below, NOTE that in the sample below 10.169.90.31 is the Broadcast address of the sub net where the ES is located. NOTE: For efficiency the BACnet engine may combine the reading of the system status property with other read property requests into a single Read Property Multiple.