Building Automation Knowledge Base

Issue NXT will not communicate using RS-485 port 3 Environment R2/AX Niagara Cause Incorrect documentation of communication port number and RS-485 wiring diagram Resolution New document is available with correct comport number 4 and RS-485 wiring diagram.  To download a copy click on link T-NXT-MtgWiring Guide

Issue A GCM / LCM stops working and displays the error message "Insufficient System RAM".  It no longer responds to information requests via the front panel keyboard/display nor via XPSI software connected on either of the available serial ports. A power cycle restores functionality but only for a limited amount of time (ie: hours or days). Environment Network 8000 GCM-84000 series GCM-86000 series LCM-84000 series LCM-85000 series LCM-88000 series Cause Free system ram drops below minimum requirements: Any GCM with sys ram below 18k Any LCM with sys ram below 10k Resolution The amount of free system ram must be kept above minimum requirements. Use Tech Bulletin 95-33 for troubleshooting the GCM / LCM.  It is a comprehensive guide providing both hardware and software suggestions that will increase free system ram.

Issue Significant changes and improvements were introduced with firmware revision 11.2P, including a streamlined "Flash clear" procedure. For Ethernet NIMs with firmware revisions prior to 11.2P, the procedure was documented in Technical Bulletin 99-56 (see below). The procedure in bulletin 99-56 was a revision of the procedure in the original NIM Networking and Configuration Practices manual, F-25955, which is no longer available. The current version of the manual, F-25955-4, applies only to NIMs with firmware  revisions 11.2P and 11.2T. Environment Ethernet NIM for network 8000; GCM-ETH-001 with firmware revision prior to 11.2P. Cause "Flash clear" procedure was changed in firmware revision 11.2P Resolution Follow the "Flash clear" procedure per Technical Bulletin 99-56.

Issue Customer wants to archive the BACnet controller backup images created through the Backup function of the WorkPlace Commissioning Tool. Environment WorkPlace Tech Tool software version 5.7.x or newer Windows XP Professional or Windows 7 Professional Cause The actual location of the Backup folder has changed between Windows XP and Windows 7 Resolution If the computer operating system is Windows XP, the specified backup project folder is in the following location: c:\Documents and Settings\All Users\Application Data\WorkPlace Tech\Backups If the computer operating system is Windows 7, the specified backup project folder is in the following location: c:\ProgramData\WorkPlace Tech\Backups Further information on the contents of the backup project folder can be found in the Release Notes documentation for WorkPlace Tech Tool 5.7.2, F-27526-2, pages 10-13.  Please note that the full file path shown in this document is based on the use of the Windows XP operating system.

Issue The FDA requires Building Automation systems to meet their standards which are outlined in Chapter 21 CFR and FDA Part 11. Environment Vista I/NET Andover Continuum TAC I/A-series Satchwell Sigma Cause Finding documentation on Schneider Electric Building Automation Systems which comply to The Food and Drug Administration rules. Resolution Vista 21CFRPart11 support in TAC Vista 5.pdf FL-VISTA-REGIND-A4 mod RO.pdf I/NET - currently unavailable Andover Continuum With the addition of the 21 CFR Part 11 compliance pack, Continuum can meets these requirements. Satchwell Sigma SoftwareOverview.pdf Advanced Security Module.pdf Note: Validation to 21CFR Part 11 can only be performed on whole operational systems and as such, a sub-system comprising the Satchwell Sigma building management system cannot be validated in it own right. Satchwell Sigma would normally be validated as part of a whole operational system. TAC I/A Series - currently unavailable

Issue The IP address can be entered into a UNC-410 using the Admin Tool but after rebooting or power cycling the device, the IP address is reset back to the factory default. Environment I/A Series (Niagara) R2 UNC-410-2(-N) with serial number greater than 36218 Cause The newer UNC hardware manages stored OS configuration data in a different manner than the older UNC-410 devices.  Because of this change, the factory default operating system has the capability to read, but not permanently change the device IP address. Resolution You must use the Admin Tool Installation Wizard to install the r2.301.527 (or newer) version of the OS and NRE (system software) before you can save any new Ethernet address information to the UNC. Follow the procedure in the UNC-410 installation manual (F-27391) section "Upgrade, License and Configure the Host" to install the OS and NRE system software and to configure the required software modules.  Click here to see the referenced page of the manual.

Issue Is there a wiring diagram available for the HOA BACnet Series Digital Output Override Cards for IA BACnet Controllers? Environment IA, MNB-300, MNB-1000, MNB-1000-15, BCS-HOA-3-BACNET, BCS-HOA-4-BACNET Cause Is there a wiring diagram available for the HOA BACnet Series Digital Output Override Cards for IA BACnet Controllers? Resolution A wiring diagram on the HOA card can be viewed in the attached document.

