Issue What is the current firmware revision for a Network 8000 GCM and is an upgrade kit available? Product Line TAC IA Series Environment Network 8000 GCM Cause Looking for a firmware upgrade part number. Resolution The following table lists the part number and upgrade kit part number for the system firmware installed in each version of the GCM, LCM and similar type controllers. The listing of a particular device part number, EPROM part number or Firmware Upgrade Kit part number does not guarantee that the specific item can be ordered. Update - 12/31/2011 - All firmware kits listed below are now obsolete and can no longer be purchased. GCM / LCM Model Current Version EPROM Part Number Firmware Upgrade Kit GCM-84x1x (GCS Version) 5.4 PROM-12-100/200/300 GCMA-120-054 GCM-84x2x (ASD Version) 5.41A PROM-12-120/220/330 GCMA-137-054 GCM-85x1x (GCS-CCL Version) 4.7C PROM-12-110/120/130 GCMA-132-047 GCM-85x2x (ASD-CCL Version) 4.7AC PROM-12-140/240/340 GCMA-141-047 GCMA-114 4.2 PROM-19-100 GCMA-130-042 LCM-84x1x (8k EEPROM) 5.4 PROM-23-100/200/300 LCMA-138-054 LCM-85xxx (CCL Version) 4.7C PROM-23-110/210/310 LCMA-141-047 LCM-88x1x (32k EEPROM) 5.4 PROM-23-100/200/300 LCMA-138-054 GCS-xxxxx 4.0 PROM-18-120 GCSA-103-040 GIM-2100 4.7G0 PROM-12-130/230/330 GCMA-140-047 GIM-MTECH 4.8G2 PROM-12-150/250/350 GCMA-143-048 GCM-ECH-002 (Echelon NIM) 11.1B PROM-48-204 GCMA-147-111 GCM-86x11 (GCS Version) 5.4 PROM-41-100 GCMA-145-54 GCM-86x21 (ASD Version) 5.4A PROM-41-110 GCMA-146-54 GCM-ECH-001 (Echelon NIM) 11.1B PROM-48-203 GCMA-148-111 GCM-ETH-001 (Ethernet NIM) 11.2T PROM-48-202 GCMA-149-113 LNC-100 5.4GL PROM-41-160 LNCA-100-054 SIM-CCM 5.4G3 PROM-41-120 SIM-CCN-U SIM-MTECH 5.4GM PROM-41-150 SIM-MTECH-U SIM-TRANE 5.5GT PROM-41-140 SIM-TRANE-550 SIM-YORK 5.6GY PROM-41-130 SIM-YORK-U

Issue When using WorkPlace Tech on a Windows Vista computer, the LON USB adaptor will not configure properly to work with my site. Environment WorkPlace Tech installed on a Windows Vista computer LON USB adaptor Cause The LON USB adaptor has a communication issue with both Vista and Windows 7. When configuring the LON communications via the automatic option in WorkPlace Tech, this error appears: "Error occurred in SetInterfaceDomain for domain index 0.” After this error, the LON interfaces will no longer function. Resolution A temporary work-around is to identify the domain and use the manual configuration option.  Echelon NodeUtil, Niagara R2 WorkPlace Pro, or Niagara G3 WorkBench can be used to identify the domain, if needed.  If the domain is "0", the "Default Setup" option can be used.

Issue In Niagara G3, how can the status (up / down) of a device object be trended? Environment Niagara G3 Cause Recording a connected controller's communication status Resolution Within the Wire Sheet that contains the device shadow object: Insert a StatusDemux object (from the kitControl pallet, Util folder).  Link the "Status" from the device object to the "In Status" of the StatusDemux object Insert a Boolean Writable object.  Link the "Down" slot of the StatusDemux object to the "In10" of the Boolean Writable object Add a BooleanCov history extension to the Boolean Writable object.  This will then track the up / down status of the device.

