Building Automation Knowledge Base

Issue Unable to log in to Vista workstation. Get error message "Failed to init session: Class not registered". Environment Vista 4.XX Cause This normally occurs after having downgraded Vista. The problem is that a number of files are stored in the C:\Program Files\Common Files\TAC Shared folder and a version compatibility problem occurs.  Resolution Uninstall Vista Locate the C:\Program Files\Common Files\TAC Shared folder Delete all the files in this folder Re-install Vista.

Issue The values for programmable Xenta controllers display "Failed to Read Signal" in Vista Workstation. Environment Menta Vista Workstation Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta Server 701, 711, 721, 731 Cause When Menta programming blocks that are specific to the 700 based menta are copied and pasted into regular menta, it will fail to complete a direct connect download. An error will pop up the reads "PARSER_CODE_ERROR". An example would be the RO output, that is a  700 based Menta programming block, being used in place of an AO output block in regular Menta. When performing a normal download through the system plug-in or workstation, the Menta will appear to download successfully. It is this situation that the value column will read  "Failed to Read Signal" for all points. Resolution The correct programming blocks must be used in its corresponding type of Menta. It is a wise practice to not copy and paste 700 based Menta programming into any other programmable Xenta controller. This will avoid accidentally adding a point that is not compatible.

Issue TGML Links or bindings disappear when upgrading to Vista 5.1.7 Environment Vista 5.1.6 or older that is upgraded to Vista 5.1.7 Cause Incorrect configuration of TGML graphic. The TGML editor and engine has been upgraded in Vista 5.1.7 and more checks are in place to detect user errors. There are now checks for both bindings and links without a name. Resolution Ensure that all links and bindings have a name. If a graphic is edited in Vista 5.1.7 a prompt will appear when saving the graphic if a link or binding doesn't have a name.  

Issue Connections between Menta function blocks not been allowed Environment Menta Cause If the rectangle (Dotted line) covers the pixel of the connection point of any function block / output, this stops the mouse from selecting the input connector to allow the connection to be made. This also occurs if you use any of the Comment, Line or Rectangle Menta features and overlay these too closely to the connection point. Resolution Select the rectangle (dotted line), (or overlaying object) and move it away from the connection point as shown below.

