Building Automation Knowledge Base

Issue Running reports on Extended Logs shows no data Environment Continuum system Cause Possible Causes: Other programs currently running extended logging (pre-1.7x style). Time sync errors Cyberstation preference is set to false Resolution Check that you do not have programs running that are performing extended logging the pre-1.7x style. Any programs that were used for extended logging should be disabled or removed. Check the Continuum Error Log listview and see if there are time sync errors. A difference of more than 5 minutes between the Master controller and the Cyberstation will stop extended logging from working properly. You will see an error indicating that the time difference has been exceeded. Ensure the Cyberstation preference is set to True Download Extended Log Data from Controllers on the LAN(RAS) If it was set to false, Stop/Restart Continuum Run List views of all points, (inputs, outputs, numerics) Example: In Explorer, Go to ListView> Listview_Infinity Inputs > Edit Click Columns> Add a Column Add ExtLogEnable Check Off Edit box Click Apply then the General Tab Run the listview Select Edit> Select All Select Object> Set Attributes Select ExtLogEnable, For Value type in True and Click OK, OK Select View> Refresh list and the attributes are set to true Repeat this for Outputs and Numerics Wait for awhile beyond how often you are logging your points. Run reports to verify data is being logged. NOTE: Occasionally, after an upgrade, you may need to set all the extended log enable attributes to FALSE FIRST and then to true again for inputs, outputs and numerics to get them working. Data may have been logging and then stopped. The data range requested in the report doesn’t have data, but there is data in the database. Here are some tips on verifying the data in the database. Using Enterprise Manager Use Query Analyzer against the Continuumdb Select * from extendedlog Using OSQL Go to a command prompt Enter in osql –Uandover97 –Ppyramid97 –S then enter (this assumes default user and pw, change if needed. –S needs to be followed by your server name Once you hit enter you’ll be brought to the 1> prompt At the 1> Prompt hit the Enter key 1> select * from ExtendedLog Type Go the Enter If values are returned, then extended logging is working. Type quit (to exit OSQL) Type Exit to close the DOS window

Issue LDF file of a database is growing rapidly. SQL Database Recovery Modes Explained Product Line Andover Continuum Environment Continuum  SQL Server Cause Recovery Mode setting could allow all transactions to be logged. Resolution The Full Recovery Mode basically logs all transactions successfully, failed, table creations, columns created etc... When the Continuum database is created, there are no additional tables added or columns added unless there is an update to the database to a different version. Some sites will require Full Recovery Mode but for most sites, we only need to know when an error occurs when updating or altering rows occurs and Simple Recovery Mode will log those. The Continuum Databases are created with Simple Recovery Mode. It is up to the individual site whether they need Full Recovery Mode. Most sites run with the default Simple Recovery Mode since there is no need to log every successful transaction but only want to catch the transactions that have an error. The Recovery Mode is especially important if your site is a single-user setup. Single user databases are limited in size and if you fill-up the .LDF log file, you can exceed Microsoft's database limitations in a short period of time. As for Enterprise versions of SQL for Continuum Lan systems, you'll need to watch your available disk space. Check what the Recovery Mode is set to by using SQL Server Management Studio Express, right-click your ContinuumDB and select properties, go to the Options tab, and check the Recovery model. See the image below for details.   Furthermore, if you have selected Full Recovery Mode in the past and now have a large unwanted .Ldf file that is causing you issues, then selecting Simple Recovery Mode at this point will also truncate your original Log file down to a more usable size retrospectively.  (Although it may take a few hours before you see any changes).

Issue Microsoft Database size Limitations and Continuum Product Line Andover Continuum Environment Continuum Site Cause There are limitations to the size that a Continuum database can be. The limitations are Microsoft's limitations. Basically if you use their limited sized databases, these are good for smaller sites. Most of these smaller sites usually don't have extended logs or a heavy volume of access and alarm events either. Resolution Microsoft Database size Limitations and Continuum On large scale sites that have a lot of extended logging, heavy access traffic, alarms and do not want to monitor the size of the databases, it is suggested to go with a enterprise SQLversion. Microsoft DB Size Limitations MSDE version (SQL 2000) 2 Gig Limit - See Database size limitation and recover options on a Single User system in Continuum for more information (Cyberstation SU versions 1.81 and earlier). Enterprise version (SQL 2000) No Limit SQL 2005 Express 4 Gig Limit  (Cyberstation SU versions 1.82 to 1.94) SQL 2012 Express 10Gig limit  (Cyberstation SU version 2.0) Exchange Server 2003 before SP2 SQL 2005 Standard Edition 18 Gig Limit SQL 2005 Enterprise Edition 8 Terabyte Limit Server 2003 SQL 2005 Enterprise Edition 8 Terabyte Limit Research your operating system and determine the size limitations for your particular installation. There are other limitations when using limited versions of the SQL Databases like Standard addition. For instance limited number of processors, limited amount of memory used for allocation pool. Note: Do not use 2 database applications on a Stand Alone installation with Cyberstation being one of the applications. 2 SQL versions or 2 database instances has not been tested with a Stand Alone and is unsupported. This scenario can cause Cyberstation performance issues as well as application crashes.  

Issue Getting error message in Vista that Menta is in 'stand alone' mode and cannot edit the .MTA Environment Vista Menta Cause This happens usually when Menta has previously been installed on the system in a "stand alone" fashion and then Vista was installed at a later time. Resolution Go to Start > Run and type "regedit" to open the Registry Editor Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > TAC > TAC Menta Double click the key named StandAlone. Change the value data to "No"   For a 64 bit OS, the path in the Registry Editor is HKEY_LOCAL_MACHINE>SOFTWARE>Wow6432Node>TAC Menta

Issue Cross Reference of Obsolete Field Devices to Current Schneider Electric Field Devices. Environment Field device replacement Cause Unknown replacement for obsolete field device part number Resolution There is an Online Cross Reference Guide located on our Schneider Electric Buildings Website. Enter the old part number into the field for part to cross reference & click on the search button not the ENTER key. The ENTER Key clears the part number entry. The Manufacturer's name is not required for a product search. Contact Product Support when no cross reference is found for additional help.

Issue LDVD: Socket receive error (Error#:53526) in a Xenta 5/7/9xx Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause This error is displayed every time the LON communication is closed down. Resolution This message does not necessarily mean that something is wrong. Check LON communication to make sure there are no other symptoms. This is very minor and common unless it occurs at a high frequency.

Issue Commission and download command on a controller beneath a Xenta Server in a Vista classic network fails. Error: Completion event-failure, Info: $Address Product Line TAC Vista Environment Vista Workstation Vista classic network Xenta Server Cause This error does not indicate an error with the addressing of the controller.  What it refers to is the reading of parameters from the controller in an attempt to commission and download.  The first parameter it tries to read is the address, and if that fails, the $Address indicates which portion it failed on.  Since $Address is first, this indicates a complete lack of communication with the controller. If this issue occurs with a freely programmable controller (Xenta 280/300/401) under a Xenta Server (Xenta 5/7/913) it may be due to the Xenta Server firmware version not matching the Vista Server version. Resolution Go to the controller and look at it.  The green LED on the front should be solid green. Physically inspect the wiring of the controller.  A shorted LON, for example, would cause this error.  Make sure all wires are terminated firmly. For DDCs under Xenta Servers: Please refer to Xenta Server firmware versus Vista Server versions for the Xenta Server compatibility matrix with Vista Server. If a Xenta Server's firmware version does not match the Vista Server version then either uninstall Vista Server and reinstall the correct version of Vista Server or reload the correct firmware version to the Xenta Server.

Issue How to install and use I/NET with SQL located on a separate PC Environment I/NET 2.40 and above Full SQL Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause The SQL database may be located on a separate server for IT, security, or backup requirements. Resolution Please see attached "RemoteServerandRCwithIO" Install full SQL on a PC and take a note of the IP address. Make sure the following criteria are met: The server must be on the Ethernet. Provide SQL services. Allow authorized clients to connect, and have an I/NET database. Setup I/NET on the Host PC as a Remote client and redirect it to the PC with SQL installed, IO server must be running on 1 of the remote clients (This Client will be in charge of updating AMT, Trends, Network Functions)

Issue When binding Output points in the script editor to the desired outputs, the bindings are not working. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation All Versions Automation Server Central I/O Modules Cause When bindings to the output points the incorrect attribute is being used. Resolution Open binding editor for the desired program. In the right hand pane, choose the desired output to be bound. Expand the point and select Requested Value. Drag the Requested Value to the desired output in the program. Save settings.

Issue Failure when upreving a Controller to a new flash version. Error window pops up with the error message "This Uprev file does not match this type of controller.". SmartStruxure "Update Failure No b3 controller matches to update" Environment Continuum Controllers b3 Cause The Controller Model has been entered incorrectly or you are trying to load the wrong flash file into the controller, e.g., the Controller Model in the Device object has been incorrectly set to i2810 when the controller is actually an i2814. Resolution Confirm that the correct flash file for your controller model and the Controller Model field both conform to the actual model type of your Controller. In offline editing check that the database also contains the correct model type. For b3s (Notice the 4th digit) The 4.501064 firmware is for the –Vs The B3865B4.500076 is for the non –V

Issue Cannot open Calendars on several BACnet Networks. Product Line Andover Continuum Environment Continuum 1.9X BCX 4040 B38XX controllers Cause BBMD Sub Net Mask Configuration. Resolution There are two configuration methods allowed in a BBMD Subnet mask. One hop configuration and a Two hop configuration. See Understanding BACnet BBMD Distribution Mask for further details

Issue Connection lines will not connect to some objects on the drawing, but will on other objects. The "Snap and Glue" feature was verified per Connecting lines in WorkPlace Tech stay red even when snapped to an object. Product Line TAC IA Series Environment WorkPlace Tech 5.x Windows XP SP3 Visio 2003 Visio 2007 Cause Objects are on the "back" layer. Resolution Select objects or complete drawing Right click Select Shape > "Bring to Front"

Issue Continuum will not start.  "Continuum is running please wait and try again" Environment Continuum 1.92. Windows 2008 Server. Cause Domain Policies are in place. They are restricting active X and registry changes. Resolution Remove the Computer from the domain. Install Continuum Rejoin the Domain.

Issue  Where do I find our BACnet controllers BACnet PICS? (Protocol Implementation Conformance Statement) Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment All BACnet controllers Cause Alternative locations to find BACnet PICS for our controllers. Resolution PICS documentation can be found on The Exchange Download Center and BACnet International website.

Issue In newer versions of XBuilder, when importing I/NET sav files into the project, an attribute called "flags" is included.  In an I2V integration, this signal can be used to decode the binary flags associated with an I/NET point. Product Line TAC INET, TAC Vista Environment XBuilder 5.1.5 and later Cause In earlier versions of XBuilder, each binary flag was separated out into an individual signal.  These signals include: test manual alarm old unack alarm_ack Binding each of these values (along with value, state, and/or control) for every point displayed on a graphic could quickly cause the number of bindings to expand to a number that caused performance issues with TGML graphics.  To combat this, all of the binary flags were combined into one signal called "flags." Resolution The masking for the flags signal comes from the communications format of I/NET: 7 6 5 4 3 2 1 0 Test Alarm Alm Inh Unack Old Manual Not Used To use these in a TGML graphic, read in the flags signal to a component attribute.  Then read the value and mask off the necessary bits: test = ((flags & 128) == 128); alarm = ((flags & 64) == 64); unack = ((flags &16) == 16); old = ((flags & 😎 == 8); manual = ((flags & 4) == 4); Test, Old, and Manual can be used to append the point value with a T, O, or M, respectively to emulate an I/NET environment.  Logic will need to be written to read in the alarm and unack signals: alarm unack inhibit result false false   No alarm condition true false false Alarm is still active, but has been acknowledged true false true Input active, but no alarm condition false true   Alarm has cleared, was never acknowledged true true   Unacknowledged alarm present

Issue BAS terminal receives system messages from a PIU with no explanation and is asked to contact Product Support. For example "Message No. 19920 not available. Please contact Product Support" Product Line Other, Satchwell Sigma Environment BAS PIU  and Sigma Pre-release 4 System Messages BAS (1 - 10499) SNP Gateway ( 10500-10999 ) CHUBB Remote Access Management ( 11000-11499 ) CEGELEC ( 11500-11999 ) OTIS   ( 12000-12499 ) CCURE ( 12500-12999 ) WORMALD ( 13000-13499 ) ASIC ( 13500-14999 ) SIMPLEX ( 14000-14499 ) CARRIER DATAPORT  ( 14500-14499 ) EXPRESS LIFT ( 15000-15499 ) CARDKEY ( 15500-15999 ) Mitsubishi ( 16000-16499 ) Liebert ( 16500-16999 ) IMPACC ( 17000-17499 ) YORK ( 18000-18499 ) AUTOFLAME (19000 - 19100) AUTOMETERS (19100-19199) MITSUBISHI PLC (19200 - 19299) SIEBE MICRONET (19400 - 19499) CROWCON (19500 - 19599) MNI (MicroNet Interface) ( 19700-19799 ) Colt OPV ( 19800-19899 ) MODBUS ( 19900-19999 ) MCQUAY (20000 - 20199) FIDELIO (20200 - 20299) ATLAS COPCO ( 20301-20399 ) UNIFACT PRO ( 20500-20599 ) Cause Due to a size limit (64Kb) not all the PIU error messages are included in the Messages.ini file. Resolution A more complete list of the of BAS error messages can be found here. Copy the appropriate section Paste into the C:\Bas\Data\Messages.ini file into the correct sequence as by message number The maximum size of the message.ini file must not exceed 64Kb Example:

Issue A Xenta 5/7/9xx controller can either be implemented as A Xenta Server, where it doubles as the LonTalk adapter and a Xenta device A LON node, where it is a part of an LNS database below a different LonTalk adapter If the Xenta is a LON node, then it will be represented as a LON device in the network, but also utilizes Xenta Group Bindings to communicate to Xenta programmable controllers (280/300/401). If graphic pages in certain Xenta units aren't displaying data, or connection objects aren't passing data as expected, the online status of the Xenta units should be checked not from the Vista Server, but from inside the Xenta 5/7/9xx. This issue will display red x's on the graphics page. Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721, 731, 913 LNS Database Cause A Xenta 5/7/9xx LON node pulls "double duty" as both a LON device and a Xenta Lacnet device. It requires one Xenta Group Binding on message tag 0 to facilitate communication with Xenta programmable controllers. Resolution Log into the web interface for the 5/7/9xx. Navigate to Utilities > LacNet > LacNet List Xenta.  "LacNet" refers to proprietary Xenta communication. View the online status of each Xenta programmable controller in the network.  It is displayed as below: =============================================== Node: RTU7 Xenta group: XG_RTUS  GroupMaster:No FTP state alarmstack, app:finished OnOff:N/A Latest FTP : 05/13/2011 11:25:59 State: online (since 05/13/2011 11:23:05) Xenta???  Software version: 3.84-01 NID: 04:6B:84:9F:01:00  Subnet/Node:  253/122 Module: SUMMARY Module: CALIBRATE Module: CONFIGURE Module: ALARMS Module: SETPOINTS Module: ERRORS Module: $LOG Module: $SYSTEM Module: $SYS Number of alarm objects: 25 Number of public signals: 7 Number of handles allocated: 8, where 1 is with notification ===============================================

Issue See Check Xenta programmable online status from a Xenta 5/7/9xx LON node to determine if the Xenta 5/7/9xx controller is communicating with Xenta programmable controllers on the network. If it's not, graphic pages in certain Xenta units won't display data, or connection objects won't pass data as expected, etc. Product Line TAC Vista Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 LNS Database XBuilder Cause A Xenta 5/7/9xx LON node pulls "double duty" as both a LON device and a Xenta device. It requires one Xenta Group Binding on message tag 0 to facilitate communication with Xenta programmable controllers. Resolution Check LacNet status (see Check Xenta programmable online status from a Xenta 5/7/9xx LON node).  If controllers are showing an offline status, proceed with the following steps. In LonMaker, right-click on the device and go to Properties. View the address table. The Xenta 5/7/9xx controller's address table should have the first entry (message tag 0) populated with an index that matches all the Xenta programmable controllers on the network (see Verifying Xenta Group Bindings in an LNS system for more information about checking address table group bindings). If the group binding for LacNet communication doesn't exist or is wrong, redo group bindings. Ensure the Xenta group masters of the network have not been manually removed from the network pane of the XBuilder project. Download the XBuilder project to the device. Recommission the device in LonMaker. If it is still not communicating, download each of the Xenta units that it is trying to communicate with and recommission them in LonMaker.

Issue Require details on how to setup multiple inputs to popup the same camera window if any of them are true. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Unsure how to setup program for multiple inputs to display video from one camera when any of them are set to true Resolution 1. Under Events | Event Filters create a new Event filter 2. On the Event Types tab untick "Include All Event types" and select the Add button  3. Browse for "All Input Events", select "Input <ZONE_NAME> Opened" and click OK 4. On the Records tab select the Add button, select Device Type "Input" and your Controller, then the inputs that you want to popup this video 5. Save the Event Filter 6. Under Events | Actions create a new Action 7. Select the Type "Popup Camera Window", select the Event Filter you created in step 1, select the camera you want 8. Save the changes and test the scenario.

Issue What BACnet services and BACnet object types are supported in the AS and ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Automation Server StruxureWare Building Operation Enterprise Server BACnet IP BACnet MSTP Cause PIC statement for supported services and object types in StruxureWare Building Operation. Resolution Page 5 of the AS BACnet PIC shows the columns of the different types of BACnet devices. Whether it is a B-OWS or a B-BC etc… the x's in the columns show the required services for each particular device according to the BACnet Standard. The last green column in the PIC, show the Product Conformance (AS) and what services the AS supports. For instance COV is not a required service, but a optional one and is selected in the last column. Below are links to the AS and ES BACnet PIC. AS PIC statement link ES PIC statement link