Building Automation Knowledge Base

Issue What is the wiring for the RS-232 A, RS-232 B, RS-485 A, RS-485 C, and 10Base-T ports on a Xenta Server? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 BACnet/IP BACnet MS/TP M-Bus C-Bus Lon Modbus Cause The wiring and pin outs for the Xenta Server hardware is detailed in chapter 2.1.2 of the TAC Xenta 500/700/911/913 Product Manual . Resolution The ports and wiring is unique for each port. RS-232 A port For serial communication it is typical to only connect the RX, TX, and Ground pins. Pin 3 4 5 Serial Cable RX TX Ground  RS 232 B port   10 Base-T port (Web connection) Note: The Xenta 913 also supports BACnet/IP and Modbus TCP/IP on this port. RS 485 A port (Modbus) Note: The Xenta 913 also supports BACnet MS/TP on this port. If two wire communication is being used then only use pins 5 and 6. Pin 5 6   + - If four wire communication is being used then all four pins will be used. Pin 5 6 7 8   TX + TX - RX + RX - RS485 C port (I/NET) This port is used for I/NET communication. Pin 19 20   + -

Issue When defining a Communication Port - Loytec the Network interface drop down is empty when the device is connected and recognized by LConfig. Product Line TAC Vista Environment Vista 4.4.0 - 4.5.0 Vista 5.x.x LoyTec NIC Cause Vista Server will only display Loytec devices connected to the computer when Vista Server is launched or started. If the NIC was connected to the computer after Vista Server was started it will not be visible until Vista Server is restarted. Resolution To populate the Network interface drop down with the currently connected devices: Shut down Vista Server Restart Vista Server If Vista is running as a service, then LConfig should function as a service also and service dependencies should be utilized to ensure that Vista Server (TACOS.exe) does not start until after LConfig.

Issue Is Webstation compatible with iOS or Android for use on tablets or smartphones? Product Line TAC Vista  Environment TAC Webstation 5.1.7 and earlier versions. Cause Today many technicians use iPad, tablets, or mobile phones in their daily work and would like to access the buildings running Webstation on these devices.  Resolution Unfortunately today it does not work well to run Webstation on iOs or Android. The problem is viewing TGML graphics. They will not load correctly.

Issue Making connections in Xbuilder for graphics, connection objects, alarms, Menta programs, or trends can be tedious due to the organization and tree structure of the System pane window. Do logical units in the system pane have to be used when making bindings? Environment Xbuilder 5.0.2 - 5.1.x Cause Both logical and physical objects can be linked (though some unit issues might cause one method to be preferable to another) to graphics, alarms, connection objects, Menta programs, and  trends. With the use of the Filter View the system and network pane can be presented in a single window filtered to only display objects which work together. Use of the Filter View will provide a user friendly connection process that avoids the need for users to scroll up and down the system pane to drag and drop signals. The filter view toolbar also provides the ability to fix the view and connect objects without having to drag and drop them into the system pane. The Filter View is only available in Xbuilder version 5.0.2 or higher. Resolution Highlight the object you want to make a connection with in the System Pane. Select the Filter View tab in the middle pane. Select the signal from the combined list of System and Network panes. Use the Connect button on the Filter View toolbar to finish the connection.

Issue Polling data from one Xenta Server to another can be accomplished over IP by importing XBuilder Projects. This will only bring over data points that reside in the Network Pane of the XBuilder Project.  If points are being calculated in a Menta object, for example, they would not be available following an import. Product Line TAC Vista Environment XBuilder Xenta Server 701, 711, 721, 731 Fixing Write Over IP Cause Importing another projects network brings over only data points that reside in the Network Pane of the XBuilder Project. In order to avoid a write over IP situation, data from the System pane sometimes needs to be browsed into the other controller's project. Resolution Expand the Network pane beneath the Xenta 700 and find the Variables folder. Right click on the Variables folder and select New Variable (if desired, choose New Folder to organize the points that need to be sent over IP). Create a variable for each point that needs to be imported into the receiving Xenta Server. Drag and drop Variables onto the Menta object outputs to associate them   Note: Only Menta object Outputs allow for this drag-and-drop functionality.  If they are public signals, then either: Add an RO, IO, BO point on the output of the signal Use a connection object in XBuilder to transfer the value to the Network Pane variable. In the receiving controller's XBuilder project, right-click on the IP Backbone and select New > Other Projects Network.  Now the Menta object variables are available.

