Building Automation Knowledge Base

Issue Checklist to be used as a basis for Maintenance visits. Product Line Andover Continuum Environment Continuum Hardware Continuum Software Cause Having a checklist available for routine maintenance will help with service calls to ensure Continuum sites continue to run smoothly over the life of the installation. Resolution There is no official maintenance checklist but some of the things you might want to consider checking on a regular basis are the items below. Continuum Analyzer Run the tests which check the database for known issues and provides a results file. See How to run Continuum Analyzer and get a report.   Review Windows Event Logs Check the Application and System Event logs for Continuum or SQL related errors. See Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes.   Check the size of the ContinuumDB The Database can't be more than 2GB in MSDE, 4GB in SQL Express, and the size of available space on the drive if using full SQL Server. Continuum will always run better when the database is kept trim, as the database size grows, Continuum transactions may start to slow down. If general system slowness is observed then check the database size and SQL Server resources first.   Truncate/trim event tables in ContinuumDB Especially the ExtendedLog table which can grow very rapidly if not kept in check. See Set up a Continuum system to do automatic log truncation to save database space.   Check that the Continuum Workstation is patched and up to date Periodically service packs and hotfixes are released for different versions of Continuum to resolve identified issues. Consult The Exchange Download Center for the current updates. Service Packs | Hotfixes   Check that Controller Firmware is up to date Check that the Controller firmware versions are supported for your version of Continuum and that they are up to date. Same as service packs for Continuum, new firmware builds are released as issues are identified and resolved. You can find supported firmware for each version of Continuum in the Compatibility Matrix. See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation. And new firmware updates are available on Exchange Extranet.   Check battery charges On controllers that have them, check that the battery for holding up the active RAM still has a charge. How to check -> Battery life in Andover Continuum controllers that have onboard batteries Replacement batteries -> Replacement batteries for the various Continuum controllers   Run the Continuum Errors listviews to see if there are any recurring errors that may need to be investigated.   Most Importantly - Backup the ContinuumDB before leaving site! Backup and restore instructions for a single-user system are below but these also apply to full SQL Server using Management Studio. Steps 1 and 2 in the article below apply to backing up a ContinuumDB. See Move / Backup / Restore a database on a Single User SQL2005 Express system.

Issue During download to a b3 controller you may see the error: Unknown object Module: BACnet plugin Module code : 0 Technical info: BatchedWritePropertyError Product Line EcoStruxure Building Operation Environment Automation Server WorkStation Cause Binding sending data to a point during the download process Resolution This error is benign and can be ignored. Also check out the SmartStruxure - b3 Engineering Process - Part 6 Downloading Quick-Help video on the Exchange. NOTE The "BatchedWritePropertyError" may also be seen with "Property value out of range" rather than "Unknown Object", in this case check the properties/settings of the BACnet Object, the channel may be out of range or an Expansion Module may be required

Issue Looking at the Status Information on the MSTP network object under the BACnet Interface of the Automation Server, the status read online FALSE Environment Automation Server - AS Cause The AS is not being passed the network token. If the Automation Server sees the token being passed on the bus but it never receives the token the AS will tag the MSTP network status as OFFLINE.. Resolution Possible reasons/solutions. CAUSE: Baud rate mismatch with third party devices. SOLUTION: If device does not support auto-baud change the speed of the MSTP to that of the device. CAUSE: A device on the MSTP is using the same mac id as the MSTP port. SOLUTION: Resolve the duplicate id issue. CAUSE: A defective device on the MSTP SOLUTION: Identify the defective device and replace it.

Issue BACnet Interface has "!" with unresolved references Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v2.0 or later Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause During the startup of a Smart-X controller, the auto-association feature fails and the data becomes corrupted Resolution Go to BACnet Interface -> Time Sync Recipients Find any devices listed as DEVICE_<Instance ID>, select & delete Verify all devices listed are configured as follows: SmartX controllers Recipient Type: Reference Recipient Device Object Reference: <Device in System Tree> If Recipient Name does not match, copy from Object Reference and paste in the field. This helps humans troubleshoot the issue. DO NOT set Recipient Type = MAC Address, Network ID = Global Network or Local Network, Mac Address = Broadcast. This will set time on other ES/AS with BACnet Interface on the BACnet System.

