Building Automation Knowledge Base

Issue What port numbers do routers have to have open in order to run a Continuum system? Product Line Andover Continuum Environment Cyberstation Continuum BACnet / Infinet Controllers TCP/IP Cause There have been many questions on which network ports the Continuum system uses for communication. Below is a listing of the network ports along with what the port is being used for. Resolution The destination UDP port from the controller will always be one of the below port numbers. The source UDP port that the controller uses is completely arbitrary and will be anywhere from 32768 to 65534. (0x8000 to 0xFFFE) Controller/Cyberstation Application Packet type Decimal port number Hex Port numbers   Controller Error Log Tool - UDP 33487 0x82CF BACNet B4 controller Point Configuration UDP 33487 0x82CF BACNet B4 controller Alarm Configuration, Alarms, and COV UDP 47808 0xBAC0 BACNet B4 controller Controller flash TCP 33456 0x82B0 BACNet B4 controller Web Server TCP 80 NetController Point Configuration, Alarms, and Events UDP 33487 0x82CF Netcontroller Save from Controller TCP 33440 0x82A0 NetController Controller flash TCP 33456 0x82B0 Sending Email  TCP 25 NetController WebServer TCP 80 (but configurable) CX9702 ** Point Configuration, Alarms, and Events See Note 33487 0x82CF CX9702 ** Save from Controller See Note 33440 0x82A0 CX9702 ** Controller flash See Note 33456 0x82B0 CX9702 ** WebServer See Note 80 (but configurable) ** Note: UDP or TCP port (user configurable via the TransportType attribute) Remote View Remote view Video TCP 18772 0x4954 CyberStation Controller Alarms and Events UDP 33487 0x82CF CyberStation Peer Cyberstation communication UDP 44224 (1.4x and 1.5x), 47808 (all other revisions) 0xACC0 (1.4x and 1.5x), 0xBAC0 (all other revisions) CyberStation Workstation to SQL database TCP Determined by Microsoft, 1433 by default CyberStation BACNet communication UDP 47808 0xBAC0 CyberStation MSMQ TCP 1801 0x0709 CyberStation MSMQ UDP 3527 0x0DC7 CyberStation MSMQ UDP 1801 0x0709 CyberStation MSMQ RPC 135 0x0087 CyberStation MSMQ RPC 2101*,2103*, 2105* 0x0835, 0x0837, 0x0839 *Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801. The Message Queuing Independent Client multicasts a server discovery broadcast over reserved UDP port 1801. Message Queuing Servers listen on TCP port 2101* for RPC-based MQIS and Active Directory lookups. Message Queuing 3.0 independent clients and Message Queuing servers make MQIS requests directly to Active Directory by using LDAP on TCP port 389. Message Queuing Independent Clients and Servers listen on fixed TCP port 2103* and 2105* for RPC-based remote reads of their public queues and private queues. Also, the Dependent Client uses these two ports to communicate with its server for send and for receive. There is a dynamic RPC port that is assigned by the RPC layer for handshaking with an Independent Client or with an RPC server for the Message Queuing Server to determine the fixed ports. This is typically port 135. The internal "ping" mechanism for Message Queuing operates over reserved UDP port 3527. When you use HTTP messaging in Message Queuing 3.0, Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801. * These port numbers may be incremented by 11 if the initial choice of RPC port is being used when Message Queuing initializes. A connecting QM queries port 135 to discover the 2xxx ports. For more information on MSMQ ports check with Microsoft, http://support.microsoft.com/kb/178517 A .PDF document containing this Network Port information can be downloaded Here.

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 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 VTRA Valve Body requires replacement due to obsolescence. Product Line Field Devices Environment VTRA 3-port Mixing Valve Body Cause Obsolescence of VTRA Valve Body Resolution VTRA Valve Bodies are obsolete and have been for many years. VTRA Valve Bodies were available with either Flanged or Screwed connections.  Details of the various size / connection combinations available appear VTRA Specification Sheet. REPLACEMENT OF VTRA FLANGED CONNECTION VALVE BODY A replacement for the VTRA Flanged Valve Body (32-80mm) may be selected from the VTRE range of Flanged Valve Bodies, see VTRE S-E Specification Sheet for more datails. N.B. It should be noted that the VTRE Valve Body is rated PN6 whereas the VTRA was rated PN10. The VTRE Flanged Valve Body may be operated by the EM9 Actuator, see Alternatively the VTRE Flanged Valve Body may be operated by the M9B Actuator, See EM 9 Specification Sheet for more details. No Linkage Kit is required to mount the EM9 or M9B Actuator on the VTRE Valve Body. Alternatively a replacement for the VTRA Flanged Valve Body (65-80mm only) may be selected from the the S-E VG311F and V321 3-Port Flanged Valve Bodies, more details can be found in the Venta VG311F 65-150C Specification Sheet and the Venta V321 Specification Sheet N.B. It should be noted that the S-EVG311F and V321 Valve Body are rated PN16 whereas the VTRA was rated PN10.   REPLACEMENT OF VTRA SCREWED CONNECTION VALVE BODY A replacement for the VTRA Screwed Valve Body (15-50mm) may be selected from the MB range of Screwed Valve Bodies, see the MB/MBF data sheet for more details. The MB Screwed Valve Body may be operated by the MD10B series Actuator, see the MD10B specification sheet for more details. Alternatively the MB Screwed Valve Body may be operated by the MD10A Actuator, see the MD10A specification sheet for more details.  

