Building Automation Knowledge Base

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 The damper position value sometimes displays as "NA" Product Line I/A Series Environment I/A Series MNB VAV Cause The VAVActuator object in the controller's database has its position initialization mode set to 0 which means it will initialize the position value at its earliest opportunity following a reset. Therefore, the position will display as "NA" until the controller reaches the full open or full closed position Resolution The VAVActuator object in the controller's database has three options for the position initialization mode following a reset. If having the position display NA for a time following a reset is not desirable the position initialization mode can be set to force the controller to go open or closed following a reset and then it will display a value for the position following a reset. The following table is extracted from the WorkPlace Tech 5.x Engineering Guide Supplement. Set the Initialization Mode to 1 or 2 (in the VAVActuator object properties) and download the application. 

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 Standard Applications for I/A Series Micronet BACnet (MNB) controllers Product Line I/A Series Environment I/A Series WorkPlace Tech 5.x and above I/A Series MNB controllers Cause A library of standard pre-engineered applications for MNB controllers is available. These can be modified and used as a reference for creating MNB applications. Resolution The library of standard applications can be downloaded from Exchange Extranet. Below is a list of the applications available for downloads.  DUI Application Stencil Operation Guide Application Objects Visio Stencil (Includes DUI_App) Applications - BACnet Zone, VAV, and Unitary Applications using SP and SPP Momentary Start/Stop Object Application Operation Guide Application - BACnet Zone Controller Applications Application - BACnet VAV Box Applications Application - BACnet Unitary Applications Stencil - Application Stencils Application - VAV_Staged_Heat.vst Application - FC_1DX_1EH.vst Application - FC_1PropCL_1PropHT.vst Application - FC_2Pipe_2PosHC_wCO.vst Application - All BACnet Unitary Applications.zip Application - All BACnet VAV Box Applications.zip Application - VAV_Cooling_Only.vst Application - VAV_Floating_Heat.vst Application - AHU_HeatPump.vst Application - VAV_Parallel_Fan_Staged_Heat.vst Application - VAV_Parallel_Fan_Floating_Heat.vst

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Process to restore MNB-1000 to factory default. Product Line TAC IA Series Environment MNB-1000 Cause If the IP address has been lost or unit has been misconfigured how can this be restored the factory default. *This step should only be taken if the data on the unit is not to be maintained * Resolution On the DIP switch settings, set all of the switches (1-8) to the ON position. Cycle power on the controller. Unit will boot up in reset mode (red flashing status light) Once completed the status light will be solid green. The unit is now in factory default mode The IP address will be 10.1.10.2 with a 255.255.255.0 subnet mask. BACnet IP will be disabled by default and BACnet Ethernet will be active.

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 Unable to send alarm generated emails via the Yahoo’s SMTP server in I/A Series G3. The following error messages are displayed in the console output window when attempting to send a mail via Yahoo’s SMTP server. javax.mail.MessagingException: Could not connect to SMTP host: smtp.mail.yahoo.com, port: 465; Caused by: java.net.ConnectException: Connection refused: connect Product Line TAC I/A Series Environment Niagara G3 ENS ENC-520 ENC-410 Cause An incorrect STMP hostname was used in the “Hostname” of the OutgoingAccount. The correct Yahoo outgoing mail address, “smtp.mail.yahoo.com”, must be entered for in the OutgoingAccount “Hostname”. Resolution Procedure and properties settings required when using the Yahoo SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.mail.yahoo.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@yahoo.com (works without the “@yahoo.com” as well) Password: Your Yahoo account password Enabled: true Use SSL: true (Yahoo requires SSL) Transport: Smtp Use Authentication: true (Yahoo requires authentication when sending out emails) Reply to: example@yahoo.com (“The Reply To” must contain a valid Yahoo account) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Unable to connect to a G3 ENC or JACE after attempting to downgrade or install a station. One of several different errors may be displayed in the serial shell console output.  The following are examples: Could not find library libcpp.so.3 Could not find library libcpp.so.4 Error occurred during initialization of VM - Java/Lang/ No Class Def found error: Java/Lang/object Product Line TAC I/A Series Environment I/A Series G3 ENC and JACE (all revisions), ENC-410, ENC-520, TRD-T-645, TRD-T-603, TRD-RB-645, TRD-RB-603, TRD-J-600E, TRD-T-700 Cause The issue is caused by downgrading the ENC / JACE without following the procedure to first install the clean distribution file. In addition, the ENC/JACE will fail if a station is copied into the ENC/JACE without first installing the OS and NRE software using the Workbench Commissioning Wizard. Note: With G3 release 3.3 and newer, the procedure for downgrading an ENC/JACE is included in the Niagara AX Platform Guide - Downgrading a JACE (Clean Dist). Resolution Tools needed: Null Modem Cable Serial Terminal (e.g. HyperTerminal or TeraTerm) Jumper Obtaining the files required to recover the ENC NOTE: If recovery of a Jace-700 is required, please contact Product Support for the recovery file. Download the appropriate OS image and gz file zip file for the ENC/JACE from the Exchange website - https://ecobuilding.schneider-electric.com ENC-410.zip ENC-410-1 standard memory - etfs512 ENC-410-EM.zip ENC-410-1 extended memory - etfs2048 ENC-520.zip ENC-520-2 standard memory - etfs512 ENC-520-EM.zip ENC-520-2 extended memory - etfs2048 NPM6E.zip JACE603/645, TRD-RB-603/645, JACE600E Note: The files used in the following procedure MUST correctly match the ENC/JACE hardware platform, otherwise permanent damage to the unit may occur. The serial shell can be used to determine the file system requirements (standard or extended memory). To find the exact image needed for an ENC (JACE 2/4/5) execute the following while connected to the unit with serial shell: Log into the unit's menu system using the platform username and password. Type sh to exit the menu system and enter the shell mode. At the # prompt, (type: cat sys/info/fs) and enter This will return the file system type of etfs512 or etfs2048. Extract the OS image and gz files from the downloaded zip to a suitable directory on the local computer (e.g. local hard drive such as: c:\temp). Enable ftp: By default, the ftp port is disabled on every ENC/JACE as shipped from the factory.  Enable the ftp as follows. Set the jumper on the ENC to serial shell mode and connect the null modem cable between the PC and the ENC/JACE. Connect to the ENC using the Serial Terminal program and the following port settings: Baud rate 57600 bps (Note: JACE-603/645 baud rate is 115200) 8 data bits, 1 stop bit, no parity After logging in to the menu system from the serial shell, do the following to enable ftp: Select option 4 from the menu Enter the port number (Normally 21). (type: 21) Press the Enter key to confirm the change Note: Leave the serial shell connection open while performing the next steps. FTP the OS image and gz files On the local system, open a command prompt window and change the directory to the location where the OS image and gz files were extracted (c:\temp). Connect to the ENC via ftp and put the OS image in the /tmp directory entering the following from the command line: Create a ftp connection to the ENC by typing: ftp and enter Type the username and password for the platform when prompted Change directory to /tmp (type: cd tmp) and enter Change to binary mode (type: bin) and enter Download the image to the ENC by using the put command. The image name must exactly match the image extracted from the downloaded zip file. ENC-410-1 standard memory (type: put york-etfs512.image) and enter ENC-410-1 extended memory (type: put york-etfs2048.image) and enter ENC-520-1 standard memory (type: put james-etfs512.image) and enter ENC-520-1 extended memory (type: put james-etfs2048.image) and enter JACE-600E, 603, 645 extended memory (type: put npm6xx-etfs2048.image) and enter Download the gz file to the ENC by using the put command. The name must exactly match the image extracted from the downloaded zip file. Change directory to the root (type: cd ../..) and enter Change directory to /ffs0/zip (type: cd ffs0/zip) and enter Download the gz file (type: put clean.tar.gz) and enter Exit ftp (type: quit) and enter Execute OS image update Return to the serial shell connection Type sh to exit the menu system and enter the shell mode At the # prompt, type: osupdate and enter After a short delay the # prompt will return. Shutdown to reboot the ENC (type: shutdown) and press enter. The ENC/JACE will reboot, install the clean distribution image and perform one additional reboot automatically. The ENC/JACE should now be recovered and allow connection to the platform. Connect and use the Workbench Commissioning Wizard to install the version of G3 required.

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 Settings for the USRobotics 5686 series for use with a DMS panel. Environment USRobotics 5686 series DMS panel Cause For the modems to communicate, V.92 protocol needs to be disabled. Resolution The V.92 protocol must be disabled when using these modems with older modems. To disable the V.92 protocol on a USRobotics 5686 series modems, enter the following setup string (without the quotation marks), in addition to any string specified in the referenced bulletin, before saving the settings: " AT +PIG=1 +PMH=1 +PQC=3 ". Refer to Bulletin 00-19