Building Automation Knowledge Base

Issue The option to purchase a permanent license of WorkPlace Tech, is not selectable in the WorkPlace Tech Purchase software. Environment WorkPlace Tech (all Versions) Cause N/A Resolution Correcting this issue will require the assistance of Product Support Services.

Issue When we open query wizard for building up any query after the year 2010, the maximum end date can be selected up to 2010 only. Environment Vykon Alarm Service  client version 2.4 Cause The Vykon Alarm Service client version 2.4 query range contains a maximum query year of 2010 within the software code. Resolution New VAS Clients (2.50 and 3.92) along with associated release notes have been placed on The Exchange Extranet website.  Please note that you must be a licensed BMS Partner to download the assets. For non-partner, please contact your Schneider Electric local branch or Partner for access.  The VAS_2.50_Client.zip file contains the VAS 2.50 Client Installer and associated Enterprise Server vas service module (vas-2.301.532.v2.jar). VAS 2.50 is for use with Enterprise Servers that utilize database management systems including Cloudscape, MSDE, Microsoft SQL, or Oracle. If currently using VAS 2.4x, upgrade to vas-2.301.532.v2 jar and VAS 2.50 client. If currently using VAS 3.xx, do not install this version. Download and upgrade to vas-2.301.532.v3.jar and VAS 3.92 client. The VAS_3.92_Client.zip file contains the VAS 3.92 Client Installer and associated Enterprise Server vas service module (vas-2.301.532.v3.jar). VAS 3.92 is for use with Enterprise Servers that utilize MSDE, Microsoft SQL, or Oracle database management systems only. VAS 3.92 Is not compatible with Cloudscape. If currently using VAS 3.xx, upgrade to vas-2.301.532.v3 jar and VAS 3.92 client. If currently using VAS 2.4x, do not install this version. Download and upgrade to vas-2.301.532.v2.jar and VAS 2.50 client.

Issue What is the minimum pulse width for an MNB-300 universal input (UI) configured for pulse input. Environment MNB-300 Cause Product Specification Resolution UI1 (Fast Pulse) Minimum rate of 1 pulse per 4 minutes Maximum rate of 10 pulses per second (minimum pulse width 50 mSec) UI2 - UI6 (Standard Pulse) Minimum rate of 1 pulse per 4 minutes Maximum rate of 1 pulse per second (minimum pulse width 500 mSec)

Issue How do I calculate the pulse constant for an MNL-800 BI object configured for pulse input? The Pulse Constant is a user entered pulse scaling value used by the pulse algorithm for calculating the output based on a pulses per second frequency. The range of the Pulse Constant value is 0.1 to 1000. Environment MNL-800 Cause How do I calculate the pulse constant for an MNL-800 BI object configured for pulse input? Resolution Calculating the pulse constant requires the value to first be scaled to the equivalent pulse rate in seconds. Two examples are shown below. The first example represents a water meter that provides a pulse that represents cubic feet per minutes. The meter generates one pulse per minute that represents a rate of 10 cubic feet per minute. The pulse constant calculates on a per second basis so the first step is to determine what one pulse represents as a rate per second. 1 pulse per minute / 60 seconds = 0.0166666 rate per second Next, divide this value into the desired output when this pulse rate occurs. In this case, the rate value is 10 so the pulse constant is equal to 10 / 0.01666666 or 600. The second example represents an electric meter that provides a pulse that represents KW. The meter generates one pulse every 0.5 second that represents a rate of 15 KW. The meter will pulse twice every second (1 second / 0.5 second). The pulse constant is calculated by multiplying the rate value by 2 or a pulse constant of 30. A meter pulsing twice per second will generate an output of 30 KW. Reference the WorkPlace Tech Tool Engineering Guide - Binary Input object (F-26580) for more details.

Issue R2, UNC-520-2 is Displaying “Authentication mismatch” error message for a MNL-800 controller.  How can this error be corrected?    Environment R2, UNC-520 Cause An “Authentication mismatch” error means that the authentication set in the in the LonWorksService does not match what is set in the MNL-800’s shadow object.  One is set to “True” and the other is set to “False”.  They should both be the same.  Authentication is rarely used due to the high overhead associated with its use, so we normally recommend it not be used. Because of this, “Authenticate” should be set to “False” in the properties of both the LonWorksService and MNL-800 shadow object. This error message applies to the MNL shadow objects as well.   Resolution To verify if Authenticate is set to true in the property of the LonWorksService: - Open the Properties of the LonWorksService and click on the Netmgmt tab. The Authenticate property may be set to “True” and grayed out. To verify if Authenticate is set to true in the property of the DynamicDevice: - Open the Properties of the DynamicDevice shadow object and click on the Engineering. The Authenticate property may be set to “True” and grayed out. To verify if Authenticate is set to true in the property a MNL controller: - Open the Properties of the MNL shadow object and click on the General tab and Engineering tab. The Authenticate property may be set to “True” and grayed out.   Steps to set “Authenticate” to “False”: 1. Disable Authentication using Command from the LonWorksService Property view       1. In WorkPlace Pro (WPP), open the station LonWorksService       2. Highlight the shadow objects that needs to be changed to “True” (or simply highlight all of them)       3. Select “Commands” from the WPP menu at top of page       4. Select “disAuth” from dropdown menu and select “Yes”              Note: An error may be displayed stating that the action failed even though it was successful. 2. Recommission each Lon device (if it fails to commission, reset the device then try again) 3. Rebind all affected bindings  

