Building Automation Knowledge Base

Issue How many histories can be created in a station and how many records are allowed per history? Environment I/A Series G3 ENC, ENS or SoftJace CComTrolCCWEBor CES Cause Technical product information update. Resolution Regardless of platform type, histories are stored under the station's file system (file:^history/). Stations running on a PC-based system (Enterprise Server or SoftJACE) store the histories in subdirectories using segmented files; this provides improved search capabilities over a flat file system. Stations running on a QNX-based system (ENC) store all of the stations histories in a single compressed file (history.zip). A running station opens the history.zip file in the ENC's ram disk space, the histories are compressed and saved to flash whenever the station is saved. Opening the history.zip file to the ram disk eliminates the need to write to the flash drive each time a record is added to the history file.   When the station needs to write a record to a history, it opens the specific history into the running station (either from the file system if PC-based, or from the ram disk if QNX-based). The open history does contribute to the heap.used of the station. The history service has one property 'max open time' (default 5 minutes) which causes the station to close the history from the running station heap if no records have been written to the history for a time period exceeding the 'max open time'.   Each history extension which is added to the station does add slightly to the station resources because the extension is represented in the bog file. When the history is first enabled, the station creates the history file. The initial file includes a 1600 byte header (defines the configuration parameters) and a single page file of 4096 byte size. When triggered by either the collection interval or COV/COS, a record is added to the page file. When the page file becomes full, additional page files are created based on the capacity configuration of the history. History Record Size by Point Type Point Type bytes/record boolean 13 enum 16 single precision numeric 16 double precision numeric 20 string variable length * *NOTE: A single 'string' record cannot exceed one page (4096 bytes)   Since histories count as file descriptors, there is a physical limitation on the number of histories allowed in a QNX-based ENC station. It is recommended not to exceed 800 histories, given the file descriptor limit of 1000. Note: The platform services view of the QNX-based JACE station includes a property to modify the size of the ram disk within defined limitations. Note that the alarm database is also maintained in the same ram disk space. Exercise caution when modifying the default ram disk size; note that allocating additional memory to the ram disk will limit the memory available for other functions by the QNX OS. Reducing the ram disk size too much could result in history or alarm records not being stored properly and erratic station behavior.

Issue If steps used in creating a LNS network are performed in an incorrect order, you can get many errors which can be easily avoided. While this should not replace the Engineering LNS Networks manual  it can be used as a quick reference. Follow this link to access the complete Manual Environment LonMaker 3.X Vista System Plug-in Cause There are several steps to perform in order to create and update an LNS Network using LonMaker. Resolution LonMaker Cheat Sheet Create new LNS Network in LonMaker Set path to Vista DB in Server Setup Start TAC Server Open TAC System Plug-In Drag and drop Devices from Stencils Assign .MTA to Xenta Devices You will be prompted to Resynchronize, say no. Assign I/O Modules Set Neuron IDs Update Vista DB Create Group Bindings Resynchronize drawing (fix up) Download Application and Parameters Commission Base Units and Modules Commence Communication

Issue How to uninstall Privilege software Product Line TAC Vista Environment Vista IV Licensing prior to 4.25 Aladdin Privilege Administrator 2.01 Cause Need to completely remove a Vista IV installation including all traces of Aladdin Privilege Administrator. Resolution Version 2.01 is mentioned in the description below, but process is similar with other Privilege software versions. Also, process may look slightly different in different Windows versions. To remove: Run the uninstaller for Privilege 2.01 Go to the Windows Control Panel and if there is still an entry for Privilege Licenser - if there is - remove it Delete the Privilege directory (default location: C:\Program Files\Aladdin). Go to the system32 folder and delete the directories PLog and PData. From the same folder, delete the files: PLInst.exe, PLockDiag.exe, PLServ.exe, PLAdmin.dll, PLCLNT.DLL, PLEsd.dll, PLInstall.dll, PLLG.dll. Run Regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Aladdin Knowledge Systems and delete Privilege Licenser. Go to HKEY_CURRENT_USER\Software\Aladdin Knowledge Systems and delete Privilege Licenser. Reboot and reinstall.

Issue During installation of Privilege software, the following message appears: "Critical file not copied!: c:Windows\Temp\~~IEWS~0\PLApiLangEng.dll" Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Error during installation of licensing software. Resolution Delete the “PLApiLangEng.dll” file that is located on your PC. (It will be reinstalled during the installation process below) Uninstall Privilege and TAC Software from the PC Reinstall Privilege and TAC Software.

