Issue The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Product Line TAC Vista Environment LonWorks Network Cause A LonWorks network test and diagnostic tool are needed. Resolution NodeUtil is a Windows console application that can be used with Echelon’s family of network interfaces (including the PCLTA-20, PCLTA-21, PCC-10, i.LON® 10, i.LON 100, i.LON 600, Loytec Devices, SmartServer, SLTA-10, U10, and U20 network interfaces) to diagnose and configure LonWorks® network interfaces, routers, and devices. NodeUtil is a test and diagnostic tool - it is not a network management tool.  It will not assign destination addresses or bind network variables. Nor will it format LonMark® interoperable device information. This tool can be used in the following conditions: The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Other network test and diagnostic need This software can be downloaded at http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0373-01A The username and password are needed. This site is opened to the public for registration, so everyone can obtain it. Once you are logged in by default "Recommended Downloads" will be selected. Select "Development Tools" instead to locate the NodeUtil software.

Issue After installation of G3 Workbench version 3.4.57 or 3.5.25, the Software Manager on the Localhost may display that the sun-jre-win-x86 VM module is out of date: Environment Niagara G3 version 3.4.57 or 3.5.25 Sun JRE VM Module Cause While this is not a fatal error condition, the module can be updated. NOTE: if the installed version is 3.5.25, replace path references to "3.4.57" in the paths with "3.5.25" Resolution Shut down Workbench Open Windows Explorer, and navigate to the C:\niagara\niagara-3.4.57 directory Rename the jre folder to jre.old Now, navigate to the C:\niagara\niagara-3.4.57\sw\1.6.0.20 directory. Using WinZip, open the sun-jre-win-x86.dist file (or the sun-jre-win-x64.dist file if using the 64-bit version of Workbench). Select all of the folders in the archive, and extract them to the C:\niagara\niagara-3.4.57 directory (see below). Make sure that the “Use folder names” (or equivalent) box is checked. After the extraction, a new jre folder is created. Run the Platform Daemon (Start > Programs > Enterprise Network Server 3.4.57 > Install Platform Daemon) Open Workbench, and then open the Software Manager in the Platform. The Sun VM will now show "Up to Date"  

Issue What is the recommended method to upgrade a Niagara R2 station to a newer version? Product Line TAC IA Series Environment I/A Series Niagara R2 Cause Unsure how to upgrade station databases. Resolution The published upgrade procedure is provided in F-27334. Below is a modified method that also works. Doing station upgrades on the server first is preferred. If there are any errors, they can be addressed without operational interruptions. Using the existing version of WorkPlace Pro (WPP), backup ALL of the UNC and Server databases into XML format. Methods of backing up and converting databases. Open the Enterprise server in WorkPlace Pro. Double click the station name. Select "Commands" and "Backup XML to save the server in XML. Then select "Backup Subordinate XML" to pull all of the UNC databases as XML into the server stations folder.   If not on site but the UNC and Server databases are available, use the DB Admin tab of the Admin tool to convert the databases locally to XML. Now install the newer Niagara revision onto the Server. Copy the stations containing the XML files to the desired WPP revision station folder. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, they can be addressed without affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This saves time later if the UNCs need reloading) Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC it will ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. This will backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. If after following this procedure the station still fails to start, contact Product Support Services.

Issue The Momentary Start / Stop (SS) object in a MNB controller is not working. The OutStrt output property remains ON and does not pulse off. Product Line TAC IA Series Environment MNB controllers Cause Application programming Resolution The OnPulse input property is set higher than the required minimum of 2 seconds.  In order for the logical outputs to work (OutStrt & OutStp), physical hardware tags must be assigned to the physical outputs (AddrStrt & AddrStp).  This is required when using the Momentary SS object in any MNB controller. The following logic can be used in place of the Momentary SS object to generate an equivalent OnPulse.  

Issue The MNB-Vx appears in the Workplace Commissioning Tool in a read-only mode. After downloading a MNB-Vx controller, an error window appears stating "The download was completed but the application was invalid. The device is now running the factory default application". Product Line TAC IA Series Environment MNB-Vx Workplace Commissioning Tool Cause This condition is related to improper AC power provided to the MNB controller. Typically, when AC power drops below 20 Vac, the controller will fall back to a factory-installed application and switch to read-only mode in the Workplace Commissioning Tool. Resolution Fix the AC power supply so that it is within specifications for the MNB controller. Do a hardware reset using the dip switches to get it out of read only mode. Try the download again.

