Building Automation Knowledge Base

Issue Is the I/A Series product line compliant with federal regulations on being "American-made"?  Is there documentation to support it?  This must include the MNB and MNL controllers, the Niagara UNC and ENC models, and field devices like valves, actuators, and sensors.  Environment I/A Series Cause Government buildings specification Resolution The "schedule" links below provide a list of all products in the I/A Series line that are American-made.  The third link provides a signed statement of declaration. Schedule A Schedule B Declaration

Issue What are the pulse input ratings for a Niagara G3 Jace-6? Environment Niagara G3 Cause Job site has pulse meters which require termination to the Jace-6. Resolution The universal inputs support both pulse contacts and normal dry (equipment status) contacts. Pulse contacts may have a change-of-state (COS) frequency of up to 20 Hz with a 50% duty cycle.  Note: Minimum dwell time must be > 25ms. (Contacts must remain open at least 25ms and be closed at least 25ms.) Standard dry contacts must have a 1 Hz. (or less) COS frequency, with minimum dwell time > 500ms. (Contacts must remain open at least 500ms and be closed at least 500ms.) Both types of dry contacts support 3.3 Vdc open circuits or 330 μA short-circuit current. Click here for more information.

Issue LMTOOLS was not installed on the computer that Vista 5.1.8 was installed on. Product Line TAC Vista Environment Vista LMTOOLS LMAdmin Cause The TAC Vista license administrator tool has been upgraded to LMAdmin, a web based license administration tool accessible using a web browser. Existing license files are compatible with the new LMAdmin tool that is included in the TAC Vista Server and TAC License installers. Resolution If the license server is not running as a service, Vista is unable to locate the license, or you need general troubleshooting help then see License troubleshooting in Vista 5.1.8 or greater. Flexnet License Admin   The default license file folder has changed with the new LMAdmin license tool. The new default license file folder is "C:\Program Files\Schneider Electric\License Server\taclic\licenses\". For 64-bit OS the default license path is "C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses\". The license server administration, LMAdmin, is installed as a web server and is accessible at http://localhost:8080 after the installation; a shortcut will also be placed in the start menu. The location of this shortcut can be found by going to Start > All Programs > Schneider Electric > TAC Tools 5.X.X > FlexNet License Admin. To check what your license file contains, how many seats are available for each program, and how many are in use click on the Concurrent icon.   To log into LMAdmin, click on Administration in the top right corner. The default login and password is admin/admin and it is recommended that this is changed after the installation is finished. User accounts can be managed in the Administration area, under the User Configuration tab. Click the New icon at the top of the window to add users. The edit button at the end of the row of each user will allow the user name and password to be changed. There is also a delete button to remove unwanted users. If the computer running the TAC Vista License server enters a power save mode, the license server may have to be restarted manually in Computer Management > Services and Applications > Services.   TAC License Setup It is recommended to use the "License Setup tool" in the start menu instead of the license popup dialog when specifying a license server name or license file location. The License Setup tool can be found here; Start > All Programs > Schneider Electric > TAC Vista Server 5.X.X. Note: When upgrading Vista from a version 5.1.7 or older to a newer version, the old license file path may still exist in the registry. This will not impact the license server in any way. The old path can be removed if you desire through the TAC License Setup. During the installation of TAC Vista Server and TAC License, any license files located in the old license file folder are automatically copied to the new license file location; the original files are not removed.

Issue What is the resistance for the DOC, DRC, DSC and DLC sensors for a Drayton Theta II EC Environment DOC, DRC, DSC and DLC sensors Drayton Theta II EC Cause Information Resolution DOC and DRC   DSC and DLC °C Ω   °C Ω           0 2339   0 6760 1 2235   5 5830 2 2137   10 4901 3 2043   15 3978 4 1943   20 3252 5 1870   25 2677 6 1790   30 2217 7 1713   35 1848 8 1641   40 1549 9 1572   45 1306 10 1506   50 1107 11 1444   55 943 12 1385   60 807 13 1328   65 694 14 1274   70 599 15 1223   75 520 16 1174   80 452 17 1127   85 396 18 1083   90 347 19 1040   95 303 20 1000   100 260 21 961   105 230 22 924   110 200 23 880   115 190 24 855   120 180 25 823       26 792       27 762       28 734       29 707       30 681       31 657       32 633       33 610       34 589       35 568      