Issue In Niagara G3, is there a way to access the Alarm Portal through a web browser? Environment Niagara G3 Alarm Portal Cause Through the web, only the alarm console associated with the connected station can be viewed, and only one station at a time. Resolution The Alarm Portal is a program that runs off the Workbench framework, but can also be purchased as a stand alone product (i.e. no need to purchase Workbench and Alarm Portal, just purchase the portal). With the Alarm Portal software, connecting to multiple consoles at once is possible (similar to using Tools > Alarm Portal within Workbench). The other option is to create a Station Recipient for the desired alarm class in the ENC station's Alarm Service that points to the Enterprise Network Server, and use the server's Alarm Console. As long as the user has permissions to access the alarm console in the server, then the user can navigate to it in the nav tree.  It can also be added as a node in the .nav file for easy access to the location.  The user would still need the appropriate permissions to access the console.

Issue In a Niagara R2 UNC-600 (or UNC-610), when using the Installation Wizard to review installed jar files, this error appears: "Cannot find distribution set platform matching the target installation platform (NT)" Environment Niagara R2 UNC-600 (or UNC-610) Installation Wizard Cause The UNC-600 and UNC-610 use jar files stored in the "nt" directory. This error appears if the "emb" directory is selected instead. Resolution The "emb" directory is used for embedded UNCs like the UNC-410 and UNC-5x0. Selecting the "nt" directory will prevent the error from appearing and allow continuation to the jar file summary review window.

Issue In Niagara G3, how can an objects value be displayed in a graphic and not its status? Environment Niagara G3 Cause Default BoundLabel properties of the object are set to display the value and status. It must be adjusted to display only the value. Resolution In the BoundLabel properties of the object, the default text format is %.% This displays the value and the status of the object. To display just the object's value, edit the format to %out.value% The object will then display only the present value in the graphic.

Issue In Niagara G3, how can a Boolean object's "False" condition be made to disappear? Environment Niagara G3 Boolean Object Cause BoundLabel properties must be adjusted for the desired operation. Resolution In the BoundLabel properties of the object, right-click on the "visible" field, and choose "Animate" In the Animate window, click on the drop-down for the "Converter Type", and choose "I Boolean to Simple" Click the drop-down for the "False Value", and select "false" Click OK to close the Animate window Click OK to close the BoundLabel properties window Save the graphic Now, when the object has a value of "false," it will not be visible in the graphic.

Issue How many histories can be created in a station and how many records are allowed per history? Environment I/A Series G3 ENC, ENS or SoftJace CComTrolCCWEBor CES Cause Technical product information update. Resolution Regardless of platform type, histories are stored under the station's file system (file:^history/). Stations running on a PC-based system (Enterprise Server or SoftJACE) store the histories in subdirectories using segmented files; this provides improved search capabilities over a flat file system. Stations running on a QNX-based system (ENC) store all of the stations histories in a single compressed file (history.zip). A running station opens the history.zip file in the ENC's ram disk space, the histories are compressed and saved to flash whenever the station is saved. Opening the history.zip file to the ram disk eliminates the need to write to the flash drive each time a record is added to the history file.   When the station needs to write a record to a history, it opens the specific history into the running station (either from the file system if PC-based, or from the ram disk if QNX-based). The open history does contribute to the heap.used of the station. The history service has one property 'max open time' (default 5 minutes) which causes the station to close the history from the running station heap if no records have been written to the history for a time period exceeding the 'max open time'.   Each history extension which is added to the station does add slightly to the station resources because the extension is represented in the bog file. When the history is first enabled, the station creates the history file. The initial file includes a 1600 byte header (defines the configuration parameters) and a single page file of 4096 byte size. When triggered by either the collection interval or COV/COS, a record is added to the page file. When the page file becomes full, additional page files are created based on the capacity configuration of the history. History Record Size by Point Type Point Type bytes/record boolean 13 enum 16 single precision numeric 16 double precision numeric 20 string variable length * *NOTE: A single 'string' record cannot exceed one page (4096 bytes)   Since histories count as file descriptors, there is a physical limitation on the number of histories allowed in a QNX-based ENC station. It is recommended not to exceed 800 histories, given the file descriptor limit of 1000. Note: The platform services view of the QNX-based JACE station includes a property to modify the size of the ram disk within defined limitations. Note that the alarm database is also maintained in the same ram disk space. Exercise caution when modifying the default ram disk size; note that allocating additional memory to the ram disk will limit the memory available for other functions by the QNX OS. Reducing the ram disk size too much could result in history or alarm records not being stored properly and erratic station behavior.

