Building Automation Knowledge Base

Issue Setting up a potentiometer or resistance input on a Xenta Programmable controller. Product Line TAC Vista Environment TAC Menta Xenta 280,300 and 400 Cause No input option is available for a potentiometer or resistance in a Xenta device Resolution A curve module can be used to create your own input lookup table, as shown below. Attached file Pot_To_0_100_R01.zip provides an example of this 10K potentiometer sample

Issue Integration to CAN bus protocol Environment I/A Series R2 I/A Series G3 Cause There is a need to integrate to devices where the available communications protocol is CAN bus.  Resolution I/A Series does not have a driver for CAN bus protocol. A third party converter / gateway can be used to convert CAN bus to a standard protocol available in I/A Series.  The following company was found after a search on the Internet. They offer solution for CAN bus to various communications protocols. http://www.adfweb.com/home/default.asp http://www.adfweb.com/home/about/about.asp   Note: Please note Schneider Electric do not endorse this product but provide this option as a workable solution. All support issues related to these products should be sent directly to their support centers.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue What is the best practice for migrating controllers from a stand alone Continuum system into an active LAN system? Product Line Andover Continuum Environment Migrating Continuum Database Cause Controllers must be migrated from a stand alone system into an existing Continuum LAN system. The ACCID of some or all of the controllers on the stand alone system are already in use on the LAN system. Resolution All address conflicts should be dealt with before the controllers are brought onto the LAN system. With the workstation in Offline mode, each controller on the Stand alone system is manually created on the LAN system.  If the controllers ACC ID will conflict with a controller on the LAN system an appropriate change must be made when creating the controller on the LAN database. Where the controllers are BACnet controllers and the intent is to have all controller on the same network, the Network ID (UDP) id must be changed to match the id of the LAN system. The Comm2 network ID of each stand alone controller should be noted and should be changed in cases where the id is already in use on the LAN system. Import files should be used to build the IP level controllers

Issue CyberStation program shows status running but current line is blank and elapsed timers are all zero. Environment CyberStation Cause Documentation Resolution Click HERE to see more information on the functionality of Cyberstation programs that are configured to run on any Workstation.

Issue Xenta Server on a remote site locks up intermittently.  A power reset of the Xenta 527 is required to bring the device back online. Environment TAC Xenta Server 511, 527, 701,711, 721, 731, 911, 913 revision 5.1.4 and earlier. Cause This Issue has been noticed in earlier firmware revision Resolution Upgrade your Xenta Server to 5.1.4 sp1 or later. Please refer to TPA-VSTA-10-0007.00 for upgrade procedure.

Issue Receiving Large Incorrect numbers in the log viewer. Environment Continuum 1.9X Windows XP Netcontroller II 9680 Cause NetController II needs updates. Resolution Go to: The Exchange Download the latest  NetController II  Flash. Edit the controller. Update OS Reload the controller.

Issue Internet Explorer 9 will not work with webClient Product Line Andover Continuum Environment webClient Windows 7 Windows Server 2003 Windows Server 2008 Cause Internet Explorer 9 isn't compatible with webclient 1.93 and below Resolution Certain versions of webclient are compatible with specific versions of Internet Explorer. Download Andover Continuum Software and Firmware Compatibility Matrix from The Exchange Download Center. Internet Explorer 9 has not been tested against webclient 1.93 or below, but there have been reports that it will not work with webpinpoint graphics. Two options to resolve: Downgrade Internet Explorer according to the Continuum compatibility matrix. web.Client v1.94 SP1 - Software (Release Date: 2013-Jul-14) for webClient 1.94 includes support for Internet Explorer 9.  

Issue Trend chart report does not show Trend Chart data Environment CyberStation Cause Maximum number of values in the report not properly set Resolution Make sure to set the 'Maximum number of values' property to include all the data in the log being plotted.

