Building Automation Knowledge Base

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 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 Wanting to use SNMP to be able to create alarm traps from the network Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site Cause Simple Network Management Protocol (SNMP) is an "Internet-standard protocol for managing devices on IP networks. Devices that typically support SNMP include routers, switches, servers, workstations, printers, modem racks, and more. SNMP is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention such as an alarm in StruxureWare Building Operation.  Resolution For SNMP to be able to create alarms from the network in StruxureWare Building Operation, beginning with Building Operation 1.3 - StruxureWare Building Operation supports an older version of this service which uses the default community password. As such, the decision to open this port should be done based upon a risk/benefit assessment. The only form of SNMP that is currently supported is the ability of SmartStruxure to respond to the network management queries that might be issued by an SNMP client.  Through release 1.5, SNMP is only supervising the equipment and can not receive traps from SNMP. Beginning in the 1.6 release, you can send SNMP traps from an alarm. In future releases it may be able to export alarm traps to SNMP, but this is really an IT function. Release 1.6.1 introduces support for SNMP alarm traps v3.0 notifications. This requires an add-on option on for the corresponding server, either the Automation Server and/or Enterprise Server. Refer to Testing SNMP alarms with SmartStruxure for further help on testing SNMP in 1.6.1 version and above

Issue Connecting to a Link or Site Environment I/NET Seven Site Cause Knowledge on how to connect to a Link or Site Resolution I/NET displays this dialog box when you select Connect from the main menu. This dialog box allows you to choose a link or remote site. Connect to a device as follows: Select Connect from the main menu. The system displays a summary list of available link devices or sites. Note: A dash (-) appearing next to a device name indicates that the device is not currently available for communication. An asterisk (*) indicates that the name of the controller or the type has changed. Highlight a link device or site in the list. Select OK to connect. After the system connects to the selected device or site, the status bar at the bottom of the screen shows the connected levels.

