Building Automation Knowledge Base

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 When attempting to add an Automation Server to an Enterprise Server, an error message "Log on temporarily disabled' is displayed. The operation fails and the Automation Server is not added to the ES. Error message displayed on version 1.8 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server (AS, AS-P or AS-B) All of the above version 1.9 or earlier Cause This only occurs after an initial failed attempt to add a server to the Enterprise Server. On each subsequent attempt to add the server, it always tries to authorize to the server with the admin account's default credentials, which in most cases are no longer valid. This locks the admin account. So when the admin account has been locked initially, it will not be unlocked, as every time an attempt is made to add the server, the default admin credentials are being used, and therefore it fails. Normally a locked account is a temporary condition, but in this case it is never recovered. This problem occurs on version 1.9 or earlier. It was fixed in version 2.0. Resolution The current workaround to allow the SmartStruxure Server Device to be added to the Enterprise Server is to perform a Warm Start or by cycling the power on the device. Upgrade to version 2.0 or later to resolve the issue permanently.

Issue How to remove, from a Niagara R2 Enterprise Server station, data for all logs prior to a specific date with one command. Product Line TAC IA Series Environment I/A Series R2 Enterprise Server Cause Cloudscape database management Resolution There is a utility that will allow deleting of records before a certain date of all or specific tables in the cloudscape database. The space from deleted records can also be recovered after deleted. This utility is called CloudscapeAdmin and is downloadable from The Exchange Download Center. Download cloudscapeAdmin.jar and place in the x:\niagara\[NiagaraRevision]\nre\lib directory (for Builds 431 and higher). To run this utility the station will need to be stopped. Once the station is stopped, open the console from either the created short cut or x:\niagara\[NiagaraRevision]\nre\bin\console.exe. From here type ‘nre CloudscapeAdmin’ and hit enter to view the commands to use it.  There are two functions that cloudscapeAdmin can do: Delete; The delete command deletes records before a certain date but does not reduce the size used on the disk. The empty area of the database will be filled with new archived data. Compact; The compact command deletes records before a certain date and recovers the space from the disk. This process is slower. Command: nre CloudscapeAdmin x:\niagara\[Niagara Revision]\stations\[Station Name] [User Name] [Password] [delete or compact] [tablename or all] [date] Sample Delete commands: nre CloudscapeAdmin c:\niagara\r2.301.522a\stations\StationName admin admin delete all 2007-07-01 Sample Compact commands: nre CloudscapeAdmin c:\niagara\r2.301.522a\stations\StationName admin admin compact all 2007-07-01

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 Is it possible to 'hot swap' IO modules? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation I/O Modules Cause Some critical applications require 24-hour operation. Resolution The I/O modules allow hot-connection of terminal bases and hot-swapping of the modules to their bases. This design ensures continuous power and communication during service operations.