Issue TAC 200 OTP Controller replacement battery information Product Line Field Devices, TAC Vista Environment Site with TAC 200 OTP Controller  Cause On-board battery is in need of replacement, Part number - 200-1005-000. Here is additional information: TAC 200 OTP compensator and optimiser TAC 200 OTP is a compensator and an optimiser. It controls the heating via a boiler output and a mixing valve or via two stages of gas boilers. TAC 200 OTP can be operated with or without a room sensor. The controller has an easy-to-use operator's panel and needs virtually no maintenance. TAC 200 OTP is also described in the following documents, all available in English: Data sheet TAC 200 OTP C-10-31 The data sheet contains a comprehensive specification of the controller and should be read together with the handbook (part number 0-003-1148). A brief instruction A small leaflet normally placed in a slot in the operator's panel (part number 0FL-3564). User's manual TAC 200 OTP The user's manual (part number 0FL-3563) is a description for installation and start-up, packed together with the unit. The contents are a condensed version of chapter 2 in this manual and a mounting instruction. Manuals are available in TAC 200 OTP User Guide, TAC 239W DHW User Guide. Resolution Replacement battery is 342200360 CAP, .22 F 5.5V RM5 

Issue No door transactions coming into AMT Transactions are not been sent by only one door. RX and TX lights on DPU / SCU are not flashing as per other DPU's Product Line TAC INET Environment I/NET SCU / DPU Cause If you have the AMT masking set correctly and the Door Editor has transaction defined for the reader entry or exit and there are no transaction messages showing up in AMT. Then one of the issues might be the Quick Poll (QP) is turned off for that DPU.  Resolution Go to Edit > Controller > MCU Configuration Select the Station in question Is QP checked for all DPUs? Here is an example where this is not properly configured: QP needs to be checked, however, it is not possible to check or uncheck this column if the controller site is already set as DPU. Change the controller type from DPU to MR, then select OK. Go back to the Communication Statistics editor and put a checkmark in the QP box for this controller, then select OK. Go back to MCU Configuration and change the controller type back to DPU, then select OK. If the site is ever edited by any earlier version of I/NET, check Quick Poll.

Issue "Needs to be Commissioned" messages and Asterisks will not go away in Vista Classic Network Environment Vista Classic Network Cause The inability of the Asterisks and "Needs to be commissioned" to go away after a download to the controllers can be a sign that your LonWorks Network object has become corrupted. Resolution Create a new LonWorks Network object and a new port object. Move the Xenta and LonWorks groups under the new Network object. Delete the old LonWorks Network object. Move the new Network object under the existing port and rename the network to the old name. Commission and download to all of your controllers.

Issue Gaining access to doors that are in Lockdown Mode Product Line Access Expert Environment Access Expert Win 8.1 and above SQl 2012 R2 SQL 2014 Cause When doors are in this mode, access cannot be granted to anyone without special privileges Resolution To resolve this issue, the following steps need to be followed: Create a Door Group called Lockdown Go to Sys Settings and select this for Lockdown Option Create a new trigger per the screen shot and save Reboot the system for it to take effect and test the procedure.

