Building Automation Knowledge Base

Issue Netcontroller power supply is not working as expected. Environment NC1 NC2 CX9900 CX9680 PS120 UPS Cause Problems with Netcontroller power supply. Resolution UPS not working Replace failed 5 Amp pico fuse (located on PC board adjacent to the UPS cable connector) UPS cable or connector has failed or is defective. Insufficient UPS battery capacity is attached to the UPS connector.  UPS requires two 12 VDC batteries). UPS Batteries are not sufficiently charged or have failed. No Power to NetController 3 Amp Slow-Blow fuse has failed.  (located on PC board adjacent to 120 volt power connector). Power switch is shut off. Insufficient supply voltage. General Mode switch is in the wrong position (See manual) Click here to download the PS manual

Issue Metric vs. Imperial Units as displayed Using Webstation Regional Settings Any device, will by default, show configured units. Regional settings must be applied to normalize all devices. Product Line EcoStruxure Building Operation Environment Webstation TGML Graphics SNVT values Cause Incorrect Units will appear in webstation if webstation regional settings are not configured correctly. Resolution Log into Webstation Select Settings > Change Regional Settings   Select the desired Language Select the desired Measurement system Click Ok NOTE: Settings are preserved via a cookie stored on the local PC. Any time cookies are deleted this will return to its default setting.

Issue TAC 200 OTP User Guide TAC 239W DHW User Guide Environment TAC 200 OTP TAC200 OTP TAC239W TAC 239 W Cause Information required regarding the TAC200 OTP Optimiser/Compensator Controller. Information required regarding the TAC239 W DHW Controller. Resolution Download here the TAC200 OTP guide. Product Part Number: 200-1005-000 Download here the TAC239 W guide. Product Part Number: 239-1010-800

Issue What are the locations where Controller configuration data is saved? Environment Continuum Cyberstation Continuum Controllers Cause Unsure as to where controller configuration information is stored and how to clear/reset this information if required. Resolution There are a number of different locations that a controllers database (configuration information) is stored - there are four locations for a BACnet controllers database and three for an Infinity controller. 1. Continuum SQL Database - Infinet tree In Continuum Explorer, this is where the controller is originally created as a Device object under a Network Folder and commissioned into the Database. This is the location where objects (inputs, outputs, programs, etc...) are created. When creating a new object, it is created in both the SQL Database and also sent out to the controllers database at the same time. The controllers information stored in the SQL Database can be sent out to the controller at any time by performing a reload of that controller (right-click Device object, Send to controller). This information can be removed from the database and the controller by deleting individual objects or by deleting the entire Device object. If the Workstation where this delete was performed is online to the field devices then the same object(s) will be removed from the live controller in the field as well as from the SQL Database. If the Workstation is offline to the field controllers  (Workstations can be taken offline for offline editing) then this delete is only applied to the objects in the SQL Database – the objects will still be located in the controllers though, creating a mismatch between the two until the controller is reloaded. 2. Controller RAM This is the active location of memory on the controller where the running database resides. On most controllers there is a backup battery that keeps this RAM alive with a trickle current when there is no power to the controller. When the controller is powered up it first tries to load its active database from RAM - this is the most current backup. The database in controller RAM can be cleared by pressing the Reset button on the Runtime tab of the controllers Device object in Continuum Explorer. 3. Controller FLASH This is the backup location of where the controllers configuration database resides. At any time the active RAM database can be saved to backup Flash by selecting "save to flash" from the controllers Device object in Continuum Explorer. This then makes an exact copy of the database in RAM (excluding point values) that can be restored at a later date either manually or automatically if the controller reboots and their is no valid database in RAM. For Netcontrollers and bCX's, this database saved to Flash can be deleted from the controllers configuration page (configuration webpage) select Clear Database Backup and then commit changes to controller. If the controllers webpage cannot be accessed, pushing and holding down the controller's reset IP switch for 30 seconds clears any backup in flash in addition to resetting the IP address and ACC node id to default. Another way to clear a controllers flash is to save a blank controller database to flash. Create a new controller Device object and then save that to flash. 4. Continuum SQL Database - BACnet tree The information stored in the BACnet tree is the BACnet side of our configured Infinet objects. This is the BACnet objects as seen in the controller and as third-party BACnet Devices will see them. When performing a "send to database" on the BACnet side, the Workstation goes out to the controller in the field, grabs all the BACnet objects and exposes them in the BACnet tree so that they can be used within Continuum. These can be deleted from the BACnet tree without harming those objects configuration in the controller or the Infinet tree. To recap:   To Create and save objects to the controller requires a two step process. Step 1: Create Database objects using Continuum Cyberstation. Objects are added to both the active RAM of the Controller and the SQL Database. Step 2: Save to Flash on the Controller. The objects in active RAM are backed up to the Flash RAM. If unsure, the only way to know that the Database in the RAM and Flash is the same as that in the SQL Database is to perform a reload of the Controller and then backup to Flash. Step 3: Send to Controller to reload configuration information from SQL Database to Controller RAM. After reload, redo Step 2 to backup to Flash. To completely wipe configuration information from a controller in the field you will need to clear its active RAM and its backed up Flash. If you want to clear all information of the controller from the field and the SQL Database then you will need to clear the RAM and Flash and delete the Device object from both the BACnet and Infinet sides of the tree. If you want to remove specific configured points from the controller but retain it in the tree, you will need to first delete the BACnet side of the controller from the BACnet tree, then you can delete individual objects (or make changes) from the Infinet tree.  

Issue In BAS and Sigma, what batteries and PSU cards can be used in a x96 controller.? Product Line Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

Issue The communication with TAC Xenta controllers is slow or inconsistent Product Line EcoStruxure Building Operation Environment TAC Xenta LonWorks communication Cause The Non group receiver timer is not properly set. Every device has a timer called Non group receive timer. The Non group receive timer is used to make sure that a re-sent Lon package will not be treated as a new message and to determine when a receiver buffer can be released. It is used in Acknowledged, Repeated and Request/Response transactions, but not in Unacknowledged ones. If this timer is set too low, a re-sent package, like Unacknowledged repeated message, may be treated as new messages, that will be sent on to the application. The communication buffers will not be released until the timer has expired. If the timer is set too long, that may result in the device running out of buffers, and new messages will not be received during this time. If a device has many SNVTs or TACNV’s being transferred there may be a need to increase the value of the Non group receiver timer. The default value for a programmable Xenta device is 768 ms. Resolution Change the Non group receive timer of the Xenta devices. The default value for a programmable TAC Xenta device is 768 ms. The recommended timer values are:   Number of network variables Non group receive timer value < 50 768 ms (default) 50 – 100 1024 ms > 100 1536 ms     The default value for the AS and AS-P  is 8,092 ms. There is no need to change that value.

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue TC series thermostats which one support Modbus protocol? TC series thermostats which one support time schedules? Environment TC100 (TC103) TC300 (TC303, TC353) TC500 (TC503, TC553) Cause Due to different TC thermostats models support different features, customers need to double check the selection guide to make sure the selected model can support all features which are required. Resolution Click here  to view a matrix which contains all TC series thermostats and their supported features. Additional information can be found on the Buildings Business Extranet website (Products > Field Devices Asia Pacific > Thermostats).

Issue When the EWS interface is created, the Status show "online". However, after clicking on the Hardware > EcoStruxure Web Service > SSLite, the Status will go offline. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause Make sure the SOAP Endpoint field says "ews" and not "EWS". Lua program is a case sensitive program. Resolution Change the SOAP Endpoint field to "ews". For firmware version support in EWS, see Firmware versions to support EcoStruxure Web Services (EWS) in SmartStruxure Lite MPM Controllers.

Issue The Conversion Settings guideline is not documented. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 Cause Lack of information on "Conversion" column in Conversion Settings for B3 and I2 Resolution The Conversion column has the highest priority in the setting. If a formula exists then the setting below will not affect the Value.   Example The ElecValue is set to 10 for the following examples. 1. The Conversion field is empty, the ElecValue = 10 which corresponds to 100 on the Engineering scale. The Input Value = 100. 2. The Conversion field is set to ElecValue, and the ElecValue = 10. The Input Value = 10. 3. The Conversion field is set to ElecValue - 7. The Input Value = 3.  

Issue System tree pane not working in webstation Get failed "Unable to locate path /your/path/../ Either the path is invalid or the location is currently offline" Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause If the root path is changed in a workspace then the issue below occurs. Webstation is trying to locate the system pane in the folder indicated in the Root path. Resolution Go to Server > System > Domains > Your domain > Workspaces Click on the workspace that us used Click on the content tab Change the root path back to ~

Issue Clarity is needed on the new ES License Inheritance feature available in EBO 3.x Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Enterprise Central Building Operation SmartX Server (AS-P, AS-B) Cause The evolving Licensing Model of EBO has offered the option of Embedded Licenses in SmartX Servers, such as SNMP Licenses, since EBO 2.x.  The concept of Inheriting Licenses from an ES into a SmartX Server is a new option which can be used from EBO 3.1 onward, although the original Embedded License option still remains, but what does this actually mean? Resolution In EBO 3.1, SNMP Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   In EBO 3.2 SNMP and TimescaleDB. Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   'Inheritance' means that an ES License will be shared down to its child SmartX Servers while also being retained for use by the ES.   Note: SmartX Servers must be running the minimum supported 3.x version for Inheritance to function There is no such thing as a 'Site License' that can accommodate multiple ES There is no Licenses Inheritance from an EC

Issue Menta Parser Error when attempting to direct download a Menta application. Warning Reference to unsupported I/O Error in COD file - Error:13 (Y=___ X=___) Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The application may contain an I/O terminal that does not exist in the device type to which the application is being downloaded.  This error could also occur in situations where the same I/O terminal reference is used more than once in the application (this could be on the Xenta or the I/O module). Typically caused by copy/paste. Resolution It is possible to have a Menta application that looks to be error free during simulation or the generation of the XIF file, but when the application is downloaded to the controller and it is being parsed by the device it reports a warning about unsupported I/O and leaves the controller without an application. The error window that pops up when trying to perform the download directly from Menta is attempting to show where in the Menta file the error is occurring.  If you can read the point names that are highlighted it can help direct toward the invalid I/O termination.  The other option is to look in Options > I/O configuration and make sure there are no duplicates or invalid I/O terminations.  For example, a 401 doesn't have any onboard I/O so a termination of M0-K1 wouldn't be valid. Note: It is recommended that all macro libraries have non-connected outputs and constant value inputs to force the user to edit these fields.

Issue DC2100 series Optimiser / Compensator Controller requires replacement due to obsolescence. Environment DC2100 series Optimiser / Compensator Controller installed to control Variable Temperature Mixing Valve, Boiler/s, Pumps etc. Cause Obsolescence of DC2100 series Optimiser / Compensator Controller. Resolution OVERVIEW DC2100 series Optimiser / Compensator Controllers are flexible with regard to the number and type of electrical inputs and outputs to which they may be connected, enabling the Controller to be applied to a wide range of control applications.  Of the DC2100 series Optimiser / Compensator Controller models manufactured, the final version was the DC2100H Overview details of the DC2100H Optimiser / Compensator Controller may be viewed here. INSTALLATION AND COMMISSIONING In view of the numerous control applications to which the DC2100 series Optimiser / Compensator Controller may be applied, numerous wiring connection variations will also apply. Please therefore check the number of inputs and outputs connected to the DC2100 series Optimiser / Compensator Controller installed before proceeding, as this will assist in determining the suitability of the possible replacement Controller suggested below. Installation and Commissioning details of the DC2100H series Optimiser / Compensator Controller may be viewed here. POSSIBLE REPLACEMENT  The most common control application to which theDC2100 series Optimiser / Compensator Controller may be applied comprises the following combination of inputs and outputs.  Outside Air Temperature Sensor Inside Air Temperature Sensor Compensated Heating Temperature Sensor Variable Temperature Heating Circuit Valve Actuator Boiler/s (2 maximum) H W S On/Off output (independent) Should such inputs and outputs be confirmed then the DC1100 Optimiser / Compensator may be installed in place of the DC2100 series Optimiser / Compensator Controller. Details of the DC1100 Optimiser / Compensator Controller may be viewed here. Drayton A7xx series Sensors connected to the DC2100 Optimiser / Compensator Controller are compatible with the DC1100 Optimiser / Compensator Controller and may therefore be retained. N.B. It should be noted that where a DC2100 series Optimiser / Compensator Controller is included in an installation of a more complex nature then an alternative solution utilizing different products may need to be considered. In such installations not only will the DC2100 series Optimiser / Compensator Controller need to be replaced but its associated Sensors will also need to be replaced. Resolutions to such installations may best be determined following a review of the control system installed by a member of the local Schneider Electric office.

