Building Automation Knowledge Base

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 In Niagara Enterprise Server versions older than N4.9, the Niagara Service fails to start. Typically the service successfully starts when the 'plat installdaemon' is executed. Product Line TAC IA Series Environment I/A Series N4 Enterprise Server (earlier than N4.9) Cause The Niagara daemon fails to restart automatically after a server reboot Resolution For older Niagara versions, these are two workarounds that may work in some cases:   Option 1:  Go to Start > Run > and type regedit  Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control  With the control folder selected, right click in the pane on the right and select new DWORD Value  Name the new DWORD: ServicesPipeTimeout  Right-click ServicesPipeTimeout, and then click Modify  Click Decimal, type '180000', and then click OK  Restart the computer Option 2: Create a Task Scheduler task that calls the command "net", with the arguments "start niagara" five minutes after boot.   Alternative Solution (reported to work on Niagara older than 4.7): There are two solutions to implement in the Niagara Service. Before performing the settings below you must first have NiagaraD successfully installed. After the computer has rebooted, manually install NiagaraD using 'Plat installdaemon'. Once the service is installed implement the two configurations below. Open Windows 'Services' and then double-click the 'Niagara' service to open the Niagara Service Properties window . You can select to delay the start of the Niagara Service which helps give Windows time to initialize before the service attempts to start. Set the recovery options on the 'Recovery' tab. It is recommended to set all three 'failure' options to 'Restart the Service'

Issue MSTP controllers go offline when changing the MaxMaster value in the Automation Server from it's default of 127 Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server MSTP Master Controllers Cause The MaxMaster value is being set lower than some or all of the MSTP controllers on the network Resolution EcoStruxure Building Operation supports MSTP Master controllers in the address range 0-127 (often refered to as the node id). The MSTP network is a token passing network where the token is passed around the network, until a controller has the token it cannot 'talk' to other devices.   The MaxMaster value is defaulted to 127 to allow all devices on the network to receive the token and reply to online status requests, send values etc. If the MaxMaster value is less than any of the MSTP Master controller addresses then those controllers never receive the token and cannot respond to online status requests.   The value for the MaxMaster needs to be equal to or greater than the highest addressed MSTP controller node id.  For example, if the highest node id=54 then the MaxMaster will need to be set to 54 or higher. For maximum efficiency the MaxMaster should be set 1 or 2 greater than the highest controller address, this allows for adding future devices without needlessly polling for many non-existent devices.    Please refer to BACnet MS/TP Network Properties – Basic Tab or Configuring the MS/TP Network for b3 Communication 

Issue After setting up a UNC as a BBMD the other UNC's on that subnet are getting "network mismatch" errors in their standard output windows. Product Line TAC IA Series Environment R2 UNC's with BACnet jar's earlier than 535a. Cause This type of error is indicative of a routing loop on the BACnet internetwork.  UNC's with a BACnet jar prior to 535a when set up as a BBMD will broadcast on their own subnet as well as to the other BBMD's and this can cause that also. Resolution Install BACnet jar 535a or later in the UNC that is the BBMD to see if this corrects this issue.  If the issue persists investigate the BACnet internetwork for a router loop. 

Issue How to configure a G3 station as a BACnet BBMD Product Line TAC IA Series Environment I/A Series G3 version 3.3.22 and later Cause Documentation Resolution In the G3 Station, expand the BacnetNetwork, expand Bacnet Comm, expand Network, and then double-click IP Port.  The IP Port Property Sheet opens (see below)   In the IP Device Type drop-down, select Bbmd.  Click Save The station is now configured as a BACnet BBMD

