Building Automation Knowledge Base

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 TAC Vista SQL transaction log file is very large and won't shrink. Product Line TAC Vista Environment Vista 5.1.X SQL server 2005, 2008 Cause An SQL transaction log consists of a number of virtual files whose size is defined in the database's properties. Once the virtual file is full, the next virtual file in sequence is used. These files are an essential part of the 'rollback' functionality, allowing SQL to roll back a transaction if for some reason (i.e. disk space runs out)  it can't be completed. With the simple model, the virtual file will be marked as reusable once the transaction(s) contained within the file is complete. So a database may look like this, with the '2' in the status column indicating that the virtual file is still in use: With the recovery model set to a simple, a shrink operation will remove all the virtual files that aren't in use. With the full or bulk-logged recovery model shrink operations behave differently. A full description of this can be found here, but the most important point is that a backup of the transaction log must be made before any virtual files can be marked as reusable.  A shrink operation may not remove all virtual files straight away either so multiple shrinks may be necessary to remove all unused/expired  Resolution Run the following queries: DBCC loginfo This will show the file structure of the SQL log file. BACKUP LOG taclogdata TO DISK = 'c:\taclogdata.bak' Run DBCC loginfo again. Check to see if there is any change. Run a 'Shrink' command (via SQL Management Studio) and then run DBCCloginfo again. Check the size of the database: sp_helpdb taclogdata Keep repeating the process until the database logfile is as small as it can be.

Issue A new feature is introduced in TAC Vista Workstation 5.1.7, enabling the user to identify broken and empty TGML bindings and TGML Links in TAC Vista Workstation. This feature can also list all bindings and links in TAC Vista Workstation, replacing the search function previously used to identify bindings and links in TAC Vista Workstation. Product Line TAC Vista Environment Vista 5.1.7 and above Cause Compiling a list of all bindings, or all empty or broken bindings, allows a user to quickly find and update any graphical problems cross an entire database at once. Resolution From Workstation, right click on a folder and choose "Find broken bindings." This replaces the previous method of searching for broken bindings within the Search window. Note the following object types are no longer available in the TAC Vista Workstation search function: TGML Bindings TGML Dynamics TGML Link TGML Links See TAC Vista Technical Manual Chapter 28.2 for additional information about this feature.

Issue When TAC Xenta 421-A is used as stand alone LonWorks node, a value read from an 0-10 VDC or 4-20 mA is sent only as 0-100%. Is it possible to send as engineering values? Product Line EcoStruxure Building Operation,TAC Vista Environment TAC Xenta 421-A Cause Then the TAC Xenta 421-A is used as a stand alone LonWorks nodes, the values from an analog input is always sent as nvoAnalog1-4, in 0-100%. Only exception is then using thermistor inputs, when the measured temperature is sent out as nvoTemp1-4. Resolution TAC Xenta 421-A used as stand alone LonWorks node, the values from an analog input is always sent as nvoAnalog1-4, in 0-100%, unless the input is configured from 1.8 kOhm or 10 kOhm thermistors..

Issue NL220 Data base will not open and an error, "Database cannot be accessed you may be in single user mode NS #22" is produced. Product Line TAC Vista Environment LNS LonMaker Vista NL220  Cause Administration rights are not granted to the Microsoft server computer user preventing the database from opening. Resolution To work around admin access from IT: Close NL220 Right-click Relaunch using "Run as Administrator"

Issue How many Vista logs can Vista 5.1.9 handle? Product Line TAC Vista Environment Vista Server 5.1.9 Cause There are no official limitations or documents on how many trend logs you can add to a Vista server. The following items listed in the resolution will assist in determining the performance of the Vista Server Resolution The following items listed are the restrictions that limit the performance of the Vista Server: The DSS writer can handle around 40 logs per second. Vista server trends are often limited by how many values per second the Lon network interface can handle. (Typically 40 for a Loytec port and 10-15 for 911 or LNS port in Vista). Size of the SQL database, 100GB for Vista trend logs is a very large SQL database. Vista can handle this provided the computer hardware is of a high-performance nature, and the SQL database and computer hard disk must have regular maintenance performed.

