Building Automation Knowledge Base

Issue The vertical scale (y-axis) in an R2 chart/log is limited to the range of 0 - 0.2, but the values in the log/ table are of a much wider range; e.g. 0.66 - 87.33. Environment R2 chart/ log data Cause Initial testing shows that the y-axis scaling issue is caused by data value of NA in the log table. Resolution As a work around, backup the station, export the .xml file. Search it for data = NaN.  Edit the line in the file so the data no longer shows NaN.

Issue How can a link be added to a Niagara R2 graphic that will display a pdf file? Environment Niagara R2 Cause Easy access to documentation via the graphic Resolution Here are the steps: Create a new folder within the running station's folder:  \niagara\ \stations\ .  Label it "Documents" (any name is fine). Paste a copy of the desired pdf file to this new "Documents" folder. Open the desired graphic in Workplace Pro, and create a new GxText object. In the Local Library, navigate to the "Documents" folder.  The pdf file should be listed below it. Right-click > Copy, the pdf file. In the Properties > Visual tab of the GxText object, place the flashing cursor in the 'hyperlinkURL" box and press + V.  This will paste the SWID of the pdf file in the box. On this same screen, for the "hyperlinkOnClick" setting, choose URL. Apply all changes. Note:  The pdf file will not actually display if viewing the graphic in Workplace Pro.  It will appear when viewing the graphic in a web browser.  

Issue When creating a third party device template with a given XIF file, NL220 displays an error LN#12. Environment NL220 Given XIF file Cause Echelon explanation: The file containing the external interface information of the device has been corrupted, or is missing. The device manufacturer should be contacted to provide a valid XIF file, or the file should be re-built using the Neuron C compiler and linker. Alternatively, the device could be installed using an "Ad-Hoc" installation scenario, in which XIF files are not required. This requires the device to be available, online, functioning, and not having the self-documentation features disabled. Resolution Trying to get the XIF file from the device In the device template panel, creating the template From Network.   If step one failed, in the subsystem try Create Node from Network.   NOTE: when trying to upload the XIF file from the device, the device need to be connected and be online. If all steps above failed, please contact product support and provide the XIF file for investigation.