Issue How to monitor if an HOA switch in an I/O module for a Xenta Server is set to something other than auto. How to tell if an I/O signal is hardware (HW) overridden/forced Environment Xenta Server (731, 721, 711, 701) Cause Some I/O modules have switches that can be used to manually force/override the outputs. It could be important to know what signals are forced. Resolution In XBuilder, each physical I/O that has a manual switch also has a signal for it.     This can be used to monitor the switch.

Issue Loytec (LTA, lon port) offline in TAC Vista when running TACOS as a service Environment TAC Vista running as Service Loytec NIC device Lconfig/NIC legacy driver Cause For TAC Vista to use the legacy driver, it must be running before Vista starts. When running TACOS as a service, by default, it will start prior to the legacy driver and the LTA port will show offline. For this reason, the legacy driver must also run as a service.  Dependencies on the Vista Server service must also be configured to ensure that the legacy drivers starts first. Resolution First make sure that the legacy driver is set up to run as a service Open Lconfig and click on advanced. Select "run as service" and click ok.   Reboot computer From the  start menu, select run, and type regedit Go to  HKEY_LOCAL_MACHIN\SYSTEM\ControlSet001\Services\TACOS\ Double click on depend on service Type in LoytecSrv on a new line.   Reboot computer.

Issue TAC Vista Web Settings > Preferences > Login and Logout > Automatic Logout (An inactive user is automatically logged out after a specified period of time) Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Set the logout time to less than 5 minutes Set the logout time to more than 30 minutes. Customize the logout time to something other than specified intervals.  Environment Vista 5.1.5 Webstation TAC Vista Web Settings Cause Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Resolution Navigate to C:\Inetpub\wwwroot\TACVistaWeb515 Open the file web.config. Use, for example, Notepad2 (Do not use wordpad as it formats the file differently) Search for "sessionState" Change the "Timeout" for the SessionState to the desired logout time in minutes Save the file 

Issue Get warning (error) "The Min and Max values for the "in" signal are out of bounds in regard to this "to" signal" when generating Xbuilder project Environment TAC Xbuilder Cause This warning refers to min and max values of signals in a connection object not matching. Resolution This is just a warning that there is a possibility that the receiver can't handle some of the values that can be sent. No action is required.

Issue Menta Crashes in Simulation Mode. Environment Menta Vista Cause Improper use of Menta objects can cause Menta to crash in Simulation mode. It is possible to cut a HFDI from inside a HFB and paste it onto the root level of the Menta drawing. Resolution If a Menta Object is used in a manner that is not normal, such as a HFDI (Hierarchical Function block Digital Input) used outside of a HFB (Hierarchical Function Block), Menta may crash when entering Simulation Mode (hotkey=F12). The best way to troubleshoot this type of issue is to systematically delete portions of the Menta file then try to enter simulation mode. If you successfully can enter simulation mode, the deleted piece was causing the crash. You can typically narrow the cause down to the object causing the issue.

Issue Some TGML javascript functions that work correctly in Vista Workstation stop working in Vista Webstation or break graphic performance. The following errors have occurred. Please correct these errors and/or contact the system administrator. An unexpected exception has occurred: Object reference not set to an instance of an object. System.NullReferenceException at TAC.WebStation.Modules.Graphics.TgmlLinkPage.CreateLinkData(TACOSTgmlPicture tgmlPicture, String oID) at TAC.WebStation.Modules.Graphics.TgmlLinkPage.GetLinkList(TACOSTgmlPicture tgmlPicture, String[] oIDs) at TAC.WebStation.Modules.Graphics.TgmlLinkPage.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Product Line TAC Vista Environment Vista Webstation 5.x.x Graphic Editor TGML 1.x.x Cause Due to the differences in Vista Workstation and Vista Webstation being viewed through internet browsers some TGML javascript functions will not function, function as expected, or cause your TGML graphic page to be unusable resulting in a Java error message. Resolution To make TGML graphic pages compatible with Vista Webstation remove the following functions: getDate getYear getMonth getDay getHour getMinute getSecond To make TGML graphic pages compatible with Vista Webstation adjust the unexpected behavior of the following functions: setTimer - this function cannot be used in the OnDocumentLoad event getStatus - this function will always return a value of 2 invoke - this function can only be used on links, not bindings.