Issue Uninstall PCT doesn't uninstall Oracle VirtualBox Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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 for assistance. Cause The uninstaller of PCT doesn't include VirtualBox as part of the uninstallation. Resolution 1. Uninstall PCT from “Control Panel\All Control Panel Items\Programs and Features”. 2. Uninstall PCT Client. 3. Uninstall Oracle VM VirtualBox.

Issue Information concerning Linux releases used within the Automation Server.   Product Line EcoStruxure Building Operation Environment Linux Operating System (OS) Building Operation Automation Server Building Operation Automation Server Premium Cause Questions concerning Linux releases used within the Automation Server. Resolution AS versions to 1.4.1 run Linux kernel 2.6.25.1 AS versions 1.5 to 2.0.2 run Linux kernel 3.0.101 AS-P versions 1.7 to 2.0.2 run Linux kernel 3.5.0-lsp-3.3.1 For questions concerning what type of Linux...i.e. Red Hat, Ubuntu, openSUSE - There is no linux distribution in the automation server just vanilla linux kernel. For further reading, download some documentation about the kernel from their website www.kernel.org  

Issue Using a 4-20 mA sensor on a Xenta 451A or 452A Product Line TAC Vista Environment Xenta 451A Xenta 452A Cause There is only enough power onboard a Xenta 451A or 452A for one 4-20mA.  Resolution Wire each sensor, using an external power supply for cases where there is more than 1 4-20mA sensor. Create an AI in the Menta file Bind the object to the 451A Select the correct Terminal Ref Choose the 4..20mA sensor If using this device as a stand alone LON module chose the 4-20 mA option for the nci NOTE: only Xenta devices ending in "A" have truly Universal Inputs.  For complete details on input configuration, see Configuring inputs on Xenta 421A or Xenta 451A when using the controller as a stand alone Lonworks node.

Issue Is there a way to capture CyberStation transactions so that I can debug workstation issues. I have been asked to send an ACCTrace capture file to Schneider Product Support.  How can I capture an ACCTrace record? Product Line Andover Continuum Environment CyberStation Workstation Continuum ACCTrace Extended logging Alarm delivery Alarm Logging Cause Some alarms are not being logged in continuum. Extended log data is missing or non existent. Resolution ACC Trace is a utility that can be used to capture the transactions CyberStation makes with controllers and with the Continuum database. ACCTrace.exe can be found in the Program Files\Continuum folder of the workstation PC. Once it is running, either use the default file name for the ACCTrace file, or a folder path and custom file name.  The extension should remain ".csv".  Note: ACCSniffer is a tool PSS generally does not use.  Once the capture file information is entered, select Start Trace.  Once the capture has been started, exercise the Continuum operations that are being tested.  Once the test is completed, select Stop Trace. The ACCTrace file is a complex record which cannot be readily interpreted by someone who does not have an advanced knowledge of Continuum software. It is often a good idea to include a Continuum Activity Log and Continuum Error log and possibly a Continuum Event log for cross analysis.