Issue Is it possible to pre-define Workstation log-in settings for each user that  logs on to windows on the PC? This would enable each user to be directed to the correct Vista server without any user input. Environment Tac Vista 5.1.X workstation. Cause On some sites it's desirable to restrict access to certain Vista servers. It can also be desirable to pre-configure the server details so the customer does not need to remember it. Resolution The short answer is that it's not possible to pre-define these settings. However it is possible to change the registry HKEY_CURRENT_USER\Software\TAC\TAC Vista Workstation\5.1.7\ODLoginMgr\Settings\CLoginDlg for each user (this requires that the user or IT dept log in with this user account). Access can then be restricted in Vista so that certain user can only access certain servers. Edit the registry 1. Open the startmenu and click on Run... 2. Type regedit and click on OK 3. Browse to the  HKEY_CURRENT_USER\Software\TAC\TAC Vista Workstation\5.1.X\ODLoginMgr\Settings\CLoginDlg. 4. Set appropriate values for CLOGINDLG:211 (show options - 0 = don't show; 1 = Show); CLOGINDLG:217 (server name); CLOGINDLG:5006 (Windows User or Vista User); CLOGINDLG:5016 (Domain if Windows User selected). 5. Attempt to login in to Workstation and confirm the settings are appropriate.

Issue Is it possible to redirect all offline alarms to a certain alarm control object in Vista? Environment Vista 5.1.7 Cause Using the "Configure alarm" function in the Vista server all offline alarms can be sent to a special alarm control object in Vista. Resolution Start with creating a new Change of state object in Vista To create a Change of State Right-click the Vista server node/object Point to New, point to Object, and then click "Change of State - System". Type the name. In the example, "Offline_Alarms". Right-click the newly created Change of State object. In the example, Offline_Alarms. Click Properties. Type a descriptive text. In the example, "Handles alarms for devices going offline". Change the priority. In the example, change the priority to 1. On the Alarm tab, in the Alarm processing control box, type the name of the alarm control object for priority 1 alarms. In the example, Alr_Cntrl1. Click OK. Filtering and Linking an Alarm We can now filter out system alarms ($EE_Mess messages) tripped by devices going offline. The alarm texts contain the word "Offline" and we use this as the filter. To filter and link an alarm On the Windows task bar, click TAC Vista Server. On the File menu, click Log in and log in. On the Configure menu, click Configure Alarms. Click Add. In the Text match box, type the filter mask. In the example, "*Offline*". In the Event object box, click Browse. In the Units list, browse to the Change of State – System object. In the Objects list, click the Change of State – System object. In the example, Offline_Alarms. Click OK. Minimize Vista Server. When a Xenta device goes offline, a priority 1 alarm appears. The alarm is handled by the Alr_Cntrl1 object

Issue When you open a trend you get the following message Environment Vista 5.x.x Cause The period selected in the trend chart does not exist in the trends associated with that chart. In the sample below the trend only store 1 days worth of information and the chart is requesting last weeks information. This would result in this type of error. Resolution Modify the period selected in the chart so that trend values that are logged will be displayed.

Issue Is it possible to sort the Vista Workstation alarms only by date, not by group in alarm viewer? Environment TAC Vista 5.x.x Workstation alarms Cause When you sort the Vista Workstation alarms in the alarm viewer by date, No matter how you sort them they are arranged by date and type OR by groups (Unacknowledged, Acknowledged and then Acknowledged Reset..etc). See the below picture for example; Resolution No, It is not possible to sort the active alarms just only by the date in Vista Workstation alarm viewer. This will sort by groups.

Issue Generating or importing one XBuilder project into another directly from Vista takes very long time Environment TAC Vista TAC XBuilder Cause In v5.1.7, a new feature was introduced that made it possible to import one XBuilder project into another directly from Vista instead of from a file. TAC XBuilder will by default do a project reference check to determine if the project is included in any other TAC XBuilder projects in the TAC Vista database. If it is included in any other project, the user will be notified in the TAC XBuilder output pane. The reference check will increase the time it takes for TAC XBuilder to generate the project; depending on the amount of TAC Xenta Servers that exist in the TAC Vista database. Resolution It is possible to disable this automatic check in the TAC XBuilder project settings. From the menubar click Project and then select Settings... In the Settings dialog box uncheck the box that says Check project references in TAC Vista database.

Issue The following message appears after approximately 30 seconds when you attempt to edit a Menta file from the system Plug-in. Environment Windows 7 Vista 5.1.5, 5.1.6 and 5.1.7 Cause The login screen does not come to the forefront when required Resolution Use the ALT - Tab key combination to scroll through the open windows. Select the logon screen and continue with the normal process.

Issue When the Xenta 102-AX plug-in is opened the following error is given, “Reply to ‘request for LonMark Object status’ message was not received” Environment LonMaker NL220 102-AX Plug-in Cause There is a bug in the certain beta versions of the LonMark/Echelon DRF-kit. LonMark resource files 13.04 and 13.10 will not work with the Xenta 102-AX plug-in. Resolution The solution for the Xenta 102-AX plug-in error is to install a LonMark resource file version other than 13.04 or 13.10. Shut down LonMaker Go to add and remove programs. Uninstall LonMark Resource Files (13.04 or 13.10). Go to http://www.lonmark.org/technical_resources/resource_files/ Download the latest LonMarkResourceFilesXXXX.exe Run the executable. Restart LonMaker. Verify that the 102-AX plug-in works without errors.

Issue When controlling I/NET DO point in Vista, for example changing the value from "0" to "1", the value of the point won't stay. It changes back to "0". Environment I/NET integrated to Vista (I2V) Cause There are several attributes of an I/NET DO point (shown below in Vista). Usually the "control" attribute is used to manually control the DO point, while "value" is used to monitor the current state of the DO. If the "control" attribute is changed from "0" to "1", the real DO point will be on, but value of this "control" property point will change back to "0". Resolution Use the "control" attribute to manually control the DO point. Use the "value" attribute to monitor the current state of the DO point.

Issue The nviStPointOffset in the Xenta 102-AX controller will not hold a value when it is entered in Vista Workstation or through the browser in LonMaker/NL220. Environment NL220 LonMaker Vista Workstation Xenta 102-AX Plug-in Cause There are two possible reasons for this issue: If there is a SNVT bound to nviStPointOffset, then the value that is manually entered will be pushed out every time the SNVT value is sent across. The Stat Adjustment Range in the Xenta 102-AX plug-in may be set to low causing the value too not hold. Resolution First check in LonMaker/NL220 if there is a SNVT bound to nviStPointOffset. If there is a binding here then it will either need to be broken or the point will not be able to be overridden. If there is no binding then move on to step two. Open up the Xenta 102-AX plug-in and click on the Operating Parameters tab. Check what value is set in the Stat Adjustment Range field. This value needs to be set high enough to accommodate the setpoint offset range that is desired. In order to enter a positive or negative offset of 5°F, then a value of 5 needs to be entered into the Stat Adjustment Range. If the value is set to 5°F and an offset of 6°F is entered, the entered value will revert back to the maximum amount allowed by the range, 5°F. Note: Keep in mind that this setting is also used to set up the range for wall stats that have an adjustment feature. In this case the range is divided by two to give the wall stat the capability to go negative and positive. For example if 5°F were entered into this setting, the wall stat will only be able to adjust up and down 2.5°F unlike nviStPointOffset that will be able to move up and down 5°F.

Issue In Menta simulation mode, when changing the RI block (using the button on the left hand side), the TSCHI will get the same value When changing the TSCHI block, nothing will happen at all  Environment TAC Menta Xenta 701, 711, 721, 731 Cause This happens due to a bug in TAC Menta. Resolution Create the TSCHI block before the RI block (this issue will only occur when the RI block is created first). Please note the this issue only affects simulation mode of Menta, you won't notice it  when the project is downloaded to the device.

Issue Trendlogs with a log period of 24 hours don't work. Environment TAC Vista 5.1.X Vista server trend logs. Cause This is only an issue in countries and states that don't use Daylight Saving Settings! There is an issue with Daylight savings settings in regions that don't have daylight saving. This is a bug that has been fixed in HF51715 (which will be released shortly). Resolution - Option 1: for Vista 5.1.7 - install HF51712 (or upgrade to 5.1.7 and install 51712) - Option 2: For older versions where it's not possible to upgrade: Double-click on the PC's clock in the task bar. Select the tab Time Zone. Change to a time zone that does observe daylight saving. Adjust the clock to the correct local time in you region. Uncheck the Automatically adjust the clock for daylight saving changes check-box. Click OK and close the dialogue. Restart Vista to apply the settings to Vista.

Issue Get "Not enough storage is available to complete this operation", could not connect to Vista message in workstation. The message appears periodically in Workstation without any operator input. Environment Vista 5.1.X Workstation 5.1.X Cause There are at least 2 possible causes for this. 1. Over utilisation of the PC's resources - in other words there is not enough physical memory on the PC. 2. Incorrect DCOM settings. Resolution Check the memory usage in the Task Manager. Is there RAM memory available when Vista is idling (not running reports and retrieving logs)? If the physical memory is used up then the only solution is to increase the memory on the PC/server. Alternatively, if there is memory available, check the DCOM settings for Vista. These can be found in the TAC Vista installation manual

Issue When installing Loytec NIC software the USB driver installation fails. Installing USB Drivers Failed LOYTEC NIC Driver Installer Error Installing USB Drivers: Could not pre-install Drivers Environment Windows Server 2003 setup on a domain. Cause The admin rights of the user is causing driver installation failure Resolution Even though you are logged on as a domain administrator the installation process fails at the USB driver stage. If you run the installation process by right mouse click on the exe file and then select run as. Then select the local administrator account the USB drivers will be installed correctly. Here are the screen captures of this process  

Issue The new scheduled SQL maintenance functions don't appear to defragment the events table, whilst the trendlogvalues table has been defragmented. Environment Vista 5.1.7 SQL 2008 R2 SP1 Cause A Microsoft SQL Server database is prone to data fragmentation and this is also true for the new TAC Vista SQL database layout introduced. It is recommended to keep the SQL database index fragmentation level at a low level to ensure performance in the TAC Vista system. A new feature has been added to TAC Vista Server to schedule regular maintenance tasks on the TAC Vista SQL database to prevent the index fragmentation level to obstruct performance deterioration; this feature is called SQL Maintenance. The SQL Maintenance feature is supported for both the new and the previous database layouts and is found in the TAC Vista Server Setup tool. TAC Vista Server Setup will also display the database layout used by TAC Vista. An event will be created in the TAC Vista Workstation event log when the maintenance task starts and ends. This event is created by TAC DSS Writer Service which launches the maintenance task. If a slave node is down in a TAC Vista network these events will not be captured by the Master node. Resolution TAC Vista SQL Maintenance feature will only execute if the total amount of data pages exceeds 1000 for the database. Maintenance should not be run when there is a low amount of data pages in a table. The total amount of data pages for a table is found in the index properties which can be seen using Management Studio. Open SQL management studio and connect to the tacvista database instance. Locate the taclogdata (default) database and expand the database in the tree. Under tables\event\Indexes locate PK_Events(clustered) and right-click on it. In the Index properties dialogue, under Select a page, select Fragmentation. The pages property can be seen in this page. Repeat the process for tables\trendlogvalue\Indexes\PK_Trendlogvalue(Clustered).

Issue Is it possible to specify a TCP port for the communication between Vista and the SQL server? Environment Vista 5.1.7 SQL server 2008 Cause  The default SQL Server port is 1433, and client ports are assigned a random value between 1024 and 5000.   Resolution It is possible to specify which port that should be used by the SQL server. Start the SQL Configuration Manager Expand SQL Server Network Configuration Click on Protocols "Instancename" Click on TCP/IP and open the tab IP addresses Go to the bottom fields "IP All" take away everything in the field  "TCP Dynamic port" Specify a port which SQL should use in "TCP Port" Now open the Vista server setup To specify which port Vista should use when communicating with the SQL server add a comma after the name of the SQL server and then enter the port number, in this case 27035 which also was specified in the SQL server. 

Issue When trying to download application and parameters in the TAC Vista System Plug-In, the message in the Output pane says 0 device(s) selected for download. The download window in the system plug-in does not open. Environment Vista NL220 LonMaker System Plug-in Cause When the system plug-in displays zero devices selected for download, it is seeing the Xenta controller as a LonWorks device. There are a couple of possible causes for this issue. The neuron ID set for this device may be wrong. The correct device template was not browsed in when the node was created in NL220/LonMaker. Resolution First check the neuron ID of the controller and verify that it is correct. If it is correct, follow these steps. In the System Plug-in, on the TAC Network side, select the Xenta controller that is not being recognized and delete it. Take note of which group the controller belonged too. Update the TAC network.  The previously deleted controller will be added back into a newly created group. Move the controller out of this new group to the correct, desired group. Delete the empty group and update Vista database. Now select the controller and download application and parameters.