Issue When you browse a Lonmaker object, the temperatures display the incorrect units. Environment Lonmaker Windows XP Cause The regional settings on the computer are incorrectly set for the systems specific region and therefore show the incorrect units for temperature. Resolution The Regional Settings of your PC need to be correctly configure for your Region. The steps to correct this are: Navigate to Control Panel Open Regional and Language Options Under the Regional Option tab ensure the correct region is selected Select the Advanced tab and ensure that the correct Non unicode region is selected. Reboot the computer after these changes have been made. If you have updated the Vista database with these object you will need to delete them from the TAC Network in the System Plug-in. Then update the Vista Database without the effected controllers. Once the database has been updated to remove these effected controllers you can let the plug-in update the TAC network. After  the TAC Network update a Vista database update can be done. This will transfer the XIF files and set them to the correct units. Check the database for any links on these updated items and correct lost object paths. 

Issue Get the following error message when preview is used in the TGML editor when the graphic have a script in it: TAC Graphics Editor - Unexpected Error A problem occurred in this application Method note found: 'Void org.mozilla.javascript.Context.__ ()'. Environment TGML editor 1.1.5 - 1.1.6 Vista 5.1.5 - 5.1.6 Cause Some DLL files from Vista 5.1.4 have not uninstalled correctly and are left in the folder C:\Program Files\Schneider Electric\GraphicsEditor. Resolution Uninstall the latest version of Vista. Install Vista 5.1.4 Reinstall the latest version of Vista.

Issue Problems upgrading/installing SQL server. The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine XXXXXXX Error:2147749896 (0x80041008). "Not clustered or the cluster is up and online” check fails. Note: In the screen shot above the clustering check was passed. Environment TAC Vista 5.X.X SQL Server 2000/2005/2008 all versions; upgrades and new installations. Cause The WMI (Windows Management Instrumentation) Control is a tool that enables you to configure WMI settings. Inadequate access permission will mean that the user is unable to access the WMI service. Resolution If one of these messages appears or other problems are encountered during installation or upgrading of an SQL server, follow the steps below: 1. Check the WMI settings Go to My Computer – either in the start-menu or go directly to the desktop icon if running windows in classic mode – and right-click on it. Select Manage. In the hierarchical tree in the pane to the left, expand Services and Applications. Locate WMI Control and right-click on it. Select Properties from the context-menu. If the message “Failed to initialize all required WMI classes” is displayed (see screenshot below) read on… 2. Change/check the DCOM settings Open the start-menu, click on Run and type “dcomcnfg”. The Component Services console should open. Expand Component Services and then expand the Computers folder. Select and right-click on My Computer. Select Properties. In the dialogue window that opens up select the COM Security tab. Under Launch and Activation Permissions select Edit Default. Check under Groups or user names to see if the group Everyone has been added. If not select Add, type in "everyone" and then click on Check names. Once the name is confirmed, click on OK. Ensure that the permissions Local Launch, Local Activation and Remote Activation are allowed for the group Everyone. Repeat the above steps for Launch and Activation Permissions but select Edit Limits.   Click on OK again to close the My Computer Properties window and then close Component Services.     3. Recheck the WMI Settings       Go back to the Computer Management console described earlier and locate WMI control under Services and Applications. Right-click on it and select properties. If all the steps have been followed the message should read "Successfully connected to local computer." After this it should be possible to upgrade/install SQL server.

