Building Automation Knowledge Base

Issue Measuring dry bulb temperature and relative humidity and need to use them to calculate the following Enthalpy Wet Bulb temperature Dew Point temperature Product Line TAC Vista, Ecostruxure Buildings Operation Environment Function Block applications Cause Need to calculate Enthalpy, Wet Bulb Temperature, or Dew Point Temperature.  These values are typically used to compare the latent heat in the outside air versus inside air for economizer cycles, in chilled water applications where condensation must be avoided, or in humidity control applications. Resolution Enthalpy - the total energy of both the dry air and water vapor per pound of dry air. Wet Bulb temperature - the temperature a volume of air would have if cooled to saturation by evaporation. Dew Point temperature - the temperature to which a volume of air must be cooled for water vapor to condense into water. Download the appropriate HFB below: Psychrometric Calculations in US Imperial Measurements Psychrometric Calculations in SI Metric Measurements

Issue The following errors are seen when trying to run SigmaX, RegSigmaX or SigView.  The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.  Application event log: Activation context generation failed for "C:\SigmaX\Bin\RegSigmaX.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis. Product Line Satchwell Sigma Environment SigmaX 7.0.6 on Windows 7 32-bit SigmaX 7.09 on Windows 10 64bit SigView Cause Microsoft Visual C++ 2005 redistributable has not been installed. It appears that SigmaX requires this version to run. Resolution Either the Microsoft C++ 2005 is not installed, or if it is, then the Service Pack 1 (SP1) is required to be installed. This can be checked under the Windows 'Apps and Features'. Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86). In some cases,  Microsoft Visual C++ 2005 SP1 Redistributable Package Security Update (x86) is required to resolve the issue. The 32bit (x86) version should be installed if installing Microsoft Visual C++ 2005 SP1 does not fix the problem. 

Issue Can you have two multiplexed Wiegand readers and two multiplexed RS-485 readers on the same Controller or Reader Module? Product Line Security Expert Environment Security Expert SP-C SP-RDM2 Cause Unsure if two reader protocols could be used on the same reader module. Resolution For this you will need to use another reader module. One module (this could be the SP-C) for multiplexed Wiegand readers, and another for multiplexed RS-485 readers. When using multiplexed Wiegand readers you will need to connect the D1 cable from the exit reader to the opposite reader port. So in multiplex reader mode you can have 4 Wiegand readers, or 4 RS-485, but not two of each. If Wiegand is being used both reader ports are setup as Wiegand. See details on this in the SP-C System Controller Installation Manual starting on page 28. The wiring for multiplexed RS-485 readers doesn't require any connections to the opposite reader port.

Issue TAC Graphic Clipart library is a collection of clipart to use as a starting point for an image based graphic page. There are pieces for building air handler ductwork, controlled equipment, dampers and actuators, and water side equipment. Product Line TAC INET, TAC Vista Environment I/NET gpg graphic Vista ogc graphic Cause Without libraries to build a background image for HVAC equipment, it can be difficult to create user-friendly graphic pages to display dynamic data.  In a graphic editor that relies on bitmaps or jpgs to build the airflow diagrams, floor plans, water side diagrams, etc, this library can be used as a starting point. Resolution Download the attached .zip file. Unzip the contents to a location on the hard drive of the computer that will be used to edit the graphic pages. Browse the contents of the .zip file.  It will be separated into logical folders.

