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.

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 The file structure is incorrect for MNL-FLOW-BAL 3.0 software for use with Windows 7 64 bit OS.  The FlowBalance.exe needs to be run in Windows XP (Service Pack 3) compatibility mode. Product Line TAC IA Series Environment Windows 7 64 bit MNL-FLOW-BAL Balance Software Cause The paths for certain files being used by the software cannot be modified. When loaded on a 64 bit PC, the default paths are incorrect for the rest of the processes to find. Resolution Manually create and insert the folder structure required. Set the FlowBalance.exe compatibility Copy the TAC folder in the Program Files (x86) folder from Windows Explorer. Paste into the Program Files folder Open the pasted TAC folder and delete all the files except for the XIF folder and the FlowBalance.cfg file in the LON FlowBalance folder. Right-click the FlowBalance.exe icon created on the desktop Open properties/compatibility tab. Set as Windows XP (Service Pack 3)

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7Windows 7 Windows 10, 2012, 2016Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7Windows 7 Windows 10. 2012, 2016Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue Feature overview and tested platforms, operating systems, databases, and web browsers for AX/G3 version 3.8. Product Line TAC IA Series Environment Niagara AX / G3 3.8 Cause Field inquiries Resolution View the PDF files below.  They were obtained from Niagara-Central.com.  Feature Overview Test Summary Windows 8.1 is also supported (not listed in the Test Summary).

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

Issue After upgrading to Niagara G3 3.8 (from 3.7), nested PxIncludes now only partially load and very slowly.  They are not all entirely missing.  After a screen refresh, most will load except for a random few.  Also, they may load all at one moment but not the next.  The same Px file in version 3.7 loads faster with nothing missing. Environment Niagara G3 / AX version 3.8 Cause PxInclude caching is disabled by default in 3.8. Resolution This issue was addressed with the release of an updated bajaui module - version 3.8.38.3.  This version re-enables PxInclude caching.  Download it here.

Issue Robertshaw T99-112 RTD Immersion Temperature Sensor - Specification Sheet & Temperature / Resistance Table Environment DMS MicroSmart Cause Create a custom temperature / resistance object in Niagara, SBO, etc... Resolution Spec & T/R table available here.

Issue Existing sensor has failed (TS-5751-850).  The application involves below freezing temperatures (not outside air but a storage freezer).  Since the sensor is obsolete, what's a suggested replacement? Environment Network 8000 MicroZone II Cause Sensor failure Resolution Try the TO series sensor from Veris Industries.

Issue Installation flowchart for a network SIGNAL software installation Environment SIGNAL network version Cause Installation documentation Resolution Installation flowchart available in the Network Supplement of SIGNAL (F-25952), page 9 (pdf) or page 7 (paper)

Issue Trying to use OPRIF to make a few programming changes to a MicroSmart controller. OPRIF is installed on a SIGNAL computer (Windows 98). With SIGNAL disabled, OPRIF is able to start and handshake with the COM port. However the Auto Answer feature is enabled by default and begins an endless loop of trying to synchronize with the modem. The looping effect prevents a proper connection to the DMS to do programming changes. How can the Auto Answer be disabled on startup of OPRIF? Product Line TAC IA Series Environment OPRIF or Operator Interface version 11.4 and higher Cause Initialization file was modified by default Resolution The readme.txt file in the DMS folder explains how to prevent Auto Answer from being enabled on startup of OPRIF. Click here to view the entire readme file. Below is the excerpt on how to disable Auto Answer: Changes to the command strings used for modem-initialization and control The default modem init-string "AT C1 E1 V1 S0=1 S7=51" has been changed. It is now "AT&C1&D2E1V1". If you or your modem don't like this string, you can now override the default. Using NOTEPAD or EDIT, create a file called MODEM.INI in the DMS directory. This file should contain a single line of ASCII, which will be your customized initialization string. The line must begin with the letters "AT", and must not contain the letters "DT". Other than this one restriction, your modem-init string can contain whatever commands your modem requires. Two separate default strings have been defined for turning auto-answer ON and OFF. These may be overridden by creating files with the appropriate names in the DMS directory. To specify a customized string to force your modem to STOP auto-answering, use NOTEPAD or EDIT to create file a called ANSWEROF.INI in the DMS directory. By default, this file would contain the single ASCII line "ATS0=0". If your modem requires a disconnect command, you could instead write a line that reads "ATH ATS0=0". The default autoanswer ON string "ATS0=1", instructs the modem to answer on the first ring. To answer on the third ring, use NOTEPAD or EDIT to create a file called ANSWERON.INI in the DMS directory. It should contain the single ASCII line "ATS0=3". SUMMARY: Description Default String Filename Comment Modem Initialize AT&C1&D2E1V1 \DMS\MODEM.INI Modified in 11.4 Auto-answer On ATS0=1 \DMS\ANSWERON.INI New in 11.4 Auto-answer Off ATS0=0 \DMS\ANSWEROF.INI New in 11.4

Issue The AX Serial Tunnel service does not initialize on a station startup: ---------- Station Starting: FRI JUL 11 14:02:45 2014 ---------- Tridium Niagara Station, r2.301.529.v1 [WFU_UNC06] MESSAGE: ErrorLogService installed [/WFU_UNC06/services/ErrorLogService] ************************************************************ ERROR: Could not init node [/WFU_UNC06/services/IbsAsdService/AxSerialTunnel] java.lang.NullPointerException at tridiumx.tunnelAx.Tunnel.doInit (bytecode 48) at tridiumx.ibsAsd.AxSerialTunnel.doInit (bytecode 84) at tridium.foundation.node.Node.init (bytecode 1) at tridium.foundation.prism.LoaderModule.initNodes (bytecode 26) at tridium.foundation.prism.Prism.initNodes (bytecode 4) at tridium.foundation.Station.startStation (bytecode 60) at tridium.foundation.Sys.boot (bytecode 27) at tridium.foundation.Sys.bootLocalSns (bytecode 17) at tridium.tools.StationMain.bootSns (bytecode 0) at tridium.tools.StationMain.doIt (bytecode 352) at tridium.tools.StationMain.main (bytecode 10) at java.lang.reflect.Method.invoke (Native Method) at tridium.nre.Nre.mainTmpl (bytecode 271) at tridium.nreNre.main (bytecode 1) Product Line TAC IA Series Environment Niagara R2 (revision 522 or above) Cause The tunnelAx jar is not installed in the host UNC. The release notes for AX Tunneling in R2 do not clearly state to install the jar file in section 2.4 and 2.5 which provide install instructions; however, section 1.2 indicates the requirement of this jar file. Resolution Install the tunnelAx jar file prior to starting the install instructions in 2.4 and 2.5.

Issue MicroSmart MSC-P1500 Series controller quick reference for interfacing voltage and current sensors. Environment MicroSmart MSC-P1500 Cause The configuration for this controller is non-standard meaning the wiring and software configuration are not 'typical' with the rest of the MicroSmart controller line. Resolution The images available here are excerpts from the MSC-P1500 Installation Instructions (F-25504)