Issue Unable to backup an R2 UNC-520 database, receive error  "java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method)            at java.net.PlainSocketImpl.doConnect(Unknown Source)         at java.net.PlainSocketImpl.connectToAddress(Unknown Source)            at java.net.PlainSocketImpl.connect(Unknown Source)            at java.net.Socket.connect(Unknown Source)   at java.net.Socket.connect(Unknown Source)   at java.net.Socket. (Unknown Source)           at java.net.Socket. (Unknown Source)       at tridium.nre.drivers.SocketDriver$TcpSocketFactory.createSocket(SocketDriver.java:690)        at tridium.nre.drivers.SocketDriver.create(SocketDriver.java:216)            at tridium.nre.drivers.SocketDriver$ConnectThread.run(SocketDriver.java:510)" Environment I/A Series R2 UNC-520 I/A Series R2 WorkPlace Pro,  error reported in build r2.301.529 Cause The WorkPlace Pro cannot connect to the UNC-520 at the given IP address.  The error message stems from a bug in the Sun java, "The Socket constructor does not give an Exception on an unknown IP address. It just hangs."  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4232651 Resolution Verify that the UNC is capable of communicating at the IP address specified. For example, if the UNC is rebooting constantly, it will not be able to communicate.

Issue In a Niagara G3 station, the BACnet Service indicates "routing enabled = false", even though it had been set = true. What caused the change? Environment Niagara G3 station in an ENC with BACnet / IP enabled Cause The ENC has detected a routing loop and automatically stops routing BACnet / IP messages, and sets the "Routing Enabled" flag = false. Resolution This can be caused by having two or more devices routing to the same network number.  Network numbers must be unique throughout the entire BACnet network.    Locate and remove the cause of the routing loop, which is more than one path to a BACnet device.   Procedure Details: Open platform director Watch output for network number error.   (e.g. Bacnet Network Misconfiguration detected(3): Network number update frequency indicates possible router loop on network 20!!!)  Check BACnet devices with Routing enable and make sure all networks have a unique network ID. 

Issue Is there a way to display only points currently in alarm in the Alarm Console? Environment G3, Workbench (all versions) Cause Only want to display points currently in alarm in the Alarm Console? Resolution Yes, the Alarm Console’s filter is used to control what alarms are displayed in the Alarm Console window.      Double-click on the ConsoleRecipient object Click on Filter at bottom of window Check the Source State box. Click on the Source State chevron to show filter options Select the alarms states, Offnormal and Fault. Only alarms currently in the Offnormal and Fault states will be displayed in the alarm console window.  (Items not checked will not be displayed.)  Click OK and OK to save.  Click File from the menu and Refresh to update change. Only alarms that are currently in a Fault or a Offnormal state will be displayed in the Alarm Console window.

Issue Is part number 40-1758, end of line resistor, still available for purchase through Schneider Electric?   Environment Network 8000, IA Series BACnet Controller Cause Part is no longer available for purchase through Schneider Electric Resolution Part number (40-1758) specified for the 120 ohm EOL (end-of-line) termination resistor is no longer available for purchase through Schneider Electric.  The resistor is utilized for RS-485 communications trunks (e.g. Network 8000, BACnet, etc.).  This resistor is a common part and is readily available for purchase through electronic stores or catalogs.    The specification for the resistor is as follows: Nominal value: 120 ohm Tolerance: +/- 5% or better Power rating: 1/4watt metal film Temperature coefficient: +/- 200 PPM or better Maximum voltage: 250 volts

Issue The shadow objects are showing orange "fault" but the values continue to update? Environment G3 (Niagara) ENC, R2 UNC Cause A shadow object will go into fault (orange) condition when the LonWorks service is reading a value that it cannot properly decode.  This "fault" condition is usually related to a SNVT enumeration that is receiving a value out of the standard SNVTs range.  This is typically seen with enumerated SNVT types (e.g. SNVT_occupancy, SNVT_lev_disc, etc.).  For example, an application in the controller is programmed to show occupancy as a value of 0 or 100. The user directly connects the object in the application to the nvoOccupancy tag.  Valid enumeration values for this SNVT are 0, 1, 2, 3, etc.. When the value of 100 is read the shadow object will go into fault (turn orange) because a value of 100 is out of the enumeration range the SNVT_occupancy understands.       Resolution Use WorkPlace Tech to evaluate the controller program and correct any object  to SNVT links that could receive a value outside of its acceptable values.  

