Building Automation Knowledge Base

Issue Epibuilder Dynamic Text fields are not displaying in a badge layout or Errors related to EpiBuilder or EPIDesigner Product Line Andover Continuum Environment EpiBuilder Badge Layout Cyberstation Cause Install didn't make the connection properly or badging wasn't enabled during the initial Continuum installation or Windows permission restrictions  Resolution From Make Edit badge in Continuum, Open Badge layout in EpiBuilder (If you have a problem opening Badge Layout see Note #2 below) View Options> Data Fields Select Use the data fields defined in a database If nothing is there, click the Other Database button Select Use an ODBC database Select the Data Source button Select System DSN tab and then select EPISDK then OK Click the Select button add the path to SDKNoDB.mdb (C:\Program Files\Continuum\EpiBuilder\Data) Click Open, Click OK All fields should now be available or the error should no longer happen on startup If receiving: ** Error Opening EpiDesigner Configuration Database error when selecting MakeEdit Badge,    Note #1: Permissions can affect the configuration of the Data Sources. If some options aren't configurable or have been changed from the default like buffers are not set to 2047 then try the configuration with increased permissions. Start>run odbc32.exe and check that the System DSN had EPISDK, If not, add it and then follow the instructions able to set the SDKNoDB.mdb  If the site is utilizing hard drive encryption on the hard drive.  Move the sdknodb.mdb to an unencrypted network share to correct the errors after updating the episdk datasource.  Note #2:  If you cannot perform step #1 from above check the following: On a 32 bit system run the following command from either the run window:  odbcad32.exe and check that the User DSN has an EPISDK entry with the datasource set to SDKNoDB.mdb .  The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\ On a 64 bit system run the following command from either the run/search window:  C:\Windows\SysWOW64\odbc32.exe and check that the User DSN has an EPISDK  entry with the datasource set to SDKNoDB.mdb . The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\

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 The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

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 How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Product Line TAC Vista Environment Microsoft Windows OS Vista 4.3 to Vista 4.5 Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using SQL 2000 or enterprise version not administered by TAC Vista: Backup SQL database named "taclogdata." Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL Server and TAC root directory (usually C:\Program Files\TAC and> C:\Program Files\Microsoft SQL Server). When using SQL MSDE administered by TAC Vista: Backup TAC Vista log and event database using backup function in TAC Vista. Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove TAC Vista Config1.x using the uninstall program in Control panel Add/Remove programs. Remove all TAC Vista hotfixes. Remove TAC Vista Server 4.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC ToolPack, TAC XBuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL server desktop engine) using the uninstall program in Control panel Add/Remove programs. Save off a customer's license (.lic) file to another location.  Delete remaining uninstalled TAC folders (usually C:\Program Files\TAC). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server) Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls Remove all keys containing "TAC Shared," e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL server Go to user profiles delete the profile Computername\TACA_Computername (Versions of Vista <5.0) Go to My computer, right click manage, local users and groups, users, and delete user account TACA_Computername and TACM_Computername. Reboot. Reinstall desired version. See How to uninstall and completely remove TAC Vista 5 for steps on removing TAC Vista 5.

Issue Controller and graphic names in Vista Workstation are red, italicized. Product Line TAC Vista Environment Vista Workstation Cause A red, italicized controller or graphic name indicates that this Vista object has been "checked out."  During a partial Vista database export, there is an option for whether or not to indicate the item has been checked out.  This can be used if multiple people are working on a single server from several engineering locations to prevent overlap. Resolution To restore the database: Import the original export .zip file. If you do not have this file, you can also right click on what you want to return to normal and select "Undo Check Out."