Issue "License software is damaged. Contact product support." error when installing Privilege Administrator license file. Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause The file has been compromised during transfer. The file was generated with errors. Resolution The license file or its digital signature has been damaged.   Contact Product Support. Ask to resend your .plf it in a zipped format for better protection. Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue Error message from I/Net Seven controller such as a 7790 in AMT which is "Memory Queue Overflow" or "Memory Overflow." Environment TAC I/NET Seven either direct connect to controller (such as a 7790) or Ethernet connection to a NPR (such as a Xenta 527) Cause Memory overload or bottle neck caused by excessive number of messages through the network. Resolution Memory Queue Overflow or Memory Overflow messages seen in the AMT (Alarms Messages Transactions) window is often caused by an excessive number of messages being requested to transfer through the network device. When you look in AMT you should check to see if the message comes from the Controller (such as a 7790) or from the NPR (such as a Xenta 527).    Throttling back the number of messages by reducing trending data, alarms, transactions, samples, or other information flow will reduce they data and free up some bandwidth.  How many controllers are connected to the NPR? Perhaps you can break this number into smaller allotments and reduce the traffic on the C-LAN which reduces the bandwidth required through the NPR. 

Issue Get message "Could not open or create file.: AC_Xenta_721.cfg" in the Xenta Server error log and in TAC vista event log. The message appears about every 10 seconds. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731 Cause This is a defect in the software. Resolution This happens if you use the internal online signal e.g. as the input for an alarm. Take out the references to the internal online signal

Issue In LonMaker, an incorrect number of targets were selected when creating a connection resulting in NS Connections #1 lcaErrConninvalidTargetcount error. Environment LonMaker Vista Cause In LonMaker, an incorrect number of targets were selected when creating a connection. Resolution You must specify at lease one and no more than 25 targets when adding members. To add more members, you must invoke the Connect method multiple times.

Issue Description of how the Bacnet TimeSync works Environment Windows OS XP-Vista versions Cause Description of how the Bacnet TimeSync works Resolution The Bacnet TimeSync that is available on the Time tab in a device editor will only send out a Bacnet UTC TimeSync message to the Bacnet IP controllers that are in the list. This is not a automatic function, but is available to use when integrating 3rd party controllers into our system.

Issue How to add another TAC Vista server node into an existing server in TAC Workstation. Product Line TAC Vista Environment Vista Workstation Cause Multi-sever Vista system is the system which has more than one Vista Server in the network. One Vista Server will be assigned as the master and the rest will be assigned as slaves. The order of setting multi-sever system is very important in order to make the system work properly. Common mistakes are: Vista servers have different versions. Adding slave computers before adding the master computer. Using same names of Vista servers. Using dynamic IP address. Vista Server object names are the same. All folders and objects found at the root level of the servers must be changed to unique names before merging the databases. Resolution Before doing that, please back up all TAV Vista databases on all computers. All computers should run the same version of TAC Vista. Also make sure all your IP networks are functioning. In addition, all Vista Servers need to be the same version. (eg. Vista 5.1.3 server will not be able to communicate Vista 5.1.4 server when they are noded together.) All computers’ TAC Vista Servers need to have different names. The server name can be checked by opening your TAC Vista Server. By default, Server name is the computer name. If the sever name needs to be changed, please following the steps listed below: Go to TAC Vista Server Setup Go to Vista Database tab Under “Rename Vista Server to” text field, type the new name Click ok and start the Vista Server to make sure the name has been changed Choose one computer to be the Master and the rest of the computers will be Slaves. Start by shutting down all instances of TAC Vista Sever and TAC Vista Workstations. Add Slave Servers into the Master Server. Start the Master TAC Vista Sever, and then start its TAC Vista Workstation. Right click on the Vista Server object. Select New>Object>Node. Type $LAN.SlaveServerName. If the Slave Server name is different from its computer name, change the IP/DNS address in the property window. (Note: this step requires a static IP address) Right click on the Slave Server Node and select Properties. Type in the IP address in the IP address/DNS name field. Repeat steps a-e for any additional Slave Servers. Leave the Master Server on, and start the Slave Server. Follow steps 4 a-e for adding Master Server into Slave Server but use the Master Server’s server name and IP address this time. Then, right click on the TAC Server object in Slave Server computer, select Properties. Under the General tab, change the Network Master to the Master Server name. Then click OK. If you have multiple Slave Servers, add the Master Server into each of them. Shut down all instances of TAC Vista Workstation and TAC Vista Server. Restart the Master Server’s TAC Vista Server and its TAC Workstation first. Then start the Slave Servers’ TAC Vista Server and their TAC Workstation. You should be able to view the Slave Servers under Master Server. Note: Master Server can view all Slave Servers’ projects, and each Slave Server can view Master Server’s project. However, each Slave Server cannot see other Slave Servers unless you node Slave Servers to each other. Any change made in Slave Server’s TAC Workstation will be reflected in the Master Server’s TAC Workstation. Vice versa also works.

