Building Automation Knowledge Base

Issue The Xbuilder device editor by default only allows 200 lines, and some integration efforts require more than 200 points to be programmed. Environment Xbuilder Device Editor Cause The device editor only has 200 rows by default. Resolution The device editor is designed with excel functionality meaning, new rows can be added to allow for more points to be programmed. To add rows to the device editor follow these steps: Open the device editor. Right click on the row number. Choose insert row. Type in the desired number of rows (up to 100) If more than 100 are needed repeat steps 2-4.

Issue When a SQL query is run on taclogdata to view events or trend logs, the time stamps returned differ by an hour or more from the those of the same events when viewed in Vista. Environment TAC Vista 4.3 and higher MS SQL Server Cause All time stamps are stored in taclogdata as UTC (Universal Coordinated Time) regardless of your local time zone and DST (Daylight Saving Time) settings. When you view events or trend logs in Vista, the Time Zone and DST settings of your Workstation are added to the UTC time so that you see time stamps synchronized with your local time. This does not occur when a SQL query is run directly on taclogdata. Resolution If you need to query the Vista SQL database directly, you could use the DATEADD function to calculate your local time from the UTC values, e.g. in SQL Server Management Studio run the following query to show the EventId, UTC time and local time for all events that occurred in the last 24 hours. USE taclogdata; SELECT EventId, EventDatetime, DATEADD(hour, datediff(hour, getutcdate(), getdate()), EventDatetime) AS LocalTime FROM Event WHERE EventDatetime > DATEADD(day, -1, GETUTCDATE()) Please note:  DATEADD adds a fixed offset to the input time.  It does not compensate for start and end dates of DST. 

Issue Multiple FLEXnet License File errors warn that the license file is about to expire or has already expired. Errors may be logged in Windows system log that may look something like this: (2372) Feature: Micronet.VisiSat.Core, expires on 30-apr-2011. This is a two week notice. Multiple errors may pop up at once or may only occur daily. Here are two examples of messages you might see. Event Type:      Warning Event Source:    taclic_LicenseServer Event Category:          FLEXnet License File Event ID:        718 Date:            30/04/2011 Time:            12:00:52 AM User:            N/A Computer:        BMSSERVER Description: (2372) Feature: Micronet.VisiSat.Core, expires on 30-apr-2011. This is a two week notice   Event Type:      Error Event Source:    taclic_LicenseServer Event Category:          FLEXnet License File Event ID:        716 Date:            5/17/2012 Time:            2:55:15 PM User:            N/A Computer:        G15HVAC Description: (2516) This license (Vista.Server.LNS) has expired. Environment FLEXnet License Server Cause A valid site license and demo license have been left in the Vista license directory. The system message is letting you know that the demo license will or has already expired. Resolution Remove or relocate the demo license once it is no longer required on site. This will prevent this error message from appearing in the Windows Event Viewer.

Issue SNVT_str_asc (ASCII string) is being brought into/sent out of Menta. SNVT output for "location" required by job specs. What are the capabilities for handling ASCII strings in Menta? Environment Menta 5 SNVT_str_asc Cause Menta does not have a very robust ASCII string handling, but it can be done. Resolution Menta can use special modes on the PIDI block to encode/decode ASCII characters into decimal character values. Macro libraries exist to perform these actions: Right click in the white space in Menta and select "Load Macro..." Navigate to Macro Block Library > Miscellaneous > SNVT Load str_asc_OUT2.AUT for an example of outputting a SNVT_str_asc Load str_asc_IN343.AUT for an example of inputting a SNVT_str_asc Different string handling applications are available: Str_asc_IN3.AUT Str_asc_IN248.AUT Str_asc_INtext.AUT Str_asc_OUT2.AUT Str_asc_to_str_int.AUT Str_int_IN_OUT1.AUT Str_int_IN343.AUT Str_int_OUT2.AUT Str_int_to_str_asc.AUT

