Building Automation Knowledge Base

Issue The first time a TGML graphic is opened after logging in through Workstation it takes a long time (approximately 30 seconds) before the graphic is shown Product Line TAC Vista Environment Windows Domain TAC Vista .NET Framework Cause This is usually only an issue when the PC has either no or a bad internet connection or is located behind a proxy server. The reason this is happening, is because an application using e.g. signed .NET Framework dll files will check for certificate revocation each time it's launched. That can only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang until a given timeout is reached. The default timeout is 35 (15+20) seconds. For a deep explanation of certificate revocation check and the base of this article, read this article. Resolution There are two solutions that can be implemented. The first is mandatory and the second is optional. The first solution solves the slow TGML opening issue, while the second seems to have a positive overall performance impact but doesn't solve the slow TGML opening issue. A third solution is to get internet connection for the PC, but that is usually not an option. Solution 1 : Lowering the timeout 1. Open the "Local Group Policy Editor" by typing "gpedit.msc" (no quotes) in "Start"->"Search programs and files..." 2. Navigate to "Local Computer Policy"->"Computer Configuration"->"Windows Settings"->Security Settings"->"Public Key Policies" 3. Open the object to the right called "Certificate Path Validation Settings" 4. In the tab "Network Retrieval" check "Define these policy settings" and write 1 in both retrieval timeout settings 5. Click "Apply" and "OK" and close "Local Group Policy Editor"   Solution 2 : Manually installing the newest certificate lists 1. Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl 2. Copy the two files to the PC having the issue 3. Open a command prompt and navigate to the folder where the files are located 4. Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

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 A Schedule or PE program can not change the value of a point because it is set by another process at a higher Command Priority. Product Line Andover Continuum Environment CyberStation bCX4040 B3s Cause Command value must be Relinquished at the priority that no longer needs to control the point's value so that a command with a lower priority can take control of it. Resolution Edit the point from the BACnet view. Go to the Command Priority tab, this tab shows the 16 priorities and their current statuses   Select the priority to relinquish and then click on the Relinquish button. The command with the next highest priority should then immediately take over.

Issue How can objects of a SmartStruxure™ Lite network be made available as BACnet points to third party BACnet building management system (BMS)? Product Line EcoStruxure Building Operation Environment SmartStruxure Lite BACnet Cause The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet and this will need to be changed if BACnet over IP is required. Resolution The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet. To verify or to change which BACnet protocol is currently in use, select the SmartStruxure Lite Manager that you want to configure from the left-side Network panel. Then choose the BACnet configuration list item. Define the Network Number (if the protocol selected is BACnet IP). Note: The Network number must be defined only on the monitor Manager. It shall be different then the Parent Network where the monitor is connected. A BACnet Device is uniquely located by a network number and a MAC address. Creating two or more B/IP networks, each with a unique network number, can be useful for limiting the propagation of local broadcast messages and for providing security by confining traffic to a particular geographic or logical area. Select the desired protocol type from the drop-down list between BACnet IP and BACnet Ethernet. Then choose an optional port number (if the protocol selected is BACnet IP). Default is 47808. Select the BACnet Priority of the BACnet write action of the SmartStruxure™ Lite's network monitor. Default is 10. Note: SmartStruxure™ Lite does not support BACnet Write Priority, per se. However, in Firmware version 2.4.x and newer, it is possible to assign the write priority for all SmartStruxure™ Lite BACnet points. Default value is 10, except if you upgrade a Manager using a version 2.3.x or older, BACnet priority will be 8, but can be changed. Click the Save button to apply the configuration changes. Click hit the Save All button to make the modifications permanent and reboot the Manager for the new options to enter into effect. Change the BACnet instance number of the Manager if required. IMPORTANT Each Manager must have a unique BACnet device instance number. A Manager device instance number can be changed by selecting the top-left icon inside the left-side Network panel.

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed

Issue Netcontroller is running slowly or occasionally goes offline (bCX NC2 ACX CX) Product Line Andover Continuum Environment Continuum Netcontroller, Net Controller, Infinet, MSTP, Bacnet, Xdriver, x-driver Cause There are various reasons why the operation of one or more Netcontrollers and or attached controllers is slow and/or goes offline occasionally.  This guide is primarily to help collate the right information which may identify the issues.  If the reason cannot be identify then this information can be provided to support for further analysis. Resolution General troubleshooting techniques should be used. Define the exact problem. What exactly is slow? eg. Sending to the controller or its connected devices, opening or refreshing graphics, opening or refreshing points, updating Xdriver points, saving programs, creating new points. Is the controller slow from all cyberstations? Is the controller always slow? If not then try to find what makes it go slow, it is time related? Can certain steps be taken to cause the slowness or offline to happen? Get a screen capture of any errors. Gather site information. Continuum version, Continuum hotfixes and service packs applied, number of Cyberstation. Cyberstation operating system, details of Ethernet network and subnets used, with BBMD information of Bacnet sites (Asbuilt or a spreadsheet with IPs, etc.) Continuum Analyzer report, site controller map or spreadsheet or text dump Check the PCs running Cyberstation, do they meet the system specifications? Gather controller information What is the Scan rate? Is the controller time sync. correct? How many objects are on the controller, how many programs are running? What is the firmware version of the netcontroller and b3 or i2 controllers? Ethernet connection - Is the controller on the same subnet as the Cyberstations? A wireshark trace may help to establish the quantity of traffic on the Ethernet (See Using WireShark to analyze communications on an Ethernet network) Comms Ports - XDriver being used? What is on the comms ports? Xdriver (how much communications, points etc) Comms Ports - Bacnet MSTP - How many b3 controllers? How much extended logging? How many alarms being sent? How many 3rd party devices? Look at bacnet settings, how many values are being sent across the network? Check COV settings. Try removing the MSTP cable from the bCX (there could be an issue with an MSTP device causing the bCX to go offline/go slow) Comms Port - Infinet - How many infinet controllers? How much extended logging? How many alarms being sent? Look at infinet settings, how many values are being sent across the network? Check port reconfigs and errors. Try removing the infinet cable from the NetController (there could be an issue with an infinet device causing the NetController to go offline/go slow) Comms Port - other. Again try removing the comms cable from the NetController (there could be an issue with a device on this network causing the NetController to go offline/go slow) Run the Controller error log tool to gather the controller errors See Gather Continuum Controller error logs if requested by Product Support for troubleshooting If the controller goes offline, run the alarm listview.  Does it line up with the Controller error log? Check the CPU LED flash rate on all connected devices (i1, i2, b3 etc) as Can't bring bCX online in Continuum but do get a response to pinging its IP address, also the RD and TD LEDs should be checked for anything unusual This guide is primarily to help the on site engineer by helping them to assess the site. If there is still a need to contact support, please review and record as many items above as possible and send them to the case owner.  Further tests can be carried out including an ACCtrace to determine if the restriction could be at the Cyberstation, See How to capture Continuum Cyberstation activity using ACCTrace NOTE: Ensure all Cyberstations, Controllers and other laptops used for logging are in time synchronization before recording any logs. If it is believed there is an issue with the Infinet or MSTP network see Infinet and mstp bus troubleshooting If it is believed the problem is with extended logging see Extended Logging gaps, performance and load balancing It is possible that something connected to the controller causes the controller to go offline, try disconnecting all other cables and connections to the controller and then re-testing Where a controller is offline when connected directly to a PC/Laptop, try resetting the IP address, otherwise the controller will probably need replacing. NOTE Disconnecting all networks from the NetController is often a good starting point (reconnected IP/Ethernet cable)  

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation, Project Configuration Tool Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a port group or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or port group you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode drop  down menu, click Accept. Note: The setting on the port group overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

Issue Reload of BCX receives error "Infinity controller error: Controller has no assigned Infinet port An error was detected while attempting to set an attribute in a remote Infinity object" Product Line Andover Continuum Environment Continuum Cyberstation BCX 9640 BCX4040 Infinet controller b3 Cause Reloading of a BCX 9640 resulted in error "Infinity controller error: Controller has no assigned Infinet port.  An error was detected while attempting to set an attribute in a remote Infinity object"   Suspected that a learn on the commport was performed or infinet controllers were manually created causing no assigned comm port. Resolution As with any edit of the Continuum system, please make sure to backup the database.   Follow these steps: Send BCX to text file  Add commport to each Infinet controller entry as below Import newly edited text dump file into the BCX. Reload BCX   Example of an original dump file exported in step 1 and the new dump file after the commport is added in step 2. Original Dump File New Dump File Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   SerialNum : 12345   VersionNum : 2.160000  EndObject   Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   Port : comm2   SerialNum : 12345   VersionNum : 2.160000  EndObject  