Issue Attempting to make programming changes to a Niagara R2 UNC-510 station.  After the changes are done, performing a backup fails.  The "save runtime db" does not complete. Environment Niagara R2 UNC-500, UNC-510 Cause The backup process (save runtime db command) requires free memory on the smart media card.  There must be enough free memory to (at least) equal the size of the .sns file. The smart media card (listed as '/sm' on the Summary tab of the Admin Tool) holds the station database (.sns file), graphic images, and other files accessible using the Remote Library. The table below summarizes flash drive volumes and usages by model.  Note that a jace in the table is a UNC. Refer to the Niagara Capacities Engineering Notes for more information. Resolution Access the Remote Library via Workplace Pro and delete unnecessary files.  As files are removed, monitor the Free File Space on the Summary tab in Admin Tool.  When the '/sm' increases a few kilobytes, try performing a 'save runtime db'.  If the command is successful, then the free file space created is adequate.  If it does not, repeat steps 2 and 3 until it is.

Issue A MicroZone II (MZ2) indicates "cold reset" or "warm reset". What do these error messages mean? Environment MicroZone II (MZ2) controller Cause The error messages are in response to interruptions to the controller's  24 Vac power. Resolution For a detailed explanation of the "cold reset" and "warm reset" messages, see the MicroZone II Programmer's Manual, F-23118, "System Resets". Click here  to see an excerpt from the manual.

Issue In a new installation, the ProView display (never configured previously) is powered and wired to the LON trunk back to a UNC-520.  In the station's LonWorks Service, a Find completes but the ProView display does not appear. Environment Niagara R2 version 529 or newer ProView Cause "New" ProView displays are somewhat unpredictable when added to a Niagara R2 station for the first time. Once it has been commissioned and programmed, its behavior improves. Resolution Add the appropriate shadow object from the 'distech' jar file (Ecdis210) to a container under the lonTrunk. The programID for the ProView display is:  90:0:83:32:b:84:4:15 In the LonWorks Service - Lon Device Manager, highlight the just-added Ecdis210 object and Commission. Use the SrvPin method to learn the neuronID (ProView display's service pin is located on the bottom to the left). Once the commission process complete, ProView is now available for programming.

Issue How to configure a Niagara R2 UNC as a LON Node  Environment Niagara R2 Cause How to configure a Niagara R2 UNC as a LON Node  Resolution Steps to configure UNC as LON Node

Issue Niagara G3 (NiagaraAx) Open NiCS (Niagara Compatibility Statement) Environment Niagara G3 (NiagaraAx) Cause NiCS attributes: Niagara G3 (NiagaraAx) licenses has brandId="TAC". A station's ability to accept NiagaraAx data from another NiagaraAx station depends on the accept.station.in="*" field in its license. A station's ability to share NiagaraAx data with another NiagaraAx station depend on the accept.station.out="*" field in its license. A station's ability to allow a copy of WorkBench to connect to it and engineer the station depends on the accept.wb.in="*" field in its license. A copy of WorkBench's ability to connect to a NiagaraAx station to engineer it depends on the accept.wb.out="*" field in its license. (Where "*" is the brandId) 'Open' licenses may be required when there is a need to: Allow sharing of a station's NiagaraAx data to another station which has a different brandId in its license. Accept NiagaraAx data from another station which has a different brandId in its license. Allow a WorkBench connection from a copy of WorkBench that has a different brandId in its license. Allow a copy of WorkBench to connect to a station which has a different brandId in its license. Resolution Niagara G3 open NiCS licenses have the following: “accept.station.in="*”; “accept.station.out="*”and “accept.wb.in="*”and “accept.wb.out="*”. The "*" is a wildcard designation to allow all brandIds. You can specify new licenses to have open NiCS by selecting the 'Request open NiCS (Niagara Compatibility Statement)' checkbox in the I/A Series G3 license request forms. You will need to purchase the part IA-LIC-CHG for each existing Niagara G3 that needs to have an open NiCS. 

Issue How many controllers can be connected to an ASD bus before a repeater is required? Environment Global controller with an ASD bus connected (GCM, UNC, ENC, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, SIM-YORK) ASD controller (LIM-1,MicroFlo II, MicroZone II, MN-ASDI integrator, PEM-1) Cause Requirements for ASD bus installation. Resolution A maximum of 32 nodes are allowed for each ASD bus segment.  Each controller and repeater count as one node, so a bus segment with a master (GCM, UNC, etc.) and a repeater can have 30 other nodes on it ( MZII, MN-ASDI, etc.) For details, See the Network 8000 Hardware Installation Practices manual, F-23061-1, "Network & Communication Wiring", "Repeaters - RS-485".

