Building Automation Knowledge Base

Issue The Pelco Endura system with cameras at a location and integrating with the TAC I/NET Seven system. Product Line TAC INET Environment Check the system requirements for the version of TAC I/NET Seven and Pelco Endura  Cause Configuration requirements of the Pelco Endura and TAC I/NET Seven are specific for the functionality in I/NET. Resolution Once your Pelco Endura system is configured and the Workstation has discovered all the devices and the System Manager is online with the cameras correctly configured, there are four basic requirements to connect TAC I/NET. Cameras have to have a unique friendly name other than default. Cameras have to have a unique camera number. Netframework 3.5 has to be installed. Windows Media Player 11 has to be installed.   If using I/NET Seven Release 2.40a then the following applies: Once INET and the requirements above are installed the Endura Install can be run. The installer for these files is located on the INET CD in the folder: Support\EnduraSDK. Note: Endura video does NOT work on Windows Vista or Windows 7.   If using I/NET Seven Release 2.40 or above: Dual NIC support is now available. For Endura, 100GB NIC and Router are suggested. 1 for I/O Server, 1  for video   Equipment used: NSMS200 Pelco Endura Network System Manager & Network Video Manager SM5000 Pelco Endura System Manager WS5070 Pelco Endura Workstation with Advanced Management Software WS5000 Pelco Endura Work Station Software package NET5301T Pelco Endura Video Encoder Spectra IV Pelco Camera Visit Pelco.com for more information. Click here to view an extended compatibility matrix for Endura and I/NET.

Issue The SX-KLCS Keypad is offline in the Client and shows ' Keypad 256 error address size' on screen If you attempt to adjust the Keypad Address in the Client it is not even visible Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS-B, SX-KLCS-W Cause SX-KLCS Keypads are normally delivered brand new to site with a default Keypad Address of 256 which the SP-C controllers cannot use and the Security Expert Client cannot even recognize to change the address via software Resolution The Keypad's address must be manually changed to a value between 1 - 254 using its touch pad. Keypad Address   Please refer to the full SX-KLCS_Security_Expert_Touch_Sense_LCD_Keypad_Installation_Manual from which this extract was taken.   Once the Keypad Address has been set to a value between 1- 254 the Keypad should then be visible to the Client and you should be able to bring it online as usual.       The SX-KLCS Keypad will now display 'Security Expert by Schneider' by default.

Issue If one Input is required to activate an Output and another Input to de-activate the Output, this Output can be defined by Input Types. The below is a simple scenario where when the first Input turns ON the Control Output turns ON, when the second Input turns ON the Control Output turns OFF. In this scenario we are activating a Duress alarm when an Input goes on and resetting that Alarm when the reset Input is triggered. Product Line Security Expert Environment Security Expert SP-C Cause Require detailed instructions on how to program a latching duress alarm scenario. Resolution Objects required:   1x Area - "Duress_Area" 2x Input Types - "Duress Enable", "Duress Reset" 2x Inputs - "VI Duress Trigger", "VI Duress Reset" 1x Output - "VO Duress Alarm"   Note: The above object names are what is used in this example, you can set these to whatever you require.     Instructions:   Creating the Area 1. Navigate to Programming > Areas. Add a new area (Duress Area), set the Entry and Exit Delay Times to 0. All other settings can be left default.   Creating the Input Types 1. Navigate to Programming > Input Types. Create a new Input Type (Duress Enable) 2. Set the Control Output to your Output (VO Duress Alarm). 3. Under Options 1 enable Generate Alarms. 4. Under Options 2 enable Activate Control Output on Alarm . 5. Set any other options that may be required. 6. Create a new Input Type (Duress Reset) and redo steps 2 - 5 above except under Options 2 enable Deactivate Control Output On Alarm.   Configuring the Inputs 1. Navigate to Programming > Inputs select the Input (VI Duress Trigger) and set the following: 2. Set the Area to the Dummy Area (Duress_Area) created earlier. 3. Set the Input Type to the Input Type (Duress Enable). 4. select the Input (VI Duress Reset) and set the following: 5. Set the Area to the Dummy Area (Duress_Area) created earlier. 6. Set the Input Type to the Input Type (Duress Reset).   Testing 1. Arm both portions of the Area 2. Activate the Input (VI Duress Trigger) to confirm Alarm is generated and Output Activates. 3. Activate the Input (VI Duress Reset) to confirm Alarm is generated and Output Deactivates. 

