Issue Can a 7716 emulate a 78061 Tap? Product Line TAC INET Environment I/NET site Cause This emulated Tap requires the use of an optional RS232 expansion module. Using this Tap function, you can connect a Hayes compatible modem to port P2 of the RS232 expansion module. You may then configure the modem for auto-dial/auto-answer (AD/AA) operation. Resolution A 7716 can emulate a 78061 Tap. Using the Hand Held Console (HHC): Press [Code], 90, [Enter] The emulated device type model number displays in the read out Press [Inc] or [Dec] to toggle through 7801, 7803, or 7806 Tap emulation Press [enter] to accept your choice You will need the RS-232 expansion card for ADAA See TCON 096 for details.

Issue Does I/NET 2000 launch "EqualCli" automatically? Environment I/NET 2000 Cause File equalization is required if you have more than one host workstation which will need access to any of the above files. One host workstation is designated as the filemaster. This designation is performed in the Configure program and is maintained in the configuration profile. When you select the Set as filemaster option, Configure automatically completes the filemaster name field with the Computer name (found in the Identification tab under Windows Network settings). The filemaster name field is read-only on the filemaster station and cannot be changed. Resolution Yes, EqualCli will launch automatically. For more information see TCON 209, The Filemaster, 1-13. When the workstation is designated as the filemaster, I/NET stores a master copy of each equalized file in the \MSTR directory. It is important that the designated workstation be constantly powered and that the EqualSrv program be running. EqualSrv will dock an icon in the system tray to indicate it is active. Both EqualSrv and EqualCli are launched automatically by I/NET on the filemaster workstation and stay running as background tasks, even when I/NET is shut down. If necessary, you can manually shut down EqualSrv from the system tray icon menu. Warning: If the filemaster workstation is powered off, or if EqualSrv is not available, file equalization cannot occur. Furthermore, other host workstations will not be able to modify any of the equalized files. It is recommended that the filemaster workstation be powered by a uninterruptable power supply (UPS). All other host workstations must enter the Computer name of the filemaster workstation in the Filemaster name field. I/NET launches the EqualCli program on the host workstations automatically. Before any host workstation can access an equalized file, the EqualCli program contacts the EqualSrv program running on the filemaster station to ensure that any modifications can be passed to the filemaster copy. If, for some reason, EqualCli cannot make contact with EqualSrv, the operator will receive an error message and will not be able to access the equalized file. This ensures that no updates to the file are lost. If EqualCli makes contact with EqualSrv, the operator is permitted to access and modify the equalized file. EqualCli passes the updates to EqualSrv, who then updates the filemaster copy. If the update is successful, EqualSrv will make the file available to all the host workstations. There are three events which trigger the file equalization procedure. When I/NET is launched on any host workstation. When an operator attempts to access an equalized file. When any operator successfully updates an equalized file.

Issue How long will I/NET 2000 be sold? Is I/NET 2000 still supported? Environment All Revisions of I/NET 2000 Cause The last release of I/NET 2000 was Revision 2.34 which was released in April 2003. Microsoft has announced that it will terminate all Windows® 98 support in 2006. Resolution As of January 1, 2006, support for I/NET 2000 is no longer available. Please review the following Customer Advisory available on The Exchange Download Center which details support information for I/NET 2000. All I/NET 2000 customers should upgrade to the latest revision of I/NET.

Issue Two different revisions of I/NET 2.31 were created: 2218 and 2227. How do you know which one to use? Environment I/NET 2.31 Cause Inet 2.31 was released with two different builds 2218 and 2227. Resolution The latest build for I/NET 2.31 is the 2227 build. If a site is running the 2218 build, it is recommended to upgrade to the later build since many functions have been greatly improved. Log in to The Exchange Download Center to download I/NET v2.31.

Issue The I/A Series Tunnel clients fail when used on Windows 7 64-bit Product Line TAC IA Series Environment I/A Series R2 UNC I/A Series WorkPlace Tech 5.8.7 - current Cause Existing I/A Series R2 Tunnel Clients were not developed for use on Windows 7 64 bit and later Windows platforms Resolution The AxTunnelClients can now be used with the I/A Series R2 UNCs. The new I/A Series R2 jar files required are on The Exchange Download Center. For details see the release notes in the tunnelAx zip file. As noted in the release notes, new jar files have also been released to allow the use of the AxTunnel client for ibsASD and ibsMS serial tunneling. Those jar files are also in the same 532 files area. This is the TAC IA Series WorkPlace Tech VLon Tunnel - User Guide.  It supplies additional information about supported platforms and configurations

