Building Automation Knowledge Base

Issue How can I/A Series G3 be configured to monitor local setpoint changes on the LON based SE7000 Series Room Controllers? Environment I/A Series G3, SE7000 Series Room Controllers Cause Setpoint values on the LON based SE7000 Series Room Controllers are maintained as a network configuration property (nciSetPts).  Local setpoint changes will not be seen at the I/A Series G3 station unless the value is polled or read. Resolution I/A Series R2 had an object (PollSnvtTempSetptCmd) in the lonextras jar that could be set to poll the nci values on a configurable time basis.  The same functionality can be setup in I/A Series G3 through the use of an interval trigger. Open the kitControl palette and expand the ControlPalette - Trigger folder Add an Interval trigger object and configure as Trigger Mode with the Interval required.  The Interval will determine how often the nciSetPts is updated (polled).  The recommendation would be 60 seconds. Right Click on the Trigger and select “Link Mark” Right Click on the SE Room Controller and display the property sheet for the device Locate and Right Click on the nciSetPts parameter.  Select Link From “Name of Your Trigger”. When the link window appears, select Fire Trigger and then select Force Read.  Select OK to complete the link. All setpoints included in the nciSetPts parameter will be updated at the time interval configured to read what has been set at the local device.

Issue An existing Niagara R2 Enterprise Server was upgraded to 535 but the Vykon Alarm Client (version 2.5) cannot connect to the server. Environment Niagara R2 Cause The Server Name in the Vykon Configuration Utility must be the server's IP address and NOT the station name nor the Windows' Computer Name. Resolution See the VAS_InstallationConfiguration Guide for more details.

Issue How to configure BACnet networks in an IA Series Jace Product Line TAC IA Series Environment I/A Series G3 (AX) ENC (Jace) I/A Series N4 ENC (Jace) Cause Need for a detailed approach to IP and MSTP network setup. Resolution This video explains the steps necessary to configure a JACE to Communicate with BACnet IP and MSTP controllers.

Issue There may be a situation where the External Interface File (XIF) needs to be extracted out of the controller in order to properly set up the controller in a building automation system.  Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment External Interface File (XIF) NodeUtil Loytec XIF Builder Cause These tools will help with the extraction of an XIF file. An XIF file is used to create a Niagara R2 shadow object, a Niagara G3 LMNL file, LonWorks device template, and a SmartStruxure device template.  Resolution The device manufacturer should provide an XIF, and in most cases, a DRF kit as well. The XIF provided by the manufacturer of the controller should be used first but if issues arise it may be required to extract the file from the controller. There are a number of tools available that will create an XIF, but the DRF kit cannot be created by any tool and must be supplied by the manufacturer. This MUST be provided along with the device. The list below covers some of the tools which are available. NodeUtil                          (header: bad,           NVs: ok,                      DMA/File-SCPTs are omitted) Vista's XIF-builder           (header: bad,           NVs: almost ok..,       DMA/File-SCPTs are omitted)  Loytec plugIn                  (does a perfect XIF from a device using Loytec's stack)   NodeUtil is available from the Echelon website (free registration is required) - The NodeUtilLauncher package attached makes it easy to use NodeUtil with Loytec interfaces. Loytec XIF Builder is available from the Loytec website (free registration is required) Using Lonmaker and the XIF Builder. Using NL220 and the XIF Builder. If the uploaded XIF still contains some detailed prompted error, refer to Error displayed when importing a device XIF into SmartStruxure.

Issue When there are multiple panels or graphics assigned to a Workspace, sometimes the layout will be in a mess when viewing it. Environment SmartStruxure Cause The layout for Workspace needs to be manually arranged and saved. Resolution After manually arranged the layout for Workspace, you need to click on the View menu and select "Save workspace layout" to save it. This work needs to be done per user, which means if you have multiple users using this Workspace, you need to log on with each user and save them separately. To set the layout back to the default, go to the View menu and select "Reset workspace layout".

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 Unable to configure Notification Report Template to filter the entries from a trend log that will be shown in the report Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause In many cases it is desirable to show a sub-set of entries from the trend log included in a report filtered by a criteria such as date range   Resolution As of EBO version 3.1 the only way to specify a sub set of entries is via the 'Number of records' property Starting in version 3.2x, the Notification Report Template configuration will allow filtering by custom date as well as providing the following built in filters Today Yesterday This week Last week This month Last month This year Last year