Issue How to set up a Mantrap Product Line TAC INET Environment I/NET Access Control Site Interlocked Doors Person Trap Anti-Passback (APB) Cause What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be opened at the same time. Either door can be unlocked and opened as long as the other door is locked and closed and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high-value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high-security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? Regarding controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two, then the term interlocking door controller should be used. Resolution I/NET has three ways to do a mantrap: Event sequences and calculations -- limit to 5-7 SCUs per 7798C due to system loading Use a "standalone" third-party device that is wired to the door and is not attached to I/NET at all Use the interlock wiring diagram that uses relay logic to function. This is also part of the I/NET System. I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-pass back/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-pass back option set to Hard, which denies access to successive reads at the same reader, it does not prevent multiple persons from entering and exiting together, and it does not provide real-time accounting for the number of people in a Zone. Besides having a guard at the door, the usual method of implementing Zones does not prevent violations.   The example below presents some thoughts about improving the Zone's security in an I/NET Seven system. There needs to be a way to restrict the number of people gaining access to the door. There needs to be a way to keep up with how many people are in the Zone. One method to accomplish the first goal is to use a two-door egress system, as is often used in jails and similar security setups. For a medium security setup where the intent is not to prevent people from leaving, only one door needs a card reader. Such a design is illustrated below: Notes: Electric strike normally energized. Low walls or fences. The area should be small enough to limit how many people or things are in it at one time. Gate with normally de-energized bolt. The gate could swing both ways, so one would only have to push it to open it. It should have a spring to close it. The door “a” would have both an Entry and Exit reader, so an Anti-pass back/Anti-tailgate can be implemented. The strike on the door “a” would normally be energized and opened by a valid reader transaction.   The bolt on the gate would be normally de-energized, allowing the gate to open freely. When the strike on the door “a” is de-energized, the bolt on the gate would be energized, preventing the gate from opening. This is designed to allow only one person to simultaneously move into or out of the Zone.   An added level of security would be accomplished by mounting IR emitter/receiver pairs along the low wall or fence at regular intervals. A person would interrupt the light at a limited number of receivers, so if more than expected are interrupted, it would violate one person at a time, and necessary action could be taken.   If material needed to be moved through the door, the gated area could be made large enough to allow for a dolly or whatever might be needed. A different access level would be provided to those who are moving material, thus preventing the alarm for too many people going through the door.   This approach would restrict movement into and out of the Zone, and the example given in the AIC note could be implemented to allow real-time monitoring of occupancy levels in the Zone.   Design thoughts:   To calculate whether more than one person is in the gated area, sum the number of receivers that are detecting and compare it to a minimum, e.g., four of six must be detecting if only one person is in the area. If material is in the gated area, generate an alarm if an authorized card is not read. Use the alarm delay for the point to give an individual time to make a card read before sounding the alarm. The AIC scheme described in the AIC note would have to be duplicated for the material mover individuals to change the calculation of a person in the gated area. For material movers, the detection would be (sum of detectors < minimum), whereas for regular individuals, the detection would be (sum of detectors > minimum). Remember, the SLI connected to this door can have only 64 AIC’s and this door now has used 2 of them. Use an inter-card delay long enough to let the person exit the gated area before another card can be read. For personnel safety, there must be a way to de-energize the strike. One method would be to mount an emergency exit button located far enough away from the door so a single person could not reach it and a second emergency exit button on the outside of the Zone so someone could keep the strike de-energized until everyone is evacuated. Most codes probably require that all strikes be de-energized in case of smoke or similar emergency to provide another fail-safe.   Here is a pdf document which explains the setup using an SCU Click here to download third-party ManTrap information.

