Building Automation Knowledge Base

Issue Lost NL220 dongle Product Line TAC Vista Environment NL220 Cause Lost NL220 dongle. Resolution Unfortunately, we cannot offer replacement dongles for the NL220 software. The licensing of the software is actually handled by the dongle. The only way we have to replace them is with a new order with Newron Systems. Sometimes rehosting the new dongle does not work. Unable to host a replacement NL220 dongle for a lost dongle contains information that may help if this problem occurs.

Issue When you add a new Xenta controller to a LNS system you get the SNVTs assigned to another controller already in the system. Product Line TAC Vista Environment Lonmaker NL220 Menta Cause The new controller had a program ID that is already in use in your LNS system. In large LNS systems it is possible to get two program ID that have been randomly generated to have the same ID. Resolution If your Xenta controller displays the SNVTs from an existing controller in your LNS system follow these steps to correct the issue. Delete the new Xenta device you have added to the system In the Menta application for the Xenta device select (Options - Program specification) and take note of the program ID If you have a NL220 System use this NL220 Program ID Check.pdf to check for and correct a duplicate Program ID If you have a Lonmaker System use this Lonmaker 3.2 Program ID Check.pdf to check for and correct a duplicate Program ID Changing the ID is documented in How can two controllers of different types be assigned the same program ID?

Issue Get Authentication Mask The entire Disk RTI subsystem is damaged. Please consult the software provider. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Unspecified, but a PSU-specific fix file is the only way to correct the situation. Resolution Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. The following is for informational and archival purposes only. PSS does not have the ability to provide this file to our customers. Contact Product Support and provide the PSU ID. A PSU-specific fix file will be generated and sent back via email. Install the fix file Install the original .plf file again. Exception: If the fix file cannot be installed, make sure that the PSU ID printed on the sticker matches the PSU ID that it presents itself when running Dongleutil. If they do not match, see Error "License run-time information is damaged. Contact software vendor. PSU ID: XXXXXXXX PSU Type: Unknown subfamily: 255".

Issue How can a new Source website account be obtained? Product Line TAC IA Series Environment Repository for all I/A files from legacy programming tools to new released versions or updates of Niagara and WorkPlace Tech Cause New employee of a Schneider Electric branch or partner Resolution The Source has been deactivated and all files have been migrated to The Exchange. Navigate to The Exchange Extranet and register for a new account. For more information on registration, see Register for The Exchange.

Issue How to configure I/NET Tools to link to an Internet URL. Product Line TAC INET Environment I/NET Seven - Windows XP or Windows 7 Cause Requirement to open a specific URL from an I/NET graphic page, without setting this as the default homepage (in Internet Explorer). Resolution There are a couple of ways you can do this:  Create a shortcut as follows (Works in Windows 7 operating system):  Open Windows Explorer and browse to the location you wish to create this shortcut. From this nominated file location create a shortcut (Right-click > New > Shortcut): Within the Create Shortcut dialog add the URL (e.g. www.google.com) Name the shortcut and select Finish: Now browse this new shortcut into I/NET Tools > Define Tools (for information on how to do this refer to User Definable Buttons and Tools) In some cases when performing the above on a XP machine you can get and an error indicating file association which can be configured in your Control Panel Folder options, alternatively you can create a batch file (This info is also in the Online Help file for I/NET) - duplicated below:   The following example describes how to create a tool that will open http://www.msn.com in your system's default web browser.  Using Notepad, create a new text file and type the following line of text: start http://www.msn.com Save the file to your PC as OpenMSN.bat. Add a new tool, select the OpenMSN.bat batch file that you just created.

Issue How do Controller LANs connect to Host LANs? Product Line TAC INET Environment I/NET Site Cause Understanding network architecture can help design and servicing of networks. Resolution Controller LANs connect to Host LANs through Link Taps. (TCON209, 1-5). Refer to Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication for further explanation.