Issue When looking in the EcoStruxure Building Operation Architectural Guidelines for the maximum number of Xenta and LonWorks devices per server, is a TAC Xenta I/O module placed under a TAC Xenta 300/400 counted as a LonWorks device? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The SmartX Server or Enterprise Server doesn't know that the TAC Xenta I/O module exists if it is placed under a TAC Xenta 300/400. The SmartX Server or Enterprise Server only communicates with the TAC Xenta 300/400 and not the TAC Xenta I/O modules under it. Resolution The TAC Xenta I/O module does not count as a LonWorks device in the EcoStruxure Building Operation Architectural Guidelines if placed under a TAC Xenta 300/400. This also means a TAC Xenta I/O placed under a TAC Xenta 300/400 does not count as a  Hosted Node or Connected Product.

Issue How can Workplace Commissioning Tool be used to backup projects and restore of I/A devices? Product Line TAC IA Series Environment I/A Series WorkPlace Commissioning Tool I/A Series MNL controllers I/A Series MNB controllers  Cause Define the procedure for backups/restore in Workplace Commissioning Tool Resolution This demostration shows how to perform backup and restore procedures using Workplace Commissioning Tool

Issue How can I derWho-is broadcasts are causing a large amount of BACnet network traffic Product Line TAC IA Series Environment I/A Series MNB I/A Series WorkPlace Commissioning Tool Wireshark Cause Experiencing network issues caused by Who-is broadcasts.  Resolution This video demonstrates how to... Troubleshoot a Who-is Broadcast Understand what initiates a Who-is Broadcast

Issue After an upgrade to EBO version 3 the  "Alarm State Sort Order" in EBO Webstation is not following the  "Alarm State Sort Order" set in Workstation for certain Alarm Views. Workstation:   Webstation: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and later Cause This issue is only seen on Alarm views upgraded from a version earlier than 1.9 to EBO 3.0 or later The problem is that in EBO version 1.9 Webstation did not follow the sort order for Workstation, back then the sort order in the alarm view in Workstation and Webstation was separated. And the default sort order in Webstation was "Triggered time" when upgrading to version 3 the upgrade does not change the sort order for Webstation. So after the upgrade the sort order in the alarm view is "Triggered time" and it will not follow the sort order from Workstation.    Resolution In EBO Webstation version 3 click on the "Filter" button in the Alarm view. Click on "Sort" and remove "Triggered time", click OK In Workstation open the Alarm view and right-click, Open Alarm view settings and click on "Reset standard layout to standard default"  

Issue Access denied error creating ContinuumDB Environment Cyberstation SQL Server Cause Firewall blocking Resolution Ensure the firewall at both the WS and the SQL Server are not blocking the DB creation process. Turn off all aspects of McAfee or Norton Anti-Virus. In particular, McAfee On-Access Virus Scanning can cause this

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue How to connect to the Jace 8000 system shell Product Line TAC IA Series Environment I/A Series Jace 8000 Cause Multiple diagnostic and low-level configuration processes need to be performed directly connected to the Jace 8000 in the system shell of the device. Resolution Connect the USB cable between the controller’s Debug port and the USB port you are using on your PC   On your PC, start your terminal emulation software. For example to start PuTTY from the Windows Start menu, this is typically Programs > PuTTY → PuTTY. PuTTy can be downloaded at no cost if you do not already have it on your PC. In the tree in the PuTTY Configuration dialog, expand Connection and click Serial. Set the “Serial line to connect to” for your PC’s (USB) COM port to use. For example, COM3. NOTE: You can examine Ports in Windows Device Manager to determine which serial port is in use on the PC. If you don't see the Jace in the COM ports, you will need to install the driver which can be Downloaded from FTDI.  It is also attached to this document below for Win10. Set the “Configure the serial line” fields as follows: • Speed (baud): 115200 • Data bits: 8 • Stop bits: 1 • Parity: None • Flow control: None In the tree in the PuTTY Configuration dialog, click Session and then click/select the “Connection type” as Serial NOTE: (Optional) You can save this configuration to reuse (load) in future PuTTY to JACE serial sessions. To do this, type in a connection name in the “Saved Sessions” field (for example, “JACE- 8000-S”), and click Save. When you start PuTTY again to serially connect to the JACE, select this name and click Load. At the bottom of the PuTTY Configuration dialog, click Enter. At the login prompt, enter a platform user name, and at the password prompt, the platform password. a. If prompted for system passphrase, enter the platform’s system passphrase. If login is successful, the TITAN System Shell menu appears. When finished making platform changes from the system shell, do the following: • If no changes or reboot is not necessary, simply type L to Logout. • If changes require rebooting, select the Reboot option. Type “y” at the “Are you sure you want to reboot [y/n]” prompt, and press Enter. Shutdown-related text appears in the terminal (PuTTY) window. Click the Close control (upper right corner) in the terminal session (PuTTY) window. Click OK in the “PuTTY Exit Confirmation” popup dialog. Unplug the USB connector from the JACE’s Debug port. This procedure is simply how to connect using USB serial port for system shell.  More information about functions available once connected can be found in other Knowledge Base articles and in the Jace 8000 Install and Startup Guide