Issue How many MSTP networks can you connect to an Automation Server (AS or AS-B)? Product Line EcoStruxure Building Operation Environment Version 1.3 and newer MSTP Network on an StruxureWare Building Operation Automation Server (AS or AS-B) BACnet MSTP Devices Cause Require 2 separate MSTP networks, either to use 2 different Baud rates or to speed up the network and split the devices across the 2 ports. Resolution You can create 2 separate MSTP networks under the BACnet interface of an AS-B or AS (version 1.3 or higher), one on Comm A the other Comm B. Each can run at different Baud rates if required. For the number of supported devices please reference, Maximum number using StruxureWare Building Operation (Scalability and Capacity). Please be aware that the listed maximum is for the Automation Server allowing you to distribute between the two comm ports.

Issue TAC Xenta I/O modules do not come online after a download from System Plug-In Rapidly blinking green light on I/O modules show offline status (fast blink) Product Line TAC Vista Environment Xenta 400 series I/O modules Cause No I/O assigned to the module in the Menta file Needs a power cycle after download to associate with the base unit Resolution Verify that at least one hardware input or output is assigned to a terminal on the I/O module. If the I/O module is a spare that has been added for later expansion capabilities, it will never associate with the master or report an online status. If this is the case, assign a "dummy" input to the module temporarily if the rapidly blinking LED is a concern. Sometimes even if all of the correct information is downloaded to the TAC Xenta controller, the green light is still blinking rapidly (not configured) on the TAC Xenta I/O module. If this happens try to power cycle the TAC Xenta controller.

Issue How to setup and use the Plain English Alarm function?   Product Line Andover Continuum   Environment PEAlmFunction, PERtnFunction CyberStation Alarm Workstation PE function Cause Manual configuration is required to create the Plain English alarm function and set certain registry keys.   Resolution As a function of Continuum CyberStation Alarm Engine, user written Plain English functions are automatically invoked at a workstation when an alarm occurs when an alarm is acknowledged when a return-to-normal condition occurs. The user optionally specifies the names of those functions in the Windows registry, and they will be called appropriately. Registry keys used for calling Plain English Alarm function PEAlmFunction : The name of the user-defined PE Alarm Function. (Ex. “AlmProcess”) PERtnfunction : The name of the user-defined PE Return-to-Normal Function. (Ex. ”AlmProcess”) Example of the Plain English Alarm function is as follows: Arg 1 A ' Network AliasName(16) Arg 2 B ' Controller AliasName(16) Arg 3 C ' Infinet Controller AliasName(16) Arg 4 D ' Object name(32) Arg 5 E ' Object AliasName(16) Arg 6 F ' Object Description(32) Arg 7 G ' Object Value(Numeric) Arg 8 H ' Alarm State(3) ALM,RTN,ACK Arg 9 I ' Graphic Object AliasName(16) Arg 10 J ' Alarm Enrollment Alarm Message(String) Arg 11 K ' Alarm Enrollment AliasName(16) Arg 12 L ' EventNotification AliasName(16) Arg 13 M ' EventNotification Priority (Numeric 1~255) Arg 14 N ' TimeStamp(16) Arg 15 O 'Logging Flag (1~255) ' String 1 Q String 80 AlmDir, Fnam File AlmF ' If M < 100 then AlmDir = "C:\" Q = chr(96) Fnam = NumToStr(random(Second)) OpenFile(AlmDir ; Fnam ; ".alm", WriteOnly, AlmF) Print L ;", " ; K ; ", " ; A , B , C , D , ", " ; G to AlmF CloseFile(AlmF) Endif Return Success Create the following registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls \Continuum\Settings: PEAckFunction (REG_SZ) PEAlmFunction (REG_SZ) PERtnFunction (REG_SZ) PEMaxBufferedAlarms (REG_DWORD) PEPopAlarm (REG_DWORD) Set PEAlmFunction to “AlmProcess” Set PERtnFunction to “RtnProcess” Restart Continuum. Create PE programs in the workstation called AlmProcess, and RtnProcess with source code similar to the example function. Files will be created in the specified directory containing the alarm and return to normal information.

