Issue The discontinuation of the SVT controller due to component obsolescence. Product Line Field Devices Environment SVT Optimiser 4201 4251 Cause What replacements are available for the SVT 4201 / 4251 controllers? Resolution Important Note - The replacement controller mentioned in this article is no longer available, and therefore a replacement for the SVT 4201 / 4251 is not available. The SVT controller range has been discontinued due to component obsolescence. The SVT controller was a basic optimiser that performed the start calculation using only an internal temperature sensor. There are no exact replacements for this controller available. What is available? The Schneider Electric DC1400 Optimiser / Compensator is the recommended replacement, but this is not a direct replacement. Differences in the controllers. The SVT controller provides only an optimum start, the DC1400 provides optimum start and stop. The SVT controller uses only a room temperature sensor for the start calculation, the DC1400 uses only a room temperature sensor and an outside temperature sensor for the start/stop calculations. The SVT controller has a dedicated "Boost" relay, which allows overriding of a CSC compensator, and control valve. This is an internal function with the DC1400 optimiser/compensator. The DC1400 has many other built in functions.   Controller wiring - Modifications will be required. SVT general wiring connections. Relay R1 is the main plant relay and relay R2 is the boost relay. To see the full controller details, please click SVT Optimiser DS2001 0210.pdf DC1400 general wiring details.   To see the full controller details, please click DC1400 DS2044A.pdf Controller Sensors As already indicated, the SVT controller uses only a space temperature detector, and this sensor is NOT suitable to use with the DC1400. The DC1400 controller will, as a minimum, require a room temperature sensor and an outside temperature sensor, meaning that extra wiring for the outside temperature sensor, and the sensor itself, will need to be installed. For details on suitable sensors, please refer to What sensors does the DC1400 optimiser/compensator require?

Issue Unable to connect to a Link or Site in I/NET Seven. Product Line TAC I/NET Environment I/NET Seven Cause The user interface requires specific steps to initiate a connection, which may not be immediately intuitive without prior experience. Resolution To connect to a device or site in I/NET Seven, follow these steps: From the main menu, select Connect. A summary list of available link devices or sites will be displayed. Note: A dash ( - ) next to a device name indicates it is currently unavailable for communication. An asterisk ( * ) indicates that the controller name or type has changed. Highlight the desired link device or site from the list. Select OK to initiate the connection. Once connected, the status bar at the bottom of the screen will display the connected levels. Warning Important: Ensure that the selected device or site is available and correctly configured before attempting to connect. Misconfigured or unavailable devices may result in failed connections or unexpected behavior.  

Issue Directions on how to commission an SSC and Mercury Controllers right out of the box. Product Line Access Expert Environment Windows 7 Windows 8 Windows Server 2012 Windows Server 2014 Version 2 Version 3 Cause No directions on setting up an SSC and Mercury Controllers to get it online. Resolution Commissioning the AX-SSC Here is a link to a video that describes how this should be done as well that can be accessed from the following link: Commissioning a new SSC 1. Connect the Access Expert Device Administrator to the SSC using USB cable then go to ‘Network settings’ to configure the device’s IP address etc. 2. In the ‘Ethernet 1 Configuration’ tab, configure the IP settings (In this example, we are using a static IP address). Make sure to configure the DNS so that the URL of your hosted instance can be resolved. Take note of the SSC’s MAC address which will have to be entered when adding the SSC in Access Expert. 3. Enable the default user in the SSC in order to be able to login with a web browser to configure additional communication parameters. NOTE: The default user will stay enabled for 5 minutes then the checkbox will automatically deselect. Once logged into the SSC you can create a new level 1 user so you don’t have to rely on the default user again. 4. Point a web browser to the SSC's IP address and login using the default user (admin/password). After logon, verify the IP settings configured from the Device Administrator, you can edit the settings here if necessary. 5. If using a Mercury EP1501 or EP1502 Controller, use the MAC address and connect to the device. Once logged in, go on to the next step 6. Go to the ‘Host Comm’ page. This is where you will configure the SSC to be able to communicate to the Access Expert database instance in the cloud. 7. Configure the connection type for ‘IP Client’. Enter the URL for your DB server instance or the hosted cloud server as shown in the above example. 8. For V3, the Host Name would be us.accessxpert.com (ax.accessxpert.com also works). If premise, then it would be the IP of the Server. 9. Note the port number used for communications and make sure this port is open; you can also configure an alternate host port as a backup. 10. Usually it is 3001, if that is blocked by the clients Network, then use Port 443. 11. Click Accept then ‘Apply Settings’ followed by ‘Apply Settings Reboot’.  