Issue Dimensions for the back plate (part # ENCL-300-BKP) used with the ENCL-300-TUB. Environment General Hardware Cause Dimensions not listed in iPortal Resolution Length = 28"     Width = 22.5"     Depth (thickness) = 0.5"

Issue Can more than one Room Temperature Sensor be connected to a MicroFlo II? Product Line TAC IA Series Environment Network 8000 Microflo Cause Site changes / retrofit Resolution The only supported configuration is one Room Temperature Sensor for up to four MicroFlo II controllers (see below). TAC Hardware Installation Practices TS-90250-850 Communication/Sensor wiring for up to 4 TAC Microflo lls sharing a single Room Temperature Sensor. Room sensor includes a 11K ohm resistor and setpoint with ASD communications. Do not add another 11K ohm resistor when installing. The ASD communication wiring MUST be isolated from the sensor/setpoint wiring. Use separate shielded cables for each. Connect the SHIELD DRAIN wire to the SHLD or GND terminal at the controller. If a ground is available at the room sensor, connect the DRAIN wire to ground. If a ground is not available, tape the DRAIN wire back at the external device only. A 120 ohms resistor (part number 40-1758) must be installed across the ASD terminals at each end-of-line (EOL). Total overall wire length between TAC MICROFLO lls and the room sensor MUST not exceed maximum distance specified. Set each address switch to uniquely identify each TAC MICROFLO II controller (refer to the job drawings). Set the MASTER/SLAVE jumper pins to the correct position (factory shipped as MASTER units). I/O Wiring - TAC MICROFLO

Issue Several MN-FLO3 and MN-FLO3T VAV controllers are connected to a Micronet 2000 MicroSmart Integrator.  There is a mode control point in the integrator for each VAV controller.  Each mode control contains elements assigned to the various setpoints that are adjustable per VAV controller.  Which ones are they? Environment Micronet 2000 Niagara R2 & G3 Cause Trying to map the proper mode control 'element' to a shadow object in Niagara so as to provide a user with setpoint control via a Niagara graphic. Resolution There are seven setpoints that are adjustable.  They are assigned to the element name 'PVALU' along with a number from 1 to 7.  See table below. 

Issue The I/A Series G3 Platform Software Manager indicates "Not Available Locally" when connected to the remote platform (ENC or JACE). Environment I/A Series G3 - All versions Cause Upon start of Workbench, the modules residing in the local Workbench module folder are scanned by the software.  During this process, new and/or updated modules are copied and saved into the local software database.  "Not Available Locally" indicates the associated module is missing from the local Workbench software database.  The following example finds the Installed Version of tacMs at TAC 3.4.64.4 with the Available Version missing with the comment "Not Available Locally." Resolution There are two methods to correct this issue. Method 1:  Copy the module directly into ~\modules directory. This makes the module(s) available in your Workbench environment, and also available to install in other remote platforms.  When the installer runs, the module(s) are also copied into your software database, available for installation. This is the typical choice. Method 2:  Copy the module into your ~\sw\inbox directory (or, use the equivalent “Software Import” feature in the Software Manager). In this case, the module(s) are not used in your Workbench environment, but are available in your software database for installation in remote platforms. If the module is invalid or corrupt, the software manager will generate and place the module in the "failed_imports" folder (e.g. unable to read the manifest files, class files, etc.).  Verify the module is valid. Reference the Niagara AX Platform Guide - Software Manager for additional details.

Issue Unable to pass data to an Enterprise Server from a UNC Environment R2 Niagara Cause bad subscription access denied 401 error Resolution Check address book and system properties.

Issue Getting error - Cannot start component: Asd Block Output Proxy Ext during the startup of the I/A Series G3 tacAsd driver.  The error appears as follows: ERROR [16:31:24 04-Mar-13 CST][sys.engine] Cannot start component: Asd Block Output Proxy Ext java.lang.ClassCastException: com.tac.tacAsd.point.BAsdPointBlockDeviceExt incompatible with javax.baja.driver.BDevice Environment I/A Series G3, tacAsd, ASD driver Cause The driver appears to operate however errors are displayed during the station startup sequence.  The error is typically related to a set of BAsdPointBlockDeviceExt objects that were duplicated as a child of the points deviceExt. Resolution Review the Points folder for each ASD device and remove the duplicated or improperly placed BAsdPointBlockDeviceExt objects.  The Batch Editor can also be used to assist in locating the duplicates. Open the Batch Editor from the Program Service and select Find Objects Using the BQL Query Builder - select (Custom Type), tacAsd, AsdPointBlockDeviceExt - select OK. This will list all AsdPointBlockDeviceExt extensions and their associated path.  There should only be one Points child folder for each device.  Locate and delete the duplicate Points folder and objects.

Issue When accessing an I/A Series R2 or I/A Series G3 station web page, a popup window is displayed warning of a possible security vulnerability. The popup warning is displayed differently depending on the browser version and Java version installed on the computer used for viewing the graphics. -------------------------------------------------------------------------- With Java 7 update 11 or newer, and Internet Explorer 8 or 9, the following popup windows is displayed (location string will vary):   Note that even if you check the "Do not show" checkbox, you will receive additional prompts because the prompt is displayed for each Java applet encountered in the current browsing session.  Likewise, if you close the browser and reopen it, navigating to the same site, the prompts will again be displayed. If accessing I/A Series G3 graphics, the following screen may be displayed: A variant of this message is as follows: --------------------------------------------------------------------------- If using a recent version of the Firefox web browser, the following message is shown in the graphic applet window: "This plugin has security vulnerabilities.  Click here to activate the Java(TM) Platform SE 7 U Plugin."   --------------------------------------------------------------------- When using the Mozilla Firefox browser to access I/A Series G3 graphics, the following security warning may be displayed (Click "I Understand the Risks" and follow prompts to continue):   Environment Windows computer Internet 9 or Firefox web browser Cause Known security vulnerabilities with the Java JRE software Resolution Since the issue is being reported by the Java software or the Java plugin in the browser, there is nothing we can do to directly resolve the issue. There are several workarounds possible, depending on how the site deals with browser security issues. The most secure approach is to allow the applet to be run each time you are prompted. If using Internet Explorer, click the [Run] button on the security warning popup window. If using Firefox, two actions may be needed.  First if the warning "This connection is untrusted" is displayed, click the "I Understand the Risks" Unfortunately, this is a Java issue, not an I/A Series R2 software issue. Oracle has added this popup to its browser plugin to warn the user that a downloaded Java applet may be unsafe to execute. According to information published by Oracle, it may take them up to two years to correct all the known security issues in the Java-JRE. Many of the known issues date back to before Oracle assumed ownership of Java. The only workaround at this time is to downgrade the Java-JRE to a version that does not notify its user that the Java applet to be executed may pose a security risk. We did some testing on Windows 7 with IE9 and found that Java 1.7.0.9 (Java 7 update 9) does not cause the prompt to be displayed. In addition, we found that in some cases we were able to greatly reduce the number of times the prompt appears in Java 1.7.0.17 by setting its security setting to Low (Java control panel applet, Security tab). On one of the virtual machines that we tested this on, the prompt would be displayed the first time you accessed the site and would not be displayed again until you closed the browser and reopened it. On a second computer, the prompt would be displayed each time you accessed a new site or re-opened the connection to the same site but not on multiple screen accesses from the same site. We are not sure at this time why some systems exhibit this different behavior. Note that when using Firefox 19.0.2 and Java 7 update 9 or earlier, a different message is displayed when the web page attempts to open a java window. This window is not displayed when using any version of Java that includes its own security warning popup. The security warning popup I am referring to is the same one displayed when using Java 7 update 17 and other recent versions on Internet Explorer 9 or Firefox 19. This message is designed to notify the user that there is a known security vulnerability with the addon being used, in this case, the out-of-date Java plug-in. There is a workaround published on the mozilla support site that documents a procedure for disabling these warnings when using the earlier versions of Java 7. This workaround does not solve the Java popup warning issue for the Firefox 19.0.2 / Java 1.7 update 17 combination. I did not test it with other combinations other than Firefox 19.0.2 / Java 7 update 9. Here is the configuration change for Firefox 19: Open Firefox Open a New tab Browse to about:config i.e., enter the string in the browser address bar Accept the security warning In the displayed list, right click on extensions.blocklist.enabled In the selection window, click Toggle to change the entry to false Close and reopen the browser. This will disable the security warning for all browser plugin applets, including Java 7 update 11 and earlier, Java 6 Updates 31-38, Adobe Flash Player 10.2.*, 10.3 or 11.0-11.4, Microsoft Silverlight 4.1 and earlier or 5.0/5.1, and about two dozen other plugins that have known security issues. At this time we have not found any workarounds for disabling the Java security warning popup that occurs with Java 7 update 12 and newer with either Internet Explorer or Firefox. As additional information regarding this issue becomes available regarding Java and Internet browser updates, this article will be updated as required.  Depending on site security restrictions, it may be necessary to disable Java when not using it for accessing I/A Series R2 or G3 systems.  See the following instructions from the Java web site: To disable Java - http://java.com/en/download/help/disable_browser.xml To enable Java  - http://java.com/en/download/help/enable_browser.xml In some cases, you may be able to bypass the warning but all your graphics pages do not  load.  This issue is sometimes caused by a security issue with some of the cached java temporary files.  There is a workaround, as follows: In the Windows Control Panel, open the Java applet. Under the "General" tab, "Temporary Internet Files"  section, click [Settings] Uncheck the box "Keep temporary files on my computer" Click [Ok] to save the change then click [OK] to exit the Java control panel.

Issue After installing WorkPlace Tech, the Purchase program is accessed with no issue.  All the information is added including a Field Office Information, Shipping Information, End Customer Information, a WIBS serial number and a Part Number from the Package List.  When clicking on the Add to Order List button, a pop-up window indicates that the program cannot open the License File.   The license file does not accept any attempts to write to it. Environment WorkPlace Tech 5.x Windows 7 Cause A Windows user account setting is preventing proper operation of executable files. Resolution If the user account settings cannot be modified, then right-click on the executable file and select "Run As Administrator".  Right-click on the executable file and go to Properties > Advanced and select the checkbox for "Run As Administrator".  This applies the "Run As Administrator" setting always.  Now just double-clicking on the executable file is sufficient.

Issue When running TreeTech revision 3.1 or 3.2 attempts to open projects and edit object properties could result in the following error messages: "Failed to start viewproperty.exe. Verify path is correct" "Failed to start propeditor.exe. Verify path is correct" Environment TreeTech 3.1, 3.2 Windows XP,Vista, 7 Cause In TreeTech 3.1 the default path for projects was changed to support newer operating systems. Operating System Default Path Windows Xp\P C:\Documents and Settings\All Users\TAC\TreeTech\Jobs\ Windows Vista/7 C:\ProgramData\TAC\TreeTech\Jobs\ In revision 3.2 the path changed to use Schneider Electric.  Operating System Default Path Windows Xp\P C:\Documents and Settings\All Users\Schneider Electric\TreeTech\Jobs\ Windows Vista/7 C:\ProgramData\Schneider Electric\TreeTech\Jobs\ This can be seen live by creating a new project in TreeTech and observing the default path. Resolution Due to the fact that any previously created projects will not be moved when installing TreeTech revision 3.1 or 3.2 these files must be moved manually to the new default path. Once the project has been moved it will function normally without the error messages.

Issue Are replacement covers available for the MicroNet 2000 wall sensors (MN-S, MN-SO, MN-SDK)? Environment MicroNet 2000 wall sensors: MN-S MN-SO MN-SDK Cause Customer wants replacement covers. Resolution As of February 28, 2013 replacement covers are available, part number MNA-STAT-1. Contact Customer Service to confirm price and availability, as they are subject to change.

Issue After creating a new Project and a new E: Equipment Database in TreeTech, the following error message appears when adding a new Network: Product Line TAC IA Series Environment Windows 7 TreeTech Cause TreeTech requires administrative rights to the Windows user account Resolution Right-click on the TreeTech shortcut Select 'Run as Administrator'

Issue Integrating several MNB-300 controllers to a UNC-510.  Bias resistors are available on the UNC-520 but not the UNC-510.  How can bias resistors be added to this MSTP trunk? Environment Niagara R2 UNC-510 Cause The UNC-510 was not designed to include built-in bias resistors for a BACnet MSTP trunk. Resolution The MNB-300 has built-in bias resistors that are disabled by default.  Remove the cover and enable them with the jumpers provided.  Keep in mind that no more than two sets of bias resistors are to be enabled for any MSTP trunk.  For more information, see the MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360).  

