Building Automation Knowledge Base

Issue Unable to activate the AD-Link on a SmartX Advanced Display Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V1 Building Operation Advanced Display V2 Cause Changes to the license server made current AD-Link software inoperable Refer TPA-SBO-17-0009.00 for details about the issue Resolution Note: Advanced Display V1 is discontinued. Effective July 31, 2023, Service Support for Advanced Display v2 will also be discontinued. The licensing server responsible for activating AD-Link and Kiosk features will be decommissioned. After this date, no new Advanced Display v2 could be commissioned as the mentioned server will be decommissioned. Advanced Display V3 can replace it. Refer to: PA-00923   The issue is solved in a new version of AD-Link To install a new version of AD-Link, there is a need to first uninstall the old version of AD-Link Go to the settings page on the SmartX Advanced Display Tap on "General" Tap on "Security" tab Tap on "Device administrators" Un-tick the AD-Link Uninstall the old AD-Link app   You will first need to uninstall the old version of AD-Link. To uninstall the old AD-Link you will need to un-tick the AD-Link in the device administrators tab,   In the settings page you will be able to go to the "General" tab and then "Security" tab, then "Device administrators"  In there you will see the AD-Link, untick it.  You should now be able to uninstall the old AD-Link app You will first need to uninstall the old version of AD-Link. To uninstall the old AD-Link you will need to un-tick the AD-Link in the device administrators tab,   In the settings page you will be able to go to the "General" tab and then "Security" tab, then "Device administrators"  In there you will see the AD-Link, untick it.  You should now be able to uninstall the old AD-Link app

Issue Modbus XDriver for BCX1-9640/4040 (ModbusRTU_bCX_xxxxxxx.xdr) on comm2 for RS-485 does not work even when the comm2 port says that the driver is installed, no errors and the comm parameters match the Modbus protocol device (ie, 19.2k, n, 8, -). Product Line Andover Continuum Environment bCX1-9640/4040 Controller Modbus XDriver Cause Check the Communication Configuration Point (Function Code 99) of the XDriver. Resolution Function Code 99 is used to select between RS-485 and RS-232 when using a bCX1-9640/4040 controller with Modbus XDriver installed in Comm2 port. Unlike the Modbus XDriver for CX ModbusRTU_2xxxxxx.xdr), the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) requires user to set correct value to the FileNumber attribute of Function Code 99 (Communication Configuration Point ). If the FileNumber attribute of the Communication Configuration Point is not set to "1", the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) uses the default value, which is "0". When the FileNumber attribute is set to "0", the Modbus XDriver for BCX1-96404040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-232. When the FileNumber attribute is set to "1", the Modbus XDriver for BCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-485. For detailed information, refer to the Modbus RTU XDriver User Guide on page15: Function Code 99 – Communication Configuration Point.

Issue Example programs for the xP Display and LD-1 Product Line Andover Continuum Environment XP Display LD-1, LD1, LD 1 ACSM Cause Need example code for these displays to act as a starting point for programming  Resolution example programs for the xP Display.  example programs for the LD-1.  Note: These applications were developed by a UK branch and should be used as a starting point for your specific application. Further information on the programming of these displays is available in The Exchange Download Center for the specific devices. xP-Display Installation and User Guide LD-1 Installation and User Guide

Issue Lost Entitlement ID when you want to rehost/return/modify existing license. Product Line TAC Vista Environment Vista 5 Cause When a rehost/return/modify of an existing license is required, the Entitlement ID is required. Resolution Contact support and provide the current Host ID (PC MAC address) /Dongle ID used, alternatively the current license file or Fulfillment ID. The directory that the License file is located in can be found using the License Setting tool. Support will then provide the Entitlement ID for license in question.  The Entitlement can also be found providing the original Purchase Order ID to the order entry department at 1-888-444-1311 if in the continental US.

