Building Automation Knowledge Base

Issue One of the Panel Units' title needs to be re-worded in a DMS database.  How is this done with OPRIF? Environment DMS 35, DMS 350A, DMS 3500 all revisions Cause Mechanical equipment naming has changed and the DMS database is being modified to match. Resolution The message text table lists the Panel Unit Descriptor Messages.  Cursor down to the descriptor requiring modification and press the "=" key.  Type in the new text and press Enter. For more information, see Chapter 4 - "Setting Up Tables" in the DMS Operator Interface User's Guide (F-25467).

Issue Using the WPTech Flow Balance software and trying to generate the balance report in HTML format.  When doing this receive  the following warning: Environment MicroNet BACnet Flow Balance Software WorkPlace Flow Balance Tool MNB-V2 Cause Cause has not been determined. Resolution If this “Warning” appears check “My Report” folder”, the HTML may have been created even though the “Warning” was issue. The cause of this anomaly has not been determined at this time. This article will be updated when a solution is found.

Issue A Niagara R2 station running the ModbusAsync Service does not see any communications traffic on the designated COM port even with the "debugOn" setting enabled. Environment Niagara R2 all versions Cause The ModbusAsync Service and the ModbusAsyncNetwork were copied to an existing station from the local/remote library. Resolution Ensure the serviceId of the ModbusAsync Service and the serviceId of the ModbusAsyncNetwork are a match.  

Issue During an electrical storm, a component labeled MFC27 was damaged.  It is one of many similar components on the MNL-800 backplane or base circuit board.  What purpose does it serve and which circuit was it a part of? Environment MNL-800 Cause High voltage spikes from an electrical storm.  Sample of MFC damage in image below. Resolution All the MFC components on the backplane are Multi-Function Ceramic (MFC) protectors.  They are designed to absorb high voltage introduced into the circuit to which they are a part of.  In particular, MFC27 protects universal input six (UI 6).   See a sample image of MFC damage below. Although damaged, the backplane can still be used but that specific circuit won't have any further high-voltage protection.

Issue The platform daemon for the localhost displays this error: ERROR   [09:21:09 28-Jun-2011] [tid=712] app registry: app svr_station NOT created, maximum app limit reached All of these stations were part of a migration from one version of G3 to another.  All the station folders were copied and pasted prior to starting Workbench. Environment Niagara G3 version 3.5 and older Cause More than 32 stations are not supported on any G3 platform (3.5 and older).  This is not a license restriction. The 32 station limit applies to the number of station folders on the hard drive under the release directory.  This is only a constraint for engineering the stations.  In Release 3.6, 3.7 & 3.8, the limit is  in excess of 150 "station" folders. Resolution If one computer (running Workbench) is being used to engineer more than 32 stations, then some of the station folders will have to be cut / pasted back and forth with some other temporary folder on the hard drive. Example: A job will have 35 total stations when complete.  In order to engineer them from one computer, 3 station folders will have to be cut out from beneath the parent "stations" folder and put in a temporary folder elsewhere on the hard drive. When there is a need to engineer one of the three cut stations, use Windows Explorer to move it back into the Niagara "stations" folder and remove some other station folder.  Always maintain 32 sub-folders under the "stations" folder. In Release 3.6, 3.7 & 3.8, the limit is  in excess of 150 "station" folders.

Issue When starting communications, a failure occurs generating the errors illustrated below:   Windows cannot find 'CDECHICO.EXE'.  make sure you typed the name correctly, and then try again.  To search for a file, click the Start button, and then click Search.     Environment Tree Tech 3.1 Cause The "Connection Type" for a network in the E: EQUIPMENT DATABASE was assigned as "ARTIC ECHELON". This connection type was used for a communication interface card that was obsoleted many years ago.  It was used with IBM's motherboards using MicroChannel expansion sockets. Resolution Click on the down-arrow and select a different connection type.  The two most-common are:  Ethernet and Serial.

Issue In G3, how to NOT have the AUTO function invoke in a Boolean Writable when the station is restarted?  Environment I/A Series (Niagara) G3 ENCs (all revisions). Cause Default setting of Fallback is check for NULL Resolution In the property sheet of the Boolean Writable object, at Fallback uncheck NULL.

