Building Automation Knowledge Base

Issue OPRIF 11.6 runs in a Command Prompt window and does not maximize to a full-screen.  This is observed on a Windows 7 computer. Environment OPRIF 11.6 Windows 7 (any version) Cause By design Resolution The Command Prompt window does not work in full-screen mode in Windows 7 as designed by Microsoft. OPRIF 11.6 was designed to work within a command prompt window.  As a result, it cannot operate in full-screen mode. By accessing the Properties of the command prompt window, it can be enlarged slightly: The Magnifier program which comes with Windows 7 can also be used to enlarge the command prompt window running OPRIF 11.6.  Screen resolution will be somewhat compromised.

Issue If there is an online selection tool for all the HVAC sensors (room temperature sensors, duct pressure sensors, etc.) Environment All Schneider Electric Buildings product lines Cause Since Schneider Electric manufactures a huge amount of sensors for different product lines. Sometimes it takes a bit of time to search for the right sensor. Therefore, Schneider Electric developed an online selection tool to help customer pick the right sensors. Resolution Click here to go direct to the online HVAC sensors selection tool. Select the desired features of the sensor. All sensors match the requirements will be displayed on the right. Datasheets can be accessed by clicking on the image or the part number. NOTE: the listed sensors may not be available in some region. Please contact the local sales or Support team to confirm the information.

Issue DuraDrive actuator feedback is 0-10 VDC or 2-10 VDC, controllers accept 0-5 VDC. Environment DuraDrive actuator (MS4x / MS5x series) MNL / MNB controllers Cause The voltage feedback output was designed for controlling slave actuators configured for 0-10 VDC or 2-10 VDC control signals. Resolution Use two 10k resistors as a voltage divider across the feedback leads with the center point connected to the controller input and the actuator common connected to the controller common. NOTE: Not all actuators in this product family use the wire colors shown for the feedback output. Please refer to the actuator GI sheet for the correct colors.    MNL / MNB Controller Analog Input Configuration For actuators with a 0 VDC to 10 VDC feedback output: Type= Volts Linput = 0 Lscale = 0 Hinput = 5 Hscale = 100 This input configuration provides a 0 - 100% output corresponding to the Actuator Position, based on feedback voltage 0 VDC = 0% and 10 VDC = 100% of actuator travel.  For actuators with a 2 VDC to 10 VDC feedback output: Type= Volts Linput = 1 Lscale = 0 Hinput = 5 Hscale = 100 This input configuration provides a 0 - 100% output corresponding to the Actuator Position, based on feedback voltage 2 VDC = 0% and 10 VDC = 100% of actuator travel.

Issue I/A Series R2 LON Device Manager does not allow me to perform a "Replace Node" to replace an MNL standard controller with a newer version of the same controller.  For example, replacing MNL-20RS1 with MNL-20RS3. MNL-xxRF2 replaced by MNL-xxRF3 MNL-xxRH2 replaced by MNL-xxRH3 MNL-xxRR2 replaced by MNL-xxRR3 MNL-xxRS1 replaced by MNL-xxRS3 MNL-xxRS2 replaced by MNL-xxRS4 MNL-xxRV2 replaced by MNL-xxRV3 Environment I/A Series R2, UNC-410, UNC-520 Cause Slight changes to the profile were made requiring a change in the device's program ID. The replace node will only succeed if the device program IDs exactly match. Resolution There are three methods to exchange the MNL shadow objects (e.g. MNLRS1 to MNLRS3, etc.).  The first method is to manually use WorkPlace Pro to delete the existing shadow, adding the new shadow object, and re-linking the associated logic. The second method is to manually edit an updated XML backup of the station database.  The following summarizes the changes required to convert a shadow object from V3.x controller profile to V4.x controller profile via XML. It is recommended to use an editor such as Textpad which is available at no cost and can be downloaded at http://www.textpad.com. Fan Coil Profile MNLRF2 replaced with MNLRF3 Heat Pump Profile MNLRH2 replaced with MNLRH3 Rooftop Profile MNLRR2 replaced with MNLRR3 Satellite Profile MNLRS1 replaced with MNLRS3 Satellite Profile MNLRS2 replaced with MNLRS4 VAV Profile MNLRV2 replaced with MNLRV3 The same modifications were made between the various profiles so the following can be used to modify each. Step 1: Replace the shadow object referenced in the text file with the appropriate new object. Do not modify the node name. For this example, replace MNLRS1 with MNLRS3.     Step 2: The nvoSecAlarm has been replaced by nvoDeviceAlarm. The only change was to remove the Sec (Siebe Environmental Controls) reference and make the nvo more generic in name. All other information (i.e. SNVT type, etc.) remains completely unchanged. Since the nvo was specifically designed to work with these devices, a binding will most likely not exist.  Note: There are two tags to edit, one tag at the start of the definition and one tag that ends the definition. Step 2: The nciSecModelNum has been replaced by nvoDeviceInfo. The network configuration property was removed to free precious EEPROM required to compile the new Echelon library. The SNVT type and index position remains unchanged. This nci was a manufacturer defined property and typically only read by the user. The information now is calculated and provided as an nvo. Replace the entire section. The third method is to use a utility included with the Smartware Tech WorkPlace Pro Utilities package.  A utility named “Profile Update” can be used to work on an offline XML to upgrade these objects. Additional information as well as Smartware's contact information can be found at http://www.smartwaretech.com.          