Issue The descriptions of the MN-S and MN-S1 sensors both state that they are temperature sensor only, what is the difference? Environment MN-S MN-S1 MN-Sx Micronet 2000 I/A Series Micronet Cause The part number descriptions of the MN-S and MN-S1 sensors both state that they are sensor only, what is the difference? Part # MN-S Description: MicroNet 2000 Wall Temperature Sensor with Temperature Sensor Only          Part # MN-S1 Description: I/A Series Micronet S-Link Sensor Assembly Providing Temperature Only.   Resolution While physically and functionally similar the two sensor belong to different product families and are not interchangeable since they utilize different communications protocols. The MN-S communicating sensor is compatible with the Micronet 2000 product family and is used with MN-FLO, MN-FLO3T, MN-HPFC controllers that use U bus communication protocol for sensor data. The MN-S1  communicating sensor is compatible with the I/A Series Micronet  product families and is used with MNL and MNB range of controllers that use S-Link communication protocol for sensor data.

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue Requests for information on a wireless access control solution Environment Continuum Schlage Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Easy access to documentation for the Schlage Wireless Access Control Solution Resolution 09-17-2012 The Security Center of Excellence is pleased to announce the integration between Schlage AD-Series locks and Andover Continuum Netcontroller II and ACX 57XX family of controllers. This integration will provide a cost effective and scalable access control solution. Schlage AD-Series locks combine all of the components typically found around the door such as the door position switch and the request to exit switch into one unit which simplifies installation and saves money. Since they are designed to be modular Schlage AD-Series locks can easily be upgraded in the future to meet changing security and technology requirements. Within Continuum Cyberstation the Schlage locking device will look and function like a normal door and an XDriver at the controller level will provide access to these devices. This solution is ideal for education and healthcare facilities but can also be used in a wide range of other applications. For more information please contact COE@Buildings.Schneider-Electric.com.   Schlage Data Sheet Final.pdf Andover Continuum _ Schlage Integration Offer Final.pdf Andover Continuum _ Schlage Integration Training Final.pdf

Issue HotFix best practices Environment Site with StruxureWare Building Operation Cause Is it supported to have a Hotfix applied to ES/Workstation, but not the AS? Is it supported to have different HotFixes applied to the same site? In other words, HotFixes can be applied to select AS, but can you have different HotFixes on different AS, with perhaps a different HotFix applied to the ES/WorkStation?   Resolution The hot fix readme details what is necessary to install a Hotfix, generally they can be mixed as necessary on the one site, if there is any dependency’s (i.e. you need to install WS with the ES) this again will be detailed in the HotFix readme file. Remember HotFixes are now consolidated (all in the one hot fix) and the build numbering of the HotFix shows this, i.e. 1.6.0.xxx is based on fixes consolidated in consolidation point 1, again the readme tells you which fixes are included. Also remember that you can only apply a hot fix when the build number is greater than the current installed build. As a general rule you should be able to have different hot fixes on a ES, on an AS and on Workstation. However, installing a new hot fix on top of a previous hot fix for any of these will remove the previous hot fix, if the read me file for the new hotfix doesn't specify that the previous hot fix is included. It will specify this not in terms of hot fix builds but in terms of fixes for ALM defect ID's. Therefore, one needs to look at the read me files for the combination of hot fixes used at any specific site to make sure all hot fixes needed are effective and not have been overwritten by a later hot fix. The above is true for read me files whether or not a hot fix is considered to be a consolidated hot fix or not. Note, the guidelines seem to imply that all hot fixes are consolidated, which is no true.   Version of firmware on an AS: Note: Not all HotFixes apply to all sites. HotFixes eliminate issues observed and defined in a particular defect.   

Issue How to configure BACnet networks in an IA Series Jace Product Line TAC IA Series Environment I/A Series G3 (AX) ENC (Jace) I/A Series N4 ENC (Jace) Cause Need for a detailed approach to IP and MSTP network setup. Resolution This video explains the steps necessary to configure a JACE to Communicate with BACnet IP and MSTP controllers.