Issue During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. Product Line TAC Vista Environment TAC Vista 5 Cause During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. PSS is creating demo license files with a monthly validity. Resolution Monthly demo license files are made by the Malmö PSS team, and may be requested from PSS. The "TS_OK" demo file is used for "Remote Desktop" applications, giving access equivalent to the demo file available for download from the The Exchange Download Center, usually valid until the end of the month. Additionally, a OPC Server license file with the same validity is also available by request. Evaluation license for TAC Vista 5.1 Demo TS License TAC Vista 5.1   More information can be found in Where to find Evaluation license for TAC Vista and Struxureware Building Operation.

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

Issue Includes PSI Error Messages and Device Error Messages Environment PSI Microzone II Network 8000 Cause Quick reference Resolution The error codes are listed in the PSI MicroZone II Operator's Manual.  The full document is available here:  F-23058. Just the error codes are available here:  Pages 59-61.

Issue What is the factory default IP address for a new I/A Series G3 JACE-6 or JACE-7? Product Line TAC IA Series Environment I/A Series G3 JACE-6 JACE-7 Cause Initial power up and connection to Workbench Resolution Two female 10/100-Mbit Ethernet connections are provided on the JACE-6 and JACE-7 hardware platforms. These are RJ-45 connectors labeled LAN2 and LAN1. Use a standard Ethernet patch cable for connecting to a hub or Ethernet switch. An activity LED for each Ethernet port is visible, and are labeled "LAN2" and "LAN1" on the cover. The factory-default IP address for LAN1 on the JACE-6 and JACE-7 is 192.168.1.12n, where the last numeral n in the address matches the last digit of the JACE's serial number, and subnet mask is 255.255.255.0. By default, LAN2 on the JACE-6 and JACE-7 is disabled. The factory default platform username and password is tridium / niagara.

Issue Unable to locate data sheet for the MD-S1 and MD-S2 auxiliary switch Product Line Field Devices Environment MD-S1 auxiliary switch MD-S2 auxiliary switch Cause No data sheets can to be found. Resolution Data sheets for the MD-S1 and MD-S2 auxiliary switches are not available. To review the MD-S Auxiliary Switch Installation Sheet, please click HERE.

Issue The TA210U controller is obsolete since many years, but the manual is sometimes still requested Product Line Field Devices, TAC Vista Environment TAC210U TA210U 2107030QRW 2107030QRT 0844427005 0844428005 Cause Old controller Resolution The (Swedish-only) manual can be found here: TA210U Controller User Manual (L3238001.pdf).