Issue Too much LON communications traffic can cause LON communications errors. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series MNL 800 Building Operation Automation Server Premium LON Network  I/A Series R2, AX, N4 Jace LON Network Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. One of four NCI objects (nciSndHeartBeatA, B, C, or D) is assigned to each NVO object in the application program. This value regulates the periodic LON transmission queuing of the NVO object values for each binding. One of four NCI  objects (nciRcvHeartBeatA, B, C, or D) is assigned to each NVI object in the application program. This value regulates the fallback timeout for each NVI object value. If a value is not received via the binding in this time period, the NVI object value will revert to its application-defined default value. In an MNL-800 controller, there are two additional NCI objects that are used to regulate the flow of data onto the LON network. The nciMinOutTime object is used to throttle the transmission of all data values queued to be sent via bindings over the LON network. This NCI object sets the transmission time interval between each NVO value being sent on the network. The important fact here is that the product of the number of bound NVO values times this interval (nciMinOutTime) must be LESS than the shortest nciSndHeartBeatX (X=A, B, C or D) interval. For example, if the Send HeartBeat is set to the default of 120 seconds and there are 60 NVO SNVTs bound from this controller, the nciMinOutTime must be set to a value of fewer than 2 seconds.  The recommendation for setting this SNVT value one half the shortest nciSntHrtBr divided by the number of NVO SNVTs bound from the controller.   The nciMinPropTm object is used to regulate the transmission queuing of changing bound NVO object values. This timer acts as a time-based filter to prevent a rapidly changing NVO value, such as a constantly changing temperature, from overwhelming the communication capacity of the LON network. Typically this value is set to a value of 1 to 5 seconds. Additional information can be found in Chapter 6 of the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). BACKGROUND: This section is provided to give the reader a basic understanding of bound LON communications, as applied to LON controllers in general. Data communications across a LON network is accomplished by using a LON Network management tool to create a binding between a device with a data source (NVO object) and one or more devices with data receivers (NVI objects) in other LON controllers. The device containing the data source will send the bound data value at a periodic rate, as defined by the associated SendHeartBeat NCI object, and whenever the value of that object changes. If the NVI object does not receive a value from the sender (bound NVO object) within a specified time period, as defined by the associated ReceiveHeartBeat NCI object, the NVI object will use a local fallback value until such time as it receives a new value via the binding.

Issue The Universal Input real-time values on a MNL-800 (or Microzone II) are fluctuating unrealistically.  They rise, peak, drop, valley and then start over again very quickly.  It is similar to an AC wave pattern. It is happening with all the inputs no matter their configuration. Product Line TAC IA Series Environment MNL-800 Microzone II (Network 8000) Cause When an actuator is interfaced with a MNL-800 (or MicroZone II), and the UI cable shields are connected to earth ground (the SHLD terminal), the shield has a common mode AC potential that couples to the UI input. Only a very small signal (UI shield to signal common) is needed to result in objectionable UI signal fluctuation. Resolution Connect all drain shields on UI inputs to UI common (C terminal). Read additional solutions and a more descriptive cause in Technical Bulletin 01-36.

Issue How can a BACnet system be customized to maximize data throughput?  The site has a Niagara R2 Enterprise Server and a UNC with a variety of MSTP controllers connected to the UNC. Environment Niagara R2 Enterprise UNC MSTP controllers Cause Improper configurations won't achieve optimum performance. Resolution This can be a relatively complicated question, however, there are a number of basic steps that can be taken in terms of best practices to enhance performance. Within the UNC station, any BACnet objects that are not needed are to be deleted. During the learn of a BACnet controller, many objects are learned that are not used. All BACnet objects when learned into a station are placed in Poll-Always containers. All but the most critical objects, schedules and trended objects are to be moved to Poll-on-Demand containers. All controllers on the MSTP bus should be consecutively addressed.  Gaps in addressing add delay in communications. The MaxMaster setting in all controllers, including the UNC, is to be set to a numeric value two greater than the highest MSTP controller address on the network. To leave MaxMaster at 127 but only have 20 controllers on the network will also add delays in communications looking for the other non-existent 107 controllers. The MaxInfoFrames setting in the UNC or MNB-1000 is to be set to a number higher than 5 but no more than 20. This setting determines how many pieces of information can be requested each time the UNC or MNB-1000 receives the token on the MSTP bus. The default value is 1 and if left at this value the system will be sluggish with updating values on graphic screens. The range of 5 to 20 is given as a starting point for experimenting and each system will be different depending on the number of controllers and what data is being requested.  Lab tests have shown there is a performance curve with an optimum point.  Starting at a value of 5, performance increases as the value increases.  Performance will then peak and any further increase to the setting will result in a performance reduction.  As a result, stay above 5 but less than 20. Refer to the document titled "I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide" (F-27360) for additional information.

