Building Automation Knowledge Base

Issue When Continuum Explorer is launched it takes a very long time to update.  Product Line Andover Continuum Environment CyberStation WebClient Continuum Explorer Cause When Continuum Explorer is launched it must populate all objects that reside at the root.  When there are a very large number of Personnel objects or other object types in the root, Continuum Explorer will be slow or unresponsive until this population process is complete. Resolution Create a Folder under the Root of Continuum Explorer and move personnel objects to this folder. Consider doing this to other objects that exist in large numbers.

Issue Script programs in b3 controllers will not autostart after reboot of the controller Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation AS-B Cause The program is not configured to autostart in StruxureWare Building Operation. Resolution In the Properties of the program object, ensure that the Autostart field is set to True. For further information on these properties please refer to Webhelp

Issue What is the best method for calibrating a thermistor? Product Line Andover Continuum Environment All CX controller All i2 devices All b3 devices Input Temperature sensors Thermistors Cause There is no documentation that details how to calibrate a Continuum sensor. Resolution There is no requirement to calibrate a Continuum Thermistor sensor, Thermistors are factory trimmed to provide an accurate temperature / resistance curve to within the tolerances defined in the datasheet. One exception to this could be if the connecting cable was of excessive length to add additional impedance to the circuit, in this situation the input point conversion line could be used to subtract an offset: Enter "ElecValue - x" where x is a factor to compensate for the cable impedance. See How to add an offset to a sensor reading for further information

Issue HID PIN Pad reader for I/NET Part NumberHID PIN Pad reader for I/NET Part Number Product Line TAC INET Environment I/NET Access Control Cause HID PIN Pad reader for I/NET and which part number to use? Resolution iPortal shows several PIN pad readers from HID (HID-6136CKD000214 HID-6136CKD000009) but only one works with I/NET.  Here is a pdf document which helps to explain which part number works with I/NET. The 09 means the 8 bit blast which is required for compatibility.  Want to use Pin Pad only without using the proxcard? The RK40  will do Prox only or Prox + Pin but not Pin only. See Essex Pin Pad Reader programming for Pin Only or for higher security Pin Only see Code-Guard Scramble Pin Pad Reader Programming.

Issue What voltage should be seen across conductors on an Infinet bus? Environment Infinet RS-485 Cause Communication issues on RS-485 bus. Resolution  Measuring Ground Potential Signal Potential refers to the horizontal plane along which signals are sent and received with respect to ground.  RS-485 requires that all devices communicating with each other be at a reasonable ground potential. Measuring the ground potential of any Infinet controller Use a voltmeter to measure between the earth ground connection (for power) and the Infinet shield connection.   Measuring the ground difference between the Infinet controller and the ground at the InfiLink or CX/NetController (shield grounding point). Set the multi meter to measure AC voltage; measure and record the AC voltage (ACV) between + and -. A reading higher than 2-3 volts indicates a grounding problem. Set the multi meter to measure DC voltage; measure and record the DC voltage (DCV) between +and -. A reading higher than 2 to 3V on either voltage indicates a grounding problem. Calculate the combined voltage using the following formula. (1.4 X ACV) + DCV = Combined Voltage. If the combined voltage is greater than 7 a grounding problem exists

Issue Attempting to start I/A Series G3 Workbench generates the following error: Exception in thread "main" java.lang.NoClassDefFoundError: com/tridium/sys/Nre Caused by: java.lang.ClassNotFoundException: com.tridium.sys.Nre         at java.net.URLClassLoader$1.run(Unknown Source)         at java.security.AccessController.doPrivileged(Native Method)         at java.net.URLClassLoader.findClass(Unknown Source)         at java.lang.ClassLoader.loadClass(Unknown Source)         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)         at java.lang.ClassLoader.loadClass(Unknown Source)         at java.lang.ClassLoader.loadClassInternal(Unknown Source) Environment I/A Series G3 Workbench (all versions) Cause The software is unable to locate class files provided within the baja.jar file.  The baja.jar is missing from the Niagara G3 module folder. Resolution Re-install Niagara and verify the path for installation is correct.  If this does not correct the issue, manually copy all files from the I/A Series G3 installation CD module folder into the appropriate modules folder on the target computer.

