Building Automation Knowledge Base

Issue Can not connect to a Remote RAS Controller Product Line Andover Continuum Environment RAS Connections to: CX9900, CX9940, CMX9924, CX9400, CX9200 Controllers with HyperTerminal support Modem connections, Dial Up Cause Can not dial up remote site over RAS connection What settings need to be checked? Resolution For assistance with troubleshooting RAS connections download the v1.9 Continuum Remote Communication Configuration Guide For older versions of Cyberstation also check out the RAS guide installed on the Cyberstation along with the Continuum software. The following settings/ configuration should be checked to help isolate the issue where a site can not be connected: Verify phone line is giving correct cadence ring tone that can be detected by the modem, some internal phone/ exchange lines give non standard tones and may not be answered by the modem . Using another External phone line verify can log on to the controller with hyperterminal using the Baud rate chosen at front end (usually 19200). See the link below for details on using the Command Terminal interface.  If Modems do not answer - Check the correct AT commands have been sent to the modem at the selected baud rate, also verify the cable is 9 cores and a DCE - DTE (Straight through cable). Ensure AT settings have been saved in the modems non-volatile memory. Verify all commport setting match the front end database settings and match any other working sites. Typically 19200 baud, 8 data bits No parity 1 stop bit. Ensure this matches the front end settings when checked using command line as on older versions of Cyberstation the comm ports screen does not always show the correct values. Verify "Track CXD" is selected and "Direct Connect" is not. Verify the Comm port "DefaultBaud"  attribute is set to the same value as the Baud rate used, so that the connection can be made following a power fail. Verify comm port flow control matches the front end, typically hardware & software XonXoffCtsRts Once successfully connected with Hyperterminal and all settings match front end ensure the port is logged off before trying to connect from the Cyberstation. If Cyberstation can not connect to any remote site, first connect a Laptop running Hyperterminal to the front end modem and dial it up from another line to verify the modem & cable are operating correctly. Then go through the software and remote site configuration as detailed in the RAS Guide. Verify Cyberstation is running on XP or Win2000 operating systems as appropriate from Compatibility matrix - See RAS is not supported in Microsoft Vista and Windows 7 for use with Continuum. Also see Continuum controllers and Remote Access Communication for information on controllers that support RAS as an Access point.  For testing with Hyperterminal, download the Command Terminal Configuration Guide