Issue Adding a Xenta Server to a Vista System for I/NET to Vista Integration Product Line TAC INET, TAC Vista Environment I/NET Vista Xenta 527 I2V Cause For systems with both I/NET security and Vista HVAC, this allows for a single point to monitor alarms. Resolution At least one of the routers on the I/NET system must be a Xenta 527 Web Server. Start Vista Server Open Vista Workstation Right click on the Vista Server object and select New>Device>Xenta 527 Name the Device Right Click on the Xenta Server Object and select Edit. XBuilder will open  If your 527 already has an XBuilder Project File   Select Project>Get From Target Enter the IP address of the 527 and the root password Select Get the Full Project Click on the I/NET object and verify settings have imported   If your 527 does not already have an XBuilder Project File Click on the TAC_Xenta_527 root object in the Network Pane Add the TCP/IP and SMTP settings as required Click on the I/NET object Add the I/NET link information and reference hosts Right click on the I/NET object and select Insert TAC I/NET Network Click Add Files Add all save files for that link Click Ok Select Vista Database>Save   You will need to repeat this process for all I/NET links to have full I/NET integration into Vista. See Additional settings necessary to receive Vista Alarms from an I/NET point to configure Alarms.

Issue How to share the thermostat data (room temperature, setpoints) among Xenta 102-AXs? Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX with or without plug-in Cause Using the wrong SNVT in Xenta 102-AX or sending the nvoEffectSetPt incorrectly will result in different unit behavior among Xenta 102-AXs. Resolution Assign the Xenta 102-AX wired with the thermostat to be the master (A), and other Xenta 102-AXs to be slaves (B to N). Use the built in SNVTs to transfer data from the master to slaves as shown in the diagram below. Sharing space temperature Bind master's nvoSpaceTemp to slaves' nviSpaceTemp. Make sure set Node Minimum Send Time and Node Send Heartbeat to be a non-zero number. (Read more information in Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller.) Sharing setpoint It is recommended to share the setpoint through the normalized nvoEffectSetpt in order to have the same unit behavior between the master and slaves. Read more information about how the nvoEffectSetPt is calculated and displayed in Xenta 102-AX Effective Setpoint (nvoEffectSetPt) Calculation. The steps of sharing the setpoint among Xenta 102-AXs are listed below: Set occupied/unoccupied heating and cooling setpoints on the master and slaves. The suggestion is to use the same setpoints setting on the master and slaves if want all rooms to operate in the same manner. In Xenta 102-AX plug-in Select Operating Parameters tab. Set the Cooling Setpoint and Heating Setpoint to desired value Without Xenta 102-AX plug-in Find SCPTsetPnts under VAV_Controller. Set the Cooling Setpoint and Heating Setpoint to desired values.   Set master's nviSetpoint under VAV_Controller to a desired temperature (eg. 72 °F or 22 °C).   Set the nvoEffectSetpt to be normalized. In Xenta 102-AX plug-in Select Operating Parameters or I/Stat Configuration tab. Under Effective Setpoint Source choose Norm of Heating and Cooling Setpoint Without Xenta 102-AX plug-in Find UCPTvavSelection.ESS under VAV_Controller Set UCPTvavSelection.ESS to 1. (Default is 0: Actual Setpoint).   Bind master's nvoEffectSetpt to slaves' nviSetPoint.   Make sure set Node Minimum Send Time and Node Send Heartbeat to be a non-zero number. (Read more information in Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller.)   Additional Suggestions: If the number of slaves is more than 30, it is better to tier up the transaction as shown below.

Issue What Xenta hardware is officially UL 864 listed? Product Line TAC Vista Environment Xenta UL 864 Cause Many consulting engineers would like documented proof that the hardware within a smoke control system is UL 864 tested and approved. Resolution The Schneider Electric Xenta UL 864 case file, outlining exactly what Xenta hardware is approved for UL 864 systems can be obtained at: www.UL.com Navigate to the bottom of the home page under Resources links and click on Online Certifications Directory Find the UL File Number field and type s5393 The Schneider Electric Xenta file will show up and click the link UUKL.S5393 under the link to file column. This will show you all of the Xenta hardware that is UL 864 certified, and can be installed in an official smoke control system. For more information, see UL Listings for Xenta Product Line.