Issue Saving station information within the I/A Series R2 Niagara Application Tunneling dialog window generates the following error: Windows Shell Common Dll has stopped working. This occurs when attempting to configure and use the tunnel client on a Windows 7 32-bit operating system. Environment I/A Series R2, LON Tunnel Client, Serial Tunnel Client Cause I/A Series R2 Tunnel Client dll file compatibility and Windows 7 operating systems. Resolution Configure the Niagara Application Tunneling dialog box with the station information as required. For the serial tunnel, select a valid COM port and enter the host address, username, and password.  For the LON tunnel, select a valid LON port and enter the host address, username, and password. NOTE: The tunnel client must be configured for Silent Mode. Select OK to save the data. Following dialog box is displayed indicating Windows is checking for a solution to the problem. The workaround involves selecting Cancel prior to the Windows timeout notifying the user to Close Program. Selecting cancel prior to the Close Program timeout saves the station information within the Application Tunnel.

Issue The software is no longer distributed on a CD.  Customer wants to install and license the software on his computer. Environment TreeTech 3.1 Network 8000 GCMs DMS panels Cause None. Resolution Download the software "TreeTech-3.1.exe" on The Exchange Download Center. Install the software by running the downloaded program file and following the displayed prompts. Run the "Purchase WIBs" program from the computer desktop.  This icon and program will be automatically installed on the computer if it does not already exist. Click the [Purchase] button to start the program. Fill out the Field Office and Customer Information parts of the form.  Make sure to fill in your purchase order number in the indicated field. The installer should also fill in his email address for emailed return of the installation codes. From the "Package List" section of the form, select the TR-TECH software and required drivers, selecting each from the list and clicking the [Add to Order] button. To request the license for the base TreeTech software, select TR-TECH. To request a license for using serial communications between TreeTech and Network-8000 GCMs or DMS panels, select IOS-SRL. To request a license for using Ethernet communications between TreeTech and Network-8000 GCM-86xxx series panels, select IOS-NW8-ETH. To request a license for using Ethernet communications between TreeTech and DMS-3500 panels, select IOS-DMS-ETH.  NOTE: At least one communications driver must be selected. After completing the form, click the [Accept Order] button and save the order form to a text file.  Click the [Done] button to save the requested license options to the computer and click the [Done] button on the WIB Purchase screen to exit the program. Email the saved license form to IASeries.WIB_Order@schneider-electric.com.  The requested unlock codes will be emailed to the address specified on the form after the order has been entered and processed.  Allow two business days for processing.  While waiting for the unlock codes, the software can be used with the automatically installed demo mode license.  The demo mode license is valid for 30 days from the time the first WIB software product is installed on the computer. When the purchased license unlock codes have been received, they must be installed using the [Unlock] function of the "Purchase WIBs" program.  After opening the program and  clicking the [Unlock] button, select one of the requested license products, enter the corresponding unlock code and click [Generate License].  This process licenses the software onto the computer and removes the product from the displayed list.  Repeat this process for each additional product license shown on the screen.  Each provided unlock code will be used only once.

