Building Automation Knowledge Base

Issue The paper version of the WorkPlace Tech Tool license request form includes the 815-637-5331 fax number.  This number has been disconnected and is no longer in service. The Schneider Electric Park Plant Customer Care Center has been relocated and the 815-637-xxxx series phone numbers have been disconnected. Environment WorkPlace Tech License Request Fax and email information Cause Incoming faxes to the Schneider Electric Buildings Customer Care Center are now handled electronically. Resolution Use of email is the preferred method for submitting a WorkPlace Tech Tool license request form although a fax number is still available. The preferred email address is IASeries.License@schneider-electric.com If it is necessary to fax the license request please use +1 888-560-3636.

Issue Graphic pipes are missing from Px pages when viewed via a Web Browser, however pipes are displayed when viewed via WorkBench. Environment Niagara G3, ENC-520 Cause The needed kitPxHvac module was missing from the ENC-520. It seems the kitPxHvac module was not installed to the ENC. Usually all required modules are automatically installed to the ENC at the time of a station install, but for some reason the kitPxHvac module was not installed. Resolution Manually install the kitPxHvac module to the ENC - Open the Application Director window for the ENC hosting the graphics - Double-click on Software Manager - Select the kitPxHvac module from list and click the “Install” button at the bottom of the screen. - Click the “Commit” button to install the kitPxHvac module to the ENC A reboot of the ENC should not be required. Open a new Windows Browser and browse to the ENC. The pipes should now display correctly in the graphics.

Issue Does the LCM driver support tunneling? Product Line TAC IA Series Environment R2 UNC with LCM driver Cause Tunneling is needed to make programming changes to the LCM's. Resolution It is possible to tunnel through the UNC to the LCM's, but it requires an RS-232 connection from the UNC to one of the LCM's.  See the LCM Integration Guide F-27422-2 for details.

Issue When opening a G3 graphic page the data points are shown but the graphic itself does not always display. Environment G3, niagara, WorkBench Cause The exact cause has not been determined. Resolution Installing 3.7.106 with the patches or installing 3.7.106.5 corrects this issue.

Issue JACE-645-R2 will not learn BACnet devices on its MSTP trunk and is spewing out the following message in the Application Director. devctl rx frame failed: No error java.lang.RuntimeException: mstp rcv failed at tridium.nre.qnx.mstp.QnxMstpDriver.rcvFrameJNI(Native Method) at tridium.nre.qnx.mstp.QnxMstpDriver.access$0(QnxMstpDriver.java) at tridium.nre.qnx.mstp.QnxMstpDriver$MstpTrunkListener.run(QnxMstpDriver.java:287) at java.lang.Thread.run(Unknown Source) Environment G3 version 3.8.37 Cause Issue with the platform drivers in G3 (3.8.37) that interface with R2. Resolution Install a clean distribution using 3.6.47 and commission with 3.6.406.

Issue A new license file was provided for a UNC so that it could communicate with other UNCs at a jobsite.  The UNC was a spare unit being used in the office for testing.  When trying to install the new license with Workplace Pro, a pop-up error appears immediately indicating:  Unable to install license. Environment UNC (all versions and models) Cause Re-licensing a test UNC Resolution Use the summary tab in admin tool to ensure there is enough free file space.  If not, open the remote library and delete unnecessary files. The free file space number will increment after a few seconds (no need for a reboot). Now, install the new license.

Issue How to determine which MNL controllers (profile and version number) are integrated to a Niagara R2 or G3 station. Environment Niagara R2 lonSiebe jar file Cause Quick reference Resolution Use the LonWorks Device Manager and cross-reference the listed MNL controllers to the table below: siebe                         MNLRF103                             SIEBE                          80:0:16:50:14:4:4:1      siebe                         MNLRF2                                  SIEBE                          80:0:16:50:14:4:4:2  (version 2)    siebe                         MNLRF3                                  SIEBE                           80:0:16:50:14:4:4:3   (version 3) siebe                         MNLRH103                             SIEBE                           80:0:16:50:33:4:4:1      siebe                         MNLRH2                                  SIEBE                           80:0:16:50:33:4:4:2     (version 2) siebe                         MNLRH3                                  SIEBE                           80:0:16:50:33:4:4:3      (version 3) siebe                         MNLRR103                             SIEBE                           80:0:16:50:1e:4:4:1      siebe                         MNLRR2                                  SIEBE                           80:0:16:50:1e:4:4:2    (version 2)  siebe                         MNLRR3                                  SIEBE                           80:0:16:50:1e:4:4:3      (version 3) siebe                         MNLRS1                                  SIEBE                           80:0:16:50:1e:4:4:10     (satellite 1) siebe                         MNLRS2                                  SIEBE                           80:0:16:50:1e:4:4:11     (satellite 2) siebe                         MNLRS3                                  SIEBE                           80:0:16:50:1e:4:4:12     (satellite 3) siebe                         MNLRS4                                  SIEBE                           80:0:16:50:1e:4:4:13     (satellite 4) siebe                         MNLRV2                                  SIEBE                           80:0:16:50:a:4:4:9       (version 2) siebe                         MNLRV3                                  SIEBE                           80:0:16:50:a:4:4:a       (version 3) siebe                         MNOTPVA3                             SIEBE                           80:0:16:50:a:4:4:8       siebe                         SiebePEC                               SIEBE                           80:0:16:50:1e:4:4:0      

Issue Does the MNB-1000-15 Remote I/O Module supports pulse inputs? Environment I/A Series MNB-1000-15 Remote I/O Module Cause How to use the MNB-1000-15 remote I/O module universal inputs to read pulse inputs. Resolution Standard pulse input is supported on the MNB-1000-15 universal inputs (UI1 to UI6).  Minimum Rate 1 pulse per 4 minutes   Maximum Rate 1 pulse per second Minimum Rate 1 pulse per 4 minutes. Maximum Rate 1 pulse per second.

Issue Structured SNVTs disappear from database following a LearnNv. Product Line TAC IA Series Environment G3 versions 3.6.406, 3.7.106, 3.8.37 Cause Modifications made to the LonWorks jar. Resolution Download and install the new LonWorks jar for the revision in question. See Lonworks 3.8 to obtain the latest LonWorks modules.

Issue JACE 645 Ethernet ports usage Environment JACE 645 Network Controller Cause JACE 645 has 2 Ethernet ports.  Resolution LAN1 is the primary network port for the JACE645. As per the JACE Install and Startup Guide, LAN2 (secondary port) can be used in the following scenarios.  Intended usage (of LAN2) is for: - Isolating a "driver's" Ethernet traffic from the primary (LAN1) interface. OR - In some cases, LAN2 may be set up with a standard, fixed, IP address that is used only by a company's service technician, when on site. This allows access to the JACE without disconnecting it from the customer's network, or without connecting the technician's service PC to the customer's network (which might go against local IT security policies). Note that only one LAN port can be set as DHCP. If enabling LAN2, you typically specify another (network) static IP address and the appropriate subnet mask. Also note the following: If enabling both LAN ports, note that the LAN1 IP address and LAN2 IP address must be on different subnets, otherwise the ports will not function correctly. For example, with a typical "Class C" subnet mask of 255.255.255.0, setting Interface 1=192.168.1.99 and Interface 2=192.168.1.188 is an invalid configuration, as both addresses are on the same subnet. A JACE does not provide IP routing or bridging operation between different Interfaces (LAN ports, GPRS, dialup). All of this also applies to the "third interface" provided by the "WiFi option" if installed in a JACE (at the time of this document, available for a JACE-700 only). However, it is likely the WiFi interface will be used as the primary interface in most cases (no LAN cabling available to the JACE).

Issue Field engineer needs to convert a TAC I/A Series project from R2, GCM or Signal but can not find the link on iPortal2. Environment TAC I/A Series project files to be converted to SBO Cause User does not have permission to make a purchase through the iPortal2 website. Resolution The field engineer / technician submitting the job must have the right to make purchases through the iPortal2 web site http://iPortal2.schneider-electric.com. The branch or partner office iPortal administrator must give the engineer/technician the right to make purchases through the iPortal site.   The user's purchase limit must be set to at least one dollar ($1).

Issue Using 3.7.106 and want to display a PDF file on a Niagara G3 / AX graphic. It's been done in the past but with "Default Web Profile" "Applet Reload on Hyperlink" set to "False" the PDF does not display. Is there a way to do it without setting the "Applet Reload on Hyperlink" to "True"? Product Line TAC IA Series Environment Niagara G3 / AX revision 3.7.106 and higher Cause More secure changes made to G3 / AX Resolution Instead of creating a hyperlink button with hyperlink: file:^blahblah.pdf Use: http://137.19.60.55/ord?file:^blahblah.pdf This opened the PDF in the browser (it left the default web profile but the back button returned to it).

Issue A BVSPP point of a MNB controller cannot be changed from G3. MNB controller is at firmware version 1.43. An “ASN error:” is displayed for value in the BACnet Discovery window when discovered in G3. Environment G3, WorkPlace Tech, All MNB controllers Cause The MNB application’s BVSPP object was initialized with “NA” in WorkPlace Tech.  The BVSPP object should only be initialized with “On” or “Off”.  The ability to initialize an object with “NA” will be removed in a future version of WorkPlace Tech. Resolution Use WorkPlace Tech to change BVSPP initialized with “NA” to either “On” or “Off” and download application to controller. If the point still cannot be change from Workbench, then delete the point in the ENC/ENS database, rediscover it and add it back to the G3 database.  The BVSPP point can now be changed from G3.  

Issue Getting a “500: Internal Server Error” when clicking on hyperlink in G3 station. The following error is also displayed in the Application Director window: javax.baja.naming.SyntaxException: Illegal char '?' in body: /ord?file:^gfx_Lib/www/nav.htm javax.baja.naming.SyntaxException: Illegal char '?' in body: /ord?file:^gfx_Lib/www/Top.htm Note:  The last part of the file path after "file:" will be different based on your station's file structure.   Environment Niagara G3, version 3.8.37 Cause A second “/” mark was being added to the hyperlinks’ paths in the htm file.  In this case, hyperlinks in the Top.htm file are the culprit. The Hyperlinks read: To date, Tridium has not determined how the second slash gets added.   Resolution The solution is to find out which htm file contains the error and correct it. Use WorkBench’s Text File Editor to examine the htm file to find the error.  - Open the station’s Files folder  - Right-click on the htm file and select “Text File Editor” - Once the htm file is found that contain the error, remove all second slashes.      Change <a href="/ord/?...     To          <a href="/ord?... (removed the second “/”) - Save changes and reopen page in new browser Note: There may be a need to clear all caches.   

Issue Is R2 or G3 compatible with JAVA 8? Product Line TAC IA Series Environment R2 G3 Cause Oracle released Java 8 Resolution At the time of the creation of this article (February 17, 2015) no versions of R2  have been tested with Java 8 and therefore Java 8 is not supported until further notice.  As of March 15, 2015, Tridium has now tested the latest maintenance builds of G3 releases 3.6, 3.7 and 3.8 and found that they appear to work properly with Java 8 update 31.

Issue Replaced a Niagara R2 UNC with a Jace-645 embedded with R2.  LON communications was stable at first but now it is intermittent.  Environment Niagara G3 - AX version 3.6.47 or higher Niagara R2 version 535 Cause The intermittent LON communications issue was identified and a supporting jar file in R2-535 needs to be upgraded. Resolution Replace the lonworks jar file with this updated version:   lonworks-2.301.535c

Issue BACnet points are not updating in the UNC after the replacement of a BACnet device. Environment Niagara R2, UNC 520 Cause Tech replaced a drive from one manufacturer with a drive from a different manufacturer. The BACnet device object in the UNC was reused. Since the replacement drive was not the same model or manufacturer as the one being replaced, the BACnet points between the two devices are different. The points in the replacement device do not match the points in the reused BACnet device object in the UNC. Resolution The solution would be to delete the BACnet device object in the UNC, discover the replacement device and learn it into the UNC.

Issue Unable to display Traditional Chinese characters in Workbench graphics and Alarm Portal Product Line TAC IA Series Environment I/A Series G3 version 3.7 and 3.8 Cause There was change between I/A Series G3 version 3.6 and 3.7. A lexicon tool was added so that the user could use a default set of lexicons (modules). This is a change in the implantation of lexicons in I/A Series G3. The issue was that the default lexicon module for (zh) did not include the font parameters causing the software to not know how to display the Unicode characters. Resolution The I/A Series  lexicon tool can be used to build and enhance the module by the user for deployment on sites. In addition, the I/A Series G3 still supports the use of the previous mechanism that used lexicon files. The lexicon file basically overrides the default module.  Copy the lexicon zh folder from I/A Series G3 3.6 (\niagara\niagara-3.6.xxx\lexicon\) Create a lexicon folder under '\niagara\niagara-3.7.xxx\' in I/A Series 3.7 (or 3.8) and add zh folder copied in step1. Exit the Alarm Portal, stop the station and close Workbench. Update the system.properties file (see below) which is located in '\niagara\niagara-3.7.xxx\lib\'. Change the field to 'niagara,lang=zh' and save.  # This system property is used to override the the default locale. # If not specified, then the VM will attempt to use a default based # on the current operating system settings. This value should map # to a lexicon directory. niagara.lang=zh Launch Workbench and Alarm Portal and verify that the issue has been resolved. 

Issue A BACnet device on the Bacnet internetwork is broadcasting an incorrect time and this is being reflected in the ENC's. How can this be disabled? Environment G3 ENC's JACE's BAcnet Cause Third party BACnet device broadcasting incorrect time periodically on the internetwork. Resolution By default "Time Synch Allowed" is enabled in the ENC and JACE's.  This can be disabled by the following steps. 1. Open the ENC station  with WorkBench then open Config, Drivers, BacnetNetwork and BacnetComm. 2. Right click on Server and View the Slot sheet. 3. Right click on timeSyncAllowed, right click on ConfigFlags, uncheck the box next to Hidden and click OK.  4. Right click on Server - View - Properties and change Time Synch Allowed to false and save.

Issue Which versions of SIGNAL can be migrated to SBO? Environment SIGNAL Cause The migration manual does not identify which versions are accepted. Resolution Two versions of SIGNAL can be backed up and migrated to SBO:  Version 4.4.1 (for Windows 95/98) and Version 5.0.0 (for Windows XP).