Issue How to display the degrees symbol (°) in WorkPlace Tech. Product Line TAC IA Series Environment WorkPlace Tech Cause Helpful to add a suffix for temperature engineering units. Instead of typing "degrees" or "deg". Resolution In the Constant Object properties (double click or right click - Set Value), click in the Suffix Text field.    Desktop PC: If you have a desktop PC with a full keyboard, press and hold the Alt key and type the number 248 on the numeric keypad. Note: The number keys above the keyboard will not work. Notebook PC: The numeric keypad on a notebook PC is overlaid on the letter keys (M, J, K, L, U, I, O, 7, 8, 9), and requires that the Fn key is held down while using this secondary purpose. The Fn key may be colored blue to match the number keypad keys. Press and hold both the Alt and Fn keys and type the number 248 (KU8). Release the Alt key (and Fn key on the laptop). A small circle ° (the symbol for degrees) should appear. Type an upper case F for Fahrenheit or C for Celsius. Click OK.   Other ASCII symbols are defined at asciitable.com or lookuptables.com.

Issue How can two Niagara G3 stations run simultaneously on a computer? Product Line TAC IA Series Environment Niagara G3 PC Cause To run two stations simultaneously on a PC, you must set up two ports to be different: The http port and the Fox port. Resolution Open the second station offline via My File System – Sys Home - Stations. Go to Services – Web Services – Properties – Http Port. Change it from 80 to 8080. In the offline station, go to Drivers – Niagara Network – Properties. Expand the Fox Service and change the Port to 1912. Be sure to save the changes and the bog file. Go to Platform – Application Director. Start the second station that you just edited offline. You should see the new ports under "Details."  Go to File - Open Station. Enter the IP address, but change the port to 1912. You should now be able to go to the Niagara Network and discover one station from the other on the same IP.

Issue How can a connection be traced in a WorkPlace Tech drawing when it is difficult to see the wire path? Product Line TAC IA Series Environment WorkPlace Tech Cause When working with objects that have numerous connection wires (perhaps an uploaded drawing), it may be difficult to see the wire routing path. The link style is too small, which may be difficult to see the wire routing path. Resolution Click on a wire to select it (green handles appear). Two clicks may be required, since the first click selects the object that the wire is from. Right click on the wire and select Format/Style. In the Line Style pull-down menu, select "Error Box" (a heavy red wire). Click OK Trace and edit the connections as needed.

Issue In Niagara G3 Workbench, how can the size of the wire sheet be adjusted? Product Line TAC IA Series Environment Niagara G3 Workbench Cause Locating the settings to configure the Wire Sheet width and height to increase or decrease the view. Resolution Wire Sheet maximum size limits Starting in NiagaraAX-3.6, you can limit the size of the wire sheet by setting size of the wire sheet in the Options dialog box. From the workbench main menu, select Tools > Options to open the dialog box. Then select the Wire Sheet option and enter a desired maximum value in the Max Width and Max Height fields, as shown, below. Click the OK button to complete the setting change. If you decrease the maximum wire sheet size, objects are repositioned to stay within the view, after the size change. Note: You may need to refresh the wire sheet view to see the changes in wire sheet size and object repositioning. Also, the wire sheet borders may not be visible until you zoom out in the wire sheet view.  

Issue In WorkPlace Tech, monitor tags can not be placed into the open application. They disappear and there is no error message. Product Line TAC IA Series Environment WorkPlace Tech Cause A layer being turned off in error and need to configure the layer setting to Visible. Resolution Below are steps to resolve the issue: Close WorkPlace Tech. Using Windows Explorer locate the VSD file, right click it, and clear the read-only and archive flags.   Open the drawing in Visio. Select "Customize" from the "Tools" drop-down menu. Highlight "Menu Bar" on the Toolbars tab of the Customize window and pick "Reset". Close the Customize window. Select "Drawing Explorer Window" from the "View" dropdown.   Expand Foreground Pages - Device Definition - Layers. Right-click RealTimes and enable Visible.   Close the "Drawing Explorer Window". Save and close the file. Insert monitor tags will now work.

