Building Automation Knowledge Base

Issue Lmtools cannot start/stop service or make changes to license method Environment Vista 5.1.0 or higher Windows Vista, Windows 7, Windows Server 2008 Cause Due to the security rules in Windows Vista or Windows 7 when UAC is enabled Lmtools does not have access change the properties of the license tools and start or stop the service. Resolution Configure Lmtools to Run as Administrator In the start menu browse to "All Programs\TAC\TAC Tools 5.1.x\Lmtools" or "All Programs\Schneider Electric\TAC Tools 5.x.x\Lmtools" and right click on the shortcut and select Properties. In the compatibility tab click the "Run this program as an administrator" and click OK. When you run the Lmtools program it will prompt you to allow access to the computer. Select Allow. Note: These steps will have to be done each time you install Vista on the computer.  

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 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 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 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 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 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 Vista Webstation crops printouts when set to scale to fit on the page Environment Vista Webstation Internet Explorer Cause Automatic scaling, or scale to fit, is not properly sizing the print job. Resolution If you are not getting a complete printout of the trend log, or have portions of it cropped off at the edge of the page, scale the print size manually rather than using a scale to fit feature.

Issue Vista Server - "Comm port not configured" error message Environment Vista Workstation LonMaker Cause While reviewing the EMS if mouse over a point you get a "comm port not configured" error message and points appear offline. This isn't a Vista Server issue however its an LNS issue resulting in the lonmaker protocol not working correctly. Resolution Open LonMaker You should receive a "recovery - global" error message. Close LonMaker  Proceed to the following path on the clients computer. C:\Lm\Db\projectname\recovery Find the "objects.dat" file. This file should disappear when Vista and LonMaker aren't running. Shutdown Vista Server and LonMaker and see if the file disappears. If it doesn't then this file has been corrupted and needs to be deleted. Once you delete the file open LonMaker and verify the error message is gone. Once verified, start Vista Server and check communication and the "comm port not configured error message should be gone as well.

Issue When trying to right click on the Xenta object in LonMaker to get the Plug-in option, it is not in the dropdown list. Unable to open plug-in for Xenta 100 series devices Environment Xenta 100 Plug-in LonMaker NL220 Xenta 101-VF, Xenta 102-ES, Xenta 102-B, Xenta 102-VF, Xenta 102-EF, Xenta 103, Xenta 104-A, Xenta 110 Cause If the option to launch a plug-in is not available, it may be because the plug-in is not installed and/or registered.  Plug-ins for most Xenta 100 devices are accessed through the function block, right-clicking on the controller will not bring up the correct menu. Most LON plug-ins are launched by right-clicking on the function block, not the controller.  The exception to this rule is the Xenta 102-AX, which requires you to right-click on the controller. Resolution Ensure the correct version of the plug-in you are trying to launch is installed and registered. Navigate to LonMaker > Network Properties > Plug-in Registration > Already Registered. If not, Register. In general, Xenta ASCs require you to right-click on the function block and select Plug-Ins to launch the plug-in. Note: It may be necessary to first add a function block in LonMaker, even if SNVT bindings are not required.

Issue It is not possible to access graphics in a Xenta 5/7xx from a smart phone mobile app. Environment Xenta 511, 527, 711, 731 Smart Phones: Apple iPhone, iPad, Android Cause Graphics in a Xenta 5/7xx webserver render in the web environment using Java.  There is not currently a smart phone in the market that is works with Java applets. Resolution There is currently no supported mobile solution for viewing graphics in a Xenta web server. 

Issue When service pin the device in LonMaker system plug-in, an error message pops up saying: Neuron ID has been used by another device, and NID went to all 0. Environment Cause some old device information got stuck in the database the device was added into the network earlier, and the user forgot about that Resolution Delete the node/device from the network. Resynchronize the drawing with database. If the device comes back, then means some information was stuck in the database. Simply delete the device again. Resynchronize again to make sure it was truly deleted. Redo this procedure if needed. If nothing changes on the drawing, then the device was added into the network before, now you need to find where it was added. Open the Echelon LNS Report Generator (Start-> All programs-> Echelon LNS Utilities). Select the network Leave the rest sections as default. Click “Generate” to generate the report. Go to the “Report Filename” Path to open the “.csv” file. You can search the problem Neuron ID under NeuronId column. With the information that report provide, you should be able to locate the node in the network. You can go back to your drawing delete it or keep it if that’s a necessary node.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter Will not work with a Dell E6400 laptop Environment PCMCIA slot Cause Dell E6400 Chipset Resolution Go to the Dell website and upgrade your laptops chipset to the latest version from the dell drivers and downloads section. The file download is a self extracting file, follow the instruction provided and when you re-boot your computer your LonTalk PCC-1 PCMCIA Network Adapter should be fully functional. For further information see TPA-SACH-10-0008.00 - LON PCC-10 PCMCIA Card with Dell E6400 Laptop

