Building Automation Knowledge Base

Issue Remote I/O Module (RIO) programming: Can I/O tags (outputs) from two different RIO modules be connected to Dual-output objects? Environment MNB-1000 MNB-1000-15 Cause The object error will occur "Outputs must connect to the same remote module". Resolution Details: Dual-output objects are objects with two addressable outputs. There are three such objects: Momentary Start/Stop Object, Floating Actuator Object and Floating Actuator Priority Object. When connecting dual-output objects to I/O tags on an MNB-1000 application drawing where MNB-1000-15 remote I/O modules have been configured, be sure to connect both outputs to the same set of I/O, whether that be the MNB-1000 controller’s onboard I/O or a particular MNB-1000-15 module’s I/O. For more information, see the latest WorkPlace Tech Tool Engineering Guide Supplement (F-27356).

Issue If a MNB-1000 application contains R-I/O programming, can it be successfully downloaded without the actual R-I/O hardware connected and communicating? Environment MNB-1000 Remote I/O Module Cause Communication lost between MNB-1000 and Remote I/O module  Resolution Yes. The R-I/O modules (MNB-1000-15) are not controllers and do not have control applications within them. All processing is done at the MNB-1000 (except fallback). Lack of R-I/O or R-I/O communications or loss of R-I/O communications has no effect on or during a download. In fact, the MNB-1000 cannot communicate with or even determine if R-I/O exists until an application configured for R-I/O has been downloaded at least once. This is because the R-I/O configuration information is stored in the application and the MNB-1000 must rely on the application to know if R I/O modules even exist.

Issue How can the instance number be changed in a Viconics BACnet thermostat? Environment Viconics BACnet thermostat Cause No visible button to enter configuration Resolution The ID or instance number is 7x000(x=series model)+ Mac address. The Mac address can be defined from the front of the unit. Press the white "config" button in the lower right hand corner of the circuit board once. Then keep hitting "no" until "Com Addr" is displayed and hit yes. Use up/down keys to set the address. For units with no white "config" button: VT7200 series press and hold the button (OVERRIDE) for 8 seconds VT7300 series press and hold the middle button (°C/F or OVERRIDE) for 8 seconds. VT7600 series press and hold the button (MENU) for 8 seconds Then press no until "com addr" displays, then press yes and use the up/down button to change it.

Issue The notification Servlet does not work in the Enterprise Server station Environment Enterprise Server station Cause NotificationServlet settings and SWID to the output object. Resolution Double check to make sure the SWID to the output object is correct. Set the NotificationServlet - properties - config - "activeCommand" to emergencyActive or manualActive and the "inactiveCommand" to emergencyInactive or manualInactive. The "activeInactiveText" for the BO can be modified to make that more meaningful.   Reboot the UNC to make these changes take effect.

Issue Unable to use the "Put" command from the DB Admin tab of the Admin Tool in Workplace Pro.  Cannot select file buttons. Environment Workplace Pro UNC series Cause UNC must be in idle. Resolution The "Put" command can only be used to import a database to an "idle" UNC. To idle a running UNC, uncheck it's "Auto Start" box and reboot.

Issue In Niagara R2, device objects are not updating. Bundles were used to speed the linking to graphics. Environment Niagara R2 Cause The device objects are in bundles. Resolution Only native Niagara objects should be placed in bundles. This includes the Niagara AO, BO, AI, BI, and logic (if desired). Due to the nature of bundles they execute at their own rate. This interferes with the normal execution of BACnet, LON, GCM, ASD, DMS, MS and other hardware objects. For additional information on the use of bundles refer to The Standard Reference Manual pages 7-14 through 7-21 and pages 5-1 through 5-6 of the Web Solutions Guide.

Issue Does Windows XP Service Pack 3 (SP3) cause a problem with SIGNAL XP? Environment SIGNAL XP computer Service Pack 3 Service Pack 2 Cause Any known issues with the SP3 helps if updating is necessary. Resolution The impact of SP3 on SIGNAL XP is not known. SIGNAL XP has been field-tested with Windows XP Service Pack 2 and the only issue identified was recognition of the Security Plug (see TA06-03). No other anomalies have been observed. There are no plans to validate SIGNAL XP with this new service pack. It is recommended that all SIGNAL XP computers maintain Windows XP at service pack 2.