Issue I/A Series R2 Optimum Start Stop program object may improperly calculate start time when outdoor air temperature compensation is used. Environment I/A Series R2 (all versions) Cause Optimum start / stop compensation is performed through the use of a program object. The object could calculate a negative start lead time when outdoor air temperature compensation was used. Resolution A check was added to the program object to prevent a calculated negative start leadTime due to outdoor air temperature compensation.  The revised object is available for download from The Exchange Download Center. Download the file >> OSS for Niagara 08_03_11.zip In addition, the object includes the following change history. 10-Nov-00  Moved the parameter reset control to an external stimulus 16-Aug-01  Changed reset input from BooleanPriority to DateTime 20-Dec-02  Added check for command time > next event time to account for a large leadtime calculation that results in a start time prior to midnight 14-Sep-05  Added safety check to prevent dynamically adjusted runtime factors from becoming too large 25-Apr-06  Corrected the following stop-time issues:            1) stop-time calculation when earliestStopTime is after schedule stop time            2) stop-time calculation when start/stop times span midnight            3) determining when to perform stop-time analysis    05-Nov-08  Added changes from 2002 and 2003            Added prestart (maxStartLimits) and comfortLimit inputs 18 Nov 02            Added the ability to use OA temperature for OSS calculation 24 Feb 03 12-Dec-08  Added OA temperature to message strings.  Added output for calculated command time. 19-Feb-09  Corrected issues with stop-time analysis:            1) lastStartTime was being used for stop-time calculation            2) analysis for heating was adjusting drift time for cooling            3) analysis for cooling was adjusting drift time for heating            Corrected issues with stop time calculation:            1) heating mode failed to drift when > upper comfort limit            2) cooling mode failed to drift when < lower comfort limit            3) stop mode calculation always reflected the next event time 15-Oct-09  Added properties and check to prevent dynamically adjusted drift time factors from exceeding a specified maximum value. 03-Aug-11  Added check to prevent calculated negative start leadTime due to outdoor air temperature compensation.

Issue I/A Series (Niagara) R2 station, needs a LON shadow object for a Square D Altivar 21 with Program ID 80:00:13:3C:0A:0A:04:50.  The closest match is Atv21, with Program ID 80:00:13:3C:0A:0A:30. Environment I/A Series (Niagara) R2 station in a UNC with a LON trunk, build 532, 529, or 522 Square D drive, Altivar 212, with LON card, Program ID 80:00:13:3C:0A:0A:04:50. Cause Square D Altivar 212 with a new LON profile and XIF file, program ID 80:00:13:3C:0A:0A:04:50 Resolution Download a new jar file: lonSquareD-2.303.532a.zip, which includes a shadow object named Atv212, manufacturer Id = TA_Control, and Program ID  = 80:00:13:3C:0A:0A:04:50. LonUtilities Manager after the jar file has been installed:

Issue After using the I/A Series (Niagara) R2 Admin Tool Installation Wizard "Upgrade" process to install an earlier version of the R2 OS and NRE, the UNC will no longer reboot properly. The heartbeat LED remains turns on and stays on. The software was downgraded to a release earlier than R2.301.527. While watching the bootup process on a serial console connection, the bootup log shows the following message just before the UNC reboots: old clock frequency detected, modifying and rebooting -> Since the BOOT Flash chip does not allow its clock frequency to be changed, this "change, reboot, start, clock change, reboot" process will continue as long as the UNC is powered. Product Line TAC IA Series Environment UNC-410 with serial number 36218b and newer UNC-520 with serial number 36184b and newer Cause The UNC features a new bootflash chip that is incompatible with the older releases of the R2 software. When the affected UNCs are shipped by the factory the following yellow warning label is attached to the transformer cover: WARNING! This Universal Network Controller (UNC) features a new bootflash chip. To properly configure or install the software you MUST use one of the following releases. Release R2.301.527 or newer Failure to follow these instructions will cause the UNC to become inoperative. Refer to Product Announcement PA-00123 on The Exchange Download Center for more details. Resolution Contact Product Support to obtain a return authorization number. The UNC returned with this issue will be repaired by the factory for a nominal fee of $250.

Issue I/A Series Micronet BACnet controllers firmware download Environment I/A Series Micronet BACnet (MNB) Controllers Cause The firmware for the MNB controllers is not available on the Extranet. Resolution The MNB controllers' firmware can be downloaded from The Exchange Download Center by searching for MNB firmware.

