Issue What values are saved when you restart a Xenta 121 Power fail Xenta 121 Environment Xenta 121-FC Xenta 121-HP Cause What information is kept when a Xenta 121 is restarted. Resolution All configuration parameters (nci). will be kept. All nvi/nvo will go back to their initial or calculated values.

Issue Add a receiver group to a Xenta server alarm in Xbuilder Environment TAC Xbuilder Cause Easiest way to add a alarm receiver group to an alarm. So that an e-mail is sent when the alarm is triggered Resolution Drag and drop the alarm receiver object on top of the alarm.

Issue Unable to associate TGML files with TGML editor after installing Vista. After right-clicking on the TGML file and selecting "Open With" it is not possible to browse in the graphics editor's .exe file. The file can be located but it doesn't appear in the dialogue. Environment Vista 5.1.X Windows 7 Cause The TGML editor application hasn't been correctly registered. Resolution Try the following steps. Check between each step to see if it's possible to associate the TGML editor with TGML files. Reinstall Vista using "Run as administrator" In regedit: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TAC\TAC Graphics Editor\5.1.8 ( HKEY_LOCAL_MACHINE\SOFTWARE\TAC\TAC Graphics Editor\5.1.8 on 32bit PCs) Check that the path given is correct under "ExecutablePath" Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.tgml and delete .tgml Reinstall Vista as an administrator

Issue Periodic Report is not printed. Environment TAC Vista 5.1.7 Cause If the box "Automatically set printing area" is checked in the properties for the report, the report is not printed. If it is left unchecked, the report will print. Resolution Uncheck the box "Automatically set printing area" in the properties for the report .

Issue Need to generate a list of all alarms in the system. Environment Vista Cause Vista has a search function to find out what alarm objects exist in the system. Resolution To search for all the alarm object in the system: In Workstation, click on Search Go to Type of devices and objects and click on the button right of view Search for "Event"  and then "Message" mark "Alarm" and click ok All objects are now listed and can be copied and pasted to an Excel sheet.

Issue What is the control signal to the actuator for a Xenta 102B? Environment Xenta 102B Cause The 102B is designed to be used with a Belimo actuator. This is why the out signal is not specified anywhere in the documentation.   Resolution The out control signal to the actuator is 0-10V.  

Issue When "Enforce acknowledge response with signature" is marked in the alarm control object the user should have to write in a cause and action when an alarm is acknowledged. This does not happen. Environment TAC Vista 5.1.8 Cause In the alarm control object, if you mark booth: "Enforce acknowledge response" and "Enforce acknowledge response with signature" It will work but if only "Enforce acknowledge response with signature" is marked it does not work.   Resolution If "Enforce acknowledge response with signature" should be used mark also "Enforce acknowledge response" in the alarm control object.  

Issue Restrict the number of login attempts for a Vista user. Environment Vista Workstation Cause Vista does not have a settings for login attempts. This is normally controlled by Windows and the Windows Domain. Resolution Create a Vista domain user. It is good practice to always log out of Windows when done. The IT department will typically have a set of rules for the domain. One of these will usually set the domain user to 3 login attempts to Windows before the account is locked.

Issue Gesytec drivers have been installed and the Gesytec device appears in Device Manager.  However there is no indication on what to call the device when entering the properties for the Lonworks Communication Port in Vista and the usual 'LON1' produces the message 'non-existent physical object'. Environment Vista Lonworks Cause When the Gesytec drivers are installed, the device adapter is not given a default name.  Vista requires a name to bind the adapter to a logical communication port object.  Resolution In Device Manager find the Gesytec device and select Properties. On the Advanced tab select the 'Lon Adapter' property and give it a Value of 'LON1' from the drop down list (if this is the first LON interface on the PC). Close Device Manager. Restart Vista Server and Workstation. In the properties for the Communication port, enter 'LON1' in the Network Interface field

Issue The time in a Xenta controller is 1 hour ahead of the Xenta server even though they are all in the same timezone and have the same daylight time settings. Environment Vista 5.xx Cause A PVR object name XENTASYSREG is in the Menta application with a value of 2. This inverts Europe daylight setting and causes the controller to adjust its time. With the adjustment of daylight times recently different countries now follow different daylight start and stop times. The updates are implemented by windows for the Vista server but the Xenta controllers still have the old times. Resolution Change the value of the XENTASYSREG to 0 and power cycle the Xenta controllers. Use the Central daylight setting object in Vista to set the Xenta summer time settings to the correct dates.