Issue Is there an updated list of all tested devices using the M-bus Xdriver? Environment Xdriver Cause Would like to know what devices have been successfully tested with the M-bus Xdriver. Resolution The current M-bus Xdriver Manual lists several devices that have been tested. The question of what devices have been tested with various Xdrivers comes up now and then. The group that develops Xdrivers is not chartered to continuously test new devices with the drivers and does not maintain a list of devices that others claim to have successfully implemented. There are likely dozens of other M Bus devices our branches/partners have used successfully but we do not capture/verify this info.   There two best options for attempting to get this information are: 1. Ask on the Continuum Community Forum (https://community.se.com/community/bms/continuum) or 2. Obtain the product and bench test it.

Issue A message stating the PC's "Resources are Low" is being displayed. These hosts are running Windows 95 and Windows 98. Product Line A message stating the PC's "Resources are Low" is being displayed. These hosts are running Windows 95 and Windows 98. Environment Older I/NET site Windows 95 Windows 98 Cause Older computer running I/NET and Windows OS Resolution Go to Window's Task Manager to find what is running in addition to Windows and I2K. These additional tasks need to be eliminated. Check the performance settings located in Windows Control Panel > System > Performance Tab. Make sure these hosts meet the minimum INET 2000 requirements. Refer to the Getting Started TCON in TCON Number and Title Cross Reference (with links) for specifications.

Issue Since Generation 1 controllers do not have a controller webpage, how can I access the controller configuration to set up the controller or access controller information. Product Line Andover Continuum Environment Hyper Terminal CX9900 CX9940 CX9400 CX9410 CX9200 Cause 1st Generation Controllers do not have an embedded webpage. Resolution Find information about the pin configuration of the direct connection cable in PinOuts for the RS-232 Connection of the older 1st Generation CX controllers. The following document describes how to log into a generation 1 controller via a PC with a terminal emulation application: CX Operators Guide.pdf

Issue How to launch the Vista System Plug-In in Visio 2010.  In earlier versions, it was located under the toolbar menu LonMaker > System Plug-Ins, but that menu item no longer exists. Product Line TAC Vista Environment LonMaker Turbo 3.2 Visio 2010 Add-Ins Cause Usual drop-down tool bar menu items do not exist in Visio 2010 as they did in earlier versions. Resolution System Plug-Ins can be found under the Add-Ins tab Add-Ins LonMaker Network Plugins. If the Add-Ins are missing, please see Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable, or Error: "unable to launch visio with file lonworks.vst".

Issue TAC Vista will not dial out to an Xenta 901 network as expected e.g. when opening a graphic or selecting a remote controller in the folder view. Product Line TAC Vista Environment TAC Vista 4 TAC Vista 5 Cause The COM port and /or the Xenta 901 network are not correctly configured. Resolution Check that Vista is in Operating mode. See Opening a graphic will not cause TAC Vista to dial out to a Xenta 901 Network for details. Check that the COM port your modem is connected to is correctly configured in Vista. The port object in Vista will be of the type 'Communication Port - Modem'. Hopefully, it will have a meaningful name relating to the connected modem. In the properties for the port check that the Device Address refers to the correct physical COM port. The Device Address is of the form "server_name-COM_xx", where COM_01 will be the first port defined in Vista. If you have multiple COM ports or a USB/RS232 converter, this may not be the address you want. You can manually change this to the required port: for example COM_03. You can see which physical ports are available in Device Manager. In the properties for the port check that Traffic direction is set for outgoing traffic. Normally you will set this to "Incoming and outgoing traffic", but you might want "Only outgoing traffic" if you don't want to receive alarms or trend logs via this modem. Check that the port has been assigned to the Xenta 901 Network. In the properties for the Xenta 901 Network - Modem select the "Ports" tab. This displays a table listing all the communication ports this network will use. If the table is empty Vista will attempt to dial out on all ports not set as "Only incoming traffic". If you have multiple ports this is probably not what you want, so use the Add and Delete buttons to select only the ports that you want this network to use. In the properties for the Xenta 901 Network - Modem select the "Outgoing Traffic" tab. Check that the phone number shown is correct for the remote site. If Vista is dialing out through a PABX, prefix the phone number with "9,". The comma after the nine tells the modem to wait 1-5 seconds (adjustable via your modems command set) so that a dialing tone can be obtained from the PABX. If you are using the recommended US Robotics modem, the many default parameters for the comm port and the Xenta 901 Network - Modem should let Vista dial out without further modification.

Issue Cable needed to Direct connect a Laptop or Desktop to a PCU Product Line TAC INET Environment I/NET site Cause The first asynchronous port (P4) provides an RS232 port for direct connection to a PC or external direct dial (Hayes) modem. The RS232 port’s baud rate is set using the HHC. Resolution CBL072 for a 9-pin PC connection CBL073 for a 25-pin PC connection Refer to TCON 096 For CBL072 information, please refer to Cable Connectivity to I/NET.

Issue Cannot connect network variable point from a third party LON device to a graphic within an XBuilder project.  XBuilder will not allow the drag and drop of LON network variable between the network pain and the system pain when you attempt to create connections. Product Line EcoStruxure Building Operation, TAC Vista Environment XBuilder Vista Lon Device .xif Cause XBuilder is very particular about the format of an .xif file and it will not allow certain characters in the function block name. Vista and LonMaker have far less limitations and these programs are able to parse these characters without causing problems. This explains why your values may show up in the LNS management tool and Vista Workstation. However, once you import the network into XBuilder you are unable to connect the SNVTs to your graphic. Resolution Replace the incorrect characters in the function block line of the .xif and reload the new .xif into your LonWorks Network.  Please see LON device can communicate in Vista, but fails in a Xenta Server / XBuilder for more information about incorrect characters in an xif file. INCORRECT FUNCTION BLOCK EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved. Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000-MP580,8500-SCC,8610-DAC The problem is the three dashes  between the object numbers and the object names in the self doc string.  This is "allowed" in Vista and LonMaker in some sense.  For  example, Vista "replaces this "-" to a "/" but then XBuilder can't handle this situation properly. CORRECTED EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved.  Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000MP580,8500SCC,8610DAC;Tracer MP580 The dashes 3 x (-)s have been removed from the function block name

Issue Get "No License available" error message when logging in to Vista webstation.  The following errors have occurred. Please correct these errors and / or contact the system administrator. Product Line TAC Vista Environment Windows 2008 server 64-bit Vista 5.1.5 Vista 5.1.9 Evaluation License downloaded from extranet Cause Incorrectly formatted license setup Resolution Check the License Setup. Open License Setup and check the format used. The picture below shows that the license server is on the local PC (using the computer name), but this will not work. Instead, type the file path to the evaluation license (see below). Note: From Vista 5.1.8 and later the path should instead be C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses If this hasn't resolved the issue try the steps outlined in TAC Vista Webstation licenses are not released after closing the Webstation browser

Issue Deleting Sigma clients from the registered clients list. Product Line Satchwell Sigma Environment Registered client Cause Sigma clients once used will remain in the registered clients list. How can these be removed? Resolution To remove old or unwanted Sigma client entries, carry out the following; Open Sigma "System Setup". Select the "Clients" menu. Select the client that in no longer appropriate. One the client is highlighted, select delete by using the icon or file option. Please note that a Sigma client cannot be deleted if it is still associated with a Sigma server. Refer to Sigma client cannot be deleted.

Issue When opening a TGML graphic page you get an error and Vista Shuts Down. Product Line TAC Vista Environment Windows 7 Vista 5.1.X Cause The monitor is using the DIVI Digital Video Input. Resolution If Vista Crashes when you attempt to open a TGML graphic then change to the analog VGA output on your video card. Here is A DVI lead Here is a VGA lead Hardware acceleration on you video card can also cause a similar issue. Please see Vista Workstation is crashing/shutting down when graphics begin to load for more information on hardware acceleration issues.

Issue Upgrading the operating system (OS) to Windows 7 on an old PC. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Older PC's Windows 7 Cause Some older PC's are not suitable for upgrading to Windows 7. Resolution When considering upgrading to Windows 7 with an older PC, it must be first checked for suitability. Run the Windows 7 Upgrade Advisor before upgrading. To review the Schneider Electric Software and Firmware compatibility matrix please see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue Is editing an exported XML file supported? Receive errors when attempting to import (a modified) exported XML file. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Export / Import  Cause There is minimal error checking on the import so errors could get through and cause problems further down the line and corrupt the database. Resolution Edited exported XML files is not supported and there is no documentation on how to properly edit exported files. This practice should not be attempted.   With 1.5 will comes Project Configuration Server (PCS) and the ability for the businesses to create their own country specific applications and mass create engineering tools. In a future release (currently indicated in 1.6) support for using the Backup and Restore feature to duplicate entire Automation Server databases will be available.  For now both these functions are not supported.  Refer to Do NOT use Backup and Restore to duplicate Automation Server databases! (1.5 and below).

Issue Using the correct URL to launch webclient and there is only white space Product Line Andover Continuum Environment Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause ActiveX controls were not installed from the Server onto the browser PC. Certain versions of browser (IE8) disable unsigned activex controls which we use for webclient Resolution It is possible that if this is happening on a domain that there is a group policy in place restricting access. Try the browser on the webClient PC or a laptop directly connected to the webClient PC. Check the compatibility matrix to see if the version of your browsers are supported with that version of webClient. Ensure the Activex controls were installed Turn Off Pop-up blocker.  Internet Explorer> Tools>Turn Off Pop-up blocker Internet Explorer> Tools> Internet Options> Security> Select the correct Zone (i.e. Internet, Local, trusted). Click Custom Level button Select Enable for Automatic prompting for ActiveX controls Select Enable or Prompt for Download signed ActiveX controls Select Enable or Prompt for Download unsigned ActiveX controls Click OK, OK Close Internet Explorer and try again. If it is still not working, clear the cache (http://support.microsoft.com/kb/260897) and try again. If the PC is 64 bit and the webclient version is not 1.94 and above, that could also cause this. In extreme cases removing and reinstalling .net, IIS and webclient may be necessary. Verify that the version of SQL Server is compliant with the version of Continuum that is being used. Ex. SQL Server 2000 with SP3 (instead of SP4) isn't compatible with webclient 1.93 Check Removal of MS KB2858725 Dot Net 4.5.1 causes issues with Web Servers IIS Functions related to .Net 4.5 Reinstall webclient Lastly, a reformat of the hard drive an complete reinstall. Note: If the white space happens in just the personnel area and this is 1.74 remove .net version greater than version 2 In IE 9 and IE10 use compatibility mode IE11 is not currently not supported in a 1.94 SP1 ** Webclient 2.0 new alarmview is blocked by IE setting "Block pop-ups" ** If you receive "Internet Explorer blocked a popup from webClient IIS" after logging into webclient then turn of the pop-up blocker for this or all sites. Open Internet Explorer > Tools > Pop-up Blocker > Turn off Pop-up Blocker

Issue SigmaX PCID changes each time the PC is restarted, Juniper Networks Virtual Private Network (VPN) has recently been installed. Product Line Satchwell Sigma Environment Windows XP with Sigma, SigmaX and Juniper Networks VPN virtual network adapter Cause SigmaX uses the Media Access Controller (MAC) address of the first network adapter on the PC to generate the SigmaX PCID, when the VPN adapter from Juniper networks is installed it is placed by windows as the first adapter. If the ipconfig /all command is run from a command prompt it can be seen that new MAC address is assigned to the Juniper adapter each time the PC is started. A search of the Juniper Networks knowledgebase shows that it is normal behaviour and the MAC cannot be fixed Summary: Is there any way to have static MAC address for Network Connect virtual adapter? Problem or Goal: Assigning static MAC address for Network Connect virtual adapter. Solution: As of now, it is not possible to have a static MAC address for Network Connect virtual adapter. The virtual MAC for Network Connect virtual adapter will always start with 00:FF and the rest of the MAC is generated dynamically. The MAC address of the Network Connect client machine is randomly generated based on the algorithm whose result will change with system and time. Resolution SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. SigmaX uses the Media Access Controller (MAC) address of the first network adapter on the PC to generate the SigmaX PCID, when the VPN adapter from Juniper networks is installed it is placed by windows as the first adapter. Since there is no way of fixing the MAC address of the Juniper virtual network adapter the work around is to disable the adapter when SigmaX is used. There are two ways that this can be accomplished:- Disable the adapter from Windows Device Manager Note that the Juniper network Connect Virtual Adapter is a hidden device in Device Manager Right Click on My Computer and select Manage from the available options Select Device Manager from the management tree Once in Device manager select "Show Hidden Devices" from The View menu Expand the network adapters tree and right click the Juniper network Connect Virtual Adapter entry and select Disable After a short delay a red X will be shown across the icon for the adapter SigmaX will now use the next adapter to generate the PCID, note that the adapter will need to be Enabled in a similar fashion to above if a VPN connection is required at a later time. Disable the adapter via a script It is possible to disable/enable the Juniper Virtual adapter from a script, this requires that the Microsoft DevConutility be first downloaded to the PC Download the DevCon utility from http://support.microsoft.com/kb/311272 Extract DevCon.exe from the i386 folder of the zip file and place it in the root directory of the PC Create a new notepad file with the following text: cd\ devcon disable *DSNCADPT* end Save this file as DisableJuniper.bat Create a second new notepad file with the following text: cd\ devcon enable *DSNCADPT* end Save this file as EnableJuniper.bat Executing these files will control the adapter and once disabled SigmaX will now use the next adapter to generate the PCID

Issue Utilize the RS-232 port to send text out to a third party device such as CCTV Product Line TAC INET Environment I/NET Seven Cause Integration Assistance Resolution This V-Doc describes the way text output can be set up in I/NET to be sent out to third party hardware such as CCTV through the RS-232 port. The port that will be used for this application cannot be one that is already being used by the serial port section, A/C reader port, or printer port in the peripheral section of the configuration profile.   For the guide of integration with Pelco analog matrix, refer to How to integrate I/NET with Pelco Analog Matrix.

Issue Check the current size of the SQL database associated with a Vista database to ensure that it hasn't become full. Product Line TAC Vista Environment SQL Cause The SQL database that installs automatically with Vista has limitations on the amount of data it can hold.  Most often, this is plenty of space for many years of trending without issue.  But if a site is very old or has many trend logs defined, it can out grow the SQL database.  Limits are: Vista IV - Vista 5.0.0 MSDE:  2 GB Vista 5.0.1 - 5.1.6 SQL 2005 Express:  4 GB Vista 5.1.7 and newer SQL 2008 Express:  10 GB Resolution This procedure checks the log size from the Vista Workstation: In Vista Workstation, click on the Vista Server in the folder pane Right click on $Backup_LDB and select Properties Scroll to the bottom and make note of the Database Size property (shown in grey).  This is the size of the database in MB. This procedure checks the file size on the hard drive.  The assumption has been made that this is not a custom install, but the default SQL installed with Vista Server: Open Windows Explorer Navigate to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data Locate files: taclogdata.mdf taclogdata_log.ldf Note:  If there are multiple instances of SQL installed on the PC, there may be MSSQL.1, MSSQL.2, MSSQL.3, etc.  Find the SQL instance that contains the file names listed above. Highlight both files and look at the bottom of the window on the status bar.  The combined size of these two files is shown.  This can be used to determine is the SQL database is full and requires a purge.  To purge a Vista IV SQL database, see How to create a new database or purge a full SQL (i.e. it has hit the limit of 2G) in Vista IV. To purge a Vista 5 SQL database, see Vista 5 full SQL database issue. If purging is not an option, then the SQL will need to be upgraded to a full version of SQL (not express).  To see the different options, see Vista Database Sizing and SQL Server Selection.

Issue What is an MCI? Product Line TAC INET Environment I/NET site Cause This interface supports a mixture of up to 64 MRs, ASCs, and DP family controllers. Resolution This stands for Micro Controller Interface. This unit provides a control interface that can integrate MRs and DPUs on the same subLAN. See Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication for further explanation.

Issue The Following error is displayed when attempting to use webUI: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source) at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source) at sun.plugin2.applet.Plugin2Manager$AppletExecptionRunnable.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet Product Line TAC IA Series Environment Niagara R2 WorkPlace Pro 532 Cause Some servlets which the browser uses were left out of the webUser-2.301.532.jar files. Resolution The plan is to correct this issue in the next maintenance build release. The workaround is to replace the current webUser-2.301.532.jars with the webUser-2.301.530a jars. Reference How to install an I/A Series R2 JAR File.

Issue In the alarm window of TAC Workstation, there is a system alarm that is Physical device no defined/configured. After you acknowledge it, it will occur again. Product Line TAC Vista Environment TAC Vista workstation Xenta 280/300/401 Xenta server LOYTEC NIC-USB Cause The controller address cannot be verified correctly in TAC Workstation. For example, a TAC Xenta Group name or number is in conflict with another TAC Xenta Group’s. Resolution If multiple TAC Xenta Groups or Lonworks networks are created, you must verify the Lonworks network’s name or TAC Xenta Group name and number is unique. The TAC Xenta Group default number is 254. The different number must be given to the different TAC Xenta Group even though the TAC Xenta Groups are beneath the different Lonworks network.   You can also reference to the articles System alarm message, Physical device not defined/configured and Physical device not defined/configured about this issue.