Issue The Drayton Theta YBL3 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBL3 Cause The Drayton Theta YBL3 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL3 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL3 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL3 Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL3 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M7 – M1 made to M7 when YBL3 Fully Closed (24Vac) Terminal M8 – M2 made to M8 when YBL3 Fully Open (24Vac) Where external wiring is connected to YBL3 Transfer Switch Terminals M7 or M8 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here. Where external wiring is connected to YBL3 Terminal M7 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 24Vac power source Terminal S2 (Normally Closed) - connect to 24Vac device previously connected to YBL3 Terminal M7 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M8 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 24Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 24Vac device previously connected to YBL3 Terminal M8   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL3 Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL3 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M7 – M1 made to M7 when YBL3 Fully Closed (24Vac) Terminal M8 – M2 made to M8 when YBL3 Fully Open (24Vac) Where external wiring is connected to YBL3 Transfer Switch Terminals M7 or M8 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here Where external wiring is connected to YBL3 Terminal M7 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 24Vac power source Terminal S2 (Normally Closed) - connect to 24Vac device previously connected to YBL3 Terminal M7 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M8 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 24Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 24Vac device previously connected to YBL3 Terminal M8   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL3 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue The device is applicationless, or is not associated with a program record. (Subsystem:  NS, #5) The target device does not have a valid application loaded. To correct this problem, right-click on the device and select the "Load" option. Then, if necessary, repeat this operation. The device was discovered to be applicationless, or not associated with a program. If you encounter this error, load the application into the device. For host-based nodes, ensure that the host application is running Product Line Other, TAC Vista Environment LNS LonMaker Vista NL220 Cause Interrupting a download can cause the download to fail and render the controller applicationless.  Also, a corrupt Menta file can sometimes successfully download, but cause the controller to go into an applicationless state. Resolution An application must be downloaded through Menta while directly connected to the controller through the RS-232 serial port.  A blank Menta file with just one PVR is sufficient to restore an application to the controller and allow it to be downloaded; however, downloading the actual Menta file is better because it can expose parsing errors in the Menta file that need to be fixed before downloading it through the System Plug-in again. In some cases, an attempt to direct download can not establish communications to the controller and "timeout". In this event, download a new .mot file to the system using the Download Wizard. Instructions are located in Instructions on how to download an .MOT file into a Xenta Programmable controller. If the Download Wizard  is not able to establish communications with the device, the program should first be cleared using a Xenta Hardware Reset Tool. You can make one by following the instructions located in Xenta Controller Will Not Download / How to Clear the Xenta Application. If the Xenta firmware is older than 3.61, the method to clear the Xenta application is to power cycle the controller 10 consecutive times.

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 Email notifications from 3rd party email account such as Gmail, Hotmail, Yahoo SMTP issues Event notification Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with any of the following: AS, ES, Reports Server Cause Sending notifications to Gmail, Yahoo mail, Hotmail, or other outside email account. Wanting to use other SMTP than Schneider Electric E-mail Server: if wanting to setup an ES or AS to send email notifications with third party SMTP, an Exchange server using port 25 supports the notifications. In release 1.7.1 and earlier though Gmail, for example, suggests port 465 and 587, the workstations alarms that the email can not be sent since it cannot connect to email server. The problem is with the Gmail-account and often other 3rd party email providers both public and private, Google requires that you connect with SSL, which have been missing in the requirements and therefore these releases do not have this functionality. In release 1.8.1 and later, you can send emails not encrypted or encrypted using either the TSL or the SSL protocol. You can select one method for the primary email server and another method for the secondary email server. The Schneider Electric Email Server does not support encrypted emails. When logging on to the email server, the user is authenticated using an authentication protocol. If no user name is specified, no authentication protocol is specified. If a user name is specified, the SmartStruxure server tries to authorize the user using the CRAM-MD5 protocol. If the first authentication fails, the SmartStruxure server tries to authorize the user using the LOGIN protocol using the CRAM-MD5 protocol. Resolution In Email Notification put the 3rd party email address such as yourname@mailprovider.com. AS and ES will use the Schneider Electric SMTP server or the POP server of your choice to send the email notification. For multiple emails, check Multiple Email Addresses for Email Notifications or Alarm Recipients. Sometimes the mail is put in the Spam folder for the recipient. Check there and change settings to Not Spam. Installing a valid SSL certificate for the Enterprise Server to allow SSL operation is not planned in a future version. Currently, the default certificate does not identify the system and is not trusted, but nevertheless enables SSL operation. ESMTP (Extended) is not supported through current release. Base64 SMTP authentication is not supported. Wanting to use SMTP other than Schneider Electric E-mail Server: An Exchange server or SMTP server which supports POP and uses port 25 supports AS and ES Notifications. Other servers which would require the setting of Primary/Secondary E-mail server fails to login to SMTP Server require an encrypted (SSL/TLS) connection which is not supported in Struxureware Building Operation versions up to and including 1.7.1. A solution is to use an SMTP proxy on the ES or another computer on the network that will handle the TLS/SSL authentication. Release 1.8.1 and later support TLS and SSL for email authentication natively. Using SmtpProxy on an Enterprise Server SmtpProxy is a small freeware application that listens on a port you choose; the default port is 25. When SmtpProxy detects a connection on this port, it does the following: Connects to the SMTP server you configure (GMail / Microsoft Live Mail / any other SMTP server) Starts an encrypted connection with the SMTP server Returns the connection information to the ES After the initial connection is established, SmtpProxy acts as a middleman. Any SMTP data received from the ES is forwarded to the SMTP server and any data returned from the SMTP server is sent the ES. SmptProxy runs as a Windows service so it can be installed on a LAN server and used by multiple devices such as AS. Note that SmtpProxy does NOT login to the SMTP server but rather credentials are passed through from the ES or AS. Note: SmtpProxy is a third party application and therefore no support is provided by Schneider Electric. Installing SmtpProxy SMTPProxy can be downloaded from http://smtpproxy.codeplex.com/ The download is a Windows Installer (MSI) file that can be used to install SmtpProxy on any machine that supports the .NET Framework v4 – Client Profile. Configuring SMTPProxy for Gmail SmtpProxy is configured using a config file. A sample config file is installed with SmtpProxy, this is a plain text file that can be edited with Notepad. Create a copy of the sample config file and rename it to: On 32 bit machines: C:\Program Files\SmtpProxy\SmtpProxy.exe.config On 64 bit machines: C:\Program Files (x86)\SmtpProxy\SmtpProxy.exe.config The following items can be configured with SmtpProxy’s config file: SmtpProxy can write a log of all its activities. The default file to write the log file to is SmtpProxy.trace.log. SmtpProxy can log several different types of activities. You can control what is written to the log file by setting the log switches. By default, they are set to Off so nothing is written to the log file. Valid switch values are Off, Error, Warning, Info, and Verbose with each one providing more information than the last. Once you have SmtpProxy working, you should turn logging Off. The Url to the SMTP server. Default is smtp.live.com. The SMTP server port. Default is 587. The port to listen on. Default is 25. Scroll to the end of the config file and locate the section SmtpProxy.Properties.Settings section and find the string mail.live.com Edit this to smtp.gmail.com After modification, you must restart the Smtp Proxy service from the services control panel for the new settings to take effect. Configuring ES to use SmtpProxy Right click on the Server in the tree and select Properties then click the Email tab Select Primary/Secondary E-Mail Server Enter Sender E-mail (e.g. Mysite@gmail.com) Under Primary E-Mail Server Settings enter Host: localhost (or 127.0.0.1) Enter the users account information. User name: e.g. gmailaccountname@gmail.com Password: MyPassword Confirm: MyP

Issue Security Expert Client crashes when attempting to browse to the Status Page Editor. Unable to create Status Pages for system monitoring. When viewing Status Pages none are shown and the word "Frame" is displayed in the view. Product Line EcoStruxure Security Expert Environment Security Expert Client Status Pages Cause The problem is due to the site database not containing the default id=0 objects.  As there is no id=0 Status Page for your site, the Client crashes when browsing to Monitoring | Setup | Status Page Editor.  This can occur when the original 'default controller' is not created during initial Site configuration. A number of default objects are also created as well as the first controller. If you look at the site database, you will also find that it does not contain any id=0 Event Filters or Actions which means that no events will be logged either. Status Page Resolution There are two options to resolve these missing default records: Start with a new Security Expert database and ensure that when creating your Site that the first 'default controller' is created with the Controller Wizard (when prompted). At the end of this process, the default id=0 site objects will also be created. Raise a case with Product Support to arrange for a remote connection.  PSS engineers will then attempt to create the missing id=0 records retrospectively. The site's SSN may need to be provided.. 

Issue We cannot get a SE8000 / SE7000 Room Controller’s occupancy command to follow the MPM’s schedule.   The controller’s display always displays unoccupied even when the schedule is set to occupied.    Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 SSL SE7000 SSL MPM Cause When the MPM's scheduler is in "unoccupied" mode (outside business hours), the default value is 0. However, that does not match any of the values of the "Occupancy cmd" parameter in the Room Controller Resolution The "Default Value" in the MPM's Scheduler object SCH1 must be changed to "3" to match the unoccupied value in the Room Controller. The Occupancy command point for each Room controller must also be ticked in the points list in the Scheduler object For SE8000 PIR ready models, set the "Occupancy src" (Occupancy Source) parameter to "Motion" The SE8000 /SE7000 Room Controller will now follow the MPM’s schedule.

Issue Although data is read correctly from the TSI Pressura RPM20 Hospital Room Pressure Monitor when integrated to a SmartStruxure Solution Automation Server, Modbus read errors and framing errors are seen. Product Line EcoStruxure Building Operation Environment SmartStruxure Solution Automation Server SmartStruxure Solution Automation Server Premium Modbus RTU Cause The instruction manual from the manufacturer incorrectly lists  the Modbus communication parameters for the RPM20 as 9600 baud, 8 data bits, 2 stop bits and no parity. Resolution Investigation of the data from the device shows that the Modbus communications parameters are: 9600 baud 8 data bits 1 stop bit No parity Ensure that these parameters are set in the Automation Server Modbus Master Network configuration.

Issue The Drayton Theta YBL1 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBL1 Cause The Drayton Theta YBL1 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1 Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1 Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1 Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue The EWS Interface is working and object status updates show in SBO but no alarms come in. Alarms are being triggered and showing in the Alarms Status Page in Security Expert Client but these same alarms are not showing in SBO. Product Line EcoStruxure Building Operation, Security Expert Environment Struxureware Building Operation Workstation Security Expert EWS SOAP Cause The authentication for the interface is not set up correctly. Resolution In the EWS Configuration Manager set the Authentication to Digest and define the SBO User Name and SBO User Password that the interface will use. These same credentials need to be used in the Web Services Interface when it is setup in SBO.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue V-Box fails to install network interface/Virtual Adapter during Project Configuration Tool Installation. Product Line EcoStruxure Building Operation Other Environment OracleVM VirtualBox (all versions) Project Configuration Tool (all versions) Cause Some security or anti-virus software prevents V-Box from installing virtual adapter during PCT/V-Box installation or prevent PCT from connecting to a virtual adapter.   Example: The anti-virus software can flag V-Box file as possible threat. Resolution Uninstall or Disable security and Anti-virus software. Install PCT. Install or Enable the software after PCT works properly.   NOTE:  You may have to disable and/or completely remove the security software even after PCT is installed and works properly.  Contact your IT group to get assistance with getting exceptions entered to have PCT work correctly in conjunction with your security software.

Issue Moving from SBO 1.9 to EBO 2.0 and above does not allow the Tech Tool to be used on SmartX Displays. Product Line EcoStruxure Building Operation Environment EBO 2.0 Cause The SmartX Display Tech Tool is being discontinued in EBO 2.0 in favour of a completely overhauled Webstation which is now designed for use on Tablets and Smart Phones as well as PCs. Resolution Tablet used here is the T580 First of all, the tablet itself will need to be brought up to Android OS 7 minimum (OS 8 works as well). Depending on how long it has been since the tablet was last connected online, the Android OS may require a number of updates before it reaches Android OS 7. Most importantly, when finished the tablet must have a firmware number ending with T580XXU2BQL1 or above.  (E.g. T580XXU2BQI9 is lower than T580XXU2BQL1). If for some reason this is not the case then please manually update the software instead. Next contact the Schneider Electric Global Expert Support Team, to obtain the latest versions of SmartX Kiosk and AD-Link application. One visible change in the Kiosk is that it now includes a Chrome shortcut as standard. The AD-Link is still required to establish the connection between the Tablet and the SmartX Server over USB using IP address 192.168.42.116. It is only the Tech Tool itself, that is discontinued. Once the AD-Link has been opened and connected, Chrome can then be used to connect to the SmartX Server using the same 192.168.42.116 Address. Successful logon can then be achieved using the same Username and Password as the Tech Tool. The new and improved Webstation interface can be accessed that is optimised for Tablet and Smart Phone screens In some cases, the customer may not want Chrome's open browser interface and may instead wish to lock down the appearance of the browser to be closer to that of the older Tech Tool. If this is the case, please refer to 'Locking Down' Chrome and Webstation in EBO 2.0 for SmartX Displays.

Issue When trying to log into Workstation you get "Access is denied". Environment Vista Workstation Windows 10 (not supported) Cause First verify that the licensing is installed and working properly on the machine. If running Vista on a Windows 10 machine and the message "Access is denied" still appears when logging in to Workstation then there may have been Windows updates applied to the PC causing the issue. Microsoft has identified an issue with their updates and have plans to correct them in future updates.  Note: Windows 10 is not a supported operating system for TAC Vista.  Resolution If using Windows 10 with TAC Vista, then check to make sure that the following updates have not been installed (updates depend on the Windows 10 build being used).  If one of these builds have been identified then remove the Windows Update and restart the PC. After the reboot, the operator should now be able to log in to Workstation.   Windows 10 1709: KB4056892 Windows 10 1703: KB4056891 Windows 10 1607: KB4056890 Windows 10 1511: KB4056888 Windows 10 1507: KB4056893   Note: There has been a couple of instances where the Windows Upload and blocked access on a Window 8 PC as well.  If the same error is seen in Windows 8 then check for recent Windows updates. Click Here if you are having issues with the updates coming back.

Issue During installation of the Keeps software an exception is thrown in ExtentPlaceholderCreator. Environment Keeps On Premise Cause Microsoft SQL Server issue. Problem has been seen with MS SQL SERVER EXPRESS 2012 SP3 Resolution Edit the 'c:\Websites\Feenics\'web.config' file and insert the text below at the exact location shown in the screen shot below. --INSERT THIS TEXT <dependentAssembly> <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" /> <bindingRedirect oldVersion="1.0.0.0-11.0.0.0" newVersion="10.0.0.0" /> </dependentAssembly> --END OF INSERT TEXT                                                    

Issue Why does the PID example function in the Script editor library not operate like the bPID? Product Line Andover Continuum, EcoStruxure Building Operation Environment Script/ Plain English differences Cause PID example does not operate as expected with regard to the integral action. Resolution The Script Program editor contains various library functions that can be selected from the "Library" tab at the lower right of the editor screen. Plain English program/ function examples were available and used in Continuum and known as the "Andover Controls Standard Modules" ACSM, they are available in Where can I obtain standard Plain English example functions? This document also contains further information about the PID use and application. In both the script PIDLoop (Long version) library function and the bPID function as used in Andover Continuum the Proportional component is the same, they both use Proportional Gain which is defined as 1 / Proportional Band. In the Script Editor Library PID function this requires the Integral Gain constant, this is defined as 1 / Integral Action Time as used in the Continuum bPID function. In the Script Editor Library PID function this requires the Derivative Gain constant, this is defined as 1 / Derivative Action Time as used in the Continuum bPID function. Either of the functions may be used in the SmartStruxure Script editor, but you need to ensure your calling program is passing the correct arguments for the PID function used.

Issue Changing the BACnet MAC address of the Multical meters Product Line Field Devices Environment Multical 601/602 with BACnet MS/TP module Cause The default BACnet MAC address of the BACnet MS/TP module has to be changed for BACnet integration to a BMS system Resolution Requires the USB Optical Eye tool (part number: MAOPTICUSB) and the software tools of the METERTOOL HCW or the Module Programmer. Both the METERTOOL HCW and the Module Programmer can be used to change the BACnet MAC address. The METERTOOL HCW is a program that installs SQL Server whilst the Module Programmer is a simple and lite program with limited functionality. So for the purpose of changing the BACnet MAC address, the procedure to change the BACnet MAC address using the Module Programmer is shown in this article.  Install the USB drivers for the USB Optical Eye tool before connecting the tool to the laptop for the first time. The Module Programmer software must be installed after the Optical Eye hardware has been recognised by the computer. Remove the protective magnet from the Optical Eye and place on the front of the meter that we want to change. The Optical Eye sits over the bottom left corner where the small window is, resting on the 2 nipples, magnetically held. Launch the Module Programmer software. If not already shown, select the Com port which says Kamstrup USB Controller. Press the Read button, this should return the Meter Type and Module Placement. If you are using the MULTICAL 602 and have fitted the module into the base of the meter Select the correct Module Type from the drop down list. Here you must select BACnet because this is what you have. Press the same Read button again, it will read out the current setting. This is the MAC address of the meter for the BACnet MS/TP network. If you are using the Schneider Electric AS/AS-P, the number must be less than 127. Use the UP/DOWN arrows to change address value or enter the number in this field manually. Press the Write button to send the new MAC address to the meter. It is best to power cycle the meter after changing any settings with this programmer tool. You can press Reset and prepare for new meter button and repeat the above steps. Read the address to verify that the new setting has been successfully written to the meter. * Contact Product Support for the software and drivers.

Issue Missing DLLs Environment SigmaX Sigma X DLLs DLL MFC71 mfc71u Cause The Microsoft Foundation Class libraries are normally installed as standard on a PC. But most applications these days are .NET. It may be that Windows 7 does not install all the MFC libraries as standard. Resolution Option 1: If the error shown below in Fig1. is displayed, you may be able to correct the problem simply by downloading this zipped file which contains both MFC71.dll and mfc71u.dll. Copy these to your "C:\Windows\System32" directory.   Fig 1. DLL files also available here. Option 2: The libraries can be installed by installing the Microsoft Visual C++ 2005 redistributable library which can be obtained free of charge from Microsoft. Copies are also available as a direct download. Click on the link below for the version required to download from the Microsoft website. Microsoft Visual C++ 2005 Redistributable Package (x86) Microsoft Visual C++ 2005 Redistributable Package (x64) Click on the link below for the version required to download direct from here. Microsoft Visual C++ 2005 Redistributable Package (x86) Microsoft Visual C++ 2005 Redistributable Package (x64)

Issue Opening Pinpoint in webClient results in one or all of the following error messages: Unknown error. Server:http://localhost/DNWACServerFactory/WACServerFactory.soap C:\User\SEEB\AppData\Local\Temp\PPxtF\WPPCachw\PinFiles\???.pin contains an invalid path. Runtime Error! C:\Program Files\WebClientPinpoint\WPinpoint.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Product Line Andover Continuum Environment Windows Vista, Windows 7 and Windows Server 2008 Continuum Cyberstation 1.93 Cause This is due to an error in the webclient install guide, page 88, where you are asked to edit the web.config file Resolution Find the web.config file, normally in program files/continuum DNWACServerFactory, the file is called "web" Edit the file with notepad and delete the content Copy the following text in its place and edit the "machine name" to your PC name, in this example the name is "WORKSTATION1" <configuration>          <system.runtime.remoting>                  <application>                          <service>                                 <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap"/>                        </service>                        <channels>                                <channel ref="http" machineName="WORKSTATION1">                                </channel>                        </channels>                 </application>         </system.runtime.remoting>         <system.webServer>                 <security>                         <requestFiltering allowDoubleEscaping="True"/>                 </security>                 <directoryBrowse enabled="true"/>         </system.webServer> </configuration> Save changes to file and restart the PC. webclient and pinpoint should work normally now NOTE: If the "RunTime Error!" occurs on a Client machine and the operating system is Windows 10, download "MSXML 4.0 SP2 Parser and SDK' x86 file from Microsoft. This will resolve the access to the graphics from the client machine. Here is the link: https://www.microsoft.com/en-us/download/details.aspx?id=19662