Issue Cannot open the FlexNet License Admin, the TAC license server is not running as a service, or the vendor daemon is down. Product Line TAC Vista Environment Vista LMAdmin FlexNet License Administrator Cause If the TAC Vista Server installation option "Use the local TAC License Server" is not selected during installation, the license server will be installed but not successfully configured. When the license server is not running it will prevent the LMAdmin web interface from launching. If the license file is not in the correct location when the license server is started, then the vendor daemon must be started manually. For general information on the new license system, see LMTools Licensing Administrator program is replaced with LMAdmin in Vista 5.1.8 or greater. Resolution Remember that a valid and un-modified License File is necessary for the following troubleshooting steps to work. If the License file was manually manipulated in any way, please revert to a File specifically licensed for the machine where the License Server resides. Before proceeding, make sure the setup of the license system is made correctly following No license after reboot when TAC Vista Server (TACOS) runs as a service Check out this video about the new Vista 5 licensing system on the Community website. Check out the TAC License Server Setting tool below for the new license system. Click here to download the zip file.       Could not reliably determine the server's fully qualified domain name This is a bug in the lmadmin.exe file. Either replace the lmadmin.exe file with the newest available or install the newest version of the license system available. You can have a newer version of the license system installed than the TAC Vista version installed. E.g. TAC Vista 5.1.8 will work together with a license server version 5.1.9 Cannot Open the Flexnet License Admin Ensure that the TACLicenseServer is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services. Scroll down and select TACLicenseServer. Click Start in the top left corner of the window. Make sure that the site license is the only file in the license server path. If there is a demo license in the file path when trying to start the license server, it will fail to start. Sometimes you will get the following Windows error. Error 1067: The process terminated unexpectedly. Note: TAC License Server with spaces is not the correct license server. If TACLicenseServer is not found in the list then move on to the next troubleshooting section titled "Setting up the TAC License Server as a Service".   If the TAC License Server will not start then it may be due to another program using the 8080 TCP port. Use TCPView to search for programs running on local port 8080 and either stop this program or use the TACLicenseServer Settings tool at the top of this page to change the port that the TAC License Server uses. If the TACLicenseServer still does not run then continue to the next section below, Setting up the TAC License Server as a Service.    Setting up the TAC License Server as a Service LMAdmin.exe must be registered as a service. When first installing Vista the option "Use the local TAC License Server" should be selected. When this option is selected it will install the license server, register it as a service and start it. When "Use a license file" is selected it will only install the license server without configuring its settings. This can be corrected by reinstalling Vista and making the proper selection or by a manual configuration procedure. The manual procedure steps are listed below. Note: The option "Use a license file" only applies to a demo license, not a site license file. Manual Procedure to Register the License Server as a Service Start a command prompt as an administrator. To do this go to Start > All Programs >  Accessories and right-click on Command Prompt, then select Run as Administrator. In the command prompt go to path C:\Program Files\Schneider Electric\License Server\ (This can be done by entering "cd" and then the directory path listed here.) For 64-bit OS go to "C:\Program Files (x86)\Schneider Electric\License Server\" Run the command: "LMAdmin.exe -InstallService TACLicenseServer".   Manually copy the license files that are to be used to the new license file folder location. 32 bit - C:\Program Files\Schneider Electric\License Server\taclic\licenses 64 bit - C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses   In the command prompt type, the following command to start the license server "net start TACLicenseServer". Note: If the license files are not copied prior to starting the license server, the vendor daemon will not be started successfully and must be manually started after the license files have been copied to the new license file location. For instruction on how to do this, follow the steps in the next section Vendor Daemon is Down When the license server is installed but not configured, as mentioned above, the TAC Vista Server installer will not create a shortcut to the license administration tool in the start menu; since the shortcut will not work. A shortcut is created in the installation folder and can be used to create a shortcut in the start menu manually. The shortcut can be found here "C:\Program Files\Schneider Electric\License Server\FlexNetLicenseAdmin". For 64-bit OS the shortcut is found in "C:\Program Files (x86)\Schneider Electric\License Server". Vendor Daemon is Down   Note: If working on a 64 bit PC, replace "Program Files" with "Program Files (x86)" in the file paths below. Go to All Programs > Schneider Electric > TAC Tool 5.X.X > Flexnet License Admin. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password). Click on the Vendor Daemon Configuration tab and then select the taclic daemon. Verify that the path in the License File or Directory field matches the location of the site license. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start. If the Vendor Daemon still does not start after checking the file paths, verify that the site license has been hosted to the correct MAC address. For help finding the MAC address, see How to locate a computer's MAC address. NOTE: Also make sure there are no other Flexnet License Servers installed on this same machine (SmartStruxure, Power Manager, etc). If there is another license server running on the same machine then this can cause a conflict. SmartStruxure license and TAC Vista license on the same PC can walk you through merging them together. If IPV6 is enabled, you may need to disable it and reboot the machine. Switching from a site license to a demo license Log into LMadmin and stop the license server Save the Demo License file in C:/Program Files/Schneider Electric/License Server/Licenses Open the desired engineering tool and point Vista to the Demo file When finished, log into LMAdmin and start the License Server.  This will tell Vista to continue using the site license. A site that has worked with the installation from a remote desktop or the different user logged in Open task manager Check for process "lmgrd" of 2 of them are running the FlexNet server might try to read from the wrong server. Shutdown down both processes and restart the FlexNet server Log in to FlexNet admin and start the vendor Reread the license file Also, check License Administrator error "EXITING DUE TO SIGNAL 28 Exit reason 5"