Issue Can a UNC be setup as a BACnet server to expose its native Niagara objects as BACnet objects? Product Line TAC IA Series Environment Niagara R2 UNC-520 Cause By default, the UNC can only act as a BACnet client, not as a BACnet Server. A UNC-520 can be configured as a BACnet Server. Resolution Steps for configuring exposing native Niagara objects and BACnet objects: Open the properties of the native Niagara object you want to expose as a BACnet object. Click on its Config tab The foreignAddress must be changed from its default of “-1” to an integer from 0 - 4194302. (BACnet instance number rules applies) Apply the change The object is now exposed as a BACnet object. The following standard Niagara objects can be exposed and BACnet objects: AnalogInput (AI) AnalogOutput (AO) BinaryInput (BI) BinaryOutput (BO) MultistateInput (MSI) MultistateOutput (MSO) Calendar Schedule Reference Chapter 4 of the "BACnet Integration Reference" guide for more detailed information.

Issue The alarm handling between TAC Vista and Xenta 913, 5XX, 7XX acting as Xenta Servers stop after 50 days Vista will stop to receive events from Xenta 913, 5XX, 7XX acting as Xenta Servers after 50 days Environment TAC Vista Xenta 511 Xenta 527 Xenta 555 Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Cause The reason for this issue is that TAC Vista sets a time reference to the computer’s internal tick count just before it’s about to rollover (which will happen every 49.7 days).   Resolution This issue has been fixed in TAC Vista 5.1.7 and a hotfix for TAC Vista 5.0.3 is also available upon request from Product Support Services.   Note: Restarting the Vista Server or the PC will also solve the problem, but only temporarily.

Issue In Niagara G3, how can an ENC be diagnosed as overloaded? Environment Niagara G3 ENC-410 Niagara G3 ENC-520 Jace-6 Cause Programming guidelines needed to prevent overloading the ENC. Resolution The CPU usage should be less than 80% on a continuous basis. The heap.used should be less than 75% of the heap.max value.  Java heap is comprised of station objects operating under runtime conditions.  Objects are created as needed and destroyed via garbage collection (GC) when no longer needed.  Garbage collection is a mechanism provided by the Java Virtual Machine (JVM) to reclaim heap space from objects eligible for collection.  An object becomes eligible for garbage collection if its not reachable from any live threads or any static references (e.g. all references are null). A heap ratio (heap used to heap max) that exceeds 75% causes the JVM to allocate additional time to perform garbage collection and cleanup.  This in turn begins to increase CPU usage which slows down overall station processing and performance.  Eventually, a station watchdog can occur if the processing becomes too slow rebooting the unit due to a watchdog timeout. Note: Make sure to execute or manually trigger a garbage collection prior to evaluating the heap.max value. Using Workbench, right-click on the connected station and select Spy from the drop down menu.  Select util and gc to execute the garbage collection. Methods to decrease heap used: Removing objects from the station logic that may not be required. Reviewing custom objects or programs that may be memory hogs. Use of a controller with additional maximum heap.  The max heap of a ENC-410 or ENC-520 (non-extended memory 128 MB RAM version) is 48 MB.  The extended memory ENC-410 and ENC-520 versions increase the RAM to 256 MB and the maximum heap to 96 MB. The JACE-6E can be purchased with the extended memory option to increase the heap to 96 MB. Add another ENC or JACE controller. Histories can also affect the heap.used value. When the station needs to write a record to a history, it opens the specific history into the running station from the file system if PC based or the ram disk if QNX-based.  The open history does contribute to the heap.used of the station.  Remove unnecessary or unused histories by disabling the history within the extension, removing the associated history file, and removing the history extension.