Issue Without a Niagara R2 UNC, Enterprise Server, or MNB-1000 on a BACnet/MSTP network, can the MNB controllers communicate reliably peer-to-peer (i.e. sharing outside air temperature between multiple MNB-300 controllers)? Environment MNB-300 controllers Cause Some site would like to avoid the use of Niagara R2 UNC, Enterprise Server, or MNB-1000. Resolution Yes. The implementation of COV subscriptions in the MNB controller line, with the 1.4x (or greater) firmware, allows for every MNB controller to function as both a COV server and a COV client. This allows peer-to-peer communications between all MNB controller models. To create peer-to-peer links, review Chapter 4 in the WorkPlace Commissioning Tool and Flow Balance Users Guide (F-27358) that details how to use Link Builder.

Issue How can an existing Enterprise Server station be configured to run the Vykon Alarm Service (VAS)? Environment Enterprise Server Vykon Alarm Service Cause For Enterprise Server to support VAS, check the Enterprise Server shipped date to determine if part number IA-ENT-AS is required. Resolution An Enterprise Server station is already licensed to support VAS. It also includes support for two VAS clients. If additional clients are required, order part number IA-ENT-AS-C for each additional client. If the Enterprise Server was shipped before November 1, 2002, it did not include support for VAS. It must be ordered separately using part number IA-ENT-AS (which will also include support for two VAS clients). The Enterprise Server must also be upgraded to, at minimum, build r2.301.330. For more information, review R2 Worksheet (xlt) tab "ENT SVR Estimator" for additional notes on various part numbers. VAS software can be downloaded from The Exchange. Download VAS v2.4 CD Image.zip and VasPatch.zip. Unzip the CD Image for the Installation Instruction Manual. The VasPatch is installed last.

Issue A Liebert SiteLink panel is not communicating with the Niagara R2 UNC using BACnet/MSTP. Environment Liebert SiteLink panel Niagara R2 UNC BACnet/MSTP communication Cause Termination resistors Resolution When connecting a dedicated Liebert SiteLink module MSTP segment to the UNC, the EIA-485 trunk typically requires 120-ohm termination resistors at each end. Field testing has determined for Liebert Sitelink-4 and –12 modules that the termination resistors have a negative affect on communication even at a low baud rate of 9600. Removing the termination resistors resolved the communication issues.

Issue How can two MicroNet 2000 MN-FLO or MN-FLO3T VAV controllers share data? Environment MicroNet 2000 MN-FLO / MN-FLO3T Cause Sharing data between the devices require MicroNet Integrator. Resolution Sharing data between two (or more) MicroNet controllers requires a MicroNet Integrator. Even if the integrator is not communicating to a GCM/DMS, it is still required to facilitate data sharing on the U-bus. The only system configuration, not involving an integrator, is stand-alone mode. Peer-to-peer data sharing is not possible. See the MicroNet 2000 Family Fundamentals Guide (F-25711) and review the chapter on System Configurations.

Issue With Niagara R2 Status Type objects, what colors are used to represent their different real-time conditions? Environment Niagara R2 Cause Configure the status indicator to turn a different color of an off-normal condition. Resolution Status-variable type objects contain a 'statusInput' (sIn) and 'statusOutput' (sOut) property. These objects are: BooleanStatusType floatStatusType integerStatusType The sOut will change to a different color for the following conditions: orange (dark yellow) -> fault yellow -> down red -> inAlarm cyan (light blue) -> OutOfService magenta (purple) -> overridden clear (grey) -> normal These are the background colors as the real-time text remains black in all cases. These are also the default colors that can be changed by modifying the statusColors.properties file.

Issue What is the preferred architecture with MNB MSTP controllers when an installation has a MNB-1000 and a Niagara R2 UNC?  Hang the controllers on the MSTP bus of the MNB-1000 or the UNC? Environment MNB-1000 Niagara R2 UNC MNB Controllers Cause Prevent any performance degradation by hooking up the MNB controllers in the correct location. Resolution Either way is OK.  If the MNB controllers are on the MSTP trunk under the MNB-1000, then the MNB-1000 acts as a router, and communication is a little slower than if they were directly connected to the UNC.

Issue Can the profile in a MNL standard LonMark controller be changed in the field?  For example, can a MNL-20RH3 (heat pump profile) be changed to a MNL-20RS3 (satellite 3 profile)? Environment MNL standard LonMark controllers Cause The LonMark Profile is stored in the controller's firmware. Resolution No, the LonMark Profile cannot be modified.