Issue Much of the literature being used for R2 and G3 reference the Niagara Jace model numbers.  Is there a cross reference list available to cross Jace model numbers to UNC model numbers? Environment Niagara R2 and G3 Cause The provided literature reference Jace model numbers. Resolution A cross of UNC to Jace controllers are as follow:  UNC-410-1                 JACE-403 UNC-500-1                 JACE-501 UNC-500-2                 JACE-502 UNC-510-1                 JACE-511 UNC-510-2                 JACE-512 UNC-520-2                 JACE-545 UNC-600-2                 JACE-NP UNC-610-2                 JACE-NX  ENC-410-1                 JACE-403-AX ENC-520-2                 JACE-545-AX Tridium reference to Ax is Schneider Electric’s G3.  

Issue Will Signal XP software run on Windows 7 in the XP mode? Environment Signal XP, Windows 7 Cause Will Signal XP software run on Windows 7 in the XP mode? Resolution SIGNAL XP software has not been tested or validated to be compatible with the Microsoft Windows 7 operating system or running in either Windows 7 XP or Virtual XP mode. Since the product is obsolete, no further engineering work will be done with the product.

Issue Getting an “out of memory error” when converting a station’s database from Release 2.301.330 to Release 2.301.529. Environment Niagara R2, UNC-520-1, UNC-410-1 Cause The sns file was used to convert database from 330 to 529  Resolution The XML copy of a station’s database should be used when bringing older version of R2 databases forward.  Convert the XML file to DB locally. Any errors will be discovered during the conversion.  Fix any error that may appear.  The database can now be downloaded to the UNC

Issue The Niagara shortcut does not appear on the desktop after installing Workbench.  Also the shortcuts do not appear in the Niagara folder under Start - All Programs. Environment Niagara G3 (all versions) Cause The setup file was run from the compressed file. When downloaded, Niagara builds are saved to the computer’s hard drive as a compressed folder.  Resolution Compressed files must first be extracted before the setup file should be run. Right-click and extract all files from the compressed folder Uninstall the version of Workbench with the shortcut issue Run the extracted copy of the setup program.   The shortcuts should now appear on the desktop and in the Niagara folder under Start – All Programs.

Issue WorkPlace Tech (WPT), application will not compile. Running the “Rebuild Application” feature does not resolve the errors. Are there other workarounds to fix the application? Product Line TAC IA Series Environment Workplace Tech 5.x Cause Some of the shapes are corrupt. Resolution Following is workaround to fix corruption: Open the project and the application that has the problem shapes in WorkPlace Tech. Perform a File, Save As, and select the file type to be “XML Drawing (*.vdx)”, and click Save. Respond “No” when asked “Do you want to save this application to the current project?” Close WorkPlace Tech and respond “Don’t Save” when asked if you want to save the application. Navigate to the user’s “My Documents\WPT Documents\My Projects\” folder. Right click the problem application “.vsd” file, select “Properties”. In the properties dialog, uncheck the “Read only” checkbox, and then click OK. Open the application “.vdx” file directly into Visio. Perform a File, Save As, and select the file type to be “Drawing (*.vsd)”, and click Save. Click “Yes” if prompted to replace the current drawing. Close Visio. Open the project and the application in WorkPlace Tech. Launch the Hardware Wizard and click “Finish”. Perform a “Rebuild Application”. Click “Save”. 

Issue The message “Error: Invalid compiled image file, please recompile and try again.” is displayed when attempting to download an application in WorkPlace Tech (WPT).  The same message is displayed after the application had been recompiled.  Also, the message “Unhandled exception during event” is displayed when opening an application in WorkPlace Tech. Environment WorkPlace Tech 5.x Cause The Workplace Tech application is corrupt. Resolution Use a backup copy of the application.  The application will have to be reengineered if a backup application is not available.

Issue Can not discover the proxy points for an UNC under the ObixNetwork of a Niagara G3 ENS.  Nothing shows up when a Discover is performed. Environment Niagara G3 Cause Obix Thread Pool count set too low in ENS Resolution Increase Obix Thread Pool count in the ENS ObixNetwork Property Sheet. Expand Drivers in the ENS Right-click on the ObixNetwork and select Property Sheet Expand the Thread Pool property Increase the number of threads

Issue Can individual terminals be purchased for the MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller? Environment MNL controllers; MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx Cause Replacement parts ... Resolution The individual terminals are not setup in the system for purchase.  The MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller base assemblies are available for purchase under the following part numbers (MNL-BASE-100, MNL-BASE-150, MNL-BASE-200).

