Building Automation Knowledge Base

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 Event Enrollment shows Event State in alarm but the alarm notification is NOT delivered to CyberStation in the Event Notification recipient list. Environment CyberStation bCX4040 b4920 b3s Cause Download To BACnet Device option NOT selected when adding recipients in Event Notification object. Resolution When an Event Notification object resides in a controller (bCX or b3) the recipient information MUST be downloaded to the controller in order for alarm delivery to work. If in the list of recipient an entry has the Download field set to false remove the recipient from the list and add it again making sure the Download To BACnet Device checkbox remains checked.

Issue Xenta Server Error: "Sequences number in unit was reset. Fetching from first event." Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 Xenta Error Log Cause When Vista asks the Xenta Server for log data,it is returned unexpected data Resolution Reinstalling or upgrading to a System Program version >5.14 SP1 should correct this issue.

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 When we display the SNVTs in Vista, NL220 or Lonmaker the name of the SNVTS are very generic. Environment NL220 Lonmaker Vista Cause The XIF file was uploaded from the device. On some devices the function specific names are not supplied from the controller. Here is a sample of non specific names when uploaded from the controller     Here is a sample of the same controller with the XIF download from the manufacturers website. Resolution Go to the controllers manufacturers website or contact them and get the functioned named XIF file for that device. Use this instead of the uploaded XIF from the device.

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 How to enable Vista to log change of state events without trending every point. Environment TAC Vista Cause Need to log events to monitor change of state without using trend log.  Resolution There are two options to enable TAC Vista to log change of state events as shown below: Option1: Right click on the object you wish to monitor and open the properties of it. Change the watch settings from No watch to Watch. Note: Must use "Change of state" object.  It is not possible to do this under the Workstation or within a controller.  Right click on the TAC Vista and create a new folder - name the folder accordingly. Right click on the Folder which was newly created and create a new Object called change of state. Give a desired name and open the properties of the object. In General tab change the priority from 9 to Info. Select the Alarm tab set the low limit as 0 high limit as 1 and minimum change as 0. Select the object tab and navigate to the object to monitor. Close the popup by selecting OK. When ever there is change in state “on” to “off” or vice versa the event is recorded as object change in the Event view To see the events right click on the change of state object and select view events. Filter it by unselecting the alarms button on the window. Observe that events of the object are shown. Option 2: This needs to be done in your Menta file and it requires downloading to the controller. Open the Menta file of the desired device using edit option. Add a Alarm block to the Menta file. Connect the output / input block to the input of the Alarm block as shown. Right click on the Alarm block and select the edit option. In edit window of the Alarm block make sure the priority is set “0” (N.B. do not change it). Click on the edit button in the edit window of Alarm block and enter the desired text in the Alarm text. Steps 2 to 6 need to be repeated, if you need to do for more then one Input/Output Save the Menta file and download the same to the controller. These events are shown in Events views and not in the Alarms

Issue Configuring a UNC 532 outstation. Environment BAS 2800+ UNC532 UNC 532 Modem Ports Cause When configuring a UNC 532 outstation to use a modem, it may not be possible to connect a BAS 2800+ terminal as well. Resolution The UNC 532 has a limited port configuration as it's comms UARTS are shared, and therefore it cannot have a modem and a  BAS 2800+ terminal configured together if the controller is communicating via the lan connection. If the controller is operating as part of a network, i.e. via the lan, then channel 3 cannot be used. The screen shot below shows how the comms UARTS are shared. Please note that PL3 is Port 3 and PL4 is Port 2 in the Node configuration window. If the UNC 532 is being used in a stand alone configuration, then the configurations below are possible.

Issue The MZ20A actuator stops controlling, and the Analogue Output remains at zero volts. Environment MZ20A MZ20A-R Actuators Surface Mount Cause If the controller power and battery switches are switched off, then when the power is switched back on, the Analogue Output remains at zero volts. Resolution To prevent is issue from occurring, it will be necessary to install a 2K2 ohm resistor between each channel and the common zero volt rail, as shown in the picture below.   Add the 2K2 Ohm resistors to the channels controlling the MZ20A actuators. These resistors do not need to be a close tolerance; a Carbon Film ¼ watt 5% is acceptable, (RS Stock No.135-881 or similar). Note – The MZ20A, are the only actuators that we are aware of that require this modification, therefore if the actuator is changed to another type, the resistor should be removed again.

Issue Get server error in '/webClient' Application when attempting to connect with the WebClient Environment WebClient 1.93 Windows 7 Cause Bad installation Resolution 1. Run aspnet_regiis.exe -i (This is done from a DOS prompt, C:\Windows\Microsoft.net\Framework\v2.0.50727)  2. Re-install Continuum WebClient