Issue When downloading the Menta file to a Xenta 300 controller, an error "No such Entity" happens. Product Line TAC Vista Environment Vista Menta Cause Looking into the Menta file, it seems that there is over-limit of work area of Menta.   The Menta application is not so complex. There shouldn't be such problem. The problem is due to so many time schedule entries for each time schedule block.   Each time schedule entry will occupy some memory of the controller. There are multiple time schedule blocks in the application. That's why the work area will exceed the limit. Resolution Decrease the Max. entry number of each time schedule block to 1 or what you need. Then download the application file to Xenta controller. For more issues about "No such Entity", please refer to Vista Workstation Error: 'No such entity' in value column.

Issue Cannot see an NPR across a wide area network (WAN) Product Line TAC INET Environment NetPlus Router (NPR) Wide Area Network (WAN) Cause There are several reasons why this may occur: The Cisco/3Com/etc. routers are doing network address translation (NAT) The network uses Variable Length Subnet Masking (VLSM) and the routers use Classless Inter-Domain Routing (CIDR). See the other FAQ on this.  The correct reference host is not specified in the configuration profile. The correct reference host is specified, but that profile was not set to active. The wrong subnet mask was used. Resolution For issues with VLSM and CIDR (Cause 2 above), see Can NPR 2000s be installed on a network that implements VLSM and CIDR. In any other case, see Customer Advisory 2003.

Issue Time Schedules link page grayed out in Xenta 555/731 Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta 555, 731 XBuilder Cause To correct a earlier issue with read only access in Xentas running 5.1.0 and previous releases "TAC ACCESS” has been added to the URL property of the link page. With XBuilder 5.1.0 and prior, it looks like this: URL = /wm/micronet/timeschedulethisnode=Time_schedule_01_.2.2.TS.102.56.0.129;itemname=Time schedule 01 With XBuilder 5.1.1 and later, it looks like this: URL = /wm/micronet/timeschedule?thisnode=Time_schedule_01_.2.2.TS.102.56.0.129;itemname=TACACCESSTime schedule 01 Resolution To update the link, re-drop the time schedule on the link and the link page will then operate correctly. If your time schedule link page is still grayed out also see What to check when viewing your Xenta 555 webpages and finding areas/pages grayed out.

Issue There is often a requirement to pass live data values between a Continuum and a Vista system, how can this be achieved? Product Line Andover Continuum, TAC Vista Environment Continuum BACnet systems Vista LONMark systems LON XDriver, X Driver, X-Driver, Bridge, Gateway Cause Continuum and Vista inherently use different open protocols. Resolution One method of passing data between a Continuum and Vista system would be to use a Netcontroller II with the FTT option, then load the LONMark XDriver. This will allow you to pass analogue and digital data between the two systems using SNVT's. You would then use LONMaker to bind the Continuum X Driver points to the Vista / Xenta points. See the LONMark X Driver manual for configuration details. Also reference Can LONMark Devices be used with Continuum? for further details. Another option would be to use a Xenta913 as a gateway to the BACnet IP network used by Continuum, this would also allow analogue and digital BACnet point types to be exchanged between the Xenta913 and Continuum Workstations or BACnet bCX1 controllers. Both of these methods use the gateway principle to pass data between the systems, this will require corresponding points being created in both systems with associated mapping / binding between them.

