Building Automation Knowledge Base

Issue Unable to view a report in webstation. When trying to open the report object in webstation the message "This report is dynamic and cannot be opened from webstation". Environment TAC Vista 5.1.X TAC Vista Webstation 5.1.X Cause As the message implies, reports are dynamic objects that cannot be viewed in webstation. Workstation is considered an engineering environment where objects are created and manipulated, whereas Webstation is primarily a viewing interface. Resolution For an alternative way of viewing the reports after carrying out the steps below, refer to this document on the Community: DOC-7604 Follow the steps below to be able to view a report in webstation: 1. Create a report - in this example named  "Report1". 2. Create a time Event object and set the appropriate interval eg. daily, weekly, monthly etc. 3. Create a Report Periodical in Vista. Link to your "Report1". 4. Link the Report periodical to your time event object (created in step 2). 5. Lastly, create a hyperlink to the location where you have saved the copy of the report.  

Issue When importing an old database into a new version of Vista, right click on a Xenta Server and select "Edit" to open the Xbuilder project. (Change the version information in the property of Xenta Server. Refer to "Edit" is not available in the right-click menu for a Xenta Server in Vista Workstation.) The old XBuilder project will automatically be upgraded to match the new version of XBuilder. However, the content of the project sometimes will be incorrect after this conversion. Product Line TAC Vista Environment Vista Workstation XBuilder Cause The XBuilder version of old the database does not match the one of the new database. Resolution Install the old version of XBuilder.  One PC can install several different versions of XBuilder. The standalone XBuilder installation file can be found on the Schneider Electric Exchange Extranet under "Engineering Tools"  Keep the Vista Server and Workstation etc. at the newer version.

Issue When you select the option to view the properties of a Object nothing appears. Environment Vista 5.1.7 Cause A Remote Desktop session is connected at the same time as a local user.  Resolution To allow the properties option to be displayed, log the Remote Desktop user off. The preferred option is to set the Remote desktop session to a single user session. Remote Desktop Protocol (RDP) / Remote Desktop Connection (RDC) and I/NET has more information on how to configure a single user setup.

Issue What are the main differences between Continuum v1.94 SP1 and Continuum v2.0? Product Line Andover Continuum Environment Continuum v2.0 Cause Required a quick list of differences between the versions of Continuum to evaluate if a site upgrade to v2.0 was beneficial. Resolution The main features that Continuum v2.0 has over v1.94 are listed below. Microsoft Internet Explorer 10 32 bit support SQL Server 2012  Microsoft Internet Explorer 11 32 bit support Software licensing Support. See Software Licensing for Continuum 2.0 and StruxureWare Solution. Email SMTP Support. See SMTP Email Alarm Configuration in Continuum 2.0. Extended Custom Wiegand Card* (ACX Series Only). See Extended Custom Wiegand features available for ACX57xx controller released in V2.0. Support for new door attribute 'ValidAttempt' see New Door attribute 'Valid Attempt' added in Cyberstation 2.0 for more information. You can also find more details in the v2.0 Feature Blast. And further information on Continuum v2.0 with the links in Continuum 2.0 Product Announcement, Feature Blast, Compatibility Matrix and Installation Guides.

Issue Enable or disable I/A Series R2 alarms via a graphic page Product Line TAC IA Series Environment I/A Series R2 Cause Alarming for an I/A Series R2 alarmable object can be disabled or enabled by accessing the object's properties, 'Alarm Setup' tab using WorkPlace Pro. In most cases, the end user is not going to use WorkPlace Pro to access the system. They will normally access the system via the graphic pages in a web browser. Resolution Create program logic in WorkPlace Pro and use Binary Output objects to link to the alarmable objects via 'Flex' objects. The BO objects can be linked to a GxPage. Below are 2 examples with an Analogue Input object and a Binary Input object. Enable / disable alarm for an AI object The FlexLimitEnableBits object can be found in tridiumx > programlib > control. Link the AI 'limitEnable' to the FlexLimitEnableBits 'link'. The BO to enable / disable the high limit alarm is to be linked to the FlexLimitEnableBits 'highLimitEnable'. The BO to enable / disable the low limit alarm is to be linked to the FlexLimitEnableBits 'lowLimitEnable'. Create suitable command texts for the BO objects.   Enable / disable alarm for a BI object The FlexBoolean object can be found in tridiumx > programlib > control. Link the BI 'alarmValueEnabled' to the FlexBoolean 'link'. The BO to enable / disable to alarm to be linked to the FlexBoolean 'propertyInput'. Create suitable command texts for the BO object. Note: The FlexLimitEnableBits object can only be found in programlib module version 2.301.532d.v1. Install this to the Enterprise Server or UNC to use it. Refer to How to install an I/A Series R2 JAR File for an example of the procedure to install an I/A Series R2 JAR file.