Issue The G3 icon for "Start, All Programs, Enterprise Network Server 3.x., Install Platform Daemon" is missing. How to locate and run the file? Environment I/A Series G3 Workbench, all builds Cause The I/A Series G3 icons that were automatically installed in the pc Start menu are missing. Resolution 1. On the drive where I/A Series G3 Niagara is installed, go to C:\niagara\niagara-3.n.nn\bin\plat.exe installdaemon. 2. Double click on the file plat.exe to run the executable file.  

Issue What are the approved cable types for a BACnet/MSTP trunk with MNB controllers?  Environment All MNB controllers Cause This is a new installation where existing trunk wiring is not available. Resolution Cable types are listed in the MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360). Table 1.20 on page 30 lists the recommended BACnet MS/TP Cable Types:

Issue Error when attempting to use LON Tunneling, "Service unavailable, Another application already connected in remote station". This message indicates that another user is already connected to the device through Lon Tunneling. Environment I/A Series (Niagara version 522 or higher) R2 UNC with LON Tunneling Lon Tunnel client Cause The general cause is that the computer disconnected the LON connection before closing the LON Tunnel. There are a number of different reasons this can happen when you have the LON tunnel connection open: Laptop goes into sleep mode while tunnel is connected. Disconnecting laptop from Ethernet network before closing WorkPlace Tech Losing the network connection Shutting down the laptop without exiting from WorkPlace Tech. Resolution This problem can be corrected without having to reboot the UNC by accessing the UNC Webserver Status Summary screen and clicking disconnect on the VLON connection.  The procedure is as follows: Access the UNC using your web browser and the following command: http://<ipaddress>/prism/webserver     A screen similar to the following will be displayed:   In the "All Threads" section, locate the line that shows the Uri "/vloncomm0/Vlon" and click the "Disconnect" link button.  This will cause the Vlon connection to be forcibly closed.  Once the connection has been closed, the LON Tunnel connection will again become available for a client connection.

Issue Niagara R2 is installed on a computer but the HostId is not known.  Aside from viewing the details of the license.properties file, how can the HostId be determined? Environment Niagara R2 Cause No access to the license.properties file Resolution Open the Niagara Console (located in the Program Group), and type the following: nre -hostid This will display the HostId to the screen (see the screenshot below) The  nre command can also display other information.  The screenshot below shows the other options.

Issue There are six object types when adding to a Network 8000 network in the Equipment Database.  When should each type be selected? Environment TreeTech 3.x Network 8000 GCM and LNC Cause Each type provides the necessary support for the different block types available in the different Network 8000 GCMs and LNC.  An upload will fail if block support is not available because the wrong object was chosen. Resolution Select the correct object type to match the field-installed Network 8000 panel. ASDGCM4  - A GCM-84000 series using revision 4.x firmware and configured with an ASD bus ASDGCM5 - A GCM-84000 or GCM-86000 series using 5.x firmware and configured with an ASD bus GCM4 - A GCM-84000 series using 4.x firmware and configured with GCS modules GCM5 - A GCM-84000 series using 5.x firmware and configured with GCS modules GIM 2100 - A Global Integration Module for System 2100 SIM GCM - same as a LNC-100

Issue Receive an error when using the Gcm Device Manager  to add an LCM to a G3 (Niagara) station running the tacGcm driver: Environment ENC-520 licensed for the tacGcm driver. Network 8000 LCM, on LCM bus under a GCM Network 8000 GCM with LCM bus Cause Although the pull-down menu for the Gcm Device Manager has  entries for "New" LCM and stand-alone LCM, selecting them results in the error. Resolution Add the LcmDevice manually: Open the tacGcm palette. Expand the Devices folder and copy an LcmDevice. Paste the LcmDevice into an existing GcmDevice. Configure the LcmDevice object to match the physical LCM controller  by setting the Panel and Network Number. In the example shown below, the Panel = 11 (as set by the DIP switch on LCM), and Network Number =1.