Issue How to estimate the amount of equipment needed for a LNS Vista system? What are the recommendations and limitations for LNS Vista system? Product Line TAC Vista Environment LNS database TAC Vista Loytec L-IP NIC852 Cause It is very important to plan ahead when designing an LNS database in Vista in order to have a stable, robust system. Listed here are some recommendations for LNS database in TAC Vista. Resolution One LNS database can support up to 3000 devices.  Each channel can have max. 100 devices (with repeater). Use one L-IP per building or do not share devices among buildings under one L-IP. Otherwise, need to run the FT-10 wire between buildings. If possible, create one LNS database per building. This is easier for trouble shooting and maintenance purposes. Then, use a NIC852 in order to manage multiple LNS database in one Vista Server. Follow the rules as below: Without NIC852, one Vista server can only take up to 4 LNS databases. (With large LNS database, number will decrease.) NOTE: NIC852 is not required in this case, but recommended for large networks in order to achieve better performances With one NIC852, Vista server can take up to 7 LNS database. (There are 8 ports on NIC852, but Vista server takes one.) One Vista sever can take up to 4 NIC852. Therefore, one Vista sever can take up to 31 LNS databases. (Suggestion: do not extend 30 LNS databases, and better keep the number under 28.) If additional Vista servers are required, a multi-server system can be used.  (It is recommended to not use more than 10 servers together for best performance.) For Xenta Group and Xenta programmable controller specifications in a LNS database, please read Xenta Group and Xenta Programmable Device specifications for an LNS system.

Issue Web pages that previously worked now just get a blank page Product Line Andover Continuum Environment 9680 BCX Cause A change has been made to the 9680 configuration that is affecting the processing of the web pages. Resolution First check the controller error log for evidence of a specific issue. Check to see if the html code can be accessed from another PC. If the html code can be accessed then refer to Unable to open config pages on a web enabled controller that previously worked in order to address the issue with the PC that is not working. Note: If a node has been added to the controller, but it is a 0 node controller, it can cause the html pages to not work because it is taking up controllers cycles to deal with the mismatch of the hardware and software.

Issue Need information about options for integrating I/NET with the Vista Product Line Product Line TAC INET, TAC Vista Environment I/NET Vista Xenta Server Xenta 527 Cause There are several possibilities with using Vista and I/NET products on the same site: You can use a 913 as a bridge between Modbus, Bacnet, or LON to write values to an existing I/NET controller You can use a 527's built in features to function as a web server, displaying I/NET alarms and points on Values pages You can use Vista Workstation with I/NET host Tool as the front end for I/NET This article focuses on connecting an existing I/NET system to Vista using the Xenta 527 Web Server Resolution Verify that you are using at least 1 527 Web Server on the I/NET site If you are using an older version of I/NET and about to install the newest version of Vista, upgrade I/NET to current revision Install Vista Install the I/NET Host tool. (available online, or on the I/NET CD) Start Vista Server Start Vista Workstation Start the I/NET Host Tool (note that you should be able to connect to controllers, edit individuals, and access all aspects of your existing database) Note that once the I/O server starts up you will be able Right-click and access the same features as though you were running I/NET. This is the same program running. In Vista Workstation, add a Xenta 527. Right Click and Edit it XBuilder will open with a new project File In the Network Pane, Expand the IP Backbone Click on the Xenta 527 Object Configure the TCP/IP settings of the Xenta 527 to match your existing Xenta 527 Web Server Expand the Xenta 527 Object Click on the I/NET object Configure the settings to match your existing Xenta 527 Web Server The SQL Host number needs to match the Host number of the computer with primary access database. Configure any other settings that are in use in the existing 527 Web Server (SMTP settings, etc.) Click Project> Generate. Check the Output Pane to ensure there were no errors Click on the ICON of the space shuttle to send the project to it's target When prompted, Choose to use the projects information over the target information. Close XBuilder In Vista workstation You can now view events from I/NET in the event Window. If you have any issues with I/NET events, and you have full version of I/NET open AMT and insure they are coming through there first. If not see AMT not receiving Data.  If you are running I/NET Host tool, you can view I/NET event by browsing to the 527 in Internet Explorer and viewing the I/NET events. Host masking can also be set for the 527 in the web browser. You should receive Full individual information for all Transactions (first, name last name, etc.) You can see this in Vista and by connecting to the Xenta 527 through your web browser. If you do not see this, ensure you are using this correct SQL Host number. You can control I/NET points directly through the Vista Tree structure or by Selecting Tools>I/NET Host Tool *The Bridge between I/NET and Vista is created using the 527. This must be the Xenta 527 not the Xenta 527-NPR (see Xenta 527 Part Number Reference) For information about setting up I/NET alarms in Vista, see Additional settings necessary to receive Vista Alarms from an I/NET point