Issue Connecting lines in WorkPlace Tech stay red even when snapped to an object. Product Line TAC IA Series Environment WorkPlace Tech Cause Verify that the Visio "Snap" option has been turned on. Resolution The following procedure can be used to verify this setting. Open the Workplace Tech Tool and open an application file. From the "Tools" menu, select "Snap & Glue" In the displayed window, verify that the following items are checked: Snap (under Currently Active) Glue (under Currently Active) Connecting Points (under Snap to) Connecting Points (under (Glue to) Click the [OK] button on the "Snap & Glue" window to save the changes and close the window. Additional "Snap to" options are normally selected by default. These options should remain selected for consistency of operation. It is suggested, to prevent inadvertent changes to these settings, that the "Snap & Glue" toolbar NOT be turned on.

Issue Can third party BACnet/MSTP devices be placed under a MNB-1000? Environment MNB-1000 Third party BACnet/MSTP Cause MNB-1000 documentation doesn't show integration with third party BACnet/MSTP. Resolution Due to the diversity, volume, and continuous revisions to third party BACnet/MSTP devices, none are tested with the MNB controller line.  If the devices are BACnet Testing Labs (BTL) compliant, they should function.  However, they will not be supported.  The use of third party devices will be at your own risk. Refer to BACnet Wiring, Networking, and Best Practices Guide (F-27360) for additional configuration recommendations

Issue For the MicroNet sensors MN-Sx and MN-SxHT, what is the drift factor per year? Environment MN-Sx MN-SxHT MicroNet Controllers Cause There is slight temperature drift with MicroNet Sensors. Resolution The non-humidity units (MN-Sx) use a glass encapsulated thermistor sensor that has a maximum drift of .022ºC in the first 30,000 hours (about 3.5 years) and is basically stable after that. The electronics uses precision resistors as references that are powered at less than 1/100 rated power. Using the shelf life specification for drift of 100PPM / year for the reference resistors would add another .022ºC / year. A conservative number of 0.03ºC / year would cover it. The humidity units (MN-SxHT) have a solid-state sensor with a humidity drift of 0.5%RH / year and a temperature drift of 0.04ºC / year maximum. The sensing chip communicates digitally with a microcontroller so there is no electronics related error.

Issue How can a remote BACnet/IP network be accessed using the WorkPlace Commissioning Tool (WPCT)? Environment BACnet/IP network WorkPlace Commissioning Tool (WPCT) Cause Remote connectivity is needed to access a BACnet device that exists on an outside network where WPCT resides. Resolution When WPCT starts, it sends out a "whoIs" (broadcast) message. The responding devices send the reply ("iAm") using its IP address. If the responding device is on a private IP network that is using NAT or Port Forwarding to access the Internet, it is this private IP address that is populated in the "iAm" response. After the response, WPCT starts using directed messages using the address it received from the responding device. Private IP addresses cannot be routed through the public Internet. Therefore, NAT or Port Forwarding cannot be used to access remote BACnet/IP networks using WPCT. There are two ways around this issue: Use a public IP address in the internal BACnet network Use a VPN to access the network For more details, consult the I/A Series Micronet BACnet Wiring, Networking, and Best Practices Guide (F-27360).

Issue The Network 8000 GCM-84000 series has two RS-232 communication ports. Which one is PORT1 and which is PORT2? Environment Network 8000 GCM-84000 series Cause Use the RS-232 ports to connect personal computer-based graphical operator interfaces, VT-100 class terminals, and/or auto-dial/auto-answer modems for remote telecommunications. Dual RS-232 ports can be used to connect personal computer-based graphical  operator interfaces, VT-100 class terminals, and/or auto-dial/auto-answer modems for  remote telecommunications. Dual RS-232 ports can be used to connect personal computer-based graphical  operator interfaces, VT-100 class terminals, and/or auto-dial/auto-answer modems for  remote telecommunications. Dual RS-232 ports can be used to connect personal computer-based graphical  operator interfaces, VT-100 class terminals, and/or auto-dial/auto-answer modems for  remote telecommunications. Resolution PORT1 is the top port and PORT2 is the bottom port. PORT2 is designed with better data buffering and should be the first choice when connecting a computer to the GCM for any type of data exchange. See the Network 8000 Service & Troubleshooting Manual (F-23024, page 88).

Issue Is the new PSI / XPSI rev 4.1 compatible with Windows XP and Vista? Environment PSI / XPSI rev 4.1 Windows XP and Vista Cause Install PSI / XPSI rev 4.1 in a Windows XP or Vista Operating System (OS) Resolution The new PSI / XPSI rev 4.1 is compatible with Windows XP and Vista. Download PSI rev 4.1 from The Exchange. The zip file includes an installer and a READ.ME file that includes Release Notes and Installation Instructions. Note that the Patton Electronics RS-232 / RS-485 converter that has been widely used with the earlier versions of PSI (3.13) will not work with the new PSI / XPSI rev 4.1.  The B&B Electronics model USOPTL4 USB converter has been successfully tested with PSI / XPSI rev 4.1. Other recommended converters are listed in the Release Notes.