Issue What I/A Series BACnet hardware (MNB) is officially UL 864 listed? Environment MNB UL 864 Cause Many consulting engineers would like documented proof that the hardware within a smoke control system is UL 864 tested and approved. Resolution The Schneider Electric MicroNet BACnet UL 864 case file, outlining exactly what I/A Series BACnet hardware is approved for UL 864 systems can be obtained at: www.UL.com Navigate to the bottom of the home page under Useful links and click on Online Certifications Directory Find the UL File Number field and type s5381 The Schneider Electric MNB file will show up and click the link UUKL.S5381 under the link to file column. This will show you all of the I/A Series hardware that is UL 864 certified, and can be installed in an official smoke control system. Also refer to the I/A Series MicroNet BACnet Smoke Control Systems Manual (F-27419) for further information related UL 864 Smoke Control applications.

Issue Aside from the firmware chip, are the SIM-YORK and GCM-86000 the same circuit board? Environment Network 8000 GCM-86000 series controllers Network 8000 SIM-YORK Cause For in-house programming purposes, a GCM-86000 is available but access to the specific SIM block used with York chillers is not available in the GCM's firmware. Resolution The SIM-YORK and the GCM-86000 are functionally equivalent circuit boards.  The only difference is the firmware.  Swapping firmware with these two controllers is all that's needed to change them into the other.

Issue Attempting to commission a Niagara G3 ENC-520 and an error indicates the nre core distribution files cannot be found on the local computer. The distribution files are typically installed under the Niagara directory in \sw\3.5.34 (or other version number) Environment Niagara G3 all versions Cause The distribution files were not installed on the computer as the checkbox for "This instance of TAC I/A Series Enterprise Network Server will be used as an installation tool" was disabled (or NOT checked) during the installation process. Resolution Re-install the Niagara G3 software version with the checkbox (described above) enabled.

Issue Can the RPTR-ECH-WW repeater be used on a TP/FT-10 LON trunk? Environment RPTR-ECH-WW; a wire-wire repeater for use with Echelon NIMs (GCM-ECH-001, GCM-ECH-001, or DMS-ECH-001) TP/FT-10 LON trunk ( under a UNC, ENC, or LNC-100, for example) Cause The RPTR-ECH-WW is for use on a trunk using the Echelon TP/XF-1250 transceiver, which use a different communications protocol than the TP/FT-10 transceiver does. Devices using different transceivers will not communicate with each other. Resolution No, the RPTR-ECH-WW cannot be used on a TP/FT-10 LON trunk such as the UNC, ENC, or LNC-100s support.

Issue Product Line Update As previously communicated in 2007, there are several important product availability measures occurring at the close of 2008 that impact the NETWORK 8000, MicroNet 2000, and SIGNAL. Environment SIGNAL SIGNAL XP NETWORK 8000 MicroNet 2000 Cause Manufacturability related to low volume, last time buy issues with components, and technology support circumstances Resolution The following product groups will no longer be available for purchase after December 31, 2008 Global Control Modules and Assemblies (GCM-84000 Series) Local Control Modules and Assemblies (LCMs) MICROFLO II Lighting Interface Module (LIM) SIGNAL Schneider Electric will honor all product warranties and will continue to offer repair services and provide Product Support for these products. The GCM-86000 series along with the Network Interface Modules (NIMs), MICROZONE II, PEM, and MicroNet 2000 controllers will continue to be available for sale. Table 1 provides a full list of the part numbers no longer available after December 31, 2008. Click here to review PA-45.

Issue How can it be determined what LonWorks Program IDs are supported by the Niagara G3 system? Environment G3 WorkBench (all builds) Cause N/A Resolution Create and install a test station on the localhost. Open the test station in WorkBench then add LonNetwork to Drivers from the lonworks Palette.   Double-click on the LonNetwork. Double-click on the Local Lon Device listed under Database and set the following properties Channel ID: 1 Subnet: 1 Node: 127 and click OK to accept changes. Right-click on LonNetwork and open the Lon Utilities Manager. Select the Local Lon Device then choose the Command of Reports and Sub-command of program Ids. Execute the command and a listing of all programIDs for the shadow objects found in the local My Module  library will appear. To save - highlight all program Ids and use “Ctrl C” to save to file.

Issue Getting the following error “The webpage cannot be found” and “HTTP 404” when attempting to access R2 Enterprise Server’s alarms database via a web browser.  Also getting the following errors in the Standard Output Window: ERROR: Could not open database connection SQL Exception: Failed to start database 'app' . . SQL Exception: Failed to start database 'app' . . ERROR: Unable to open database java.lang.IllegalStateException: Database not connected! Environment R2 Enterprise Server, WorkPlace Pro (all versions) Cause Corrupt server app folder. Due to the corrupt app folder, Database Service never started; so the alarm pages were never created. Resolution Stop the server’s database and delete its app folder.  A new app folder will be created when the server is restarted.