Issue Running I/O Server as a service and an error 1075: The dependency service does not exist or has been marked for deletion pops up. Environment Running I/Net as a Host Tool under TAC Vista and wanting to configure I/O Server to run as a service. Cause I/O Server requires that MSSQL be tied to the dependencies of the service and when it is not listed, it will generate that error. Resolution When this error comes up, there are several things that needs to be checked to verify that it is set and connecting to the correct database in I/NET: Right Click on My Computer and go to Manage. Select Services and Applications, expand that and select Services. Select I/O Server, Right Click and select Properties then click on Dependencies. MSSQL should be listed in there and more than likely it is not and has to be added. To add it, go to run and type regedit, go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\INet7IoSrv] DependOnService – add the SQL instance (for example MSSQL$TACVISTA) and the TAC Vista Server (TACOS). This multi string value should list:RPCSS,TACOS, MSSQL$TACVISTA Restart the PC and it I/O Server should be running as a service now.

Issue Existing NL220 license is not working correctly. Environment Vista NL220 Engenuity Newron Systems Cause License is preventing proper execution of the software. Resolution All licensing errors should be resolved via Newron Systems Americas distributor, Engenuity at the following contacts:   Phone: 480-782-5600   2165 W. PECOS RD. STE. 1 Fax: 480-782-5601   CHANDLER,  AZ Toll free: 800-375-3363   85224 Email: info@engenuity.com

Issue When upgrading Vista Workstation to version 5.1.6, each Xenta Servers' properties should be set to XBuilder version 5.1.6. Then by right-clicking and selecting "Edit," that project will be opened and upgraded. However, if another projects network has been browsed in, it will ask you to please upgrade that project before continuing. If two Xenta Servers are each browsed into each other's networks, then it will not allow you to upgrade either of them. In previous versions, this was allowed, but with changes to 5.1.6 it is not possible to bypass this warning. Environment Vista Workstation 5.1.6 and above Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause All Xenta Servers passing data between each other should be the same version. In the past, this fact was made optional, but with the release of 5.1.6 a check on the source file requires that they match. Resolution This requirement is only true of true Xenta Servers in a Vista system. Stand-alone XBuilder projects do not have this same check. To bypass the warning: Go to Start > Programs > Schneider Electric > TAC Tools 5.1.6 > XBuilder This will open XBuilder 5.1.6 in a stand alone mode (not from Vista Workstation) Go to File > Open Project and browse to the first Xenta Server's XBuilder project file folder and double click the .xbp515 project file The XBuilder project will be upgraded to 5.1.6. The other project's network will still be 5.1.5, but this is allowed in the stand alone mode. File > Save will save the .xbp516 file to the hard drive. Go back to Vista Workstation, right click and edit the second Xenta Server's XBuilder project and it will not upgrade and can be saved to the Vista database and to the hard drive. The first Xenta Server can now also be upgraded.

Issue XBuilder allows for the target type to be changed via the Project menu > Change Target Type. This will change all references in the project if changing from a Xenta 527 to a Xenta 731, for example. Sometimes this menu item is not available and appears grayed out. Environment XBuilder Vista Classic Network Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause When a Xenta controller is used as a Xenta Server in a Vista classic network, there are references in XBuilder to the Vista database that will prevent the target type from being altered. Resolution Save a copy of the database XBuilder project to the hard drive.  File > Save As... Open XBuilder in a "stand alone mode" (Start > All Programs > Schneider Electric > TAC Tools 5.1.X > XBuilder) Open the project from the hard drive Select Project > Change Target Type. This option should now be available. Change target to the desired type and send to target. Note: The device in the Vista database has not been updated by this process. If the Xenta Server needs to change types, this must be done in Vista Workstation. Create a new Xenta Server and then use the XBuilder menu Vista Database > Save As... to reassociate the XBuilder project with the database object.

Issue Logging into Vista Workstation results in error: "Can not connect to TAC Vista Server, No such interface supported" Environment Vista Cause Some connection between the Vista Server and the LNS Server has been broken. This is because of some change to the PC configuration: virus scan, Windows updates. You have installed a component of a different version. Resolution Uninstall TAC Vista, system plug-in etc. Delete any TAC Shared folder in the \\Program Files\Common Files catalog Reinstall Vista