Issue During step 9 of How to replace a Xenta controller in a LNS network it is possible to receive a warning with the following information: Warning: The device has no application file (MTA file) thus disabling the possibility of a download of application and parameters to the device. Please download via serial port any application file (MTA file) of your choice by using Menta before attempting to download to this device again. Product Line TAC Vista Environment Programmable Controllers 281, 282, 283, 301, 302, 401 & 401:B Cause Attempting to install a Xenta programmable device that does not have a Menta Application loaded into controller. NOTE: A new controller out of the box should have a simple MTA Application already loaded.  However, if you receive the warning above your controller may not have any Menta file and loading any simple Menta file (i.e. one PVR block) will suffice. Resolution You will need to direct connect to the new controller with a RS-232 cable to upload any simple Menta application (i.e. one PVR block) before the Vista System Plug-In will properly communicate and download the new controller.  The System Plug-In will not communicate with an applicationless device.

Issue Web pages opened in TAC Vista Workstation is shown in compatibility view. That might have unwanted impact on some web pages. Product Line TAC Vista Environment TAC Vista Workstation Cause By default TAC Vista Workstation will use the newest version of Internet Explorer installed on the PC, but enable compatibility view. That might have unwanted impact on some web pages. Resolution Add a registry entry to define what version of Internet Explorer you want TAC Vista Workstation to use. Navigate to the following registry key: 32 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] 64 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] Add a new DWORD (32 bit) value Give it the name "TACVistaExplorer.exe" Give it the decimal value 11000 to set Workstation to use IE11 This ZIP file contains registry imports that will set the browser used to IE9, IE10 or IE11

Issue In a Vista system how do you get alarm sounds on only selected alarms Product Line TAC Vista Environment Vista 5.x.x Cause It is not clearly defined how to associate alarm sounds to a specific set of alarms. Resolution To add alarm sounds to specific alarms in Vista follow these steps. Locate the alarms that are required to sound and alarm at the PC. Set a unique ID that will be able to be filtered on. A good example would be use a unique alarm priority. Priority 7 has been used in this example. Add a new Alarm Viewer in Your Vista  Database. Right click on the new Alarm Viewer and select properties then select the Alarm Priorities tab. Add the priority 7 to the viewer. This will allow only alarms with priority 7 to be displayed in this viewer.   Then set that Alarm Viewer to sound on an alarm. In the new Alarm Viewer right click in the alarm area and select customize. Then select the Miscellaneous tab and check the Alarm Buzzer option. This will result in a new alarm viewer that only receives priority 7 alarms and will trigger the alarm buzzer when an alarm is received. This Alarm Viewer will need to be added to the program settings of the user. To change the alarm sound use the Window's Sound option (found in Control Panel) and locate the Vista alarm sound. You can then browse to a new sound if required. A tool has been developed to streamline this process: TAC Vista Alarm Notifier

Issue It is unclear if the included client licenses work the same as WorkStation Standard or WebStation licenses when adding an Editors license (SXWSWEDIT00001). Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Cause It is unclear if the Editor license can work with the included licenses that come with Enterprise Server or Enterprise Central. Resolution The Editors license can be added to the included licenses and allow programming and graphic editing 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.

Issue Where to find the domain ID of a LonWorks Network underneath a LonWorks Interface in a Building Operation network. The domain can also be changed in this same location. Product Line EcoStruxure Building Operation Environment Building Operation workstation Cause If the domain ID of a LonWorks network needs to be changed or known for some reason it can be done through the properties of the LonWorks Network. Resolution Right click on the LonWorks Network underneath the LonWorks Local Interface. Click Properties. Click on the Advanced tab and look at the Domain table for Network Interface. The value in the first row of the ID column is the domain ID in decimal form. In order to change the domain ID, use the Addressing entry field "Domain ID Length" to enter the new Domain. Click OK.