Issue Trying to order a controller part number that has been discontinued due to low volume sales / duplicate part numbers. Product Line Andover Continuum Environment Continuum IP level Controllers NetController II Series bCX1 Series ACX Series Cause Discontinuation of duplicate and low volume parts has removed a number of previously existing part numbers from the Continuum catalog. These parts are still available but will need to be ordered as a base unit and then upgraded through Repairs. Resolution The IP level controllers were part of a roll up of the product numbers where low volume part numbers were discontinued. These parts can still be obtained but will need to be chosen from the list of available parts and then get an upgrade through Repairs to add the additional features that may be required. See Active Network Level Controller Part Numbers, and Discontinuance of Low Volume Part Number Configurations - Andover Continuum - PA-00269A on this which includes the currently available part numbers. To order a BCX1-CR-127-SA part which is no longer available, you will need to order the base unit BCX1-CR-127 and then have Repairs add the -SA (SNMP) option to that controller. Note: for further Continuum parts that have been discontinued see What Continuum products have been discontinued?.

Issue Vista Server restore database fails Product Line TAC Vista Environment Vista Server Cause The Restore Database function will not work on the database directory that Vista is currently using. The restore is being performed on a directory that has files that are flagged as read only. The backup file may be incomplete. The backup file may be corrupt.  Resolution If the Vista Server restore database function is not restoring the database then it is probably one of the problems listed below. The Restore Database function will not work on the database directory that Vista is currently using. To restore to your normal database directory, use Server Setup to point Vista Server to a different database directory. Then start Vista Server and perform the restore. The restore is being performed on a directory that has files that are flagged as read only. These files cannot be written over until this flag is removed. This can be caused inadvertently with database transfer as described in Transferring a Vista Database from one computer to another. The backup file may be incomplete. Maybe it was copied to portable media (CD, USB drive, etc.) before it was finished. To test whether the database backup file is incomplete, restore to an empty directory and open it with Vista Server to examine it for missing objects or to see if it launches at all. The backup file may be corrupt.  This is the case if the following error message (or similar - this is from a Spanish system) is seen:   The database MAY be salvageable.  Send the backup file to PSS who will attempt to fix it, with help from R&D.  There are no guarantees - only do this if you have no other recent healthy backups to restore. It is always recommended to take regular backups.

Issue What is the maximum distance between SC3000 relay pack  and SE7300 controller Product Line EcoStruxure Building Expert Environment SC3000 relay pack SE7300 controller Cause Depending on installation and site configuration, the max distance between units may be of interest. Resolution This hasn't been tested, but at least 100 ft (30 m) with 22 GA or bigger wire. For additional details, also please see Which models of the SE7300 series room controllers can be used with the SC3000 series relay packs?

Issue Problem with redirecting a $EE_Mess alarm using "Configure alarms" in the Vista server. The alarm is not redirected to the new alarm object and therefore not changing the priority. Product Line TAC Vista Environment TAC Vista Server 5.1.6 Cause $EE_Mess should be redirected to message object in Vista. A change of state should be redirected to another change of state object in Vista Resolution Redirect the $EE_Mess to a message object in Vista and not to a change of state. Refer to How to redirect a offline alarm to a certain alarm control object in Vista? for a guide on how to create a system alarm to handle offline alarms