Issue EcoStruxure Building Operation Demo Database Package Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site Cause EcoStruxure Building Operation Demo Database Package and going between releases. Resolution All current and previous sales packages/demo databases can be found on the Exchange for download. Note: The Demo Database package is a sales and marketing tool for your use "as is." It is not supported through Product Support Services (PSS). If you have product specific technical issues such as installing the software applications (e.g. License Administrator, Enterprise Server) PSS may be able to help. However, PSS does not support the Demo Database contents or features. The Demo Database can be re-installed to return to its original state.

Issue Power cycling the SE8000 room controller will cause the settings to revert to default. This requires reconfiguring each of the parameters once again. Product Line EcoStruxure Building Expert Environment Multi Purpose Manager Automation Server SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause This has to do with BACnet priority; if the configuration was not written with the appropriate priority, the Room controller will overwrite the parameters upon a power cycle and set them to default. Resolution There are a few ways to prevent the SE8000 from reverting to its default settings after a power cycle: Configuring each Room Controller locally by navigating to the configuration menu. (Centralized and Standalone system) Using a LUA4RC script (Centralized and Standalone system) Writing to points with a specific priority via the BACnet front-end (Centralized system) NOTE: Since Zigbee does not have any command prioritization mechanisms, setting the parameters from an MPM via Zigbee will not be retained after a power cycle and is strongly not recommended. All three methods can be used to configure a Room Controller prior to or after its installation. Configuration prior to installation can save a lot of time for the technician on site.     1 - Configuration on SE8000 (Local) Changing the parameters on the SE8000 locally will permanently save the settings and will also allow the user to change the parameters settings locally (e.g. Occupied cooling setpoint). This however can be time consuming.   2 - Configuration via LUA4RC This method is especially useful in standalone applications with no BACnet front end. If there are many parameters that need to be adjusted, it will be quicker to upload the script to each of the Room controllers rather than navigate to each parameter manually. By default, when you assign a value to a BACnet point, the write priority will be priority 16 Example: ME.MV6 = 2 --Set "Network Units" to Imperial (blocked by using priority 16, not user-adjustable) To write to another priority, an array is used Example: ME.MV4_PV[3] = 1            --Language will be blocked by user, room controller and bacnet front-end. Will be saved to memory and will stay after a power cycle NOTE: To release this priority, you can set it to nil (example: ME.AV25_PV[8] = nil). To access the relinquish default, priority 17 can be used Example: ME.MV10_PV[17] = 1    --Set "Occupancy Command" to "Local Occupancy"; here it is mandatory to have (_PV[17]) because thermostat must be able to toggle between "Occupied" and "Unoccupied" temperature Use the script below as a template for your LUA4RC script (remove comments to use less memory) if not init then ME.MV6 = 2           --"Network Units" ME.MV10_PV[17] = 1  --"Occupancy Command"  ME.AV46_PV[17] = 3   --"Standby Temperature Differential" ME.MV5 = 2           -- "Time Format" ME.AV67_PV[17] = 4   --Standby Time ME.AV68_PV[17] = 12  --Unoccupied Time ME.MV46_PV[17] = 3   --UI 16 Configuration ME.MV4_PV[3] = 1     --Language --Add all required configuration parameters init = true end   3 - Configuration Via BACnet: SE8000 parameters can be configured via the BACnet front end by using the following priorities: Priority 2 or 3: Using these priorities will permanently save the setting on the SE8000 and will not allow the user to change the settings locally. Relinquish default: This will allow the user to change the value locally on the SE8000. This is typically used with setpoints NOTE: using Priority 16 will not allow the user to change the value locally on the SE8000, however, the SE8000 will revert to value to default upon a power cycle. Another effective method is to push the configuration to multiple SE8000s across the network using a lua script. See Bulk Lua4RC upload via BACnet (Mass upload).