Issue Is the TAC228R controller still available? Environment TAC228R 2281084000 Cause Availability of old controller Resolution The TAC228R was withdrawn in 2011 and is no longer available for ordering for new projects. It will still be available as a spare part until 2021-12-31 when it will be terminated. A suitable alternative is the SE8300 series of room controllers. The TAC228R had the ability of a remote setpoint using a 0-10V signal, by using lua script and utilizing the input UI23, the same operation can be achieved.

Issue What is included when the PIR option is ordered? Environment SE7300 series controllers Cause The SE7300 series controllers can be ordered both with and without the PIR option Resolution If the PIR sensor functionality is ordered as included from factory, code 55 (example: SE7600A5545E) should be used. If PIR functionality is not required, code 50 (example: SE7600A5045E) should be used. PIR functionality can be retrofit at any time. For details and part numbers, please see related documentation.

Issue Failed to initialize view, access denied or type mismatch when logging in to workstation with some users. Environment TAC Vista Cause When you log in to TAC Vista workstation a default alarmview is always opened (if you are using user profiles you can specify other alarm views. All users that are using the default alarm view have to have at least read rights to $AlarmColumns, $AlarmView and $DisabledView Resolution Log in with a system user Right click on the $AlarmColumns and select authority. If everyone is not in the access control list with at least read rights drag everyone from the Group/users list. Repeat for $AlarmView and $DisabledAlarms

Issue Wrong XIF is used for device when updating from system plug-in. SNVTs are there but not the SCPS XIF has a name like TACCab6.xif instead of the real name if you look in the XIF tab in the device properties Environment TAC Vista System plug-in Cause This happens when the system plug-in can't find the XIF file in the directory it was when the device was created. Then the system plug in creates a XIF from the information it can get from LNS. If the device was created using a template then the path is C:\lonworks\import, you can see the path by clicking on the device in the LNS network pane in the system plug-in This is typical if you have moved the LonMaker database to a different PC that does not have  plug ins installed. Resolution There are two different steps you can take to try to correct this issue. Delete the device in TAC Vista, install the plug in (or copy the XIF to the correct location) and update from the system plug-in again. Manually browse in the correct XIF file into TAC Vista workstation under the XIF tab in properties of the controller. Sometimes this must be done twice in order to bring in all configuration points and SNVTs. Once the XIF is in the right place any new device added will get the right XIF

Issue Modbus TCP/IP Server is not an option when programming a Modbus Gateway in an Xenta Server. Environment Xenta 913 Xenta 7xx XBuilder Cause There are only 3 Modbus Interface configurations for Modbus in an Xenta Server. Modbus RTU Client ("Master"), Modbus serial line master on a network Server ("Slave"), Modbus serial line slave on a network Modbus TCP Client ("Master"), Modbus TCP client to a server or router on a network Modbus TCP Server is not possible. Resolution Modbus TCP/IP can only be configured to be a Client (Master) in an Xenta Server. A solution if TCP Server is absolutely necessary would be to use an IP to 485 converter, such as an EGX100, and use the RTU interface.

Issue Calibration requirement? Environment STD300: 006920121 STD300-300 -50/50 006920141 STD300-300 0/100 Cause Some sensors on the market requires calibration when connected to the controller, in order to function properly. Resolution No calibration is required when connecting the STD300 to a Xenta controller. The sensor is using a 4-20mA output signal, so the controller needs to be configured for this type of signal in order to work with this sensor.

Issue What is the BACnet address and BACnet object ID for the Xenta 913? Environment TAC Xenta 913 Cause The Xenta 913 does not have those features since it's not a BACnet device. Resolution The Xenta 913 is a gateway that translates the BACnet objects so that they can be read by for example Lonworks devices. It is not a native BACnet device itself, hence it doesn't have a BACnet address or a BACnet object ID.  

Issue Is it possible to monitor TAC Vista 5.1.x active alarms in some third party system? Environment TAC Vista 5.1.x Cause The alarms in Vista is saved in a text file in the Vista database. But reading this file is not a good way for a third party system to get the active alarms. A better way is to use OPC. Resolution Install the Vista OPC server and use a OPC client to get the alarms from Vista in to a third party system.

Issue Xenta 301XT/N/P is not available Environment Vista Xenta Cause Xenta 301XT/N/P is a Xenta unit made for the US market where some facilities needed some extra range of temperature. The XT stands for Extended Temperature. Resolution This unit is obsolete now and can no longer be ordered.

Issue Is there a limitation in number of lines in the TGML editor when running in source mode? Product Line TAC Vista Environment Vista 5.1.8 TGML editor 5.1.8 Cause When a graphic is opened in the editor and Source mode is chosen it is possible to see the source code for the graphic and the number of lines in the source code. Resolution There is no known limitation on number of lines for a TGML graphic.