Building Automation Knowledge Base

Issue A Niagara G3 server station was running well for a long time.  Then in a matter of a couple of days, the station began failing to run.  The error listed in the Application Director Output is:   ERROR [java.lang.OutOfMemoryError: GC overhead limit exceeded 13:46:17 20-Mar-14 EDTjava.lang.OutOfMemoryError: GC overhead limit exceeded][sys.leasejava.lang.OutOfMemoryError: GC overhead limit exceeded] Error in run Product Line TAC IA Series Environment I/A Series G3 Enterprise Server Cause There is not enough memory allocated to the Java Virtual Machine (JVM). The email service is keeping a very large outbox because the network email server's IP address was changed. Resolution Increase the Java Virtual Machine (JVM) memory allocation Using a text editor, open the nre.properties file (located in the niagara 'lib' subfolder on the server hard drive). Locate the line: java.options=-Xmx256M. Change it to java.options=-Xmx512M. Empty the outbox file (i.e. delete it) and/or update the email server's IP address.

Issue This is a short guide to show the correct use of output blocks with forced values in Function Block programs Environment SmartStruxure AS using Function Block programs Cause There is a design difference between the Vista Menta function block programming and the new version for SmartStruxure. In the old Menta programs it is possible to connect the output from an output block and connect it to an expression block. The forced value from the output block was passed to an expression block connected downstream of the output block. This is NOT supported in SmartStruxure at the current release Ver 1.3 (April 2013) If this is done in SmartStruxure then should the output block be forced in any way the forced signal is ignored by the downstream block Resolution Follow the guidelines as detailed in the attached document.

Issue A McQuay MicroTech 2000 water source heat pump controller may be addressed as a Level 3 device under an MCG (MicroTech Communications Gateway). This can be confusing when addressing WSHP1 blocks in a SIM-MTECH. Environment Network 8000 SIM-MTECH McQuay  MCG (MicroTech Communications Gateway) McQuay MicroTech 2000 water source heat pump controllers Cause The MCG needs to use an Echelon communications protocol with the water source heat pump  (WSHP)controllers, which uses level 2 internally, and puts the WSHP controllers at LEVEL 3 Resolution The way to address the WSHP blocks under the MCG is HBYTE = 1, LBYTE = x, where x is the address of the controller.  Unlike earlier McQuay controllers where the unit address is set by rotary hexadecimal switches, the addresses of the MicroTech 2000 heat pump controllers are set in software by the McQuay  technician who commissions their network. Click here to see an excerpt from F-26133, Systems Integration Module- MicroTech, SIM-MTECH. See Fig 2.1, and Table 2.1, pp 2-2 through 2-4

Issue ALARM blocks can be added to an SBO Function Block application, but it is not possible to set delay, priority or alarm text parameters from within the Function Block Editor.  Also, the preceding block is assigned an auto-generated name and public status, if it did not already have a name. Environment SBO 1.5.0 and earlier. Function Block Editor Cause When an alarm block is added to a Function Block program an alarm object is automatically created in the SBO System Tree, below the FB program object.  By default, the alarm object is not visible until the filter 'Show non-presentation objects' is set The public block preceding the alarm block is required so that the alarm object in the System Tree can have a Monitored Variable reference.  The 'Function Block Editor and Menta Editor Difference Guide 04-15010-01' states that 'The function block programs still need the ALARM blocks, but the blocks only serve as inputs and outputs to the alarm functions..'.  This is misleading as you do not need to explicitly create an external alarm object - all the usual alarm properties are available in the automatically generated alarm object, once it is made visible. Resolution Set the System Tree filter to 'Show non-presentation objects'.  Then set the required alarm properties in the displayed alarm object below the FB program object.

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 

Issue The Wonderware Temporary License is out of date. How can a new one be obtained? Environment WonderWare Cause Since Schneider Electric (Rockford) is no longer a Wonderware OEM software distributor, demo licenses can no longer be provided. Resolution The 30-day temporary Wonderware demo mode license is available to the Wonderware SI selling the Wonderware software.

