Building Automation Knowledge Base

Issue Replacement for discontinued I/A Series hardware UNC-410, UNC-520, ENC-410 & ENC-520 Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers UNC-410 and UNC-520 I/A Series G3 Enterprise Network Controllers ENC-410 and ENC-520 Cause Due to component availability, the following UNC/ENC parts have been discontinued as of 1st December 2013.  Resolution Discontinued UNC/ENC controllers can be replaced with the JACE 603, JACE 645 controllers series. The JACE 603 and JACE 645 are the first network controllers that can run either R2 or G3 Niagara applications when a corresponding license is installed.  New sites and expansions – these Network Controller parts come with the same metal box enclosure as the products they replace: Retrofit applications – these Network Controller parts are a replacement board that fits into an existing UNC/ENC enclosure: Refer to PA-00251 for details.  *Note - The parts for new sites and expansions are not available for all regions. Contact your local Schneider Electric sales representative if you have any questions.  * Updated May 2015 The parts TRD-RB-603-R2 and TRD-RB-645-R2 are not longer available. See below for the equivalent parts. TRD-RB-603-R2 > TRD-RB-603 + TRD-R2-RB-6XX TRD-RB-645-R2 > TRD-RB-645 + TRD-R2-RB-6XX _______________________________________________________________________________________________________ * Updated March 2019 The JACE-603 and JACE-645 has been discontinued as of June 2018.  The recommended replacements are the EcoStruxure Building Operation AS-P or the I/A Series JACE-8000. Refer to PA-00592 I/A Series JACE 600 End of Commercialization. 

Issue Performing an action that normally starts WorkPlace Tech Editor or Monitor does not start the tool. A warning message is displayed. Schneider Electric StruxureWare has stopped working A problem caused the program to stop working correctly. Please close the program. Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure WorkStation SmartStruxure WorkPlace Tech Editor and Monitor program Cause .NET support not enabled in Visio Resolution Enable the .NET programmability support in Visio. as documented in Section 4.6 of  the SmartStruxure WorkPlace Tech Editor and Monitor manual. Open Windows Control Panel Click Programs and Features In the list of programs, select Microsoft Office Visio and then on the File menu, click Change In the Change your Installation dialog box, select Add or Remove Features and then click Continue On the Installation Options tab, expand Microsoft Office and then Microsoft Office Visio Click .NET Programmability Support, select Run from My Computer, and then click Continue Windows reconfigures Microsoft Visio. When finished, click Close