Issue I/A Series MNL-VAV controller continues to display a small air flow value (CFM or L/S) even when airflow is not present (zero flow conditions). This condition is typically seen as small CFM readings on graphics screens when air is not present (AHU off condition). Product Line TAC IA Series Environment MNL-V1RV3-2, MNL-V2RV3-2, or MNL-V3RV3 Cause The I/A Series MNL-V1, V2, V3 and controller platforms were recently redesigned to incorporate the latest Echelon FT 5000 Neuron Smart transceiver. With no air flow, when the fan system is not running, minor fluctuations in duct pressure could result in false air flow readings from the MNL-V1RV3-2, MNL-V2RV3-2, and MNL-V3RV3. Resolution Use the MNL Firmware Updater Utility to update the MNL-V1RV3-2, MNL-V2RV3-2, or MNL-V3RV3 controller firmware to version 4.3B5. A velocity pressure reading below 0.005 in. WC (1.25 Pa) will be processed within the controller as no or zero flow. Controllers within these date code ranges should be updated with the utility detailed below. MNL-V1 and MNL-V3 starting with date codes of 1208 MNL-V2 starting with date codes of 1212 Note: The MNL VAV control range of 0.05 to 2.00 in. WC (12.5 to 498.2 Pa) is not affected. When air flow control below 0.05 in. WC is required, the I/A Series MNB VAV controllers, with a control range of 0.004 to 1.5 in. WC (1.0 to 373.6 Pa), should be used. MNL Firmware Updater Utility The MNL Firmware Updater 4_3B5.zip can be downloaded from The Exchange Download Center. The zip file contains these instructions and the “MNL Updater Setup.exe”. Executing “MNL Updater Setup.exe” will place the latest firmware into C:\Program Files\Schneider Electric\MNL Firmware Updater\bin and add the installer to the Start Menu item under Schneider Electric. MNL-V1RV3-2, MNL-V2RV3-2, and MNL-V3RV3 controller firmware version 4.3B5 MNL-5 controller firmware version 4.3A5 If the MNL Firmware Updater had previously been installed, the MNL-V1RV3.NDL, MNL-V2RV3.NDL, and MNL-V3RV3.NDL files located in "C:\Program Files\Schneider Electric\MNL Firmware Updater\bin" will be replaced.

Issue I/A Series G3 support for virtual machines Environment I/A Series G3 version 3.6 Cause There is a requirement to run I/A Series G3 in a virtual environment.  Resolution As per Product Announcement TAC I/A Series Software Updates, I/A Series G3 release 3.6 is validated for VMWare Server 2 and Microsoft Virtual Server 2008. 

Issue Station sending SMTP server its LAN IP address instead of WAN IP address causing the SMTP server to block the connection. Environment I/A Series G3 (Niagara) Cause SMTP server is blocking the connection due to the LAN IP address being used. Resolution A new system property is available that can be used to define how the station identifies itself to remote SMTP servers. This can be done by setting the mail.smtp.localhost property in the system.properties to the station's external facing IP address or FQDN. Example: mail.smtp.localhost=12.34.56.78 Download the listed (or newer) email module from Exchange Extranet website.   email-3.3.34.1.zip email-3.4.65.zip email-3.5.34.2.zip email-3.6.33.zip email-3.6.48.zip

Issue I/A Series G3 graphic pages can be displayed in a web browser but any graphic images on the page are not rendered properly or are rendered as blank after the Java version is updated to Java 7 Update 65 or later. The issue may not immediately appear but generally appears after navigating between various pages containing graphic images. This issue is most apparent when the user is logged in to the I/A Series G3 system via a WB profile. Product Line TAC IA Series Environment I/A Series G3 systems of any release. Cause Java language issue Resolution If the I/A Series G3 graphics server is running I/A Series G3 release 3.7.106, install the updates from the file Consolidated_Patches_3.7.106_SE_01222015.zip. If the I/A Series G3 graphics server is running I/A Series G3 release 3.8.37, install the updates from the file Consolidated_Patches_3.8.37_SE_01222015.zip. Updates for this issue in other I/A Series R2/G3 releases are not available.