Issue In a Vista classic network, right click and edit a Xenta 121. Click the load button to load a .zbc file stored on the hard drive and there is no option but to cancel. It will not take a load. Environment Xenta 121 ZBuilder Vista Classic Network Cause Because the Xenta 121 type is stored in the Vista database at the time of the creation of the node, it will not allow a fan coil (FC) file to be loaded into a heat pump (HP) or vice versa. Resolution Right-click on the 121 Go to Properties > XIF File Look at the source file listed and make sure it contains either HP or FC and that matches the actual controller. Alternatively: Right-click on the 121 and select Edit Click on Load Unavailable templates will be grayed out -- see if it is the FC or the HP templates that are grayed out. Make sure the template .zbc that you are browsing to on the hard drive is set to the same type as the controller that is defined. If necessary, delete the existing controller and add it back as a different type.

Issue Operation of Xenta 121-HP Flow Feedback Error as sensed via hardwired flow input or nviSourceFlow network input. Environment Xenta 121-HP ZBuilder Cause For a heat pump, nvoSystemStatus bit 12 is set if an expected flow is missing. For example, when the isolation valve is open there should be a flow feedback, but when it is closed or opening, no signal is expected. Resolution Flow feedback error will disable cooling and heating outputs. There is no need to define an exception mode in ZBuilder in order to enable this safety override.

Issue How to Integrate GSM/SMS functionality to TAC Vista using SysMan SMS Server Environment TAC Vista SysMan Server Cause What are the GSM modems can support to integrate with TAC Vista. Where to find the Installation/Product manuals.  How to Integrate SysMan SMS Server with TAC Vista Resolution For supporting modems/Documents/Integration details go to http://www.sysman.no/ Part Numbers: 1. SysManSMS ALERT SERVER: 900800600 2. SysManSMS GSM Modem: 900800610   In the UK when ordering please use the below part numbers. 1. SysManSMS ALERT SERVER: 802000 2. SysManSMS GSM Modem: 100002

Issue Is it possible to add a new font in the TGML graphics editor Environment Tac Vista 5.1.X TGML editor Graphics Editor TGML 1.1.X Cause There are a number of reasons why a customer would like a particular font. For example, the customer has a corporate font that they use on their existing website and they would like to this to be used in their TGML graphics. Resolution To add a new font, just add the .ttf file to C:\Windows\Fonts (or the equivalent in your language) and restart TGML editor. Please be aware that the font must support regular (non bold) line weight, otherwise it will not be read by TGML editor at startup.  

Issue How does the Xenta 121 indicate that a fan feedback failure condition has occurred? Environment Xenta 121-HP Xenta 121-FC Cause The fan failure signal could be used to trigger another sequence of events, to annunciate an alarm in the Workstation, or to send an email to the on-call mechanic. Resolution The output SNVT, nvoSystemStatus bit 15, represents a fan failure condition.

Issue In Vista 5.1, TGML graphics bindings can be bound using a multi-bind .[OBJECT] bindings. Dragging and dropping a single object can then automatically bind all other defined signals, for example. But there is a limitation of two network levels. Environment Vista 5.1 Workstation TGML Graphics Bindings window Cause Controllers with standard naming (especially application specific controllers with pre-defined naming) can be bound to graphics more quickly and efficiently with the use of multi-binding. There are limitations to what can be multi-bound simultaneously. Resolution Multi-binds can bind all defined signals for up to two levels of their database structure. For example: RoomTemperature.[OBJECT] can be used to bind: RoomTemperature.PV and RoomTemperature.OVR You can travel up one more level, though to get even more signals at once: SUMMARY.[OBJECT] can be used to bind: SUMMARY.RoomTemperature.PV and SUMMARY.RoomTemperature.OVR and SUMMARY.RoomSetpoint.PV You cannot travel up any more levels, so you could not do: LonworksNetwork.[OBJECT] in order to bind all signals in a network at once.  

