Building Automation Knowledge Base

Issue Can the WorkPlace Flow Balance Tool (for BACnet) override the fan in a fan-powered VAV box? Environment WorkPlace Flow Balance Cause Balancing requirements Resolution The fan cannot be controlled from within the Tool.  It will have to be powered on or off using another tool like WorkPlace Tech or from the networked controller (i.e. UNC/ENC)

Issue If the WorkPlace Tech Tool application file has been modified when you attempt to monitor a controller containing that application, blank or incorrect monitor tag values will be displayed. Environment WorkPlace Tech Tool software versions 5.0 through 5.8.2 or 5.8.6 MNL or MNB controller loaded with an application downloaded from WPT Visio 2003, Visio 2007 or Visio 2010 Cause There are two causes: First, the WPT software, release 5.8.3, 5.8.4 or 5.8.5 will modify the application when it is opened making it appear to be different than the previously downloaded application Second, failure to observe the following three constraints, regarding the application .vsd file will make the application file appear different than the application previously downloaded: The application file (.vsd) must not have been modified and/or re-saved in any version of the WorkPlace Tech Software since the application was downloaded. The application file (.vsd) must not have been modified directly in Visio and re-saved. The application file (.vsd) must have been last saved, compiled and downloaded using any version of the WorkPlace Tech Tool software, 5.0 through 5.8.2 or 5.8.6, running in Visio 2003, 2007 or 2010.   Resolution An application downloaded to an MNL (or with the compatible WPT version, MNB) controller can be monitored provided that the application .vsd file has not been modified or re-saved after download and that the current version of the WorkPlace Tech Tool software, versions 5.0 through 5.8.2 or 5.8.6 (not versions 5.8.3, 5.8.4 or 5.8.5)  is being is being used with a compatible version of Visio (2003, 2007 or 2010). NOTE: For MNB controllers this applies only to WPT versions 5.7.0 through 5.8.2 and 5.8.6 as the earlier versions are not compatible with MNB application development.

Issue A LON -USB adapter is configured as LON2 on a Windows laptop.  Several efforts were made to modify its address to LON1 but to no avail.  Running a Niagara R2 station on a laptop, with the LonWorks Service, defaults to using LON1 for the interface.  Can LON2 be used instead? Environment Niagara R2 Cause Unable to modify the adaptor's LON address Resolution In the Admin Tool, modify the drivers.properties file located on the Installation tab. Change the line "lon.deviceName=LON1" to "lon.deviceName=LONx"      where x = new port number. Restart the station.  

Issue Analog Pulse Command Object Environment I/A Series R2 Cause A standard I/A Series Analog Output object will send a value periodically or when there is a change of value. However, the lighting control system requires a pulse command type.  Resolution There is a 'Fp1Shot' object in the programlib library which can functions as an Analog Pulse Command. This object is located in tridiumx > programlib > util.  If you go to the properties of the 'Fp1Shot' object, you can set the minimum and maximum values that allowed to be set. You can also set the delay time which determines how long the value should hold before being released.  If you go to the properties of the 'Fp1Shot' object, you can set the minimum and maximum value allowed to be set. You can also set the delay time which determines how long the value should hold before being released. 

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Environment Remote Control Software. Cause Not all features are seen when a BMS platform is viewed using remote control software. One example is: When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. Resolution When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. The above example is one scenario. There are a number of other remote control software applications where similar instances may occur. If such an issue occurs, check that the BMS software is functioning correctly by both being viewed and ran in the same environment. Because of the number of different remote control software options that are available, anomalies will prevail.

Issue Selecting the "WorkPlace Tech Tool Help" function from the WPT help menu brings up a Schneider Electric TAC I/A Series product splash screen but there is no way to access the documentation from that menu.  The external web based links are functional but none of them work without Internet access. Environment WorkPlace Tech Tool software version 5.8.x Cause The document browser requires the capability of running local active-x controls on the computer. Resolution Due to tightened application and internet security policies, some computers have the default browser configured to block the use of local active-x controls. To allow these menu functions to run, perform the following steps: Open the Internet Explorer and select "Internet Options" from the Tools menu.  Note: Different versions of the browser use different methods for displaying the tools menu. In the Internet Options window, select the Advanced tab. In the list of settings shown in the settings box, scroll down to the "Security" section. Check the checkbox for the option "Allow active content to run in files on My Computer" Clock the [Apply] button then the [OK] button at the bottom of the Internet Options window. Close the Help (browser) window. When you reopen the WorkPlace Tech Tool help window, the documents menu bar will be displayed in the window just above the TAC I/A Series title bar.

Issue Setpoints and Commands from Niagara objects are not being written to the BACnet points Environment I/A Series R2 WorkPlace Pro and UNC I/A Series MNB controllers Cause The BACnet objects are located in a PollOnDemand container. BACnet objects in the PollOnDemand container will only be polled when linked Gx objects (graphics) are viewed. In this particular case, these BACnet objects are not required to be displayed on graphic pages and thus they are not linked to any Gx objects.  being viewed Resolution Create GxText objects in the PollOnDemand container and link the BACnet objects' outputs to the GxText objects. With this, the BACnet objects will be polled when the PollOnDemand container is viewed. 