Issue Is there a way through Niagara G3 WorkBench to log into multiple ENC/ENS stations without being re-prompted for the Username and Password for each station?  Environment Niagara G3 (version 3.3 or higher), ENC, ENS Cause Is there a way through Niagara G3 WorkBench to log into multiple ENS/ENS stations without being re-prompted for the Username and Password for each station? Resolution Starting in AX-3.3, a multi-station “realms” feature was added. This feature allows a Workbench user to open one station (fox), then have Workbench access to other stations, without re-prompting for credentials. The following must be performed in each station, where each station must have the same “realm” name: Open the property sheet of the root-level Config component in the station. In the “Sys Info” property, click the Facets control (>>) for the Config Facets editor. The Config Facets editor appears  Add a key named “realms” of type String, with the string value (whatever desired) for the realm name. To do this in the Config Facets dialog: Click the “+” button. Under Key, select “realms” from the dropdown menu. Under Type, be sure that String is selected. Click in the “Value” field and type the name of the realm. Note this realm value has no literal meaning, but must be the same for all stations. Click OK to add the facet. See figure below for an example of realm "shazam" being added Repeat this procedure for every station that’s part of the single sign-on realm. Note: This feature requires that the user has an account (with same credentials) on each station in the realm.  Otherwise, the user will still be prompted to login. For additional information, reference the section, “WorkBench single sign-on (SSO) realm”, located in chapter 9 of the Niagara AX-3.x User Guide. 

Issue When tunneling through a UNC (R2) or ENC (G3) to an ASD bus with XPSI, set the baud rate to 1200 to eliminate communications timeout errors. Environment PSI/XPSI software, any version. I/A Series UNC (R2) or ENC(G3) with an ASD bus connected. All versions. Serial tunnel client, R2 or G3. Cause Delays introduced by the Internet between the PSI/XPSI computer and the remote tunnel client can result in communications timeout errors. Setting the PSI/XPSI baud rate = 1200 can help minimize or eliminate the effects of these delays. Resolution Set the baud rate of PSI/XPSI to 1200, per the TAC I/A Series Enhanced ASD Driver Engineering Guide, F-27429, Chapter 5, Table 5.1, "Site Setup Configuration", excerpt below:

Issue Some connecting lines may not be drawn attached to the left side of control objects.  This may occur when using a new version of the WorkPlace Tech Tool to display an application created with an older version,  For example: Environment WorkPlace Tech Tool 5.7.x or 5.8.x Cause Line and Object display coordinate round-off errors between various versions of Visio. NOTE: This does not affect the processing of the application in the WorkPlace Tech Tool because the real logical connections are stored in the application database. Resolution To resolve this "drawing" issue, it is necessary to move the control object slightly.  When the object is redrawn, the connecting line coordinates are recalculated and will redisplay properly. If many connecting lines exhibit this issue. you can select all objects on the drawing (use Edit / Select All or Find / Select All menu selection or the keystroke shortcut, Ctrl-A) then move the selected objects a very small amount.  The objects will then be redisplayed with the lines connected.  An easy way to move all selected objects is to use the arrow keys, pressing the Right-Arrow key, wait for the drawing to update, then move everything back by pressing the Left-Arrow key.  Once the drawing has updated, you can click anywhere within the drawing to unselect everything.

Issue The issue occurs when the instance Number is changed.  After the instance number is changed the MNB-1000 will look normal in the current WorkPlace Commissioning Tool (WPCT) session, but the next time WPCT is opened the MNB-1000 will either be unable to be found or the controller icon will be displayed as a gray rectangle with a question mark in it.   Selecting Extended Data will cause a loss of communications with the controller as signified by red exclamation point (!). Environment Any MNB-1000 with 1.510 firmware Cause This is a firmware issue present in 1.510 only. Resolution Cycling power to the MNB-1000 after changing the instance Number will correct the issue. Once communications is established upgrade the MNB-1000 firmware version 1.511 to prevent the possibility of this happening in the future.