Issue Various changes to the PC operating system can alter the IA Series software host ID causing the license to be invalid. When this occurs the window below will be displayed providing the new Host ID read from the PC. Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Workbench I/A Series SoftJace platforms    Cause Upgrading the Operating System (Windows, Linux, etc.) always changes the Host ID.  Making other changes to a Niagara host platform may also change the Host ID.  These are the types of changes that can alter the Host ID: upgrading from Windows 7 to Windows 8 upgrading from Windows 8.0 to Windows 8.1 upgrading from Windows 7 or 8 to Windows 10 installing the 2 August 2016 anniversary update to Windows 10 upgrading from RHEL5 to RHEL6 Upgrade from RHEL6 to RHEL7 will change your Host ID. Installing certain Microsoft Windows updates (patches/fixes) may also cause the Host ID to change. Resolution Email the hostID from the current license or a copy of the current license as well as the new hostID provided in the "Request License window" to Schneider Electric Customer Care (Email Information) and request a license replacement.

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 Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue DC1100 / DC1400 Optimiser / Compensator Controller Alarm LED is illuminated. Environment Stand alone discrete Controller in Alarm mode. DC1100 Optimiser / Compensator Controller. DC1400 Optimiser / Compensator Controller. Cause DC1100 / DC1400 Optimiser / Compensator Controller Alarm LED has been triggered by the occurrence of one of the following conditions: Sensor Input is short circuit or open circuit and / or out of range. Boiler Temperature at least 10 deg C above Boiler High Limit value. Boiler Temperature below Boiler Low value after one hour. Compensated Flow Temperature below Flow Low value after one hour. Resolution DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be viewed and / or cleared using the following procedures. VIEW ALARMS DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be viewed as follows :- Turn Front Panel Selector to SET Using Up and Down Arrow Keys move Screen Display Arrows to SYSTEMS MENU Using Up and Down Arrow Keys move Screen Display Arrows to TEMPS & ALARMS Using Up and Down Arrow Keys move Screen Display Arrows to VIEW ALARMS CLEAR ALARMS DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be cleared as follows :- Turn Front Panel Selector to SET Using Up and Down Arrow Keys move Screen Display Arrows to SYSTEMS MENU Using Up and Down Arrow Keys move Screen Display Arrows to TEMPS & ALARMS Using Up and Down Arrow Keys move Screen Display Arrows to CLEAR ALARMS Using Up and Down Arrow Keys Select Pass Number (0112) and ENTER In the event that an Alarm is not cleared by the above procedure and the Alarm LED does not extinguish then the Sensors and / or installation in general should be checked further. DC1100 Optimiser / Compensator Controller overview may be viewed here DC1100 Optimiser / Compensator Controller details and menus may be viewed here DC1400 Optimiser / Compensator Controller overview may be viewed here DC1400 Optimiser / Compensator Controller details and menus may be viewed here

Issue The following error asserts when attempting to convert a Cloudscape database to SQL 2005 in the Niagara R2 console window: java.sql.SQLException: Invalid object name STATION_NAME.dbo.sysobjects'. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:777) at tridium.util.MSSqlServer.doesTableExist(MSSqlServer.java:341) at tridium.util.MSSqlServer.checkTableWithKey(MSSqlServer.java:316) at tridium.datax.sql.DxSqlUtil.checkTableWithKey(DxSqlUtil.java:190) at tridium.datax.sql.DxSqlUtil.checkTable(DxSqlUtil.java:173) at tridium.tools.DbAdmin.migrateData(DbAdmin.java:1007) at tridium.tools.DbAdmin.main(DbAdmin.java:198) at tridium.tools.DbAdmin.main(DbAdmin.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at tridium.nre.Nre.mainImpl(Nre.java:663) at tridium.nre.Nre.main(Nre.java:603) Environment Niagara R2 WorkPlace Pro version 529 and higher Windows SQL 2005 Cause The Enterprise Server and SQL 2005 database names do not match. The Enterprise Server and SQL 2005 database names have to be the same when migrating the Cloudscape database to a SQL 2005 database. Resolution Rename either the Enterprise Server station or SQL Server database so that the names are the same. Once the names are the same, the migration should go without issues.

Issue Site experiencing comm issues on the Infinet or MSTP bus. Controller error logs show many 1465 (Cyclical Redundancy Check) errors. Product Line Andover Continuum Environment Infinet MSTP b3 i2 Controller error log Cause CRC errors are check sum errors. Before a packet is sent, the sending controller calculates a checksum based on the packets contents. This checksum is then appended to the packet. When the packet is delivered, the receiving controller calculates it's own checksum based on the packets contents. If the check sums do not equal, this indicates that somewhere in the delivery process the packet has been altered, usually due to bad cable or connections, controller grounding, or a bad controller transceiver. For additional information on troubleshooting the infinet or mstp bus, see Infinet and MSTP bus troubleshooting. Resolution CRC errors usually indicate poor signal integrity on the physical bus. Infiltration of "noise" on the comm cable due to the presence of high voltage conductors, radio transmissions, etc. In some cases a failed transceiver may be involved but this is generally not the case. Poor controller grounding can also contribute to this issue. Generally CRC errors call for using a scope to assess the signal integrity on a bus.

