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 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.

Issue When using I/A MNL800 controllers in Vista classic network (without using LNS database), an issue will happen when commissioning and downloading the controller: Local Network Management Failure, Info: nci_Location. The xif file has been updated to the newest version of the WPT program. Environment WPT version higher than 5.7.2 Vista 5.1.6 Cause The possible cause is that the WPT version is too high for Vista classic network to integrate. Resolution Firstly it isn't recommended to use I/A LonWorks controllers in Vista system. And there is no specific compatible matrix for Vista and WPT. Currently the proved version of WPT that can be used with Vista 5.1.6 is 5.7.2. The version higher than this will has this issue. So the only solution is to use the xif file generated by WPT 5.7.2 in Vista classic network.

Issue Start TAC Vista Comm. Log Product Line TAC Vista Environment TAC Vista Server Cause Sometimes to solve a problem we need to record the communication to and from TAC Vista. Resolution Start the TAC Vista server Open workstation and close all graphics, charts, etc., that are not needed to reduce traffic and make the log easier to read. Log in to TAC Vista Server. Go to Log > Comm. Log Set Physical layer to active Click Ok  The log will be created in the $log folder in the TAC Vista db.

Issue Naming a point in Menta results in a pop up error Warning Syntax error Product Line TAC Vista Environment Menta Cause Special characters are not permitted in the names of Menta signals. Resolution Remove all of the following characters from the Menta signal name: space . period, ? question mark - dash (hyphen) !, @, #, $, %, ^, &, *, (, ) \ backslash denotes the Menta module name separated from the Menta signal name. One is permitted, the second will cause a syntax error The best rule to go by is to use nothing but alphanumeric characters and (_) underscores in Menta naming conventions.

Issue Get "Type error: cannot call method "toFixed" of null" error message when opening a TGML graphic, upgraded to Vista 5.1.7   A TGML script has stopped working after upgrading to Vista 5.1.7 Environment TAC Vista Workstation 5.1.7 TGML editor 5.1.7 219 Cause Javascript method toFixed can only be used with numerical values. The TGML engine in TGML 5.1.7 is stricter than the older versions, so an upgraded script may have worked in previous versions. Resolution An example when using convertCustom element. Original script: function convert(value) { value = value.toFixed(2); return value; } should be: function convert(value) { value = Number(value).toFixed(2); return value; }  

Issue Get "Value does not fall within expected range" error message when trying to view values from a Vista node in webstation. Environment Vista 5.1.X Webstation 5.1.X Vista in network (master with at least 1 slave) Cause This is a COM error caused by a difference in regional settings on the Vista servers. E.g. 100 000.00 may be retrieved as 100,000.00 if other settings are used on another server. This will cause a mismatch. Resolution Ensure that the settings for digit grouping and decimal symbol are the same on all Vista servers. Click on Start\Control Panel\Regional and language options. Select Customize and check the settings on the Numbers tab. Compare these settings with the other Vista servers.

Issue Import/Export in TAC Vista Workstation does not work. Nothing happens when trying to start the import/export. Environment TAC Vista Cause The $DatabaseExport and $DatabaseImport objects in the Vista database has been removed, probably during an upgrade. Resolution In the instructions below, we assume that TAC Vista is installed in the default location. Replace the version number (5.1.6) with the actual version you have installed, and the Vista Server name (VistaServer) with the actual name of your Vista Server. This procedure requires that TAC Vista Server is running as an application, and not as a service. 1. Make sure TAC Vista Server is stopped -- First we need to change a file to allow creation of these objects -- 2. Browse to C:\Program Files\Schneider Electric\TAC Vista 5.1.6\$cfg 3. Find a file named "objtmpl.cfg", make a copy, just in case. 4. Edit the file with notepad and find the strings FI_EXPORT and FI_IMPORT. 5. Remove AB on each of the two lines, (stands for abstract object), save and close. 6. Browse to the TAC Vista database folder, and open the folder $thisdb. 7. Change the name of the file TacVista.cfg, to TacVistaOld.cfg 8. Start TAC Vista Server. -- Now we need to create the missing objects -- 9. Open the testclient (testclt.exe) located in the folder C:\Program Files\Schneider Electric\TAC Vista 5.1.6 10. In the menu, click "Session-->Log in" 11. In the menu, click "Services-->Create" 12. In the ID field, write "VistaServer-DatabaseExport" and in the type field write "FI_EXPORT" 13. Click "Create". 14. In the ID field, write "VistaServer-DatabaseImport" and in the type field write "FI_IMPORT" 15. Click "Create". -- Now we have to change the name of the created objects to $DatabaseExport and $DatabaseImport -- 16. In the menu, click "Services-->Access" 17. In "Enter ID:" write "VistaServer-DatabaseExport.$name" 18. Click "Request" 19. Write "$DatabaseExport" in the "New Value" field, and click "Poke". 20. In "Enter ID:" write "VistaServer-DatabaseImport.$name" 21. Click "Request" 22. Write "$DatabaseImport" in the "New Value" field, and click "Poke". 23. Reenter AB on each of the two lines in "objtmpl.cfg" previously edited in step 4, save and close.  