Issue Not all commands in Plain English are available in Building Operation Script. Product Line EcoStruxure Building Operation Environment Script editor in Building Operation Cause Conversion of PE to Building Operation script is unsuccessful. Unsupported Script commands. Resolution Plain English may be imported into Building Operation; however, there are some minor edits that must be performed to make it work. Bindings must be applied. There is some automated manipulation of PE to Script upon import and it should continue to improve in future releases. By creating a "dump" file in Continuum and editing the file to remove the Header and Footer areas, the remaining code can be imported into Building Operation as Script. There are some functions Continuum uses that will not be used in Building Operation, the Script will error upon event to save if unsupported code is used in the imported script. Notification of each line of code is in error will occur upon a save attempt. Navigate to the lines in error and correct the code. The following link has information on PE to Script changes. Log in is required to access full online help: StruxureWare Building Operation Online Help

Issue Emailing alarms if Microsoft Outlook is not used on the site? Product Line Andover Continuum Environment Continuum Cyberstation 1.73 and above bCX 4040 Netcontroller II (9680) ACX57xx Series (ACX II) Cause The customers site IT system is unable to provide reliable Email communications from Microsoft Outlook on the Continuum Workstations. Resolution The documented Outlook support: Initially Full Microsoft Outlook or Microsoft Exchange was specified as the requirement 1.92 to 1.94 specified Microsoft Outlook 2007 for Windows XP and Vista (Full Microsoft Outlook or Exchange) 1.94sp1 to 2.03 specified Microsoft Outlook 2007 Microsoft Outlook 2010 (Full Microsoft Outlook or Exchange software package)   For further information on outlook versions see the KB article Outlook 2007 and Outlook 2010 with Continuum email alarms. Notes Only 32bit Outlook was tested/supported Continuum does not support MS Outlook Express for emailing alarms From v2.0 CyberStation has internal SMTP email options see  SMTP Email Alarm Configuration in Continuum 2.00 to 2.03 There are other email option for emailing directly from controllers. There is a feature in the bCX (also NetController II, ACX II) controllers to be able to email messages directly to a SMTP server either manually or via Plain English programs, although this is not directly linked to the Continuum Alarm system and would require a Plain English program to determine what emails are to be sent. See the "bCX1 Controller Technical Reference" Commissioning section for details on how to set up the controller to send out emails to a 3rd party SMTP email server.  There is also the Continuum SNMP Configuration guide for use with SNMP alarming with a Network Management System. Then in the CyberStation online help see the "SendEmail" function help on how to use Plain English to get the bCX (Netcontroller II or ACX II) to send out messages via email.  

Issue Is there any way I can transfer a value between 2 LUA programs without using a BV or AV? Example: A Lua program (PG1) is created to turn on lighting, a variable called LightOn is created but other Lua programs PG2, PG3, PG4 cannot reference the "LightOn" variable. Is there any way a variable from one Lua program can be accessed from another Lua program? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Lua programming Cause Each PG script has its own dedicated environment, which basically means variable names cannot be shared between scripts. The only things that can be referenced are actual objects (AV, BV, etc.) Resolution An AV or BV object will need to be created within the EcoStruxure Building Expert controller to store the value and make it available for other programs to read. For example a BV1 could be created and read from or written to by multiple Lua programs by referencing ME.BV1 For more information, please reference the EcoStruxure Building Expert Software - User Interface Guide document on the Exchange.