Issue LonWorks point count recommendation for the Xenta 5/7/9xx series controllers What is the device limitation on the FT-10 LonWorks channel installed on a Xenta Server Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause The load point table can be found in Vista version Release Notes on The Exchange Download Center. When Xenta 700 was released the Product Announcement had a table with the recommended number of LonWorks devices attached to Xenta 5/7/9xx. Below you can see a small revision of the recommendations. The list applies to devices which the applications in the Xenta 5/7/9xx are interchanging data with. Other devices that are completely handled by TAC Vista through the LTA port of Xenta 5/7/9xx are not included in this calculation. These devices will influence the LonWorks network performance in a similar way as if they were connected through a Xenta 911 and have to be considered. Not following the design recommendations and adding too many LonWorks devices to a single channel will cause poor Xenta Server performance. Resolution Each device uses "load points" according to the table. As a general guideline the total "load points" on the network shall stay under 100 to get a reasonable performance. In reality the e.g. intensity of the traffic also has an influence as well as, of course, the expectations on response time. Type of device Load points I/O module 5 Xenta group master 280/300/401      20 Additional Xenta 280/300/401      in the group 2 Standard LonWorks device, including Xenta 100, polled 2 Standard LonWorks device, including Xenta 100, bound 0.75 Refer to The Exchange Download Center for future releases of Vista / Xenta Release Notes containing software and updated load calculations This information is usually found in the Appendix B - Engineer Information, and look for section titled LonWorks recommendation for the Xenta 500 and 700 series

Issue Controller labelling and documentation does not describe how to connect expander modules or which modules are supported. Product Line EcoStruxure Security Expert Environment Security Expert SP-ACX SP-ACX-V2 SP-O8 SP-I16 SP-MRDM2 SP-RDM2 SP-I01 SP-IO84 SP-MI16 Cause Documentation is scheduled to be updated but due to UL certifications for some of these documents the process may take some time to complete. Resolution Expander modules are able to be connected to the SP-ACX and SP-ACX-V2 controllers. There is no restriction to the type of Expander Module, all modules are supported unless specifically stated that they are not. The Expander Module network is connected to the RS-485 port on the right-hand side of the controller just above the Digital Outputs port. This port should be labelled with N+, N-, NA, NB and is to be wired up as per the below diagram. Expander Module RS-485 port

Issue Steps for Troubleshooting Readers Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Readers are offline or not returning the correct card data Resolution Common Issues Issue Solution My reader is not returning any data when I present a card Check to make sure the technology card you are using matches the requirements of the card reader. A prox card will not work on an iClass reader. Check the Reader wiring to confirm CLK and DATA on wired correctly. Check that the Reader addressing matches the reader port. Check the power being supplied to the reader. Multiclass readers cannot be powered off S2 (green boards). They require an external power supply. Bluetooth readers cannot be powered off the S2 (green) boards. The power required by the Bluetooth readers is directly related to the range at which the Bluetooth readers are programmed to work. My reader is returning different results every time I swipe my card. Check the power to the reader. If the reader requires more power than the board can provide, use a dedicated power supply. My reader is returning the correct number of bits but the encoded card information is incorrect. Check to make sure your CLK and DATA wires are not switched. If the CLK and DATA wires are switched the 0's and 1's will be inverted causing the card number reported to be wrong.  My reader is returning the correct number of bits but the raw HEX data is all 0's.  This is most often caused by a bad reader or a bad port on the Mercury board. Check the reader wiring and power first, then try the reader on a different port.    My EP1501 uses the Reader 1 port for my SIO, how do I utilize the on-board reader? The on-board reader for the EP1501 is placed on the internal port and is physically placed on Reader 2 (TB3); it should still be addressed as reader address '0' in Feenics. I wired my reader to Reader 1 on the board, what's my reader address? All reader addresses are -1 from the physical port the reader is wired to. Reader wired into Reader 1 is address 0. I don't understand what to set my offline access method to. No Change: Reader access will remain in the 'Online Access Method'. Facility Code Only: Only the facility code is required to receive and access granted event. Unlock: The reader will unlock during its offline state. Lock Down: The reader will be locked down during its offline state. OSDP Reader goes offline when I select 'Secure Channel'. From the top menu bar select 'Start Linking Mode'. The OSDP reader will come back online. Please Note: The OSDP reader must be new or never have been configured for Secure Channel previously. If it was previously configured for Secure Channel it will need to be reset with a config card. My Engage NDE/LE lock is showing a Magnetic Tamper Follow the manufacturers instructions to calibrate the door sensor. My reader is posting "Access Granted - Not Used" events. This can happen for two reasons. First, the cardholder badged at the door but never opened the door to enter. Second, the door does not have a door contact wired at the door and one is programmed into the system. Since there is no device telling the system if the door was used, the system reports no door use. My reader is posting "Access Denied" events immediately after "Access Granted" events. Whenever troubleshooting event data always be sure to expand the event message to learn more. If the event is returning data is without a card read following the first access event, it suggests there may be power coming back into the comms, or are sending feedback into the comms loop. You can test this by Does removing the load (pull the output/strike) oof the terminal render the same results? Is there any change when placing the reader directly onto the Mercury board? A thorough investigation of the power wiring on the board will help isolate the location of the issue. My reader is posting "Access Denied - Incomplete Card or PIN Sequence" The Card and PIN reader mode requires a valid PIN sequence followed by a valid card read. The Incomplete Card or PIN Sequence can occur Only the card was presented to the reader. Only the PIN Code was entered at the reader. The card was presented before the PIN code was entered. Keep in mind, if someone enters a random PIN sequence at a reader and happens to guess a valid PIN but does not present a card, this event will show. The reader is producing an "Unidentified Person on Site" event. This event is produced when a controller grants access at a reader to a cardholder that is on the controller database, but that is not currently within the Feenics Database. This can happen if a controller missed an event when a person was deleted from the database. The system will delete this card from the controller after this event. The next step is to identify the person and remove them from the building. The reader is posting "Access Denied - Invalid Facility Code" but showing the correct Facility Code in the expanded event data. This can occur if the Card Format programmed with the appropriate Facility Code on the controller does not have the correct parity bits for the card being used. The Mercury Service checks the Card number, the Facility Code, and the parity bits in that order. Due to this, when creating a card format, the parity bit is often the last part of the Card Format to be checked. Access Denied - Card/Pin Not Found The User does not have access to the door. Add the User to the door through an Access Level    

