Issue DDE won't work when running Vista as a service Environment Windows 2008 Server or Windows 7 Vista server communication with a device or application via DDE (Dynamic Data Exchange) Cause Applications and services no longer run under the same session in Windows 2008 server or Windows 7. Resolution Run Vista as an application.

Issue Xenta 913 is locked up randomly, and it needs reboot to make it return to work. When referring to the error log on the web page, the following errors show up: event power PowerFail 1 System is safely shutdown (Error#:49154) event power InitSYS 1 System start - power on (WARMSTART) (Error#:49156) Environment Xenta 913 BACnet Cause Possible cause is the baud rate for BACnet communication is too high that Xenta 913 can't deal with it properly. Resolution It is recommended to decrease baud rate for BACnet communication to 9600 or 19200 bps, and then Xenta 913 should work fine now.

Issue How many LON Bus Coupling Unit MTN880451 and LON Multi-Sensor LA-21 MTN880541 could be supplied by the Power Supply MTN884019? Environment Schneider Electric Lighting Cause Both MTN880451 as well as MTN880541 has a power consumption about 285 mW, that gives about 7 mA. The power supply MTN884019 could give 1.3 A used with 230 Volt or 1 A used by 115 Volt, so it is more than the number of devices you could have on a segment that are important.   Resolution Both MTN880451 as well as MTN880541 has a power consumption about 285 mW, that gives about 7 mA. The power supply MTN884019 could give 1.3 A used with 230 Volt or 1 A used by 115 Volt, so it is more than the number of devices you could have on a segment that are important. If you use LinkPower, you theoretical have up to 128 devices, but if you also have FTT devices, these should be counted twice, so 20 LPT and 15 FTT devices should be counted as 50. It is a recommendation to stay below 64 devices on one segment.  

Issue Can't receive "Power Factor" values from ABB's M-bus meters. Environment Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Cause Earlier versions of X700/ X913 system software did not support M-bus manufacturer specific data that contains extra status information in the VIFE Resolution For Xenta 700, there is a hotfix for v5.1.8 that adds support for this type (also included in v5.1.9 and later) . For Xenta 913, v5.1.9 and later includes this hotfix.

Issue Sending nvoSpaceTemp to nviSpaceTemp in TAC Xenta 102-AX does not work even if we are using SCPTmaxSendTime and SCPTmaxrcvTime. Environment TAC Xenta 102-AX Cause SCPTmaxSendTime of 60 means that the value is sent at least once every 60 second. SCPTminSendTime of 10 means that you could not send more often than once every 10th second. But, SCPTmaxRcvTime of 10 means that if the device has not got a new update within 10 seconds of the latest value, the value goes back to default value.   Resolution SCPTmaxRcvTime in the receiver has to be set to at least longer than the SCPTmaxSendTime in the sender, to avoid timing issues, there the receiver resets its value before the sender sends out a new value.  

Issue When installing SQL server 2008 or SQL 2008 R2 to manually an instance for I/NET, Vista or Continuum, sometimes an error "Invoke or BeginInvoke cannot be called on a control until the window handle has been created" will show up. Environment SQL 2008 / SQL 2008 R2 Vista I/NET Continuum SmartStruxure Cause This issue is happening because of a behavior change in .NET that is exposing an issue with SQL Setup User Interface (UI). Resolution Generally, if you just rerun the installer, it won't hit the issue again. If this can't help, just manually create a C:\temp folder and it will work fine.

Issue When importing a file from TAC Menta into StruxureWare Building Operation Functional Block Editor, the import of the application file fails. Environment TAC Vista TAC Xenta StruxureWare Building Operation Cause The following characters are not allowed in object names in StruxureWare Building Operation. • / • " • ? • * • ~ • White space is not allowed in the beginning or the end of an objects name. • . (period) is not allowed in the beginning of an objects name. Colon (:) is not allowed either, but will automatically be replace by an underscore (_) when importing   In TAC Vista, signal names could contain the character "/". In SmartStruxure, this character is not allowed. Resolution Remove illegal characters from object names in the Function Block program.

Issue When using STR150 connected to a TAC Xenta 121-FC, the Occupancy Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC, which is the only analog output on the TAC Xenta 121-FC device. Environment TAC Xenta 121-FC STR150 Cause When using a STR150 connected to a TAC Xenta 121-FC, the Occupancy Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC device, which is the only analog output on the TAC Xenta 121-FC device. Resolution In ZBuilder, it is possible to move the Occupancy Mode indication from the default location at Y1 to K1-4. In this case you also need to have an external power supply with 5 Volt DC for the Occupancy Mode indicator.

Issue The configuration in "License Setup" changes autonomously meaning that you open "License Setup", make a change, close "License Setup", open "License Setup" and the configuration has reverted to what is was before the change was made. It reverts back to what it was before making the change. Environment TAC Vista 5.1.9 Cause The cause of this is unknown. TAC Vista Server is supposed to set some values in the registry while running also regarding licensing, but not like described here. Resolution Make sure TAC Vista Server is stopped while changing the license setup: Stop TAC Vista Server Change the license setup Start TAC Vista Server

Issue Schneider Electric MTN881001 or the SVEA LON I/O Module DR-N 3DIM 1-10V. Changing the SNVT nviLALampValue_? does not give the expected output. Environment MTN881001 SVEA 36237-552 Cause Changing the SNVT nviLALampValue[i] to the following values, shows the following VDC volt on the analog output: nviLALampValue Analog output 100.0 1 -  9,94 VDC 80.0 1 -  7.65 VDC 60.0 1 -  6,75 VDC 50.0 1 -  6.25 VDC 20.0 1 -  4.86 VDC 1.0 1 -  3.97 VDC When nviLALampValue is 50.0 1, the analog output is 6.25 VDC (not proportional) and the minimum analog output value is 3.97 VDC, which does not make sense.   Resolution The module is using a logarithmic behaviour for the 1-10V output as default. This is because the device is mostly used for fluorescent lamps. You can change the behaviour by using the UCPTadaptationTable in the lamp Actuator object. UCPTadaptationTable consists of 21 values representing the digits (from 0 to 255) for the output value in steps of 5%. This means:   first value: 0% second value: 5% third value: 10% ... 21st value: 100% To get a linear behaviour you should set as follows: first value: 0 second value: 13 third value: 26 ... 21st value: 255

Issue After upgrading a TAC Vista system on a site with high IT security you can end up with a wrong schema version in the SQL database causing issues such as failure to insert trend log data. Environment TAC Vista SQL Cause In some versions of TAC Vista, the SQL database upgrade carried out during the installation of TAC Vista doesn't upgrade the SQL database to the newest version. The first time you start TAC Vista Server, the server (TACOS) carries out the remaining upgrade steps. On a site with very high security standards, TAC Vista Server is however not able to apply the last SQL database upgrade scripts as those can only be carried out by the IT department directly on the SQL server, and as a result the SQL database is not fully upgraded. Resolution   1.      Note exactly what schema version the SQL database currently has This can be checked through SQL management studio with this query USE taclogdata; SELECT dbo.DSS_SchemaVersion() AS Db_SchemaVersion 2.      Note exactly what version of TAC Vista you have upgraded to 3.      Contact PSS to get a SQL upgrade script specific for the site and run that on the SQL database

Issue Do not get any values in webstation Bindings in TGML do not work Environment Vista Cyrillic Cause If bindings in TGML contain Cyrillic characters and the operating system installed is set to a language that can not handle Cyrillic (i.e English), the bindings will not show their values. Resolution Set the region and language settings all to the desired language, i.e Russian or Polish. Be sure Webstation is set to handle the language by installing the correct language pack. Edit the TGML and make a small change so you can save again, this time the Cyrillic letters will be understood by Tacos.

Issue The SNVT bindings break after replacing a VT6700 Viconic thermostat with a VT7600r, VR76_PIR, SE7600, etc. Environment LonMaker NL220 Schneider Electric SE76XX stats Cause The older VT7600 Viconic thermostat includes the nvoOAT SNVT. On the newer models of the Viconic stats the nvoOAT variable is no longer available. The removal of the nvoOAT variable causes the SNVT table to become unaligned and breaks the existing bindings that had been created. Resolution When replacing a VT7600 thermostat with any new Viconics model the existing SNVT bindings will be broken. It is important to make note of all bindings made to the stat before performing a replace with a newer stat.

Issue What type of sensor element is used in the STR300? Environment STR300 Cause The HVAC European+Sensors+Catalogue.pdf on the Extranet, as well as the datasheet for the STR300 Series says that the sensor element is PT100 Class B. Resolution The actual sensor element for the STR300 that are made today is NTC Thermistor 10 kOhm. The output from the STR300 is 4-20 mA.   The documentation will be updated shortly.

Issue Could the L-VIS screen be manage even if the operator is using latex gloves? Environment Loytec L-VIS Cause The screen used on Loytec L-VIS is resistive, and due to that can be managed with latex gloves. Resolution The screen used on Loytec L-VIS is of resistive type, and due to that can be managed with latex gloves.

Issue Trend log values from two or more M-bus meters under a Xenta Server are intermittently mixed up, also when viewing a trend log page in the Xenta Server's web interface. Values from meter 1 are (sometimes) logged in meter 2's trend log and/or vice versa. Environment Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 M-bus meter Cause When secondary addressing is used for the meters, there is an extra telegram sent from the Xenta Server before asking for the actual values/data. The M-bus meters then replies to this telegram so that the Xenta Server knows which secondary address belongs to which meter. In some cases (only seen with a few meters) these addresses seems to be intermittently mixed up and this will cause the issue described above.  Resolution Use primary addressing for the M-bus meters.

Issue Manually add individual components to a Component Library Environment TGML Graphics Editor Cause Components are sometimes stored as a file type TGMLCOMPONENT File with the extension .tgmlcomponent file. Resolution Open the Graphics Editor and Select a Component Category you wish to add components to Open Windows Explorer and browse to the .tgmlcomponent files. Drag the file(s) from Windows Explorer to the the TGML Graphics Editor Component Category window. Click OK or press enter to acknowledge each file as it is added.

Issue When using the SmartStruxure Interface, is it necessary to configure any DCOM or firewall settings to run TAC Vista and SmartStruxure on different computers? What protocol is used for communication between the SmartStruxure interface for TAC Vista and the ES? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista server TAC Vista SmartStruxure Interface SmartStruxure Enterprise Server (ES) Cause Communication issues between interface and SBO Resolution Only HTTP/HTTPS are used. You can configure the interface to use only one of the protocols. You can also configure what ports to use.

Issue Is it possible to use the TAC Xenta 110-D device with room unit STR150? Environment STR150 TAC Xenta 110-D Cause It is not possible to use STR150 together with the TAC Xenta 110-D device. Resolution TAC Xenta 110-D does not support STR150.

Issue Values in graphics from Xenta and Lon devices under a Xenta 911 network are not updated. Some values show database values and some values are showed with red crosses. When clicking on the value in the graphic the value is shown correct.  Environment TAC Vista 5.9 with a Xenta 911 as Lon network interface. Cause This could happen if many Lon and Xenta devices under the Xenta 911 is offline. When Vista do a online poll for a Xenta or Lon device and don't get a reply the communication will be halted for 3 seconds because of retransmission and time outs. This would not be a problem if a Loytec interface was used as it can handle more then one communication thread at the time but the Xenta 911 only use one communication thread. In this case it is possible to see the correct value when clicking on it in the graphic as that is a user command with much higher priority than updating values in a graphic have. Resolution Try to minimize the number of offline devices which reside under a Xenta 911 network in the Vista database as these devices will slow down the communication on the Lon network.