Building Automation Knowledge Base

Issue Opening java or TGML graphics is very slow or they don't open at all. You may also have various java error popups. Environment TGML Graphics Cause The Java applet is limited to the amount of memory it is allowed to use. This will also limit how much memory java or TGML graphics are allowed to use, and can slow the rendering. Resolution It is possible to expand the amount of memory the Java applet has access to, and that seems to help in some cases. To increase this memory, do the following: Open the Control Panel in Windows and double click on "Java" Click the tab "Java" In "Java Applet Runtime Settings", choose "View" Find the most recent Java version runtime line (1.6.0_11) and double click on the "Java Runtime Parameters" box and add "-Xmx300m". This sets the Java maximum heap size to 300 MB. For some unknown reason, some computers with large amounts of installed memory are limited to how much memory they can assign to their Java VM. If you experience problems, just reduce the "300" to some smaller number (like 250, 200, 150, etc). However some computers have no problems setting the value to "1000". This procedure must be done to each computer individually. Also, remember to close all Internet Explorer windows for the changes to take affect.

Issue Time schedule in Menta on Xenta 731 using a Central Time Chart not becoming active. Environment Xenta 731 Menta TSCHI Central Time Chart Cause Even though a Central Time schedule on the server level can be created with an event that spans 2 days (23:00 to 01:00), the TSCHI block in Menta does not process the day change and will not activate the schedule. Resolution The Java schedule does not allow creation of these schedules. 2 separate events would be required to work across 2 days (should you need a schedule to be active across midnight). For example, running a schedule from 6pm to 2am you would need 2 separate events: one from 6pm (18:00) to 12-midnight (00:00) and one from 12-midnight(00:00) to 2am (02:00).

Issue When filtering, column sorting or column selecting is made inside an Alarm or Event Viewer, the changes are not saved when the viewer is closed. Environment Vista Workstation Cause Changes made to the current view are considered temporary. Only changes made to the properties of the Alarm or Event Viewer are stored permanently in the database. Resolution To make your changes persistent, do the filtering, column sorting or column selecting by right clicking the Alarm or Event viewer object and select properties.

Issue Updating the Loytec NIC driver Environment NIC852 NIC-USB Cause You can run into trouble upgrading the Loytec NIC driver on a PC where there is already an existing TAC Vista installation. If you do the update like this, you should stay clear. Resolution Stop TAC Vista Server, and if it's running as a service, set it to disabled. Unplug the NIC-USB or NIC852. Uninstall the NIC driver. Delete the folder %ProgramFiles%\Loytec\NIC Delete the HKLM\SOFTWARE\LOYTEC folder in the registry Reboot the PC Install the new Loytec driver Reboot the PC Insert the NIC-USB or NIC852 Start TAC Vista server

Issue When setting "Notification on change" on a Xenta Server in Vista, nothing seems to happen. There is no reduction in the traffic. Environment XBuilder Confirmed in Vista version 5.1.1 Cause If you have a space in the XBuilder project name (see Project > Settings) "Notification on change" does not work. Resolution In XBuilder, navigate to Project > Settings If there is a space in the Project Name, delete the space or substitute with an underscore Upload the project again.

Issue SNVT_press_p cannot represent a value above 32766 Pa Sending a value of 15psi out of a Menta application using a SNVT_press_p and it is arriving at the receiving controller as 4.75psi. Environment SNVT_press_p Menta LonMaker/NL220 Cause All LON communication is transmitted in metric units, so the data sizes are limited by the valid range of Pascals (or kiloPascals for SNVT_press). Resolution There are three different SNVT types defined to represent a pressure (gauge) value. SNVT_press, SNVT_press_f, and SNVT_press_p. It is important to recognize the valid ranges of data each one can represent. Name Units Maximum Minimum SNVT_press kiloPascals 3,276.70 -3,276.80 psi 475.25 -475.26 inches wc 13,154.74 -13,155.15 SNVT_press_f Pascals 3.40E+38 -3.40E+38 psi 4.94E+34 -4.94E+34 inches wc 1.37E+36 -1.37E+36 SNVT_press_p Pascals 32,766.00 -32,768.00 psi 4.75 -4.75 inches wc 131.48 -131.48

Issue Remove a TAC Xenta OP that is commissioned in LNS from the LNS network. Product Line TAC Vista Environment TAC Xenta OP installed and commissioned in an LNS network Cause If an installed OP is to be removed from the LNS network, it should be restored to the original factory setting to avoid problems, before it is used in another LonWorks network. Resolution OP version >= 3.40 Check in the OP Service menu #10. OP mode that Mode is set to MAN, Disconnect the OP electrically from the LonWorks network. Remove the OP from the LNS database. OP version < 3.40 Check in the OP Service menu #10. OP mode that Mode is set to TAC or MAN, (in OP version < 3.11, Bindable OFF). Start the LonMaker Browser. Restore SNVT_config_src from cfg_external (1) to cfg_local (0). SNVT_config_src may be called var_2 in the Browser. Disconnect the OP electrically from the LonWorks network. Remove the OP from the LNS database. Factory setting If the OP has been de-installed in an incorrect way, it may be restored to the factory setting in one of two ways: Reconnect the OP to the network, reinstall it and perform the steps above in the correct order, Use the Nodeutil program and perform the following. Select OP Service menu #10. OP mode that Mode is set to TAC or MAN, (in OP version < 3.11, Bindable OFF). Start Nodeutil. Press the Service pin of the OP. Type G (Goto) Type 1, and then press Enter. Type M (Mode) Type S (State) Type C (Configure) Type U (Update) Type 2 (nciNetConfig) and then press Enter. Type 00 (cfg_local) and then press Enter.