Issue How to populate emailed event messages with specific event details. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Security Expert documentation is missing instructions on how to add specific object details to emailed event messages. Resolution 1. The following email tags can be inserted in the Message and Subject fields to dynamically populate the event email. <FIELDTIME> or <FIELD_TIME>   <EVENTID> or <EVENT_ID>   <LOGGEDTIME> or<LOGGED_TIME>   <FACILITYNUMBER> or <FACILITY_NUMBER>   <USERNAME> or <USER_NAME>   <CARDNUMBER> or <CARD_NUMBER>   <USERID> or <USER_ID>   <INSTRUCTIONS>   <DESCRIPTION>   <INSTRUCTIONS2> (second language)   <DESCRIPTION2> (second language)   <ALARM>   <COMMENTS>   <ACKNOWLEDGED>   <DOORNAME> or <DOOR_NAME>     2. Security Expert documentation is being modified to include this information on the email tags that can be used to populate email messages.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Procedure for converting a bCX9640 to a CX9680 (NC2) Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 (NC2) Cause Documentation Resolution This article provides some guidelines for converting a bCX9640 to a CX9680 in the field. As of version 1.94 CyberStation does not automatically convert a bCX9640 to a CX9680, such conversion while complex and error prone can be done manually.   DISCLAIMER: Be aware that due to the differences between the two models not everything can be converted; certain items may have to be re-created from scratch in the new CX9680 controller. DIFFERENCES BETWEEN BCX9640 AND CX9680   Feature bCX9640 CX9680 1 System Variables 47 65 2 Comm Ports 2 4 3 IO Expansion Modules IOU Modules 4 Infinet 1 2 5 Access Control No Yes 6 UPS Support No Yes 7 Display Module Support Yes No   Procedure: Make sure you have a recent backup of the SQL ContinuumDB as a precaution. From CyberStation send the bCX including children to a text file, the dump file can be later used for reference. Take note of the bCX9640’s name, AccNetID and network settings. Put the CyberStation in offline edit mode and delete the bCX9640 then create the CX9680 using the exact Name, ACCNetId and network settings as the deleted bCX. After creating the new controller object it will come online, at this point you are still communicating with the bCX9640 hardware. In the ‘Send to Database’ options make sure to select ‘Save attached objects and controllers’ then select the new controller in the Continuum explorer and perform a ‘Sent to database’, depending on how many Infinet devices you have this make take a while. When the send to database operation has completed you are ready to remove the bCX9680 hardware and connect the CX9680 hardware. After disconnecting the bCX from the network commission the CX9680 hardware with the same AccNetID and network settings as the bCX it is replacing. When the new hardware comes online reload it from Continuum making sure you don’t reload the Infinet devices (Reload attached objects but not attached controllers)   At this point you have converted the bCX9640 to a CX9680, the next steps in the process is fixing the items that do not convert properly due to the differences between the two controllers. LCD Display Configuration If the bCX has an display module attached all configuration related to the display module must be removed as the CX9680 does not support it. Fixing IO If the bCX had IO then appropriate IOU modules must be configured in the CX9680. In some cases points may have to be moved to a different IOU. For example if you were using a xPBD4 (which has both inputs and outputs) then you’ll have to put the inputs and outputs on different IOU modules as there is not an IOU module that is the equivalent of the xPBD4. Fixing References Any references in programs/functions to objects that do not exist in the CX9680 must be manually removed/fixed. For example the CX9680 does not have some system variables supported in the bCX such as all the system variables related to the display module (ACCLCDBeeper etc) Other items that need partial or complete manual fixing include… Alarms, links will convert ok, but references to Graphics, Program, Video may be have to be re-assigned. Extended logging   Use the dump file created on step #2 for reference when manually re-entering lost configuration.   Article as a document: Procedure For Converting a bCX9640 to a CX9680

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 An "Invalid Pointer" error message is displayed when attempting to open an existing project in the WorkPlace Tech Tool software. Environment WorkPlace Tech Tool release 5.x.x Cause The WorkPlace Tech Tool project database file (project-name.wtp) is missing or is corrupted. Resolution Use the WorkPlace Tech Tool software to recreate the project and reassociate the applications with the project. Navigate to the project folder using Windows Explorer. If the a .wtp project database file is present, rename the file, by adding .save to the end of the existing .wtp file name, for example, rename My_Project.wtp to My_Project.wtp.save Close Windows Explorer. Open WorkPlace Tech but do not open the project. Under the WPT Project Menu, select New Specify the name of the project. Use the same name as the existing project folder. Using my example from step 2, you would create the project named My_Project In the displayed "Add Application to Project From..." window, select the "Unassigned File" tab. All existing applications for that project will appear in the list. Select them all by holding down the [Ctrl] key on your keyboard and clicking on each file shown in the list. Click the [OK] button at the bottom of the window to add all the selected applications to the newly created project. Exit from the Workplace Tech Tool software. When you reopen this project, all applications should be shown and any of them should open properly.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue Schneider Electric domain firewall policy Product Line Satchwell BAS & Sigma Environment Engineer's laptops Cause Schneider computer/domain updates include McAfee firewall updates. It has been seen on some laptops with a fully working Sigma system, after a  Schneider policy update, the Sigma client fails to connect to the server.   Resolution Access to the firewall setting, on most Schneider Electric engineer's  laptops is not possible. Disabling the McAfee firewall should allow Sigma to load. Locate and, with a right mouse click, select the McAfee Icon  (found on the taskbar near the clock). From the list provided select "Quick Settings" Then select "Enable Firewall Timed Groups", You will need to enter a reason. The firewall will be disabled for a one hour period. 