Issue What's the easiest way get a TIP license for Tree Tech 3.1 for legacy panel database maintenance? Environment Tree Tech 3.0 (included with WIBS 1.1) Tree Tech 3.1 Network 8000 DMS Cause Up to four unlock codes are required for Tree Tech: - one for Tree Tech itself - one for the serial driver - one for the Network 8000 ethernet driver - one for the DMS ethernet driver  Resolution In the Purchase program, select the part number in the package list called IV-DEMO-CDE (scroll down to the bottom of the list). Ordering and unlocking this part number will include Tree Tech and the three communication drivers. This is a permanent license and does not expire.

Issue A VAS Client has been configured with low-level access for use at a security desk in a building.  Only certain alarms are routed to this client and the user account assigned allows for the ability to view and acknowledge alarms.   The Security Mask settings are illustrated below:   However, these settings do not allow for acknowledged alarms to be deleted from the VAS Client's Alarm History: Environment Niagara R2 Enterprise Server; build r2.301.529 was tested. Niagara R2 Vykon Alarm Service (VAS) Client; version 2.5 was tested. Cause The VAS Client requires access to the entire alarm history database in order for the ability to delete acknowledged alarms. Resolution To give access to the entire alarm history database, the Security Mask settings must be modified as illustrated below:   Note:  These settings will route all alarms to the specific VAS Client.  As a result, the user will be able to view, acknowledge, and delete any alarms. There is no way to avoid this scenario.  If alarm deletions are to be reserved for an administrative user, then restore the Security Mask settings as per the illustration in the Issue section of this article.

Issue To enable BACnet communications in an I/A Series (Niagara) UNC station, enter a valid instance number. Environment I/A Series  R2 (Niagara) UNC, all versions Cause The BACnet Service in the UNC defaults to instance number = -1, which prevents the BACnet service from communicating. Resolution Assign a valid Instance Number on the General, Config tab of the BACnet service. The valid range is from 0 to 4194302. See the Niagara BACnet Integration Reference, Chapter 1, "Configuring Essential Station Properties", Procedure 1-2, Step 2. Note: In addition to setting the Instance Number, the appropriate Link-Layer must be enabled, eg, "ipEnable = True".

Issue Passing Analog data between multiple  I/A series UNC-520s with DMS panel. Environment I/A series UNC-520 DMS-3500 Cause Application note Resolution For each DMS panel receiving an Global (broadcast) Analog Value, create a dummy AP point (UC AP) , name it and then select AP type 07. At the UNC, learn the new point and select PVALU:WRITE, select "Add"  then "Create". In the workspace two object will appear, AO and DmsGenericAO. Insert an Math object and link the pOut to pIn of AO. See below. The Math Object is required to convert the AI from floatStatus to floatPrioity. Link (Math Object) sinA to the analog point in the DMS panel that will be broadcast to other panels that has this point.   Don’t forget for each UNC station, add each IP to the “AddressBook” set up for PEER   For any MicroSmart controller, add a LP point and link it to the DMS. The DMS AP will be the input to linked MicroSmart LP point. Edit the Broadcast Channel  with the GLOBAL number for broadcasting

Issue What is a quick way to determine the IP address of a MNB-1000 that is integrated to a Niagara R2 station?  Assume only Workplace Pro is available (Workplace Commissioning Tool is not available). Environment MNB-1000 Niagara R2 UNC-410 and UNC-520 Cause None Resolution The IP address is stored in hexa-decimal format within the properties of the controller's shadow object.  A unit-conversion calculator is required to determine the IP address in decimal format (the Windows calculator can do this task). To find the IP address, Locate the shadow object of the MNB-1000 Go to its Properties, Config tab Record the first 8 digits of the hexa-decimal number displayed at the "address - MAC Address" parameter.  The last four digits are the UDP Port number and are not part of the IP address Convert to decimal Example,     C0 = 192,  A8 = 168, 01 = 1, 96 = 150 BA:C0 = 47808 (UDP Port Number) MNB-1000 IP address is 192.168.1.150

Issue ERROR [Current Date] [AsdNetwork_COM3] Unlicensed: /Drivers/AsdNetwork Javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd Environment I/A Series G3 (Niagara) Asd Driver Cause The issue is caused by a missing certificate. Each license installed needs to have a matching certificate. Resolution Obtain TAC_LLC Certificate Install under License Manager Reboot ENC If issue persists verify the license file name is correct, i.e. TAC_LLC.license.   If it doesn't match this name exactly obtain new license file.

