Issue TAC Menta could give mainloop overrun then having an application with many Alarm blocks and more than one ERR block. Environment TAC Xenta 280/300/401 TAC Menta Cause When the ERR block is executed, it goes through all Alarm blocks to check status, having more than one ERR block makes this loop to be run more than once. Resolution There sould be a maximum of one ERR block per application.

Issue The customer wants to have a binding and transfer a value, but also wants to have backup set on the receiving variable in the TAC Xenta device. Environment TAC Vista TAC Xenta 280/300/401 Cause Setting the Backup flag will make the variable be written into the flash memory every time the value is written. Doing this on a value that is regularly transferred will damage the flash memory, as it has to write all the time. Resolution The Backup flag should not be set on variables that are written to on a regular basis.

Issue On a Windows 2003 Server or Windows XP, TAC Vista is not able to locate the license server, even though everything seems to be set up correctly. You get the message "-15, 10 System Error: 10061 Winsock Connection Refused" when you try to open any TAC Vista software. Environment TAC Vista Flexnet license Windows 2003 Windows XP Cause The TAC Vista software is looking for the license server on the PC defined, but the license server is running using the TCP/IP v6 address and the software doesn't support that on this operating system. Resolution Uninstall TCP/IP version 6 and reboot the PC. Below is a description on how to do it.   For the IPv6 protocol for Windows XP with SP1 or later or Windows Server 2003, do the following: Log on to the computer with a user account that has privileges to change network configuration. Click Start, click Control Panel, and then double-click Network Connections. Right-click any local area connection, and then click Properties. Click Microsoft TCP/IP version 6 (for Windows XP with SP2 or later or Windows Server 2003) or Microsoft IPv6 Developer Edition (for Windows XP with SP1), and then click Uninstall. When prompted to confirm the removal of the Microsoft IPv6 Developer Edition or Microsoft TCP/IP version 6 protocol, click OK. Alternately, from the Windows XP or Windows Server 2003 desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt. At the command prompt, type netsh interface ipv6 uninstall. To remove the IPv6 protocol for Windows XP with no service packs installed, do the following: Log on to the computer with a user account that has local administrator privileges. From the Windows XP desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt. At the command prompt, type ipv6 uninstall.

Issue When editing a TGML error A generic error occurred in GDI+ appears Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista StruxureWare Building Operation TGML Graphic editor Cause This issue occurs after you install security update 3045171. You experience a crash when you use Windows GDI+ to create text outline-based path objects on a computer that is running Windows 7 Service Pack 1 (SP1) or an earlier version of Windows. Resolution Download the patch below from Microsoft https://support.microsoft.com/en-us/kb/3065979 It has been noted that this patch do not solves all the issues, if you still have issues with other applications uninstall the security update KB3045171.

Issue Selection and installation of a pulsed output module. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, TAC Vista Environment Heat Meter Multical 602 Pulsed output module No pulses Cause Installed card does not give output pulses. Resolution Selection of the output card. The Schneider Electric part number is MAPULSETOPC and this is the equivalent to Kamstrup part number 602-0C This card will provide 2 pulse outputs for energy and volume, CE and CV respectively. Normally, energy (CE) is connected to 16-17 and volume (CV) to 18-19, but other combinations can be selected via the PC program METERTOOL, also used to select pulse duration 32 or 100 ms. The MAPULSETOPC is actually a top module, which means that it is fitted into the top piece of the MC602 calculator, basically the inside LCD cover. This is released by pressing downwards in the middle of the plastic piece on the left, and at the same time pushing the top module towards the left.