Issue The hostId for a computer running I/A Series G3 version 3.8u1 (or earlier) and N4 versions 4.2 (or earlier) may be changed from the result of a Windows update. Product Line TAC IA Series Environment I/A Series G3  I/A Series N4  Cause The hostId is automatically generated upon first install of the software and stored within the registry.  The location of the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update.The hostId is automatically generated upon first install of the software and stored within the registry.  The location of    the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. Resolution I/A Series G3 version 3.8.213 (or higher) and I/A Series N4 version 4.3.58.18 (or higher) have been modified to guard against Windows updates to prevent hostId changes.  Installations of N4 4.3 and/or G3 3.8u2 will continue to operate normally and will not assume a new hostid after a Windows update.  All previous versions of Niagara could generate a new hostid after a Windows update, requiring a license replacement.   Schneider Electric recommends updating I/A Series G3 and N4 installations to the latest released software in order to maintain the latest security protection and to gain benefit from the latest features.  These builds are:   I/A Series 3.8 Update 2 (3.8.213 and later) I/A Series 4.4 (and later)   Patch to address multiple Host IDs on a single Microsoft Windows© platform   A set of patch files have been created to stabilize the Host ID for cases where customers have not upgraded to the latest version of Niagara (see installation instructions below). Once these patches are applied to the older versions of Workbench the Host ID is stabilized and should not change if Windows updates are installed.   Note: This is a reminder that a 32-bit install will always generate a different host-id than a 64-bit install.   IMPORTANT NOTES REGARDING THE PATCHES   Patches are only supported for the latest update (maintenance) version for the relevant release. Patches are not available for I/A Series G3 release 3.5 and earlier, or I/A Series N4 release 4.0 or 4.1. Builds prior to G3 3.8.213 are considered unsupported. Customers applying these patches do so at their own risk. Newer versions of Niagara (3.8U2 and 4.3) have introduced a stabilized method of managing the Host ID and do not require any patch. The patches do not eliminate the issue of different Host IDs generated when installing 32-bit and 64-bit Niagara. Installation Instructions   The Host ID patch file is available for download on the EcoBuilding Exchange Download website.  Login to the Schneider Electric EcoBuilding Exchange Download Center and enter G3 and N4 Host ID Patches in the search area or the filename of the zip shown below.    Download the G3_N4_HOSTID_PATCHES.zip and unzip into a temporary folder. The archive contains 'nre.dll' for various versions of I/A Series G3 and Series 4.2 in a directory structure identifying them first by version and sub-directory identifying 64-bit or 32-bit Windows. The 4.2 folder also contains 'njre.dll' which will need to be copied only for 4.2 installations.  Follow these instructions:   Verify the installed java version to be either 64-bit or 32-bit. Start a Niagara Command Line (Home>/bin/console.exe) from the desktop of the platform to be patched. From the Niagara Command Line execute the command: nre -version One of the listed items will be java.vm.name. If the text contains “64-Bit” then the installation is 64-bit otherwise the installation is 32-bit. Stop any running station using Workbench's Platform Application Director on the platform to be patched. Exit Workbench if running on the platform to be patched. From the Niagara Command Line ... /bin/console.exe execute the command: plat uninstalldaemon  Prior to replacement, save a copy of the existing nre.dll located in /bin folder. If Niagara 4.2 is being updated also save a copy of the existing njre.dll located in /bin folder. Copy the version appropriate and OS appropriate (64-bit or 32-bit) downloaded version of nre.dll file to the Home>/bin folder. If Niagara 4.2 also copy njre.dll to /bin folder. Overwrite the existing file(s). From the Niagara Command Line (/bin/console.exe) execute: plat installdaemon Start Workbench.  Open a platform connection to the patched platform. Using the Application Director, start the station.  

Issue I/A Series G3 Security Alert – Directory Traversal and Weak Credential Storage Vulnerability and default encoding of credentials in authentication cookies Environment I/A Series G3 – All Versions Cause Recently, independent security researchers Billy Rios and Terry McCorkle notified ICS-CERT of a directory traversal and weak credential storage vulnerability with proof-of-concept (PoC) exploit code for the I/A Series G3 software.  This vulnerability could affect systems if not properly configured. ICS-ALERT-12-195-01 TRIDIUM NIAGARA DIRECTORY TRAVERSAL AND WEAK CREDENTIAL STORAGE VULNERABILITY Resolution Download and review TPA-IA-12-0003.02 Technical Product Advisory that outlines how to verify if a system is properly configured to protect against directory traversal.  Schneider Electric strongly urges you to review the TPA, assess the status of the system configuration and take the prescribed steps to secure if necessary.

