Issue Executing a Project Builder File should launch Visio and open a drawing. Instead, Visio opens but stops short of the file opening. Environment Project Builder Visio Cause Project Builder is disabled in Visio. Resolution In Visio go to Help>About Microsoft Visio Click on Disabled Items button in the pop up. Ensure Project Builder is not listed If so, select the Project Builder Listing Click the Enable button. Restart Visio.

Issue When adding a physical layer Xenta repeater, or Loytec smart-switch, to split a single channel into multiple segments, there is no need to represent that repeater/smart-switch in the LON network.  It will be invisible to the LNS database, and will function only on the physical layer. Environment LON Network with more than 64 devices on a single segment Xenta Repeater, Loytec Smart-Switch Cause A single LON segment can have up to 64 devices (though a conservative recommendation is typically closer to 50).  A segment is a single LON wire that is separated from another segment either by a physical layer repeater, smart-switch, or router.  A channel can have up to 3 segments separated by a repeater with a limitation of 128 devices (or nodes) total on the channel. Resolution There is no need to represent a physical layer repeater/smart-switch on the LON drawing or in the LNS network.  It will be operating on the physical layer either amplifying signals or filtering noise and bad data, and repeating messages on the wire.  The LON network will only see a single channel without any indication that there are 2 segments, other than the fact that there may be more than 64 devices on that channel.

Issue Each time the PC starts the below prompt indicating that the license server manager could not determine where to find the licensing data it needs.  This has to be manually re-entered on each restart of the computer. Environment Vista 5 Windows XP Cause Security settings or policies on the workstation are not allowing the registry setting to be saved or are been overridden during start up. Resolution Security settings or policies on the workstation must allow this setting to function or not be overridden. For information, the registry setting is located in the following registry key. "HKEY_LOCAL_MACHINE - FLEXlm License Manager - TACLIC_LICENSE_FILE" key.

Issue I/O-modules go offline After adding more than 16 I/O modules, some I/O modules start going offline Only 16 out of 20 I/O modules comes online Environment TAC Vista TAC Xenta 700 Server TAC Xenta I/O modules Cause In TAC Vista 5.1.0 and earlier, the default value for Receive Timer is set to 24576 milli seconds. That is too long time if you want to keep 20 I/O-modules online (the Xenta 700 device does not answer some of the I/O-modules). TAC Vista 5.1.1 and newer have the receive timer set to 2048 by default, though this only applies to new installations (i.e. if you upgrade it will keep the old value) . Resolution Open the properties window of the Lonworks network Change the receive timer to 2048 ms.  All the I/O modules should now come online. If not, lower the receive timer one step, though not less than to 768 ms.

Issue How do I reset the view of the System Plug-In  to the original look. Environment System Plug-In Cause They folder pane has been modified and now the default layout is required. Resolution A reset to default will be required to get the original settings These steps will reset the view to default Open the System Plug-In Under the file menu select Default Settings A message will appear that "The command requires a restart to take effect." Shut down the System Plug-In Restart the System Plug-In  with the original default setting is applied

Issue Upgrading SQL server whilst Vista is running Environment Upgrading from SQL 2000 express -->  SQL 2005 express Upgrading from SQL 2005 express -->  SQL 2008 express Any other upgrade eg. express to full version. Cause Issues may arise if trying to upgrade the SQL log database whilst Vista is running. Resolution 1.Turn TAC DSS writer off a. Click on Start\Settings\Control panel\Administrative Tools\Services. b. Locate the TAC DSS Writer Service and right-click on it. c. Select "Stop". The service will be stopped. 2.Upgrade the SQL Database 3.Turn TAC DSS Writer on a. In the services console opened in step 1 right-click on the TAC DSS Writer Service and select start. Whilst SQL is being upgraded, the events and logs will be written to the $Queues\insertevents and $Queues\insertlogvalues folders. Once the upgrade is complete and DSS writer is running again the $Queues folders will be emptied and all values will be logged to SQL.