Issue Version of I/NET software and StruxureWare Building Operation software Product Line EcoStruxure Building Operation, TAC INET Environment Windows 7 I/Net versions 2.40 and greater Cause With the release of StruxureWare Building Operation's integration with I/NET, customers want to be prepared for it when it comes out and needs to know which version of I/NET software they need to be running to do so. Resolution For the initial rollout, 2.42 was listed as the preparation build to upgrade to for StruxureWare.  Users can upgrade to this build or the current build (2.43 at last edit) and begin upgrading all bin files. This will be required for StruxureWare integration. The bin files did not change between 2.42 and 2.43. Each release of StruxureWare may have a corresponding release of I/NET.  For the time being users will be required to upgrade both I/Net and StruxureWare at the same time. The upgrade from 2.42 to 2.43 is a no-cost upgrade. It should be considered a best practice to upgrade I/NET and StruxureWare at the same time even when not required.  The 1.3.0.938 release of StruxureWare requires I/NET 2.43. If the site upgraded to 2.42 they will not need to upgrade bin files for the controllers.

Issue The damper position value sometimes displays as "NA" Product Line I/A Series Environment I/A Series MNB VAV Cause The VAVActuator object in the controller's database has its position initialization mode set to 0 which means it will initialize the position value at its earliest opportunity following a reset. Therefore, the position will display as "NA" until the controller reaches the full open or full closed position Resolution The VAVActuator object in the controller's database has three options for the position initialization mode following a reset. If having the position display NA for a time following a reset is not desirable the position initialization mode can be set to force the controller to go open or closed following a reset and then it will display a value for the position following a reset. The following table is extracted from the WorkPlace Tech 5.x Engineering Guide Supplement. Set the Initialization Mode to 1 or 2 (in the VAVActuator object properties) and download the application. 

  Issue How can system alarms be configured so that electronic signatures are required? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Alarm Decoration rules are required to configure change control/electronic signatures for system alarms. Resolution Use the Alarm Decoration filters to apply/override settings for alarms. Create an Alarm Decoration Rule under ~/System/Alarm Control Panel/Alarm Decoration   Select the Alarm Decoration rule that filters on all System Alarms or the specific ones, select to override electric signature, and set it to True.    

Issue Deleting Sigma clients from the registered clients list. Product Line Satchwell Sigma Environment Registered client Cause Sigma clients once used will remain in the registered clients list. How can these be removed? Resolution To remove old or unwanted Sigma client entries, carry out the following; Open Sigma "System Setup". Select the "Clients" menu. Select the client that in no longer appropriate. One the client is highlighted, select delete by using the icon or file option. Please note that a Sigma client cannot be deleted if it is still associated with a Sigma server. Refer to Sigma client cannot be deleted.

Issue When installing Building Operation software i.e. License Administrator, Workstation, etc. the following error may show: "This software requires .NET Framework version 4.7.2" Product Line EcoStruxure Building Operation Environment Building Operation installers Microsoft .NET Framework Cause Building Operation requires .NET Framework 4.7.2 or greater to install and function Resolution Most Windows machines have the latest version of Windows installed and updated for security reasons. If for some reason an older version of Windows hasn't been updated then it may show the error until .NET has been updated.   Here is a Microsoft article that shows how to determine what version of the .NET Framework is installed on the Windows PC. How to: Determine which .NET Framework versions are installed There are several methods, this is the registry method:   Windows 10 version 20H2 includes 4.8 as part of its default components. It is recommended to upgrade Windows to this version or greater.   Once the version of .NET Framework is upgraded, the error dialog will no longer appear

Issue How fast does the software run in an AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Cause Knowledge about application cycle time is important when designing project solutions. Resolution Both Function Block and Script programs run at a speed defined by the specific time task they are linked to, the available tasks are: Task 1 - 100mS Task 2 - 500mS Task 3 - 1 Second Task 4 - 5 Seconds Task 5 - 10 Seconds Programs that are not cyclic or time based can be run from a main or executive sequencing program. The AS cycle speeds are comparable to other Building control systems, but the power of the AS allows many more programs to be run in parallel at higher speeds. See also the WebHelp topic Application Scheduler for more information.