Issue When adding points to your OPC Client from a Schneider Electric Vista OPC Server that contains points from Xenta Servers error "The item definition does not conform to the server syntax". Product Line TAC Vista Environment Vista 5.x Vista OPC Server 1.6.x Xenta Server 511-B, 731, 527, 913 Cause There are certain characters that are invalid in an OPC Server environment which are allowed in the Vista Server database. Invalid names include I/NET, RS232/485 A, and TCP/IP. Resolution Create a folder in the Vista database and create shortcuts for the points that are suffering this problem. This avoids any invalid characters, but grants full functionality for the data in question. For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue Only one Xenta Server can be installed in Vista on a single Lonworks network. Product Line TAC Vista Environment TAC Vista Lonworks Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause When a Xenta 500/700/913 is installed in Vista as a Xenta Server, it is intended to act as the Lonworks network interface for Vista. By default, the Xenta 500/700 also handles the alarms generated in devices on the Lonworks network.  Only one Xenta Server can, therefore, exist on a single Lonworks network.  To enforce this, Vista does not allow you to add a Xenta Server to an existing Lonworks network. Resolution Install the first Xenta 500/700/913 device as a Xenta Server. Install any additional Xenta 500/700/913 as Lonworks Devices on the network. As the Xenta Server handles the alarms generated in devices on the Lonworks network, the additional Xenta 500/700s must be prevented from handling alarms. This is done by changing the Alarm Server setting in XBuilder to 'Disabled'. The XBuilder projects for the Xenta 500/700/913 configured as Lonworks Devices cannot be accessed from Vista.  In A LNS environment, SNVTS will be able to be seen through Vista workstation but no XBuilder parameters. These XBuilder projects must be treated as standalone and an XBuilder project backup is managed from outside the Vista database.   For details on configuring multiple Xenta 500/700/913s in Classic and LNS networks see these manuals: TAC Vista - Classic Networks - Technical Manual TAC Vista - LNS Networks - Technical Manual TAC Xenta Server - TAC Networks - Technical Manual TAC Xenta Server - Gateway - Technical Manual

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 When setting up a Video Server the option for Pelco Type 2 (Endura) can not be selected. Environment Continuum V1.91 and above. See the Video Compatibility matrix for supported Pelco Endura products on the various Continuum versions, link: Video Matrix link Cause Continuum requires the security key to be enabled for Endura video to allow this option to be available. Resolution The Endura option cannot be purchased from the Factory.  In order to obtain the Endura option you must contact our Upgrades department. The upgrade part number is: UPG-ADD-ENDURA You can reach Upgrades by email at upgrades.continuum@schneider-electric.com Note: for testing purposes a Single User may be run in Demo mode for a few hours which will allow the Endura option to be selected.

Issue What is the procedure on transferring Continuum from one PC to another PC?   Environment Cyberstation SQL Cause Workstation hardware must be replaced. Resolution Collect information from the existing machine Backup the Continuum Database Collect all IP address, DNS server and WINS server IP information from the existing workstation. Determine if the workstation was a member of a network domain and record the domain name.  Run Continuum Database Initialization on the existing machine. Select Workstation. Record the following information. Workstation Name Folder Name Device Node ID Network ID Data Source Name Database Name User Login ID Server Name. Verify that you have the correct database User Password. Start Continuum and run PinPoint. From the View menu select Options Record the folder path indicated under Graphics (Pin Files):. Record the folder path indicated under Image:. Record the folder path indicated under Background:.  Install CyberStation on the new machine Before removing the existing machine from the network, start the new Workstation without connecting it to the network. Log on to the PC using an the Local Administrator password. Configure the IPaddress, DNS server and WINS server IP address collected from the existing machine. Disable all Virus protection software. Turn off all FireWalls (Windows 7 has three firewalls). On Windows 7 machines disable Windows Defender. On Windows 7 machines shut off SPS Software Protection Services. Install Cyberstation on the new Workstation PC Shut down the PC. Note: Do not run Continuum Database Initialization at this point. Swap the workstations Shutdown the existing workstation and remove it from the network. Connect the new workstation to the network Start the computer. Log on to the computer using an Administrator level user account. If the existing workstation was connected to a network domain, join the network domain. Verify that you have full network connectivity by pinging known ethernet addresses. Update the Continuum Database. Run Continuum Database Initialization. Select Workstation. Enter the information under Workstation using the information collected on the existing machine and apply changes. Launch Continuum CyberStation and verify that Cyberstation is working properly. Run PinPoint From the View Menu select Options Enter the pinpoint file path location collected from the existing workstation. Select the Checkbutton and verify that a failure notice (a red "X") does not appear beside any item. Apply changes. Verify that all Continuum functions are operating as expected.