Issue How do I read unsigned 8-bit (byte) values from a Modbus holding register and represent the analog value in Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In this case, the Modbus holding register is a 16-bit unsigned value that is used by the Modbus device to represent two individual 8-bit values.  The 16-bit unsigned value is an integer with a range of 0 to 65,535 and needs to be converted into two analog values. Resolution Use a Building Operation Modbus Analog Input Point for each value required.  Each object will be configured to read the same Modbus register address with the bitmask value applied before evaluating the value to determine the output. For example: Read Modbus holding register 40001 which is a 16-bit unsigned value and decode as two analog values. Under the Modbus device object - create a Modbus Register Group Under the Modbus Register Group - create two Modbus Analog Input Points Configure each point as follows: Modbus Analog Input Point 40001 (AI-HighByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 8 through 15 Modbus Digital Input Point 40001 (AI-LowByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 0 through 7 Additional information can be found in the Building Operation Technical Reference Guide - Modbus Point Configuration (Bitmask) or WebHelp at Point and Value Configuration

Issue After updating FireFox to version 34 and later, you get the message "Unable to Connect Securely" when accessing a Xenta Server using HTTPS   After updating Chrome to version 40 and later, you get the message "This webpage is not available" when accessing a Xenta Server using HTTPS   In Internet Explorer, you get the message "This page can't be displayed" when accessing a Xenta Server using HTTPS Product Line TAC Vista Environment Xenta Server FireFox Chrome Internet Explorer Cause From version 34 of FireFox and version 40 of Chrome, SSLv3 is disabled by default for security reasons as SSLv3 is no longer considered secure enough. As per Vista Server Cryptographic Protocols TAC Vista, TAC Xenta Server and TAC Xenta 911 is using SSLv3 and is therefore blocked when using SSL (HTTPS). In the newest versions of Chrome and FireFox, not even the work around described below works, so you need to set the Xenta Server to low security through the XBuilder project. Resolution In Internet Explorer, FireFox and Chrome you can manually reenable SSLv3.   Solution 1: Set the Xenta server to only use HTTP and not HTTPS This is done in TAC XBuilder   Solution 2: Allow SSLv3 in FireFox 1: In the FireFox address bar, write about:config 2: Accept the warning 3: Write security.tls.version.min in the search field - below you can see the default setting 4: Double click the line, and change the number to 0 5: Try logging into the Xenta Server again. If it doesn't work the first time, restart the browser and try again   Solution 3: Allow SSLv3 in Internet Explorer Check the advanced settings in Internet Explorer. SSL 3.0 must be enabled. If it's not, then enable it. If you can't, it's because it's disabled by a policy, and you need to get the IT department to enable it.   Solution 4: Allow SSLv3 in Chrome 1: In the Chrome address bar, write chrome://flags/#ssl-version-min and select SSLv3 in the drop down box. Solution 2: Allow SSLv3 in FireFox 1: In the F

Issue How to use AutoCAD layout in TGML Graphic Product Line TAC Vista Environment Vista 5.1.9 and earlier versions of Vista 5 TGML Graphic AutoCAD Cause Sometimes it is necessary to use the AutoCAD layout in TGML graphic, for example, to use the plant layout as a background. The official support for importing AutoCAD files was removed early in the life of TGML. It can’t be guaranteed that EVERY file will import without a problem, so it is an unsupported feature. Resolution The following steps need to be followed: Open the drawing in AutoCAD Save as .DXF Open TGML Editor File Open the .DXF A screen should pop up saying converting DXF to SVG followed by converting SVG to TGML It is recommended to use the "Create path" command in the Object window in TGML for the converted graphic. Because the response speed of the computer will be very slow if used without this action. Note: Line widths and text will be in disorder because they are not imported along with the object. If the DXF file fails to import, here are some steps to try: Move every object in AutoCAD to a single layer Delete all unused layers in AutoCAD "Explode" complex objects in AutoCAD

Issue How do you define the number of decimal places displayed for a point? Is it possible to change the number of decimals displayed in WorkStation / WebStation? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation  Cause The operating system's regional settings determine the default resolution for decimal places displayed. This value cannot be modified within WorkStation; however, the regional settings in WebStation can be adjusted to show the desired number of decimal places. Resolution This setting applies to all displayed values except graphics, where the graphic editor can define the number of digits displayed.   WorkStation Open Control Panel Select under Clock and Region - Change date, time, or number formats As shown in the screenshot below, select Additional Settings [1]  Then adjust the Customize Format "No. of digits after decimal to your requirements" [2]. Restart WorkStation if already opened. WebStation  From the User Account drop down Select Settings Select Regional Change the Decimals from Auto to the desired number (0-6) required in WebStation.  Click Save Log off/on to WebStation to see these changes.   

Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site with at least one ES or AS Cause A good example of when multiple email addresses are required for alarm notifications is a facilities staff. You may need critical alarms to go to several people at once to make sure they are handled in a timely fashion. Note: Consider configuring Building Operation to email a distribution list as opposed to several email addresses. That way the IT department can handle making changes without having to access the building control system. Resolution in the email address field of the Email Notification, addresses should be separated with only a semicolon. No space is permitted between the addresses. Note: This will not work from Webstation, only from Workstation. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com

Issue Can B-Link repeaters be used with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site release 1.xxx and higher Cause Need to add repeater(s) for EcoStruxure Building Operation Resolution For communication using RS-485, the versions of B-Link BACnet MS/TP Repeaters repeaters shown below were tested and passed for EcoStruxure Building Operation use. Part Number Description B-LINK-AC BACnet MS/TP Repeater, 120/240VAC B-LINK-AC-OP BACnet MS/TP Repeater, 120/240VAC, open class no enclosure B-LINK-AC-S B-LINK, AC, SMK B-LINK-DC BACnet MS/TP Repeater, 24VDC B-LINK-DC-OP BACnet MS/TP Repeater, 24VDC, open class no enclosure B-LINK-DC-S B-LINK, DC, SMK B-LINK-F-AC B-LINK, AC, FIBER B-LINK-F-AC-S B-LINK, AC, FIBER, SMK B-LINK-F-DC B-LINK, DC, FIBER B-LINK-F-DC-S B-LINK, DC, FIBER, SMK   Note the supported cable diameter in microns: 62.5/125. The first number, 62.5, refers to the diameter of the fiber cable's core. The second number, 125, refers to the diameter of the outside of the fiber cable's cladding. For more information see: BACnet b-Link MS-TP Repeaters - Andover Continuum - Specification Sheet b-Link Series - Andover Continuum - Installation Sheet Additional information about Fiber diameters from The Fiber Optic Association Fiber cabling information for an Infilink i2210 and the B-link-F Series

Issue Unable to connect to a BCX configuration page Product Line Andover Continuum Environment Continuum BCX9640 and 4040 Cause 404 Page not found error accessing the configuration page using the controller IP in a browser Resolution Note: This document is for troubleshooting help, it is not a comprehensive BCX setup guide. Please refer to the BCX1 Technical Reference for detailed setup instructions.   Using a LAN or a cross-over cable? If the BCX is on a LAN and was working before, remove the LAN cable from the BCX and try to ping the BCX. If you get a response then you have a duplicate IP. Same subnet? Make sure DHCP is disabled on your computer. Use a straight-through or cross-over cable to access the BCX directly. Has this cable been used successfully before? Reset the BCX to the default IP. The button is under the cover, top right. Be sure to hold down the IP reset button for about 20 seconds Is the controller in bootloader mode? This can be seen by observing the CPU light flashing rapidly, approximately two times a second (2 Hz at 50% duty). Flashing the application through Cyberstation may fix this and enable you to get back into the controller. Even though access to the config page is not available, the update OS button in Continuum using the controller's Network setting and ACCNet ID may be accessible to perform a firmware upgrade. Ping the IP from a DOS prompt, can the BCX be pinged? Ex. Ping 169.254.1.1 Use Ipconfig /all to see your PCs network settings. The best case scenario is to be on the same subnet or connect directly. Are there multiple NIC cards on the PC? (Ex. Ethernet and wireless on a laptop) Disable the wireless adapter or other adapters. Continuum does not support a multiple NIC card configuration. Run Wireshark to get a capture between the BCX and The PC. Remove power from the BCX and reapply power. When the BCX starts it sends a gratuitous ARP that will indicate the IP address within the BCX. It may be a different IP than expected. Did the issue of not accessing the web page happen after a power outage? Is the CPU light flashing amber and it was flashing green before and no one has flashed the controller? Is the CPU light solid amber? If so, contact support for assistance.

Issue There is currently no summary KB article for all the data collection available in EBO systems. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Identified the need to review data from EBO to analyze performance or issues. Resolution Purposes for Data Collection Provide visual information about the issue Screenshots (from Windows Snip & Sketch or other tools) Video Capture or Mobile Device Video Device LEDs, provide any information about them and when they change. Provide information about your configuration/installation Network devices, including routers, switches, and any configuration you can provide BMS Routers Site Topology, including all devices included in the communications path Provide server (EC/ES/AS) XBK backup Configuration only is smaller and useful when investigating configuration, bindings, and/or programming All Data is larger and recommended when need to see trends or events to help investigate the issue's timeline. Provide any information to replicate the issue. Provide as specific as possible steps used to create that outcome Provide VERSIONS of ALL software, hardware, and protocols involved If submit any captures or logs, perform the following: Provide any steps performed in EBO during the capture or log with the date & time, so these events can be matched.   Servers (EC/ES/AS) Collect logs from an Automation Server Collect logs from the Enterprise Server and Enterprise Central Backing Up EcoStruxure BMS Servers Manually  (Configuration Only or All Data) Server Fieldbus Protocols Infinet: Gathering Trace Log information for the Infinet bus in EBO Lon: (Video included) Analyze Lon communication using trace log in EBO Modbus: Capture a Modbus trace log in EBO/SBO   Software EBO Webstation Collect EBO Webstation browser logs EBO Workstation Collect EBO Workstation logs EBO Project Configuration Tool (PCT) Collect log files from Project Configuration Tool (PCT) Windows Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Wireshark For extended period capturing, use this article to set up a Ring Buffer in Wireshark. Wireshark capture ring buffer for continuous capturing Hardware b3/Infinet Controller Collect log from a b3 or Infinet controller BACnet/IP Controller Workstation method - BACnet/IP Controller Diagnostics Building Commission method - Viewing and Exporting Diagnostic Files (WebHelp) or Viewing Diagnostic Files (YouTube)   Protocols & Electrical Interfaces Ethernet Capture any ethernet traffic, including IP: Using WireShark to analyse communications on an Ethernet network Capture Loopback (127.0.0.1) traffic between applications and/or servers running on the same host OS: How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues Lon Using Loytec LPA with SpaceLogic Server AS-P RS-485 Fieldbuses include BACnet MS/TP, I/Net, Infinet, Modbus RTU BACnet MSTP Capture Application - Communities (se.com) aka mstpcap.exe BACnet - PicoScope Basics Picoscope Configuration for Modbus RTU capturing and decoding

Issue What is the process to replace a CX9400 with a CX9680 NC2? Product Line Andover Continuum Environment Upgrading a CX9200, CX9400 Eclipse, CX9900, CX9940 to a NCII Netcontroller. CMX9924. Model Number, Type change. Cause Where can I get the process to upgrade my obsolete CX controller. Resolution Cyberstation V1.74 SP2 or above is required to support the upgrading process of a CX9200, CX9900 and CX9940 up to a Netcontroller 2. The upgrade process for this is detailed in Appendix B or the NetController II Operating and Technical Reference Guide. For the CX9400 Eclipse controller they require a minimum of V1.91 to support the upgrade. For the older versions of Cyberstation that do not support direct upgrading of a model number, you will need to bring the Netcontroller II on line as a new controller, then in offline editing copy /paste (or Drag /Drop) all objects over to the Netcontroller II. Then go online and fully reload the Netcontroller II and any connected Infinet controllers. The old controller can then be deleted from the system. The objects could also be copied over using edited ASCII dump files if you prefer that method, but either way you may still have to re-animate your Pinpoint graphics unless you upgrade to a version that supports the Netcontroller II replacement. NOTE ACC-LON RS-485 and ACC-LON FTT-10A protocol options A CX9900 may be labeled CPU-8M and a CX9940 labeled CPU-4M. Later CX99 models may have FT added, eg. CPU-8M-FT When replacing a CX9900 or CX9940 it is vital to know if it requires an RS485 or FTT10 IOU module port (if this port is being used) as this CANNOT be modified on site. See article titled No response from I/O module when learning in an IOU This process cannot be used to upgrade the CMX9924 controllers.  The available range of Netcontroller II controllers available has recently been reduced, see PA-00535 "Andover Continuum Offer Optimization"

Issue Cannot bring controller online in Continuum even though all settings are correct. Unable to browse to that controllers configuration webpage but can ping the controller. CPU LED blinking approximately two times a second (2 Hz at 50% duty). Product Line Andover Continuum Environment bCX40xx bCX96xx b3xxx i2xxx Cause The controller is in bootloader mode and has lost its application program. Resolution If the bCX is in bootloader mode, with the CPU LED blinking approximately two times a second (2 Hz at 50% duty), then there are a couple things you can try to do to get the controller back online before sending it back for repair. Basically it has lost its application program and dropped into bootloader mode. Try to uprev the controller with its application firmware to see if that will bring it back online. Attempt to uprev (Update OS) the controller from its device object in Continuum even though it may not show as online. Alternatively uprev the controller using the RoamIO to send the application firmware to the controller. If neither of these options work the controller must be returned to be repaired through your normal RA procedure for your region. (this option may no longer be available, due to the age of the controller) Note: An error code including 6818(hex) (c2026818 has been seen) or 26648(dec) during an attempted download or on a graphic. Example1: Example 2: See a Quick time movie to indicate CPU light modes for controllers that shows the various stages of the CPU LED blink rate.

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue Blinking red lights Solid red lights Blinking orange light Blinking green light Solid green light Environment Xenta Server Controllers 511, 527, 555, 701, 711, 721, 731, 911, 913 Cause The indicator lights on the face of the Xenta Server controllers can help explain the state of the controller in many different situations. Resolution A number of light-emitting diodes (LEDs) on the Xenta device indicate that the application program is running and when communication is in progress.    Fig. 1: LED diagram on the Xenta Server device.   Table1: LED description on the Xenta Server device.     Position Description 1 Neuron status indicator • Off – Normal mode • Red, blinking – Unconfigured mode • Red, steady – Hardware fault 2 Serial RS-232 B port activity indicators: • RX – Indicates that data is received • TX – Indicates that data is transmitted 3 Overall Run indicator • Green, steady – Normal mode • Green, blinking – Start mode • Red, steady – Fail-safe mode (see    description below) • Red, blinking – Unit fault 4 Serial RS-232 A port activity indicators: • RX – Indicates that data is received • TX – Indicates that data is transmitted 5 Serial RS-485 C port activity indicator. 6 Ethernet 10Base-T activity indicator Note • The LEDs for the RS-232 A interface (position 4) do not indicate communication when using the RS-485 A interface although internal port A is used for both.               Fig. 2: Internal serial ports and RS-232/485 interfaces.

Issue SE8000 Best Practices Product Line Field Devices, EcoStruxure Building Expert Environment SE8000 Cause Best Practices for commissioning SE8000 room controllers Resolution The following information has been contributed by a field engineer and their experience to assist others in commissioning the SE8000 device. It brings together or provides leads to various articles that can be found on the Download Center. SE8K Programming Tutorial v1.1

Issue Clicking on a URL in Workstation gives the error message "Navigation to the webpage was canceled". Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The website owner has added additional code to prevent their webpage from being displayed in a 3rd party application e.g. EBO. However, the webpage can be viewed in a web browser e.g. IE, Chrome or Firefox. This additional measure makes use of a feature called X-Frame-Options and is used to prevent 'clickjacking' and prevents embedding in other websites. In 2009 Internet Explorer 8 introduced a new HTTP header X-Frame-Options which offered partial protection against clickjacking and was shortly after adopted by other browsers (Safari, Firefox, Chrome and Opera). The header, when set by the website owner, declares its preferred framing policy: values of DENY, SAMEORIGIN, or ALLOW-FROM origin will prevent any framing, framing by external sites, or allow framing only by the specified site, respectively. See Mozilla article for further information. Resolution If a web site implements the usage of X-Frame-Options to limit which other web sites it can be embedded into, there is nothing to be done about that. It is the providers' decision, and cannot be circumvented. In Building Operation release 1.9 and later, there are two global policy settings used to protect Building Operation presented web content, so it is resilient against clickjacking. Option 1 - Enable external content to be embedded in WebStation This option must be selected to permit another web page to be rendered in a WebStation <frame> or <iframe>. To protect against clickjacking for all use cases, this option should be turned off. Option 2 - Enable WebStation to be embedded in another site This option permits Building Operation web pages to be rendered in a <frame> or <iframe> from the local server. If this option is selected with option 1, then there is no protection against clickjacking. The most secure and recommended configuration is when both options are turned off. However, when an application requires embedded web content, one or both these options can be turned on. Since this is a global policy, these settings will affect all embedded content. If only some content is required to be embedded then there is no solution or workaround within EBO unless the website owner can remove or change this feature.

Issue Belden Cables for LonWorks Networks Approved LonWorks cables Product Line EcoStruxure Building Operation,Satchwell, MicroNet,TAC IA Series,TAC Vista Environment LonWorks networks TP/FT-10, TP /XF-78 and TP/FT-1250 Cause The Echelon document 'Junction Box and Wiring Guideline for Twisted Pair LonWorks Networks' indicates Belden 8471 and Belden 85102 as the recommended cables from Belden for LonWorks networks. These may not be available from the local Belden office or the Belden distributor. Resolution Refer to Belden Technical Bulletin TB 102E 'Belden Cables for LonWorks Networks' for a list of Belden cables suitable for LonWorks communications. Take note of the difference in cable drop length and total cable bus length for the various cable models listed.