Issue The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. In cases where multiple BACnet networks containing SE7000 BACnet room controllers are connected to the same BACnet internetwork there could be duplicate ID's when using this schema. In these instances a T7600 Device Configurator Tool can be used to change these fields. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. For example when a VT7200F5000B room controller with a MAC address of 41 is connected to a network, its default Device Name will be VT7200F5x00B-41 and its default Device ID will be 72041. The device ID and name will change as soon as the MAC address is changed at the controller. The MAC address is set in the Installer configuration parameter menu using the Com Addr parameter. These fields can also be set by any BACnet management tool that can access these properties. Resolution The goal of this document is to give simple instructions on how to change the Device Instance of the VT7000 series thermostats using the T7600 Device Configurator tool and the recommended connections and wiring. 1. Converter (can be other models): Model 485OT9Lor USOTL4 from B&B Electronics. A USB-to-RS485 converter, like one used for MSTP captures, will work as well.  2. Recommended wiring for the configuration of Device Instances: The SE7000 room controllers have to be connected only to the converter (which has to be powered up) and disconnected from the network controller. The EOL resistors should remain at both ends of the trunk. 3. Setting up the software The software is supplied as a simple installer file download the software from here and run the installer. Prior to running the program for the first time setup steps 4 and 5 must to be accomplished. 4. Setting Windows Compatibility mode The T7600 Device Configurator Tool is legacy tool and therefore is only supported in a Windows 9X operating system, It has been tested and found to work in later versions of Windows by setting the compatibility mode to Windows 95 Locate the executable file T7600_MSTP_Config.exe in the C:\Program Files\Fastek\T7600 Config\ folder. Right click the file and select properties Go to the compatibility tab and change select Run this program in compatibility mode for: "Windows 95" from the drop down menu then click OK 5. Set the PC communications port Open the BACDOCM.ini located in the C:\Windows folder and enter communications port number in the line highlighted below and save the file. If a valid com port is not entered here the program will generate errors when launched and will not operate. Instructions on how to use the converter (file T7x00 MSTP Config.exe): 1. Open the configuration Tool 2. Double click on the BACDOOR icon in the icon tray on the bottom right of the PC. 3. On the window BACDOOR OEM MSTP Client status, click configure and in the configuration window set the Device instance to any number that does not conflict with any other device instance on the network.: 4. Close the BACDOOR configuration window and in the T7000 Device Configurator, click refresh device list. 6. All the devices on the trunk should appear and you can start changing the device instances one after the other. To do that: a. A- Select the first device.     B- Click Connect to device. The connection process can be long, wait for all the objects to be discovered.     C- change the instance ID using the keyboard.     D- click Apply changes. b. Select the next device and do the same. c. Repeat this action for all the discovered devices. 7. After making all the recommended changes, remove the RS-485 to 232 converter and reconnect the network.

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

Issue When attempting to open the WorkPlace Tech Tool software, a Windows fatal error box is displayed: WptEd has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve WptEd. We will treat this report as confidential and anonymous. Product Line EcoStruxure Building Operation, TAC IA Series Environment WorkPlace Tech Tool software WorkPlace Tech Editor Cause This problem can occur when you use an unsupported version of Visio, such as Visio 2000, prior to starting WorkPlace Tech Editor. Only Visio 2010 SP1, Visio 2007 SP2, and Visio 2003 SP3 can be used with the WorkPlace Tech Tool or WorkPlace Tech Editor. Resolution In the warning message, click [Don't send]. Close Visio. Open Visio 2010 SP1, Visio 2007 SP2 or Visio 2003 SP3.  This causes Windows to initialize and configure that specific version of Visio. When Visio opens, confirm that the selected version opens.  If the wrong version opens, you may need to repair the installation of the selected version. Close Visio. Restart WorkPlace Tech

Issue  Script error when navigating menu in TGML graphic in 1.4. Graphic was working fine in 1.3. Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Automation Server Cause In releases prior to 1.4, graphic objects were not unloaded when navigated away from. This has been fixed in 1.4. As a result of this change, If a TGML has a navigate in a script (by using invoke) this could cause a script error if there are scripts on parent elements. Resolution Open the graphic Navigate to the script and edit, or view in source mode Add evt.stopPropagation(); before the invoke in the Click() function. For an updated version of the component without the error, go to the community: Navigation Menu (JF/Denmark) rev 2.