Issue Standalone v1.93 system has about 1000 points being extended logged for site commissioning. There are "holes" in the extended log data. Product Line Andover Continuum Environment Standalone CyberStation v1.93 Cause Standalone v1.93 system has about 1000 points being extended logged for site commissioning. There are "holes" in the extended log data. The points are being logged at 2 minute intervals. Partner added a second (temporary) workstation to help with extended logging. This is still a standalone (SQLExpress) system. Extended log data is being extracted using Excel on the standalone server.   Even with the second CyberStation helping with the load, there are still holes in the log data. Resolution The workstations cannot handle the extended logging of ~1000 points at 2 minute intervals. Not using SQL Express on a single user even with a second workstation. See also Extended Logging gaps, performance and load balancing. This article mentions 2000 points per workstation but it is likely that this was all based on 15 minutes intervals and running full SQL Server. At 2 minutes intervals you need to gather 720,000 entries/day or 8.333 entries/sec. At 15 minute intervals you need to gather 96,000 entries/day or 1.111 entries/sec. This is a big difference. In addition, the Excel script is reading from the same extended log table being written to, at 8.333 entries/sec.   The controller log engine is completely independent of the extended log engine. The controller logs never send their data to CyberStation; CyberStation has to go get it. The extended log engine uses the general preference settings. In this case the settings are as follows and appear fine. 7. Extended log database check interval (minutes): 5 8. Extended log maximum LAN buffer interval (minutes): 30 10. Extended log automatic purge interval (days): 5   CyberStation is constantly trying to gather data from logs well before the “deadline” when the log fills and is about to be overwritten. While doing this, CyberStation also has to monitor time in the controllers, to make sure it is not too far out of sync, and this may potentially take place on field bus controllers on many network controllers, which may even be in different time zones. It also has to know when controllers have gone offline, or for some reason extended log values have not been updated. In this case, CyberStation must try to play catch up when the controllers come back online (remember, these offline controllers have most likely continued to log data). And the same “catch up” has to take place if one or both workstations are turned off, or are busy doing other tasks like running reports or polling points via Pinpoint or Listviews. The bottom line is that the CyberStation extended log data collection engine is sophisticated and complicated. To get a sense of this run AccTrace.exe (in the \Continuum folder) on a system busy with extended logs and you'll see it firsthand.  When a SQL Express system with one or two workstations is trying to collect the logs and do everything else that CyberStation does (listviews, reports, schedules, pinpoint, etc), at times, some data may get dropped. The recommendation at this site was to lighten up the CyberStation load by changing the log interval to 15 minutes and monitor if the extended log holes get eliminated.  

Issue Instead of logging a value on a set time interval, can I only log the value when it changes? Product Line Andover Continuum Environment Logging - all controller types. Time Interval = 0 Log value on change. Semi Automatic logging. Cause When working with strings, date times or Plain English comms drivers, it is often required to only log a value on change. How can this be achieved? Resolution Create the point in the usual way. On the "Logs" tab, enter the number of log entries required. Select "Log Instantaneous." Leave all of the Time intervals at 0. The controller will now log a new value every time the point value changes and all log entries move down 1 position. This is often called Semi Automatic logging. Note: This logging method is not related to time in any way, however creating an Infinity DateTime point and writing to that with the Date system variable when the point is updated would allow the time / date of the change to be recorded.

Issue Access denied and/or insufficient access errors reloading CX9680 or ACX2 (5720/5740) The above typically happens following an uprev of the controller FW to a different version. Product Line Andover Continuum Environment CyberStation CX9680 ACX5720 ACX5740 Cause RAM Memory issue due to the difference between the two builds, this problem will be addressed in future releases of the FW A similar warning can be seen if an XDriver is not correctly loaded. (Xdr may be referred to in the Distribution Properties page) Resolution Remove the battery Power down the controller, wait 5 minutes to make sure RAM is fully erased. Power up and reload the controller once it is online. Or reload the XDriver correctly first