Building Automation Knowledge Base

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 I/A Series R2 oBIX User Guide Product Line TAC IA Series Environment I/A Series R2 oBIX driver Cause The R2 oBIX User Guide is not installed with I/A Series R2 version 529 and earlier. It is available with the installation of I/A Series R2 version 532 and later.  Resolution Niagara release 2 oBIX User Guide

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 There is a compatibility issue between Revision 2 MNL controllers and S-Link sensors. This incompatibility is noticed when a later production S-Link sensor is connected to an older Revision 2 controller. When the sensor is connected to the controller, 88.8 appears on the sensor’s display window along with all of the other LCD icons. The display never recovers from this mode, which makes the sensor non-functional. Product Line TAC IA Series Environment MN-Sx sensors MNL-10Rx1 and MNL-20Rx1, where x denotes profile type (F, H, R) MNL-V1RV1, MNL-V2RV1, MNL-V3RV1 Cause New MN-Sx production S-Link sensor firmware is not compatible with older Revision 2 MNL controllers. Resolution Newer model S-Link sensors have been released to address this issue. The new part numbers are MN-S1-2, MN-S2-2, MN-S3-2, MN-S4-2, and MN-S5-2. The MN-Sx-2 model line was designed and verified to work with older Revision 2 controllers.  Reference TPA-RKFD-09-0028-00 for more details. Please note that the new MN-Sx-2 S-Link sensors are only for use with older Revision 2 controllers.

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.

Issue The user of OpenLDV and Echelon U10 USB adapters with their Engineering Laptops are concerned that Niagara 4.9 does not have a 32-bit installation option. Product Line TAC IA Series Environment I/A Series N4 4.9 and later Windows 10 64 bit Cause OpenLDV 5 runs as a 32-bit application on both 64-bit and 32-bit versions of Windows. It cannot be called from a 64-bit client application. In order to use OpenLDV on 64-bit Windows, the OpenLDV client application must be compiled and run as a 32-bit application. Prior to Niagara 4.9, some customers used the Niagara 32-bit installer exclusively, which no longer exists, so that they could use OpenLDV.  Resolution The 64-bit Niagara 4.9 Windows install includes a 32-bit daemon application that, without any extra configuration, provides a bridge between 64-bit Niagara and 32-bit OpenLDV. This means that technically, the Echelon U10 USB adapter should work in 64-bit Niagara version 4.9 and newer, on a Windows host (Tridium cannot guarantee operation). There is no longer a need to install 32-bit Niagara, and in fact, it is no longer available. 

