Building Automation Knowledge Base

Issue Backing up a GCM database in Tree Tech, but the system wasn't originally engineered using Tree Tech. Is there a documented procedure for doing so? Environment Tree Tech 3.1 or 3.2 Tree Tech Engineering Guide, F-26640-4 Network 8000 GCM-84000, GCM-86000, LNC-1000, SIM-x Cause Earlier versions of the Tree Tech Engineering Guide, F-26640, didn't include a step-by-step procedure for backing up a GCM that had not originally been engineered using Tree Tech. Resolution The latest edition, Tree Tech Engineering Guide, F-26640-4,  has been appended to include a step-by-step procedure for creating and configuring all Tree Tech components necessary for ultimately uploading a GCM database. A link to this revised edition is available through the "Help" menu:     See Appendix B, "Creating a GCM Database Backup". Topics include: 1. Creating a New Project Database 2. Adding the Equipment Segment 3. Adding the Network 8000 Object 4. Adding a GCM to the Network 5. Adding the Workstation Segment 6. Adding a Port 7. Configuring the NETWORK 8000 Network 8. Communicating with the GCM 9. Prepare for Backup (Upload) 10. Uploading the GCM Database

Issue How do you convert MicroNet 2000 controller filenames generated by the MicroNet Controller Interface "Get Multiple" function to integrator and controller addresses? Environment MN-2000, MN-CI, MicroNet Controller Interface Cause The "Get Multiple" function is used to upload application programs from multiple MicroNet controllers under one MicroNet Integrator or a series of MicroNet Integrators.  The application programs are stored as files with the integrator and controller addresses appended to the name. Resolution When uploading files from multiple MicroNet VAV Controllers, the CI creates unique filenames for each uploaded application file by appending the integrator number and device number to the prefix entered in the Enter File Prefix window. The integrator number and device number are appended in hex format. The file shown in the illustration above was uploaded from MicroNet controller 11 under MicroNet integrator 6.

Issue Unable to access the "Tools" menu item to configure options in the "standalone" version of I/A Series G3 Alarm Portal Environment I/A Series G3, Alarm Portal, ENS-ALM-CON-G3 Cause The "Tools" menu item was removed in I/A Series G3 versions 3.6 and higher to prevent any user from configuring Alarm Portal options (e.g. appearance and operational behavior). Resolution Configuration of the Alarm Portal options on a "standalone" version requires a set of files to be transferred from a full Workbench version of the Alarm Portal to the standalone version. Start Workbench and select Tools - Options Configure options (e.g. Alarm Console, Alarm Portal) Close Workbench and use Windows Explorer to locate the options subfolder for the user that modified the Alarm Portal options Copy the associated options files (alarm-AlarmConsoleOptions.options and alarm-AlarmPortalOptions.options) to the standalone Alarm Portal. Place the files under the appropriate user using the same path structure in an options subfolder.  The Alarm Portal will now use the options defined.

Issue The MnFlow shadow device, in Niagara R2, comes with six objects.  What do the inputs and outputs cross-reference to down in the Micronet 2000 VAV controller? Environment Niagara R2 (ASD driver) Micronet 2000 Cause Programming Niagara objects to control setpoints in the Micronet VAV Resolution Document F-25720 lists tables illustrating what each input and output is mapped to in the Micronet VAV. MnFloEmsDi object in Niagara R2: MnFloEmsAi object in Niagara R2: MnFloDvOuts & MnFloAvOuts objects in Niagara R2:

Issue OPC points status' shown as 'fault' and not updating after Matrikon OPC Server is restarted Environment I/A Series r2.301.529 Enterprise Server OPC Client integration to Matrikon OPC Server Cause The root cause for this issue has not been determined at this time, the following workaround currently resolve this issue.  Resolution The current workaround is to disable and then enable the OPC Server in WorkPlace Pro.  1. Right click on the OPCServer object and go to its properties. 2. Go to the Config tab. Change the serverEnable property to False and Apply. Change the serverEnable property back to True and Apply.      

Issue Dimensions for the ENCL-DOOR-PLA.  Environment DMS Cause They are not provided on the datasheet available via iPortal. Resolution Dimensions are illustrated below:

Issue How to extract the status of DI 01 from a Viconics thermostat for plotting on a web graphic in Niagara. Environment Niagara R2 Cause Integration requirement Resolution In the Se76PIR shadow object, use nvoSccStatus, bit 18 (see illustration below).   Link to a DynamicDemux object (located in the lonworks jar file, conversion folder) to gain access to bit 18.  Now it can be used in the Niagara station for graphics or logic programming.

Issue It takes a lot of time to test each node in a database to verify that they are all truly online. Environment NL220 Cause Instead of checking each node in NL220 one at a time, a test can be performed that will check all nodes at one time. Resolution Right click on the subsystem in the network tree of NL220 Click on Nodes Make sure that "Recursive commands on subsystem" is checked Click on Network Click Test NL220 will now go through the entire database and perform a test on each node.

Issue Niagara R2 hosts in a Microsoft Windows Server Environment Environment Niagara R2 Cause Replacing a UNC-6x0 with a UNC-520 reduces the feature set available when connected to a Windows network. Resolution Summary table listing the features of Niagara R2 hosts on a Windows network.  A JACE-NP is a UNC-6x0.  A JACE-5 is a UNC-520.  A JACE-4 is a UNC-410.  This table can also be found in the Network Connectivity Guide, Chapter 3, Table 3-1, page 3-5.

Issue Several Viconics LON thermostats are installed on a job.  Only one won't communicate properly.  What do the different conditions of the Status LED indicate? Environment Viconics all LON thermostats Cause One of many installed is not communicating properly Resolution Different possibilities with the Status LED behavior for the LON thermostat

Issue Checking COM port settings in SIGNAL. Environment SIGNAL (all versions) Cause Troubleshooting communications Resolution There are two locations to check COM port settings:  the main SIGNAL desktop and in Project Manager. The setting must be an exact match in both locations.  The example below is for a Direct Connection to a GCM (Network 8000) Main SIGNAL desktop Click on the Utilities pull-down menu and select Configure Communications. Highlight the computer COM port number to be used and then click the Configure button.  The following screen shows the required settings:     Project Manager From the main SIGNAL desktop, click on Project Manager. Double-click the Gateway Record and then the Communication button. Ensure the settings are as illustrated below:  

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.