Issue Tips for Configuring HID OSDP Reader LED Colors Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert OSDP Reader Cause Additional tips for configuring OSDP Reader LED Colors Resolution The Configuring LED Colors section of AN-254 Configuring OSDP Readers in Security Expert  details the basic steps for LED configuration. This article details some additional areas of the HID reader setup and Security Expert configuration that may be useful when configuring the LED colors.   Note: The steps in this article are specific to an HID Signo RP10 Reader BLE and may not apply to other HID reader models or other brands of OSDP readers.   Upgrade the Reader firmware to the latest version. Earlier versions of the reader firmware would not correctly allow LED control. The Bluetooth option allows the configuration of the reader using the HID Reader Manager App. For detailed information see HID Reader Manager App Information Note: To use the HID Reader Manager App to configure a reader, the Security Technician or Security Installer needs to create and register an account with HID. The Reader Manager Administrator for your organization or company needs to enroll this new account using the Reader Manager Service and issue an invitation code and key authorization for this and other readers. The Security Technician can then verify the key authorization has been received in the HID Reader Manager app. Detailed instructions for all of this are included in the HID Reader Manager App Information URL listed above.   HID Reader Manager App Firmware snapshots       In the HID Reader Manager App, change the Reader Options for LED color to "Host Controlled" in 2 places. The reader must be controlled by the Security Expert controller. Credential Reader AV LED Idle Color Ensure that the firmware for the following hardware is upgraded to these versions or greater in order for LED Color Output to work. Security Expert 4.3.308.46 SP-C 2.08.1234 MRDM2 1.2.590 In Security Expert the Outputs to control the LEDs need to be manually created. Programming> Outputs> Add A pop-up asking to Invert Output will display, select 'No' when prompted Output 3 (GreenLED Port 1) Output 4 (Red LED Port 1) Output 6 (Green LED Port 2) Output 7 (Red LED Port 2)   Name the Outputs whatever is appropriate Example:  GreenLEDPortON RedLEDPortOff LED Colors The default LEDs are Blue when Idle and Green when active. As an example, the LED colors will be changed to Red when Idle and Green when Active. Color Options:   Set the colors for both Red(idle) and Green(active) in the Security Expert Output Command Window for the newly created outputs RedLEDPortOff   GreenLEDPortOn Update the modules and wait for about 15 seconds before activating the output to test. Just saving the updated command setting doesn't work, the module must be updated.   Activate the GreenLEDPort1 - the color should change to what the output was set to in the command. In this case, green. Deactivate goes back to Off (idle) Red. GreenLEDPort1 = On State RedLEDPort1 = Off State   Note: The Off state if left at the default of Blue can't be used with the On state of custom(non-default). Both Outputs must be specified in the command window for the colors to work together.   Example: If the OFF state is left at the default of blue and the color of the ON state is set in the command window and Activated, the LED color will change to what it is set to(green), but when deactivating the Off(idle) output it will not turn blue.

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue How to add Web Service and create Simple XML Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add XML files and how to add to a project or site How to create values from the XML Files added How to make a graphic that uses the values from XML Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: Are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Weather for a particular location data using Simple XML: Select New > Interface > Web Service > Simple XML Specify the URL for this data (to find the weather for your area, Google XML data Make changes to polling, alarm, retry interval Choose Create Now you can Create a value from that Simple XML Web Service by highlighting and select New > Value > and type of value. Select Analog for temperature, String Value for wind direction and so forth. One can add as many of the values as desired. The Simple XML List View would look like the below screen capture. Lastly for Simple XML Web Service a graphic is created and the values which come from the XML Web Service are place on the page. Also check out the SmartStruxure - Web Services - Simple XML Interface Quick-Help video on the Exchange.

Issue During Continuum installation error comes up that SQLncli_x64.msi file is missing. Microsoft SQL Server 2005 Setup An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli_x64.msi'. Product Line Andover Continuum Environment CyberStation Windows SQL Cause The Microsoft SQL Server Native Client has not been installed. It must be present before installing Continuum software. Resolution Before installing SQL Server, download and install Microsoft SQL Server Native Client x64 file (sqlncli_x64.msi) from Microsoft Download Center: Feature Pack for Microsoft SQL Server 2005.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue BACnet COV subscription system Product Line EcoStruxure Building Operation Environment BACnet Settings COV subscriptions v1.7 and earlier Cause A site will have a problem with the amount of traffic because of misconfigured COV Increments. The problem is that Building Operation, the  ES and AS resubscribes to values every 10 seconds and one by one. So for example: hh:mm:ss 00:00:00 Value1 00:00:10 Value2 00:00:20 Value3 00:00:30 Value4 ... 05:00:00 Value1800 If you have more than 1800 subscriptions the ES or AS is not able to do all subscriptions in 5 hours.   5 hours is used because Building Operation subscribes to the values with a lifetime of 5 hours.   Resolution BACnet COV subscription system is not influenced by the requested transfer rate in the edit bindings system (Subscriptions using BACnet). That is used in the case where the external device does not support COV, and read-property must be used instead. The design in 1.4 and 1.5 simply did not anticipate such large numbers of COV subscriptions. Workaround: 1.Exit Workstation 2. Stop the Enterprise Server Edit using notepad the server.properties file located in "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\ Find at the bottom: # Set GenericConsume communication defaults Add the two following lines: NspServer.BACnetPlugIn.COVSubscriptionLifetime entry = 28800 NspServer.BACnetPlugIn.COVTimerPeriod entry = 5 Save your changes and close the server.properties file. This changes the default values from 5 hours to 8 hours and 10 seconds to 5 seconds. NOTE From version 1.8 the BACnet Interface manager (/Server 1/System/Interface Manager/BACnet) provides access to these settings (COV subscription lifetime (default 8 hours) and Server COV renew rate(default 5 seconds)) The settings will be controlled via the Enterprise Server if connected.

Issue TCONs are listed and available on The Exchange Download Center. This index is meant to provide a quick reference to find the desired TCON even if the number is not known. Product Line TAC INET Environment TCON documents Cause The Exchange Download Center allows for searching by either TCON number, title, or document content. This is a list of those documents with links to the Download Center. Click here to view the complete list in The Exchange Download Center. Resolution TCON069 Unitary Controller (Model 7200 Series Unitary Controllers) Installation Guide TCON073 Model HC7410 Hand-Held Console Installation Guide TCON074 Building Manager Access Instructions Card TCON077 Model 1000 Door Processing Unit (DPU 1000) Installation Guide TCON078 Elevator Control Unit (EVC) Installation Guide TCON079 Remote Dial Tap (RDTAP) Installation Guide TCON082 Discrete Input Unit (DIU 1600) Installation Guide TCON083 The ABC’s of DDC (CSI-1991) TCON084 Docutrend ... the Quick and Easy Way! Reference Guide TCON086 Door Processing Unit 3000 (DPU-3000) Installation Guide TCON087 Fiber Optic Interface (FOI) Installation Guide TCON092 LAN Monitor 1 (LANMON 1) Reference Guide TCON093 Model 7460 Universal Controller Interface (7460 UCI) Installation Guide TCON094 I/NET System 7700 Operator Guide TCON095 7700 DCU Installation Guide TCON096 7716 PCU Installation Guide TCON097 7740 DCU (includes 7741 DCU) Installation Guide TCON098 7750 DCU Building Manager Installation Guide TCON099 7760 Unitary Controller Interface Installation Guide TCON100 7780 Distributed Lighting Control Unit Installation Guide TCON101 Model 7800 Series Taps & Repeater Installation Guide TCON102 7771 Industrial Communication Interface Installation Guide TCON103 I/NET 7700 Icon Editor Reference Guide TCON104 I/NET 7700 Text File Compiler User Guide TCON105 Discrete Input Monitoring and Output Control Unit (DIO-8000) Installation Guide TCON106 7718 PCU Installation Guide TCON109 7790 LAN Interface Unit Installation Guide (7791 DPI, 7792 MRI, 7793 MCI) TCON110 I/DISC Sorting Procedure Reference Guide TCON111 Door Processing Unit (DPU 3100) Installation Guide TCON112 CSI Access Control Readers Installation Guide TCON113 I/STAT & Micro Regulators MR123 Installation Guide TCON114 Model 7728 Series I/SITE I/O Controllers Installation Guide TCON115 Door Processor Unit 7900 (DPU 7900) Installation Guide TCON116 DPU 7910A Installation Guide TCON117 DPU 7920 Installation Guide TCON120 Guidelines for Smoke Control Reference Guide TCON122 Series 7797 Industrial Communication Interface Installation Guide TCON123  I/NET Memory Interface Processor (MIP01) Installation Guide TCON124 DIU 7930 Installation Guide TCON125 DPU 7940 Installation Guide TCON126 I/STAT & Micro Regulator Controller Installation Guide TCON127 7756 PCU Installation Guide TCON130 MR55X and I/STAT Installation Guide TCON135 I/NET Communications Interface for Cerberus Pyrotronics (779703 ICI Cerberus) Installation/Reference Guide TCON136 I/NET Communications Interface for McQuay MicroTech Open Protocol Communications (779704 ICI McQuay) Installation/Reference Guide TCON137 I/NET Communications Interface in Support of YorkTalk XL/LINC Chiller ISN (779705 ICI YorkTalk) Installation/Reference Guide TCON138 7798 I/SITE LAN Installation Guide TCON139 I/NET Communications Interface for Trane (779706) Reference Guide TCON140 I/NET Communications Interface in Support of Notifier AM2020 Fire Detection System (779707 ICI Notifier) Installation/Reference Guide TCON142 I/NET v4.30 System Operator Guide Operator Guide TCON143 I/DISC Fob Installation Guide TCON144 7798 I/SITE LAN Installation Sheet TCON145 I/NET System Technical Reference Guide TCON146 I/NET Communications Interface in Support of Square D PowerLogic Network Interface Module (779708 ICI Square D) Installation/Reference Guide TCON147 ASC-VAV-AX Installation Guide TCON148 ASC-VAV-AX Installation Sheet TCON149 ASC-MR-VAV-Series (AX and X1) Pocket Reference TCON150 I/DISC Reader (IDISCRDRB) Installation Sheet TCON151 I/NET Docutrend Technical Reference Guide TCON152 Video Badging Subsystem (S/90 Integrated Video Badging) Installation Guide TCON153 ASC MR-AHU Installation Guide TCON154 ASC MR-AHU Installation Sheet TCON155 ASC MR-VAV-X1 Installation Guide TCON156 MR-VAV-X1 Installation Sheet TCON157 I/NET System Forms and Worksheets Reference Guide TCON158 ASC MR-AHU Pocket Reference TCON159 I/NET Communications Interface for Edwards Systems Technology Fire System (Model 779711) Installation/Reference Guide TCON160 I/NET v4.x Utilities Software Operator Guide TCON161 ASC MR-HP Installation Guide TCON162 ASC MR-HP Installation Sheet TCON163 ASC MR-HP Pocket Reference TCON164 ASC MR-VAV-X2 Installation Guide TCON165 ASC MR-VAV-X2 Installation Sheet TCON166 ASC MR-VAV-X2 Pocket Reference TCON168 I/NET Video Badging (I/NET VB) Operator Guide TCON169 I/NET ODBC Driver (INETODBC) Technical Reference Guide TCON170 Intellution Driver CSI I/O Driver for the Intellution FIX DMACS Installation Guide TCON171 Door Processor Unit 7920 with Essex PIN Installation Guide TCON172 PWM-C Pulse Width Modulation to Current Transducers Installation Sheet TCON173 PWM-P Pulse Width Modulation to Pressure Transducers Installation Sheet TCON174 PWM-R Pulse Width Modulation to Resistance Installation Sheet TCON175 PWM-V Pulse Width Modulation to Voltage Transducers Installation Sheet TCON176 Model IP Current to Pneumatic Transducer Installation Sheet TCON177 Model ASC1 Analog Signal Converter Installation Sheet TCON178 XFMR Series Transformers TCON179 Model SA1 Surge Arrestor for System 7700 and System 90 Installation Sheet TCON180 UniHub Tutorial (UniHub 2.2) Reference Guide TCON181 I/NET v4.3x Getting Started TCON184 NetPlus Router 2000 Installation Guide TCON185 I/Site LAN Installation Sheet TCON186 I/View Version 1.0 Operator Guide TCON187 UniHub Version 3.1 Technical Reference Guide TCON188 UniHub 3.0 Tutorial Reference Guide TCON189 779712 ICI BACnet Installation Guide/Reference TCON190 7798B1 I/SITE LAN TCON191 NetPlus Router Installation Sheet TCON192 I/NET v4.10 Guide opérateur du système TCON193 Système I/NET Guide de Référence Technique TCON194 I/NET Docutrend Guide de Référence Technique TCON195 I/NET System v4.10 Bedienerhandbuch TCON196 I/NET System Technisches Referenzhandbuch TCON197 I/NET Docutrend Technisches Referenzhandbuch TCON198 I/NET Sistema v4.10 Manual del Operador TCON199 I/NET Sistema v4.10 Manual de Referencia TCON200 I/NET Sistema v4.10 Docutrend Manual de Referencia TCON203 NetPoint VAV (NP-VAV-AX) Installation Guide TCON204 NetPoint VAV-AX Installation Sheet TCON205 NetPoint VAV-AX Pocket Reference Card TCON206 NetPoint™ VAV-AX (NP-VAV-AX) Application Reference Guide TCON207 I/NET 2000 v1.x System Operator Guide TCON209 I/NET 2000 v1.x Technical Reference Guide TCON210 I/NET 2000 v1.x Docutrend Reference Guide TCON211 I/NET 2000 v1.x ODBC Driver (IODBC32 Driver) Technical Reference Guide TCON212 I/NET 2000 v1.x Operator Guide TCON213 I/NET 2000 v1.x Getting Started TCON215 NetPoint General Purpose Unit 506R (NP-506R) Installation Sheet TCON217 I/NET 2000 Troubleshooting Guide TCON218 NetPoint General Purpose Unit 546R (NP-546R) Installation Sheet TCON219 NetPoint General Purpose Unit 1008R (NP-1008R) Installation Sheet TCON220 NetPoint General Purpose Unit 1048R (NP-1048R) Installation Sheet TCON221 NetPoint General Purpose Unit (NP-GPU) Technical Reference Guide TCON222 NetPoint General Purpose Unit 506 (NP-506) Installation Sheet TCON223 NetPoint General Purpose Unit 546 (NP-546) Installation Sheet TCON224 NetPoint General Purpose Unit 1008 (NP-1008) Installation Sheet TCON225 NetPoint General Purpose Unit 1048 (NP-1048) Installation Sheet TCON226 I/NET 2000 Dial Setup Guide TCON227 UniHub Application I/NET Notifier Interface Reference Guide TCON228 I/NET Interface UniHub Application CASI-RUSCO Secure Perfect Reference Guide TCON229 I/NET 2000 v1.x Operator Guide (MTRC) TCON230 I/NET 2000 v1.x Technical Reference Guide (MTRC) TCON231 Smoke Control Systems Manual TCON236 I/NET 2000 v2.x Operator Guide TCON237 I/NET 2000 v2.x Technical Reference Guide TCON238 I/NET 2000 v2.x Getting Started TCON238A I/NET 2000 Revision 2.10 Addendum TCON239 I/NET 2000 v2.x Docutrend Reference Guide TCON240 I/NET 2000 v2.x ODBC Driver Technical Reference Guide (IODBC32 Driver) TCON241 I/NET 2000 v2.x Utilities Operator Guide TCON242 7716-U8 Smoke Control Data Sheet TCON243 7756-U8 Smoke Control Data Sheet TCON244 7771-U8 Smoke Control Data Sheet TCON245 B7771 U8 Smoke Control Data Sheet TCON246 7790A-U8 Smoke Control Data Sheet TCON247 7797-12-U8 Smoke Control Data Sheet TCON248 7798B-U8 Smoke Control Data Sheet TCON250 FSCS-1-xxxxx-U8 Smoke Control Data Sheet TCON251 FOI1-U8/FOI2-U8 Smoke Control Data Sheet TCON252 20010-U8 & 20020-U8 Smoke Control Data Sheet TCON254 MR88R-U8 Smoke Control Data Sheet TCON255 MR88-U8 Smoke Control Data Sheet TCON256 MR632-U8 Smoke Control Data Sheet TCON257 MR55-U8 Smoke Control Data Sheet TCON258 MR55X-U8 Smoke Control Data Sheet TCON259 MR160-U8 Smoke Control Data Sheet TCON261 MR-HP-U8 Smoke Control Data Sheet TCON262 MR-VAV-AX-U8 Smoke Control Data Sheet TCON263 MR-VAV-X1-U8 Smoke Control Data Sheet TCON264 MR-VAV-X2-U8 Smoke Control Data Sheet TCON265 78010-U8 Smoke Control Data Sheet TCON266 B78010-U8 Smoke Control Data Sheet TCON267 78035-U8 Smoke Control Data Sheet TCON268 B78035-U8 Smoke Control Data Sheet TCON269 78061-U8 Smoke Control Data Sheet TCON270 B78061-U8 Smoke Control Data Sheet TCON271 78020-U8 Smoke Control Data Sheet TCON272 B78020-U8 Smoke Control Data Sheet TCON273 78022-U8 Smoke Control Data Sheet TCON274 B78022-U8 Smoke Control Data Sheet TCON275 78032-U8 Smoke Control Data Sheet TCON276 B78032-U8 Smoke Control Data Sheet TCON277 7808-U8 Smoke Control Data Sheet TCON278 B7808-U8 Smoke Control Data Sheet TCON280 DPU7911A/7912A-U8 Smoke Control Data Sheet TCON281 DPU-7920-U8 Smoke Control Data Sheet TCON282 DPU7921/7922-U8 Smoke Control Data Sheet TCON286 I/STAT-LCD Installation Sheet TCON287 I/NET® 2000 System with ID Works Upgrade/Integration Guide TCON289 NetPoint General Purpose Unit 546-X1 (NP-546-X1) Installation Sheet TCON293 779715 ICI ModBus Installation Guide/Reference TCON294 I/NET 2000 Web Interface Reference Guide TCON295 INET to Vista (I2V) Graphics Conversion Utility Reference Guide TCON296 TAC OPC Server for I/NET Seven TCON297 Distributed Link Architecture (DLA) User Guide Version 1.0 TCON298 I/NET Seven Getting Started TCON299 I/NET Seven Operator Guide TCON300 I/NET Seven Technical Reference Guide TCON301 I/NET Seven Reference Guide – Database Connectivity and Reporting TCON305 Model 2000 NetPlus Router Notice TCON306 7920 DPU - DPU48K Installation Sheet TCON307 LAN Connector Advisory TCON311 7798C SubLAN Interface Installation Guide TCON312 SCU 1200, SCU 1280, SCU 1284 Installation Guide TCON313 SCU 1200, SCU 1280, SCU 1284 Installation Sheet

Issue Alarm code, configuration code passwords for DC1100 and DC1400 Product Line Field Devices Environment DC1100 controller DC1400 controller Cause Configuration Resolution Passwords are: 0112 for configuration mode 0402 for fast run mode

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

  Issue The customer has created an alarm, this alarm has an Attachment that displays a Graphic (Display on Alarm enabled). All the remote Workstations at this site show the graphic popup on alarm, except a single Workstation. That Workstation will display PDF Files 'On alarm', but not TGML graphics. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Workstation Cause Either, they at the same time had two monitors and placed the graphic attachment on the other monitor, and then the position was saved. Or by mistake managed to move the attachment out of the current monitor scope Resolution Remove WorkStation cache from both (User + Program data) :  User: C:\Users\*user-name*\AppData\Roaming\Schneider Electric EcoStruxure\Building Operation\WorkStation  Program data: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation The alarm will now display the TGML graphic attachment

Issue How to configure the EcoStruxure BMS External Log Storage feature using PI System. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need EBO to send selected trend logs and the event log to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. Resolution The following video will illustrate how to: Install and configure AVEVA PI system (PI Server and PI Web API) for testing. Configure PI system settings in EBO. Configure trend logs to be written to PI system. View and organized the data in PI system Explorer. Things you need: EBO 2023 (V5.0.3) or higher with valid AVEVA PI System connection license or demo license (Enterprise Server, AS-P, AS-B or Edge Server). AVEVA PI server and PI web API with valid license (Check EBO Information Technology System Planning Guide for tested versions). For more information about PI system recommended architectures, system requirements and installation instructions, please check AVEVA documentation, PI System™ | AVEVA, OSIsoft - PI System and YouTube video published by AVEVA for detailed instructions about installing and setting up PI system Setting up a PI System Development Environment From Scratch - YouTube Note: In EBO V7.0.1 or higher, values can also be read and hosted from an AVEVA PI System, refer to: Hosting Points from AVEVA PI System

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

Issue The datasheet for DO-FA-12 says: Contact rating .......................250 VAC/30 VDC, 2 A, Pilot Duty (Power Factor 0.35) What does "Pilot Duty" mean? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Bundled (AS-B) Building Operation IO-module Cause The datasheet specifies the rating class of the relays.  Understanding what "Pilot Duty" means is needed in order to know what load can be controlled by the relay. Resolution A "Pilot Duty" rating means that this relay is made for a specific highly inductive load, such as controlling the coil of another relay or contactor. Contacts with a "Pilot Duty" rating have passed standardized testing to prove they can reliably control a "Pilot Duty" load. In another example the datasheet of a device may say: Relay contact rating 250 VAC / 30 VDC, 2 A Pilot Duty (C300) In this case C300 indicates the rating of the relay, according to the UL 508 standard. The start current of a motor could damages the relays in case the current is too high. The start current could be up to 8 times the rated current, or more.

Issue To downgrade an Automation Server, a DFU procedure must be performed on the device Product Line EcoStruxure Building Operation Environment Automation Server Cause When deploying a 'New Database' to an Automation Server, the controller must first be cleared of existing data. The firmware is then reloaded with a blank database image. This process may require placing the device into DFU mode to complete the installation successfully. Resolution To reset an automation server to DFU mode:   Start the Device Administrator. For more information, see Connecting to an Automation Server Using the USB Device Port . On the automation server, press the Reset button 3 times within 2 seconds.     Use a USB cable to connect the USB device port on the automation server with a USB port on the PC. Ensure that the automation server is displayed in the list and DFU mode is displayed in the Device status column.   The automation server is now ready for the upgrade procedure. For more information, see Uploading and Upgrading a Field Server .

Issue There are BACnet/IP devices on several different IP subnets. Each subnet has one BACnet/IP device setup as a BBMD, however when doing a discover, no BACnet/IP devices from the different subnets are not being discovered. Environment Niagara G3, ENC-520 Cause Setting up the BBMD in the ENC-520 is as simple as Changing its “Ip Device Property Type” from its default of “standard” to “Bbmd”. Once the ENC is configured as a BBMD device, then the BBMD’s required Broadcast Distribution Table (BDT) is automatically created. The ENC’s BDT includes its own IP address and Broadcast Distribution Mask (BDM), as well as the IP address and BDM of all other BBMD devices on the other IP subnets. The BDT allows for manual editing. We have found in some cases that the BDMs were being confused with the IP address subnet mask. The BDMs were being changed to reflect devices’ IP address subnet mask, which were something other that the standard BDM of 255.255.255.255. BBMD devices’ BDM must be set to 255.255.255.255. Resolution The Broadcast Distribution Mask must be set to “255.255.255.255” for each BACnet /IP Address listed in the ENC’s Broadcast Distribution Table. This is also true for other BACnet/IP devices configured as BBMDs on the other subnets. 1. Expand the ENC’s BACnetNetwork 2. Expand Bacnet Comm and then expand Network 3. Expand Ip Port and then expand Link 4. Expand the Broadcast Distribution Table 5. Expand any devices listed and set their Broadcast Distribution Mask to 255.255.255.255 for any one not listed as such. Save changes. Try and discover again.  

Issue Using the Xenta 421A, 422A, 451A or 452A I/O modules as a stand alone Lonworks node and all values are reading the default 0. Product Line EcoStruxure Building Operation, Field Devices, TAC Vista Environment Xenta I/O Modules Xenta 400, 421A, 422A, 451A, 452A as stand alone LON nodes Cause The Xenta 421A and Xenta 451A as stand alone Lonworks node require the UCPTConfiguration to be set to the necessary integer value for the required input. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network management software (Lonmaker, NL220, Tridium, Etc.) Browse / Edit the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the UCPTConfigInput variable within that module Set this UCPTConfigInput variable to one of the following: 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication NOTE: This is normally done in Menta when you are using these controllers as I/O modules to a Xenta 401, Xenta 301, Xenta 302 base unit.  The scan time of all inputs is (200ms * number of inputs used).  So if there are 3 inputs, the complete module will have been scanned every 600ms.