Issue Unable to bring interfaces(downstream devices) online, showing as unknown Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or On-Premise SSC (Security System Controller) Downstream controllers Cause Offline interfaces can occur under a number of circumstances, below are the most common reasons. The controller is not yet active. Once all interfaces, readers, and I/O have been added, it’s important to remember set the device as active. Interfaces were added to the controller after it was made active. The controller requires a reboot to download the correct configuration. Dipswitches and addressing on the board may be incorrect Check Wiring  Resolution Go through the following steps to get interfaces online Set the device as active (Go go back to the controller page ) Reboot the controller (containing the interface) Check that the DIP switch settings are correct on the controller (see the Mercury hardware manual) Switches 1-5 on an interface module set the address in binary, this means 32 addresses are available (0-31). Users must set the correct address inside Access Expert that matches the DIP switch value. Switches 6 & 7 set the Baud rate, both on for default 38400. Switch 8 should be off to disable AES key encryption. (Communication is instead encrypted over TLS 1.2) Note: The orientation of the DIP switches may be upside down compared to some labels on other connectors, so it's easy to have everything inverted. On this MR52 board, the On label on the connector is DOWN. These dip switches are configured for address 0, baud rate 38400, and no encryption. Check wiring Ensure that the panels are wired correctly. Verify your RS485 communication and refer to the hardware installation guides Verify End of Line Termination Verify End of line termination jumpers are set, refer to hardware installation guides

Issue When a remote I/O module goes offline the JACE will show an "NA" for the analog inputs but the binary inputs from a remote I/O module still show maintain their last value. Product Line TAC IA Series Environment I/A Series MNB 1000-15 I/A Series JACE Cause The BIs from a remote I/O module that is offline are going to an "NA" status if viewed from WorkPlace Tech.  At the JACE an "NA" received from a BI object will be interpreted as a "fault" and the object will show its last value and turn orange to indicate it is in fault. Resolution When a Remote I/O module is off-line its AI and BI outputs will show as NA in WorkPlace Tech. At the JACE an "NA" received from a BI object will be interpreted as a "fault" and the object will show its last value and turn orange.  The BI can be set up to annunciate an alarm based on the fault condition in the JACE if necessary.

