Issue After reviewing a DMS installation, the red end-of-line (EOL) termination modules are not installed on the Microsmart trunk. The original part number was N406-032. Are they available for purchase? Product Line TAC IA Series Environment DMS Cause Part number cross reference Resolution The part number is changed to RBSC-16. Use this number when contacting customer support services.

Issue Reverting to an older than installed version of the firmware is required. Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series MNB 1000 Cause Prior to the 1.515 version of the firmware, it is not possible to revert to an older release of the firmware. Resolution Firmware after 1.515 has the ability to be reverted. 1.515 is the oldest version the controller can be installed with.  If this procedure is required, please contact your countries Product Support for more information.

Issue MNB Controller firmware upgrade failed, which resulted in the device showing a blinking-red status LED. Product Line TAC IA Series Environment I/A Series MNB Controllers (ASC) (All firmware revisions) Note: This does not apply to the MNB-1000 Cause A blinking-red status LED means the MNB controller is in Boot Loader mode and it cannot reboot. It is now a "slave" unit, listening to traffic, not initiating communication. Resolution Using the WorkPlace Commissioning Tool, click on the File pull-down menu and select "Add MS/TP Slave". If asked to select from IP, Ethernet or MS/TP, select MS/TP. (Note: It's a good idea to have the controller isolated from the trunk, so the firmware upgrade process runs less risk of being interrupted.) At the prompt for the address, enter the address set on the controller DIP switch. The controller should get added to the list. If it is already in the list, a message will indicate that there's a duplicate address. Answer prompts in such a manner to get the controller added to the list. The 'slave' controller may show up with a blank name. Do the firmware upgrade again. This procedure works 80% of the time. If the upgrade fails, put the controller into Dedicated Boot Loader Mode. Take the controller off the MSTP trunk, set the DIP switch address to 254, cycle power, and try another firmware upgrade (keep it addressed as 254). Following a successful firmware upgrade, set the DIP switch back to the correct controller address and cycle power to the controller.

Issue Running a G3 / AX server with version 3.8 on a Windows 8.0 host. After a recent upgrade to Windows 8.1, the Niagara hostId was changed. Product Line TAC IA Series Environment Niagara G3 / AX 3.8 Cause Recent operating system upgrade Resolution Add the following line to the nre.properties file:  disableHostIdGeneration=true right after softjace=false   

Issue BACnet proxy points and BACnet devices are configured to use COV subscriptions however points are listed as Polled when added to database. Product Line TAC IA Series Environment Niagara G3 all version, ENC-520, ENC-410 Cause The "Use Cov" property is set to false in the BACnetNetwork Default Tuning Policy. The "Use Cov" property default is "False." If set to "True," and the assigned proxy points are under a BacnetDevice that supports the Subscribe COV service, any necessary updates (Niagara proxy subscriptions) are attempted using BACnet COV subscriptions to the device. If the subscription attempt succeeds, the "Read Status" property of the point's BacnetProxyExt displays "COV." If the subscription attempt for a proxy point fails, normal polling is used and the "Read Status" property shows "Polled." Resolution The "Use Cov" property must be set to true for COV subscription to function. It’s a good idea to create a separate tuning policy for BACnet COV subscriptions. Creating a new Tuning Policy Expand Tuning Policies under the BACnetNetwork Right-clicking an existing policy, then choosing "Duplicate" in the shortcut menu. "Name" it as desired. Open the tuning policy you just created Set "Use Cov" to true and save. Assigning the new tuning policy to the proxy points under the BACnetDevice that is configured for COV subscriptions. Expand the Points folder of the BACnet Device Double-click on the proxy point you wish to configure to use Cov Click on the drop down menu next to Tuning Policy Name and select the tuning policy you created. Save. Configuring the BACnetDevice to use COV Open the BACnetDevice under the BACnetNetwork Set the "Use Cov" property to True. Note: Typically, you create multiple tuning policies in the BACnetNetwork—especially if you have multiple BACnet network ports enabled. This allows you to reference different tuning policies from BACnet proxy points under different networks (often with vastly different performance capabilities). For example, points under a BACnet MSTP network would likely use different tuning policies than those under a BACnet IP network. Reference the "About BACnet Tuning Policies" section of the Niagara AX-3.x BACnet Guide document for additional information.  

Issue When using OPRIF 11.6, the Microsmart "Upload" command locks up the program. After selecting a Microsmart to upload, OPRIF 11.6 stops responding and must be forced closed. Product Line TAC IA Series Environment OPRIF 11.6 Cause The file path where OPRFI 11.6 installed is too long. Resolution OPRIF 11.6 by default will install in the following default directory (x = drive letter): x:\Documents and Settings\username\Local Settings\Temp (Windows XP) x:\Users\username\AppData\Local\Temp (Windows 7) If OPRIF is already installed, uninstall it.  Re-install it using a different folder (of your choice).  For example, many users will select the drive's parent folder (C:\ or D:\).  The DCT, DMS VDI, and DOI folders will be created in the parent folder. Microsmart uploads will now work correctly.

Issue WorkPlace Tech Tool menu functions and toolbar icons do not respond when selected even though they are visible (not grayed out) after changes are made to the Visio Menus or Toolbars. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software Cause Some COM add-ins are not compatible with the WorkPlace Tech Tool software. Resolution From the Visio menu, within WorkPlace Tech, select Tools / Customize then select the Toolbars tab. Select each checked toolbar in turn, clicking the reset button for each one. Next select the Options tab and click the "Reset menu & toolbar usage data" button. If this does not correct the issue, disable the COM add-ins and delete the Visio directory cache using the procedure listed below. The procedure depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Options. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for the ",Send to Bluetooth", and any other third party add-ins. Click OK to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WorkPlace Tech, all menu items should be there. If some or all of the WorkPlace Tech Tool menu entries are still grayed out, repeat these steps, disabling all COM add-ins. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there. Workplace Tech with Visio 2002 Open Visio 2002 Open the Tools menu. Select Options, then Advanced. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2002. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\VISIO.BIN If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\VISIO.BIN Open Visio 2002 and wait while Visio updates its directory cache. The process is complete when the "Choose Drawing Type" window is displayed. Close Visio 2002 Open WPT, all menu items should be there.

Issue Is it possible to just install the IA Commissioning Tool (WPCT) or IA Flow Balance Tool without having to install WorkPlace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Flow Balance Tool Cause  WorkplaceTech is not required on the PC but the operator needs to use the WPCT and or Flow Balancing Tool. Resolution It is possible to install the WPCT and/or the IA Flow Balancing software without having to install WorkPlace Tech.  At the time of the WorkPlace Tech installation, there are three options to select from: WorkPlace Tech Flow Balance Tool Workplace Tech Commissioning Tool WorkPlace Tech 5.x. WorkPlace Tech Flow Balancing Tool is preselected.  It cannot be deselected – it must be installed.  You can choose to install the WorkPlace Commissioning Tool by selecting it. If WorkPlace Tech is not needed then do not select the box next to it. WorkPlace Tech will not be installed during the installation process.

Issue In the Niagara G3 ASD Device Manager, MicroNet 2000 devices can not be discovered. Product Line TAC IA Series Environment I/A Series G3 ENC-410 or ENC-520 MN-ASDI integrator with attached MN-FLO / MN-FLO3T / MN-HPFC devices Cause It appears that the ASD Device Manager checks all MN-ASDI integrators, with DIP switch addresses 1-7, for devices in the range of 1-31 under them. Resolution When using the ASD Device Manager to discover MicroNet 2000 devices (MN-ASDI integrators on the ASD bus, and the controllers on the U-buses under the integrators), set the Start Address and End Address in the range of 1 -31. For example, assume there is an MN-ASDI with DIP switch address = 2, and on the U-Bus under the integrator there is an MN-HPFC with DIP switch address = 3. In the Discovery Filter, set the Discover Mn2k flag= true, Start Address = 1, and End Address = 31. The Device Manager will put a MnHPFC_35 object and a MnGen_32 object in the upper pane. The ASD Device Manager assigned an ASD device address = 32 to MN-ASDI, and an ASD device address of 32+3 = 35 to the MN-HPFC. It appears that the ASD Device Manager checks all MN-ASDI integrators, with DIP switch addresses 1-7, for devices in the range of 1-31 under them, and then assigns an ASD device address in the range of 32 – 224 to the integrators, and in the range of 1-254 to the MN-FLOs and MN-HPFCs.

Issue When starting TreeTech communications one or more error messages similar to the following will be displayed in the "... Licensing System Error" window. N8K PTP ... License Expired N8K Serial TLP ... License Expired N8K Ethernet TLP ... License Expired DMS PTP ... License Expired DMS Serial TLP ... License Expired DMS Ethernet TLP ... License Expired Product Line TAC IA Series Environment Windows 2000 or Windows XP (TreeTech 1.x) Windows Vista or Windows 7 (TreeTech 3.0)  Cause No license installed for the IOS (I/O Support module) required for communications between the TreeTech software and the field panel.  Resolution Use the "Purchase WIB Software" to purchase a license for each of the required IOS modules. The following modules are available: IOS-SRL Serial I/O server for NETWORK 8000 and DMS IOS-NW8-ETH NETWORK 8000 Ethernet I/O server IOS-DMS-ETH DMS Ethernet I/O Server (The following license is available only to partner offices for use on the engineer's desktop and laptop computers) IV-DEMO-CDE InVue Demonstration Package (includes Tree-Tech and all IOS drivers)   After adding the desired modules to the license form, click the "Accept Order" button and select the option to save the order to a file. The saved file may then be emailed to IASeries.WIB_Order@schneider-electric.com for processing.

Issue LON bindings stop updating in a Niagara R2 UNC station. The following message also appears in the standard output window: MESSAGE: Unmatched LonWorks response received! [LonCommReceive.run] The LON bindings are re-bound but the problem re-occurs. Product Line TAC IA Series Environment  Niagara R2 UNC Cause This message indicates that a LON controller is sending a message to the UNC's subnet/node address that the UNC cannot match to its LON database. This happens when a controller has not had its binding table updated. Resolution Make sure the UNC is the only LON network management tool used on the associated controllers. Compare the UNC's LON database information to the data actually held in the associated controllers. Right click on the LonWorks Service and select Lon Utilities Manager. Leave the "device" to 'localLonDevice' and set the "Command" to 'reports' and the "SubCommand" to 'verify.' The resulting output will show any mismatches in the various tables. To correct, re-commission the localLonDevice, re-commission all other devices (which clears their tables), and then re-bind all listed bindings. Re-run a 'reports' > 'verify' to ensure all devices are up and running on the network.

Issue When using "link builder" in WorkPlace Commissioning Tool, MNB-V2s and MNB-300s link OK but links to MNB-1000s do not work. Product Line  TAC IA Series Environment WorkPlace Commissioning Tool I/A Series MNB VAV I/A Series MNB 70 I/A Series MNB 300 I/A Series MNB 1000 Cause An incorrect value set for APDU retries in the MNB-1000. Resolution Use WorkPlace Commissioning Tool to display the devices, and double click the MNB-1000 in question to display the Device Properties window. Select the Advanced tab and ensure APDU retries is not set to 0. If it is, set it to 3, reboot the controller and the links will function properly.

Issue For the Niagara R2 MicroSmart Driver (ibsMs), what are the latest firmware revisions for MicroSmart controllers that are supported? Environment ibsMs MicroSmart controllers Cause Check and upgrade MicroSmart controller firmware to the latest firmware to avoid intermittent problems. Resolution ibsMS a Supported Controller Part Number Cntlr Type Cntlr Level Description P/N To Order Firmware P/N Revision CheckSum IC# Yes 1 ENV-III AHF L11 Anemostat Envirotrak III PROM-KIT-10 PROM-48-119 11.1X $8F1E IC12 Yes 1 ENV-III-MPC AHG L11 Anemostat Multi-Purpose Controller PROM-KIT-11 PROM-48-120 11.1X $63F1 IC11 Yes MN-MSI MIM L11 Integrator for MicroSmart Bus PROM-KIT-4 PROM-42-100 11.1T $0B48 IC20 Yes MSC-L1000 ELC L11 Lighting Controller PROM-KIT-16 PROM-48-125 11.2H $31B4 IC3 Yes MSC-MPC-001 HPA L11 Multi - Purpose Controller PROM-KIT-5 PROM-48-104 11.2H $2996 IC11 Yes MSC-P-751/752/753/754 SVA L11 Package Unit Controller PROM-KIT-7 PROM-48-106 11.2H $B762 IC3 Yes MSC-P1501/1502/1503/1504 PCB L11 Package Unit Controller (early version) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-P1501/1502/1503/1504 PCC L11 Package Unit Controller (enhanced AI) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-V-511/512/521/522 VAC L11 VAV Controller PROM-KIT-9 PROM-48-107 11.2H $7D17 IC9 Yes MSC-V-751/752/753/754 SVA L11 VAV Controller PROM-KIT-8 PROM-48-106 11.2H $B762 IC3     ELC-001 SVC L10 SiteManager Controller PROM-KIT-12 PROM-48-121 10.2 $C708 IC4 Yes 1 ENV-III-MPC AHE L10 Anemostat Multi-Purpose Controller N/A       IC11 Yes MSC-MPC EHP L10 Multi - Purpose Controller PROM-KIT-2 PROD-EHP 10.3 $0FEE IC11 Yes MSC-P1000 ELP L10 Enhanced Low PUC PROM-KIT-13 PROM-48-122 10.1 $C25B IC18 Yes MSC-P2000 EMP L10 Enhanced Medium PUC PROM-KIT-14 PROM-48-123 10.1 $AC7A IC24 Yes MSC-U1000 EUC L10 Enhanced Unit Controller PROM-KIT-3 PROD-EUC 10.4C $945F IC21 Yes MSC-V501/502 VAD L10 VAV Terminal Controller PROM-KIT-17 PROM-48-126 10.4D $345C IC9 Yes MSC-V501/502 VAB L10 VAV Terminal Controller PROM-KIT-15 PROM-48-124 10.3 $017C IC12   Yes 1 ENV-IIB (N1-1087) A2B L9 Anamostat (2) Fume Hood Controller N/A PROD-A2B 9.1 $6858 IC23 Yes 1 ENV-II(N1-1058) AHC L9 Anamostat Unit Controller PROM-KIT-1 PROD-AHC 9.1 $320F IC37 Yes MSC-GPC GPC L9 General Purpose Controller PROM-KIT-18 PROM-48-736 9.4C $4E78 IC25 Yes MSC-IOC SIO L9 Input/Output Controller PROM-KIT-21 PROM-48-739 9.4C $64A7 IC43   MSC-L-100 MLC L9 Lighting Controller PROM-KIT-25 PROM-48-743 9.1R $AA35 IC5 Yes MSC-P-100/112/120 LPC L9 Low PUC PROM-KIT-22 PROM-48-740 9.4C $C9FE IC17 Yes MSC-P-200 MPC L9 Medium PUC PROM-KIT-20 PROM-48-738 9.4C $9031 IC23 Yes MSC-T-100 STC L9 Temperature Controller PROM-KIT-23 PROM-48-741 9.4C $558E IC6 Yes MSC-UC UC L9 Unit Controller PROM-KIT-19 PROM-48-737 9.4C $FB25 IC22 Yes MSC-V-100/V110 VAV L9 VAV Terminal Unit Controller PROM-KIT-27 PROM-48-749 9.4C $45AE IC12 Yes MSC-V-200 VSD L9 VAV Terminal Unit Controller PROM-KIT-24 PROM-48-742 9.4C $5CE8 IC13   MSC-V-200E (ETI) VE1 L9 VAV Terminal Unit Controller N/A TEST VE1 9.0C $6A7E IC13 Yes MSC-V-300 VDD L9 VAV (Dual) Terminal Unit Controller N/A PROD-VDD 9.3 $7DC6 IC15 Yes MSC-V-400 MOV L9 Mobil Package Unit Controller PROM-KIT-26 PROM-48-744 9.4C $5148 IC17 a The firmware revisions listed above were validated with this driver. Other versions may function correctly but were not tested. If difficulties are experienced, upgrade firmware. 1 Controller validated with ibsMS-2.302.514a.v1 or greater.

Issue Can all the RAM be used in a MNL controller? Environment MNL controller Cause After doing a compile in WorkPlace Tech, there are only 8 bytes left in the RAM available (shown in the Application Statistics window).  Is there a concern if the application uses all available RAM?  Resolution The controllers are designed to operate whether there is leftover application RAM or not.  Use the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254) to see the RAM memory requirements for each object.

Issue How can the resource count be found for a Niagara R2 station? Environment Niagara R2 station Cause User can't locate the Resource counts using Workplace Pro or a web browser. Resolution There are two methods. Using Workplace Pro, Open a station (Note:  the station must be running)  Highlight the station name Select Search > Resource Count in the drop-down menu bar (alt-R shortcut) Using a web browser, In the address bar, type http://[stationHost]/prism/resources. Sign into the station using an Admin user account. This will display a summary at any level of the database. For each level there is a "Total objects" listing at the top of the page. This is where the resource count is displayed for that level.

Issue "Access Denied" errors are reported during the re-installation of the Niagara R2 software. Environment Niagara R2 software Cause The files installed in the nre\modules folder are write protected. Resolution If an attempt is made to reinstall Niagara R2 software on a computer, an installation error frequently occurs. The Niagara installer (second installation program) progresses one tick on the progress bar then displays a "Module Install Error" window containing the message "Access is Denied". Clicking the OK button to acknowledge the error results in the message window reappearing multiple times. This occurs because the files installed in the nre\modules folder are write protected when installed. To prevent this problem before attempting to reinstall any release of the Niagara R2 software, Open Windows Explorer ("My Computer") Select all files in the niagara\nre\modules folder Right-click on the selected files Select "properties" from the displayed menu. The Properties window appears.  Clear the mark in the "Read-only" box Click the OK button.

Issue Is there a way to backup a Niagara R2 UNC or Enterprise Server station from a web browser? Environment Niagara R2 UNC Enterprise Server XML-capable browser (IE 4.x or higher) Cause Need to save the station's database on the PC for possible restoration. Resolution Yes but note that this method will only backup the station database.  It will open the entire station database in XML format on the webpage.  Depending on the size of the station it may take a long time.  It is best to use this method if Workplace Pro is not available. Follow the steps below to create a station backup of a UNC or Enterprise Server via a web browser: Log into the station via a web browser Navigate to the following URL:  http://[ip-address]/prism/backup. Watch the lower left hand corner of the web browser.  The web pager loader indicator must finish. Once the web page indicates that it is done, save the page as a XML file to your PC.  Use the “Save As” choice to do this step. For more information review Appendix B of the Niagara Browser Access Guide.

Issue Is WorkPlace Tech 5.x compatible with Microsoft Windows 2000 Professional and Visio 2002? Environment WorkPlace Tech 5.x Microsoft Windows 2000 Professional Visio 2002 Cause WorkPlace Tech 5.x system specify Visio 2003. Resolution WorkPlace Tech 5.x is designed to function with Visio 2003. However, considerable development testing was done on Windows 2000 Professional with Visio 2002 platforms to verify functionality and compatibility. WorkPlace Tech 5.x appears to be fully functional with Windows 2000 Professional with Visio 2002.

Issue When compiling a WorkPlace Tech application, the error message "Error-Failed to create nci file" appears. Environment WorkPlace Tech Cause NCIs value is out of bounds. Resolution Typically, this occurs when an out-of-range "NA" or "NaN" value is written to a NCI by a Niagara station, LonMaker, LNC or some other head-end device. If this issue occurs, check the values of all NCIs on the application drawing.  Any NCI displaying out-of-range values (i.e. 1.#QNaN, 1.#INF or etc.) should be reset to normal values or "NA".

Issue The following error message appears when adding a LON application to a project in WorkPlace Tech 5.x from the pre-engineered "WPT Applications" zip file: AppXMLAddon Error Code: -2032465751 Code meaning: Unknown error 0x86DB08A9s. Environment WorkPlace Tech 5.x WPT Applications.zip Cause Workplace Tech encountered one or more values in the application that contain invalid characters. Generally, the most common value that causes this issue is the nciLocation SNVT. The value that should be in this SNVT is "/0", but through a previous Microsoft Visio conversion, it was replaced with a "vertical bar" character. Resolution Locate the invalid characters Replace them with valid ones or delete them. Once this is done, select "Application - Rebuild Application" from the drop-down menu.