Issue I/A Series Software Compatibility with the Windows 7 Professional Operating System Product Line TAC IA Series Environment Microsoft Windows 7 Professional operating system (32-bit, 32-bit XP Mode, 64-bit XP Mode) WorkPlace Tech Tool (WPT) 5.7 and later PSI / XPSI  4.1 MNCI 4.0 MICROFLO Balance 4.0 PSOPRIF 11.6 Tree Tech 3.1 LON Flow Balance 3.0  Cause I/A Series software should only be run on tested and compatible equipment to avoid problems with software or hardware. Resolution See Product Announcement PA-00163 for detailed information on compatibility of current I/A Series Software tools and Windows 7. (Updated 3-14-12, replaces PA-00114 with PA-00163). See I/A Series (Niagara) R2 Windows Compatibility Matrix for information on the I/A Series (Niagara) R2 compatibility See WorkPlace Tech 5.8.x and 5.9.x Operating System and Microsoft Visio Compatibility for information on the I/A Series Workplace Tech compatibility

Issue AMT messages: Ind. D/L failed & DCU Queue ovflw Product Line TAC INET Environment I/NET Site Download failed Queue Overflow Cause Failure to communicate in C-LAN and SubLan Resolution For the Ind. D/L failed message in AMT, as well as SCU Lost, is from the Host Workstation. It is telling us that there was an error in downloading individual's information to the SCU. Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication has a drawing of a simple INET network, and how it is connected with labels for the names to help with understanding and terminology. Please note the resistors mentioned and make sure your site has these. Firmware: Check to make sure the same Firmware revision for the INET version you are running is in all the controllers. The DCU7798C is experiencing communication failure. Take a moment to check this as well as from 7798C to the SCU, check the resistors which are shown in the drawing, check the wiring, firmware, etc. That will resolve this failure. If you look closely at the screen shot, it even shows this is a door controller with exceptionally poor communication to the 7798C. It shows the door points. This shows you where to start with the troubleshooting. Distance: What is the distance between the controllers? I recommend the resistors on long runs or if you have a lot of controllers. If you have more than these two or they are a long way apart, then resistors, yes. If they are 2 meters from each other and it is just these two, then not that critical. The issue appears to be with the CLAN. The pulling down the communication is producing these errors. Check to make sure the wires are protected in conduits and not running along side power or Power-Over-Ethernet, or ballasts. These items can cause interference, which can cause this failure. Earth Ground: Is the issue on one or between two 7798Cs that are wired the same way? The second 7798C is probably giving the problems. The issue is no earth ground wire on the three terminal power plug. This is the ground that is used on the CLAN comm circuit. There will be LAN Reconfiguration from ALM, the second 7798C is failing on the CLAN communications.

Issue The space temperature (nvoSpaceTemp) is displaying an invalid or default value (either 621.81 degrees Fahrenheit or 327.67 degrees Celsius). In newer versions of Vista the value will display "Invalid Value". Product Line TAC Vista Environment Vista Workstation Xenta 104-A STR-150 LonMaker NL220 Cause The option to use the STR-150 wall module with display has not been selected. Resolution If using a Xenta controller with software older than version 1.2 see STR-150 Not Compatible With Software Version 1.1 Xenta 100 Series Controllers. Otherwise, there are two ways to correct the problem: Using the Xenta 104-A Plug-In Open the 104-A plug-in. Select the General tab. Verify that the "Enable wall module with display" box has been checked. Click Apply or OK. Using Vista Workstation In the tree menu find and open the Xenta 104-A. Open the "8030" object. Locate and double-click nciAppOptions. Verify that Bit 14 has been checked and click OK.

Issue Under multiple PC environments, the time of a DCU changes automatically for a specific period. The time of the Server/Filemaster is correct. Product Line TAC INET Environment I/NET Multiple PCs environment Cause For multiple PC environments, the time setting of each PC does not synchronize. The time of Server/Filemaster is correct, but the time of Remote Client/Equalized Client may be not correct. If there is a DCU Synchronization function set on the Remote Client/Equalized Client, the wrong time will synchronize to the DCU for specific period set in the function of DCU Synchronization. Resolution Synchronize the time on Remote Client/Equalized Client with Server/Filemaster through NTP or manually. The other way is only to set DCU Synchronization function on Server/Filemaster, not on Remote Client/Equalized Client. The NTP as of March 1, 2013 no longer works. See Time sync is no longer working for suggestions

Issue Attempts to download images or object files to UNC532 controllers only partially download then fail. This is often seen in the Sigma debug window. Product Line Satchwell Sigma Environment Sigma Ethernet ARCnet UNC532 Cause Large quantities of Sigma global data can adversely affect the ability of the slower processing controllers such as the UNC532 from accepting large files due to communication timeouts.   From experience this affect has been with global levels of 600 broadcasts per minute. Resolution If there are problems on site with downloading files then checking the global broadcast rates can be achieved by; Using Wireshark to trace the Ethernet Backbone communications  (See Using WireShark to analyse communications on an Ethernet network) Email the trace to Product Support and request a global data analysis.

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.