Building Automation Knowledge Base

Issue Error when installing SQL 2005 Express on a machine that had previously had MSDE installed Product Line TAC INET Environment SQL 2005 Express Cause  MSXML 6.0 SP2 is causing the installation to fail Resolution Download the program linked below Remove SQL 2005 from the system Run the application to remove MSXML 6.0 from the system Re-install SQL2005 Express MicrosoftFixit50568.msi.zip For alternative solutions see SQL Express install fails on MSXML 6 and Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.).

Issue How long can the power to AS be interrupted Product Line EcoStruxure Building Operation Environment PS Power Supply Automation Server Cause Question regarding the AS and the power supply module. If the power is interrupted from the 24VAC power supply for say, 100 milliseconds, will the power to the AS be interrupted? There is a cold cap in the PS, and how long does it maintain power supplied to the AS? What about the RTC?   Resolution The power to the AS will be interrupted if there is a 100mS main power fail. The AS will then save the server cache. When the power returns the AS will make a restart that will take approx. 2 minutes. The AS Power supply fully complies with the IEC 61000-4-11 standard and can withstand voltage dips, with a 20mS dip and a 0% residual voltage.  The Power-fail process: When the AS loses power the super-cap keeps the AS alive for 15 seconds. 10 seconds of it dedicated to power-fail process to flush all the data that that are currently in the RAM to the SD card(That data can be anything with any value they have before power-fail). When power comes back that data is retained and are stored in appropriate place on the SD card. Real-Time-Clock(RTC) is maintained when the AS loses power by a dedicated capacitor which backs up the RTC chip for a minimum of 30 days in the absence of power since there is no battery in the AS.    

Issue SP-C-WEB Recommended Limits Product Line Security Expert Environment Security Expert SP-C-WEB Cause The SP-C-WEB limitations are mentioned in briefly in the SmartX Controller SP-C-WEB presentation but detailed information on this is not available in the current SP-C-WEB documentation.  Resolution Schneider Electric's recommended limits for the SP-C-WEB:Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000 Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000

Issue Values of Units change when viewing English OS from Metric OS Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site Cause Changes in Unit Value English OS example of Pressure Unit of Bar: Metric of same exact unit from a Metric OS: Resolution This behavior of different Units being displayed on OS systems with metric units. In the State the English units for measurement are on the OS and StruxureWare Building Operation. The issue described is Functions as Design in StruxureWare Building Operation. Not just IO, but all the functions are like this. The localization follows the regional settings of the PC’s operating system, out of the control of users. To change your PC's measurement System, complete the following steps: Open the Control Panel on your PC and browse to "Region and Language" In the Region and Language editor, click on the "Additional Settings" button found at the bottom of the "Formats" tab. Change the measurement system to the desired system                                                                  Click OK to close all Windows Restart all applications for changes to take effect.

Issue How to enable Continuum site for use with Endura DVRs and cameras. Product Line Andover Continuum, Pelco Environment Continuum V1.91 and above Pelco Endura DVR See the Video Compatibility matrix for supported Pelco Endura products on the various Continuum versions, Cause Want to enable Continuum for use with Endura but unsure which security keys support the addition of the option and what the option provides. Resolution Why is this option required? The Endura -E option for Continuum security keys is required to be able to: Configure VideoServer objects in Continuum to use Endura DVRs. Use VideoAdministrator and VideoMonitor to configure and view Endura cameras. It is not required to be able to configure and view cameras from DigitalSentry DVR's or to view Endura cameras using VideoLayout objects that have already been configured. Which Workstations can have the option added? SU and LAN Cyberstation security keys can be enabled with the Endura -E option. This option cannot be added to the WEBC key for WebClient Servers. If configuring Endura cameras is required, a Cyberstation with the -E option must be used. WebClient browser users are able to use the VideoLayout to view DigitalSentry and Endura cameras. The Endura option is only available through the upgrade process through Repairs. There is no part number to specify to enable Endura at the time of ordering the security key. Once you have the serial number of the key, contact Repairs below. Email:  upgrades.continuum@schneider-electric.com How to tell if the option is enabled? If the system is operating normally (not in Demo Mode), open up a Video Server object. If the key is video enabled it should look like this: If it is not enabled, the Pelco Endura option is not available:

