Issue Java is no longer available or supported in most web browsers so accessing Niagara using the Java Applet is no longer possible Product Line TAC IA Series Environment I/A Series G3 Enterprise Server/Jace 3.8U4 I/A Series N4 Enterprise Server/Jace 4.4U3 and subsequent Cause Oracle announced the end-of-life of Java SE 8 (Standard Edition). As of January 2019, free public updates for commercial users are no longer available. Customers accessing Niagara with the Java Applet/Web Start are impacted by this change. Those who have upgraded to full HTML5 versions for your browser front-end will not be affected. For customers who use the Java VM and Java Web Start for their legacy systems, Tridium has developed a suitable alternative, the Niagara Web Launcher. Resolution The Niagara Web Launcher application is now available. You can download Niagara Web Launcher using the following link: 64-bit systems: Web Launcher for 64 bit, 32 bit OS 32-bit (-x86) systems: Web Launcher for 64 bit, 32 bit OS Niagara Web Launcher download links are also available from the Niagara station login page. Niagara Web Launcher support is included in Niagara versions: 4.4U3 –Included in (4.4.94.14). 4.7U1 - Included in (4.7.110.32) Subsequent releases of Niagara 4 will include Niagara Web Launcher support. A patch for Niagara 3.8 U4 can be downloaded from here.  Copy web.jar module version 3.8.403.1 into the modules folder of your Niagara AX 3.8 U4 workbench or supervisor station.  This module may also be installed on JACE platforms.  To use Niagara Web Launcher, Web Start must be enabled in the Web Service of the station.

Issue WorkPlace Tech Tool reports Database Error when attempting to link to the output of a copied custom object. The displayed error message shows the name and attribute of the object being connected along with the error "Exception error occurred during WriteProperty [0xE0330020]". Product Line TAC IA Series Environment WorkPlace Tech Tool Software Version 5.7.x or newer Workplace Tech application file containing a custom object copied from another WPT application. Cause Unknown, believed to be an internal Visio error. Resolution Open the application file in the WorkPlace Tech Tool software and select the page for the Custom Object that is reporting the error. Break the connection (disconnect the link) between the Custom Object output tag and the corresponding source object. When breaking the link, it is suggested that the wire link be dropped onto the drawing page before being re-linked. Select the link and reconnect it to the proper object. It may be necessary to perform this unlink and relink operation for all output tags within the Custom Object that had been copied from another WPT application file.

Issue The following Popup window is displayed when attempting to open WorkPlace Tech. WPTech Unable to load WorkPlace Tech Ribbon for Visio. There was a problem loading the WorkPlace Tech Fluent Ribbon for Visio, therefore, it will be unavailable. Product Line TAC IA Series Environment Visio 2010, 2013, 2016, and 2019 WorkPlace Tech Tool release 5.8 or later Cause If Visio crashes when a third-party ribbon bar function is in use, Visio may lockout that ribbon bar, believing that something on that ribbon bar caused Visio to crash.  In this case, a menu function, selected from the WorkPlace Tech (WPT) ribbon bar was being processed at the time Visio crashed, therefore Visio locked out the WorkPlace Tech ribbon bar. This is a system protection mechanism built into the ribbon bar handler in all Microsoft Office applications including Visio.   Resolution To re-enable the WorkPlace Tech ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech. Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'WorkPlaceTech.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech ribbon bar will be available in WorkPlace Tech.  

Issue Documentation supplied with new UNC, ENC, or Jace 8000 was discarded.  Is there a way to determine the default, the factory-defined IP address, for the Ethernet port on the controller? Product Line TAC IA Series Environment I/A Series (Niagara) R2 UNC I/A Series (Niagara) G3 ENC Niagara N4 or G3 Jace 8000 Cause Lost or discarded document, shipped with the controller, that contained the configured IP address. Resolution The default Ethernet IP address for an I/A Series (Niagara) UNC or ENC is based on the serial number and type of device. For a UNC or ENC, the default address is 192.168.1.14X where X is the last digit of the device serial number.  The default serial number is found on a sticker on the controller circuit board.  This sticker has the full model number, date code, and the serial number of the controller.  The serial number is preceded with S/N:.The subnet mask is 255.255.255.0 in all UNCs, ENCs, and Jace 8000 The default address base address (192.168.1.140) is the same for all UNC-410, UNC-510, UNC-520, ENC-410, and ENC-520 controllers. The default IP address of a Jace 8000 for PRI (LAN1) is 192.168.1.140.  SEC (LAN2) is by default disabled.