Issue How can a WorkPlace Tech application be identified as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x? Product Line TAC IA Series Environment WorkPlace Tech Cause Jobsite with an installed base of MNL or MNB controllers but the version of WorkPlace Tech used is not known. Resolution NOTE: Do not allow the application to be converted, if so prompted. Open the application file in an appropriate version of Visio. (WorkPlace Tech not needed). While holding down the left-shift key, right click on the background of the application and select "Show ShapeSheet", holding the left-shift key down until the ShapeSheet window is displayed. Verify that the text table window that is opened shows the file name followed by "". If not, close the shapesheet window and repeat step 2. The left-shift key must be held down until the ShapeSheet table is displayed. Look for the "User-defined Cells" table in the displayed information and verify that an entry named "User.wptVersion" is shown. This field will show the version of WorkPlace Tech that created the application. If either the "User-defined Cells" section or the "User.wptVersion" field are not displayed in the shape sheet, the application was created / edited with a version of Workplace Tech prior to version 3.2sp1. Close Visio. Respond by clicking NO if Visio prompts to save the document. In Visio 2010, the ShapeSheet is located on the Developer tab, which is not displayed by default. To show the Developer tab, do the following: Click the File tab. Under Help, click Options. Click Customize Ribbon. Under Customize the Ribbon, select the Developer check box. To open the ShapeSheet, do the following: On the Developer tab, in the Shape Design group, click the arrow below Show ShapeSheet and then do one of the following: To open the ShapeSheet for a selected shape, click Shape. To open the ShapeSheet for the active page, click Page. To open the ShapeSheet for the entire drawing, click Document.  

Issue Is there an easier way to get log information out of a Niagara R2 Enterprise Server station other than by using a web browser, saving the data, and importing it to Excel? Product Line TAC IA Series Environment I/A Series R2 (Niagara) station with logs. Cause Tech tip. Resolution There is no easier way to get log information than to use a web browser, save the data, and import to Excel. However, by default, a query to the archived log limits the number of records to 2500. This limit can be changed by adding $limit=xxxx.  Note:  Attempting to query a large number of records (> 7500) may cause the process to fail due to timeouts. A review of the cloudscape2excel document provides some details.

Issue Configuring LON tunneling in Niagara G3 Product Line TAC IA Series Environment Niagara G3 Cause See below to watch a video document (vdoc) explaining the process to configure Lon tunneling in Niagara G3. Resolution The purpose of this video is to show you how to configure Lon Tunneling in G3. It's already assumed that there is a LON network that has been installed, commissioned, and discovered in the G3 ENC.  

Issue Getting "invalid status error 503" when trying to access a Niagara R2 UNC station remotely Product Line TAC IA Series Environment Remote I/A Series R2 station Cause Issue is due to large number of UNCs on site, and / or high browser traffic. Resolution This is an issue seen from time to time on sites that either have many UNCs present or see lots of browser traffic. Check the system.properties file. There is a line that reads:  webServer.threadPoolSize=15 .       This is the number of web server threads that can be opened to the UNC station.  Each station to station connection takes up one thread, as does a web browser connection.  I believe the JDE takes up three threads when it connects to the UNC station.  If the UNC station runs out of available threads you will see the "503" error. Change that number to 25 or 30 and reboot the UNC. If the problem persists, then change this line to false: ie.activex.activation=true

Issue Is there a way to convert a Trane BCU (BMTW or BMTX) from BACnet/Ethernet to BACnet/IP for integrating to a Niagara R2 UNC? Product Line TAC IA Series Environment Trane BCU (BMTW or BMTX) Niagara R2 UNC Cause There are two components required to change over the BCU from BACnet/Ethernet to BACnet/IP. Resolution A special serial cable is required to download the BCU with the new configuration. Below are the pin outs to make the cable:     Access to the Tracer Summit software. Here are the steps for running the BCUconfig.exe program to change over the BCU from Ethernet to IP: Open Windows Explorer and navigate to C:\Program Files\Tracer Summit\Bin Double-click on BCUconfig.exe Enter the information and select download. Note - This is where you must have the Trane serial cable. The BCU will reset. Now change the Connection type in the Tracer Summit software to IP connection: Open the Tracer Summit software and select Connect. The Site connection Wizard will appear. Select the BACnet/IP radio button. From the Ethernet Configuration window, select the 'open on startup' check box. Select the 'Use BBMD connection' from the BACnet/IP configuration window. Specify the IP address of the BBMD BCU and the UDP port which is the BACnet port. Select Finish.