Issue   The requested information is not available from the device. (Subsystem: NS, #28) Product Line TAC Vista Environment LonMaker 3.2 (Turbo) Cause The requested information is not available from an application node. For example, transceiver status, SI/SD data, and the network variable names are not always stored in the node. This error is a known issue with LonMaker 3.2 (Turbo). Resolution Navigate to http://www.echelon.com/support A username and password are required to access the download section, but it is free to register. Download LonMaker Turbo Service Pack 2 Install LonMaker Turbo Service Pack 2.

Issue Plug-in 'TACZBuilderPlugIn.Application' launch failure. Unspecified error Product Line TAC Vista Environment LonMaker 3.X TAC ZBuilder Plug-in Cause An unspecified error in the launching of the TAC ZBuilder Plug-in is either caused by a faulty installation or registration of the plug-in. Resolution Check under Start > Settings > Control Panel > Add or Remove Programs. Look for TAC ToolPack 5.X.X. Make sure the version number 5.X.X matches the current Vista installation. If it does not, uninstall the current version of the ToolPack and install the correct version. If it is the correct version, proceed. Check the plug-in registration. In LonMaker go to LonMaker > Network Properties > Plug-in Registration. Look for TAC Vista System Plug-In (Version 5.X.X) Make sure the version number 5.X.X matches the current Vista installation. If it does not, unregister the current version of the Plug-in and register the correct version. If everything appears to be installed and registered correctly, but the error persists, uninstall and reinstall the correct ToolPack. Reboot the PC, reregister the plug-in, and try to launch it again.

Issue Original company sold to new company Site License needs to be updated for install/upgrade.  Computer failure and no software/license information is available. Downloaded software and during install it requests a CD Key Product Line Andover Continuum, TAC INET Environment Site Licensing for install/upgrade Cause Changes in company or computer replacement/upgrade or downloaded software and it is requesting a CD Key Resolution I/NET: 1. Original company sold to new company and Site License needs to be updated for install/upgrade: for company naming changes, contact your sales representative who in turn will contact Product Support and request a transfer of information or upgrade/purchase. Once the information has been cross referenced for validity, either a new or replacement CD Key can be generated. Please include the following when requesting transfer: User Name Site Name Site Address Serial Number Version number Build number CD Key 2. Computer failure and no software/license information is available: Send email to Product Support with the following information: User Name Site Name Site Address Serial Number version number Build number CD Key 3. CD Key for licenses on purchase of software can be ordered by contacting Contact Customer Care. Link is available on the Contact tab of this web page. Customer Care offers pricing, order placement, changes, expedites, and order status. Check Licensing of I/NET with SITE and SEAT License with License Key for issues with CD Key and Licensing information. Continuum: since Continuum only has physical security key licensing, the license is owned by the holder of the key. If you hold the key, you own the license. There is no need to contact PSS for moves, changes, restructuring. If the security key's are lost or stolen, you will need to purchase new keys to replace them. Continuum Software Licensing is available with Release 2.0. 

Issue How to find a dongle ID (PSU ID) if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista IV TAC Dongle Utility Cause The dongle ID (PSU ID) can be found printed on the side of a Vista IV licensing dongle. However, on older dongles, this number can rub off. It is still possible to extract the dongle ID using the TAC Dongle Utility. Resolution Download the TAC Dongle Utility Install TAC Dongle Utility and run the program. Start > Programs > T A C > TAC Tools > TAC DongleUtil Plug in a valid Vista IV end user dongle. Hit Refresh on the Dongle Utility PSU ID is displayed. This is the ID required to add new licensing to an existing dongle. ReadFind a Vista 5 dongle ID for how to find a Vista 5 dongle ID.

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.

Issue LonWorks point count recommendation for the Xenta 5/7/9xx series controllers What is the device limitation on the FT-10 LonWorks channel installed on a Xenta Server Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause The load point table can be found in Vista version Release Notes on The Exchange Download Center. When Xenta 700 was released the Product Announcement had a table with the recommended number of LonWorks devices attached to Xenta 5/7/9xx. Below you can see a small revision of the recommendations. The list applies to devices which the applications in the Xenta 5/7/9xx are interchanging data with. Other devices that are completely handled by TAC Vista through the LTA port of Xenta 5/7/9xx are not included in this calculation. These devices will influence the LonWorks network performance in a similar way as if they were connected through a Xenta 911 and have to be considered. Not following the design recommendations and adding too many LonWorks devices to a single channel will cause poor Xenta Server performance. Resolution Each device uses "load points" according to the table. As a general guideline the total "load points" on the network shall stay under 100 to get a reasonable performance. In reality the e.g. intensity of the traffic also has an influence as well as, of course, the expectations on response time. Type of device Load points I/O module 5 Xenta group master 280/300/401      20 Additional Xenta 280/300/401      in the group 2 Standard LonWorks device, including Xenta 100, polled 2 Standard LonWorks device, including Xenta 100, bound 0.75 Refer to The Exchange Download Center for future releases of Vista / Xenta Release Notes containing software and updated load calculations This information is usually found in the Appendix B - Engineer Information, and look for section titled LonWorks recommendation for the Xenta 500 and 700 series

Issue Connecting to a Morpho Sigma Reader and getting an error using V-Sation from Schneider Electric Environment Continuum V 1.94 and above Morpho Sigma Reader BioBridge Cause V-Sation is not compatible with the Morpho Sigma Series Readers at this time. The Continuum Integration was done by  SafranMorpho and not by Schneider Electric using their Software called BioBridge and Secure Admin for configuration when in Legacy Mode. Resolution This application is not supported by Schneder Electric and all questions should be directed to SafranMorpho Tech Support.

Issue Problem with downloading bin file with more than one door defined causes second set of doors to deny reads. Bin files connected to this issue are 3.24, 3.25, 3.26 Environment TAC I/Net Seven using Access Control. SCU 1284 configured with two doors. (Dip Switch 6 ON gives double address)  Cause Bin file failure to download with double address setting. Resolution On an SCU, an SCU is configured for 4 doors. 2 of those doors are working. 2 of the doors on the SCU are not working. Only thing that has changed is the SCU was downloaded with a new bin file. Nothing in door configuration was changed, no dip switches were altered. Solution: Find out which doors were not working, (probably the second two doors like 0104) Go to Edit/controller/MCU Configuration and Set those doors to Internal, and then download the SCU with the bin file again. Go to Edit/controller/MCU Configuration and Set the doors back to DPU. 

Issue All values in the Xenta 102-AX Plug-in are blank. Product Line TAC Vista Environment Xenta 102-AX Plug-In LonMaker Cause If the Resource File Languages have become corrupted on your PC, then the plug-in will not know how to display the required data. Go to LonMaker > Network Properties > Resource File Languages.   If the only Language listed is "ENU," then the language files are corrupted. ENU is the default language and will display all data in the LNS environment -- plug-ins, browser, get values -- in an enumerated format that is not usable. Everything will continue to work, but monitoring data in the LNS environment and configuring ASCs via plug-ins will be impossible. Resolution Restore the Resource File Languages: Shut down LonMaker Go to http://www.lonmark.org/technical_resources/resource_files/ Download LonMarkResourceFiles1300.exe Run the executable Restart LonMaker Check Network Properties again. US English should be listed and the plug-in should populate with data. Note: There may be Beta versions 13.04 and 13.10 on this website. Do not use these LonMark resource files. The newer versions cause errors in the 102-AX plug-in. For more information see Opening the Xenta 102-AX plug-in results in "request for LonMark Object status" error .

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue   An error occurred while setting the system language property. Please validate that your language resource files are valid. Invalid format. (Subsystem: LNS, #40) Product Line TAC Vista Environment LonMaker Cause Resource File Languages have become corrupt. Resolution Restore the Resource File Languages:  Shut down LonMaker. Go to http://www.lonmark.org/technical_resources/resource_files/ At the time of this article, the latest version is LonMarkResourceFiles1304.exe.  Download this file.  If a later version exists, download the latest file. Run the executable. Restart LonMaker.

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 Import Vista Alarms and Events into an Excel file Product Line TAC Vista Environment Vista 5 SQL 2005 Cause Unable to import Vista Alarms and Events in to excel file from Vista Resolution Select Data > Import External Data > Import Data as shown in below screen capture.   Select New SQL server connection as shown in below screen capture.   Enter Vista SQL Server instance name as shown in below screen capture.   Select taclogdata from dropdown menu as shown in the below screen capture.   Select Event table as shown in the below screen capture.   Rename .odc as .dsn as shown in below screen captures.   Click finish button.   Select Edit Query as shown in below screen capture.   Select SQL as shown in below screen capture.   Paste the Query as shown in below screen capture. Click OK button to apply the query.   Click OK button as shown in below screen.   Click OK button as shown in below screen.   Events are imported in to Excel   Query for Events based on dates: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN '10/12/2009' AND '10/12/2009 23:59:59.997') Query for One Day Events: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE()) Query for Alarm based on dates: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (Event.EventDatetime BETWEEN '08/24/2010' AND '08/25/2010 23:59:59.997') Query for One Day Alarm: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE())

Issue When only the MSDE version of I/NET Seven is installed there is no way to automatically backup the entire SQL Database at scheduled intervals. Product Line TAC INET Environment TAC I/NET Seven running on Windows XP using Microsoft MSDE SQL Server. Cause When only the MSDE version of I/NET Seven is installed there is no way to automatically backup the entire SQL Database at scheduled intervals. Resolution A batch file BackupInetDb.bat has been developed to allow users to create a Scheduled Task within Windows which launches the batch file with the appropriate command line switches. Click here to download the zip file which contains the BackupInetDb.bat and instructions on how to configure an automated backup.