Issue Logs are not archiving in the ENC-520 and the error “Cannot append out-of-order or duplicate record” is being displayed Environment Niagara G3, ENC-520 Cause The timestamp of the archived logs were found to have a date code of the year 2106.  The error is because the ENC’s histories Last Timestamp is later that the ENC’s current station time.  Because of the incorrect timestamp, the ENC thinks its duplicating records so it will not append the records.  The ENC will not append any additional records to the histories until the ENC’s station time is later than the histories Last Timestamp time.   Resolution Delete the history folder from the ENC station Make sure ENC current time is correct

Issue Both the BACnet Comm and the BACnet IP Port are enabled in an ENC-520, but BACnet devices are not being discovered. The Discover button it grayed out. Environment Niagara G3 all version, ENC-520-2, ENC-410 Cause The ENC’s Object Id number (instance number) setting under the station’s BacnetNetwork/LocalDevice/ property was set to its default value of “-1”. Resolution A valid Object ID (instance number) must be entered for the station.  - Open the BACnetNetwork of the station and go to LocalDevice - Enter a valid instance number in the range of “0” to “4194303” in the Object Id property - save change You should now be able to Discover the BACnet devices.   

Issue What port is used for the Niagara R2 LON and Serial tunnel clients? Environment Niagara R2 Cause Want to modify network routers to allow port forwarding for tunneling Resolution The port used is the same port used as the UNC station. By default, the port is 80.  So, both tunnel clients also use port 80. If the station port is modified, the tunnel clients will use the new port number.

Issue A Fieldserver device was successfully commissioned in a Niagara R2 station using LON. The Lon Link Manager shows all related bindings with a status of "service_type_error".  None of them will bind. Environment Niagara R2 Cause Most Fieldserver devices using LON typically require a different service type other than the default 'standard' binding type. Resolution Change the binding type from 'standard' to 'critical'.  Then try to bind them.

Issue Can a Jace-Nxt installed with Niagara R2 be cleared and re-installed with Niagara G3?  It's from an existing jobsite that was R2 and is now being converted to G3. Environment Niagara R2 Niagara G3 Cause Jobsite is upgrading from Niagara R2 and G3. Resolution Yes it is possible.  Use remote desktop to connect to the internal Windows desktop and proceed to install Niagara G3 as is done on any Windows box. If the Jace-nxt has a hard drive, there will be plenty of free space to install Niagara G3.  If it has the flash drive, space is limited.  You may have to completely remove R2 to get the installation files for G3 copied over and installed.  A G3 license will have to be purchased for the unit. Note:  Tridium does not offer this 'upgrade' type of service.  It is a do-it-yourself task.

Issue Jobsite has some existing Microsmart and ASD controllers that will eventually be replaced with LON or BACnet controllers as budget allows.  Can they co-exist on a UNC-520? Environment Niagara R2 Cause Existing controllers that cannot be replaced right away due to budget limitations. Resolution The two drivers and their jar files will not conflict.  They can be both installed and work independent of each other.

Issue When emailing an alarm from the ENC the timestamp is always the time the alarm occurred; even when the Alarm email is due to an acknowledgement or return to normal. Environment G3, ENC's, JACE's Cause The default "body" property of the EmailRecipient contains only the %timestamp% which represents when the alarm occurred. Resolution Additional parameters can be added to the EmailRecipient "body" property to provide the "return to normal" and "acknowledged" timestamps. The return alarm timestamp can be added with %normalTime%. The acknowledged timestamp can be added with %ackTime%.  

Issue Procedures and processes to secure I/A Series G3 (AX) Systems Environment I/A Series Niagara G3 (AX) Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara G3 system. While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara G3 system more secure by carefully configuring and using.  Passwords Accounts and Permissions Authentication TLS and Certificate Management JACE-8000 Settings Additional Settings Please note that while all of these steps should be taken to protect your I/A Series Niagara G3 system, they do not constitute a magic formula.  Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn't mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it.  Note: Schneider Electric strongly recommends upgrading to the latest I/A Series G3 version 3.8 maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build included documentation to understand the behavioral impacts of the security enhancements. Download the Niagara AX Hardening Guide for more details.