Issue After selecting a project and opening an application, WorkPlace Tech 5.7.7 successfully connects to a controller.  The monitor tags update.  After disconnecting and opening a second application (same project), WorkPlace Tech cannot connect to the controller. At the top of the window, it indicates that it's connected but the monitor tags remain gray.  The application downloads successfully but that does not help with the monitor tags. The only way to resolve the issue is to close and re-open WorkPlace Tech.  This action allows the first application to connect successfully to the controller but not any subsequent applications. Environment WorkPlace Tech 5.7.7 Cause Import of existing applications Resolution When a computer has been upgraded to WorkPlace Tech 5.7.7, the Projects folder is typically cut & pasted from a previous version. Any application that was from a previous version of Workplace Tech must be rebuilt within version 5.7.7. This step has corrected the gray monitor tag issue in several instances. This applies to both the MNL and MNB product lines. For more information, review Appendix B of the WorkPlace Tech Tool 5.7 Engineering Guide Supplement (F-27356).

Issue The application requires use of an object that only exists in newer versions of the programLib jar file. Environment I/A Series R2 (all versions) Cause Requires use of objects only available in newer versions of the programLib jar file. Resolution There have been no schema changes to the programLib jar file that allows the jar to be installed and used with previous versions of I/A Series R2.  Download and install the latest programLib jar file version from The Exchange Download Center.

Issue Where can I find an End User Guide for G3 that’s not written for developers? Environment G3, WorkBench (all versions) Cause N/A Resolution Each G3 release zip file includes a document folder.  The PDF file titled docNaxBag.pdf (Niagara AX-3.x Browser Access Guide) is an end users guide and can be found in this folder.

Issue Can a Niagara R2 Enterprise Server and Niagara G3 Enterprise Network Server be installed on the same computer? Environment Niagara R2 all versions Niagara G3 all versions Cause None Resolution The Niagara R2 ES software and Niagara G3 software can be installed on the same computer provided the following: The Windows operating system is supported by both platforms (e.g.  Windows XP) Only one Niagara service can run at anytime (so both platforms cannot run simultaneously)

Issue The error messages "Cannot open admin session.java.lang.NullPointerException" is displayed when attempting to open the WorkPlace Pro Admin Tool Environment R2, WorkPlace Pro (all versions) Cause Both R2 and G3 are on the same PC.  Niagara G3 was last run on the PC.  Error is caused by the failure to run R2 "Install Niagarad" after running G3.  The G3 service stays active even after G3 is closed and will continue to be active until R2 "Install Niagarad" is run. Resolution "Install Niagarad" must be run when switching from the G3, WorkBench to R2, WorkPlace Pro. Close all versions of Workplace Pro Click the Start button then click All Programs Select the Niagara R2 release to start then click "Install Niagarad" The Admin Tool can now be opened.

Issue I need to know hardware specifications for the BACnet controllers and cannot find it in any documents.  Environment The specifications given below are accurate as of 6/30/2011 but are subject to change without notice. Cause Not applicable Resolution The memory specifications below are also available in the MicroNet BACnet Wiring, Networking, and Best Practices Guide.  If a formal document for the CPU and I/O specifications is required contact your Regional Salesman or Product Marketing. MNB-V1 and MNB-V2 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution  MNB-70 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution MNB-300 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB, FRAM 8KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution  MNB-1000 Main Control Processor: Freescale Coldfire MCF5485 (32-bit) operating at 200 MHZ Memory: Flash 16MB, SDRAM 64MB, EEPROM 1KB, Boot Flash 2MB Motherboard (Local I/O Processor) Processor: Atmel ATMEGA128 series 8-bit microcontroller running at 16 MHZ Memory: Processor Flash 128KB, SRAM 4KB, EEPROM 4KB.  Motherboard SRAM 256KB, EEPROM 128KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution

Issue The .class files are related to a Cloudscape / Microsoft JVM memory leak eventually causing the hard drive to fill and become unusable.  The station will fail or exhibit slow response (e.g. station operation, opening remote or local library, etc.).  Versions prior to 514 require the use of a garbage collection feature to correct the issue. Environment I/A Series R2 UNC-600, UNC-610, and Enterprise Server Cause Cloudscape / Microsoft JVM memory leak Resolution Builds 330 or earlier - Enable the garbage collection by adding the garbage collection servlet to the root of the station database.  The GarbageCollectionServlet can be found in the tridiumx library (lib jar file - servlets). Copy and paste the servlet into the root of the station. Garbage collection for build 428 and 431 is enabled by modifying a parameter within the system.properties file. Stop the station database. Use the WorkPlace Pro admin tool to open the system.properties file and locate the following line: #gc.daemon=600000 Uncomment (remove leading #) to enable the feature. Save and close the system.properties file. Restart the station database. Builds 514 and higher will not exhibit the memory leak due to the change of the JVM from Microsoft to Sun Hotspot.

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