Issue When reviewing events from Doors or Users, the below error is shown. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. Error - The communication object Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Workstations SP-C Controllers. Cause Firewall and/or Port settings are incorrectly configured. Certain ports must be opened to enable communication between the server, client workstations, and controllers. Resolution Check the Firewall to ensure that all required ports are open between the Security Expert Server, Security Expert Client Workstations and the SP-C Controllers. Refer to the IP Networking Ports section in the SX-SRVR Security Expert - Networking Guide for Administrators - Reference Guide for details on required ports.

Issue Epibuilder Dynamic Text fields are not displaying in a badge layout or Errors related to EpiBuilder or EPIDesigner Product Line Andover Continuum Environment EpiBuilder Badge Layout Cyberstation Cause Install didn't make the connection properly or badging wasn't enabled during the initial Continuum installation or Windows permission restrictions  Resolution From Make Edit badge in Continuum, Open Badge layout in EpiBuilder (If you have a problem opening Badge Layout see Note #2 below) View Options> Data Fields Select Use the data fields defined in a database If nothing is there, click the Other Database button Select Use an ODBC database Select the Data Source button Select System DSN tab and then select EPISDK then OK Click the Select button add the path to SDKNoDB.mdb (C:\Program Files\Continuum\EpiBuilder\Data) Click Open, Click OK All fields should now be available or the error should no longer happen on startup If receiving: ** Error Opening EpiDesigner Configuration Database error when selecting MakeEdit Badge,    Note #1: Permissions can affect the configuration of the Data Sources. If some options aren't configurable or have been changed from the default like buffers are not set to 2047 then try the configuration with increased permissions. Start>run odbc32.exe and check that the System DSN had EPISDK, If not, add it and then follow the instructions able to set the SDKNoDB.mdb  If the site is utilizing hard drive encryption on the hard drive.  Move the sdknodb.mdb to an unencrypted network share to correct the errors after updating the episdk datasource.  Note #2:  If you cannot perform step #1 from above check the following: On a 32 bit system run the following command from either the run window:  odbcad32.exe and check that the User DSN has an EPISDK entry with the datasource set to SDKNoDB.mdb .  The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\ On a 64 bit system run the following command from either the run/search window:  C:\Windows\SysWOW64\odbc32.exe and check that the User DSN has an EPISDK  entry with the datasource set to SDKNoDB.mdb . The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\

Issue SE7300 series BACnet controller does not come online in StruxureWare Building Operation if the communications address is greater then 127. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment StruxureWare Building Operation BACnet Cause The communications Address of SE7300 series BACnet controller can be set between 0 to 254. In StruxureWare Building Operation the highest address can be set only up to 127. Resolution Set the communication address less than or equal to 127 for SE7300 series BACnet controllers. Please refer to the Default Device ID / Device Instance of SE7000 series BACnet controllers to know the default Device ID / Device Instance of SE7000 series BACnet controllers.

Issue What web browsers are compatible with Sigma Web ActiveX interface Product Line Satchwell Sigma Environment Sigma 4.3 and later Cause Later versions of Internet Explorer do not display the Sigma ActiveX web pages. Resolution Sigma 4.3 introduced the ActiveX web client, this interface is only compatible with Microsoft Internet Explorer. The table below details the versions of Internet Explorer that are compatible with the various Sigma Web ActiveX releases. Operating System/Sigma Version 4.08 4.07 4.06 4.05 4.04 4.03 Microsoft ® Windows 2000         IE6 IE7 IE6 IE7 Microsoft ®Windows XP IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows Server 2003 IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows 7 IE8 IE9 IE8 IE8 IE8     Microsoft ® Server 2008 N/A N/A N/A N/A     Later versions of Internet Explorer than those listed above may be supported in Compatibility View

Issue Newly enrolled users biometrics are not working at Suprema readers while existing users are functioning normally. New user updates appear to be working, the Download Server is online, with changes being made to the controller .dat and suprema reader .dat files in the Security Expert Servers ProgramData folder as users are updated. Controller .dat files Product Line EcoStruxure Security Expert Environment Security Expert Suprema Integration Cause The Suprema BioStar services are running on the Security Expert server which conflicts with the operation of the Security Expert Download service. Both the BioStar software and Security Expert Download service use the same port (51211) to communicate with the biometric readers. Resolution The Suprema BioStar software is only used during commissioning and configuration of the biometric readers and does not need to be permanently running. Due to the port conflict, the Suprema services cannot be run on the Security Expert server with the Security Expert Download service active. Stop all of the BioStar services running on the Security Expert server and set the startup type to manual. Suprema services Restart the Security Expert download service. Download service New user updates will now be downloaded to the Security Expert controllers and Suprema readers.

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 Numbers are rounded. Why two values of nearly equal magnitude are subtracted, significant digits are lost.  This occurs in a variety of places within EcoStruxure Buildings Operation, and explained using a script program in the example below. Product Line Ecostruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause In a string program and the NumToStr function, if a number (example 5.7) is entered and Save is selected, then the Value in the Variables window at the bottom shows 5.6999998. The value is altered from the original. Resolution When looking at a value in the watch window or variables view, there is no rounding so you are going to see the full length of the float number which suffers from a thing called “loss of significance” More information on float numbers can be found at: https://en.wikipedia.org/wiki/Loss_of_significance This phenomenon happens everywhere. An alternative would be to add a formatting feature to do the rounding. Script handles numbers as IEEE754 single precision floats, so the accuracy is limited to (IIRC) seven significant digits. The accuracy loss starts around 1.677E7. On www.binaryconvert.com/convert_float.html?decimal site, a decimal number can be converted to binary and then back to decimal in order to see how the decimal number will be handled in Script. Script handles numbers as IEEE754 single precision floats, so the accuracy is limited to (IIRC) seven significant digits.   The accuracy loss starts around 1.677E7.   On this site you can convert a decimal number to binary and then back to decimal in order to see how the decimal number will be handled in Script. http://www.binaryconvert.com/convert_float.html?decimal

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue When starting Vista software (other than Vista Server) an error appears stating that the license has expired. lc_checkout failed: Feature has expired. Feature: Menta.View Expire date: 31-May-2011 License path: C:\Program Files\Schneider Electric\License Files\Demo_5_1_31_may_2011.lic FLEXnet Licensing error:-10,32 For further information, refer to the FLEXnet Licensing documentation, available at "acresso.com". Product Line TAC Vista Environment Vista Workstation Menta TGML Editor Vista Webstation Cause The temporary trial license for Vista has an expiration. If Vista returns an error stating that the license is expired this may be due to one or more of the following reasons: The temporary license file being used has indeed expired Vista was pointed to a temporary license file that has now expired rather than being pointed to the license files folder The computer date is set incorrectly Resolution Start by checking to see that the computer date is set correctly. If it is set to a future date beyond the expiration date of the temporary license file this will prevent Vista from starting up. Check to verify that the temporary license file being used has not expired by opening Windows Explorer and browsing to the following folder: C:\Program Files\Schneider Electric\License Files or C:\Program Files\TAC\License Files if this is an older installation. The expiration date of the file is part of name of the file. For example, Demo_5_1_31_aug_2011 expires on the 31st of August, 2011. The terminal services licenses need to be updated every two weeks and the expiration date can also be found in the file name in a week-of-the-year format. The easiest way to find the exact date is to open the license file in a text editor  and the expiration date can be found in the first line. For example, the first line of the license file Demo+TS_OK_5_1_valid_through_week32_2011 is: "FEATURE Vista.Workstation taclic 5.1 14-aug-2011 uncounted \" therefore this license expires on the 14th of August 2011. If the exact license file rather than the license location was specified during installation, Vista may not be able to find a new temporary license file once the old one expires. The location where Vista looks for the license should be cleared out by following the steps in the resolution of Switching from the Demo license to the site License in Vista 5.1.7 or older. Once the registry value has been cleared Vista will ask where the license is found the next time it is started up.