Issue Where to find the documents for KNX System Integration with TAC Vista Product Line TAC Vista Environment KNX Protocol (LON) TAC Vista 5.x.x Cause When KNX Lighting system (LON) want to Integrate with TAC Vista system, It requires a Gateway to connect from KNX Protocols to TAC Vista. Resolution Download the KNX documents from the below link: Product Announcement - Field Devices Europe New 3rd Party Gateway between LON and KNX Learn more about LON-KNX Gateway

Issue A Xenta 102-AX accepts a 0-5V input on all external inputs. If Universal Input 3 is designated as CO 2 , the range of the input needs to match the range of the sensor. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Universal Input 3 CO 2 sensor Cause The default setting (a gain of 1/1) results in 0V = 0ppm 5V = 1023ppm (1023 is a resolution of the onboard analog to digital converter.) Resolution Refer to page 3-66 of the TAC Xenta 102-AX Software & Hardware Manual for more detail. Calculate the required gain for the range of the CO 2 sensor. Ensure the sensor outputs a 0-5V signal. Note the CO 2 level at 5V. In this example, 2000ppm. Divide the maximum CO 2 reading by the analog to digital converter bit resolution (1023). Multiply the result by 1000. (2000 / 1023) * 1000 = 1955 Locate the value for Universal Input 3 SCPTgain. There are four locations to alter this value: Xenta 102-AX Plug-in Go to the Browser Tab > Xenta102AX > UnivIn3 Sense > SCPTgain > multiplier. Over on the right, enter in 1955/1000 and hit Set Value. LonMaker or LNS browser Open the browser window by right clicking on the 102-AX in the drawing and selecting Browser. Look in the Functional Block column for UnivIn3Sense. In that category is a point called SCPTgain. Click on it and then enter up top 1955/1000. Hit the red down arrow to download the value to the device. Enable monitoring on the nvoCO2sensor value or reopen the browser to view the new CO 2 value. Vista Workstation Go to the 102-AX.UnivIn3_Sense module and locate the SCPTgain point. Double click it. By Multiplier enter 1955 and by Divisor enter 1000. StruxureWare WorkStation Go to the 102-AX and click on UnivIn3Sense module and in the Variables tab locate the nciGainUIx point and expand it. For Multiplier, enter 1955 and save. For Divisor, enter 1000 and save.

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

Issue When trying to install TAC Vista and running the installation file the only option available in the installation wizard is to uninstall TAC Vista. Product Line TAC Vista Environment Vista server Cause A registry key which is not taken away when uninstalling TAC Vista is indicating to the installer that Vista is already installed. Resolution NOTE: Serious problems can occur if you modify the registry incorrectly. Make sure that you follow these steps careful. Open the Registry: go to Start > Run and type "regedit" Remove the folder for TAC Vista Server under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall The Vista folder will contain "TAC Vista Server" in the "Display Name" field and can be found by selecting each folder.

Issue The path to the templates and libraries is not documented Product Line EcoStruxure Building Operation, TAC Vista Environment Graphics editor Cause In order to use your own color and gradient templates and to copy component and snippet libraries you need to know the path to these files and folders. Components and snippets can preferably be managed directly through the graphics editor. Resolution In TAC Vista The libraries and templates are one and the same for all users: Colors and gradients: C:\ProgramData\TAC Graphics Editor\Brushes Components: C:\ProgramData\TAC Graphics Editor\Components Snippets: C:\ProgramData\TAC Graphics Editor\Snippets In SmartStruxure Each user has their own set of libraries and templates: Colors and gradients: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Brushes Components: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Components Snippets: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Snippets