Issue Attempts to login are unsuccessful and device reports that logins are blocked. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server tracks attempts to log in by recording the IP address and Username of the login attempt. After 5 login attempts it will block any attempts to login to with that username and IP address for 10 minutes. Resolution Use a different user account on the Xenta Server to login and perform the necessary work or wait 10 minutes for the lockout to expire. If the lockout is continuing after 10 minutes then ensure that if the Xenta Server is in a Vista database that it is not running and trying to communicate to the Xenta Server with an incorrect username and password. Any changes to the root user password must also be changed in the Vista database to avoid perpetual blocking of login attempts on that computer and IP address.

Issue When a SHR100-T is setup with a 0-10 volt humidity sensor the temperature reading fluctuates Environment Xenta controllers I/NET Controllers SHR100-T Temperature Humidity Sensor Cause Interference from the 24Volt AC power supply in the same cable causes this temperature fluctuation. Resolution  The two tested fixes that stabilize the temperature reading are. Set the humidity as a 4-20mA signal, this will stabilize the temperature reading. Run the 24Volt AC power supply in a separate cable. This is the better option if this is noted before installation is started.

Issue The following error message occurs when starting OGC editor on a remote PC using remote desktop: "Local TAC Vista Server not started. Cannot reserve graphic object". Environment Vista 5.X Remote Desktop Windows XP Windows 2003 server Windows 2008 Server Windows 7 Cause There are two ways of connecting with remote desktop - connect to the console session or create a new session. The console session is what you see when you log in locally on the server. If you create your own session that is not the same as what’s shown on the server’s own monitor. If you start a programme in a new session this will not be seen in the console session. Each new session receives a new session ID. Resolution Connect to the remote desktop using console admin mode. Click on Start\Run and then type mstsc.exe /admin Log on to the remote desktop with a user that has administrator rights on the remote PC. Confirm that you are connected to the console session. Start OGC graphics editor. Open the task manager - Right-click on the task bar and select Task Manager. Select the tab Processes. Ensure the column Session Id is shown. If not go to  View\Select Columns and select Session ID Locate the process TADRAW.exe process and ensure that the session ID = 0 (in other words the console session) Please note that Schneider Electric does not officially support this method of running programs.

Issue Is TAC Vista webstation 5.1.X supported on Windows 7? Environment Windows 7 Webstation 5.1.X Cause Webstation works with Windows 7, but the reason why it's not officially supported is that the number of concurrent connections is limited to 10 (the same as in XP). Resolution Webstation is not supported on Windows 7. If/when an issue arises our advice will be to upgrade to a server (2003, 2008) as unexpected behaviour may be resolved simply by doing this.

Issue If "Use server assigned subnet/node address" is unchecked and manual addressing is used what addressing guidelines should be followed. Environment Vista Server/Workstation Vista Classic Network Cause The node addressing of a network can be performed in different ways. All nodes need an individual Subnet/Node address, in other words, a logical address. The Subnet address can be any number between 1 and 255. Server assigned subnet/node addressing typically uses Subnet 255. To facilitate future router connections it is recommended that you start with Subnet no. 10. Normally the I/O modules or STR 350/351s have the same Subnet address as their TAC Xenta 280/300/401. Resolution The addressing of a TAC Xenta Node should follow some simple rules. Each TAC Xenta device requires three consecutive node addresses; the first for the device itself, the other two are always reserved for the handling of one or two operator panels. Example: Device 1 - Node address 10(and 11 and 12 for any OP) For each TAC Xenta 301/302 device a maximum of two I/O modules or STR 350/351s may be added (for TAC Xenta 401 ten I/O modules/STRs; for TAC Xenta 280 two STRs), each requiring its own address. The address will typically follow the two OP addresses. Example: I/O Module 1 - Node address 13. I/O Module 2 - Node address 14 and so on. The maximum number of Node addresses on one subnet is 127 (125 for the TAC Xenta 280/300/401). If the number of nodes exceeds 125 on a Subnet, or if logical grouping is required for other reasons, a new subnet number is used.