Issue For example: >  Can a I/A Series G3 3.5.34 station in an ENC be edited with a 3.7.106 release of Workbench? >  Can a I/A Series G3 3.6.47 station in an ENC be edited with a 3.6.406 release of Workbench? Environment I/A Series G3 ENC or JACE controller (any 3.x release) I/A Series G3 Enterprise Server or Workbench software at any 3.x release Cause When engineering a mixed system it is advised that you use the correct version and brand of Workbench to connect. This insures that the modules on your Workbench will be compatible with the modules used by your station.  It is known that connecting with a different set of modules, i.e., different release, can result in a few odd behaviors or display problems or it may not allow you to connect at all. The incentive to upgrade is primarily for the new features. But it is also convenient to have all your stations at the same build so that you do not have to load different builds of Workbench to properly design and maintain the site. Resolution There are two solutions to this issue. Upgrade the older stations to the latest release. Install multiple copies of the I/A Series G3 software on the engineering computer and use the appropriate version when editing an existing ENC or JACE station.  When more than one version of the I/A Series G3 software is installed on the same computer, you must load the corresponding version of the Niagara platform daemon before attempting to use the Workbench software.  There are two ways to load the Niagara platform daemon.  When newer versions of the I/A Series G3 software are installed, a Windows Start menu folder is created for that version.  The "Install Platform Daemon" command will be found under that folder.  After running that command and allowing the Niagara Daemon service to start, you can use the "Enterprise Network Server" in the same Start menu folder to launch the corresponding release of the Workbench.  With any version of the I/A Series G3 software, you can manually install & start the platform daemon then start Workbench.  To set the version, start the Niagara console (<release directory>\bin\console.exe) for the version you want to run and then type the command "plat installdaemon".  You can then also start the workbench from that console window by typing "wb" at the command prompt.

Issue Browser wbapplet Guest user account login issue with I/A Series G3 versions 3.6.406 and 3.7.106 - indicates syntax error. Environment I/A Series G3 build 3.6.406, web module 3.6.406 I/A Series G3 build 3.7.106, web module 3.7.106.4 Cause Issue with web modules 3.6.406 and 3.7.106.4. Resolution Download and install the latest Consolidated Patches for the 3.7.106 environment.  This is available for download from The Exchange Download Center.

Issue I/A Series G3 HTML navigation tree example   Environment I/A Series G3 graphics Cause Need an example of creating a HTML navigation tree for I/A Series G3 graphic pages. Resolution The demo station that is installed with the I/A Series G3 software includes an example of a HTML navigation tree. Open the demo station in Workbench and go to Config > Services > UserService. Open up the user 'adminFrames'. From here you can see that the Web Profile used is the Handheld Wb Web Profile. The Nav File used is 'frames.nav'. In the station, go to Files and then the nav folder. Expand the folder and open the 'frames.nav' nav file. From here, we can see that the target ord for the home page is frames/home.html.  In Windows Explorer, navigate to \niagara\niagara-3.x.xxx\stations\demo\frames. You can see 3 files here, home.html, top.html and tree.html. Look at these 3 files to see how the tree and frames are created. The images folder contains the images used on the page.  Major steps. Engineer your station database and graphics as what you would do normally.  Create user(s) that uses the Handheld Wb Web Profile.  Create a nav file that points to home.html. Assign the nav file created in step 2 to user(s) created in step 1. Edit the home.html, top.html and tree.html according to your requirements.  User(s) created in step 2 will have the tree view when they log on from a web browser. 

Issue A Niagara G3 jace-6 has been operational in a building for more than two months with no reported problems.  End customer reported no updates to related graphics screens.  The jace-6 stopped responding on both of its ethernet ports.  A serial shell connection displayed the following information: IPL for NPM 6-E (PPC440EP) v4.00-6.32 ECC Press to stop autoboot... Autobooting... npm6xx startup version 7.00-6.41 Welcome to QNX Neutrino 6.4 on the NPM 6xx (ppc440) Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:01:f0:8e:5f:70 media: Ethernet none full-duplex status: active inet 143.83.31.10 netmask 0xffffff00 broadcast 143.83.31.255 inet6 fe80::201:f0ff:fe8e:5f70%en0 prefixlen 64 tentative scopeid 0x2 ------------------------------------------------------------------------- NPM6-E with T2023 JACE-2 Base Board detected SRAM mounted successfully at /sramopt LON interface detected # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGILL (0x4) at pc=0xfe4a26dc, pid=1773598, tid=1 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_34-b28 mixed mode, sharing) # Problematic frame: # Memory fault   Environment Niagara G3 jace-600, jace-600E, jace-700 Cause Internal memory issue Resolution The jace-6 cannot be repaired with a reported memory fault.  Replace it.

Issue During installation and commissioning of a MNL-800, a component labeled MFC21 on the backplane was damaged. Is it necessary to replace the backplane? It seems like the MNL-800 is still completely functional.  It's reading all of its inputs and the program logic is controlling the outputs accordingly. Environment MNL-800 Cause The issue is typically a ground loop between full-wave and half-wave devices or power supplies connected to the UIs and / or AOs.  MFC21 is a Multi-function Ceramic protection capacitor / varistor component connected between the internal +15 VDC and earth ground (not common).  This and the other 28 varistors on the base board provide various forms of protection.  MFCs have burned out in situations that contain one or more transformers and a combination of full-wave / half-wave devices. Connections (common) between these devices can cause undesired ground loops (especially where transmitters are involved). It may also be related to how the transformers are wired (e.g. 24H / 24G or one side tied to earth ground).  The MNL-800 is a full-wave power supply device. Resolution Review the power wiring of all connected I/O. Replacing the backplane is ideal because it will provide proper protection for the next voltage spike. Without a functional MFC21, the logic card may get damaged.