Issue Losing VAS client connection; getting error: java.lang.outofmemoryerror: unable to create a new native thread. Environment R2 VAS 2.50 Cause Users at the client were not signing off but rather switching users causing multiple connections to VAS from the same pc.  Resolution Ensure user is logging off, not just switching users.

Issue Upon rebooting an MP-V, that has not yet gone through a Flow Balance, the Box Flow data goes to zero. Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV Cause When a box is not yet balanced, the Balanced K-Factor is zero. Part of the calculation of Box Flow is based on the Balanced K-Factor. Resolution There are two workarounds for this issue: Workaround 1: Balance the box Workaround 2: Enter in a number for the Box measured maximum flow and the Hood measured maximum flow. Either option will update the Balanced K-Factor to being a non-zero value.   This has since been fixed and first consolidated in IPC Hotfix 3.01.02.02000 (CP1), and fixed in release firmware release v3.02.01. See details in Box Flow goes to zero on restart, warm start, or cold start in the Known Issues and Solutions community page.

Issue RP-C address dial is difficult to see in poor light Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RP-C) Cause The controller modbus address setting dial is difficult to see in poor light conditions. Resolution By default, the dial is set to address '1' (there is a small arrow on the cross head dial) and the dial is numbered 1....9,0 clockwise.

Issue Has a ListView defined under a controller that shows the alarms for that controller only. Error 'Object does not exist' when trying to use 'is like' with Device ID in a list view qualifier. Example:   Environment CyberStation Cause Documentation Resolution When adding the qualifier DO NOT write the word ID after the device name in the value field, Continuum will automatically add it when the list view is saved. NOTE: If getting the error even after removing 'id' from the qualifier try entering the full path to de device.

Issue XIF files for Version 1 and Version 2 of MNL controllers Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure with MNL Cause Not available on other online resources Resolution Download the zip file available here for the following profiles:

Issue On a old MNL project, a MNL-MI device was found. Is it required to integrate into SmartStruxure? Environment SmartStruxure with MNL Cause Outdated LON product Resolution The MNL-MI provided network-level management functions for a network of MNL controllers.  An RS-232 port on the MNL-MI provided for a connection to a computer running the MicroNet Tech Tool or MicroNet View software (both obsolete).  It is not required for a SmartStruxure integration and can be removed from the LON trunk.

Issue Attempting to set the Retain Level attribute of a Value object results in the following error: Saving Changes Invalid data 'Prohibit to retain both Value and priority properties at same time: (point name) Invalid data Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.1 Cause Prior to EBO 3.1, it was possible to set retention levels on both the Value attribute and individual members of the Priority Stack. Starting with 3.1, that is not allowed and will give this error if you attempt to change the retain level setting of a Value that already has it set on a Priority, or vice versa. For systems configured in EBO 3.0 or prior that are upgraded to 3.1, the now invalid double-retention will be resolved automatically during the upgrade by retaining the Priority Stack retention level and setting the Value attribute Retain Level to No. Resolution Only set the retain level on one attribute of an object. The best attribute to retain is the Value. Setting Retain Level to Cold Start or Warm Start on the Value will also retain the full priority stack on a power failure or restart. Check the retain levels of each member of the priority array and ensure all are set to "No" and then set the Retain Level of the Value attribute to "Cold Start" or "Warm Start." To clear the retain level of individual priorities: Open point's Property window Click the Command tab Click the gear icon next to a Priority level, most likely starting with Priority 16. Check the checkbox for Retain level and set to No. To set the retain level on the Value attribute: Open point's Property window Click the gear icon next to the value Check the checkbox for Retain level and choose the desired level.