Building Automation Knowledge Base

Issue An upgrade site that has gone from a 7798b with dialup capability attached via modem to see the I/NET Seven C-Lan network has gone to VoIP phone communication. This changes the dialup communication. How to make this communication work? Environment I/NET Seven communicating with remote dial-up to a 7798b control board using USRobotics modem and analog phone line Cause Changing company structure to Voice over Internet Protocol (VoIP) rather than analog dial-up communications Resolution The Xenta 527 web based router will need to be in place to replace the dialup connection. Add a CLX card to the 7798b so it will work communicating to the 527 web based router (Note: the 7798C has this capability soldered onto the board and is not necessary). XBuilder will be required to set up graphic pages and email alerting if outbound communication from the network is needed.

Issue   Invalid database version. (Subsystem: LNS, #81)[DB #-2038] Environment LonMaker 3.1 Cause A computer running LNS version 3.2 or higher (sometimes called LNS Turbo) can open any LNS database. If the database being opened is LNS version 3.1 or earlier, the database will be upgraded. This process is irreversible. Once the database is upgraded, earlier versions of LNS can no longer open it. The opposite is not true. If a computer running LNS version 3.1 attempts to open a 3.2 database, this error will appear. Resolution The LNS version must be at 3.2 or later to open a 3.2 database. Either upgrade the LNS version on the PC attempting to open the database, or revert to an earlier version of the database before it was upgraded (if possible). To upgrade your LNS version to 3.2: Navigate to http://echelon.com/support/downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks.

Issue "Incorrect or missing I/Net Host Tool license." error occurs when I/NET Host Tool is launched via Vista > Tools > I/NET Host Tool. Product Line TAC INET, TAC Vista Environment I/NET Host Tool Cause "Incorrect or missing I/NET Host Tool license" error will occur if there is a full version of I/NET installed with its own license key. Running the full version of I/NET and launching I/NET Host Tool via Vista, will attempt to open a new instance of I/NET. The system will throw the error message because there is already an open instance with a license that is not the I/NET integrated license. I/Net (2.4X) runs as a service and will also create this condition if a second instance is launched. Stopping the service will allow I/Net to open without error. When using XBuilder to refresh the I/NET network. In XBuilder, upon a refresh, an instance of I/NET Host Tool is launched. If there is a current open I/Net instance, the error is thrown. Resolution This will not affect the network in any way since I/NET Host Tool and the full version use the same I/O Server. To avoid this message, shut down I/NET and I/O Server and start it again via Vista > Tools > I/NET Host Tool.

Issue   PARSER_CODE_ERROR Error in COD file - Error:15 When directly downloading a Menta file a Parser Code Error is displayed. This is a Parser Error that is alerting you to the fact that there is a problem with your Code. An error in the Menta file is stopping it from downloading successfully. Product Line TAC Vista Environment Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Direct downloading a Menta file (via the RS-232 port, a serial cable, and Online Simulation Mode) can bring to light Parsing Errors that are not reported by the System Plug-in. These errors will result in unsuccessful download attempts without any indication of the failure. To find them, direct download the Menta file. The download gets to where it is parsing the file before it fails:  There are three known reasons why the parsing of a Menta file will fail with Error Code 15. With some careful investigation of the error the cause can be determined, although checking all known causes is not prohibitively time consuming. Either the Menta application is too large, contains SmartStruxure Function Block following a cut-and-paste of code, or the file has corrupted public values indicated by the values being shown in scientific notation. Resolution First, determine the source of the error. Three known issues are discussed below: Corrupted public values show in scientific notation The Error:15 window attempts to show the user where in the Menta code the error is occurring. Without a fairly intimate knowledge of the inner workings of Menta, this can be less than helpful. However, if scientific notation in a PVR is causing the error, the error window will show this. The first line states: PVR     3,Z4 R1.0762e-042 This is showing that a PVR in the Menta program has a value of 1.0762e-042. It may take some searching, but you will need to locate the PVR in the Menta file that has this corrupted value and change it back to something valid. Also check public constants in the file to make sure they are not corrupted.   SmartStruxure Function Blocks in TAC Menta application This error also appears if there are any SmartStruxure specific Function blocks in the application. RO, BO, RI, BI, TSCHI, ERROR, II, IO, PI, PO Check the if any of the blocks are in the COD file (in the error window), find the blocks and replace/remove them.   Menta Application is too large The only other option is that the Menta application is too large. So if the Error:15 window comes up and does not indicate scientific notation in any of the values, it has to be that the file didn't fit inside the controller. Check the memory in Menta under Options > Memory Usage. You want to see free space in all categories. If there are any negative numbers then that portion of the application is too large. Bear in mind that this is a simple estimation by Menta as to the memory needed. Trend logs, OP tree, network description files and the Menta application all need to be stored in the controller, so sometimes a very low, albeit positive, number can indicate problems as well. Try cutting down on trend logs or OP trees to free up space if the application cannot be reduced.

Issue How to Rehost an NL220 Dongle to another PC. Product Line TAC Vista Environment NL220 License Transfer Cause Once an NL220 licensing dongle has been locked to a PC, it cannot be hosted to another computer without Newron's involvement. If you use it on another PC, it will be in "MOVED" mode which allows you to do all engineering tasks except for ordering more credits. Resolution You need to "free" the dongle in order to be able to Rehost it on a new computer. Download the NLDongleUtility from Newron Systems here. A login is required, but it is free to register. Make sure the dongle is plugged into a USB port of the PC Launch the NLDongleUtility by going to Start > Programs > NLSuite > NLDongleUtility > NLDongleUtility At the bottom of the screen is a button that says "Free." Click this button. This generates a code in the green tinted window. Use the "Copy" button to copy the code. Paste this code into a "free request" email addressed to fr-newron-credits@abb.com They will reply with an update key that will unlock the dongle and you will then be able to host it on the new computer. When the software key is sent back from Newron Systems re-open the NLdongle Utility click the Free button at the bottom of the program. Paste the Free Key sent from Newron Systems in the Free Key section and click the "Free" button. Open NL220 and confirm the dongle transfer.

Issue Lost NL220 dongle Product Line TAC Vista Environment NL220 Cause Lost NL220 dongle. Resolution Unfortunately, we cannot offer replacement dongles for the NL220 software. The licensing of the software is actually handled by the dongle. The only way we have to replace them is with a new order with Newron Systems. Sometimes rehosting the new dongle does not work. Unable to host a replacement NL220 dongle for a lost dongle contains information that may help if this problem occurs.

Issue What is the preferred method of finding the MAC address of a Niagara R2 UNC? Environment Niagara R2 UNC Cause Determine the MAC address to set up the reserved IP address. Resolution The quickest and easiest method of finding the MAC address of a UNC is by way of the following: From a command window, ping the UNC using the following command: ping IP , where IP Address is the Internet Protocol Address of the known UNC.  After receiving the Ping Statistics, type the following command: arp -a The physical address will then be shown. *NOTE: All UNCs will have the following generic first four octets: 00-20-96-05. The last two octets will be specific to the Serial Number of the UNC.

Issue Xenta error log - NoLink 29 Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause When checking the error log of an Xenta there is a error "NoLink 29". The error means that the network cable has been unplugged or that the Xenta has lost contact with the host in another way. Resolution 1. Check so that there is no loose ends on the TCP/IP cable connected to the Xenta and the router/switch. 2. Check with IT department to see if there has been any planned or unplanned disruption on the network.

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 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 Remote Client Configuration Issues I.Net 2.31 and prior Product Line TAC INET Environment I/Net Seven version 2.xx with need for Remote Client configuration. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.21 to 2.31 release. Resolution There are two different configurations for the Remote Client setup in I/Net Seven. Clicking the links below will open a PDF document which will show how the communication should be setup. This configuration is in the I/O Server under the current profile and can be found in the Workstation Options.   *IP Addresses are for demonstration purposes only.

Issue Update Vista Database fails. Error in the Output Build window states: 6/4/2010 12:00:00 AM Error: Operator unit object defined in TAC Network settings does not exist; Server_Name. 6/4/2010 12:00:00 AM Update Vista database failed.   Environment TAC Vista System Plug-In Cause The operator unit object is the name of the Vista Server that is being updated. If the server has been renamed through Vista Server Setup or (more often) the database has been moved from PC to PC, then the default defined operator unit object may not match the current Vista database.   Resolution Update the Operator Unit Object in the System Plug-in. In the System Plug-in, navigate to TAC Network > Settings... > Network > Operator unit object: Click the browse button (...) Click on the Vista Server object and hit the Select button Update Vista database again. The error is cleared.

Issue How to understand the Time Stamp on the different Xenta 5/7/9xx log reports. Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause When you log in to the Xenta via a webinterface and choose utilities you can choose to view some reports.  The time stamp on different reports are used differently. Resolution When you log in to the Xenta via a webinterface and choose utilities you can choose to view some reports "Error" and "System report" When you open up the Error report you can see this information on top of the screen (System Error Log - Compiled "Date") The Date field are set to the Date and Time you pressed the link, This is because the report are generated the minute you press the link. When you open up the System Report you can see this information on top of the screen (System information overview "Date") The Date field are set to the Date and Time the last event came in (approximately). You also have the System Information log. When you click on this you will see on top System information overview "date" Where the date will be set to the minute you press the button. This is because the report are generated when you click the link.

Issue I/NET - Temporary Individual download problem Environment I/Net Seven using Access Control with at least one host pc for making badges or used for Access Control editing. Cause Download of changes to Access cards or Individual information not getting to the controller right away. Resolution If you add a card to the system and want it to be temporary be sure to check the "Automatic DPU restore" under Edit - Network configuration choose modify the Link. Choose what Host that should handle the request. Listing more than one Host address will increase network traffic and burden the network. I suggest you put a single Badging Machine or Host for Restore host 1. This can be read about in TCON300 under page 5-10.

Issue SQL server uses up my harddrive, templog.ldf is several Gb. Environment SQL Express 2005 Cause In SQL there are some system databases used by the server when administrating data within the server. If you run SQL server for several months without restart, templog.ldf will grow Resolution By adding growth restrictions for tempdb this will not be a problem. Most sites do not have these problems as updates, etc., usually force restarts of the computer.

Issue Which antivirus software is compatible with Niagara R2 and G3? Environment Niagara R2 Workplace Pro (all versions), Niagara G3 Workbench (all versions) Cause Antivirus software can block ports and services used by Niagara R2 and G3 Resolution By default, Niagara R2 software needs the following ports/services/applications "open", or unblocked: Port 80 (station communications & Web access) Port 3011 (Admin Tool) Niagara Service (Control Panel > Administrative Tools > Services) Files in the C:\ < niagara r2 release number > \nre\bin directory By default, Niagara G3 software needs the following ports/services/applications "open", or unblocked: Port 80 (Web access) Port 1911 (station communications) Port 3011 (Platform access) Niagara Service (Control Panel > Administrative Tools > Services) Files in the C:\ < niagara g3 release number > \bin directory Various antivirus software products by default will block one or more of the above, and need to be configured to allow or "unblock" them.  Niagara R2 and G3 software will work with any antivirus program that allows unblocked communication to the above ports, services, and files.   NOTE: The specified ethernet ports must be open bidirectionally for both TCP and UDP traffic.

Issue Error importing I/NET sav file to XBuilder Environment XBuilder I/NET sav file import Cause There's a problem in how the DcuXml.exe and XBuilder handles the import of sav files. If the "home" folder of the Windows user you are logged in with has a ".", XBuilder will import the sav file to the I/NET folder alright, but will actually look for the sav file in the Files folder, so one folder back. Eg. Domain user: br Location of the copied sav file: C:\Documents and Settings\br\Local Settings\Temp\XBuilderPrj\PROJECTNAME\Files\INET (For Win7 & Win Server 2008, it should be C:\Users\br\AppData\Local\Temp\XBuilderPrj\PROJECTNAME\Files\INET. You need to turn on the Show hidden File option in Folder and search options under the Organize menu ) Where XBuilder looks for the sav file: C:\Documents and Settings\br\Local Settings\Temp\XBuilderPrj\PROJECTNAME\Files\INET (For Win7 & Win Server 2008, it should be C:\Users\br\AppData\Local\Temp\XBuilderPrj\PROJECTNAME\Files\INET) Local user: br Location of the copied sav file: C:\Documents and Settings\br.WSDKHER9562\Local Settings\Temp\XBuilderPrj\PROJECTNAME\Files\INET (For Win7 & Win Server 2008, it should be C:\Users\br.WSDKHER9562\AppData\Local\Temp\XBuilderPrj\PROJECTNAME\Files\INET) Where XBuilder looks for the sav file: C:\Documents and Settings\br.WSDKHER9562\Local Settings\Temp\XBuilderPrj\PROJECTNAME\Files (For Win7 & Win Server 2008, it should be C:\Users\br.WSDKHER9562\AppData\Local\Temp\XBuilderPrj\PROJECTNAME\Files) Resolution XBuilder will generate an error, and the import.xml will be locked by the DcuXml.exe process, so you manually have to stop that. What you have to do is manually copy the sav file to the PROJECTNAME\Files directory before you import the I/NET network.

Issue Reassigning a USB Serial Adaptor to a desired COM port Reassigning a USB to DB-9 Adaptor to a desired COM Port Product Line TAC Vista Environment Windows OS Cause It is common for newer laptops to come without DB-9 serial connections. USB to DB-9 adaptors have to be used instead. When this USB device is installed, Windows will allocate the first COM port available in the system. In most cases, this will not be COM1, which is the default port designation for both Menta and the Download Wizard. If COM10 or greater is assigned, then it cannot be used with Menta for a direct download because Menta's COM port designation drop-down list only goes to COM9. Resolution Reassign the USB to DB-9 adaptor to the desired COM port: Right-click on My Computer and select "Manage" In the left pane of the Computer Management Console, select Device Manager. This will populate the right pane with system information. Expand "Ports (COM & LPT)." There will be a list of ports in use and which device is associated to the COM port. Look for the USB to Serial Bridge (COMx). If the USB to DB-9 adaptor is not assigned to the desired COM port, right-click on it and select "Properties." From the Port Settings tab, select "Advanced." In the Advanced Settings is a drop-down menu for assigning the COM port number to this device. Select the desired COM port. If it is noted that the COM port is "(in use)," find the device using that port Reassign that device to another open port. This will free up the desired COM port for the USB to DB-9 adaptor. Changing COM port may take some time for Windows to process and put into effect. Monitor "Ports (COM & LPT)" in the Computer Management Console. This will show the reassigned COM port when the operation has finished. *it is also possible to assign to a port in use which should move the previous device to another com, however this should be used as a last resort.

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 Two different revisions of I/NET 2.31 were created: 2218 and 2227. How do you know which one to use? Environment I/NET 2.31 Cause Inet 2.31 was released with two different builds 2218 and 2227. Resolution The latest build for I/NET 2.31 is the 2227 build. If a site is running the 2218 build, it is recommended to upgrade to the later build since many functions have been greatly improved. Log in to The Exchange Download Center to download I/NET v2.31.