Issue A TAC Xenta programmable controller has issues, and more information is needed to analyze what is happening in the controller. Product Line EcoStruxure Building Operation Environment TAC Xenta 280 TAC Xenta 300 TAC Xenta 401 XentaErrorLogViewer Cause The TAC Xenta 280, 300 and 401 series has an internal Error Log, that in some cases could give more information about the way the device is acting, storing restart reasons etc. Resolution The XentaSystemErrorLogViewer is used to read out the internal error log file from a TAC Xenta 280, 300 or 401 device. The XentaSystemErrorLogViewer is a program that runs in your PC, and you have to connect to the TAC Xenta device by the use of a serial cable. You must have at least the same version number of the XentaErrorLogViewer as the device you want to read the information from. Please note that the XentaSystemErrorLogViewer program only works with released version of the TAC Xenta 280, 300 or 401 devices. 1. Download XentaSystemErrorLogViewer 2. Install the program 3. Connect the TAC Xenta to the PC using the TAC Xenta programming cable. Refer to the cable guide for further information. 4. In "Preferences", select the COM port to which you connected the serial cable 5. Check "Write System Error Log to file" 6. Click "Get new information" 7. The information is written to "C:\Windows\Temp\XentaSystemErrorLogg.txt"

Issue Video of DigitalSentry system can't be seen in I/NET. Alarm of Endura system, for example Motion Detection or Video Server Offline can't be shown in AMT. Product Line Pelco, TAC INET Environment I/NET 2.41 Cause The possible cause is that when installing SarixSDK of I/NET 2.41, there will be an error: Error 1904. Module C:\Program Files\Pelco\Common Files\IntegralPelco4600 dll fail to register. HRESULT-2147220473. Resolution The possible resolution is to uninstall the SarixSDK, delete the Pelco folder in Program Files folder and reinstall the SarixSDK. The error should disappear during the installation. And then video and alarm should be able to appear in I/NET. For more issue about video that can't be seen in I/NET, refer to Video in Endura/Digital Sentry System Can't be Shown in I/NET.

Issue Enterprise Network Server BTL Certification Environment I/A Series G3 3.6.35 BACnet Advanced Operator Workstation (B-AWS) I/A Series G3 3.6.35 BACnet Operator Workstation (B-OWS) Cause The PIC statements for the I/A Series G3 Enterprise Network Server for BACnet Advanced Operator Workstation and BACnet Operator Workstation is available from Schneider Electric. However, they are not listed on the BTL website under Schneider Electric.  Resolution Schneider Electric is focused on maintaining BTL listings for servers and controllers that are an active part of the SmartStruxure solution. There are no plans to add or renew BTL listings for products that are only supported by TAC I/A Series systems at this time. Existing listings that don't apply to SmartStruxure solution will remain on the BTL website until they expire. Schneider Electric product BTL listing can be found here.

Issue Error when commissioning a Xenta 5/7/9xx indicates an out-dated or mismatched XIF (device template). Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) on a Xenta 5/7/9xx LON device   If this error occurs on any other device besides a Xenta 5/7/9xx, please reference Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) for resolution. Product Line TAC Vista Environment LonMaker 3.X Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Cause The Program ID inside the controller does not match the Program ID specified for that controller inside the LNS environment resulting in a Program ID mismatch. Program IDs are unique identifiers created for use in device templates and are based on the XIF. Resolution Resolve the Program ID mismatch by making the Program ID in the controller match that in the LNS environment. Download the controller using XBuilder. Send project to target. Generate the latest XIF for the XBuilder project. In the Network Pane, right-click on the root (TAC_Xenta_511 in this example) Select Generate XIF File   Find the new XIF that has been generated in the XBuilder Project directory: targetimage\configdb\lon\TAC_Xenta_511.xif Default XBuilder locations XBuilder 5.1.3 and prior: C:\Documents and Settings\All Users\Application Data\TAC\TAC XBuilder Projects XBuilder 5.1.4 and later: C:\Documents and Settings\All Users\Application Data\Schneider Electric\TAC XBuilder Projects Windows 7: C:\ProgramData\Schneider Electric\TAC XBuilder Projects A good practice is to view details of the folder to confirm the time stamp of the XIF file. It should match the time that the file was generated in XBuilder. This file will be selected later, so another good practice is to rename the file to something more meaningful -- the name does not matter. "WebServer.xif" may be easier to find later and confirm it is the correct file. It is also perfectly acceptable to move this file to a new location -- Device Files of your overall project, for example. That can also help in later steps, especially if the default XBuilder Project location is used. In LonMaker, right-click on the device, and choose "Replace" (Not in System Plug-In)   Browse to the newly generated XIF file. Give the new device template a name. Select Finish. Commission the Xenta 5/7/9xx into the network. The Program IDs now match and the error is cleared.