Issue When the remote I/O modules (MNB-1000-15) are powered for the first time, the status LED stays blinking red. Product Line TAC IA Series Environment I/A Series MNB 1000 -15 Cause This is a normal operation. Resolution When the associated MNB-1000 receives a database configured with remote I/O modules, it will initiate communication with the remote I/O modules. If it is successful, then the status LED with turn green.

Issue Following an attempt to update firmware, some MNB MS/TP controllers appear to be in a locked-up condition (ie: the status LED is red and blinking). Product Line TAC IA Series Environment I/A Series MNB controllers Cause The device was interrupted before completing the update, which cause the controller to be in bootloader mode. Resolution To perform a successful firmware update it is imperative that once the update has been initiated it must not be interrupted until complete. A successful firmware upgrade must be completed to get the controller out of bootloader mode. However, in most cases when this issue occurs the unit is no longer displayed in the WorkPlace Commissioning Tool device list.  Therefore it cannot be selected for an upgrade. To get the unit to show up in the list, it must be added as an MS/TP slave. This is done under the WorkPlace Commissioning Tool menu selection: File – add MS/TP Slave. The network number and the controller's MS/TP physical address must be known. Once defined as a slave it will appear in the list and can be selected for a firmware upgrade. Note: If a controller shows up in MS/TP slave mode and indicates it contains the latest firmware it will be necessary to downgrade it to the previous firmware version to recover the unit and then upgrade to the latest firmware.  To downgrade the firmware in an MSTP device open its Device Properties, go to the Firmware tab and click on "Update firmware".  On the Update Firmware window check the box next to "Check here to preview or modify the updates to be applied and click "next".  On the Update Details window click on the change button and a window with available firmware versions for that controller will be displayed.  Select the "bin" file for the previous firmware revision and click on the Open button.  Now click on the Start Update button to perform the firmware downgrade.  If successful the controller will show up in the WPCT device list and can be upgraded to the latest firmware. If suspect communications are what caused the update failure, it must be remedied prior to attempting another update. Once a successful firmware update has been completed the unit will boot normally.  The status LED will be green and it will appear in the Device list.

Issue The MNB-70 firmware upgrade displays version v1.130 during the upgrade process when upgrading to v1.430   The firmware included with WorkPlace Tech 5.8.5 will display the correct filename (MNBU70-01430.bin) however the version will indicate v1.130 within the WorkPlace Tech Commissioning Tool. The firmware included with the MNB Series v1.430 Firmware Pack extractor will display an incorrect filename (MNBU70-01130.bin) as well as indicate v1.130 within the WorkPlace Tech Commissioning Tool. Product Line TAC IA Series Environment I/A Series MNB 70 I/A Series WorkPlace Tech 5.8.5 I/A MNB Series v1.430 Firmware Pack extractor Cause An incorrect version of firmware for the I/A Series MNB-70 controller has been included with the WorkPlace Tech 5.8.5 distribution and the MNB Series v1.430 Firmware Pack extractor both released in mid-July 2013. Resolution Replace the existing MNB-70 firmware file with an updated version: Locate and delete the existing MNB-70 firmware files (where applicable): MNBU70-01130.bin MNBU70-01430.bin The firmware files are typically located … Windows XP \Documents and Settings\All Users\Application Data\WorkPlace Tech\Firmware Windows 7 \Program Data\WorkPlace Tech\Firmware Download the updated MNB Series v1.430.A Firmware Pack extractor from The Exchange Download Center: MNB Series v1.430.A Firmware Pack - BTL Compliant.exe Execute the extractor and the files will be extracted to the firmware directory for use with the WorkPlace Tech Commissioning Tool.

Issue After importing a new template into AET, the different folders and objects are all different colors. What does each color represent? Product Line EcoStruxure Building Operation Environment AET Folder View Cause Each color indicates a different status for the object. Some must be resolved before proceeding and others are information only. Resolution Below is the list of the different status colors and their meanings:  Red – Duplicated object. This must be corrected. Green – Existing folder. Orange – Folder with duplicated object below. Black – New object or folder. Blue – Existing object in EcoStruxure system tree Brown – Device that will be created automatically by AET Light Blue – Empty IO Channel

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.