Issue There are a number of TGML link or binding objects with the name ??128 in a folder in Vista workstation. They cannot be deleted. An error message "Could not delete the object. Attempt to delete an abstract object" appears. Product Line TAC Vista Environment TAC Vista Workstation 5.1.X Cause Sub-objects from a TGML graphic have not been removed from the database when the graphic has been deleted. This may be an indication that the database is corrupt. The error from Vista is "nonexisting object in request/advise/poke". Resolution It may be possible to delete the folder that the objects are in and thereby remove the sub-objects. Otherwise a backup of the Vista database (from a time before the objects appeared) will need to be restored.

Issue Vista hangs when navigating between TGML graphics. The screen dims, Vista workstation stops responding and an error message is displayed. In the event viewer the following event description is displayed: Description: Application: TACVistaExplorer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException Stack:    at java.lang.String.instancehelper_length(System.String)    at SE.Graphics.DOM.TGML.TgmlTextShape.setAttribute(System.String, System.String)    at SE.Graphics.DOM.TGML.TgmlBind.internalSetAttribute(System.String, System.String)    at SE.Graphics.DOM.TGML.TgmlBind.executeBind(System.Object, System.String, System.String, Int32)    at SE.Graphics.GraphicsServices.Dynamics.BindUpdater.executeBinds(SE.Graphics.GraphicsServices.GraphicsDocument)    at SE.Graphics.GraphicsServices.GraphicsDocument.UpdateBinds()    at SE.Graphics.Viewer.Windows.GDIPlus.GraphicsViewerControl.UpdateDynamics()    at TAC.Graphics.Windows.Vista.VistaGraphicsViewerControl.UpdateView()    at .CODEChildTgmlGraphics.UpdateView(CODEChildTgmlGraphics*)    at ._WinMainCRTStartup()   Environment Vista Workstation 5.1.6 TGML graphics Cause Workstation crashes when the TGML graphic updates it's content. It's suspected that at the same time as the TGML graphic is updating it's content, the graphic is changed, which means that it's not there anymore to receive the updates. Resolution Change the registry key HKEY_LOCAL_MACHINE\SOFTWARE\TAC\TAC Vista Workstation\5.1.X\MaxTGMLFPS  (max TGML frames per second) to 0.

Issue The Xenta 121-FC/HP controller will not build a terminal load when in unoccupied night setup mode. Environment ZBuilder 5.1.6 Xenta 121-FC Xenta 121-HP Cause The “Cooling interlocked to fan” setting prevents the unit from building cooling terminal load in unoccupied mode. Resolution This issue will be corrected in a future upgrade but for now this is a work around. Open ZBuilder Go to the Configuration tab > Control > Fan > Interlock Uncheck the box called “Cooling interlocked to fan”. Click Apply at the bottom of the window to update the settings in the controller.  

Issue Instructions for finding the version of LonMaker and LNS Server on a machine. Environment Echelon LonMaker Cause Knowing the version of LonMaker and LNS are necessary for many troubleshooting techniques. Support representatives may ask you to have this information available in order to assist you better. Resolution Please follow these steps to find the version of LonMaker and LNS server on the machine: Open LonMaker, then pick and completely open a network. Choose the LonMaker menu in the menu bar, then about LonMaker: This is the about LonMaker window that should be shown. As you can see in this screen capture, LonMaker 3.1 is being run with the LNS server version 3.27.

Issue When doing Xenta server to Xenta server communication, via other projects network, a good troubleshooting technique is to determine if the two Xenta servers are truly communicating to one other over TCP-IP. This is possible via the online status of the imported Xenta server in the project tree. Environment Xenta 511, 527, 555, 701, 711, 721, 731, and 913 Cause Two Xenta servers are set up to communicate to one another, but they are not passing data properly. Troubleshooting step number one should be to determine if the two Xenta servers are online to each other on the TCP-IP Resolution To  check the online / offline status of a Xenta server follow these steps: Login to the web browser of the Xenta server that that is configured to receive data. Navigate to the project tree similar to the image below. 3.  Within the project tree, browse down to the Xenta servers and check the online status as shown here: