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.

Issue What LonWorks data is accessible from a Xenta Server and what can the data be used for? Environment Xenta 500 Xenta 700 Xenta 900 XBuilder Cause There are different types of data accessible on a LonWorks network. TAC network variables / Public Signals - TAC proprietary communication for signals from Xenta programmable controllers SNVT - network variables available for bindings SCPT/UCPT - Configuration properties for LonWorks devices. UNVT - User defined SNVT. Data accessible from a Xenta Server can be used in Xbuilder in multiple ways: Polling - value polled for use in graphics page, values page, alarm, trending, and scheduling. Connection object - poll and send process to pass value from one device to another (could cross protocols). SNVT binding - binding from a SNVT created on the Xenta Server. Resolution Use the following table to identify which signals types are supported and how they can be used. Data type  Polling Connection Object  Binding  Public Signals  Yes 1  Yes 1  No  SNVT  Yes  Yes  Yes 2  SCPT/UCPT  No  No  No  UNVT  No  No  No 1 Xenta Server must be commissioned to have the TAC group address in its address table. Create group bindings in TAC System Plug-in for LNS networks Commission LonWorks network for Xenta Servers in Classic networks Commission and download Xenta Server acting as LonWorks unit in a LonWorks group in Classic network. 2 SNVTs must be created by Xbuilder on the Xenta Server device. These SVNTs are then bound using a network management tool such as LonMaker or NL-220.

Issue The minimum activation value for a terminal load exception mode is 14.0 and minimum reset value is 32.0. Environment Zbuilder 5.1.5-5.1.6 Xenta 121-FC Xenta 121-HP Cause In Zbuilder 5.1.5 the option to use an exception mode based on terminal mode exists (Restricted to Exception mode 7 and 8). The units for the activation and reset values are treated as temperatures. If Zbuilder is displaying values in US units then it will restrict your minimum values as 14.0 F activation, 32.0 F reset value, and the reset value must be below the activation value if using the above condition. The unit is actually using a Celsius value to store the settings and this is being converted to F. Resolution Change the configure to display values in SI and then set the activation and reset values as a 0-100% value. Then you can change the units back to US and have it convert the value automatically. Warning: Note that even though terminal load is -100% to 100% the exception mode will ignore the sign of the terminal load. Use the "Controller is in cooling mode" and "Controller is in heating mode" check boxes to restrict the behavior to a positive or negative terminal load.