Issue How to connect 2-10 Vdc position output signal of an actuator to an analog input of LON or BACnet controllers. Controller’s Analog Inputs are limited to 0-5 Vdc input. Environment WorkPlace Tech I/A Series Lon (MNL) controllers I/A Series BACnet (MNB) controllers Cause Controller’s Analog Inputs are limited to 0-5 Vdc input. Resolution See the WorkPlace Tech Tool Engineering Guide (F-27254-3) Analog Input object discussion (page 129) for reference. Setting up a 2 to 10 VDC feedback voltage divider, use a 120 K (120,000) Ohm in series with a 100 K (100,000) Ohm resistor; connect the UI across the 100K Ohm resistor. As long as the signal never exceed 10 VDC, the voltage across the 100 K Ohm will never exceed 5.0 VDC. Based on the above test results, 10Vdc [actuator output] = 4.545 Vdc [after voltage divider] 2 Vdc [actuator output] = .909 Vdc [after voltage divider] Set-up the Analog Input Object Linput= 0.909 Vdc LScale= 0 Hinput= 4.545 Vdc HScale= 100 Your values maybe different based on the resistor accuracy.

Issue The TAC I/A Series G3 ASD Driver Installation and Configuration Guide, F-27522, does not describe the Send Group object. Environment I/A Series G3 (Niagara) station containing the ASD driver I/A Series Network 8000 ASD controllers ; MicroZone II, MicroFlo II, LIM, or PEM1 PSI / XPSI to edit database in the ASD controller. Cause Setup not documented. Resolution Basic setup procedure: Verify the configuration of the ASD controller, using PSI: ASD device, Edit, device, Setup, Group # RGRP:n block, where n matches the Group Number in step 1 Edit the G3 station using the Workbench, as follows: In the ENC station, AsdNetwork, Groups (AsdGroup Device); verify Enabled = True verify status = OK  SendGroup object under the Groups. Verify Device Type matches the controller type ( Mz2, Mf2, Lim, or Pem) Verify Group Number is the same as in Steps #1 & #2 above. Set Mbx Input = true;  by either setting Mbx Input Default = true, or by connecting a Boolean Writeable to the Mbx Input

Issue Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC. Product Line TAC IA Series Environment Niagara R2 UNC-520 Niagara G3 ENC-520 Cause Pinout diagram for wiring Resolution This image details two pinout configurations:  Null Modem and Straight-through.  The Null Modem version is available for purchase using part number UNCC-405.  The Straight-through version is not available for purchase. This image is also part of the UNC-520 Installation Instructions (F-27391)

Issue Installed the I/A Series(Niagara) R2 software on a new Windows computer but cannot get it to connect to an existing UNC that has the same release of the I/A Series R2 software.  One possible error, "Java.io.EOF Exception", that might be displayed is shown below: Another possible error message is an HTTP 401 error. This issue may also prevent the I/A Series R2 tunnel client from connecting to UNC. Environment Computer with any supported version of Windows software including the usual assortment of utility and security / anti-virus software. I/A Series (Niagara) R2 software (any version) installed on the computer. Cause The Windows Firewall and/or Anti-Virus/Internet Security software has been installed and configured such that it is blocking Ethernet communications into or out of the computer on certain Ethernet ports. According to the I/A Series Networking & Connectivity Guide, provided with the I/A Series (Niagara) R2 software, specific user definable Ethernet ports, must be open for two-way communications between the WorkPlace Pro software and a UNC.  If communications is blocked on these ports, the WorkPlace Pro software will not be able to communicate across the Ethernet network. Similar issues are caused by the firewall built into many of the Internet Security software packages.  The following programs have been known to cause port blocking issues: Trend Micro Internet Security - Workstation Edition Trend Micro Office Scan - Workstation Edition Symantec Internet Security Suite version 9 Avast 7 (Free) Antivirus with 30 day demo of Avast Internet Security Bitdefender Antivirus Software Kaspersky PURE 3.0Total Security Kaspersky Endpoint for Business Resolution Verify that the Windows Firewall has been configured to pass bidirectional Ethernet communications over the two required Ethernet ports (default ports are 80 and 3011 - for both the TCP and UDP protocols).  Refer to the online Windows Help for configuration information.  Note that  computers that are members of a Windows Domain may have firewall configuration restrictions enforced by domain policies.  In these situations, it will be necessary to contact the Domain Administrator or facility PC-Help Desk for assistance. Verify that any installed Internet Security software does not block the required Ethernet communications ports.  Some specific Internet Security software packages are known to permanently block the use of some Ethernet ports, for specific uses.  Any Internet Security software of this type must be totally removed from the computer before the required communications can be established.  Three known software packages of this type are the "Symantec Internet Security Suite, version 9", "Bitdefender Antivirus Software" and "Trend Micro Internet Security software".