Issue Getting error message: “Login Failed - Could not connect to fox server. Check that fox and web SSL settings match or try connecting using https.” when trying to connect to G3 station via a web browser. Product Line TAC IA Series Environment In Niagara G3, Version 3.7.106 Cause Security setting for the Web browser and Fox Service do not match, or the FOX or FOXS port is being blocked. In Niagara G3, Version 3.7 and later, users can set up SSL for both HTTP and FOX connections. The intention is that, when using the applet, SSL settings for HTTP and FOX must match (i.e. HTTPS/FOX or HTTP/FOXS are not allowed). In Niagara G3 3.7 update1 and earlier, users can connect to the applet using the invalid HTTPS/FOX combination. In addition, when loading the applet while using HTTP/FOXS, users are redirected back to the login screen with no error message. In NiagaraAX 3.7 update2 and later, users attempting to use the applet with an invalid HTTPS/FOX or HTTP/FOXS connection will be redirected to the login screen. An error message will appear indicating what went wrong. The Web and Fox settings do not match. They must be set to either HTTP/FOX or HTTPS/FOXS. We’ve found that there is a condition where the error message still displays even though both Fox Service and HTTP match. Reason being is during login to a station via web browser, a check is performed to determine if the Fox Service match the HTTP setting be used. If accessing via HTTP, then port 1911 (FOX) is checked. If accessing via HTTPS, then port 4911 (FOXS) is checked. We found that the corresponding, FOX or FOXS, port were not opened.  Resolution Open the needed FOX or FOXs port: Depending on if HTTP or HTTPS is used, the correct port must be opened for the corresponding FOX or FOXS connection. Port 1911 needs to be open if using HTTP/FOX connections, and if using HTTPS/FOXS, port 4911 needs to be open. Port need to be open to bidirectional TCP traffic.

Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue The Drayton Theta YBM2A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBM2A Cause The Drayton Theta YBM2A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2A 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 YBM2A 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 YBM2A 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 YBM2A 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. N.B. The YBM2A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :- Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBM2A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   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 YBM2A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue The Drayton Theta YBL1A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBL1A Cause The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1A 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 YBL1A 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 YBL1A 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 YBL1A 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 YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   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 YBL1A 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 YBL1A 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 YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   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 YBL1A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue The System Alarms: "Timeout Cloud SMS channel offline" and "Cloud telemetry channel offline" are never reset and therefore always present in the Alarm view. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Building Operation Enterprise Server Cause When cloud connectivity is enabled, the EcoStruxure BMS sends data from the system to the central storage for diagnostics and analysis along with data from other buildings and sites. Under the Cloud Connectivity Tab, The default communication setting is "Auto". If the customer has the "server.cloud.customer" license feature, the BMS Server tries to activate the cloud communication. The alarms are generated if the ES/AS-P, at some point, was able to connect to the cloud, but then taken off the internet while the setting was "Auto/Enabled". Resolution Upgrade the system to EBO version 3.2.1 or to the latest available version. According to Release Notes for EBO version 3.2.1 this issue should have been fixed in that version, see defect 42293 in Release Notes If the issue is still present see the solution below. The only way to reset the alarm is to have a successful connection to the cloud(Internet) again. Make sure the ES/AS-P has internet access Now the Cloud alarms should go away. Verify that they disappear. Go to the Control Panel in Workstation and click Cloud Connectivity Set the Communication setting to Disable and save the changes. Take the BMS Server off the internet again