Issue Reader beeper needs to be disabled so the reader makes no noise during operation including when a card is being badged at the reader. Product Line EcoStruxure Security Expert Environment Security Expert Smart card readers Cause When attempting to disable reader beeper by toggling the Disable buzzer processing option under Reader expanders Reader options tab the reader will beep when a card is read. Disable buzzer processing: When this option is enabled the reader expander will not control the reader beeper. The reader will beep once when a card is read, but will not beep additional times to indicate access granted or denied. The BZ output can be used for another function. Disable buzzer processing Resolution Unfortunately the reader beeper cannot be completely disabled, it will continue to produce a single beep when a card is read. This single beep on card reads is hardcoded into the reader firmware.  

Issue What is the difference between Lonmaker 3.2 and "Turbo Edition"?  Environment Echelon LonMaker: 900800130: LonMaker 3.2 Standard Ed. 900800140: LonMaker 3.2 Professional Ed. 900800150: LonMaker 3.2 Std Ed Upgrade 900800160: LonMaker 3.2 Pro Ed Upgrade Cause In some documentation and price lists, LonMaker 3.2 is mentioned as "Turbo edition." Resolution There is no difference between Lonmaker 3.2 and "Turbo Edition." It is just a different name for the same product.

Issue Running Bomgar Remote Support Client from Linux for support from Product Support Services Product Line EcoStruxure Building Operation Environment Building Operation Edge Server - Standard Cause Bomgar session downloads Bomgar-scc-[long string of characters].desktop file and need to run to connect with a Product Support Services agent. Resolution The file needs to be granted permission to execute and then run. Open browser on Linux OS for website: https://seconnect.se.com  Enter the 7-digit Session Key and press SUBMIT button. After saving the client to the Downloads folder, right-click on the bomgar-scc-[long string of characters].desktop file, then click Properties.  Click on the Permissions tab, then check the checkbox next to Execute to Allow executing file as program.  Open Terminal, then type "sh " (without quotes and not forgetting a space), then drag the file to the Terminal window, then press Enter. The full command will look similar to this image.  Once the executable runs, this image will appear on the screen as the full session begins.  Click Allow to let the agent view and control your computer. 

Issue Niagara 4.9 (or later) sometimes has a new Host ID that differs from the Host IDs of other versions of Niagara that were installed on the same host PC Product Line TAC IA Series Environment I/A Series N4 Enterprise Server Cause Niagara 4.9 and later, are only available in a 64-bit version. The older Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions. Resolution If the older versions are Niagara 4.3 or lower, you may need to update the older versions, as per the following document… I/A Series G3 and N4 Eliminating multiple HostID on a single PC  Niagara 4.9 (or later) is only available in a 64-bit version.  The other Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions.  In this case, the host PC will require one of the following Un-installing the 32-bit versions and re-installing 64-bit equivalents One license, to be "transferred" to a different Host ID when necessary Multiple licenses, one for each unique Host ID.

Issue Cannot connect network variable point from a third party LON device to a graphic within an XBuilder project.  XBuilder will not allow the drag and drop of LON network variable between the network pain and the system pain when you attempt to create connections. Product Line EcoStruxure Building Operation, TAC Vista Environment XBuilder Vista Lon Device .xif Cause XBuilder is very particular about the format of an .xif file and it will not allow certain characters in the function block name. Vista and LonMaker have far less limitations and these programs are able to parse these characters without causing problems. This explains why your values may show up in the LNS management tool and Vista Workstation. However, once you import the network into XBuilder you are unable to connect the SNVTs to your graphic. Resolution Replace the incorrect characters in the function block line of the .xif and reload the new .xif into your LonWorks Network.  Please see LON device can communicate in Vista, but fails in a Xenta Server / XBuilder for more information about incorrect characters in an xif file. INCORRECT FUNCTION BLOCK EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved. Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000-MP580,8500-SCC,8610-DAC The problem is the three dashes  between the object numbers and the object names in the self doc string.  This is "allowed" in Vista and LonMaker in some sense.  For  example, Vista "replaces this "-" to a "/" but then XBuilder can't handle this situation properly. CORRECTED EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved.  Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000MP580,8500SCC,8610DAC;Tracer MP580 The dashes 3 x (-)s have been removed from the function block name