Issue Strange characters are displayed in the display of a VT7000 and SE7000 Series thermostat. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause The thermostat has experienced a brownout condition. Any time the power drops below 16-17Vac for a 1/10 of a second or so it will cause this condition. Resolution The thermostat still updates to the BMS correctly; it’s only its display that’s affected.  Cycling power to the unit will clear the issue. However, if the brown out condition is not addressed, it can happen again. If a repeated brownout issue at the site cannot be corrected, consider powering the controller with an UPS.   

Issue The client is inquiring about the availability of  I/A Series R2 and G3 objects for interface with the SE7000 Series Room Controllers Product Line TAC IA Series, EcoStruxure Building Expert Environment I/A Series R2 UNC I/A Series G3 ENC SSL SE7000 Cause Not able to locate shadow objects with matching LonWorks program IDs within the existing I/A Series R2 and G3 modules. Resolution A set of new modules have been generated for use with the new SE7000 Series Room Controllers.  The new objects interface with the following program IDs. R2 objects: Se7273         (80:00:10:55:00:04:04:20) Se76Pir         (80:00:10:55:00:04:04:21) Se76RhPir    (80:00:10:55:00:04:04:22) Click to download ... lonSchneider-2.301.330.zip Click to download ... lonSchneider-2.301.431.zip Click to download ... lonSchneider-2.301.534.zip G3 objects: Se72_73.lnml (80:00:10:55:00:04:04:20) Se76Pir.lnml (80:00:10:55:00:04:04:21) Se76RhPir.lnml (80:00:10:55:00:04:04:22) Click to download ... lonSchneider-3.5.39.1.zip Click to download ... lonSchneider-3.7.17.zip The 3.5.39.1 module should be used with G3 versions 3.5 and lower. The 3.7.17 module should be used with G3 versions 3.6 and higher.

Issue There are only fan coil control applications available and unable to find the Heat Pump Application. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The end-user might be using an incompatible controller for their application. Resolution Heat pump applications for the SE8x00 product are scheduled for availability in the 4th quarter of 2014.

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below:

Issue AutoCAD wiring symbols for I/A Series MicroNet LON controllers (MNL) Product Line TAC IA Series Environment I/A Series Micronet LON controllers (MNL) Cause The files are not available on the Download Centre Resolution The files can be downloaded from here.

Issue I/A Series G3 Workbench License Manager build 3.8.37 will not automatically import from the License Server even when the connection to the Internet is active.  The result is the display of the Request License dialog box that provides the host ID and email information for Schneider Electric. Product Line TAC IA Series Environment I/A Series G3 Workbench 3.8.37 Cause The issue is related to a setting within the brand.properties file included with the 3.8.37 install.  This setting enables or disables the online license server request function within Workbench.  The setting was inadvertently set to disabled (false). Resolution The issue can be easily resolved by changing the setting by one of the two methods shown below. Method 1 - Replace existing brand.properties file with an updated version Close Workbench Download the following zip file with the updated brand.properties file > brand.properties Use the Windows Explorer and navigate to the lib directory under the niagara-3.8.37 directory Extract the updated file from the zip and replace the existing brand.properties file Method 2 - Manually edit the brand.properties file Close Workbench Use the Windows Explorer and navigate to the lib directory under the niagara-3.8.37 directory. Open brand.properties using a text editor such as Notepad Carefully edit the following line changing the false to true:      license.onlineRequest=false ... update to license.onlineRequest=true Save the file Workbench will now import licenses from the license server.

Issue The OrOr object in MNB controllers always reports that it is "ON". Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series MNB Controllers  Cause  Input to the OrOr object is inverted and has nothing attached to it. When an "OR" input property of a logic object is inverted with nothing attached to it, the input will be seen as an "Off," resulting in an output of 100. Resolution If the input of an OrOr object is not connected to I/A Series BACnet controller, an "OR" input should not be inverted.   If another object outputting a "NA" is attached,  the "OR" input will function correctly.