Issue A space temperature sensor is not reading correctly on a MicroSmart controller (Model # MSC-P-1504).  The type of sensor is not known due to its remote location.  What are the possible values for the SCALE, OFSET, and CVTYP elements? Environment MicroSmart MSC-P-1500 line of controllers Cause Trying to determine the type of sensor installed so a spare sensor can be brought for the service call. Resolution The different combinations of SCALE, OFSET, and CVTYP can narrow down the type of sensor installed (i.e. RTD, voltage, or current).  The exact model cannot be identified remotely.  See page Table 6 on page 17 of the Installation Guide for this controller family.

Issue Is there a SmartStruxure specification that includes a piece for Network 8000 migrations? Environment Network 8000 Cause sales request Resolution The document is available on the Buildings Business Extranet, under Products > SmartStruxure solution > Sales > Guide Specification. It's a Word doc so it can be modified to suite the desired needs. The current version is 1.4 and is available here for convenience.

Issue The customer is replacing a defective actuator on a hot water reheat valve downstream of a VAV box.  The VAV and associated hot water valve are controlled by a DMS MicroSmart MSC-V-511 controller. Can the MF41-6043 actuator be wired into the MSC-V-511 and control the valve? Environment DMS MSC-V-511 MF41-6043 Cause Defective actuator is discontinued and cannot be swapped with an identical, working one. Resolution The triac outputs on the MSC-V-511 can properly control the MF41-6043 actuator. Terminals D1 to D4 provide 24 Vac which is the voltage required for the actuator. Look at the MSC-V-511 installation guide (F-25710) on page 18 for details on how to wire and program the actuator. Remember that the MSC-V-511 provides 24 Vac power so there's no need for an external power source.   If needed, the MF41-6043 installation guide has wiring diagrams on page 6. The actuator requires 2.3 VA. The digital outputs on the MSC-V-511 can provide up to 12 VA.

Issue Can the SE7605B5045 be converted to work on an Echelon trunk? Environment Viconics SmartStruxure Lite Cause Wrong controller ordered for application Resolution VCM7600V5045E Echelon Retrofit Communication Card is available for purchase and can be installed in the field. Click here for a list of all communication cards available.

Issue Proxy objects were successfully created in a G3 obix integration of a R2 station.  The writable proxy objects (ie: setpoint overrides) in the G3 station do not propagate the new value to the native object in the R2 station. Environment Niagara G3 Niagara R2 Cause This is a known issue with the G3 obix driver. Resolution Right-click the proxy object in the G3 station and do a 'forceUpdate'. If there are several dozen proxy objects affected, download this program object.  Paste it anywhere in the Obix Network and execute it.  A 'forceUpdate' will be done to all proxy objects. As of June 2013, these are the most up to date jar files for an obix integration:  2.301.535i.beta.jar, 2.301.535i.beta.jar.pc, and niagaraDriver.zip. Extraction password:  niagara (all lowercase)

Issue A network of GCMs are configured with the NIM card in each GCM to allow intercommunications over the ethernet network. Some (or all) of the devices are no longer communicating.  No known changes have been made to the ethernet network. Environment GCM-86xxx series GCMs with GCM-ETH-1 ethernet network cards The GCM-ETH-1 network card contains firmware version 11.1F. Cause Known issue with the older version of the firmware (rev 11.1F)  where network traffic issues can cause communications failures. Resolution If a firmware upgrade kit (GCMA-149-113) is available you should update the firmware in the NIM card to version 11.2T, using the procedure in document F-26229. In the event that you cannot obtain a firmware upgrade kit or a replacement GCM-ETH-1 NIM card, the procedure documented in Technical Bulletin 99-56, can be used to clear the memory of the NIM card, allowing it to re-establish communications.

Issue What was the repeater used on MicroSmart communication trunks? Environment DMS MicroSmart (all revisions) Cause Information on a discontinued product line Resolution The typical repeater installed was Model # RPTR-DMS-WW.  There are other model numbers for trunks installed with fiber. Click here to view the Repeater Installation Instructions (F-25846).

Issue Need a currently available sensor that is compatible with the MicroFlo II controller. Environment MicroFlo II VAV controller Cause Need a sensor for the obsolete MicroFlo II. Resolution See the Spec Data sheet (F-24314-5, page 3) for a list of compatible sensors that are currently available. NOTE: The MicroFlo II controller is OBSOLETE.

Issue What date was the DMS product no longer available?  Is there supportive documentation of the announcement? Environment DMS Cause Documentation required for an end customer's request Resolution The DMS product line was no longer for sale on April 1, 2005. Click to view Announcement 05-016.

Issue I/A Series R2 and G3 Security Update - Oracle has released a Critical Patch Update for Java SE that addresses a number of security vulnerabilities Environment I/A Series R2 - All versions I/A Series G3 - All versions Cause Oracle has released a Critical Patch Update for Java SE that addresses a number of security vulnerabilities.  The patch contains fixes for 50 security vulnerabilities including 44 that only affect client deployment of Java.  These vulnerabilities can only be exploited on desktops through Java Web Start applications or Java applets.  One reported vulnerability exploits the installation process of client deployment of Java – installation of the Java Runtime Environment on desktops.  This Critical Patch Update also includes fixes that were previously released with the Java 7 Update 11 alert (Security Alert CVE-2013-0422). Resolution Download and review TPA-IA-13-0001.01 Technical Product Advisory that details the vulnerabilities.  Schneider Electric recommends that customers evaluate the risk of enabling Java, based on how the affected PC is used and that customers review the download and install the Critical Patch Update as needed.

Issue When logging into SIGNAL, a pop-up error appears: Path not found. Error, Btrieve #915.  A local or shared drive cannot be found.  Correct the problem and try again. Environment SIGNAL Cause The SIGNAL.INI file located in the WINDOWS folder contains folder paths that no longer exist or were changed. Resolution Replace this file with a copy containing the default directories. The file can come from a database backup, another installation of SIGNAL, or from the link available in the previous line above.

Issue What type of SIM is a Type 40? Environment Network 8000 Cause Service call to an older installation of Network 8000 product Resolution Type 40 is a SIM-TRANE. Click here for the SIM-TRANE Integration Manual.

Issue Identifying the non-MicroSmart controllers in a DMS system. Environment DMS Cause Old installation of DMS with controllers not identified in any Niagara DMS/MicroSmart integration literature Resolution Controllers that were manufactured prior to revision 9.X do not have MicroSmart capability. These controllers are accessed through DMS programming only. It should be noted that it is not possible to add MicroSmart capability to these controllers. The controller model numbers are: Slave CO/CI Module N604-002, N604-012 Slave AI Module N604-003 Slave Pneumatic Motherboard N604-004 Slave AO Module N604-016, N604-017 General Purpose Slave Module N604-021, N604-025 The controllers listed above can reside on the same trunk with MicroSmart controllers that are revision 9.2, 10.X or 11.X. The only requirements are that the Slave controllers must have revision 9.0 firmware installed and the trunk must be a 2 wire design (not 4 wire). For more information about non-Microsmart controllers, review Tech Tip #350-95-03

Issue On December 13, 2012, the certificate verifying the authenticity of the Schneider Electric I/A Series G3 Workbench Applet (wbapplet) expired. Users will see the following error in their browser when accessing a station that is using a version of the wbapplet.jar with an expired code signing certificate: Environment Niagara G3 Cause When accessing an I/A Series G3 station through a web browser using a WbWebProfile, the web browser runs Workbench within a Java applet. To enhance security, this applet is 'signed' using a code signing certificate. This ensures that the applet has come from a reliable source and can be trusted to run with the proper permissions. Certificates used to sign applets are issued by a Certificate Authority (CA). Each code signing certificate issued by a CA has an established expiration date, with the maximum expiration being two years. Once this expiration date has passed, continuing to use a Java applet with an invalid certificate will result in warning messages within the browser. The applet will only be allowed to run after the user has acknowledged the warning and granted approval. Resolution An updated certificate is available in the new wbapplet.jar, available from The Exchange Download Center. This file will need to be added to the Enterprise Network Server, as well as on any ENCs that will be accessed from a browser. This file is for all released versions of TAC I/A Series G3 and is valid until March 30, 2015. Download wbapplet_March_2015.zip. Extract the wbapplet jar file  Click and Download The WbApplet Installation Guide. Note: Updated WbApplet files are available as part of upcoming Niagara 3.5 and 3.6 maintenance builds, as well as being from the Source website. In 3.7, wbapplet.jar is integral to the web.jar and contains an up to date certificate.;

Issue What is the pinout diagram for the interface cable connecting a computer to a Network 8000 LCM? Environment Network 8000 Cause cable not available for purchase Resolution Diagram available here.

Issue Unable to link an I/A Series R2 UNC to a McQuay Microtech III DAC or SCC to clear alarms via nviClearAlarms. Product Line TAC IA Series Environment I/A Series R2 UNC-410 UNC-520 Cause The nviClearAlarms is used to clear faults, problems, warnings, etc. from a McQuay Microtech III controller.  The variable used by McQuay is a UNVT (user network variable type) and requires a combination of objects to connect and control. Resolution This article specifically details the interface to the newest Microtech III shadow objects as shown below.  The same general solution can be applied to other McQuay devices as needed. McQuay Microtech III Applied Air Unit Controller DAC - MtIIIAhuDac01B (80:00:25:56:0A:03:04:B2) McQuay Microtech III Applied Air Unit Controller SCC - MtIIIAhuScc01B (80:00:25:55:00:03:04:B2) Note: Update the lonMicrotechIII jar file to version 535b or higher.  An issue with UNVT definitions prevented the DynamicMux object from properly interfacing to the nviClearAlarms on the MtIIIAhuScc01B shadow object.  The lonMicrotechIII-2.302.535b.zip file can be downloaded from The Exchange Download Center Add a DynamicMux object from the tridiumx lonworks jar (conversion folder) to the workspace.  Connect the DynamicMux object to the nviClearAlarms input. Add a Program object to the workspace.  Edit the Program object and add the program text from the appropriate text file.  Compile the Program object and link to the DynamicMux. Download text file ... MtTIIIAhuDac01B_Alarm Download text file ... MtTIIIAhuScc01B_Alarm Add a Multistate Output object and configure the Visual stateText to the desired values shown below.  Link the Multistate Output object to the Program object. 0 = None 1 = ClearAllFaults 2 = ClearAllProblems 3 = ClearAllWarnings 4 = ClearAllAlarms default = Error

Issue How to configure an analog input on a DMS MicroSmart controller as a voltage input. Environment MSC-MPC (revision 10) and MSC-MPC-001 (revision 11) MicroSmart controllers Cause Adding new voltage sensors Resolution Click here for an explanation on how to configure an analog input as a voltage input

Issue Loading or upgrading new firmware into a 102-AX VAV controller that resides under a Jace controller Environment Jace Vista Xenta 102-AX Firmware Cause Updating firmware in a 102-AX VAV controller that has previously been commissioned into an existing network Resolution Please click here to see a step by step procedure document on the recommended procedure for this task.