Issue History Extensions in History Service show a “Fault” Status.  The Fault cause displays: "Duplicate history id:" followed by the name of the object. Environment I/A Series G3, version 3.3.22 and later Cause  By default, history extensions inherit the name of the objects they’re attached to (e.g. CFM).  If CFM is to be trended on multiple VAV units (VAV1, VAV2, etc.), this can cause issues when enabling history collection in the History Service; one or more histories will be in a “Fault” state, with the error message: “Duplicate history id:” for the Fault Cause. Resolution To resolve the issue, the history names can be configured to include the parent folder names:     1.  Open the Program Service in the station’s Services container, and click on the “Find Objects” button at the bottom of the Batch Editor view 2.  In the Bql Query Builder window, select (Custom Type) in the “Of type:” drop-down menu.  Two more drop-down menus will appear.  In the middle drop-down, select “history”.  In the last drop-down, select the appropriate history extension (e.g. NumericIntervalHistoryExt).  Then, click OK.  The Batch Editor view will populate with all of the history extensions in the station for the extension type selected     3.  In the Batch Editor view, highlight all of the history objects, then click the “Edit Slot” button at the bottom of the view 4.  In the Edit Slot window, select “historyName” in the Property drop-down menu.  In the New Value field, type the following:      %parent.parent.name%_%parent.name%     NOTE:  Depending on the tree structure, the filter may need to be modified in order to create a unique history name.  For example, if the network is structured in the following format:   In this example, the object nviSatSwitch1_value is a child of the Points container, which is a child of the device MnlRs3_10. In order to create a unique name for the history extension, the correct filter would need to be:         %parent.parent.parent.name%_%parent.name%.   5.  Click OK.  After a few seconds, the BatchEditor Results window will appear, displaying the objects that were changed.  The history extensions now have unique names, and can be enabled in the History Service

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue Network scanning software causes a loss of Jace network communication. Product Line TAC IA Series Environment I/A Series Jace 8000 N4.9 and later Cause As network security awareness continues to expand, software-based scanners, such as industry-standard Qualys and Nessus, intended to detect and report on vulnerabilities within internal networks will likely continue to gain popularity.  Today, Tridium is seeing these scanners being deployed and run against Niagara-based platforms like the JACE-8000 and Edge 10.  In some cases, these scans are causing Niagara platforms to become unresponsive or reboot via an Engine Watchdog Timeout, all of which are not acceptable for the critical applications that Niagara facilitates. Resolution While Tridium has no control over how these scanners behave, or how and when they are executed within an organization, Niagara 4.9 introduces a number of changes intended to allow a Niagara-based hardware platform to appropriately respond to the scanning utilities, and also maintain operation.  Below is a brief explanation of how Niagara will function under the different known circumstances currently employed by these scanners, and how to interpret the results.   Recognition of non-Niagara Traffic on the platform In the event a scanner is interrogating a Niagara 4.9+ platform connection, the Niagara Daemon has been modified to recognize non-Niagara traffic over a period of time, shut down the connection if necessary, and wait for a pre-determined amount of time before re-enabling connectivity.  Under these conditions, a scanning utility may report that the Niagara instance has encountered denial of service, when in fact, Niagara has simply disabled the communication mechanism by which the scanner was attempting its interrogation. During this time, normal platform communication will also be affected; however, the Niagara platform and station will continue to run.   Prioritization of Internal vs. External Communication on the Niagara station In the event, a scanner is interrogating a Niagara 4.9+ station (external communication) and Niagara detects that this interrogation may cause an Engine Watchdog Timeout, the station’s web server will be stopped and restarted. Under these conditions, a scanning utility may report that the Niagara instance abruptly stopped communicating, and may have encountered denial of service.  During this time period, normal/expected client web connections to the station will also be affected; however, the Niagara platform and station will continue to run. As mentioned, these scanners are outside the control of Tridium, and likely always evolving to meet the needs of the various threats they are intended to protect against. As a best practice, Tridium recommends not scanning in production if possible, as any findings would be just as legitimate during scheduled downtime. Additionally, it may be prudent to work with the scanning tools to configure the appropriate priority of a scan, as the intensity of which you scan a production multicore, failover redundant web server host, is likely not the best choice for scanning a single-core JACE. Should you encounter an issue with a network scanning utility and Niagara 4.9 and above, please contact your support organization.