Issue Running SevenReports a C++ Run Time error. Happens either in Archive data reports or database reports yyyy-mm-dd hh:mm:ss Environment I/NET Seven version 2.16 to current Cause Scope of Data yyyy-mm-dd hh:mm:ss Resolution    The C++ Runtime error or crash of SevenReports is due to a timeout problem because the archived data is so much information. What you will need to do is a couple of things listed below: Run the archive file SevenReport or ArchiveSevenReport file with the following steps in mind 1. If using Archived reports, mount the archive file with the desired dates to search 2. when the date range comes up on the screen, offering to search with date, hour, minutes, and seconds yyyy-mm-dd hh:mm:ss limit the time range. The whole key here is to limit the time range. Example of range is below.   In other words, search for only 2 minutes on just one day. Do not put in three days, or three hours. Only search within a very limited search window. The crash occurs because there are huge archive or database entries with thousands of transactions that have to be sorted and searched through. The crash was due to the report program attempting to generate a report with to much data to sort through. Be patient. Even on old computers, with XP, 500MB or RAM, and limited resources, the reports will be produced.  Time and time again, this issue comes across. Using my old computer in the lab, the database from the customer is loaded, the archive files are loaded and still it works every time. The C++ Run Time error appears when expanding the search to more data and crashed the report. But limiting the amount of time to minutes or perhaps one hour, produces a report. (For an example of unusual examples: there have been 2 minutes of time for the search criteria, and 38,000 pages of report produced.)     2010-08-16 09:00:00 until 2010-08-16 09:02:00   One thing you may want to look into at your site if you are experiencing large amounts of data for reports is Scan Interval. Read TCON300 for more info. Information on Scan Interval and how this information is collected in the database. This is important because the more data you collect, the faster the scan rate interval, the more data will be in the reports. Input and Output Points Point Database Parameters   The Scan Interval field is used with all point types. Enter a number between 1 and 255. This is the length of time in seconds that elapses between point scans.   If the point is an external input point, the controller scans the point at the interval you specify here, and updates its state/value in RAM memory of the DCU.   If the point is an external output point, or an internal input or output point, the scan interval determines how often a calculated point equation controlling the point (if applicable) is processed.   If the point is an indirect input or output point, the scan interval governs the time it will take to go to the “old data” state.   The default scan interval is 10 seconds for input points and 60 seconds for output points. All points can have their own unique scan intervals. All external discrete input points are scanned for discrete contact changes at 100 millisecond intervals.   Note: Defining an individual scan interval reduces available RAM memory in the DCU by approximately four bytes. You can conserve DCU memory by using the same scan interval for multiple points.

Issue When running the stored procedure sp_changedbowner to change the dbowner to "andover97", the following error message is received: "The proposed new database owner is already a user or aliased in the database". Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 (Keywords: drop user ) 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. Cause The Andover97 user already has access to the database through an existing alias or security account within the database. This can occur when the DB is not restored properly to the SQL server. The database may have been detached and then attached again, which is not the preferred method of restoring a ContinuumDB. Resolution Under the ContinuumDB there is a "security" and then "users" folder. Check to see if the Andover97 user is in this folder. Continuum does not put this user in this folder. If it is there, then it will need to be dropped from the database before trying to change the dbowner. Do the following: Do a complete full backup of your ContinuumDB. Run the following SQL script to drop the user from the ContinuumDB. USE [ContinuumDB] GO DROP USER [Andover97] GO Re-run the stored procedure to change the db owner below. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO To minimize the chance of this occurring again, the correct procedure for moving or restoring a Continuum database is to do the following: Create a new ContinuumDB with Continuum's Database Initialization. This creates the DB, SQL jobs, stored procedures, adds Andover97 as an admin and a lot of behind the scenes security settings. Restore a previous backup over top of the ContinuumDB created in step 1. Change the db owner with the above query using the sp_changedbowner stored procedure. Re-initialize the Cyberstation into the Database using Continuum's Database Initialization.

  Issue How are Modbus 64-bit registers calculated in the Modbus limitations on an RP-C? Can both RS485 ports be used for Modbus on an RP-C? Product Line EcoStruxure Building Operation Environment SpaceLogic RP Controller series RP-C Modbus Cause EBO version 2023 introduced 64-bit register support in RP controllers. EBO Webhelp states that an RP-C has a maximum limit of 250 Modbus registers. It is unclear if a 64-bit register is counted as four 16-bit registers or just one register on the Modbus maximum count. The RP-C controller has two RS-485 ports, and it is unclear if both ports can be utilized for Modbus simultaneously. Resolution A 64-bit Modbus register is counted as one register in the Modbus maximum register count. The RP-C controller has two configurable RS-485 ports that can be used for: Sensor bus Room bus Modbus network As per EBO webhelp, the controller can host two networks, but only one network of each network type.