Issue Getting distribution file installation (no core software) error when attempting to commission the JACE-6E.  The error states "No core software was found that can be installed to the remote host." Environment I/A Series G3, JACE-6E, TRD-J-600E Cause Attempting to install an I/A Series G3 version that is not compatible with the JACE-6E platform (e.g. versions below 3.6.47). Workbench not set up to be an installation tool (required distribution files are not available within the Workbench environment). Resolution Attempting to install an I/A Series G3 version that is not compatible with the JACE-6E platform (e.g. versions below 3.6.47). The TRD-J-600E is compatible with I/A Series G3 version 3.6.47.1 or later. The I/A Series ENS with Workbench files are available for download from The Exchange Download Center. Workbench not set up to be an installation tool (required distribution files are not available within the Workbench environment). Re-install the I/A Series G3 software and enable the checkbox that configures Workbench to be an installation tool. The checkbox indicates "This instance of TAC I/A Series Enterprise Network Server will be used as an installation tool." The distribution files related to each of the platforms will be installed on the computer.

Issue In I/A Series G3, is there an object that provides a BooleanStatus output reflecting the overridden status of a Boolean Writable or Numeric Writable? Environment I/A Series G3 Cause Need to detect and / or act upon the status conditions of a Boolean Writable or Numeric Writable object. Resolution A StatusDemux object can be linked to the Boolean Writable or Numeric Writable object to provide a Boolean output for each of the status flags (Alarm, Down, Fault, Null Status, Disabled, Overridden, Unacked Alarm, and Stale). Within the Wire Sheet that contains the Boolean Writable or Numeric Writable object: Insert a StatusDemux object (from the kitControl pallet, Util folder). Link the "Out" from the Boolean Writable or Numeric Writable object to the StatusDemux "In Boolean" or "In Numeric" input.