Issue During initial setup, the incorrect ethernet IP address or subnet mask was entered.  Now when rebooting the UNC, I cannot reconnect to it using the I/A Series R2 Admin Tool.  How can the incorrect information be changed? Environment UNC-520 or UNC-410 Cause Network connectivity cannot be established if the IP address or subnet mask was entered incorrectly.  Likewise, if an invalid subnet mask is entered, the UNC may not boot completely (or at all). Resolution The following information is provided in more detail in the section "Determining Network Settings", subsection "JACE-4/5" of chapter 3 of the Niagara Networking & Connectivity Guide.  This document is provided with and installed with the I/A Series (Niagara) R2 software. Required hardware: Serial Cable Terminal Emulator software on computer (such as "Hyperterminal" or "Putty") Procedure: Configure the Terminal Emulator to run at 9600 baud, 8 bits, one stop bit, no parity, hardware flow control Jumper the upper two pins of the Console "MODE" connector,  located in the upper right corner of the UNC-520 circuit board (See photo at right). Connect the terminal emulator via a UNCC-405 serial cable to port COM1 on the UNC and power-cycle the UNC. Wait for the UNC to complete its bootup process (do not break out of the boot process). Check the displayed information to determine what IP address and subnet mask was entered. Power cycle the UNC and when the console display shows "Press any key to stop auto-boot"., press the space bar. Follow the procedure in the section "Determining Network Settings", subsection "JACE-4/5" of Chapter 3 of the Niagara Networking and Connectivity Guide for the procedure to step through the settings changing them if necessary.  Please note that the figure 3-8 may not include all lines of information shown for your UNC. If the serial console is showing any errors after you have verified the IP address / Subnet mask entries, please provide product support with a text copy of the serial console output showing the error messages.

Issue Temperature readings from an I/A Series Micronet LON controller is displayed as a Fahrenheit value in an I/A Series R2 UNC station The default units of measure has already been set to Metric in the WorkPlace Tech application Environment I/A Series R2 Cause SNVTs defined as a temperature is converted to Fahrenheit by the LonWorksService in the UNC station. Resolution The temperatureUnits property needs to be changed to the desired unit. Here are the steps to accomplish this: Right-click on the LonWorksService in the UNC station and go to Properties. Go to the 'General' > 'Config' tab. Change the temperatureUnits to 'celsius'. Click 'Apply'.   The definition of the temperatureUnits property is: Temperature units are the only units that Niagara R2 allows you to modify. The LonTalk protocol measures all values in SI units, therefore, temperatures are measured in degrees Celsius. With this property set to Celsius, no temperature conversion is performed—the value coming off of the wire is assumed to be in degrees C. If set to Fahrenheit, any SNVT defined as a temperature is converted.

Issue A controller with only 2 available outputs is being used to control a 3 stage device. Environment Three stage device control where lower stages must remain active. Cause Hardware or space limitations may prevent there from being enough outputs to control a three stage device. Resolution Two controller outputs in conjunction with a DPDT (dual pole, dual throw) relay can be configured to control a three stage device. This will allow you to activate stage 1, stages 1 and 2 or all three stages by activating either one or both of the controller outputs. An example of when this might be used is to control three stages of heat or a three stage fan. A standard "ice cube" type relay can be used (IDEC RH2B or similar) and should be wired as shown in the diagram below.   The controller should be programmed to activate only output 1 for stage 1, activate only output 2 for stages 1 and 2 and finally to activate both outputs for stages 1, 2 and 3. Note that certain application specific controllers may not allow the outputs to be configured in the way described above and thus cannot take advantage of this setup.

Issue On an FTT-10 trunk  segment wired in a Loop Topology, where should the LON-TERM1 terminator be installed? The Loop Topology is a subset of the Free Topology. Environment LonWorks FTT-10 network including I/A Series MNL controllers wired in a Loop Topology. Cause Installation detail Resolution In a Free Topology segment, only one termination (LON-TERM1) is required, and may be placed anywhere on the free topology segment.