Issue Procedure for converting a bCX9640 to a CX9680 (NC2) Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 (NC2) 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. 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 Having difficulties binding (pairing) room controller with MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) SE7000 Room Controller Cause Unable to make sense of LED blinks status Resolution The room controller cover needs to be removed to expose the LED located on the ZigBee communication module.   Here is a description of the LED status for Sigma Room Controllers (SE7000 Series): Blinks once: ZigBee Communication module is powered but might be defective or incompatible with the room controller base board. Blinks twice: ZigBee Communication module is compatible with room controller base board but cannot see any ZigBee network in its range that matches its own channel and PAN ID. Blinks 3 times: Room controller has joined the network successfully but it is not bound to MPM. Blinks continuously: Room Controller has joined the network and is placed in identify mode by MPM during the binding process. Blinks 4 short and 1 long: Thermostat is bound to the MPM and is communicating.

Issue Errors occur when trying to open up graphics in Vista Workstation similar to these: Microsoft .NET Framework Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. A generic error occurred in GDI+. TAC Vista Workstation Encountered an improper argument. Environment Windows 7 Windows XP Vista TGML Cause Installing Windows XP on a machine that came pre-installed with Windows 7 has been observed to cause this problem. Resolution Computers that are sold with Windows 7 pre-installed typically have hardware that is optimized for Windows 7 and often experience a variety of problems when they are re-imaged to Windows XP. The best solution is to re-install Windows 7. TAC Vista 5.1.4 and newer is compatible with Windows 7 as well as some third-party LNS network tools (check manufacturer's websites for more information). Windows 7 Professional, Ultimate and Enterprise can run programs using "XP Mode". XP Mode is a separate download available for free from Microsoft's website.

Issue Time Zone and DST when syncing time to an NTP server Time differs from NTP server with x hours. DST is not following NTP server time. Environment TAC Xenta 701, TAC Xenta 711, TAC Xenta 731,TAC Xenta721, TAC Xenta 511, TAC Xenta 527 NTP server Cause NTP provides UTC, no information about time zones or daylight savings ( DST)  is sent. So if you don't set the correct time Zone and DT settings the time will be set to UTC time in the device. Resolution Log in to Xenta server Go to  Configuration- Time- Regional Settings Set correct information

Issue Downloaded the WPT (WorkPlace Tech Tool) software.  How do I get a serial number so that I can complete the licensing form displayed with the "Purchase WorkPlace tech Software" program? Product Line TAC IA Series Environment WorkPlace Tech Tool 5.x.x Cause The WPT license generator program requires a "WIBS serial number" so that the license request can be generated. If the field is left blank, the program will not allow the license request to be generated.   Resolution The serial number is provided on purchased CDs so as to provide a method of tracing the manufactured CDs. To license the downloaded version of the Workplace Tech Tool software, you must enter an 8 digit serial number.  It is suggested, although not required, that you enter the current date as the serial number. When using the date as the serial number, enter the four digit year followed by the two digit month followed by the two digit day, i.e., in the format YYYYMMDD. For example, 20230203.

Issue Where can I obtain the technical information, manuals, guides or other documents on Continuum? (or other product lines) Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Continuum Cause Manuals and documentation can be used for training or self-help troubleshooting for Continuum. (or other product lines) Resolution Review the course notes The notes and document gathered during training can be very useful and a great source of information. Technical Documentation is available on the EcoBuilding Download site at: https://ecobuilding.schneider-electric.com/ For technical data/PDFs installed with Continuum, Go to Start > All Programs > Continuum > Documentation The discs and downloaded zip files that are used to install Continuum also include technical PDFs. Some of these are installed when Continuum is installed. (CONTINUUM) Most of the online help is context based, thus if you click help within a InfinityNumeric, then InfinityNumeric help is given. This help file can also be searched in the normal way. It is an excellent source of information. (CONTINUUM) Bookmark this Knowledge Base:  https://community.se.com/t5/Knowledge-Base/tkb-p/knowledge-base_public New articles are added daily and should be used as a first stop for self help. The Exchange Community site has a community space just for Continuum, SmartStuxure, Sigma, Vista etc.  for posing questions, sharing solutions, https://community.se.com/ (CONTINUUM) The Continuum catalogue also provides a good overview of the product range Some documentation is freely accessible, see https://www.schneider-electric.com/en/work/products/building-automation-and-control.jsp If an end user has problems on site, they should first contact Schneider Electric local support or service department (In the UK contact Support Bureau 0870 606 2800, cs.bureau@uk.schneider-electric.com) SmartStruxure For Building Operation help can be found online at: http://help.sbo.schneider-electric.com/home/index.castle?locale=en-US&productversion=1.8   CONTINUUM ONLY Always ensure the site fits within the Continuum Compatibility Matrix, this includes:  For PC requirements see the relevant Installation Instructions included with the Continuum Software Controller firmware (Continuum, BACnet, Infinet), use the most up to date available (of the correct version) Workstation operating systems, service packs and .NET framework versions SQL versions See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for other system data The Continuum.chm file found in the Continuum directory include the "online help" It is usually worth ensuring the latest Continuum service pack is applied to ALL workstations on site (Cyberstation and WebClient) Click Here

Issue Although data is read correctly from the TSI Pressura RPM20 Hospital Room Pressure Monitor when integrated to a SmartStruxure Solution Automation Server, Modbus read errors and framing errors are seen. Product Line EcoStruxure Building Operation Environment SmartStruxure Solution Automation Server SmartStruxure Solution Automation Server Premium Modbus RTU Cause The instruction manual from the manufacturer incorrectly lists  the Modbus communication parameters for the RPM20 as 9600 baud, 8 data bits, 2 stop bits and no parity. Resolution Investigation of the data from the device shows that the Modbus communications parameters are: 9600 baud 8 data bits 1 stop bit No parity Ensure that these parameters are set in the Automation Server Modbus Master Network configuration.

Issue After a card is created and added to a user, card is read and the credentials are invalid and not working. Product Line Access Expert Environment Access Expert, Server 2012 R2 and above. Version 2 Version 3 Cause There are several reasons that  could cause Access Denied to occur as listed below. Resolution To resolve the issue please follow the steps below: Access Denied – Invalid Card Format The intelligent controller has no configured card format which matches the number of bits sent from the credential reader. Opening this event inside the live monitor or event history view will display the card bit length of the credential along with its hexadecimal encoding. Access Denied – Invalid Facility Code The intelligent controller has a card format which matches the bit length of the card, however there are no card formats which match the facility code. Opening this event inside the live monitor or event history view will display the interpreted card numbers & facility code based off of the card format with matching bit length. Access Denied – Card/PIN Not Found The intelligent controller has matched the card format & facility code, but has no matching card number value. Opening this event inside the live monitor or event history view will display the interpreted card number & facility code based off of the format with matching bit length. When receiving this event with a card believed to have been programmed correctly, Users may issue a clear/reload cards on the controller to update the database. Access Denied – No Door Access The intelligent controller has acknowledged that this card has access on this intelligent controller, but not to this particular reader.     Access Denied – Door Schedule The intelligent controller has acknowledged that this card has access to this reader, but it is outside the allowed schedule. This event may also trigger if the interface dip switches are not configured correctly. **Don't forget to take advantage of Mercury’s Simulated Card Read functionality to ensure that the controller is making the correct access decision. In V3 the Card Formats needs to be added to the Controller in Order for this to work. **If a reader produces no audible response or LED change when a credential is presented it means that either the reader is powered incorrectly, or that it cannot read the credential technology.

Issue Cannot generate a report from Access Expert V2. Getting an error when attempting to generate the report "Could not load file or assembly Microsoft.ReportViewer.WebForms, Version=11.0.0.0"   Product Line EcoStrucure Access Expert Environment Version 2 Report Viewer Windows Cause The ReportViewer files that are from Feenics's website contain version 11. Microsoft does have older and newer versions of the file (i,e 10 and 12) so there is a potential that these files will not work. Resolution To resolve this issue 1. Download the Microsoft Report Viewer (Feenics Training> Web App V2> Miscellaneous Downloads) http://www.feenics.com/Downloads/ReportViewer.zip 2. On the Access Expert application PC (Not the SQL Server PC in a 2 PC system)     Uninstall all versions of Report Viewer and SQLClrTypes from Windows> Control Panel> Programs and Features 3. Stop the Feenics Keep Render Service 4. Unzip the Download files (Report Viewer.msi  and SQLClrTypes.msi) and install both of them 5. Restart the Feenics Keep Render Service Test Reports 6. If they are still not working, reboot the Access Expert PC and test again. If this is still not working, contact your local country support.