Building Automation Knowledge Base

Issue The word TEST is displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation preventing it from being commissioned. Environment Satchwell Climatronic CSC5252 CSC5352 CXR5805 CXT5605 CZT5305  Controller Display TEST LCD Screen Cause The cause of the word TEST being displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation and preventing it from being commissioned is normally due to a micro processor programming error occurring during the course of production. Resolution There is no field remedy that can be applied to a Climatronic Controller displaying the word TEST on the Liquid Crystal Display screen that will enable it to be commissioned successfully. The Controller should therefore be returned to the vendor for replacement under the terms and conditions of the warranty applicable at the time of purchase.

Issue When installing SQL server 2008 or SQL 2008 R2 to manually an instance for I/NET, Vista or Continuum, sometimes an error "Invoke or BeginInvoke cannot be called on a control until the window handle has been created" will show up. Environment SQL 2008 / SQL 2008 R2 Vista I/NET Continuum SmartStruxure Cause This issue is happening because of a behavior change in .NET that is exposing an issue with SQL Setup User Interface (UI). Resolution Generally, if you just rerun the installer, it won't hit the issue again. If this can't help, just manually create a C:\temp folder and it will work fine.

Issue In the past there was no way to calibrate the space temperature from a STR-150 when used with a Xenta 121 FC/HP.  Environment STR-150 Xenta 104A Xenta 120 Xenta Programmables Cause Any calibration applied to the temperature of a STR-150 had to be done downstream of the stat in the controller. In the past when the STR-150 room stat was wired up to a Xenta 121 there was no way to calibrate the space temperature as the Xenta 121 FC/HP had no kind of Temp Offset in the controller. Resolution Starting with version 1.4 (released September 2013) of the STR-150, there is a calibration feature built into the stat. This feature allows the calibration to be applied before the temperature is sent down to the controller (Example: Xenta 121 controller). Below you can find out how to check the version number of the stat and how to perform the calibration. There is not a way to upgrade older versions of the STR-150 to 1.4 or greater. Checking the STR-150 version number The version number of the stat can be found as parameter P0. View version: Push the fan and bypass button simultaneously for 2 seconds to display P0. The version number will be displayed here. Using the STR-150 Calibration Feature Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0.   In P0, hold down the bypass button and push the fan button three times to enter configuration mode. Note: the wrench symbol is lit when the STR-150 is in configuration mode.   In Configuration Mode: Press the fan button repeatedly until you reach parameter F0. Note: The two digits farthest to the left on the display show the parameter, while the two digits farthest to the right show the value.   Use the increase or decrease button to adjust the value. The offset scale ranges from 0-99 which corresponds to -5.0 to +4.9 degrees. If the STR-150 is setup for degrees C, then the offset is exact. If the STR-150 is setup for degrees F, then the offset is recalculated to a corresponding value.   Exit Configuration Mode: Push the fan and bypass button simultaneously for 2 seconds or allow the idle timeout to exit configuration mode on its own.

Issue How to set up extended logging. Product Line Andover Continuum Environment Continuum Cyberstation Extended Log Cause Configuration of extended logging. Resolution Sample configuration for extended logging. This example would create enough entries for a 24 hour period. Create an Infinity Numeric Select the logs tab Number of entries (96) Type will be LogInstantaneous (Stores the current value of this point at the beginning of every interval) Interval will be 15 minutes (15 minutes in a 24 hour period is 96 which is what we set for the Number of entries) By default the Workstations are setup for 5 minute checks to the controllers to see if there are extended logs to enter into the database. For more in-depth configuration of extended logging, please review Extended Logs in the Continuum Online help system.  For performance and load balancing please see Extended Logging gaps, performance and load balancing.

Issue Error 'The UPREV engine was asked to process an invalid code type' when flashing the firmware in the controller. Product Line Andover Continuum Environment bCX9640 CX9680 ACX5720 ACX5740 Cause RAM issues Resolution Using a browser login to the controller and perform a 'Clear Database Backup', commit changes and restart the controller. When the controller has re-started  disconnect the battery, power down the controller and after a minute power the controller up and re-connect the battery. Wait for the controller to come back online and then try the uprev operation once again.

Issue Does Schneider Electric support the Niagara Andover Infinity Driver? Environment Niagara Infinity Driver Infinet Drivers Cause Unable to get Andover Infinity Driver working. Resolution The Andover Infinity Driver was created by and for Tridium.  Schneider Electric do not sell nor support this driver and all enquiries should be referred to Tridium.

Issue Customer wants a customizable permanently installed touch-screen display instead of a computer and web based graphics for display of points from their network of I/A Series BACnet controllers.  They would like to accomplish this without having to create shadow objects in a UNC or ENC. Product Line TAC IA Series Environment I/A Series MNB family of controllers Optional ENC or UNC Cause Customer does not want to deploy computers that would be easily stolen but instead wants to have permanently installed touch-screen displays. Resolution The LoyTec LVIS-ME212 or LVIS-ME215 touch panels can be directly connected to any BACnet-IP or BACnet-MS/TP network and can be linked to any BACnet object on the interconnected BACnet networks including those objects accessible over attached BACnet routers such as an ENC or MNB-1000. Available through the Schneider Electric iPortal online ordering system as LOY-LVIS-ME212 and LOY-LVIS-ME215  