Issue Is it possible to install TAC Vista Webstation on a PC that does not have Vista installed? Product Line TAC Vista Environment Vista Webstation 5.x.x Cause For security reasons some customers need to have TAC Vista Webstation installed on a PC located in the DMZ. The purpose of a DMZ is to add an additional layer of security to an organization's local area network (LAN); an external attacker only has access to equipment in the DMZ, rather than any other part of the network. Resolution TAC Vista Webstation must be installed on a PC where TAC Vista server is already installed. To resolve this you can install an empty Vista server on the PC and connect it to the Vista network together with the Vista servers already installed. After that you can install Webstation on the PC with the empty Vista server.

Issue Is it possible to use the TAC Xenta 102B device with room unit STR150? Product Line TAC Vista Environment STR150 TAC Xenta 102B Cause It is possible to use STR150 together with the TAC Xenta 102B device with system program 1.20 or higher. Resolution To use an STR-150 on a TAC Xenta 102-B controller, set nciAppOption bit 14.

Issue After the user have logged in to TAC Vista Workstation it hangs and the only option is to close it Product Line TAC Vista Environment TAC Vista Workstation 5.x.x Cause When users log in to TAC Vista workstation all events specified in the Event viewer window is retrieved. If too many events are retrieved to Vista Workstation it can cause Vista workstation to hang. Resolution Under the TAC Vista server object open properties for $Eventview Open the "Date and Time" tab and specify a shorter time period. Click OK

Issue TGML graphics to display "OFF" and "ON" instead of "0" and "1" Product Line EcoStruxure Building Operation, TAC Vista Environment TGML Graphics Editor Cause Data in the Vista database is stored as 0,1 but may be displayed using paired texts. Those paired texts can be set to show up on the graphic, or a unique conversion can take place in TGML. Resolution If you use default snippets that come provided with the editor, you have the option of displaying a value with either NumericPresentation or TextPresentation. The only real difference between the two is that TextPresentation defines the binding's behavior format as "Presentation" rather than "None." This will only display built in presentation formats -- an alarm state will show up as "Alarm" or "Normal" -- or if you've defined paired text within a binary point in the Vista database, that will show up instead of (0,1). This does not, however, explicitly give you the option from within the Graphics Editor to convert decimal values into text. The example TGML code below describes how to take a value that is showing up as "0" and "1" and make it read instead as "OFF" and "ON." <Text>Value   <Bind Attribute="Content" Name="Value">     <ConvertValue SignalEqualTo="0" AttributeValue="OFF"/>     <ConvertValue SignalEqualTo="1" AttributeValue="ON"/>   </Bind> </Text> Cut and paste this TGML code into the editor's Source view to view it in the editor. Just be sure to paste it between the opening tag and closing tag. If all you see in the Source view is one self-closing tag, that is because the page is empty. Either add separate opening and closing tags, or go back to Design view and add one object to the page to automatically split them.You can see here that a Text object has a binding associated with it. That binding's target attribute is "Content" because this will alter the content of the Text. (We could also change the text's stroke color, background color, font size, position on the page, etc., by changing our binding's target attribute.) ConvertValues underneath the binding tell the binding how to alter the Text's content. A SignalEqualTo 0 will write "OFF" to the content and a SignalEqualTo 1 will write "ON" to the content. The number of ConvertValues is not limited to only two. There could be a third one to say that a value of 2 should read "STANDBY."

Issue TGML Objects are not highlighted when dragging and dropping snippets to the graphics editing pane. If a number of objects are close together, it can be difficult to see which object the snippet is being dropped on to. Product Line TAC Vista Environment TAC Vista 5.1.7 TGML editor 5.1.7 Cause Updates to the TGML Editor in 5.1.7 removed this feature. Resolution The item which the mouse-pointer is hovering over is highlighted in the TGML menu tree in later versions. An upgrade will restore this functionality. As a workaround in version 5.1.7, snippets can be dragged directly to the desired object in the Objects Pane as opposed to the editor workspace to ensure the proper object is selected.