Issue Problems installing Webstation 5.1.4 on PCs running Internet Information Services (IIS) 7 or higher. The installation appears to be OK but just before it finishes it "rolls back" to the beginning and webapps is not installed. Installation problems - Webstation 5.1.4 on Windows 2008 server Installation problems - Webstation 5.1.4 on Windows 7 Vista 5.1.4 webapps software crashing during install Environment Windows 2008 server Windows 7 (not officially supported) Vista webapps (webstation) Cause This issue is caused due to compatibility issues with IIS 7. Vista 5.1.5 is compatible with IIS 7. Vista 5.1.4. is not compatible with IIS 7. Resolution In order to install TAC Vista Webstation successfully on Windows Server 2008 it has to be done in the following order: Note : Make sure all installation is done as an administrator (Right click the file/application and select "Run as administrator")! 1. Install IIS 7 with IIS 6 Management Compatibility Start the Server Manager (Right-click on Computer in the start-menu or the Computer desktop icon if running classic start-menu and select Manage). Right-click Roles and click Add roles. In the dialogue that opens up click Next and then select Web Server (IIS). In the dialogue that follows click Add Required Features. Click Next (twice). On the select Role services page select ASP.net. In the dialogue window that appears click Add Required Role Services. Click on "Add roles" and then "next" in the dialogue window that opens. Scroll down to "IIS 6 Management Compatibility", check the box and follow the rest of the installation wizard. 2. Install TAC Vista Server 3. As administrator, Run the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) for ASP.NET version 2.0 Run the command prompt as administrator and type in the following: %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 4. Install TAC Vista Webstation 5. As administrator, Migrate the ASP.NET application configuration to IIS7 Run the command prompt as administrator and type in the following: %SystemRoot%\System32\inetsrv\appcmd migrate config "Default Web Site/" 6. Change the Application Pool in IIS7 Go to the Webstation/ScreenMate settings in IIS. Select "Advanced settings" under "Manage Application". Change Application Pool" from "DefaultAppPool" to "Classic .NET AppPool". 7. Change the application pool identity Locate the Application Pools in IIS Locate the "Classic .NET AppPool" application Pool Right-click on it and select "Advanced settings". Locate the Identity attribute and set it to "Local System".

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue An easy way to monitor K and V digital output states of a Xenta 121 in LonMaker for troubleshooting purposes. Environment Xenta 121 Vista Lonmaker Cause Uncertain of the output state on a Xenta 121. There are SNVT outputs to represent different functions of the Xenta 121, but they do not always represent the final RAW DO Status. Resolution Monitoring the SNVT nvoRawDOStatus to tell what state the output is in. nvoRawDOStatus is displayed as a 16 bit binary value. Each output will be represented by a bit. Bit 0 is the least significant/leftmost bit, and bit 15 is the most significant/rightmost bit. K1-K4 are displayed 1 for closed relay, 0 for open relay, Bit 0=K1 Bit 1=K2 Bit 2=K3 Bit 3=K4 V1-V4 are displayed 1 for on, 0 for off. Bit 4=V1 Bit 5=V2 Bit 6=V3 Bit 7=V4 X1-X3 are displayed 1 for shorted to ground. 0 for open. Bit 8=X1 Bit 9=X2 Bit 10=X3 U1 value is 0 not configured as digital input, 1 configured for digital input. Bit 11=U1 In Lonmaker right click on the Xenta 121 device Select Browse Navigate to nvoRawDOStatus Select Ctrl+M to monitor the nvo

Issue When navigating in TGML pictures, some are opened, a few then the picture "hangs" and I get thrown out from Webstation and have to log in again. Get logged out form webstation after opening a couple of TGML graphics   Environment TAC Vista 5.1.x TAC Webapps 5.1.x (Webstation) Windows 2003 Server Cause If the site admin has set the  properties on the application pools to restrict the memory a process can use this restriction will be applied to the SE.ASP.NET v4.0 Classic application Pool that webapps are using. These restriction have to be taken or set to a higher value. Resolution Open IIS Manager Expand Application Pools and right click on SE.ASP.NET v4.0 Classic Select properties Uncheck Maximum virtual memory and maximum used memory (or type in higher values) Click ok and restart the website.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.

Issue When trying to open TAC Webstation the following error message appears: Webstation error," Could not load file or assembly 'IKVM.AWT.WinForms' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." Environment Vista 5.1.5, Windows 2008 server 64 bit Windows 2003 server Cause Wrong Application pool is used for Webstation in the IIS, a ASP.Net version 2 is used instead of a .Net version 4. Webstation 5.1.5 is developed in ASP.Net 4. Resolution  In the IIS, under Websites\Default Web Site\Webstation - right click and select Properties and then the ASP.NET tab, change the Application pool from the DefaultAppool(ASP.NET version 2) to SE ASP .NET v4.0 classic (ASP.NET version 2) Application pool.