Issue Disable alarm using the status of another object / point Environment I/A Series G3 Workbench Cause Alarms are not required to be generated when equipment is not running. As an example, alarms should not be generated when the equipment is not running after hours.  Resolution Object alarm extensions have an 'Alarm Inhibit' property which a Boolean object can be linked to. A true value at the 'Alarm Inhibit' prevents alarm generation due to any transition or state change.  The Alarm Inhibit property is within the alarm extension. As such, it is not visible on the parent object and therefore, unlinkable. We can expose properties of an extension by using the 'Composite' function. After adding an extension to a Control object. Right click on the object and select 'Composite'. The Composite Editor window will appear.   In the Composite Editor, expand the object and the extension.   Find 'Alarm Inhibit' and double click on it. Alarm Inhibit will be added to the right of the Composite Editor window. You can rename it if required. Click OK.   The Alarm Inhibit property will now be available on the parent object and linkable from a Boolean object. 

Issue On an InVue client computer, alarms are not being received. When opening Windows 2000 DDE shares and selecting Shares/DDE Shares, an error pop-up window appears: Environment Wonderware for Intelligent Buildings (WIBS) 1.1 Windows 2000 Cause NetDDE service is not running. Resolution Access the Services in Windows 2000 and start the NetDDE Service.  Modify its properties so that it runs automatically on bootup of Windows.

Issue Getting I/A Series G3 javax.baja.xml.XException error when attempting to configure proxy extension conversion as Generic Tabular. Environment I/A Series G3, ENC, JACE Cause The conversion selection Generic Tabular provides a way for a VoltageInputPoint or ResistiveInputPoint to support a non-linear responding signal on a universal input (using point Facets other than temperature).  Generic Tabular uses a "lookup table" method similar to the "Thermistor Tabular" conversion, but without predefined output units.  Selection provides a popup Tabular Conversion Dialog in which you can enter a custom source-to-result" non-linear curve, including the ability to import and export response curves.  Use of Generic Tabular requires the kitIo module to be installed. Resolution Use the Platform Software Manager to install the kitIo module into the target ENC or JACE.