Issue Disable FTP (File Transfer Protocol) in all X5/7/9xx controllers Environment Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 Cause In some high security project installations, local IT groups require that FTP (File Transfer Protocol) be disabled on all devices within their network. Resolution FTP into the Xenta 5/7/9xx controller by typing FTP://x.x.x.x (where x.x.x.x is the IP address of the controller) in the Windows Explorer address bar. Login with the root username and root password. Browse to the sys/system/ftp.cfg file and copy it to the desktop of the local machine. Open the ftp.cfg file with notepad on the local machine. Set the FTPMaxUsers="4" line to FTPMaxUsers="0" and save the file. Copy the file back to the FTP session on the controller and paste / replace it over the existing file. Logout of the FTP Session Cold start the controller Now the Xenta 5/7/9xx controller will not have FTP access. If there is a need to re-enable FTP please follow this steps on the Xenta 511, 527, 555, 701, 711, 721, 731, & 913 Login into the controller via the web interface with the root level username and password. Navigate to Configuration > Servers > FTP Server Set the Max. number of users back to a valid number of 1-5 and click save. Cold start the controller. If FTP needs to be re-enabled on the Xenta 527-NPR the only option will be to reload the system program. This is because the 527-NPR does not have a full web configuration interface like all other Xenta 5/7/9xx controllers to set the number of users.   Update note: In later versions of the Xenta Server, FTP is disabled by default (the number of users are set to 0). If you still can't login to FTP, try to format the controller, reload the system program and try it again. Then it should work now.

Issue Can the RPTR-ECH-WW repeater be used on a TP/FT-10 LON trunk? Environment RPTR-ECH-WW; a wire-wire repeater for use with Echelon NIMs (GCM-ECH-001, GCM-ECH-001, or DMS-ECH-001) TP/FT-10 LON trunk ( under a UNC, ENC, or LNC-100, for example) Cause The RPTR-ECH-WW is for use on a trunk using the Echelon TP/XF-1250 transceiver, which use a different communications protocol than the TP/FT-10 transceiver does. Devices using different transceivers will not communicate with each other. Resolution No, the RPTR-ECH-WW cannot be used on a TP/FT-10 LON trunk such as the UNC, ENC, or LNC-100s support.

Issue When logging in once the login screen appears again Environment Vista Webstation Windows 2003 Windows 2008 Cause Windows 2003 server and 2008 server have different default security  settings for Internet Explorer and may deny cookies, this problem should not appear in Windows XP if default settings are used, you can also check if it works with Firefox, if it do so its ought to be the security settings in Internet Explorer. Resolution When the problem occurs, there should be a notification after the address bar. Click on that and allow an exception for the IP address for the Xenta.

Issue The priority attribute was not specified as configurable. (Subsystem: NS Connections, #11) lcaErrConnPriNotConfigurable An attempt was made to modify the priority attribute; that attribute was not specified as configurable. For network variables, the priority keyword may be included as part of the connection information in the Neuron C variable declaration.  The config and nonconfig keywords specify whether the priority designation can be modified with a network management tool. The default is config. The priority keyword affects output or polled input network variables.  Please refer to the Neuron C Reference Guide for more information. Environment LonMaker Cause Applying a connection description to a new binding that causes a connection error, such as applying a connection description with the priority attribute set to a connection that does not support it, causes this error message to be displayed. Subsequent attempts to add any connection with the default connection description will result in the same error message. Resolution Exit LonMaker Re-open the LonMaker tool.  Then add the connection.  Alternatively, explicitly select a valid connection description other than "Default."

Issue Setpoint button may break if forced outside of movement range. Environment STR-106 Cause Excessive force used to turn setpoint button outside of movement range. Resolution Report faulty unit through Warranty Claim System. Replacement button carries component no 372069900.

Issue Can't see the Xenta Server Menta  program online in the browser Menta program is working but it is not possible to view it online All other viewers work correctly Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause One reason could be that there are texts (comments) in the Menta application that does not have any font specified. Resolution Edit the Menta file form Xbuilder Find any comment/texts Double click to edit Click on font Select a font and save Download the Xbuilder project again

Issue Modifying alarm tripped text and reset alarm text on a Xenta programmable controller under a Xenta Server is not reflecting these changes. Environment Vista 5.x.x/4.5.0 Xbuilder 5.x.x/4.5.0 Cause When the Xenta programmable controller is added to the LonWorks network under a Xenta Server an alarm object is created in Xbuilder with the Tripped Alarm Text and Reset Alarm Text from the MTA file. Updates to the MTA file or alarm object in Vista server does not update the Xbuilder project. Resolution Edit the Xenta Server object and modify the Tripped Alarm Text and Reset Alarm Text for the in the Alarms folder under the programmable controller in the Network pane of Xbuilder.

Issue What resources are available to get more information on the M-Bus protocol? Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment M-Bus Cause The M-Bus protocol information is available on www.m-bus.com. Select The M-Bus: A Documentation Rev 4.8 Resolution The M-Bus protocol specifications is broken down in multiple chapters. Basics of Serial Bus System Overview of the M-Bus Physical Layer Data Link Layer Telegram Format, Meaning of Fields, Communication Process Application Layer Structure of fixed and variable data blocks. Network Layer Appendix Table of units, medium, data field codes, VIF extensions.

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