Issue Updated license to add additional BACnet MSTP ports on the ENC and rebooted. After rebooting the added MSTP port could be enabled but the port settings could not be changed. Environment UNC 520 UNC license file shows "numberOfBACnetMSTPTrunks=2" (or 3 or 4) Cause Failure to reboot the UNC after enabling the BACnet MSTP port in the UNC Resolution Reboot the UNC after enabling the BACnet MSTP port. The UNC's BACnet service will automatically detect any saved BACnet port configuration changes and will apply the changes immediately.

Issue Does WorkPlace Tech 5.8 operate in the Visio 2003 and the Windows XP environment? Environment WorkPlace Tech 5.8 Windows Visio 2003, 2007, and 2010 Windows XP Windows 7 Cause NA Resolution WorkPlace Tech 5.8 will run on the Windows XP (sp3) and Windows 7 (sp1) 32 bit version operating systems. WorkPlace Tech 5.8  is compatible with Visio 2003 sp3, 2007 sp1 and 2010 sp1.

Issue The following error is showing up in the Application Director of the ENS: ERROR (09:45:06 26-Jul-11 EDT)(alarm) Cannot write alarm. java.lang.NullPointerException… Environment G3 (Niagara) ENS Cause The number of alarms in the system have exceeded the capacity defined in the AlarmService. Resolution By default the “capacity” for the AlarmService is set to 500.  Increasing this to a value greater than the number of alarms in the system will correct the error, however consider doing periodic Alarm Db Maintenance to keep the number of alarms at a manageable level.