Issue Not possible to filter alarms on priority using comma. If alarms with priority 1 and 4 to 10 should be shown in the alarm window, it has been possible in earlier versions (before Vista 5.1.4) to write "1,4-10" in the filter for alarm priorities. Today it is not possible to use the comma. An error message saying "Invalid input, check values and syntax" will appear when closing the filter. Environment Vista Workstation 5.1.4 Cause It is only the user interface which will not allow a comma. Resolution Use the raw dialog for filtering the alarm window instead. Hold down Ctrl+Shift and click on the filter button Change APPRIO. Fixed in version 5.1.5.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue taclogdata_log.ldf file is too big Environment SQL 2005   Cause Fail to perform frequent SQL DB maintenance   Resolution To Shrink the LOG file (.ldf) follow the procedure. Connect to taclogdata.mdf using SQL server management studio. Run the following command: dbcc shrinkfile (taclogdata_log,100,truncateonly)   This will reduce the size (taclogdata_log.ldf) to 100 mb. Note : You can get the logical file name for the log by running the following select statement: (select * from sysfiles) The following are the query results: 1          1          6400    -1         6400    2          0          taclogdata         c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata.mdf   2          0          2624    268435456      1280    66        0          taclogdata_log  c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata_log.LDF   If the database has the truncate log checkpoint turned off, then the transaction log file will be shrink to the target size only when the transaction log is backed up. OR If the truncate log on checkpoint is turned on then go to Enterprise Manager - all tasks - and click "truncate log". This will shrink the file down to the target size and will release all the unused space to the Operating System.

Issue The maximum stat adjustment range that can be set using the Xenta 102-AX Plug-in is 10°C (17.98°F) or roughly 5°C (9°F) above and below the base setpoint. This limitation is applied to the 102-AX Plug-In, Operating Parameters, Stat Adjustment Range. Environment Xenta 102-AX Plug-in Cause The LNS Xenta 102-AX Plug-in limits the values that can be written to the stat adjustment range parameter. Resolution Write to the stat adjustment range variable through Vista Workstation.  There is no limitation applied to this value when the LNS Plug-in is not being used.  The point can be found in the Xenta 102-AX controller at VAV_Controller.nviSetpoint.SCPTmaxRnge. If the 102-AX Plug-In is accessed after the change, the plug-in will limit the value again resulting in 10°C (18°F) being written back into the 102-AX.

Issue In some situations, the STR-350 is needed to send an absolute setpoint to another device on the network, and the nviEffectiveStpt is needed to be able to raise or lower that setpoint over the network. When doing this, the nvoSetpoint will not mirror the set value in the nviEffectiveStpt.  Environment STR-350 v1.2 & v1.3 Cause If the nciSendHeartbeat is greater than 0, the stat will only use the adjusted value at the stat and will ignore a network value from the nvi.  Resolution Set the nciSendHeartbeat to 0 and any change on the nviEffectiveStpt will be reflected on the nvoSetpoint and as the current setpoint on the stat.

Issue BACnet values drop out occasionally BACnet devices update slowly, or miss updates Xenta Server must be power cycled to restore communication Environment Xenta 913 BACnet Cause BACnet physical layer best known practices were not followed. Resolution The following must be verified on your installation. The physical BACnet layer must be wired as specified to have the wire grounded at each BACnet card and at the 913. The physical layer must be terminated with end of line terminators of the type specified in the documentation. It is recommended a BACnet segment should not exceed more than 15 per segment. It is recommended BACnet cards must be sequentially addressed leaving the 913 as Master node address 1. The 913 Xbuilder project and BACnet cards must reflect a "max master" setting of the last master address on the BACnet segment. A default baud rate of 38.4k may be attempted but it is safe to slow the network to 19.2k if you experience communication issues.