Building Automation Knowledge Base

Issue PE program in i28xx controller controls the VAV with TriState Triac output, and the Triac output gets damaged randomly. Environment i2 controller ( i28xx , i28xx-V ) with Triac output. Cause The output channel can get damaged / burned when Triac output value is changed to +ON from -ON ( or to -ON from +ON ) without setting the output value to OFF before the change. Resolution Check the VAV control PE program and make sure the program sets the Tri-state Triac output value to OFF before changing it to the opposite value.

Issue A license is needed for using the Roam IO2 with ethernet Product Line Andover Continuum Environment Roam IO2 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause A license is required to use the ethernet feature with the Roam IO2 Resolution Follow the instructions for Generating a License request in the BACnet Service Tool Generating a License manual, (PDF attached). Include your contact information, PO (purchase order) and RA numbers for the RoamIO2. Send that information to Upgrades.Continuum@schneider-electric.com to process the request.

Issue The Save to Flash exclamation point (bang) shows on a Continuum BACnet controller object. Hovering over the icon, a tooltip comes up indicating that the controller 'requires flash backup'. However when performing a backup to flash, a result comes back that the 'controller doesn't need flash backup' and the exclamation icon remains. Re-loading the controller and performing a send to database have no effect. Product Line Andover Continuum Environment bCX4000 bCX4040 B3 Field Devices Cause Controller's restart mode not configured to use cool start (cool start = restoring DB from flash backup) Resolution Set controller's ACCRestartMode system variable to one of the modes below that includes cool start. The available re-start modes are (except in the b3885 and b3885-V): ACCWarmStartOnly (0) ACCCoolStartOnly (1) ACCWarmToCool (2)

Issue How can you find the Trend Log ID / GUID of trend logs in the Vista Server for use with custom reporting or querying of the SQL database? Environment Vista 5.x.x Cause The Vista database uses a Global Unique Identifier (GUID) for trend log storage in the SQL database. This Trend Log ID/GUID is stored in an property not immediately visible in the property window of the Vista Workstation environment. In Vista 5.1.7 a new database layout was introduced, database  layout version 2. The version of the layout  for the log database is possible to see from the Vista server setup. And it is possible to upgrade the database to version 2 with a tool called SQL Database Upgrade tool which is included in the Vista installation from Vista 5.1.7.    If using the new layout of the SQL database in Vista version 5.1.7 both the name of the trend log and the trendlog GUID is included in the TrendLog table. Resolution Single Trend Log Hold CTRL + SHIFT + right click and select properties of the trend log object. The Trend Log ID is one of the visible properties. Multiple Trend Logs Start a new search in Vista Workstation. Change the object types to Files\Trend Logs. Change the property to Trend Log ID. Leave the string as "*" for all trend logs. Click Search The results can be printed listing the database path, object name, and trend log id for use by the individual building the SQL reports. If using the new layout in Vista version 5.1.7 both the name of the trend log and the trendlog GUID is included in the TrendLog table.

Issue What are the correct settings for the i2 controller input reference resistors for different input types? Environment i2 Controllers Cause What are the correct settings for the i2 controller input reference resistors for different input types? Resolution See the section starting on page 71 of the i2 Controller Technical Reference. As a general rule, the reference resistor switch is ON for 10K thermistors, contact closures (including supervised) and counters; it is OFF for voltage inputs (which includes 0-20mA and 4-20mA current inputs since the use of the external resistor makes the input signal a voltage).

Issue Unable to save any program in a workstation giving error  "Unable to lock an object because it is already locked"   Environment Cyberstation Programs Cause This is usually caused by the FiringOrder attribute being locked, often due to a PC crash or other unexpected operating system shutdown. Resolution This is due to the firingorder attribute being locked, start the Continuum Command Line application, select the problem workstation from the network button. At the R> enter: firingorder editlock = false This should clear the edit lock and allow the programs to be saved. **Check to make sure that another program that accesses this program is not disabled.