Issue What security levels are available in Vista? Product Line TAC Vista Environment TAC Vista Workstation User Administration Cause Different security levels can be set for different users to administrate what they can and cannot see or modify. Resolution Low security Low security is intended for TAC Vista systems not using a Windows NT/2k network. You usually log in as a TAC Vista user. Users from a Windows NT/2k network may be used at this level of security.  High security High security is intended for TAC Vista systems using a Win NT/2k Network. To set up a high security account in Vista: The user logs in as a user in a Win NT/2k network. TAC Vista users are not at this level of security. The user is verified by a domain controller in the Win network. To be able to log into the Vista system a Win NT/2k account must be defined in TAC Vista for each user/group who are authorized to access the TAC Vista system. When logging in the user is identified by TAC Vista via the domain controller in the Win network. 

Issue When an old OGC graphic is converted to a TGML graphic in TAC Vista the conversion will fail if the name of the OGC graphic is longer than 36 characters. The OGC to TGML converter will just close with no error message. Product Line TAC Vista Environment Vista Workstation Cause The OGC to TGML converter does not support OGC graphic names longer than 36 characters, but if you try converting with longer names, the converter just closes down without any error message indicating why the conversion failed. This is a defect in the OGC to TGML converter which is reported to R&D. Resolution Rename the OGC graphic to a name with 36 characters or less.

Issue How to set up PWM output in ZBuilder for TAC Xenta 121/122 devices. Product Line TAC Vista Environment Xenta 121 Xenta 122 ZBuilder Cause To be able to set up the PWM function for outputs, you need to understand each entry in the settings windows. Resolution   Activate at % TL The PWM output control starts when Terminal Load reaches this value. Fully active at % TL The PWM output control is fully active when Terminal Load reaches this value. Min control signal % The PWM output will not send out lower percentage of full stroke. Max control signal % The PWM output output will not send out higher percentage of full stroke. Period seconds The time for one full PWM period. This period will be cyclically repeated. Pulse change if change ≥ % Applicable only for actuators giving a position directly proportional to the pulse width and not dependent of cyclic updates (PWM with US terminology). This means the output will only activate when the Terminal Load has changed more than the set value, since last activation. Normally closed The TRIAC output is connected to ground (activated) when Terminal Load is zero, and the PWM output is not active. When the PWM output activates, the TRIAC output will not be connected to ground. Normally open The TRIAC output is open, not connected to ground, when Terminal Load is zero, and the PWM output is not active. When the PWM output activates, the TRIAC output will be connected to ground.

Issue In Vista Workstation you can create a new user and password using all characters of a keyboard. Vista Workstation allows creation but when you try to login to Workstation you get a login error. Product Line TAC Vista Environment Vista Workstation Cause Using characters in the password field that Vista does not recognize. Resolution Don't use the following characters in a password for users: !   @   #   $   %   ^  &  *  (  )  -  =  +  ,  <  >  '  "  ?  \ The following special characters can be used in the password field: _  .  /  : 

Issue After upgrading to TAC Vista version 5.1.7 no new values will be shown when a trendlog is opened.  Error message in Vista: System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near ')'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at TAC.DSS.DataAccess.SqlServer.SqlMaintenance.GetDatabaseFragmentationLevel(String tablename) at TAC.DSS.DataAccess.SqlServer.SqlMaintenance.GetDatabaseFragmentationLevel_TrendlogValue() at DssCliLib.Utility.GetDatabaseFragmentationLevel_TrendlogValue(SByte* pszConnectionString, Int32* plSize) Product Line TAC Vista Environment Vista Server version 5.1.7 Cause This issue occurs due to the use of an incompatible SQL server version. A number of new features were introduced in Vista 5.1.7, one of which was a check of the SQL database's fragmentation level. It is this check that fails as it uses a query that is not recognised in SQL 2000. Resolution Upgrade/run the database to/on SQL 2005 server or higher.