Issue What is the purpose of the Max Info Frames attribute in a Continuum BACnet controller? Product Line Andover Continuum Environment BACnet MS/TP, MaxInfoFrames Optimizing MSTP Cause Information on the Max Info Frames function. Resolution The Max Info Frames setting on the BACnet controller object editor specifies how many messages that the controller can send out to other controllers when it has the token on the network. For instance, a B3 controller has a default of 2 for this setting. If it receives the token on the MSTP network and it has 5 COV or Event notifications to send to other controllers or workstations, it will send the first 2, and wait until it gets the token the next time around and send 2 more, etc. The BCX controller has a default of 8 for Max Info Frames. This setting is changeable through the BACnet controller editor, however care should be taken not to increase it to too large a number. The larger the setting, the more time that particular controller can hold the onto the token, which in turn denies other controllers on the network the capability of sending out their data in a timely manner. It should only be adjusted if there is a definite need for increased messaging, but on the MSTP network it is not recommended to go above 10, although we do not limit the value. In a Cyberstation Version 1.8 or above the setting can be made on the details page of the BACnet controller device editor. If adjustment of this parameter is done using any Cyberstation prior to version 1.8, the setting will not stay at the new value after a controller reload from the Infinity side, it will revert to it's default. You will need to create a PE program in the controller to set this parameter to the desired value if it is reloaded. The program should be autostart and fallthru, and use the "Writeproperty" keyword to set the parameter. The syntax should be as follows: Line SetMaxInfo WriteProperty ("Full Bacnet path name of controller", MaxInfoFrames, "New Value") Stop

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 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 Why do controllers go into bootloader mode? Product Line Andover Continuum Environment Bootloader NC2 BCX CX99xx CX96xx i2 b3 Cause Continuum controller are placed into bootloader mode if they repeatedly hit a firmware level exception. An exception is when the controller tries to do something that cannot be done.  Some examples of an exception are... A controller tries to read from memory that it cannot read from. A controller attempts write to memory that cannot be written to. On startup, flash generation controllers load the application from flash RAM.When they hit an exception, older, non-flashable controllers would simply clear the application software from ram, power up and wait for the software to be loaded from the front end.  If there is a bad application there needs to be a means by which a user can intervene before the application is loaded so that the controller firmware can be reloaded or upgraded.  When a flashable controller hits more than three exceptions within a ten minute time period the controller is placed into bootloader mode intentionally. Resolution When a controller repeatedly goes into bootloader mode it is time to take a close look at environment which might be driving the controller to hit exceptions A controller usually goes into bootloader mode due to environmental issues such as Heavy ARP traffic Controller grounding Controller power issues Problems with the communication bus. A controller that repeatedly hits exceptions is placed in bootloader mode by design.  Flashing a controllers firmware is the only way to get a controller out of bootloader mode. 

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue Procedures and processes to secure I/A Series Niagara 4 Systems Product Line TAC IA Series Environment  I/A Series Niagara 4 Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara 4 system.  While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara 4 system more secure by carefully configuring and using: Passwords System Passphrase Platform Account Management Station Account Management Role and Permission Management Authentication TLS and Certificate Management Module Installation Additional Settings External Factors Please note that while all of these steps should be taken to protect your I/A Series Niagara 4 system, they do not constitute a magic formula. Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn’t mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it. Note: Schneider Electric strongly recommends upgrading to the latest I/A Series N4 version maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build-included documentation to understand the behavioral impacts of the security enhancements and JACE hardware platforms supported. Download the Niagara 4 Hardening Guide_2023 for more details.

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 After installing a self-signed certificate via Internet explorer as detail in article  SSL Certificates - Security Certificate Risk warning logging in to WorkStation or WebStation using HTTPS  There is still a warning in Chrome and Firefox that the site is "Not secure" This warning is not seen in the earlier versions of Internet Explorer but from version 11 it is also seen in Internet Explorer. Product Line EcoStruxure Building Operation Environment WebStation Cause Different browsers have different policies to Self-signed Certificates and display a different warning, but still use HTTPS. These policies may change over time, but it is not something that can be controlled Without a neutral and recognized third party—such as a certificate authority—verifying certificate ownership, a certificate is meaningless. To better understand, when doing something like creating an HTTPS connection you have the following chain: A client web browser making the request to the server. The remote web server sending data back to the client. And an HTTPS certificate authorized by a neutral 3rd party that vouches that the server is who it is and the encryption is valid because of that. A self-signed certificate is inherently untrusted because anyone can generate a self-signed certificate. Anyone including an entity that deliberately pretends to be something/someone they aren’t. With a self-signed certificate there is simply no trusted third party that has the basic human procedures set to simply state, “Okay, this domain has a certificate we issued them and thus you can trust them. We say they are in fact the domain the claim to be and not an imposter.” And since anyone in the world can create a self-signed certificate on their own, it’s usage has inherent trust issues. What makes a certificate valid has very little to do with deep technology or encryption techniques but what makes it valid is a process centered around a neutral—and recognized—third party validating a usage procedure and browser makers adhering to respect of those procedures. At the end of the day, an encryption key pair is an utterly meaningless pile of bits and bytes without the enforcement of the processes and procedures that surround them. Resolution Internet Explorer - No warning Chrome - "Not Secure" shown Firefox - Initially a "Your connection is not secure" warning is seen "10.158.7xx.xxx:xxx uses an invalid security certificate. The certificate is not trusted because it is self-signed. Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT" Add Exception, allows access as below   The best way to permanently remove the warning is to pay for a certificate from a certificate authority. See this forum post on how to get generate and add a certificate from a certificate authority

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 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.

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 for assistance. Issue When restoring a Continuum database the process fails with a Cannot show requested dialog error message. Index was outside the bounds of the array. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Server Microsoft SQL Server Management Studio Cause The version of SQL Server Management Studio is not compatible with the Microsoft SQL Server version. In this example the error occurred when attempting to use SQL Server Management Studio for SQL Server 2005 Express to restore a database on an SQL Server 2012 Express server. Resolution Uninstall the incompatible version of SQL Server Management Studio and then install a compatible version. The database can then be restored.