Issue How to Prepare a Server for Access Expert Premise Software Product Line Access Expert V2 On-Premise ONLY Environment Windows Server 2012 and above Cause There is no documentation on how to prepare a server for a Premise Install. Resolution In order to do this there are several pieces that needs to be followed on how to configure it correctly. First step is to install the server software, in this case Windows Server 2012: Configure the local server Add Roles and Features, Click Next Server Selection, select a server (should be the local machine) Click Next a few times, to complete this part Scroll down to the bottom and select WebServer IIS and add all features Click Next to complete this part Click on .net Framework 4.5 Features Check the box for ASP.net 4.5 Expand WCF Services Click on HTTP Activation, Add Features Scroll down to Message Queuing Expand and scroll down to SMTP Server - Add Feature, Click next a couple of times to install Once completed, Close and Exit Installing SQL Server Open media where software is located and launch the installer Select the option to Install a new instance and click Next Select Install DB Engine and Mgmt Tools, click Next Select Default instance, click Next Use same service accounts, click on Server Configuration Tab Add - License Administration as a Group Select the Data Directories Tab, change where the data files are stored by default Create new Folders for SQL Data, SQL Logs Change Directory Paths as well for Temp Create new folder for Backup Click on next and Install Once finished, close out to complete the install. Enable sysadmin in SQL for NTAuthority Installing Keep Here is a link of a video that goes through this process as well. Premise Installation of Keep for Access Expert Download Keep By Feenics software from the Software Downloads Tab on the Feenics training site http://www.feenics.com/training/courses/technical-certification/ Browse to the location and launch Keep Installer, click on Next When complete, Test Db Connection, once it passes, click on Next Make sure all elements are selected, click on Next to install Launch the Keep Instance Management, click on Connect Connect to the local Host Give the site a name that will used for the instance (if this name is changed, it would require a new instance license key to be generated) Give a url to the name db name with username and password (admin/admin) Change the path for file location and DB Log location from earlier steps Save configuration and Close On the Web Browser, Go to Tools - IIS Manager Add a new Binding, check the Box for "Do not show messages" Delete the default website Click on created website and select Bindings Click on Add - use same name in original browser Start IE Browser (url) created earlier Load license from Activation Code and Activate Log in to the system. Host File If the browser does not start and fails to open the page, then modify the Host File to contain the IP address of the server as well as the URL of the instance Go to C:\Windows\System32\drivers\etc hosts Modify the file by entering the IP address of the server as well as the URL Save and close. Open up the page again and it should allow the application to be started. For V3 On-Premise Installation Instructions, see the following link: https://ecoxpert.se.com/search?documentUUID=846b8347-4412-42ad-a983-53ef97bb5cc4&title=AccessXpert%20On%20Premise%20Deployment%20Walkthrough%20v3.pdf  

Issue 'Failed to connect to SQL Server (local\TACVISTA). "[18470] Login failed for user 'xxx\xxxxx'. Reason: The account is disabled." message appears when trying to install Vista using another account than the account that is logged on to the server. Product Line TAC Vista Environment TAC Vista 5.1.X SQL installation/connection Cause The TAC Vista installer SQL configuration settings page states 'Select authentication and specify SQL Login or Windows account and password to set how TAC Vista Server will access the SQL server.' This means how TAC Vista will access the SQL server when Vista is running, not during installation. Resolution Ensure that the user running the TAC Vista installer has the correct permissions to install an SQL server (if this is a new database) and configure it. The specified user will be used during runtime, but the launching user during installation. The installing user can then be removed from the SQL server security settings after installation is complete.