Issue Unable to upgrade a JACE 8000 to I/A Series Niagara 4.8 or later due to insufficient memory allocation. Product Line TAC IA Series Environment I/A Series Niagara 4 I/A Series JACE 8000 Cause I/A Series Niagara 4.8 or later running on a JACE 8000 will consume approximately 40 MB more memory than Niagara 4.7 due to new features including a new OS (operating system) and JRE (Java Runtime Engine). Resolution The following information will help identify if there is sufficient system memory to upgrade to Niagara 4.8 or later and if not, how to tune memory parameters to increase required system memory. Use the following analysis to determine if a Niagara 4 platform, operating at release 4.7 or earlier, requires a memory allocation adjustment PRIOR to upgrading to version 4.8 or later. Determine the amount of Free Physical RAM in the embedded platform while running the current release (prior to a 4.8 or later firmware upgrade) Open the embedded platform with the Niagara Platform Administrator tools. Check the amount of Free Physical RAM that is currently available. The image below displays where the information is located. If the amount of Free Physical RAM is greater than 40,000 KB (40 MB), the JACE 8000 platform is ready to perform an upgrade to Niagara version 4.8.  If the amount of Free Physical RAM is less than 40,000 KB (40 MB), the platform will require adjustment to the NRE Memory allocation using the steps below. Determine the amount of memory allocation required Subtract the current amount Free Physical RAM (MB) from the required 40 MB allocation. In the example above, 40 MB – 26.3 MB = 13.7 MB. Round this value up 14 MB. Next, add a buffer value of 10 MB to the previous result for a new total of 24 MB. System memory will be freed by reducing size of RAM disk used for histories. Ensure that /mnt/aram0 contains at least this “allocation adjustment” free space.  Using the above example, there is 326,944 KB (approximately 326 MB) of available memory that can be re-allocated to satisfy the additional 24 MB requirement.  Note: If there is not enough free space available in the /mnt/aram0, please contact Product Support for more options. Adjust the NRE Memory allocation Use the Platform Administrator tool to locate and select the Configure NRE Memory button as shown below. Record the current memory allocations for Heap Space and Meta Space by reviewing the memory sizes shown below. Increase the Meta Space by using the Meta Space slider to provide additional working space. Slide the Meta Space adjustment shown below to add 40 MB to the existing value of 48 MB increasing the Meta Space to 88 MB. Increase the System Reserve by the required 24 MB calculated in the example above. Slide the System Reserve adjustment shown below to set the value to 24 MB. Return (increase) the Heap Space back to the original 384 MB size by adjusting the Heap Space slider shown below. The final adjustment will bring the Meta Space back the original 48 MB size by adjusting the Meta Space slider shown below. Save the changes and reboot the JACE 8000.  Using the information from Step 1, verify that the Free Physical RAM is now above 40 MB.  If confirmed, the JACE 8000 platform is ready to perform an upgrade to I/A Series Niagara version 4.8 or later.