Issue Upgrading a Xenta 102-AX controller to a higher software version (eg. V2.16) Upgrading a Xenta Sever version (eg. V5.1.4) Error message says: System image is not compatible Environment Xenta 102-AX HW version below 2.0 Xenta Server HW version below 2.0 Xenta 511, 527, 701, 711, 721, 731, 913 HW version below 2.0 Cause This issue is due to Xenta 102-AX and Xenta Server earlier hardware versions. Resolution Check the hardware version of the controller. The hardware version is printed on the sticker with HW X.X on the controller. If the HW label is missing, that means this Xenta 102-AX or Xenta Server is hardware version 1.0.   Unfortunately, hardware version cannot be upgraded. If this error message appears, it means the controller cannot be upgraded to a more recent firmware version.

Issue Xenta 121-FC SNVTs show up in LonMaker or NL220 but are missing in Vista Environment Xenta 121-FC LonMaker/NL220 Vista Workstation 4.5 System Plug-in Cause A problem has occurred with the import of the controller into the Vista database. Resolution In the Vista System Plug in, delete the controller from the TAC Network.  In the LNS network tab, right click on the controller and disable it from being updated in the TAC Network. Update the TAC Vista Database Refresh the Folder View in Vista Workstation.  Verify that the controller has been removed from Vista. In the Vista System Plug in, re-enable the controller to be updated in the TAC Network Move it back into its former location in the TAC Network Update the Vista Database a second time. Go to Vista Workstation, verify that the controller has returned and values are being properly displayed.

Issue How to change the path of the points bound to for all bindings of a TMGL or OGC graphic simultaneously using the Change References command. Environment Vista Workstation TGML Graphic Cause There are many reasons why binding paths would need to be updated.  The network structure could have changed/been renamed.  Or it may be that a graphic has been copied, pasted, and renamed (say AHU1 to AHU2) and now all the points need to be redirected to another unit. Resolution Right-click on a graphic or a folder of graphics in the Folders pane of Vista Workstation, choose "Change References..." In the Change References window, hit the "Search" button.  This will populate all bindings and links in the graphics folder. There is no way to list just the bindings of a single graphic. The full folder is always displayed. Highlight the graphics points that need to be updated -- it is usually best to click on the "Name" header to sort the bindings by graphics pages. Then just one graphic page's links can be highlighted to edit. Hit the "Replace" button. Enter the "Search for:" and "Replace with:" strings.  It is often a good idea to include as many common characters as possible to prevent accidentally destroying bindings. Example:  Instead of search for "AHU1" and replace with "AHU2", search for "-LNS-AHU1-" and replace with "-LNS-AHU2-" If the desired string was found, the "New" column will now be populated with the new path.  Review the newly formed path to ensure no mistakes were made. When verified, commit the changes to the database by pressing the "Save" button at the bottom of the window.  References have been changed in the database.

Issue When attempting to run the WorkPlace Tech Tool, Application Menu missing or grayed out. All WorkPlace Tech Tool related entries in the Tools menu are grayed out or missing.   Project Toolbars are not displayed. "Unknown error occurred in an add-on to WorkPlace Tech" Environment WorkPlace Tech Tool 5.7.4 and later versions Microsoft  Visio 2003 or Visio 2007 Microsoft Windows XPsp2, XPsp3,  Vista or Windows 7 Cause Various causes beyond the scope of this article. Resolution There are several different reasons why these entries are grayed out or missing and therefore not selectable. The exact procedure for correcting the problem depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for each third-party add-in. Click [OK] to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WPT, all menu items should be there. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Verify that the box for "Enable COM add-ins" is checked. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click [OK] to apply. Open the Tools menu and select Macros then select "COM Add-ins" Uncheck all third-party add-ins shown in the list. Click [OK] to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there.