Issue The sticker on the face of a Xenta 102-AX identifies the hardware version (1 or 2). If the board is changed out, then the actual hardware version may not match what is listed on the label. Visually inspecting the board can reveal if the board is a hardware version 1 or hardware version 2. Environment Xenta 102-AX Cause The orientation of components on the PCB of the Xenta 102-AX changed on the major revision from 1 to 2. Resolution Remove the plastic face plate from the Xenta 102-AX to reveal the logic board beneath. Look at the angle of the velocity pressure sensor. If the velocity pressure sensor is positioned perpendicularly to the controller (at a 90° angle), then it is a hardware version 1 controller. If the velocity pressure sensor is positioned at an angle, then it is a hardware version 2 controller. See image below for clarification:  

Issue When using the Generate project command in XBuilder the Generate output screen will not show any errors even though it reports an error was encountered or the error is visible but the info message indicating what it was trying to build the caused the error is not visible. Using the Window-> Restore Default Settings does not correct this. Environment TAC XBuilder Cause A filter has been applied to the Output window. Resolution Right click in the Output window and ensure that each of the following options are selected: Show Info Messages Show Warning Messages Show Error Messages

Issue Xenta 104-A ships from factory with a resistor on terminals 7 and 8 Environment Xenta 104-A Cause Terminal 8 is input U1, which is used by the controller for outside air temperature in the economizer calculation. Resolution The resistor is 1.8kΩ A temperature sensor on U1 would be a 1.8kΩ thermistor, if this input was being used. The resistor is a place holder to keep the unit out of economizer during initial setup if a thermistor is not going to be used.

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 Services for assistance. Issue After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

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 Recommendations for RS-485 LAN communications wiring Environment I/NET C-LAN, Sub-LAN Cause A review of some of the I/NET manuals yielded several instances of the following description: The same communications cable will support a combination of 32 Application Specific Controllers (ASCs), Micro Regulators (MRs) and Door Processing Units (DPUs), connected together in a "multi-dropped" arrangement, as illustrated in Figure 2. The cable should be run in a contiguous node-to-node arrangement without stubs or branches. Resolution We recommend the RS485 LAN (Including the Host LAN, Controller LAN & Sub-LAN) be arranged in a contiguous node-to-node bus configuration without stubs and within the maximum 4000' (1210 m) / 5000' (1500 m) length with 24/22 AWG low capacitance twisted pair shielded cable. 7808 Repeater For the RS485 Token Passing Controller LAN (C-LAN), the model Repeater can be used to branch (stub) off the main LAN bus with a C-LAN bus extension. The 7808 Repeater acts as a single RS485 node on both of the C-LAN segments with both being wired in a contiguous node-to-node bus arrangement. Additional 7808 Repeaters can be applied along the main LAN to distribute additional branches (if needed). The distribution of Stubs/Branches along the main LAN can continue up to a maximum of 32 RS485 nodes (in total) along any one copper segment. There can be another 32 RS485 nodes on the copper segment on the other side of the 7808 Repeater. The 7808 Repeater provides the vehicle to - Stub off the main C-LAN Split the main C-LAN distance when length is greater than 4000' (1210 m) Split the main C-LAN cable length when inferior cable (higher capacitance) is introducing excessive distortion Divide the RS485 node count to a maximum of 32 RS485 nodes on any single segment of copper. I.e. the 7808 provides a separate copper segment on each of the two sides with full RS485 node count (32) and distance specifications Repeated/Tiered Stubbing The 7808 Repeater can further accommodate stubbing off of the stubbed C-LAN segment as long as no more than four 7808 Repeaters separate any two C-CLAN controllers on the controller LAN network. I.e. looking from any 77xx controller out to all of the other 77xx controllers on the same controller LAN, you must not have to go through more than four 7808 Repeaters to reach any of the other controllers (regardless of whether the application actually has any interaction with the other controllers). Old Commentary on C-LAN Tolerance Dating back to the first release and field applications of the Series 6000 followed by Series 7000 controllers, there have been many instances where our Branches and Partners have needed to use exiting wiring in a facility. Inevitably, either the cable characteristics were not as specified (low capacitance data grade twisted pair), or the cable characteristics were not known, or the cable's geographic routing was not conducive to a node-to-node bus configuration. The economic impact of using existing cabling was always a magnet that attracted the project engineer and had to be balanced with a perspective of risk vs. reward. In many cases the existing cables made a node-to-node bus difficult, or impossible to achieve, without rewiring the facility. In some instances, the bus could be accommodated but would inject a large additional copper length into the main bus with the cable run to and from the distant controller location, before proceeding along the bus. With the prescribed cable, the preference is for the bus. But in forced situations where the cable isn't what it should be, it may be better to have a 250' stub than inject 500' of bad cable in the middle of the main LAN segment, with the preferred accommodation being the addition of a 7808 repeater to handle (isolate) the stub. The 7808 Repeater was created specifically to resolve such installation problems, and in most cases it is indeed installed after the fact as remedy for a problem instead of a initial installation and design of the system. Early in the product life this issue/question on use of existing cabling prompted investigation on my part regarding potential guidelines as to where deviations in the recommended LAN configuration could possibly be tolerated. At the 19,200BPS data rate we are running on the C-LAN, there is a significant amount of tolerance for reflected wave distortion from impedance and loading mismatches on the cable. This creates a scenario where the installer can frequently get away with "minor" violation of one of the specified cabling constraints, but doing such is exhausting at least some portion of the system's tolerance for communications distortion and degradation. The problem is that continued successful violation of one recommendation is sometimes molded into what is thought to be standard practice and frequently followed by other and sometimes more subtle violation(s) and the system becomes intermittent because the tolerable margin of error/distortion has already long been exhausted. Standard LAN Installation Recommendations Designated Low Capacitance Cable  Cable Impedance of 100-150 ohms (120 ohm = RS485 standard and preferred) Conductor Gage of 22 or 24 AWG - Data Grade twisted pair with shield Specified maximum of 32 nodes on a copper LAN segment Maximum cable length (4000' (1210 m) for 24AWG) Node-to-node bus configuration without stubs Pass through connection of the cable shield at each controller location Earth ground connection on cable shield at one end only Earth ground connection to each RS485 controller on the designated ground terminal/conductor Any comments regarding I/NET and the subject of "Ts and Stars being allowed" has to be an interpretation of possible earlier commentary by myself and/or others at TCON, Schneider Electric regarding what the I/NET C-LAN system will "typically" tolerate. I.e. what you can probably get away with, if you must. The recommended RS485 wiring approach is that the LAN be configured in a node-to-node bus configuration using the specified cable characteristics, distance limits and node counts and the 7808. Repeaters can be used when stubs or distance extensions or node count requires. When economics of rewiring a facility inject an elevated tolerance for risk, it has been said that the C-LAN system will typically tolerate up to 10 stubs of up to 250 ft ("when other specs are not being violated"). That is a guideline of typical C-LAN tolerance and not a system installation recommendation or approval. The 7808 Repeater has often served as an insurance policy for some who have found the economic need to stub, and in some instances ran into subsequent problems. In other words, they injected stubs when needed and then added Repeaters later if needed to resolve a problem caused by the stub(s). Note that the 7808 Repeater is applicable only to the RS485 Host-LAN and C-LAN, and there is no such post installation solution for the Sub-LAN. The distances are typically shorter on the Sub-LAN and therefore typical tolerance in other areas is higher, but the recommendations remain the same. Termination In most cases the RS485 LANs on I/NET are not being terminated. This is also a tolerance associated with the I/NET RS485 protocol and speed and is a functional issue regarding the 7808 Repeater and the Sub-LAN's SLI (7790A or 7798). The 7808 Repeater depends on C-LAN biasing and is not tolerant of termination on the C-LAN. The C-LAN can indeed be terminated with a 120 ohm resistor at each end of the C-LAN "BUS", when 7808 Repeaters are not being used. This can be a first step in resolving a C-LAN communications problem prior to introducing 7808 Repeaters. The 120 ohm 1/2 watt termination will reduce distortion on the C-LAN and improve noise immunity. The Sub-LAN will not tolerate 120 ohm termination due to the 2.2K ohm biasing of the Sub-LAN required at the 7790/7798 controller. You will have to use a 620 ohm 1/2 watt resistor on the Sub-LAN systems

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 Xenta 102-AX space temperature sensor calibration offset can be set through Vista Workstation. If using degrees Fahrenheit, it is helpful to change the units on that value from "°F" to "°F, diff" to eliminate the 32° offset and make it more intuitive to the user. Environment Xenta 102-AX Vista Workstation Classic Network UCPTvavSelection.CSS Cause 0°C (whether a temperature value or an offset value) converts to 32°F. If referring to an offset value, the units of °F, diff eliminate this 32° offset. Resolution Navigate to the VAV in the network structure in Workstation Go to VAV_Controller and find UCPTvavSelection.CSS Double click the value Click on the Unit field and choose °F, diff from the drop down menu Click OK Open the value again, now enter any desired calibration offset for the space temperature.