Issue Certain values in the Xenta 102-AX can be put into override mode through the Plug-In: Airflow Auxiliary Temperatures 1 and 2 Universal Inputs 1, 2, 3, and 4 CO 2 Space Temp Damper Position Universal Outputs 1, 2, and 3 If the plug-in is not available, they can be overridden through the SNVT input nviRequest (type SNVT_obj_request). Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The plug-in might not be available for a multitude of reasons. For example, if the Xenta 102-AX is being integrated into a third party LON system, or no LNS management tool is being used. The values below can be used to implement an override through the SNVTs. Resolution Signals required to perform external control of inputs and outputs on the Xenta 102-AX: Set the override behavior value signal to 1 (OV_SPECIFIED) Set the desired value in the override value signal Send a SNVT to the signal Node_Object.nviRequest. It is a structured SNVT input with the following members: OBJECT_ID - refer to the list below for the appropriate object ID for each override OBJECT_REQUEST - set to value to 6 (RQ_OVERRIDE) to initiate the override, set to value 0 (RQ_NORMAL) to release the override. The tables below specify all necessary signals for each override. They are displayed in the following format: ID Title Overridden Value Desired Override Value Override Behavior   1 Airflow Reading (CFM, l/s) Airflow_Sense.nvoAirFlow.PV Airflow_Sense.nvoAirFlow.SCPTovrValue.PV Airflow_Sense.SCPTovrBehave.PV   2 Universal Input 1 (%) UnivIn1_Sense.nvoUnvInput1.PV UnivIn1_Sense.nvoUnvInput1.SCPTovrValue.PV UnivIn1_Sense.SCPTovrBehave.PV   2 Duct Inlet Temperature UI1 (°F, °C) UnivIn1_Sense.nvoAuxTemp1.PV UnivIn1_Sense.UCPTovrValueTemp.PV UnivIn1_Sense.SCPTovrBehave.PV   3 Universal Input 2 (%) UnivIn2_Sense.nvoUnvInput2.PV UnivIn2_Sense.nvoUnvInput2.SCPTovrValue.PV UnivIn2_Sense.SCPTovrBehave.PV   4 Universal Input 3 (%) UnivIn3_Sense.nvoUnvInput3.PV UnivIn3_Sense.nvoUnvInput3.SCPTovrValue.PV UnivIn3_Sense.SCPTovrBehave.PV   4 CO2 Reading UI3 (ppm) UnivIn3_Sense.nvoCO2sensor.PV UnivIn3_Sense.UCPTovrValueCO2.PV UnivIn3_Sense.SCPTovrBehave.PV   4 Outside Air Temperature UI3 (°F, °C) UnivIn3_Sense.nvoAuxTemp2.PV UnivIn3_Sense.UCPTovrValueTemp.PV UnivIn3_Sense.SCPTovrBehave.PV   5 Universal Input 4 (%) UnivIn4_Sense.nvoUnvInput4.PV UnivIn4_Sense.nvoUnvInput4.SCPTovrValue.PV UnivIn4_Sense.SCPTovrBehave.PV   5 Setpoint Offset UI4 (°F, °C) UnivIn4_Sense.nvoSetPtOffset.PV UnivIn4_Sense.UCPTovrValueTemp.PV UnivIn4_Sense.SCPTovrBehave.PV   6 Space Temperature (°F, °C) VAV_Controller.nvoSpaceTemp.PV VAV_Controller.nviSpaceTemp.SCPTovrValue.PV VAV_Controller.SCPTovrBehave.PV   7 Damper Actuator (%) Damper_Actuator.nviRelStPt.PV Damper_Actuator.nvoActualValue.SCPTovrValue.PV Damper_Actuator.SCPTovrBehave.PV   8 Universal Output 1 (%) UnivOut1_Object.nviUnvOutput1.PV UnivOut1_Object.nviUnvOutput1.SCPTovrValue.PV UnivOut1_Object.SCPTovrBehave.PV   9 Universal Output 2 (%) UnivOut2_Object.nviUnvOutput2.PV UnivOut2_Object.nviUnvOutput2.SCPTovrValue.PV UnivOut2_Object.SCPTovrBehave.PV   10 Universal Output 3 (%) UnivOut3_Object.nviUnvOutput3.PV UnivOut3_Object.nviUnvOutput3.SCPTovrValue.PV UnivOut3_Object.SCPTovrBehave.PV