Issue The time in TAC Xenta Server should be the same as the time on the TAC Vista Server PC. When Xenta Servers connect to the TAC Vista Server, they should synchronize their time with the Vista PC. Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 NTP Server Vista Server Cause There are different scenarios. Vista Server PC has no internet connection Vista Server PC has internet connection Resolution Corresponding to the causes above: Set the Xenta Server to synchronize with the Vista Server PC. You do that by adding this AuthoritativeNTPserver.zip reg file to the registry on the TAC Vista Server PC, and enter the IP address of the PC into the Xenta Server as described in Setting NTP in Xenta Server.pdf. Set the Xenta Server and the Vista Server PC to synchronize with a NTP server on the internet. Find servers here: http://support.ntp.org/bin/view/Servers/NTPPoolServers Area HostName Worldwide pool.ntp.org Asia asia.pool.ntp.org Europe europe.pool.ntp.org North America north-america.pool.ntp.org Oceania oceania.pool.ntp.org South America south-america.pool.ntp.org In general, make sure that firewall is not an issue. NTP uses port UDP 123

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue How to read a controller error log Environment CX 9680 ACX 57xx BCX 9640 BCX 4040 i2 controllers B3 controllers Cause Need to decipher a controller error log Resolution Deciphering the controller error log can be accomplished by using a few of the fields of the error log. There is one field that is able to be deciphered very easily. The Error Code column of the error log is a code that can be matched to its text description. The other fields are used internally by PSS and engineering. To find out what one of the entries in an Error Code column means, open up the Continuum online help file. The Continuum online help file can be found by in the Continuum Explorer by selecting the menu item Help/Contents. From there select the Index tab and type in the keyword Error. A selection will be available for Error messages, Cyberstation. On this page you will be able to take the last 4 digits of the Error Code from the controller error log and match it up to its description. Example: Error Code  0x00001401 translated into decimal form would be 5121 The error code will be listed by both the hex and decimal format. Not all codes will be in the online Error description fields. Some of these codes are internal use only. If you find that you need a code deciphered, please open a case with Product Support.

Issue Need to know what different system alarms can occur in EcoStruxure Building Operation?  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause System alarms are alarms built into the system, such as "IO module offline" or "Server offline". In EcoStruxure Building Operation, over 230 system alarms exist. Resolution For all system alarms check WebHelp article: System Alarm ID Enumerations

Issue Error when running the Checklic license utility: "InitCrypkey Error -103: NETWORK: REPLY FROM NETWORK DRIVER IS BAD" "InitCrypkey Error -102: NETWORK: NETWORK DRIVER APPEARS TO NOT BE SERVING THIS DIRECTORY" Product Line Other, TAC Vista Environment LNS 3.0 LNS Turbo Edition (Ver 3.2) LonMaker 3.0 LonMaker 3.1 LonMaker Turbo (Ver 3.2) Vista Cause A problem has occurred with the LonMaker licensing. Resolution There are two procedures for fixing this problem. Try Procedure 1 first, and if the license still has the same problem, try Procedure 2. Internet access may be required for Procedure 2 to in order to download the setupex.exe and cks.exe programs and request a replacement license. Procedure 1: Confirm that the Windows Crypkey License service is started. To confirm, click Start > Control Panel > Administrative Tools > Services. Verify the Crypkey License status is Started. Also verify that the startup type is Automatic. If not, right-click the name and then click Start. Double-click the name to enter the properties dialog and change the startup type to Automatic. Close the Service window.   Confirm the Crypkey NetworkX driver is started by running C:\Program Files\Common Files\Microsoft Shared\MSInfo\Msinfo32.exe. Expand System Summary > Software Environment > System Drivers in the category tree in the left pane, then locate NetworkX in the right pane. Confirm that the State is Running and the Status is OK. Close the System Information window. If you cannot find these software components, uninstall the Echelon Software product, reboot, and reinstall the product. Antivirus and Internet security software can interfere with the proper installation of the software. Disable such software before you re-install the Echelon software product. At this point, if you are still unable to run your LonMaker or LNS application because of a License Access error message and if the Checklic license utility still reports a -102 or -103 error, follow the steps in Procedure 2. Procedure 2: Check to see if two files exist in the C:\Windows\LNS Licenses folder. setupex.exe cks.exe The LNS Licenses folder is hidden; if you do not see it, open the Windows Explorer Tools menu, click Folder Options, and in the View tab, select Show Hidden Files and Folders and clear Hide Protected Operating System Files (Recommended). If you don't see these files, download them from Echelon and extract them to the C:\Windows\LNS Licenses folder. Open a Windows command prompt by clicking Start > Run and typing in cmd (or command for Windows 98). Type the following command to change your working directory: cd "\Windows\LNS Licenses" Type the following command: setupex /U Reboot the computer. Repeat steps 3 and 4, and then type the following command: setupex Reboot the computer. Open a Windows command prompt and enter "checklic lonmaker.vsl" for the LonMaker Tool or "checklic nsseng.exe" for other LNS tools and applications. If no errors appear, then the LNS application should start. Exit now. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening/creating network. If the -4/-1 error remains, use the license wizard to request replacement credits. If the InitCrypkey Error -102/-103 error is shown, delete the following files under C:\Windows\LNS Licenses (do not delete other files from the LNS Licenses folder): For the LonMaker tool: LonMaker.rst LonMaker.ent LonMaker.key LonMaker.41s For an LNS tool or application other than the LonMaker tool: nsseng.rst nsseng.ent nsseng.key nsseng.41s Delete esnecil.ind in the C:\windows\system32 folder. Reboot the computer. Run the Checklic license utility again. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening or creating a network. If the -4/-1 error remains, use the license wizard to request replacement credits. Once the license is fixed, download and install the LNS Licensing Update 2006.

Issue String comparison in TGML script is not working. Product Line TAC Vista Environment TGML graphics editor 1.1.X Cause Javascript has a string class and a string literal. String literals are denoted by double or single quotation marks ("" or '') and it is important to compare "like" with "like". String literal: string1 = "Apples" String class: string1 = target.getAttribute("Name"); Resolution A deeper comparison is required in the example below. Instead of: name = target.getAttribute("Name"); tmp = target.getParentNode().getElementsByTagName("Ellipse").item(i).getAttribute("Name"); if (tmp==name) Use: if (tmp.equals(name)) An example is shown in the TGML graphic attached. Download graphic Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue There is no quick and efficient way to configure a TAC Xenta 102-AX controller after adding it to a LonWorks Network in Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC Xenta 102-AX controller is typically configured using the LNS plug-in that is currently not available in version 1.4.0 and newer. Resolution As an alternative to the LNS plug-in, the graphic page available on the Community [1] can be used. This zip file contains the TGML graphic, binding template, and a full import file with a Xenta 102-AX that is already bound. [1] Xenta 102-AX SXW TGML Plugin v1.6.1 (SBO 1.8.0 to 1.9.3) Example Plug-in TGML Graphic Page

Issue A network level controller is shown offline. Can a flash upgrade (Update OS) be done to it? Product Line Andover Continuum Environment BCX ACX5720 ACX5740 NC2 CX9900 Cause A bCX needed a flash upgrade but was offline in CyberStation. How can we update the OS? Resolution The Update OS function can sometimes be completed even if the controller indicates that it is offline. If it cannot be pinged from CyberStation, it will not likely be able to be upgraded in its current state and may require returning for repair. But if it can be pinged it, try doing the Update OS. Follow the progress in the Distribution window. If it completes, the controller will likely come back online a few minutes after the update is complete Completing this "Blind Update OS" can often restore to normal operation a controller that has its Operating System corrupted not allowing the Web page to be accessed, as long as you know the ACCNet ID and IP address (a reset IP can be performed) this process may be attempted. It is also possible to flash an offline controller if it has reverted to the default IP address (169.254.1.1) and ACCNet ID of 1 if the Workstation is set to be in the same subnet so it can ping the controller and these default settings are used for the controller configuration. If after a full cold restart and at least 2 attempts to flash the controller fail, then the controller may need to be returned for Repair. Some possible causes of this problem are listed in What can cause a controller to reset, cold start or lose data.

Issue How to set the neuron ID of an I/O Module in a Vista classic network. Product Line TAC Vista Environment Vista Classic Network Xenta I/O modules Cause Xenta I/O modules beneath a base unit (300 or 400 series) do not show up in the Folder view tree structure.  You cannot right-click and set a neuron ID the same way you do for a base unit. Resolution Click on the Xenta base unit (300 or 400 series controller) in the tree structure. This brings up a list of modules inside the Menta file as well as two option modules that cannot be seen from the tree structure-- $IO and $LOGS. Double click the $IO module. All of the I/O modules defined in the Menta file are listed here.  Right-click, properties, to set the neuron ID.