Issue Why do you need to mask the events in both door editor and the point itself (08, 09)? Environment I/NET Seven Cause Door masking is required in both the door editor and the point itself. Resolution Think about door masking as layers. When you create a door, you need to create a point/relay for the door. This relay changes state (0,1), this is the hardware layer, Layer one. In order for AMT to get a event that the point have changed state it needs to ask the controller of the status. This is done by a quick poll command issued by the SLI. In order to make this point to behave like a door we need to add some feature to it, a second layer. This layer is not hardware dependent but it speaks to the hardware. Here you can add some additional event or in this case alarm as "forced door". This alarm will be distributed to the event handler of the point so next quick pull will catch this information and it will be sent to AMT. So in order to get alarms and transaction from the door specific attributes both the point/relay (So the quick pull can get its information) and the second layer door needs to be masked. So the information will become correct its also important that the points and door masking priority are the same.  

Issue In-house Vista dongle is broken. Environment Vista 4 Vista 5 Dongle Cause Physical Damage has broken the dongle. Resolution Return the broken dongle to your local orders dept, using the Warranty Claim System, WCS, and get a replacement dongle (component part no 362140040 for Vista 5). Orders Dept should also be able to provide you with information about any eventual cost for this procedure. Part number for a Vista 4 inhouse - 000880460 (no longer available) Part number for a Vista 5 inhouse - 000885000

Issue A list of all the default ports used by a typical Vista system. Product Line TAC Vista Environment Vista 5 TCP/IP Ports Cause Below is a list of some components and protocols associated with Vista 5 and their default port assignments. Resolution TAC Vista 5 Component/Protocol Default Customizable Comment TAC Vista Server and Workstation       TCPPORT 45612 No Vista Server to Vista Server DCOM 135 + dynamic No Remote Workstation LMGRD 27000-27009 Yes License Server TACLIC Dynamic Yes License Server. Will find an available port         TAC Vista Remote Workstation       DCOM 135 + dynamic No Remote Workstation LMGRD 27000-29000 Yes License Server TACLIC Dynamic Yes License Server. Will find an available port.         TAC Vista Webstation Client       HTTP 80 Yes Web Browsing HTTPS 443 Yes Web Browsing         TAC Xenta 5/7/9xx       DHCP Server 67 No Dynamic IP address DHCP Client 68 No Dynamic IP address DNS 53 No Name resolution HTTP 80 Yes Web Browsing HTTPS 443 Yes Web Browsing, Log-in FTP 20/21 No File transfer. FTP Server SMTP 25 No E-Mail SNMP 161 No Network management SNMP Traps 162 No Network management LTA IP 1068 Yes LonWorks Communication over IP. LTA for TAC Vista Variable transfer IP Network 1233 No Peer-to-peer communication between TAC Xenta Servers Variable transfer HTTP 80 Yes Read/write values from Web Browser UDP 9088, 9089 no Xenta Server to Xenta Server data point TX via UDP (>5.15)

Issue Unbound signals in Webstation appear as offline. Environment TAC Vista Webstation 5.1.4 and prior Cause In Vista Workstation, unbound signals are ignored; but in Webstation, and unbound signal is treated as offline.  This may result in a red X across the entire component if any binding is unbound.  This is an inconsistency across the two platforms. Resolution Make sure all signals are bound.  Even if it's a binding that is not used for any display purpose (like a multi-bind .[OBJECT] binding for example). Any signals that are unbound and unnecessary should be removed from components.

Issue After changing password of a user in webstation it is not possible to log in with the new password. This happens on machines were the TAC Vista server in installed, without language pack, on a server that have different regional settings than the operating system language. Environment Windows with regional settings set to another than the OS language. TAC Vista installed without language pack Cause There is a mismatch between localization settings for Tacos server, Webstation and the regional settings on the Windows system. Resolution Make sure you are using the same language pack for Vista as the regional settings on the host are set. If you are using a webserver and change the password via a webstation you can also workaround this issue by changing the language code in the “C:\Inetpub\wwwroot\TACVistaWeb514\web.config”. Look for the entry   The example above uses English settings. Change this to desired localized setting. For instance the culture code for Poland is pl-PL (language-country) and sv-SE for Sweden. Note: It is always recommended to use the correct language pack before changing the localization code by hand in the config file. Having a mismatch between the installed language pack (or manually changed culture code) and regional settings might cause problems with incorrect formats (e.g., for dates, times, decimal character, character sets, etc.).

Issue LDVD: Socket receive error (Error#:53526) in a Xenta 5/7/9xx Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause This error is displayed every time the LON communication is closed down. Resolution This message does not necessarily mean that something is wrong. Check LON communication to make sure there are no other symptoms. This is very minor and common unless it occurs at a high frequency.