Issue When attempting to run the WorkPlace Tech Tool, Application Menu missing or grayed out. All WorkPlace Tech Tool related entries in the Tools menu are grayed out or missing.   Project Toolbars are not displayed. "Unknown error occurred in an add-on to WorkPlace Tech" Environment WorkPlace Tech Tool 5.7.4 and later versions Microsoft  Visio 2003 or Visio 2007 Microsoft Windows XPsp2, XPsp3,  Vista or Windows 7 Cause Various causes beyond the scope of this article. Resolution There are several different reasons why these entries are grayed out or missing and therefore not selectable. The exact procedure for correcting the problem 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 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 each third-party add-in. 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 WPT, all menu items should be there. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Verify that the box for "Enable COM add-ins" is checked. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click [OK] to apply. Open the Tools menu and select Macros then select "COM Add-ins" Uncheck all third-party add-ins shown in the list. 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.

Issue WorkPlace Tech Tool 5.7.4 causes Visio to crash when attempting to open some MNL-800 applications.   The problem occurs with MNL-800 applications that were created with WorkPlace Tech version 4.x where the application does not use the hardware schedule function.  Environment WorkPlace Tech Tool version 5.7.4 MNL-800 application file created with WorkPlace Tech Tool version 4.x Hardware schedule has never been enabled using an earlier version of WorkPlace Tech Tool version 5.x Cause Required hardware tag "DayOfWk" missing (normally shown on left tag rail, if unused in the application). Resolution This problem is automatically repaired in WPT version 5.7.5 or newer. While we recommend upgrading WPT to 5.7.5 or newer, you can continue to run WPT 5.7.4 and  correct the problem by taking the file to a computer running WorkPlace Tech version 5.7.3 and following this procedure: Open the existing file in the existing project (or in a new project). Run the Hardware Wizard and click [Next] twice to display the Time & Schedule page. Check the box  "Enable the built-in schedule" then click [Finish] to update the application file with the schedule reference tags. Run the Hardware Wizard a second time and click [Next] twice to display the Time & Schedule page. Un-check the box "Enable the built-in schedule" then click [Finish] to update the application file removing the unused schedule reference tags. Close the application.  This will save the changes to the application file.  If prompted to convert the drawing, do not convert it. The saved application file will be usable in WorkPlace Tech Tool version 5.7.4

Issue Changing the nci_PowerUpDly value in the MNL-800 has no effect.  With the nci_PowerUpDly set to 120 seconds in the MNL-800, the outputs turned on after 10 seconds, the default setting. Environment WorkPlace Tech, all versions. MNL-800 Cause The nciPowerUpDly provided in the MNL-800 does not function correctly. The design intent of the nci was to determine the time, in seconds, that must expire following a controller reset before the MN 800 hardware outputs (Digital Outputs and Analog Outputs) are activated. Resolution Be aware that the nciPowerUpDly in the MNL-800 does not work properly, and that the outputs are delayed approximately 10 seconds, regardless of the value entered for nciPowerUpDly.

Issue The I/A Series G3 (AX) Lon Tunneling client does not work in Windows 7 Environment G3 Version 3.5.25 and later Windows 7 Professional OS WPT 5.7.5 and later   Cause The G3 Lon Tunnel client is written to run in Windows XP, and is not designed to run with native Windows 7. Resolution Ensure that the NiagaraAX Lon Tunnel Service is started (Control Panel > Administrative Tools > Services) Locate the vlonax.exe file in the C:\Windows\system32 directory. Right-click on the file, and select Properties In the Properties window, click the "Run this program in compatibility mode for:"  box, and select Windows XP (Service Pack 3) from the drop-down box.  Next, check the "Run this program as an administrator" check box Click OK to accept the changes The Lon Tunnel client is now configured to work in Windows 7.  

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue MN-CI revision 4.1 returns an error 511 when sending a “Reset” command to a MicroNet 2000 controller. The controller does reset as commanded. Environment MN-CI rev. 4.1 software, MN-FLO, MN-FLO3T, MN-HPFC Cause The problem is caused because MN-CI rev. 4.1 sends the “Reset” command twice, and temporarily loses communications with the controller. Resolution The error is considered a nuisance and can be ignored.