Issue What specification should the Continuum Infinet bus cable meet? Environment Systems using Infinet comm's  with i2 & i1 Infinet controllers. Cause Often an incorrect cable type is used when wiring Infinet devices (Infinet Controllers), unless the correct cable specification is used it is unlikely you will get reliable communications. Resolution Infinet Cable Specifications : Cables used to form the Infinet should conform to the following specifications: Wire Size: 24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 120 Ω Velocity of propagation: 78% Capacitance: <12.5 pF/ft between conductors and < 22 pF/ft between the conductor connected to ground and the next conductor.

Issue Information Environment Optimiser/compensator Controller Cause Requirement Resolution Specification No. STC600D Part No. 5126020000

Issue Upgrade warning and Error Conversion Log Analysis Additionally upgrading an AS from version 1.3 to 1.4 can create a number of unresolved or invalid references. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, ASP, ASB Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause When upgrading using the Device Administrator various warning and errors can be seen. Errors will prevent the upgrade, but warning will still allow the upgrade to continue. Starting in version 1.4, new rules have been put in place that will invalidate some bindings that had previously been made in older versions. These rules may cause errors to be produced in the Conversion Log found in the Device Administrator. The three new rules are: Public Numeric/Signal bindings will be dropped. Multiple bindings will be restricted to one. Binding to Local Node NVIs will be dropped. For more information regarding the rule changes made in version 1.4 see Reference Guide and References beginning with 1.4.x. Resolution Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see Upgrading Automation Servers from 1.3 to 1.4. Breakdown of the Conversion Log The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

Issue Get "Value does not fall within expected range" error message when trying to view values from a Vista node in webstation. Environment Vista 5.1.X Webstation 5.1.X Vista in network (master with at least 1 slave) Cause This is a COM error caused by a difference in regional settings on the Vista servers. E.g. 100 000.00 may be retrieved as 100,000.00 if other settings are used on another server. This will cause a mismatch. Resolution Ensure that the settings for digit grouping and decimal symbol are the same on all Vista servers. Click on Start\Control Panel\Regional and language options. Select Customize and check the settings on the Numbers tab. Compare these settings with the other Vista servers.

Issue Continuum reports an Unknown Model Number error. Product Line Andover Continuum Environment Controller Model number Bootloader Learn Cause Possible reasons why Continuum may report an Unknown Model Number error. Controller is in bootloader mode. Controller is not responding fast enough due to a comm issue. The controller type saved in the Continuum database is different from the controller type physically installed. The total number of controllers exceeds the maximum number of nodes allowed on the Master. The baud rate of the bLink is not correctly set for the MSTP bus. The comm bus is not stable. Problems introduced to the bus due to a bad controller or electrical interference. Resolution Communication issue must be troubleshot by using a combination of Controller error logs and LAN capture analysis. A controller can be brought out of bootloader mode by flashing the firmware.  Create the device manually. Attempt to learn the controller onto the bus with no other controllers attached Correct misaligned baud rate settings. Run an ACCTrace at the Workstation during a learn to detect duplicate IDs. Other articles that address this issue: Unknown model number error when learning I2/b3 device Learn Process stopped and get an error "Can not learn this controller, it contains an unknown model number"

Issue Virtualization using VMWare, Virtual Server or other products is useful when deploying applications Is virtualization supported with Continuum?  Will Continuum work in a virtual environment?  Environment Continuum WMWare Virtual Server Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Continuum compatibility with Virtual Machines (virtualization - VMWare) Resolution VMWare VSphere 5.5 and 6.0 has now been qualified to work with Cyberstations and Web.Client in Continuum v2.0 and above. Note that this will require a software licence and that the virtual environment must comply with the minimum system requirements for Cyberstation and Web.Client Server. See the latest Continuum v2.0 Compatability Matrix for details.                                                         There have been reports from the field from engineers that  have used Continuum and SQL server with various virtual software not currently qualified. If there are any issues with this implementation with an unqualified solution, then it would be necessary to install Continuum on a supported configuration (see the Continuum Compatibility Matrix) prior to involving engineering to evaluate any problems. This solution has not been tested and is outside of what we currently support. These include: Other VMWare environments, Microsoft Virtual PC (HyperV), Citrix, Windows 7 XP Emulation, etc. Marathon Redundant SQL Servers is a very specific solution which does use virtual machine. This is an isolated case and does not apply to standard implementations of Continuum or Webclient.