Issue When attempting to run the WorkPlace Commissioning Tool using the BACnet-IP or BACnet-Ethernet protocols, the search stops immediately and the "sweeping flashlight" is not displayed.  No BACnet devices are found. Environment Windows 7 Professional operating system WorkPlace Tech Tool software version 5.7.4 through 5.7.7 and 5.8 Cause The WinPcap ethernet communications driver could not be started causing the network search to fail silently. During the installation of the WinPcap software, the installer presents an option to start the WinPcap driver at boot time.  Due to potential security concerns, it is suggested that this driver be configured not to start automatically when the computer is booted.  When the WinPcap driver has been installed in this mode and the user does not have system administrative rights, the driver cannot be started automatically when needed.  This issue and the required actions were documented in the WorkPlace Tech Tool 5.7.4 and 5.7.5 release notes. Resolution As published in the release notes document, there are two different ways the issue can be handled. Turn off Windows U.A.C. (Not recommended for security conscious users) Open the Windows control panel and select User Accounts.  If the control panel display is organized in the "Category" view mode, select "Add or Remove user accounts" then select the "Go to the main User Accounts page" link. Select "Change User Account Control Settings". Drag the displayed slider to the bottom position, "Never notify" then click [OK] to save the setting and exit.   Configure the three WorkPlace Tech Tool programs to run with administrative rights. (May not be allowed on some customer owned computers).  NOTE: When the WorkPlace Tech Tool programs have been configured in this manner, the User Account Control screen stating "Do you want to allow the following program to make changes to this computer" will be displayed each time one of these programs is run. It is necessary to click the [Yes] button to allow the program to run. From the Windows start menu or from the desktop select "Computer". Navigate to the folder "\Program Files\WorkPlace Tech" on the local disk C: (or the local disk where the WorkPlace Tech Tool software was installed. Right-click on the application WPCT (may be shown as WPCT.exe) and select Properties from the displayed list.  Click on the "Compatibility" tab then click the button [Change settings for all users].  In the "Privilege Level" section, check the box "Run this program as administrator".  Click [OK] to save the change and close the "All Users" compatibility options window.  Click the [OK] button to close the properties window. Right-click on the application WPFB (may be shown as WPFB.exe) and select Properties from the displayed list.  Click on the "Compatibility" tab then click the button [Change settings for all users].  In the "Privilege Level" section, check the box "Run this program as administrator".  Click [OK] to save the change and close the "All Users" compatibility options window.  Click the [OK] button to close the properties window. Right-click on the application WPTech (may be shown as WPTech.exe) and select Properties from the displayed list.  Click on the "Compatibility" tab then click the button [Change settings for all users].  In the "Privilege Level" section, check the box "Run this program as administrator".  Click [OK] to save the change and close the "All Users" compatibility options window.  Click the [OK] button to close the properties window. Close the Windows explorer window. In the event that a customer's security policy prohibits either of these methods of security permission control, the alternative is to uninstall the WinPcap program and reinstall it (by running the WorkPlace Tech Tool installer), configuring WinPcap to start automatically when the computer is booted.

Issue How do you sort the displayed list of applications and folders within a WorkPlace Tech project?  There does not seem to be any order to the displayed files and folders. Environment WorkPlace Tech Tool version 4.x WorkPlace Tech Tool version 5.x.x Cause The initial display order for the folders and files contained in the WorkPlace Tech project is a function of Windows and its searching processes.  Files added to the project as a group appear in alphabetical order, top to bottom.  Folders added to a project as a group are added in reverse alphabetical order.  Any new folders and or files will automatically be added to the top of the project list.  When a group of folders or files are added to the project, they will be ordered as described above.  There is no option for reordering the order of the files and folders in the displayed contents of an existing project Resolution The easiest solution to this issue is to import the existing group of application files and folders into a new project.  Use the following procedure: Open WorkPlace Tech (WPT) and create a new project. Close WPT Open the existing project folder using the Windows Explorer. Select all files and folders in that project folder and copy them to the new project folder. Open WPT and open the new project. Add the existing files and folders to the new application using the following steps: Open "Add Application To Project". Select the "Unassigned File" tab Make sure all files shown are selected. Click the [OK] button to add the selected applications and folders to the project. This process orders all application files in alphabetical order and all folders into reverse alphabetical order.  All applications contained in folders are also placed in alphabetical order.

Issue Can I purchase a replacement battery for part number E17-140? Environment DMS 35, DMS 350A, DMS 3500, DCM, MSC-MPC Cause E17-140 battery is obsolete and no longer available for purchase. Resolution Purchase replacement battery E17-131. The E17-131 battery is specified for use with the DMS-35, 350, 3500, and DCM.  This battery may also be marked N100-5058.   The E17-140 battery is specified for use with the MSC-MPC and may be marked N100-5074.    Both batteries are rechargeable Nicads.  The E17-131 battery has a slightly larger mAh capacity and a wider temperature operating range.  The E17-131 battery can be used in in place of the E17-140. UPDATE MARCH 2016:  The E17-131 is no longer available for purchase.  Try this supplier:  www.tnrtechnical.com

Issue Attempting to downgrade the ENC-410 or ENC-520 using the Commissioning Wizard can corrupt the ENC file system making the ENC become unusable. Environment I/A Series G3, ENC-410, ENC-520 Cause Attempting to downgrade the ENC-410 or ENC-520 using the Commissioning Wizard can corrupt the ENC file system making the ENC become unusable. Resolution Downgrading from one software release to an earlier release can present compatibility problems. This applies particularly to QNX-based ENCs, as binaries for the (QNX) OS are included in dist files.  However, at times it may be necessary to install an older release onto a ENC, or to restore a ENC to a known good state. To downgrade a ENC, or otherwise “wipe it clean to start over,” a clean distribution file must first be installed.  The following procedure is also detailed in the Niagara AX Platform Guide included with the G3 software. Installing a clean dist will wipe the file system and install an appropriate version of Niagara platform daemon, resetting the unit to a “near factory state.” Only the following settings are preserved: • TCP/IP settings • license files • brand.properties All other data is removed from the file system, including station bog files, Px files, modules, etc. In addition, a clean dist restores the factory-default platform credentials and port (3011).  Therefore before installing a clean dist file, make sure to backup station files plus any other modules on the ENC you wish to keep. Remember, that a “Station Backup” creates a dist file that (when restored) includes the same level of software installed at backup time, so instead of (or in addition to) this type of backup, you may wish to use the Station Copier. Note that after installing a clean dist, you must recommission the ENC, using the Commissioning Wizard. --- To downgrade a QNX-based ENC from any G3 3.x build to an earlier release: Step 1: Before installing a clean dist file, make sure you have backed up the station files plus any other data and modules on the ENC you wish to keep. Step 2: Start G3 3.x Workbench and open a platform connection to the ENC. Step 3: Open the Distribution File Installer and click Cleaning button for the !/cleanDist directory. Step 4: Select the appropriate clean dist file for the platform and install.  The file system clean will take a few minutes, then the ENC will automatically reboot. Wait for the reboot to complete. Note: After reboot from a clean dist install, the ENC is using default platform credentials and port (3011). Step 5: Re-install the software versions to the ENC. Use a version of Workbench that runs the same software versions that you want on the UNC, and use the platform Commissioning Wizard to install the desired software build. For details, refer to the section “About the Commissioning Wizard” in the JACE NiagaraAX Install and Startup Guide.