Building Automation Knowledge Base

Issue Unsure how to enable Demo Mode and what features are available in this mode. Environment Cyberstation webClient Cause Need to know what features are supported and how to use demo mode. Resolution Demo mode will only work on a single PC (Single User mode not LAN mode) if there is no Continuum Security Key plugged into the Cyberstation. Make sure that you have never plugged in a Continuum Security Key to the workstation that you want to use in demo mode. (If you have and it is not working then go here.)   The demo mode gives you access to the following Continuum Security Key options: -B Badging Option -D Data Exchange Option – includes Personnel Import Utility -E Endura integration option -F FIPS 201 option -WCxPRO Option to add web.Client Pro to Single User CyberStation (SU), x user connections = 1, 2 With some limitations: Demo mode lasts for 4 hours and then the Cyberstation will pop a warning message before shutting down "Demonstration Mode" shows on the Continuum splash when starting Continuum. Only one network controller can be used and it must be ACCNetID = 1.   Note: When using Continuum v1.94, or greater, in Demo mode you might experience it being very slow to start, possibly taking up to two minutes to initially startup. See article here for further details.

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 When logging in once the login screen appears again Environment Vista Webstation Windows 2003 Windows 2008 Cause Windows 2003 server and 2008 server have different default security  settings for Internet Explorer and may deny cookies, this problem should not appear in Windows XP if default settings are used, you can also check if it works with Firefox, if it do so its ought to be the security settings in Internet Explorer. Resolution When the problem occurs, there should be a notification after the address bar. Click on that and allow an exception for the IP address for the Xenta.

Issue When attempting to follow the instructions for setting up RAS communication with a Windows Vista or Windows 7 PC, there are instructions that do no apply or RAS will not work. Environment Continuum Windows Vista Windows 7 Cause Microsoft changed the way that RAS is used to communicate in Windows Vista and Windows 7. Resolution RAS is not supported in Microsoft Vista and Windows 7 with Continuum 1.9x or 2.x. This is indicated in the notes on the compatibility matrix when Windows Vista was added as an OS. It's also indicated in 1.93 matrix and now includes this note for Windows 7.  It would require an  additional code revision to allow Windows 7 to work with future revisions of Cyberstation and since demand of RAS has slowed it is not in the roadmap.

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 System generates error "No designated List View for class name" when right clicking a class and selecting view in the Continuum Explorer. Environment Cyberstation Cause This can happen after the default list views have been moved Resolution 1. Delete the default list view objects. 2. Run the Continuum Database Initialization utility. 3. Check the "Create Default List Views" box and update the database.

Issue Some actions selected in the event notification repeat each time an alarm is repeated and others do not Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Some actions can be repeated when using repeat alarms and others are not Resolution Actions that will repeat are:  Display alarm view- time stamp may be the only change Display Graphic Run Program Display Video All these items are listed in the points alarm tab with specific object links at the bottom   Actions that will NOT repeat are:  email pages beep blink print etc

Issue The priority attribute was not specified as configurable. (Subsystem: NS Connections, #11) lcaErrConnPriNotConfigurable An attempt was made to modify the priority attribute; that attribute was not specified as configurable. For network variables, the priority keyword may be included as part of the connection information in the Neuron C variable declaration.  The config and nonconfig keywords specify whether the priority designation can be modified with a network management tool. The default is config. The priority keyword affects output or polled input network variables.  Please refer to the Neuron C Reference Guide for more information. Environment LonMaker Cause Applying a connection description to a new binding that causes a connection error, such as applying a connection description with the priority attribute set to a connection that does not support it, causes this error message to be displayed. Subsequent attempts to add any connection with the default connection description will result in the same error message. Resolution Exit LonMaker Re-open the LonMaker tool.  Then add the connection.  Alternatively, explicitly select a valid connection description other than "Default."

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

Issue When attempting to Discover devices on the Niagara Network getting the following message: java.net.socketException can't assign requested address. Environment G3 (Niagara) ENC Cause The address in the default gateway of the ENC is invalid. Resolution Under the station Platform open TCP/IP Configuration and enter the proper gateway address in the "IPv4 Gateway" field.

Issue Are the Universal Inputs (UI) common isolated from the Analog Outputs (AO) common on the MNL-800? Environment MNL-800 Cause N/A Resolution No, the commons for the MNL-800 Universal Inputs and Analog Outputs are not isolated from each other.