Issue Can ASD bus wiring be used for LON communications in a retrofit situation? Environment ASD bus wiring LON network retrofit Cause The communications protocols for RS-485 and LON are two totally different and opposing specifications. Resolution No, ASD bus wiring cannot be used in conjunction with an existing LON network. Any deviations from LON standards result in unsatisfactory performance. Not adhering 100% to the published best practices guides for LON bus wiring will result in no end to problems with the installation.

Issue Xenta 555/731 resets when an alarm is blocked or unblocked. Environment Xenta 555, 731 XBuilder Cause If you set an alarm object to email you when the alarm is blocked or unblocked, the Xenta will send the email, and change the alarm state to blocked or unblocked, but then performs a reset. Resolution Work around for now is to not check the blocked and unblocked condition to send emails in XBuilder

Issue CNT block in XBuilder Xenta 700 Menta is replaced by a PI block. Environment Xenta Server Xenta 701, 711, 721, 731 XBuilder Menta Cause Differences between the regular Menta and the XBuilder Menta for Xenta 700 programming. Resolution The CNT block is replaced by the PI (Pulse input) block in XBuilder Menta. In XBuilder, connect the PI to a Binary or universal input where the sensor type is set to counter.

Issue How can I change the logo in a Xenta 7XX so it shows my company instead of TAC/Schneider Electric? Environment Xenta 701, 711, 721, 731 Cause Image files are loaded with the download of a system program and default to TAC or Schneider Electric branding depending on the version. To customize them to another corporation's logo, the files must be manually edited through FTP. Resolution Use ftp to get the files below from the Xenta 7xx. Edit the files with the new logo and rewrite them to the original location in the Xenta7xx. Power down/Power up the Xenta 7xx. Logo files:  Directory www/index user_logotype.gif  Directory www/images user_logotype.gif  s_logotype.gif  loginlogo.gif  731splash.jpg (change if Xenta 731)  721splash.jpg (change if Xenta 721)  711splash.jpg (change if Xenta 711)  701splash.jpg (change if Xenta 701)  Note that this will be reset back to default if a new system program (firmware) is loaded.

Issue Is there a way to link to a Xenta Server so you don’t have to log in to it? Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause Access to Xenta Server with auto log in is not a supported feature. Resolution There is no auto log in function in the Xenta Server but you can add the password to the URL https://xx.xx.xx.xx/www/index/index.html?UID=root,PW=root This will log you in and take you the start page for the user You can also go direct to a page (TGML, Trendlog etc.), this way you will not get any other frames. First you have to figure out the path to the page. Easiest way to so this is to log on the 731 with FTP and browse to the graphic you want to display. Copy the path and add ?UID=root,PW=root (for root user) Here is an example what it might look like https://172.20.10.91/www/info/The+site+name/Folder+2/Graphic_page.html?UID=root,PW=root Note that if you use this method the user can not log out (the user will still be logged out after the default time still)

Issue TAC Menta Online Device DI block shows "Offline" for I/O modules with numerical names The DI block in TAC Menta has a functionality "device offline", when the device name starts with a number (e.g. 2), the device online function doesn't work as supposed. Device online flag is tripped, (or actually set to 0) but will never be reset when device is online again. Environment Menta Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B I/O modules Cause The reason that this functionality doesn't work is because if the device address starts with a number it's considered to be an I/O module. Resolution Rename the I/O module devices to a name that does not start with a number.

Issue After I have commissioned a LWU I get “Invalid Value” on several of my SNVTs. Environment Vista Workstation 5.1.2 or later Cause In earlier versions of Vista, null values for SNVTs were displayed.  For example, a null value for a SNVT_temp_p is 621.8°F.  This was sometimes confusing, so in 5.1.2 a change was implemented to no longer display null values for any SNVT type.  Instead, it will show "Invalid Value." Resolution This is a new feature in TAC Vista 5.1.2 if the value is out of range for the SNVT or at the max value TAC Vista will no longer show the value it will say "Invalid Value."  This is normal operation and no cause for concern.

Issue Vista events from a standalone Xenta 5xx must be adjusted. Product Line TAC Vista Environment Vista Event Logging Xenta 5xx Cause Situations where the Xenta controller must handle more events while in a "standalone" installation. Resolution In Xenta firmware versions >5.1.3 it is possible to change the event storage capacity of the Xenta with a console command "eventcap". The variable of eventcap allows the user to define how many event storage files Xenta may have. The valid number range of events is from 10 to 2000. Each file stores ~150 events, depending on event size. Example: 700 files are recommended to store ~100,000 events. Note: This only works for Vista events, not I/NET. I/NET uses another memory module of the Xenta device and will not be affected with this change.