Issue The Niagara 4 JACE's platform daemon fails to start making it impossible to login and configure using Workbench tools such as the Commissioning Wizard or Dist File Installer. The error within the serial shell typically indicates ... /proc/boot/ksh: niagarad: cannot execute - No such file or directory. Product Line TAC IA Series Environment Niagara 4 JACE-603 JACE-645 JACE-600E JACE 8000 Cause This can occur as a result of an Incorrect or failed upgrade or improper downgrade without first installing a clean distribution. Resolution Requirements - You will need the following to complete the recovery steps: A terminal emulator such as PuTTY A SFTP client such as FileZilla Serial-Shell cable for your JACE hardware model (specified in the .PDFs below) The Niagara 4 Clean Dist file for your JACE hardware A zip file utility such as 7-Zip The hardware and startup documentation for your JACE model (provided with Niagara 4 installer) Obtain recovery files from the Niagara 4 Clean Dist File for the matching hardware: The clean dist files can be found in your Niagara4 $system_home directory, or in your Niagara 4 image files under the cleanDist directory or in the overlay\cleanDist directory. Open the .dist file for your JACE's platform using a zip utility like 7-Zip and extract the zip/n4clean.tar.gz file. Also, extract the dev/shmem/n4-xxx.image file, where xxx will be different, depending on the JACE's platform type. JACE 300 ... qnx-jace-n4-npm3xx-etfs2048-clean.dist JACE 600 ... qnx-jace-n4-npm6xx-etfs2048-clean.dist JACE 600E ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 603 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 645 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 700 ... qnx-jace-n4-javelina_booke-etfs2048-clean.dist JACE 8000 ... qnx-jace-n4-titan-am335x-clean.dist Make a Serial Connection to the JACE The .PDFs in the N4 documentation set describe how to make a serial connection to a JACE in the "system shell" section(s) of each document. Once connected, the controller will boot and display the "login:" prompt.  Enter your Platform credentials. After login, either a "#" or "$" shell prompt or configuration menu similar to the following is shown.   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011     dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255         inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------     1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot     L.  Logout     Enter choice:   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011   dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255             inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------   1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot   L.  Logout   Enter choice: Verify correct system time and update as needed The RTC time may not be correct if the unit has been unpowered for longer than the on-board capacitor backup period. Using menu ... the first item in the menu list allows you to Update System Time.  The current date/time is displayed. Enter the new date/time in the form YYYYMMDDhhmm[.SS].  Note that entering the seconds is optional. For example: 201801111420 for 11-Jan-2018 at 8:20am UTC or 8:20am CST. Enable SFPT The Secure FTP service is not enabled by default on a JACE.  Enable the SFPT from the menu above or the shell prompt (if required). Using menu ... the fourth item in the menu list allows you to enable SSH/SFTP.  Enable it now, using port 22. Once enabled, enter another choice, "sh" (without quotes).  This will give you the "#" or "$" prompt that you need. If you could not enable from the menu in the step above, manually start by issuing the command tsudo syssh_sshcfg at the shell prompt.   If the command fails, issue the syssh_sshcfg command.  If the command fails again, enter the following ... $ cd /sys/bin ... then enter $ ./syssh_sshcfg ... then enter Transfer the n4clean.tar.gz and OS Image Files using SFTP Client Using an SFTP client such as FileZilla, transfer the n4clean.tar.gz file previously extracted for the platform from the clean dist file to the JACE's /zip directory. If the transfer fails with a permissions error, issue the command tsudo chmod 777 /zip at the shell prompt and try it again. Next, transfer the .image file you extracted from the clean dist file to the JACE's /dev/shmem directory. Run osupdate From the login menu prompt, type sh.  This will exit the menu system and enter the shell mode.  At the "#" or "$" shell prompt, issue the command osupdate.  After a short delay, the shell prompt will return. Reboot the JACE Finally, reboot the JACE.  This can be done by issuing the command shutdown hf 0 at the shell prompt.  When the JACE restarts, the unit will automatically process the clean dist file.

Issue A Niagara R2 UNC is installed in a remote location with internet service provided by Comcast. Until now, a static IP address was provided by Comcast allowing for a static IP address to be provided to the UNC. Comcast has now switched to dynamically assigned IP addresses. Each time the installed internet router is power-cycled, it will receive a different IP address. Can the UNC be enabled to support DHCP and continue to be remotely accessible? Product Line TAC IA Series Environment Niagara R2 Cause Comcast's changes in internet service policy Resolution Niagara R2 stations support DHCP but the IP address must be 'reserved' within the DHCP server. See the Niagara Networking and Connectivity Guide, page 3-23. In this application, there is no DHCP server. Enabling DHCP will not allow for remote connectivity to continue as it did. Review the requirements with Comcast to determine if they can provide a solution involving a reserved IP address for the installed router. This will allow the UNC to retain its static IP address and maintain remote connectivity. Alternatively, dynamic IP addressing can be "out-sourced" to a 3rd party company. See the Niagara Networking and Connectivity Guide, page 5-22. The company TZO and its website www.tzo.com has changed to www.dyn.com and their most often-used product is dyndns-pro (http://dyn.com/dns/dyndns-pro). There is a small annual service fee but it has worked successfully with Niagara R2 applications. There is also a free version available at http://free.domain.name/en.html?domain=dyndns-home.com.