Issue What hardware is required to connect directly to a BACnet/MSTP trunk containing just MNB controllers? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Balance Tool Cause Replacement for the previously recommended adaptor, the B&B Electronics model USOPTL4. Resolution Purchase the following part: MNB-ROAM-IA.  This is used in conjunction with WorkPlace Tech.

Issue Upgrading Visio. Should WorkPlace Tech be uninstalled first? Product Line TAC IA Series Environment I/A Series WorkPlace Tech Cause Software upgrade Resolution Un-install both WorkPlace Tech and Visio.  Then install Visio following the instructionsWorkPlace Tech Installationand Workplace Tech 5.10.4 Release Notes 

Issue When attempting to run standalone WorkPlace Tech the following message is displayed. After attempting to launch Microsoft Office Visio, WorkPlace Tech was unable to access Visio functionality. Product Line TAC IA Series Environment Workplace Tech version 5.8.X and 5.9.X Microsoft Windows 7 and Windows 10 Microsoft Office 2013 and Office 2016 Microsoft Visio 2010 and 2013 Other versions of Office and Visio may apply.  These have known issues corrected by this procedure Cause A non-approved version of Microsoft Visio (Visio 2013/2016) was installed. Microsoft Visio 2013/2016 was uninstalled and replaced with Microsoft Visio 2010 SP2. It is suspected that the uninstall of Microsoft Visio 2013/2016 left behind files causing this issue. Resolution Uninstall Workplace Tech, Visio 2010 SP2, and Office 2013 and reinstall the software in the following order: Microsoft Office 2013 or Office 2016 Microsoft Visio 2010 SP2  Workplace Tech 5.8.X or WPT 5.9.X Run Visio standalone, shut it down, and then run WorkPlace Tech.

Issue When importing an application file created or previously edited with release 3.2sp1 of WorkPlace Tech, a "Workplace Tech Tool - Visio" error window is displayed:  "Cannot find the WorkPlace Tech add-ons for Visio.  WorkPlace Tech functions will be unavailable" Product Line TAC IA Series Environment WorkPlace Tech Tool software release 5.7.4 WorkPlace Tech application file created or edited with WorkPlace Tech Tool software release 3.2sp1. Cause The Visio stencil pages referenced in the application file cannot be found in the location specified in the application file. Resolution This is not a fatal error.  It occurs because WorkPlace Tech cannot locate the Visio object stencil files referenced in the existing application drawing file.   Click the [OK] button to ignore the error message and continue with the application file upgrade.  The error message is displayed because the default location for the stencils has been moved starting with WorkPlace Tech version 5.7.4.  During the application file upgrade, the proper stencils, as specified in the original application file, will be located and attached to the application. After clicking the [OK] button, WorkPlace Tech will display a Windows message box indicating that the application must be converted to WorkPlace Tech (WPT) 5.0 format before it can be modified or downloaded.  The message ends with a prompt asking the user if they would like the application converted.  Clicking [Yes] will allow WorkPlace Tech to process the application file and convert it to the current file format.  This is the required choice if the user intends to use the imported application in the current version of the WorkPlace Tech Tool software. Clicking [No] will bypass the conversion leaving the incompatible application open in WorkPlace Tech. Clicking [Cancel] will abort the import process.

Issue The BACnet object goes into fault when writing a NaN to an MNB controller. Product Line TAC IA Series Environment I/A Series MNB VAV I/A Series MNB 70 I/A Series MNB 300 Cause Firmware 1.424 and higher responds to receiving a NaN with an Error: "value out of range".  In firmware 1.420 it would accept the NaN and respond with a normal acknowledge message.  This is a result of a change required for BTL compliance. Resolution A slight setup change can accomplish the same result without causing the object to go into fault.  In the ENC edit the properties of the AVSPP object and set the fallback to "null".  Go to the slot sheet of the object being overridden to hide the "Set" option.  This will prevent the operator from attempting to send a NaN that causes the fault.  When a right-click override is performed only the emergency (priority1) and Override (priority8) choices are displayed.  When the override expires or the object is manually put back into “auto” the “fallback” value is output which is “null” and that is accepted at the controller and serves the same function as sending a NaN.