Issue How many Modbus TCP Clients can be connected to Vista via an Xenta 913? Product Information TAC Vista Environment Vista 5.1.X Xenta 913 5.1.X or later Xenta 511 5.1.5 or later Xenta 701 5.1.5 or later Xenta 711 5.1.5 or later Xenta 721 5.1.5 or later Xenta 731 5.1.5 or later Cause When planning a system it's important to know how many devices are required. Resolution A maximum of 40 Modbus TCP clients are supported when communicating via a Xenta 913, Xenta 511 or Xenta 700. Each TCP Client may have up to 100 Modbus devices (see page 4 in the datasheet).  

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue How to calculate total memory required for controller to store logging information for the required duration. Product Line EcoStruxure Building Operation, Andover Continuum Environment NetController (CX9900, CX9940, CX9680, bCX9640) InfinetController (i2xxx) BACnet Controller (bCX4040, bCX9640, b3xxx) Cause Need to know how much memory is needed per point to determine the maximum number of entries and minimum interval time that the controller can use. Resolution The general equation of calculating memory use for controller logging is as below; * Memory usage per point = { 8bytes + (4bytes * NumberOfLog) } In addition to that, each controller requires minimum 1~2KB of freemem after the controller logging memory allocated.  Regarding the log interval, if the point is being logged for controller only, you can set the interval in seconds unit.   But if you configure the point for ExtendedLog as well, the logging interval should be in minute unit. Again, if there many objects with one minute interval for Extended Logging, it will affect the performance of the Cyberstation and also increases the size of ContinuumDB dramatically in short period of time. In this case, consider increasing the log interval to 5 ~ 15 minutes for Extended Logging.

Issue Are 64-bit operating systems supported on the Andover Continuum product line? Product Line Andover Continuum Environment CyberStation webClient Cause Compatibility requirements for Andover Continuum with 64-bit operating systems Resolution Release 1.93 and earlier: For all machines with CyberStation or webClient software installed, only operating systems running in 32-bit environments are supported. 64-bit environments are not supported.  However, for the Database Server on a LAN system where no Cyberstation or webClient software is installed, a 64-bit version of Windows Server 2008 (SP2) or Windows Server 2008 R2 may be used on systems running V1.92 and above. These will also require Microsoft SQL 2008 running in 64-bit mode. Release 1.94 and later: Release 1.94 supports 64-bit Operating Systems, however, Microsoft recommends the 32-bit version of Office 2010 because it prevents potential compatibility issues with other 32-bit applications, specifically third-party add-ins that are available only for 32-bit operating systems. Please refer to the release notes for compatibility notes in specific versions.

Issue The CPU light condition allows for limited troubleshooting of Expansion Modules Environment Continuum i2 controllers b3 controllers BCX B4920 ACX 57xx Cause Expansion modules require troubleshooting and the CPU light offers some information Resolution The expansion module closest to the controller will blink once at a 2Hz rate. A second module connected to the first expansion module will display 2 short blinks every 2 seconds Incompatible or malfunctioning expansion modules may display the CPU light as a steady ON or ON and then completely OFF When main power supply does not provide enough power for the controller and connected expansion modules, the CPU light of expansion module display a steady ON.

Issue Will there be any problems wiring two HID iClass RP40 readers to one reader channel?  Environment ACX57xx, AC-1 Cause Need two readers on a vehicle entrance at different heights Resolution Tested (2) HID RK40 (iClass with keypad). The RP40 uses less power but should be very similar. Not recommended to power the two readers from the same reader input unless you are sure the reader input can handle the combined peak mA rating of the two readers. ACX5720 - worked fine. The RK40s were powered with different reader channels and then just doubled up the 1-DATA, 0-CLK and LED1 terminals on the ACX with the DATA1, DATA0 and Green LED leads from the readers. AC1 - worked fine. The AC-1 terminals are small so a single piece of wire was used off the DATA/1, CLK/0, and LED terminals of the AC-1 and landed on a terminal block with DATA1, DATA0 and Green LED leads from the readers. The RK40s were powered with an external power supply.  

Issue Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147) lcaErrNsLicenseViolation 147 LNS license access failure. Product Line TAC Vista Environment LonMaker, NL220 LNS Network Cause Feedback from Echelon on this error message. A variety of conditions may cause this error. Some relate directly to internal licensing components. For example, the license DLLs may not have installed properly, the files that identifies the license (nsseng.exe for the LNS Server, lonmaker.DSL for LonMaker) do not exist, or the Crypkey licensing components (crypserv.exe and ckldrv.sys) are not running properly. You can resolve these problems by deleting the files that may be causing problems, and re-installing LNS. The license DLLs, as well as the crypserv.exe and ckldrv.sys files, can be found in the Windows 'LNS Licenses' folder, and the Crypkey files can be found in the Windows 'system32' folder. Note that you must stop the 'CrypkeyLicense' service and 'NetworkX' driver before deleting the Crypkey files. Certain conditions on the PC operating the license may also cause this error. For example, if the PCs file system is corrupted or low on space, or if the license files have been manually deleted, tampered with in any way, or moved by some disk-defragmentation utilities, this error will occur. You can resolve these situations by ordering a replacement license key. If the PC clock is set back to a time before the creation of the license or before the last time credits were purchased, this error will occur. In some cases, this can be resolved by rebooting the PC. Otherwise, it may be necessary to order a replacement key. The error may occur if the license has been transferred out of the PC, manually terminated, or if there are zero maximum credits. In this case, you need to purchase additional credits for the license. For more information on licensing, see Chapter 13 of the LNS Programmers Guide. Resolution It is very likely that you have corrupted LNS Credits. To determine if this is the case and how to solve it please reference Corrupted LNS Credits.