Issue There are many issues that can happen at Cyberstation and some methods are needed to troubleshoot. Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are a number of steps and tools that can be used to troubleshoot Cyberstation Resolution This subject encompasses software and hardware. It isn't a comprehensive list but should offer some methods and tools to help troubleshoot Cyberstation or webClient. Typically errors that are Cyberstation or webClient related will display some sort of an error message on the screen which can be used to diagnose the problem. Isolated or System Wide - Is the issue happening on 1 or multiple Workstations? If so, it could be a system wide issue, but if it's just one workstation then it is isolated to this PC and could be an install, Windows OS, hotfix or hardware issue. Continuum Compatibility Matrix - A number of issues can happen if Continuum Service Packs or hotfixes or Windows Operating System (including Service Packs), Microsoft SQL Server, Internet Browser version and the version of Continuum or webClient do not match the matrix. See document Software and Firmware Compatibility Matrix Version 2.03 Cyberstation Error - Is there an error message that is being displayed. A list of some Cyberstation specific errors can be found by pressing F1 with Cyberstation open, select index, type in Error, select error messages, Cyberstation How do you locate error messages in Cyberstation? Windows Error - Is there an error showing in the Windows event viewer? This step can be very useful when troubleshooting Cyberstation problems from issues installing Cyberstation or SQL to problems happening because of a Windows Operating System issue. Typically there are errors, event ids, and details that occur at the time of an issue that can be used to search the web for a solution. These can also be sent into support for some help analyzing the issue. Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Windows Service Pack or hotfixes- Were any Windows Service Packs or hotfixes recently applied to this PC that could be affecting this installation? To display all the hotfixes on a PC, see the following MS article: Windows: How to List All of the Windows and Software Updates Applied to a Computer Installed Software- Since the issue started happening has any additional software been installed on the PC. Take a look in Start> Settings> Control Panel> Add/Remove programs(XP) or Programs and Feature (Windows 10) and see what may have been recently installed. Antivirus / Malware -  On some occasions, we have seen Cyberstations or webClient PCs affected by viruses or malware. If an issue is specifically related to one PC and particularly if that PC is exposed to the internet, but doesn't have any Anti-Virus software installed, it could be infected. Updating Anti-Virus definitions and Malware/Spyware programs and running scans is recommended to clean up the PC. Hardware Issues - PCs will break over time from wear and power bumps, etc. Memory, NIC cards and Hard Drives are typically what goes first. *Memory - Many PC manufacturers supply memory diagnostic features in the system bios to detect if a RAM module is bad. This will often show in a certain spot every time in a certain program, not necessarily Cyberstation and can actually indicate that is can't access a memory reference. *Hard drives - drives can crash or certain files can become damaged. Checkdsk and the Windows OS attempts to keep the drive clean, but sometimes reformatting the Hard Drive and reinstalling the Windows OS will be required to correct the issue. If it's a physical issue with this drive then the problem could come back and a new hard drive may be needed. *NIC (Network Interface Cards) - can cause connection issues and affect system performance. Not all NIC cards are created equal and at times integrated NICs(built into the motherboard) can be less robust than a third party NIC card. See the following for extensive troubleshooting advice, but often swapping the card is easier. Advanced network adapter troubleshooting for Windows workstations *Graphics Displays - Some issue are more related to Pinpoint or Video. Check the graphics display and see if the most up to date video driver has been installed. Run any diagnostic that may be supplied by the video card manufacturer or swap out the card. Windows Device Manager - In Windows device manager you may see a black exclamation point on a yellow field which indicates the device is in a problem state. There can be many reasons this can happen and is beyond the scope of this article. See the following MS article for more information. Error codes in Device Manager in Windows System Info and Belarc Advisor - These tools can be used to see what hardware and software are installed on the PC. System info is installed with Windows. Description of Microsoft System Information (Msinfo32.exe) Tool This can be sent into Product Support as a .nfo file and can be brought up with details. This information can be difficult to work with. Belarc Advisor - This is a free tool that can be installed on a PC and will display the information in a very readable browser format. This tool will often find things that may have shown in System Info but was difficult to find. Belarc Advisor Restore Point - Windows XP, Vista and Windows 7 all have the ability to restore the system to a previous place in time by using Windows Restore Point. This is a Windows Operating System function and has some risks associated with it, but can be very useful to get back to especially when the issue is happening on a Stand Alone setup. What is System Restore? If the restore point doesn't work then a reinstall of Cyberstation or the Windows OS could correct the issue. Lastly, a reformat of the hard drive and a complete reinstall of the Windows Operating System and then reinstall Cyberstation or webClient may be needed.