Issue In the TAC Xenta 151-D, the nvoAlarmStatus handles the test of the dampers, but the translation of the status is not documented Environment TAC Xenta 151-D Cause nvoAlarmStatusis used to report the actual status of the fire damper tests. Resolution nvoAlarmStatus is a SNVT_state with the use of the following bits: nvoAlarmStatus.bit0 = 1   OBJECT1_CLOSE_TIME_TOO_LONG    nvoAlarmStatus.bit1 = 1   OBJECT1_CLOSE_TIME_TOO_SHORT   nvoAlarmStatus.bit2 = 1   OBJECT1_OPEN_TIME_TOO_LONG     nvoAlarmStatus.bit3 = 1   OBJECT1_OPEN_TIME_TOO_SHORT    nvoAlarmStatus.bit4 = 1   OBJECT2_CLOSE_TIME_TOO_LONG    nvoAlarmStatus.bit5 = 1   OBJECT2_CLOSE_TIME_TOO_SHORT   nvoAlarmStatus.bit6 = 1   OBJECT2_OPEN_TIME_TOO_LONG     nvoAlarmStatus.bit7 = 1   OBJECT2_OPEN_TIME_TOO_SHORT    nvoAlarmStatus.bit8 = 1   OBJECT1_SET_CLOSE_TIME_FAILED nvoAlarmStatus.bit9 = 1   OBJECT1_SET_SELFTEST_OK        nvoAlarmStatus.bit10 = 1  OBJECT1_SET_SELFTEST_FAILED    nvoAlarmStatus.bit11 = 1  OBJECT2_SET_CLOSE_TIME_FAILED nvoAlarmStatus.bit12 = 1  OBJECT2_SET_SELFTEST_OK        nvoAlarmStatus.bit13 = 1  OBJECT2_SET_SELFTEST_FAILED     

Issue It is desired to configure a minimum off time, so when the compressor stops in e.g. heating mode, it will not start again before a minimum time has elapsed in the same mode. This setting is not available in the device. Environment TAC Xenta 121-HP Cause There is no setting for minimum stop time when in the same mode, there is only a minimum stop time between modes. Resolution As a workaround, set the "Activate at" value to something other than zero (say 10%), so that you can use the "Hysteresis" at 10%, and this way get a delay. This way you will get a delay in the most cases, a little time before the controller reacts.

Issue Why isn't the OpenLNS a full, un-limited license? Environment OpenLNS OpenLNS CT Cause Renewing OpenLNS CT Annual Maintenance You can renew your annual maintenance for OpenLNS Server and OpenLNS CT before they expire. Renewing your OpenLNS and OpenLNS CT annual maintenance enables you to continue installing software updates and upgrades. If you do not renew the products’ maintenance, you can still use the products; however, you will not be able to upgrade it with updates or upgrades released after your annual maintenance expired. You cannot renew your annual maintenance after it has expired. Once it has expired, you must purchase a new activation key to be able to install any updates or upgrades released after your maintenance expired. To renew your annual maintenance, purchase an OpenLNS Commissioning Tool Professional One-Year Maintenance Renewal (Echelon model number 93800) or an OpenLNS Commissioning Tool Standard One-Year Maintenance Renewal (Echelon model number 93810). Echelon will process your order, and your maintenance coverage will be extended so that you can continue updating and upgrading OpenLNS and OpenLNS CT for an additional year. Resolution If paying the annual maintenance fee, you have access to updates and upgrades. Not paying still means that the program could be used, however it could not be updated with the latest patches.

Issue TAC Xenta I/O modules that are added as LonWorks units in TAC Vista, are converted to Xenta I/O modules belonging to a Xenta Base unit (SlaveSpeak devices) in EcoStruxure Building Operation, after conversion using TAC Vista Conversion Tool. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista Server TAC Vista Conversion tool Xenta Xenta I/O-modules Cause In TAC Vista, the Xenta I/O modules are normally located on the same subnet as the Xenta Base unit, and belong to the Xenta Base unit, communicating as SlaveSpeak devices. If a Xenta I/O module is located on another subnet than the Xenta base unit, it could instead be added as a LonWorks Unit in Vista, and therefore communicating via LonWorks bindings to the Xenta base unit using SNVTs. Vista Conversion Tool does not handle this configuration. In the conversion tool, all Xenta I/O modules are expected to be connected directly to a Xenta base unit, located on the same Subnet, and are therefore always treated as SlaveSpeak devices. Resolution After running the Vista Conversion tool, you have to re-build the LonWorks Bindings between the Xenta I/O module and the Xenta Base unit manually in EBO, as the Conversion Tool does not handle the actual configuration setup.