Issue I/A Series G3 Security Alert Security Patch Released for 3.5 and 3.6 to remove a directory traversal vulnerability allowing a user with a valid user account or guest privileges to escalate his or her privileges on a Niagara AX based system. Product Line TAC IA Series Environment IA Series G3 - Versions 3.5.xx and 3.6.xx Cause The patch addresses a new vulnerability that was publicly disclosed in January 2013 at a security analyst conference by two security researchers – Billy Rios and Terry McCorkle. The patch removes a directory traversal vulnerability allowing a user with a valid user account or guest privileges to escalate his or her privileges on a Niagara AX based system. Resolution Schneider Electric strongly recommends all customers apply the security patch to any existing 3.5 or 3.6 systems to correct this vulnerability. Customers with systems running a version of I/A Series G3 released prior to 3.5 should purchase an upgrade to the latest version of the Niagara Framework software in order to take advantage of the latest security improvements. Download and review TPA-IA-13-0003.00 Technical Product Advisory that details the vulnerabilities and security patch installation instructions. Security patches are available for download from The EcoBuilding Download Center: Security Patches. Note: The patch does not affect any standard Niagara configuration or functionality. The only impact of the change is to remove the vulnerability.

Issue I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE reboot or station start.  The controllers do not drop offline and the associated Modbus proxy points no longer appear to update. Environment I/A Series G3, Modbus TCP 3.6.47 and lower Cause Modbus TCP transaction Identifiers are used to associate the future response with the request.  The transaction ID is a two byte value that can range between 0 and 65535. The Siemens Moore 353 controller appears unable to process Modbus transaction IDs at or higher than 1024. Resolution The I/A Series G3 Modbus TCP driver has been modified to allow the configuring of the maximum transaction ID for each device. Download the following modules from The Exchange Download Center: modbusCore-3.6.47.1.zip modbusTcp-3.6.47.1.zip Install to the appropriate I/A Series G3 Workbench modules folder and upgrade the modules in the ENC/JACE. Modify the transaction ID to a value lower than 1024 and reboot the ENC/JACE station.

Issue Customers are reporting that TRD-T-IO-16 and TRD-T-IO-34 modules do not communicate "right out of the box". The "PWR OK" led on the IO-34 is lit up, but the device remains undiscoverable in Workbench (in the Ndio Board Manager view). The IO-16 has no LEDs lit, and also cannot be discovered. The IO modules are brand new, unused units. Environment I/A Series G3, TRD-T-IO-16, TRD-T-IO-34 Cause The IO-16 or IO-34 module was initially powered up for too brief a time and then powered off, interrupting an "automatic IO firmware upgrade" that was underway. The JACE keeps the latest NDIO firmware in its image distribution, and automatically updates any attached IO module found with older IO firmware. This IO firmware upgrade process occurs for each attached IO module, in sequence, starting with the lowest logical address IO board (IO module closest to JACE). During an IO firmware download, the JACE's Status LED has a long duty cycle blink -- long On, blinking Off. This IO firmware upgrade takes at least 30 seconds for each IO-16 module, and at least 60 seconds for an IO-34 module. Therefore, if multiple IO modules are attached with older IO firmware, it can take as long as 4 minutes of uninterrupted power to safely complete this operation. Once completed, the JACE continues booting and starts its platform daemon process. Therefore it is always safe to cycle power to the JACE once a platform connection can be made. Resolution If the JACE is powered down or if the IO module is removed during this IO firmware update, the IO module becomes unusable and must be returned to the factory to be re-imaged. The "PWR OK" LED will show green on an IO-34 even after is has been broken this way, but it will remain undiscoverable and unusable. Reference TPA-IA-12-0004-00 for more details.

Issue After powering down a Microzone II controller and powering it back up, the ENC will not immediately reconnect to the device. Environment I/A Series G3 ENC with tacASD 3.4.64.1 or earlier module (jar file). Any ASD devices under the ENC. Cause The existing tacAsd module, (release 3.4.64.1 or earlier) may exhibit excessive device initialization and recovery times upon a restart of the station or a power cycle of the ASD devices. Resolution Update the tacAsd module to release 3.4.64.4. File acAsd-3.4.64.4 can be downloaded from Ecobuildings Download Center.

Issue I/A Series G3 ASD driver exhibits excessive device initialization and recovery times upon a restart of the station or a power cycle of the ASD devices. Environment I/A Series G3, ASD Cause Driver not synchronizing baud rates to efficiently recover the devices on the bus. Resolution The tacAsd 3.6.47.4 module resolves this issue by improving the mechanism that synchronizes the baud rates between the station and the ASD devices. Download the file tacAsd-3.6.47.4 from The Exchange Download Center.