Issue In newer versions of XBuilder, when importing I/NET sav files into the project, an attribute called "flags" is included.  In an I2V integration, this signal can be used to decode the binary flags associated with an I/NET point. Product Line TAC INET, TAC Vista Environment XBuilder 5.1.5 and later Cause In earlier versions of XBuilder, each binary flag was separated out into an individual signal.  These signals include: test manual alarm old unack alarm_ack Binding each of these values (along with value, state, and/or control) for every point displayed on a graphic could quickly cause the number of bindings to expand to a number that caused performance issues with TGML graphics.  To combat this, all of the binary flags were combined into one signal called "flags." Resolution The masking for the flags signal comes from the communications format of I/NET: 7 6 5 4 3 2 1 0 Test Alarm Alm Inh Unack Old Manual Not Used To use these in a TGML graphic, read in the flags signal to a component attribute.  Then read the value and mask off the necessary bits: test = ((flags & 128) == 128); alarm = ((flags & 64) == 64); unack = ((flags &16) == 16); old = ((flags & 😎 == 8); manual = ((flags & 4) == 4); Test, Old, and Manual can be used to append the point value with a T, O, or M, respectively to emulate an I/NET environment.  Logic will need to be written to read in the alarm and unack signals: alarm unack inhibit result false false   No alarm condition true false false Alarm is still active, but has been acknowledged true false true Input active, but no alarm condition false true   Alarm has cleared, was never acknowledged true true   Unacknowledged alarm present

Issue Is it possible to prevent a graphic page from being edited? ie. it should not be possible to change the graphic page from a remote workstation. Product Line TAC Vista Environment Vista workstation/remote workstation 5.X Cause Many sites have varying levels of operators who have access to the TAC Vista system. It may not be desirable for all of the users to be able to change graphics and other Vista objects. Resolution To lock the graphic page for one workstation you can simply log in with a user that has read-only authority. This can be set by right-clicking any TGML/OGC object in Vista and selecting "Authority". In the dialogue window that opens up select an appropriate user and add it to the "Access control List". Using the "Access Level" drop-down box, select "Read(R)".

Issue Are 64-bit operating systems compatible with Echelon's LTAs? Environment Windows 64-bit operating systems TAC Vista 5.X PCC-10 PCLTA-20 PCLTA-21 Cause 64-bit operating systems are becoming increasingly common when customers upgrades their site PCs. Resolution The PCC-10, PCLTA-20, and PCLTA-21 are not supported on any 64-bit versions of Windows. Please refer to Echelon's Software Version and Compatibility List for updates.

Issue It is only possible to remove the last I/O module in the Options > Device Specification list.  And it cannot be removed until all references to hardware I/O are also removed.  Attempts to delete it prior to this will result in: "The I/O Modules cannot be removed because it is bound to the following blocks:" If it is the second I/O module of 8 that needs to be changed to a different type, this describes the most efficient way to remove I/O references and put them back. Environment Menta Cause This warning is a precaution against leaving stranded hardware I/O points if the modules they are associated with are deleted. Resolution In Menta, go to Options > I/O Configuration Table Click the "Bound to" column header twice to sort by bindings with hardware I/O listed first In this example, remove I/O Module #8. Find all references to "M8-" Double click each output. Change the Bind to option to Not connected Double click each input. Change the Bind to option to Network Variable.  Leave the Network Address blank. Repeat these steps for the I.O module that will be replaced as well as any higher in the list. Go to Options > Device Specification Remove all I/O Modules down to the one needing to be replaced.  Add them back in in the desired configuration. Go back to Options > I/O Configuration Table Click the "Bound to" column header once to sort by bindings with Network Variables listed first Double click each converted input and output and switch them all back to Physical Input, Linear Analog Input, Non-linear Analog Input, or Physical Output, where appropriate. The physical I/O bindings are recalled when the point is changed back to physical I/O. Note:  The sensor configurations (0..10V, 2..10V, etc) will need to be set up again.

Issue A forced value from Vista Webstation does not reflect that is has been changed. A value that has been changed to read-only in Vista Workstation is still able to be forced from Vista Webstation. Environment Vista Webstation using TGML graphics Vista Workstation using read-only attributes on a value that can be forced. Cause When forcing a value in Vista Webstation, a right click will display the "forced" check box and change value field regardless if the value has an attribute of read-only.  To Webstation users, it will appear as if the ability to change any value is working.  All changes to a read-only value will be ignored by Workstation because there is not a write attribute for the User. The value in the Webstation TGML graphic will not update to reflect the desired forced change. The rejected change is never propagated back to Webstation which could give the impression that something is wrong in Vista.  Resolution If the user should be able to make a forced override of the value, modify the Read attribute to Read-Write. A solution to the issue is to grant access to the points needing changed after creating a 'User' user.  It is best in any environment to restrict all access and grant where necessary making the system less vulnerable to attacks by having a restriction not in place. If you grant access to everything for the user then restrict access, the possibility for unauthorized changes in a system are more likely.  

Issue What is the required version of .NET framework and ASP.NET for TAC Vista software? Product Line TAC Vista Environment Vista 4.x.x Vista WebApps 4.x.x Vista 5.x.x Vista WebApps 5.x.x Cause Microsoft .NET framework is a core technology used by Vista software. ASP.NET is used by Vista Webapps for web presentation through Internet Information Services. With the many versions of .NET framework available from Microsoft it can be unclear which to install or ensure is available for Vista software. A new release of .NET framework is not necessarily supported by TAC Vista software until design changes have occurred in subsequent releases. Resolution Use this compatibility chart to ensure the proper version of .NET framework and ASP.net are installed: Vista Version .NET Framework Version ASP.NET Version 4.3.0 1.1 sp1 1.1 4.3.1 1.1 sp1 1.1 4.4.0 1.1 sp1 1.1 4.4.1 1.1 sp1 1.1 4.4.2 1.1 sp1 1.1 4.5.0 1.1 sp1 1.1 5.0.0 2.0 2.0 5.0.1 2.0 2.0 5.0.2 2.0 2.0 5.0.3 2.0 2.0  5.1.0 3.0 2.0 5.1.1 3.0 2.0  5.1.2 3.0 2.0 5.1.3 3.0 2.0 5.1.4 3.0 2.0 5.1.5 4.0 4.0 Note: A higher version of installation package might be present on the computer. To confirm the presence of the lower versions also being available review the C:\Windows\Microsoft.NET\Framework\ directory. The Microsoft.NET framework is available for install from Microsoft's website (http://www.microsoft.com/net/)

Issue Most TAC Plug-ins come with the Toolpack and are installed into the correct drive and available to be registered through an LNS management tool, like LonMaker or NL220.  This article describes the steps to follow if a new plug-in has been downloaded and needs to be added to the system. Environment LNS Plug-ins Viconics Stat Plug-In Cause In order for a plug-in to be used, it must first be downloaded, installed, and registered.  But sometimes merely placing it in the correct directory will not allow for the LNS tool to register the plug-in. Resolution Download the plug-in .exe file Place the file into C:\LonWorks\Apps\TAC directory Double click the .exe file.  This brings up a dialog with options to register/unregister the new plug-in. Register the plug-in. Launch LonMaker or NL220 The plug-in should be available to be registered in the LNS management tool.

Issue Unable to connect a TGML link to a I/NET Time Schedule, Trend Configuration, Point Control, or Alarm Configuration page. Environment Xbuilder 5.x.x Cause The link of a TGML graphics page must be linked to a System pane object or URL. Resolution Use a Links Page object as an intermediary Create a new page -> Links page Set the Visible property to False. Drag the I/NET specific page on the Link of the Link Page. Drag the Link page object on to the Graphics page link.

Issue Can't log in to Vista Workstation. The following error message occurs: "An unhandled Microsoft.net Framework exception occurred in TACVistaExplorer.exe[5420]" Environment TAC Vista 5.1.5 Windows XP Cause This can be caused by the regsrv32.exe not functioning correctly. Regsrv32.exe is a Windows program task that registers programs into your system registry. This causes problems during the installation of Vista as certain parts of Vista will not be registered correctly. Resolution The following can be checked in an attempt to correct this fault: Check the %systemroot%\Windows\System32\ catalogue to see if the regsrv32.exe file exists. Check that it is spelled correctly and that the file type is .exe. After correcting these 2 points reinstall Vista.

Issue Get error message 0x80004002 when trying to access objects under an OPC server in the Vista OPC tool. It is possible to see the OPC server but get the error when accessing the object under it. Environment Vista 5.1.5 Vista OPC tool Cause For some reason some important DLLs for OPC were not registered on the client PC. Resolution Register the following DLLs: opccomn_ps.dll opc_aeps.dll opchda_ps.dll opcproxy.dll

Issue Can not access the SQL database with a Windows domain user, but it works with a local user on the computer. Environment Vista 5.x.x Cause By default, the Windows users in the administrator group on the PC have enough authority in the Vista SQL database.   Resolution Add the Windows domain user to the administrator group on the PC and it will work.

Issue How should a Echelon Lon Talk Adapter (LTA) be configured if used in a Vista classic network? Why is the network and controllers offline in Vista Classic? Environment Vista 4.x.x Vista 5.x.x Echelon LTA (PCC-10, PCLTA-20) Cause The NI application of the LonTalk adapter needs to be configured as NSI not VNI (Virtual network interface) in the LonWorks Plug n' Play which configures the LTA. Resolution Change the NI application of the LonTalk adapter. Open the Windows Control Panel Select the LonWorks Plug N' Play. Change the NI Application For a PCC-10 LTA select NSIPCC For a LTA-20 LTA select NSIPCLTA Click Apply Start Vista Server.

Issue Changes made to Device Templates in the XBuilder Device Editor for interfaces with Modbus, BACnet, etc are not seen by the controller after download. Environment XBuilder 5.x.x Xenta Server 5xx/7xx/9xx Cause Device Template files are not recognized by the device until the unit has restarted. Resolution When downloading the project to the Xenta Server select to "Send all project files".  This will force a warm start of the device causing the changed Device Template to be recognized.