Issue The majority of the Satchwell MicroNet and Satchnet product ranges is now re-branded to Schneider Electric. Product Line Satchwell MicroNet Environment IAC-420-F IAC-420-P IAC-440-F IAC-440-P MN350-LON MN450-LON MN550-LON MN650-LON MN50-TS-LON MN50-TSP-LON MNN-COM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM MNN_RTC M50_RTC MN-TK MN-VWIO-NCP MN-VWIO-SNP MN-VW100-UK MN-VW500-UK MN-VWP500-UK MN-VWP2K-UK MN-VWP10K-UK MN-VWP60K-UK Monitor Tool MicroNet View Cause The branding exercise provided some insightful information regarding sales volume. As a result, a number of products that were low or zero sales have been discontinued. Resolution Updated June 2019   The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- For more information on the re-branding of the Satchwell MicroNet product range, see PA-00145A - Satchwell MicroNet Range Rationalisation and Schneider Electric Re-branding. Old Part Number New Part Number IAC420-F IAC420-P MN350-LON MN350-NCP + MNL-C (LON card) MN450-LON MN450-NCP + MNL-C (LON card) MN550-LON MN550-XCOM + MNL-C (LON card) MN650-LON MN650-XCOM + MNL-C (LON card) MN50-TS-LON MN50-TSP-LON (Panel Mounted Only) MNN-COM MN550-XCOM or MN650-XCOM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM  

Issue DCX 250, backlight is working but no text or splash screen is being displayed. Product Line Andover Continuum Environment DCX250 Cause Failure of controller hardware. Resolution Replace DCX250.

Issue The hostId for a computer running I/A Series G3 version 3.8u1 (or earlier) and N4 versions 4.2 (or earlier) may be changed from the result of a Windows update. Product Line TAC IA Series Environment I/A Series G3  I/A Series N4  Cause The hostId is automatically generated upon first install of the software and stored within the registry.  The location of the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update.The hostId is automatically generated upon first install of the software and stored within the registry.  The location of    the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. Resolution I/A Series G3 version 3.8.213 (or higher) and I/A Series N4 version 4.3.58.18 (or higher) have been modified to guard against Windows updates to prevent hostId changes.  Installations of N4 4.3 and/or G3 3.8u2 will continue to operate normally and will not assume a new hostid after a Windows update.  All previous versions of Niagara could generate a new hostid after a Windows update, requiring a license replacement.   Schneider Electric recommends updating I/A Series G3 and N4 installations to the latest released software in order to maintain the latest security protection and to gain benefit from the latest features.  These builds are:   I/A Series 3.8 Update 2 (3.8.213 and later) I/A Series 4.4 (and later)   Patch to address multiple Host IDs on a single Microsoft Windows© platform   A set of patch files have been created to stabilize the Host ID for cases where customers have not upgraded to the latest version of Niagara (see installation instructions below). Once these patches are applied to the older versions of Workbench the Host ID is stabilized and should not change if Windows updates are installed.   Note: This is a reminder that a 32-bit install will always generate a different host-id than a 64-bit install.   IMPORTANT NOTES REGARDING THE PATCHES   Patches are only supported for the latest update (maintenance) version for the relevant release. Patches are not available for I/A Series G3 release 3.5 and earlier, or I/A Series N4 release 4.0 or 4.1. Builds prior to G3 3.8.213 are considered unsupported. Customers applying these patches do so at their own risk. Newer versions of Niagara (3.8U2 and 4.3) have introduced a stabilized method of managing the Host ID and do not require any patch. The patches do not eliminate the issue of different Host IDs generated when installing 32-bit and 64-bit Niagara. Installation Instructions   The Host ID patch file is available for download on the EcoBuilding Exchange Download website.  Login to the Schneider Electric EcoBuilding Exchange Download Center and enter G3 and N4 Host ID Patches in the search area or the filename of the zip shown below.    Download the G3_N4_HOSTID_PATCHES.zip and unzip into a temporary folder. The archive contains 'nre.dll' for various versions of I/A Series G3 and Series 4.2 in a directory structure identifying them first by version and sub-directory identifying 64-bit or 32-bit Windows. The 4.2 folder also contains 'njre.dll' which will need to be copied only for 4.2 installations.  Follow these instructions:   Verify the installed java version to be either 64-bit or 32-bit. Start a Niagara Command Line (Home>/bin/console.exe) from the desktop of the platform to be patched. From the Niagara Command Line execute the command: nre -version One of the listed items will be java.vm.name. If the text contains “64-Bit” then the installation is 64-bit otherwise the installation is 32-bit. Stop any running station using Workbench's Platform Application Director on the platform to be patched. Exit Workbench if running on the platform to be patched. From the Niagara Command Line ... /bin/console.exe execute the command: plat uninstalldaemon  Prior to replacement, save a copy of the existing nre.dll located in /bin folder. If Niagara 4.2 is being updated also save a copy of the existing njre.dll located in /bin folder. Copy the version appropriate and OS appropriate (64-bit or 32-bit) downloaded version of nre.dll file to the Home>/bin folder. If Niagara 4.2 also copy njre.dll to /bin folder. Overwrite the existing file(s). From the Niagara Command Line (/bin/console.exe) execute: plat installdaemon Start Workbench.  Open a platform connection to the patched platform. Using the Application Director, start the station.  

Issue XIF files for the standard MNL controllers are available on The Exchange Download Center.  Please do not use with SmartStruxure.  See XIF files for Version 1 and Version 2 of MNL controllers. Product Line TAC IA Series Environment I/A Series standard (fixed profile) controllers: MNLRF2 - Fan Coil profile MNLRH2 - Heat Pump profile MNLRR2 - Rooftop profile MNLRS1 - Satellite 1 / Rooftop profile MNLRS2 - Satellite 2 / Rooftop profile MNLRV2 - VAV profile MNLRF103 - Fan Coil profile MNLRH103 - Heat Pump profile MNLRR103 - Rooftop profile MNOTPVA3 - VAV profile MNLRF3 - Fan Coil profile MNLRH3 - Heat Pump profile MNLRR3 - Rooftop profile MNLRS3 - Satellite 3 / Rooftop profile (revised previous Satellite 1) MNLRS4 - Satellite 4 / Rooftop profile (revised previous Satellite 2) MNLRV3 - VAV profile Cause XIF files are available if needed. Resolution Download the file TAC_LLC.zip from The Exchange Download Center. Also see the accompanying Readme file.

Issue A jobsite of MNL controllers was done with WorkPlace Tech 4.x.  The original databases are no longer available.  Can they be uploaded with WorkPlace Tech 5.x and will the upload convert them from 4.x to 5.x? Environment WorkPlace Tech versions 4.x and 5.x MNL controllers Cause Loss of original controller databases Resolution Uploading a MNL controller's program does not change anything within the controller.  Only downloads do. If a MNL controller was programmed with WorkPlace Tech 4.x and is uploaded with WorkPlace Tech 5.x, the uploaded file can only work with version 5.x.  If the resulting file is then downloaded to the same controller, the program version in the controller will then be at 5.x.  It will no longer work with 4.x.

Issue Upgrading an AS results in an empty database. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 StruxureWare Building Operation 1.1.0.362 to 1.2.0.767  Cause When upgrading the database, the Enterprise Server (ES) upgrades without error, but when upgrading the AS, the result is an empty database. Resolution StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 The problem is caused by the initial engineering of the system being carried out on an old AS that was not LON or BACnet specific, copying into new hardware at R1.0 then when upgraded to R1.1 the upgrade fails due to the wrong type of AS being used (LON or BACnet). This practice is not common place and rather rare. When the trace log is examined, they find that the upgrade fails due to the fact that an illegal object type is attempted to be created – a BACnet interface. This is not legal in an AS-L. The reason that this occurs is that the backup file is from an AS-L that had been restored from a 1.0 AS-B backup file. Check New Release or Upgrade StruxureWare Building Operation Site Software. The issue you face could possibly be a procedural one and this article clearly defines the steps. StruxureWare Building Operation 1.1.0.362 to 1.2.0.767 The solution is identifying problems with a period, space, or other character in names. Placing a period at the end of a name or accidentally having a space at the end is suggesting something is following or further action. If using BACnet, please see the note below. Problems with bindings which were still in tact when values were removed also are a potential issue and not properly removed.    Work Around: Backup AS Upgrade PC to 1.2 Open Device Administrator Upgrade AS to 1.2 DO NOT close Device Administrator Open StruxureWare Workstation Log into AS If Database is Blank go back to Web Browser Connect to AS Log in In the top right hand corner of the screen select Setting>Device Configuration Select the Server Log tab Click “Get all log files” Once downloaded, open “trace” using Notepad Click Edit>Find Type the word “nsp.csc.UpgradeManager ERROR:” The error lines run from date stamp to date stamp so isolate the line beginning with the year and ending with the next instance of the year. Here is an example: 2012-08-29 16:39:32.990 [32] nsp.csc.UpgradeManager ERROR:    Error Parsing Dump Objects:  RecoverableException: source/Path.cppy) ) Error: Invalid_Path (0x10001), module Coml(11), moduleCode 0, dispString "Heatsink Temp.", techString "Path& Path::Append(const UTF8String& name)"  The “dispString “_______”” section of this line will give you the object name that contains an illegal character. Downgrade the AS back to 1.1 Locate the dispString object and change the name so that it does not contain any illegal characters. This is typically a name ending in a period. NOTE: when the rename dialogue pops up, it will indicate that an illegal character is present to confirm you are modifying the right object. Backup the AS Re-Upgrade the AS to 1.2 If the upgrade fails, repeat steps 9-20 or call product support. Be prepared to provide a Db backup at 1.1 as well as the trace file from the 1.2 failed upgrade. BACnet Note: A BACnet device including an object name "East Duct Max." is no longer valid because of the illegal character at the end of the name. Before upgrading the ES from 1.1 to 1.2, remove any full stops/periods from any object names. "East Duct Max." is changed to "East Duct Max"  Other illegal characters include *°?|/"<> or ~ and an object cannot begin or end with a white space or period. Select TPA-SBO-12-0008.00 - ES upgraded from 1.1 to 1.2 loses database to review this TPA.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation, Project Configuration Tool Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a port group or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or port group you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode drop  down menu, click Accept. Note: The setting on the port group overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

Issue CSMC 3805 Codes, CSMC User Guide. Environment CSMC3805 CSMC CSMC 3805 Cause There is a code displayed on the controller screen. What does this mean? Resolution The codes display the plant status under certain conditions. They are as follows: L05 = Return Water Temperature Low Limit. F = Water Frost Limit (Flow or Return). L01 = Inside Low Limit (Frost). H4 = Flow Water High Limit. A = Alarm (If alarm display is not required set code B61 to 1). 0 to 9 = Optimiser Status (only displayed if code B49 is set to 1). The User Guide can be downloaded from here.    

Issue When using the Modbus RTU X Driver to communicate to multiple Socomec Diris A20 electric meters it has been found only 2 or 3 devices can be networked together, even using a b-Link to boost the signal does not resolve the issue. Product Line Andover Continuum Environment Modbus RTU X Driver on bCX1 or Netcontroller II B-Link repeaters Cause The Socomec Diris A20 meters require a minimum of 4V RS-485 signal to communicate reliably, but the EIA RS-485 standard only calls for a +/- 1.5 volts signal and the Receiver Input sensitivity should be +/- 200mV. When using a bCX1 with the X Driver on Comm1 you will require a b-Link to provide the RS-232 to RS-485 conversion, although the B-Link fully conforms to the EIA RS-485 standard it does not have the drive levels required by the Socomec products. Resolution To resolve the non standard electrical requirement of the Socomec Diris meters use a Socomec RS-422/ RS-485 Repeater this will output the required electrical levels required by the Diris meters, the Socomec  part reference is 48990120.  Please refer to SOCOMEC Communication accessories or RS-422/485 Repeater Operating Instructions   If a B-Link is to be used each RS-485 output that is used will require a separate Socomec repeater.  

Issue How to set the Network 8000 MicroZone II (MZ2) back to its factory-default settings? Environment Network 8000 MicroZone II (MZ2) Cause Need to set the Network 8000 MicroZone II (MZ2) back to its factory-default settings Resolution See Technical Bulletin 95-08 for a detailed procedure. Revised 12/22/2011

Issue How are two 4-20 mA loop-powered sensors wired into a MNL-200? Environment MNL controllers with at least two UI inputs (MNL-100, MNL-150, MNL-200, MNL-800) Cause n/a Resolution The image below provides a basic (but accurate) diagram of two loop-powered sensors and how they are wired with a power supply and a MNL controller.

Issue Unknown meaning of object status numbers and descriptions Product Line Andover Continuum Environment Continuum Cyberstation Cause Continuum uses object status numbers and descriptions for diagnostics.  A list of these enumerations is required. Resolution See file Stsvc.txt in the Continuum directory In Continuum Versions 1.5 and higher, a new database attribute exists. This new attribute is "ObjectStatus". When the value of an object in the Continuum system is greater than zero, then an indicator icon is placed on that object in the explorer view. This indicator icon is also placed on the parent object and subsequent parent objects as applicable. This indicator icon will reveal the reason it has been placed on the object when you place your mouse over the indicator icon. This ObjectStatus attribute value is a bitwise type of attribute. ObjectStatus values and their descriptions: 0   - No mouseover, display normal 1   - Requires a Save from Controller (Parent) 2   - Requires a Save from Controller (Child) 4   - Requires a Flash Backup 8   - Object must be reloaded 16  - Object has been offline edited 32  - Object has been offline created 64  - Flash backup disabled 128 - OS update fail Combination values will display more than one description.  For example, 144 would display OS Update Fail and Object Has Been Offline Edited

Issue Need to be able to read and write to a point. Environment StruxureWare Building Operation Workstation ES AS Cause Need to be able to read and write to a point. Resolution Declare the point as Output and bind it. Outputs can be read and written.