Issue How to set an LNC-100 back to factory-default settings. This will erase all block programming and device configuration. Environment Network 8000 LNC-100 and related controllers based on the GCM-861X0 series platform, including the GCM-86110, GCM-86120, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK Cause Sometimes it is necessary to manually clear the controller EEPROM in order to reload a database. Resolution Follow the steps below: Backup the controller database. Clear the controller's EEPROM. This is accomplished by pushing the reset button and the EE CLR button and holding both for at least 20 seconds before releasing. The reset process is complete when the top two red LEDs on the right edge of the controller begin blinking in their normal sequence (second LED blinks twice as fast as top LED). This process will clear the user programmable memory (including all block programming), returning the controller to its original factory condition. This step is important as it insures there will be no conflict between the new revisions firmware and the older version. The procedure above is excerpted from Technical Bulletin 99-27 , steps 1 and 2.

Issue What issues, if any, are there to replacing Workplace Tech 5.7.7 with 5.7.6 on a Windows XP computer? Environment Workplace Tech 5.7.7 and 5.7.6 Cause none Resolution Workplace Tech version 5.7.7 comes with new firmware for the MNB-1000.  It is better to use version 5.7.7 with any MNB-1000 controllers installed with the new firmware.  This is especially true on job sites adhering to GSA guidelines. If the computer is only used with MNB-1000 controllers running previous firmware releases, then re-installing version 5.7.6 won't create any issues. Review the release notes below for more details. Release Notes - WorkPlace Tech 5.7.7

Issue When trying to run Workplace Tech 4.0 for the first time, it may not start successfully, and an error message will be displayed: "Microsoft Visual C++ Runtime Library, Runtime Error!" Environment Workplace Tech version 4.0 Visio 2002, SR1 Windows XP Professional, Service Packs 1-3 Windows 2000 Professional, Service Pack 4 Cause The error is typically caused by not initializing Visio 2002 before running WPT 4.0 for the first time. Resolution See Technical Bulletin TB04-02, which details the issue and resolution.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue I/A Series R2 Enterprise Server and I/A Series G3 Enterprise Network Server redundancy solution Environment I/A Series R2 and I/A Series G3 Cause Continuous uptime is required for I/A Series system and data. Resolution The recommended software for I/A Series redundancy is from Stratus Technologies (http://www.stratus.com/). Contact your local Stratus Technologies office or distributor / partner for details. Also refer TVDA document 'everRun Mx with SE Building Management Systems'.   Frequently asked questions: What does Stratus Technologies solutions do? It delivers simple, affordable, continuous uptime for any Windows application running on unmodified, industry-standard server hardware. This high availability solution protects applications, data, and operating systems from faults, failures, and dropped network connections. How does it work? Stratus software synchronizes two standard Windows servers and creates a virtual application environment that runs on both of them simultaneously. If one server fails, the Windows application continues to operate uninterrupted using the other server with no failover, transaction rollback, or other complex procedure. Are there any special I/A Series licensing requirements? The Stratus solution requires a single I/A Series license only. Only one copy of the Enterprise Server / Enterprise Network Server is required. There are no special properties or license requirements. Which Marathon product should be used? All Stratus products can be used. The particular Stratus product will be determined by the end-user hardware and performance requirements. Are there any special properties that need to be set up in the Enterprise Server / Enterprise Network Server when using the Stratus product? The installation of I/A Series (R2 or G3) is no different than installing the product on a standard Microsoft Windows platform. Keep in mind; if the Microsoft Windows platform is running IIS, then either IIS or the Enterprise Server / Enterprise Network Server will have to run on something other than port 80. Both applications cannot utilize the same port.

Issue There are no existing objects in Niagara G3 that can split a 16-bit Modbus register into two 8-bit values with one representing the high byte (bits 8-15) and another the low byte (bits 0-7). Environment Niagara G3 all versions Cause Modbus integration of a 3rd-party product using 16-bit values which must be split into two 8-bit values. Resolution A program object is available below that will achieve this requirement.  The output of this object generates two 8-bit integer values and two string values for use with logic programming and display purposes.  Text file of program code

Issue Attempting to commission and bind to a Trane lon controller (object name:  Lcir & programID 80:00:CF:07:00:0A:04:05, 80:00:2A:55:00:03:04:0C, and Lcir-DAC 80:00:2A:56:0A:03:04:04. Both processes fail.  An xif file was created directly from the controller using Nodeutil. Click here to view the xif file. Environment Niagara G3 version 3.5.25 Cause The commissioning process concludes with a change of state to the controller ('config/online' to 'offline' to 'online'). The issue is that this particular Trane controller responds to the first requests ('config/online' to 'offline') but fails to respond to the 'online' request (original message plus three retries as defined by the LonWorks protocol) or approximately 400 mSec. In addition, the binding process also utilizes an 'online' to 'offline' to 'online' change of state and has some similar delays within the controller response. Resolution Modifying the Retry Count within the Lon Comm Config settings (from 3 to 6) allows up to 6 retries in the event of a no response for this type of  message. The actual Trane node appears to take a long period of time (over 500 mSec) to respond to the change of state message. This change to the retry count will not affect the bus unless there are bus issues that generate multiple retries. Basically, the change will be not be noticeable on a solid operating bus.