Issue How to create a LNS database in NL220 and then bring it to Vista Workstation online Product Line TAC Vista Environment NL220 Cause In order to have a healthy LNS database, it is very important to create this database with proper steps in NL220. Resolution Preparation: Configure the Infrastructure Device Set up Vista Database path   Creating LNS Db in NL220 NL220: Add infrastructure device, nodes, etc. System plug-in: Assign Neuron ID (Optional), Menta file Back to NL220: SNVT binding   Bring LNS Db to Vista Db System plug-in: Network settings, Update TAC Network, create group bindings, add I/O modules, update the TAC Network again, check TAC Network, Update Vista Database   Bring Vista Db online NL220: Commission the Infrastructure Device System plug-in: Verify network settings, assign Neuron ID if needed, update TAC network and Vista database, download application and parameters Back to NL220: Commission and downloading all nodes besides I/O modules. Back to system plug-in: Change infrastructure setting, commence communication

Issue What is required to control command priorities in 3rd party controllers using Plain English? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Controller (BCX, B4920, B3) BACnet command priority Plain English Cause Need to understand how to control command priorities and point values with Continuum workstation programs or controller infinity programs. Resolution Command Priority is a BACnet mechanism to decide the control hierarchy of a point, with 1 being the highest priority and 16 being the lowest.  Consider the following:   Default setting for a workstation program priority level is ManualOperator priority 8 Programs located in the workstation default command priorities can be controlled through Bacnet Preferences Controller InfinityPrograms will need to use the WriteProperty function to set a different priority other than priority 10 To relinquish a priority level use Relinquish(pointname, priority level)   The WriteProperty function is written in the format: WriteProperty (object_name, value, priority, index) object_name  Includes a full pathname, followed by a property name. The object identifier and property identifier are combined as one argument value   This actual value to which the property is set. This is optional.  If it is not present, then the next argument, priority, must be present to perform a Relinquish command.  (See the example in Relinquish.)  priority  The priority  number, ranging from 1 (highest) to 16 (lowest).This is optional.  It applies only to a set commandable property.  For controllers:  If it is not present, priority 10, if applicable, is used.  For CyberStation: The value, based on the priority in the BACnet Preferences dialog, is used.  index  This is optional.  It applies only to an array-type BACnet property.  The index is ignored whenever it is not applicable.   Infinity controller samples: This line will write the value of 22 to priority 10 BACnetDevices\BNet_4444\B3_885\B3Num1 = 22 This line will write the value of 33 to priority level 4 WriteProperty(BACnetDevices\BNet_4444\B3_885\B3Num1, 33 , 4 ) This line will relinquish the value for priority level 4 setting the value back to NULL Relinquish(BACnetDevices\BNet_4444\B3_885\B3Num1 , 4 )

Issue While PSS does not write PE for partners we do in some instances provide sample PE code for guidance. This article provides sample PE code for optimized Start/Stop routines. Environment CyberStation All CXs All b3s All i2s Cause Complex PE routines may be difficult to implement without sample. Resolution See Self-adaptive Optimized Start and Optimized Stop Routines Sample PE Code.pdf

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 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 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.