Issue Vista to I/NET Integration Tips Product Line TAC INET, TAC Vista Environment I2V Integration I/NET XBuilder Xenta 913 Xenta 527 Cause An input in I/NET can only be controlled from an outside source if it is in "Test" or "Manual," so outputs must be used. Resolution When integrating with an I/NET system using a Xenta 5/7/9xx, all I/NET points must be defined as either AO or DO, regardless of the direction of information flow. To get data from an I/NET system (into Lon, BACnet, or Modbus) use the AO attribute "value" or DO attribute "value." To get data into an I/NET system (from Lon, BACnet or Modbus) use the AO attribute "value" or DO attribute "control."

Issue Is it possible to replace a Xenta 400A I/O module in a LonMaker based project without a program download? Environment LonMaker Xenta 421A, 422A, 451A, 452A I/O Modules Cause There is an option in the system plug in that decides how the addressing of the I/O module is handled. If the checkbox "Xenta I/O modules commissioned with LNS" is checked (this is called preconfigured in the old NDB tool and in XBuilder), the Xenta starts communicating to the I/O module using the subnet node address it has been given by the network tool (Lonmaker).  If the Checkbox is not checked, the Xenta will communicate with the I/O module on the neuron ID first to give the module the address that it thinks it should have. Resolution If the checkbox "Xenta I/O modules commissioned with LNS" is checked in the System Plug-In, and you replace the module in LonMaker, you do not have to download the Xenta. If the checkbox is not checked (the I/O module does not need to be commissioned in LonMaker), you have to download the controller or you can add the I/O module using the OP.

Issue If a signal name or description in XBuilder Device Editor has non-Latin characters (like Swedish å, ä, ö, Å, Ä, Ö) it will read [Invalid Address] when viewing the signal in Vista. Value pages are displayed correctly. Environment Vista version 5.1.5 or prior Menta Xenta XBuilder Cause Signal name or description in XBuilder Device Editor has non-Latin characters (like Swedish å, ä, ö, Å, Ä, Ö)  Resolution Don't use non-Latin characters (Or space) for signal name or description. This issue was confirmed in versions 5.1.2 - 5.1.5. It has been fixed in version 5.1.6.

Issue Unable to save periodic report to network drive when Vista is running as a service. Vista Alarm: Warning logged in B0WARLOG.TXT on node XXXXXX B0WARLOG.TXT: report >> Could not save report Reports-Report, hRes=[-2146827284] Product Line TAC Vista Environment Vista 5.x Cause When Vista Server (TACOS.exe) is running as a service, it is not functioning as part of the user desktop. This means that network map drives are not accessible under the aliases (J:\, M:\, S:\, etc). Vista Server is instead running under a specific user account name that must have access rights to the network drive and the report object must reference the full path to the network drive location. Resolution NOTE: it is recommended that the destination folder for these periodic reports be located on the local disk C;/ drive.  It can be problematic to have the destination folder located on the desktop. Open the Services MMC from Control Panel\Administrative Tools\Services. Find TACOS in the list of services. Stop it if it is running. Right click on the service and select properties. On the Log On tab check the "This Account" option and fill in a local administrator user that has access to the network location. Click Ok. Start the TACOS service. Start Vista Workstation and log in. Right click the report you are trying to save to a network drive and select properties. On the Report tab ensure that the "Save to folder:" has the full network path (ex. \\computername\directoryname). Use the browse if necessary. Click OK The next time your periodic report runs it will properly save the report to the network location.

Issue Bug in conversion of real numbers to integers in Menta Expression Blocks Environment TAC Xenta 280/300/401 with system program version up to version 3.41 Cause A bug exists that causes real numbers to be improperly converted to integers in Expression Blocks. The issue is that some functions that return a real result (e.g. +-*/ and exponentiation) will sometimes return a value slightly less than expected. For example, 2**5, which is 2 to the fifth power, should return 32. Instead, 31.9999999999 is returned. In an expression that then then converts this to an integer (e.g. "A&(2**5)"), the result gets truncated to 31 instead of the expected 32. In the example "A&(2**5)", A will then be bitwise AND-ed with binary 01111 instead of 10000. Unfortunately, this bug is only seen when running the code live on a controller. In offline simulation mode, 2**5 returns the correct value of 32, which only makes the bug more difficult to diagnose. Oddly, The XPI block and the INT() function convert results to integers differently. An XPI block with expression "2**5" will return 32. However, and XPI block with expression "INT(2**5)" will return 31. In some cases (e.g. 19**3) both the XPI block and the INT() function return the incorrectly truncated value. This behavior is corrected from version 3.50 of TAC Xenta 280/300/401 Resolution The work-around is to never use operations that return real values in an expression that also does operations that convert the operands to integers (such as bitwise operations). This behavior is corrected from version 3.50 of TAC Xenta 280/300/401