Issue What does that controller/device look like Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Site with TAC or Schneider Electric Controller(s) Cause Questions concerning what a controller looks like, or if there are no labels on the controller which help identify. Are photographs or drawings available? (This is an article in progress. Have one that is not listed? Please help by taking a good picture(s) and including or send to Product Support) Resolution I/NET: 7728 7728 Left side 7728 Right side  7790 7790 side 7790 older model  7790 older model side  7798C Top 7716 7920 7920 side  MR-AHU MR-AHU left side MR-AHU right side P8UI8DO Expansion board  SCU1284 SCU1284 side Continuum: ACX5720 ACX5720 Open CX9702  b4920 b4920 Open BCX1 BCX1 open i2-600 Series i2.600 Series Open  i2_850 i2_850_Open i2_887_L_115  i2_920 i2_920_open CX9400 with three 32s and two 16s in 8 card rack CX9400 CPU front CAD Drawings for the Continuum controllers are also available on The Exchange Download Center: Link Here.

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 for assistance. Issue How to connect to the Jace 8000 system shell Product Line TAC IA Series Environment I/A Series Jace 8000 Cause Multiple diagnostic and low-level configuration processes need to be performed directly connected to the Jace 8000 in the system shell of the device. Resolution Connect the USB cable between the controller’s Debug port and the USB port you are using on your PC   On your PC, start your terminal emulation software. For example to start PuTTY from the Windows Start menu, this is typically Programs > PuTTY → PuTTY. PuTTy can be downloaded at no cost if you do not already have it on your PC. In the tree in the PuTTY Configuration dialog, expand Connection and click Serial. Set the “Serial line to connect to” for your PC’s (USB) COM port to use. For example, COM3. NOTE: You can examine Ports in Windows Device Manager to determine which serial port is in use on the PC. If you don't see the Jace in the COM ports, you will need to install the driver which can be Downloaded from FTDI.  It is also attached to this document below for Win10. Set the “Configure the serial line” fields as follows: • Speed (baud): 115200 • Data bits: 8 • Stop bits: 1 • Parity: None • Flow control: None In the tree in the PuTTY Configuration dialog, click Session and then click/select the “Connection type” as Serial NOTE: (Optional) You can save this configuration to reuse (load) in future PuTTY to JACE serial sessions. To do this, type in a connection name in the “Saved Sessions” field (for example, “JACE- 8000-S”), and click Save. When you start PuTTY again to serially connect to the JACE, select this name and click Load. At the bottom of the PuTTY Configuration dialog, click Enter. At the login prompt, enter a platform user name, and at the password prompt, the platform password. a. If prompted for system passphrase, enter the platform’s system passphrase. If login is successful, the TITAN System Shell menu appears. When finished making platform changes from the system shell, do the following: • If no changes or reboot is not necessary, simply type L to Logout. • If changes require rebooting, select the Reboot option. Type “y” at the “Are you sure you want to reboot [y/n]” prompt, and press Enter. Shutdown-related text appears in the terminal (PuTTY) window. Click the Close control (upper right corner) in the terminal session (PuTTY) window. Click OK in the “PuTTY Exit Confirmation” popup dialog. Unplug the USB connector from the JACE’s Debug port. This procedure is simply how to connect using USB serial port for system shell.  More information about functions available once connected can be found in other Knowledge Base articles and in the Jace 8000 Install and Startup Guide

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.

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 Is it possible to use Sysman Alert Server with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Alarms and Events Cause Customers may wish to send important alarms to duty staff via SMS. Sysman Alert Server is one way of doing this and is easy to configure.  Resolution This is possible. The following document details the setup procedure: Sysman Alert Server with StruxureWare Building Operation The configuration will depend on the setup and location of the SysMan Server, but will generally involve "Write to File" Notifications if the Enterprise Server and Sysman Servers are installed on the same PC, or Emails to the SysMan Server (from Enterprise or Automation Server) More information can be found on Sysman's website. Part Numbers: SysManSMS ALERT SERVER: 900800600 SysManSMS GSM Modem: 900800610 In the UK when ordering please use the below part numbers. SysManSMS ALERT SERVER: 802000 SysManSMS GSM Modem: 100002