Issue What are the email addresses used for I/A Series license requests? Product Line TAC IA Series Environment I/A series license Cause Request license to upgrade existing devices. Resolution All TIP and end customer WorkPlace Tech license requests and Niagara license requests are emailed to: bms.licensing@se.com

Issue What port is used for the I/A Series G3/N4 LON and Serial tunnel clients and can it be changed? Product Line TAC IA Series Environment I/A Series G3/N4 Enterprise Server I/A Series G3 ENC I/A Series Jace 8000 Cause Requires port change due to routing or firewall conditions. Resolution By default, the G3/N4 Tunnel Service utilizes TCP port 9973. The port used for tunneling can be configured by modifying the Server Port within the tunnel service properties. Example: Configuring the Lon tunnel server In the palette sidebar, open the lontunnel palette. Open the ENC/JACE station and expand its Services folder. If no TunnelService exists, paste one from the palette into the Services folder. If a TunnelService does exist, go to the next step. Note: Only one TunnelService is needed in a station's services, and it can hold multiple tunnel components (both LonTunnel and (serialTunnel). The TunnelService in the lontunnel module is identical to the TunnelService in the (serial) tunnel module. From the palette, paste a LonTunnel under the station's TunnelService The station should now have a TunnelService and a child LonTunnel component. Configure the properties and modify the TunnelService server port if required. Note: If the ENC/JACE has multiple LON ports (and corresponding LonNetworks), the same number of LonTunnel components can be copied under the TunnelService. Each LonTunnel component can then be associated with a particular LonNetwork (by its LONn device name). For any station user that needs to Lon tunnel, make sure the user has admin write permissions for the LonTunnel(s). Example: Configuring the serial tunnel server In the palette sidebar, open the tunnel palette. Open the ENC/JACE station and expand its Services folder. If no TunnelService exists, paste one from the palette into the Services folder. If a TunnelService does exist, go to the next step. Note: Only one TunnelService is needed in a station's services, and it can hold multiple tunnel components (both LonTunnel and (serialTunnel). The TunnelService in the lontunnel module is identical to the TunnelService in the (serial) tunnel module. From the palette, paste a SerialTunnel under the station's TunnelService. The station should now have a TunnelService and a child SerialTunnel component. In the SerialTunnel's property sheet, expand the "Serial Port Config container." Enter the COMn "Port Name" used by the target driver network, and specify other parameters as defined in the network's configuration. If the ENC/JACE has multiple serial-type driver networks (and corresponding COM ports), the same number of SerialTunnel components can be copied under the TunnelService. Each SerialTunnel component can be associated with a particular network (by its COMn port name) and set the other parameters accordingly. For any station user that needs to the serial tunnel, make sure the user has admin write permissions for the SerialTunnel(s).

Issue Platform connection using TLS fails. Standard HTTP connection of port 3011 successful. Product Line TAC IA Series. Environment I/A Series Enterprise Server Cause TLS platform connection fails immediately and throws an exception in Workbench. Note that the Niagara Daemon is running and a non-TLS HTTP connection is successful. No station is currently running on the PC. All stations are stopped.   Example exception- SEVERE [08:45:58 02-Sep-20 CDT][wb.shell] Error connecting to platform daemon at localhost: GET /platformInfo javax.baja.naming.UnresolvedException: platformssl: Resolution A possible cause is a zero-byte file size bog file in the Daemon Home 'stations' folder. Check all of the station folders in Daemon Home, searching for any bog file that is zero bytes in size. Look for 'Config.bog.lock' files as one could be orphaned when a station running in the Niagara daemon were to stop unexpectedly, such as the system reboots suddenly or the PC is powered down. Remove all files that are zero bytes in size. Remove any 'Config.bog.lock' files. Test the TLS connection for a successful connection.

Issue Niagara Runtime Environment (NRE) fails Console output when starting Workbench Product Line TAC IA Series Environment I/A Series N4 Workbench Cause An issue has occurred in the security of the user home for the installation of Niagara N4 Resolution If the Workbench fails to launch. Open the Console for the build you are trying to use by following the illustrated path and clicking the console.exe If the Console output is as shown under "Issue" above, follow the path shown below. Complete the instructions in the illustration below. Open the Workbench as you normally would.