Issue Once the occupied cooling and heating setpoints are written from a BMS, the user is not able to change the setpoint from the room controller Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Series Room controller Viconics branding VT8000 Series Multi Purpose Manager (MPM) BACnet Cause By default, the occupied setpoint value is written to Room Controller with priority level 16 by the BACnet front end. Attempting to change the setpoint locally using the up and down arrows on the SE8000 Room controller will not be allowed since the Room controller uses the relinquish value internally (priority 17) which will be automatically overwritten by the BACnet front-end. Resolution The work around is to release the BACnet front-end control over the BACnet object using a LUA4RC script. The script can be uploaded using one of the following two methods: 1 - Uploader Tool A USB cable is required to upload the script. The uploader tool can be downloaded from the Exchange Download Script Download Uploader Tool   2 - BACnet The script can also be directly uploaded via BACnet using the "Description" field as shown in the image below if (ME.AV92 == 6 or ME.AV92 == 7) then ME.AV39_PV[16] =nil ME.AV39_PV[10] =nil ME.AV40_PV[16] =nil ME.AV40_PV[10] = nil ME.AV92_PV[17] =0 end Where, ME.AV92 is the Keyboard value ME.AV39 is the Occupied Heating Setpoint ME.AV40 is the Occupied Cooling Setpoint Using this method, the script can be uploaded to multiple SE8000 Room Controllers by following the steps in Bulk Lua4RC upload via BACnet (Mass upload) For more information about Lua4RC, refer to the Lua4RC Programming Guide

Issue "Communication failure due to routing device not available" errors when trying to view BACnet controllers or the objects they contain. Product Line Andover Continuum Environment Continuum v1.74 and above. Cause The Cyberstation is unable to route to the desired device(s). This can occur due to changes in the network, network settings, or blocking software on the PC.  Resolution Check that the IP settings of all devices are configured so they can see each other. Specifically that the subnet mask configured for each device allows them to be seen on the same logical network. Also see the following articles: Communication failure due to routing device not available Eaton IP BACnet Lighting Panels go offline with error "Communications failure due to routing device not available" Simple BBMD setup

Issue Wire colour coding for the SPP110 Product Line Field Devices Environment SPP110: 004702020 004702040 004702060 004702080 004702100 004702120 004702140 Cause Wire colour coding SPP110 required. Resolution Due to supply problems, between week 23 to week 32, there was a change to the sensor's cable and the wire colours. This was implemented by the manufacturer without Schneider Electric's knowledge. So no product announcement was produced.                      Original       Week 23 to Week 32 No. Function Colour                Colour 1     Y            Brown                Green 2    GO         Black                  White 3    G            Red                    Brown   Standard                                                                                           Week 23 to Week 32   Refer to the SPP110 Pressure Transmitter Wet Media Specification Sheet for more information.   The SPP110 installation sheet showing the standard wire colouring is available here The SPP110 installation sheet showing the wire colouring is attached.

Issue Attempts to change the buffer size on an existing BACnet trend result in the following error. Saving Changes Property write access denied '~/BACnet Interface/IP Network_2/VAV01/Application/Trends/RmTmp/Buffer_Size' BACnet Product Line EcoStruxure Building Operation Environment BACnet Trend Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause The buffer size cannot be changed on an enabled trend. Resolution Right-click the trend in question and open the Properties window. Set Log enabled to False. Click OK Open Properties again and change the buffer size to the desired size. Click OK. Open Properties a final time to set the Log to enable back to True. Click OK.