Issue XBuilder project was upgraded and OGC graphic pages were converted to TGML using the automatic conversion. The same names were used for the graphic pages, but they will not display in the web interface. Java console reports: java.io.IOException: Wrong file format feature < 0 or reature > 7  at se.tac.applet.graphics.ogc.OGCStreamHeader.load(Unknown Source)  at se.tac.applet.graphics.ogc.OGCPicture.loadPicture(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.go(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.init(Unknown Source)  at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)  at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder 5.x.x Xenta Servers Xenta 511, 527, 711, 731 Cause The graphic object was properly converted, but the graphic page is still using the old template (Graphics.html) which is designed for OGC graphics instead of the new graphics page template (TgmlGraphics.html). This causes the java to interpret a TGML graphic file as an OGC graphic file. Resolution This can be resolved two ways Manually edit the Template property of the Graphic page objects in XBuilder to be TgmlGraphics.html. Delete the graphics page in XBuilder and recreate it. When the graphic object is linked to the graphics page it will properly assign the correct template based on the type of graphics file type.

Issue Can Inovonics wireless equipment be used with Xenta Servers? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Inovonics Frequency Agile product line which is compatible with the Xenta Server driver is being obsoleted by the manufacturer Inovonics at the end of 2011. Resolution If you have existing devices installed in the field then they should continue to work and function. New installations should explore other options for wireless sensors due to unavailability from the manufacturer. The ability to add a RS232 wireless Inovonics interface was removed from XBuilder beginning in version 5.1.8.

Issue Offline Xenta 401 Not Generating Alarms Environment Xenta 401 Xenta Group Cause Xenta Group Master is offline Resolution Determine if the Group Master is offline In the Vista System Plug-in TAC Network Pane, the Xenta Group Master will be the only controller in the Xenta Group that is underlined Determine if this controller is offline in LonMaker or NL220 If the group Master or any of the Xenta devices in that Xenta Group show an " * ", you will need to download application and parameters Change the Group Master to a more reliable controller Determine which controller in the Xenta group has the least amount of potential traffic In the Vista System Plug-in TAC Network Pane, Right-Click on this device and select "Set as Master". Download Application and Parameters to any device that shows and " * " after this change.

Issue Xenta Servers are producing lots of Messages that contain the text "$COS#...#MA1 All Messages start with $COS# followed by an object ID and they end with #MA1 The messages are coming, although there are no trend log values missing. Environment Tac Vista 5.1.6 or older Cause This is a bug which is fixed in Vista 5.1.7. This message - $cos - is created every time Vista tries to retrieve an alarm from a Xenta controller and fails. Vista then tries again a couple of times. If successful, this message is removed. The problem is that the acknowledgement that should remove this log entry never arrives. Resolution Upgrade to Vista 5.1.7

Issue Procedure to Change Imperial to SI units in VAV Controller in Classic Network System. Environment Xenta 102-AX VAV Controller TAC Vista (Classic) Cause In classic Network System, when trying to change the Xenta 102-AX VAV units from Imperial to SI, it is not changing. Resolution It is possible to change the Xenta 102-AX VAV units from Imperial to SI, in LNS System using the plug-in, But in Classic Network system, it requires some system settings to take the effect. Follow the below steps to change the Xenta 102-AX VAV units from Imperial to SI: Make sure that these setting are checked in the Administrator account. I some cases there may be two or more administrator accounts that require these setting checked Go to Control Panel -> Open "Regional and Language Options" -> in Standards and formats, change from English (United States) to English (United Kingdom). Note: - If the units are required in Fahrenheit set the English language to United States. - If the units are required in Degree Celsius set the English language to United Kingdom.   Change the Location to your local region.   Go to Advanced TAB -> change from English (United States) to English (United Kingdom). Note: - If the units are required in Fahrenheit set the English language to United States. - If the units are required in Degree Celsius set the English language to United Kingdom.   Click on "Apply all Settings to the current user account and to the default user profile".   Click on "Apply" and then click on "OK".   Re-Start the Computer.   After the computer has restarted, open the TAC Vista Server and Work Station. Then Right Click on "VAV Controller", go to its properties, and reload the XIF file, then press "OK".   Commission and Download.   It should now be possible to change the units of the device.

Issue Is it possible to access the Pelco Video Server through TAC Vista Webstation Environment TAC Vista Webstation Pelco Video Server (Digital Sentry) Cause The Pelco Video Server can not be accessed through TAC Vista Webstation. Resolution No, It is not possible to access the Pelco Video Server through TAC Vista Webstation. It is only possible to access Pelco video viewers through TAC Vista Workstation. In TAC Vista Workstation activates a special program which allows viewing of this video. Note: TAC Vista supports only for Pelco - Integral Digital Sentry Video System.

Issue Is it possible to determine if a TGML graphic is being run in Workstation or Webstation? Environment TGML Graphics Editor 1.1.X Vista 5.1.X Workstation TacWebApps 5.1.X (Webstation) Cause There are differences in the rendering of graphics between Workstation and Webstation. Sometimes this leads to the necessity of creating two sets of components depending on where the graphics will be presented. By being able to programmatically determine the environment, one set of components can be used regardless of the presentation, reducing engineering time. Resolution The results of the JavaScript function Packages.java.lang.System.getProperty can determine whether the viewer is currently in Vista Workstation or not.    Note: This is not a supported function in TGML. Because it is unsupported, it is subject to change without notification, and should be used accordingly at your own risk.   Create a document-level script tag that runs OnDocumentLoad. Determine the current Vista version (and keep potential future upgrades in mind as well). The implementation of the property changed in an upgrade from Vista 5.1.4 to Vista 5.1.5. If the system is Vista version 5.1.4 and prior, use the following function: if (Packages.java.lang.System.getProperty("browser") == "ActiveX Scripting Host") If the statement is true, then the graphic is being run in Workstation. If the system is Vista version 5.1.5 and later, use the following function if (Packages.java.lang.System.getProperty("java.runtime.name") == "IKVM.NET") If the statement is true, then the graphic is being run in Workstation. The following script can be run for any version of Vista 5. /*   returns what browser Tgml is viewed in (Workstation==false,Webstation/Webserver==true)  */ var getBrowserType = function() {    var browser = false; // initiates browser indication variable as Webstation/Webserver  if (Packages.java.lang.System.getProperty("browser") != null) { // checks Vista version   // evaluated for Vista is 5.1.4 or earlier   if (Packages.java.lang.System.getProperty("browser") == "ActiveX Scripting Host") {       browser = false;   // indicates variable as Workstation   } else {      browser = true;    // indicates variable as Webstation/Webserver     }  } else {   // evaluated for Vista 5.1.5 or later   if (Packages.java.lang.System.getProperty("java.runtime.name") == "IKVM.NET") {    browser = false;   // indicates variable as Workstation   } else {    browser = true;    // indicates variable as Webstation/Webserver   }  }   return browser;     // returns browser indication } 

Issue Zbuilder will not launch from LonMaker on Windows Vista. If running LonMaker in elevated mode or with User Access Control disabled then trying to launch Zbuilder will result in an error: Unhandled exception thrown. Message: Object reference not set to an instance of an object. StackTrace: at TAC.Xenta100ConfigTool.Framework.LNS.LnsNetworkManager.OpenNetworkAndSystem(String network) at TAC.Xenta100ConfigTool.Framework.LNS.LnsNetwork.InitLNSPlugIn(String objectPath, String mode, String networkInterfaceName) at TAC.Xenta100ConfigTool.Program.RunAsLnsPlugIn(Assembly frameworkAssembly, String[] args) at TAC.Xenta100ConfigTool.Program.Main(String[] args) Environment LonMaker 3.2 Vista 5.1.0, 5.1.1, 5.1.2 Windows Vista Cause When the Vista Toolpack 5.1.0 was developed, LonMaker did not support Windows Vista limiting the ability to test for compatibility and all problems. As a result this problem is only experienced when launching Zbuilder from LonMaker. Resolution Upgrade the TAC Toolpack to version 5.1.3 or higher. If Vista Server is being used as well then ensure that the Toolpack and Vista Server versions are still the same revision.

Issue Dehumidification using Xenta 121-FC Environment Xenta 121-FC Xenta 121-HP Cause Some aspects of how the dehumidification mode in the Xenta-121 operate are undocumented. Resolution The dehumidification feature of the Xenta 121 can operate either by turning on external dehumidification equipment using one of the digital outputs or, if no external equipment is provided, it will use the cooling for dehumidification. In the latter scenario, the heat continues to be operational when the cooling is forced for dehumidification. Additionally, if there is an outside air damper, it will be controlled to its minimum position before forcing the cooling on. When is external dehumidification enabled? For On/off cooling, cooling is enabled for dehumidification when the nvoDehumidActive value is greater than 10% and is disabled when the nvoDehumidActive value drops below 5%. For all other types of cooling, nvoCoolPrimary is set to match the nvoDehumidActive whenever it is a greater than cooling PID output + 5% or whenever the cooling PID output is less than 5%. The dehumidification feature can be configured using the ZBuilder configuration tool. However, the individual features can also be accessed via the points listed below using either Vista Workstation or another Lon management tool such as LonMaker: Applic UCPTappOptions Bit Usage If FALSE If TRUE Additional notes 5 Dehumidification control enable Not active Active   6 Dehumidification type Internal External Only applicable if bit 5 = true. External control can be hardwired or via SNVT. Internal will force cooling as a dehumidification method. 7 External dehumidification active on Open contact Closed contact Only applicable if bits 5 and 6 are both true. UCPTappOptions2 Bit Usage If FALSE If TRUE Additional notes 7 External dehumidification type Digital Analog If true then the RH reading is mirrored to the analog output (0-100% = 0-10V). Only applicable if UCPTappOptions bits 5 and 6 are both true.

Issue Xenta Group and Xenta Programmable Device specifications for an LNS system Network communication errors Environment Vista NL220 LonMaker Vista System Plug-in Cause Improper configuration of Xenta Programmable controllers will result in poor network performance Resolution Design Each LNS database within the following limits A maximum of 400 Xenta Programmable devices A maximum of 30 Xenta Groups A maximum of 30 devices with-in each Xenta Group Xenta groups should not have members separated by a router