Issue The automation server was added successfully; however, it never appeared in the server list. It did, however, get added to the communications tab. The System Tree server list varies from the Communication tab list of servers. No servers shown under "Servers" List in System Tree but is seen in Communications tab Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause This is typically caused by the Group account not having permission to access the root path.  To verify this is the issue, log in with the "admin" user account and verify that the server lists match.    Looking at the screenshot below: If the Add (+ icon) option has been used to add the ES-1 Path Permissions, no server will be visible.  Additional Path Permissions need to be added for each server. If the Add System (Hierachial icon) option is used (the default for the local admin account group), this is the System's top-level path. Then, all servers will be seen.       See online WebHelp topic User Account Group – Software Permissions Tab Resolution Depending on which method is required by the end user. If using the Add (+icon) option  Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add (+) the Automation Server(s) to the path permissions as shown below: Repeat the above step for every server Each time a new Automation Server is added, repeat all steps.  If using the Add System (Hierachial icon) option Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add System (Hierachial icon) to the path permissions as shown below: Users must log off and log on to see any of the implemented changes.    

Issue After configuration, Suprema readers are showing as offline in the Security Expert client. There are Security Expert Download Service events logged in the windows application event log. Cannot load DLL - LoadLibrary() Failed. Cannot load DLL event mesage Product Line EcoStruxure Security Expert Environment Security Expert Suprema biometric readers Cause Required DLL SecurityExpertSV2.ThirdParty.dll is missing from the installation folder. Some versions of Security Expert installer will not install this required DLL and the file need to be manually added. Resolution Check the Security Expert install folder, typically C:\Program Files (x86)\Schneider Electric\Security Expert, to confirm if the file SecurityExpertSV2.ThirdParty.dll is present. SecurityExpertSV2.ThirdParty.dll   If the file is not in the installation folder then it can be sourced from the integration guide ZIP package. AN 264 Security Expert - Suprema Biometric - Integration Guide contains the three DLL's required for the integration. Install the file by copying it into the installation folder, then restart all of the Security Expert services or restart the Security Expert server.

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue Connection details for the MZ20A / MZ20A-R actuator. Product Line Field Devices Environment MZ20A-R Wiring Connections Cause How do the cable colours relate to the connection numbers on an MZ20A / MZ20A-R actuator? Resolution The MZ20A / MZ20A-R actuator connection details are shown below.   For the actuator data sheet please click .HERE

Issue A TGML Graphic is added or imported into Vista. Then when you right click on the TGML Graphic and select " Open Bindings Window" a blank bindings window is opened. None of the objects defined in the TGML Graphic appear in the binding list to be bound to objects in the Vista database. Environment Vista 5.1.7 Cause The TGML Graphic is named with .(dot) characters in the name. E.G. VAV1.1.7 Resolution Do not use dots, dashes or hyphens in the naming convention for any Vista objects. Either eliminate it altogether, or use underscores (_) instead. To correct this issue after the TGML Graphic has been added  with the incorrect naming convention, is: Edit the TGML Graphic and save it out of the database. Delete the TGML Graphic with the name including the . (dot) character. Add a new TGML Graphic using the correct naming convention E.G. VAV1_1_7 Open the TGML Graphic that was saved out of the database and save into the new TGML Graphic you created with the correct naming convention. Note: Renaming the TGML Graphic object from VAV1.1.7 to VAV1_1_7 in the Vista database does not fix the problem.

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.

Issue Infinity controller error: Type not valid for this IO channel Product Line Andover Continuum Environment Continuum Cyberstation Cause ElecType mismatch between what is in the database and the field controller hardware. An example of this problem would be offline creating a voltage output on a DO-4.  It will save to the DB since it is a valid InfinityOutput configuration.   Although when attempting to do a Send to Controller the controller knows that point type is not valid on the specific IOU module hardware. This can also happen when an object is imported into Continuum because the database error checking is less strict than when creating the object online. Resolution Go into offline editing Check the point configuration If it does not match the field hardware, then correct it, save it, go to online mode and reload.

Issue Creating Folder Structure to Organize Reports Environment SmartStruxure StruxureWare for Building Operation Report Server Cause A large number of reports may result in difficulty navigating the report tree.  The following processes allow you to sort the various created reports. Resolution Creating folders to store the saved reports.  Log into the SQL Report manager from the reports Server using the URL http://localhost/Reports   or  http://localhost/Reports_SQLEXPRESS     Open the folder you wish to add new folders to.  For this example I will use the Production reports folder.   Click "New Folder" Name the Folder and click OK NOTE: In order for the Folder to show up in the reports Server, it will have to have at least one object inside of it. You can move any report to the new folder by clicking on the drop down beside it and selecting "Move". Updating the StruxureWare reports Server to display the new folders  Connect to the StruxureWare Web Reports interface, using an account that is part of the Reports Administrators group. Click on Report Packs. At the bottom of the Screen click "Synchronize" This must be done to apply any changes made in the SQL Report Server Web interface to the StruxureWare Reports Server Saving a Reports parameters for quicker access.  You may wish to save a report to quickly run last months Trend Data. This type of saved report is referred to as a "Dashboard Report" Run the report you wish to save, using the desired parameters Above the report, click Save As In the Report name Field, type the Folder name and report name that you wish to use. NOTE you are limited to 30 characters for the report name. Be sure to check the "Dashboard report" option. Without this option checked you will be making a duplicate of the original report. The Dashboard Report option saves the parameters you have selected. Click "Save as"

Issue Has the AC256 Xdriver been qualified or modified to work on any second generation controllers (NC2, bCX)? Product Line Andover Continuum Environment bCx9640 CX9680 Xdriver AC256 LA-1 Cause With the obsolescence of the NetC (CX99xx), will the AC256 Xdriver be updated to work with NC2 and/or bCX controllers? Resolution There are no plans to upgrade the AC256 Xdriver for the NC2 and/or bCX. One option, if a site only has AC256 IOU boards, is to use the NC2 and the LA-1 LBus Adapter module or the NC2 with built in LBus support (on comm4 or comm1 with an RS232-to-RS422 converter) to communicate over the LBus with Plain English programming in the NC2. Note: If you configure the controller for Lbus (using the LA-1 or directly to comm1 or comm4) you cannot use Continuum IO modules on that controller. For further information on X Driver compatibility and how to request new drivers/ upgrades, please see Will Continuum communicate with a third party system?

Issue I have to replace a faulty Xenta 301 but found that the existing Xenta 301 was system version 1. The system consists of about 12 Xenta controllers sitting on a Menta only network using .nwc,ndb network configuration tool. Environment TAC Xenta 300 TAC Menta Cause New devices are delivered with version 3. Resolution As TAC Xenta system program version 1 and version 3 can not work on the same network, downgrade the new device to replace the faulty one. Download TAC Xenta 300 system program version 1.17 Use Download Wizard as normal to download the system program, however, going from version 3 to version 1, do NOT keep old application in the Download Wizard. Select Clear Application. Download the Menta application and network configuration manually via the serial cable. You could use the actual TAC Menta versions to do this.

Issue Replacement an AF24-S Actuator? Environment AF24-S Damper Cause Customer requires a replacement actuator for a AF24-S. Resolution The AF24-S is a 24v power open, spring return damper actuator, it has a torque of 15 Newtons. To view the data sheet, please click HERE. The replacement actuator range is the MD10SR/MD20SR ranges. The MD10SR damper actuators have a torque of 10 Newtons (dampers up to 2m2) and are available in the models shown below. To view the full data sheet, please click HERE.   The MD20SR damper actuators have a torque of 20 Newtons (dampers up to 4m2) and are available in the models shown below. To view the full data sheet, please click HERE. In the specific case of the AF24-S the replacement would be the MD20SR-T or -TS if auxiliary switches are required.

Issue Service Pack 2 provides the following correction: MicroNet VisiSat import file replaces all non-ASCII chars with replacement character( Defect 31467). Fix applied so that the characters are converted correctly.  Fix applied so that points with alarms and trends results in the import file being generated. Product Line Satchwell MicroNet Environment VisiSat 2.1 Build 196 201 Cause Correction of raised defects. Resolution This Service Pack should only be added to VisiSat 2.1.196 or 2.1.200 if service pack 1 has been installed. Note: When installed, the VisiSat 2.1.96 or 200 installation (200 if service pack 1 has been installed), the build number increases to 2.1.201. (due to one of the files in 'Program Files'). VisiSat will still show as Build 2.1.196 in Control Panel - Programs - Programs and Features - Uninstall or change program. Installing VisiSat Service Pack 2 =============================== Shutdown VisiSat and the VisiSat-Server. Run "VisiSat 2.1.196 Service Pack 2.exe". Extract to VisiSat installation root drive. (or extract to another location and move the Satchwell folder, created when extracted to the root of the C: drive). To the question 'Would you like to replace the exiting file', select 'Yes to All' Restart VisiSat. Download VisiSat 2.1 Build 196 Service Pack 2. See VisiSat version 2.1 Build 196 service pack 1 where information on VisiSat 2.1 Build 196 Service Pack 1 can be found and the service pack downloaded.

Issue Unsure what options are available in the Lua smtp.send() function. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause The Lua smtp.send() function is not fully documented. Resolution The syntax of the smtp.send() function is: smtp.send { from = string, rcpt = string or string-table, source = LTN12 source, [server = string,] [user = string,] [password = string,] [port = number,] [domain = string] }   From above you can see that the "from", "rcpt" and "source" fields are required. Whilst "server", "user", "password", "port" and "domain" fields are optional. Example Lua code is: --============================================================================== -- SSL email notification script example --============================================================================== -- Define the input you want to monitor below var("temperature", "ME.AI1") -- Room Temperature limit = 78 -- define the threshold now = scl.sysclock() if (temperature > limit) then -- When temperature is above threshold     if (sent == nil) -- Check if e-mail was already sent     and ((last == nil) or (now - last > 15 * 60)) then -- Maximum every 15 minutes         sent = true -- Only send e-mail once         last = now -- Keep track of last time     result, reason = smtp.send {     user = "alerts@server.com",  -- Enter your existing SMTP username     password = "test1234",  -- Enter your existing SMTP password     from = "alerts@company.com",  -- Enter your existing Source address     rcpt = {             "user1@company.com",  -- First recipient             "user2@company.com",  -- Second recipient             "user3@company.com"  -- Third recipient             },     source = smtp.message( {     headers = {     from = "alerts@company.com",  -- Displayed source address     to = "technicians@company.com",  -- Displayed recipients     subject = "Temperature Alert"  -- E-mail title                 },     body = "Current temperature is: " .. temperature .. " (above " .. limit .. ")" .. " [" .. os.date() .. "]"}),     server = "server.com" – enter your SMTP server                 }     if result ~= 1 then         print(os.date(), "E-mail was NOT sent:", reason)     else         print(os.date(), "E-mail was successfully sent.")     end end     else     sent = nil -- Re-enable alerting on condition end   --[[ Disclaimer: We hope that this script example and associated information (the "information") is valuable to you. Your use of this information, however, is at your sole risk. All information is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Schneider Electric.. Further, Schneider Electric. shall not be liable for any damages you may sustain by using/installing/modifying this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages. --]]  

Issue Netcontroller 2 offline with CPU LED and Ethernet LED's on solid. This occurred after electrician installed new equipment in the same cabinet. Environment Netcontroller 2 Continuum Cause Controller database has become corrupt. Resolution Clear controller RAM and Flash and reload controller. In this instance, the Controller did not seem to respond to pressing the "reset IP" button for 30s. Removing power and battery connections for a minute and then reconnection power cleared the memory. Able to see device online and reload from the Workstation after this.

Issue Script editor shows blank canvas or shuts down immediately after launching. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Cause User settings file contains information the Script Editor application can't process correctly. Resolution First, to confirm that the issue is indeed caused by information in the user settings file, navigate to the location where the file is located (i.e. C:\Users\Your User\AppData\Roaming\Schneider Electric EcoStruxure\Script Editor\3.1.2.29) and make a backup of the User.settings file then delete it. If the Script Editor launches fine after deletion of the file, and you need to narrow down which setting was causing the problem, you can put back the original file then open the file in a text editor such as Notepad++ and comment out suspected lines until you identify the exact setting causing the issue. You comment a line or block of lines by inserting <!-- at the beginning of a line and ending the line(s) with -->  (see below)