Issue When accessing the VEO group of an LCM or GCM with XPSI revision 4.1 Terminal Mode, the data is displayed normally for about 90 seconds before it starts to become garbled. The problem begins at the top line of the display and progresses from the top down, one line at a time.   The arrow keys are not operable, cannot move the cursor to select attributes. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Unknown Resolution A work-around is to use a different terminal emulator instead of XPSI revision 4.1; possible alternatives are HyperTerminal or PuTTy.  PuTTY.exe can be downloaded at http://www.putty.org/.  Select putty.exe for Windows on Intel x86.

Issue In XPSI 4.1 Terminal Mode, there is a noticeable delay in the action of the “Escape” key when backing out of a Current Status or VEO group display screen. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Serial communications are slower with the Microsoft port controls used with XPSI version 4.1. Resolution The “Escape” key will work, it just takes a few seconds longer in version 4.1 than it did in earlier versions, such as 3.13.

Issue Alarms in UNC are not archiving to the Enterprise Server. Environment I/A Series R2 Universal Network Controller (UNC) and Enterprise Server Cause The UNC station and Enterprise Server station has their NotificationService 'archiveMode' property set to 'archive_disabled'. This is the default selection and it prevents notification from happening. Resolution Change the default settings in the UNC station and Enterprise Server:  Set the UNC station's NotificationService 'archiveMode' to 'archive_remote'. Set the Enterprise Server station's NotificationService 'archiveMode' to 'archive_local'. (The “archive_local” selection is valid only if the station is running the DatabaseService) The following have to be also correct in order for alarms archiving to happen: AddressBook entries should be properly setup in the Enterprise Server and UNC stations. Refer to Page 1-15 and 1-16 of the Niagara Standard Programming Reference for further information.  Supervisor checkbox in the UNC's NotificationService 'alarmArchiveAddress' property should be checked. NotificationClass(s) in the NotificationService container in both the UNC station and the Enterprise Server station have to be the same.

Issue Cannot enter a "." (period) into an Object Name of an application drawing using WorkPlace Tech 5.7.4 and newer.  It was possible with previous versions. Has this ability been removed? Environment WorkPlace Tech 5.7.4 and newer Cause The change to not allow a period in an Object Name was to make WorkPlace Tech compatible with StruxureWare. Resolution If a period must be use in an Object Name, do the following:  Open Notepad. Type the desired name (including period). Copy and paste it into the object's name.

Issue What is the procedure to upgrade an existing I/A Series Enterprise Network Server to a newer release of the G3 software? Environment Existing I/A Series G3 ENS installation. Newer release of the G3 software to be installed. Cause Upgrade Resolution Back up existing ENS station. Open the Application Director in the existing version of WorkBench and stop the running station then close Workbench. Install new release of the I/A Series G3 software by running the setup.exe program from the distribution file set (expanded zip file or CD). If the installer prompts to allow copying of settings from previous installation, allow the copy to proceed. At the end of the installation process, allow the installer to start the new Niagara Daemon but not Workbench. Under the Stations folder in the old installation of the G3 software, locate the folder for the station that was being run. Copy the entire folder locate in step 5 from the Stations folder of the old installation to the Stations folder of the new installation. Start the new version of the Workbench, then use the Application Director to start the copied station.

Issue Upgrading / downgrading a jar file in I/A Series G3 Environment Niagara G3 (all version) Cause Not applicable Resolution Do the following: 1. Shut down Workbench 2. In Windows Explorer, navigate to the C:\Niagara\<release>\modules directory 3. Find the original module (e.g. tacAsd.jar), and rename it (e.g. tacAsd.old) 4. Copy the new module in to the modules directory 5. Re-open Workbench, then go to Platform > Software Manager 6. Highlight the module (e.g. tacAsd.jar), then click Install, then click Commit 7. The module will be installed, and the ENC will re-boot