Issue There are missing serial ports (COM ports) when viewing the 'SerialPortService' under 'PlatformServices' in a station. Some or all COM ports will be missing. Local serial ports and/or serial ports of the attached modules do not function. Product Line TAC IA Series Environment I/A Series AX Jace 8000 Cause This could show up for several reasons. This was found during an upgrade to Niagara 4.2. It was also experienced when converting a Jace8000 running N4.2 (or lower N4 version) to AX. This can occur with a new out of the box J8000 to AX conversion if you do not first commission the Jace8000 to Niagara 4.4 or above before converting to AX. All of these problems are due to older version USBbinary files not being properly updated during commissioning. The LON option module (side-car) might stop communicating on the LON trunk due to the same binary file issue. Resolution This can be fixed via serial shell; either by direct connecting with a mini-USB cable or via ssh after it is enabled from the Platform Administration view. It is recommended that PuTTY.exe be downloaded and used as the terminal program to access the shell. The directions below are CASE-sensitive and must be entered exactly as shown. We recommend that you do not type these commands, but rather use copy-and-paste to avoid typographical errors. This is especially true of the usbSerialNumber itself -- it is case-SENSITIVE. By default, PuTTY.exe uses mouse-left-click-drag-and-highlight as an automatic shortcut for copy. Mouse-right-click is the automatic shortcut for paste. Once logged in type: Display the USB serial number(s) sh [hit enter] $ ls /etc/usb [this will display the USB serial number(s), if nothing displays see the note* at the bottom] 85091090FPGGS41 [this is an example serial number] Display the available binary files $ ls -Rp /sys/images/usb [this will display the available binary files] /sys/images/usb/applet-flash-sam4s16.bin* /sys/images/usb/vid03eb/pid2404/Tridium232-1_r03.bin* /sys/images/usb/vid03eb/pid2425/Tridium485-2_r04.bin* Note: You could also see '_r05' instead of '_r04'. If this is your result, make sure to update using the line below. /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin* The USB ports unavailable is due to the 'Tridium485-2_r04.bin' (or Tridium485-2_r05.bin) file was not written to the USB serial number file. This can be corrected by updating the USB serial number file with the correct binary file using the statement below. Make sure to replace the X in the statement with the highest number binary found in 'STEP 2' above. $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r0X.bin > /etc/usb/<usbSerialNumber> Update the binary file Using the example serial number and USB binary file found in STEP 2: $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin > /etc/usb/85091090FPGGS41 Make sure to use the serial number found when 'ls /etc/usb' was called. If there is more than one serial number found, write the command multiple times, once for each serial number found. Also, make sure to use the highest USB binary file number found. Currently r05 is the highest number. If '_r05' is returned as the available USB binary file, make sure to use '_r05' when updating the USB serial number. After a reboot, check the SerialPortService to confirm the ports are restored. *Note: if no usb serial number was found using ls /etc/usb another method would be to call for the slog by typing: $ sloginfo An error would have been logged here during the last startup and will display the serial number; example output: Oct 10 13:42:06 1 6 0 serusb_is_device_supported: Device 2 on bus 0 unrecognized. Using CDC-ACM Class Oct 10 13:42:07 4 11111 0 error opening /etc/usb/85091090FPGGS41 rc=-1 In addition to the symptoms listed above, the inability to communicate with the LON option module may cause the any of the following messages in the Serial Shell and/or the Platform Administration System Logs: error opening /etc/usb/<serial number here> rc=-1 U50Read returned unknown rc = 8!!! io_write failed ldvRC=7, length=<various numbers of bytes> The Station will most likely show that the LON network is up, but the LON devices are down. The device fault cause may show "unable to write" or something similar.

Issue BACnet tuning policies improperly applied can cause BACnet network problems Product Line TAC IA Series Environment I/A Series G3 ENC I/A Series AX / N4 Jace Cause Configuration parameters in the BACnet tuning policies can initiate high polling rates, force high volumes of writes, reads, and apply confirmed COV to BACnet proxies in the Jace / ENC. Resolution The following video will help us, Configure the "DefaultPolicy" as well as creating additional tuning policies for BACnet proxies   Apply tuning policies to regulate BACnet network utilization

Issue How to configure BACnet networks in an IA Series Jace Product Line TAC IA Series Environment I/A Series G3 (AX) ENC (Jace) I/A Series N4 ENC (Jace) Cause Need for a detailed approach to IP and MSTP network setup. Resolution This video explains the steps necessary to configure a JACE to Communicate with BACnet IP and MSTP controllers.

Issue What is the procedure for upgrading firmware in an I/A Controller? Product Line TAC IA Series Environment Workplace Commissioning Tool I/A Series MNB Cause Improvements to MNB firmware require upgrades to be made periodically to the controllers. Resolution This video demonstrates how to upgrade MNB devices with the I/A Commissioning Tool.