Issue What is Domain Name Service (DNS)? Product Line Andover Continuum,EcoStruxure Access Expert,EcoStruxure Building Expert,EcoStruxure Building Operation,EcoStruxure Security Expert,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment TCP/IP Networks Cause DNS is a distributed hierarchical system for resolving host names into IP address. Under DNS, there is no central database with all of the Internet host information. The information is distributed among thousands of name servers organized into a hierarchy similar to the UNIX file system. DNS has a root domain at the top of the domain hierarchy that is served by a group of name servers called the root servers. Source: TCP/IP Network Administration by Craig Hunt, O’Reilly & Associates, Inc. Resolution Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they're easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4. The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.  

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue Documentation on the MSC-MPC Microsmart controller and its associated modules. Product Line TAC I/A Series Environment Microsmart controller MSC-MPC MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-MPC. Click each associated module part number below to view its installation instructions: MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue Some jobsites require the use of conduit for all wiring between controllers. Is there a specific enclosure made for this purpose?  A general purpose enclosure such as the ENCL-100 can be used but must be punched or drilled to fit the damper shaft. Product Line TAC IA Series Environment MN-FLO / MN-FLO3T MNL-V1RVx / MNL-V2RVx MNB-Vx Cause Installation manual with reference to part number was misplaced. Resolution MNA-FLO-1 This enclosure is listed as an optional item in the installation manuals for all VAV controllers listed above. Click here to see F-26282-5, Installation Instructions for the MNL-V1RVx and MNL-V2RVx. Click here to see F-27346-4, Installation Instructions for the MNB-V1 and MNB-V2 Click here to see F-25718-6, Installation Instructions for the MN-FLO and MN-FLO3T

Issue A Niagara G3 station (version 3.5.25) reports the following error in the Application Director Output (full text version of error): ERROR [10:41:43 09-Mar-12 CST][sys.engine] Cannot start component: false {ok} javax.baja.sys.IllegalNameException: Illegal name "booleanSwitch.invalidInSwitch".    at javax.baja.naming.SlotPath.verifyValidName(SlotPath.java)    at javax.baja.sys.BFacets.make(BFacets.java)    at javax.baja.status.BStatus.make(BStatus.java)    at javax.baja.status.BStatus.make(BStatus.java)    at com.tridium.kitControl.util.BBooleanSwitch.onExecute(BBooleanSwitch.java)    at javax.baja.control.BControlPoint.doExecute(BControlPoint.java)    at javax.baja.control.BControlPoint.fw(BControlPoint.java)    at com.tridium.sys.engine.EngineUtil.descendantsStarted(EngineUtil.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)    at javax.baja.sys.BComponent.start(BComponent.java)    at com.tridium.sys.engine.EngineManager.start(EngineManager.java)    at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java) Product Line TAC IA Series Environment Niagara G3 Cause There is a known issue with version 3.5.34.2 of the kitControl module:  An error occurs when "null" is used as the value for "inSwitch" Resolution Upgrade to version 3.5.39 of the kitControl module.  Click here to download a copy or visit niagara-central.com (downloads).

Issue PSI / XPSI Revision 4.0 will not tunnel, nor will it connect via modem. Product Line TAC IA Series Environment PSI / XPSI Revision 4.0 Cause Not supported in this release. Resolution Upgrade to PSI / XPSI Revision 4.1, which the file PSIv4.10.zip is available for download on The Exchange Download Center. Click here to see the Release Notes included in the zip file.

Issue Microsoft no longer allows OEM computer manufacturers to install Microsoft® Windows Server 2003 or Microsoft® Windows Server 2003 on OEM computers.  Is there a valid legal and legitimate workaround for running software products that are not compatible with Microsoft® Windows Server 2008? Product Line TAC IA Series Environment New server class computer that was purchased pre-loaded with Microsoft® Windows Server 2008 or Microsoft® Windows Server 2008 R2 I/A Series software that runs only on Microsoft® Windows Server 2003 such as: I/A Series (Niagara) R2 - all releases I/A Series (Niagara) G3 - all releases prior to 3.6.x Cause Microsoft® Windows Server 2003 is no longer available on new computers. Resolution Downgrade the Microsoft® Windows Server 2008 to Microsoft® Windows Server 2003 According to the Windows Server License supplied with all versions of Microsoft® Windows Server 2008 (including R2), the license grants the customer the right to run an earlier level or edition of Windows Server.  Microsoft permits this downgrade because many customers need to continue using old versions of Windows Server for compatibility reasons. More information is available in this Microsoft document.

Issue In an I/A Series G3 station, is there a way to relocate a history from one parent history container to another without losing history data? In addition, can the associated history ID be modified to allow new data to log and append into the relocated history? Product Line TAC IA Series Environment I/A Series G3 (Niagara) station Cause Sometimes a user will want to move a history to a different folder. Resolution See the procedure illustrated with screen captures.

Issue Not generally available Product Line Field Devices Environment I/A series Field device Cause Information not provided with the documentation supplied. Resolution The STR800 Series User manual can be downloaded by selecting this link. The STR800 Temperature Sensor RoHS Certificate can be downloaded by selecting this link. The STR800 Wall Module Specification Sheet can be downloaded by selecting this link. Other STR800 documentation is available on the Schneider Download Center.