Building Automation Knowledge Base

Issue "No license for LonWorks communication" with TAC Vista Server LE Product Line TAC Vista Environment TAC Vista Server LE (LE= Limited Edition which has no Webstation or multiserver functionality) Cause If TAC Vista Webstation is installed on a TAC Vista Server LE machine, Lon communications will not work correctly. It will work for 10 minutes then an alarm message appears, "No license for LonWorks communication," and all communication with the Lon network will stop. Resolution Uninstall Webstation Related Articles: "No license for LonWorks communication" error when using a non LE dongle. "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network. "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue What is the format of the SNMP alarm traps and where can I obtain the MIB's Product Line Andover Continuum Environment Netcontroller II CX9680, bCX1 & ACX57xx with SNMP alarming enabled. Cause Documentation on the SNMP Alarming is required. Resolution The Configuration guide for SNMP Alarming can be downloaded from The Exchange Download Center, link: Andover Continuum v1.9 SNMP Configuration Guide This will detail how the SNMP alarming is configured and operates. The SNMP Alarming sends the same alarm messages as shown in the Continuum alarm viewer out to the third party system via SNMP traps. The format of the traps is defined by Management Information Blocks (MIB's) these can also be downloaded from The Exchange Download Center, click on the following link: SNMP MIBs There is no facility to change these formats within the controllers or Continuum

Issue Import/Export in TAC Vista Workstation does not work. Nothing happens when trying to start the import/export. Environment TAC Vista Cause The $DatabaseExport and $DatabaseImport objects in the Vista database has been removed, probably during an upgrade. Resolution In the instructions below, we assume that TAC Vista is installed in the default location. Replace the version number (5.1.6) with the actual version you have installed, and the Vista Server name (VistaServer) with the actual name of your Vista Server. This procedure requires that TAC Vista Server is running as an application, and not as a service. 1. Make sure TAC Vista Server is stopped -- First we need to change a file to allow creation of these objects -- 2. Browse to C:\Program Files\Schneider Electric\TAC Vista 5.1.6\$cfg 3. Find a file named "objtmpl.cfg", make a copy, just in case. 4. Edit the file with notepad and find the strings FI_EXPORT and FI_IMPORT. 5. Remove AB on each of the two lines, (stands for abstract object), save and close. 6. Browse to the TAC Vista database folder, and open the folder $thisdb. 7. Change the name of the file TacVista.cfg, to TacVistaOld.cfg 8. Start TAC Vista Server. -- Now we need to create the missing objects -- 9. Open the testclient (testclt.exe) located in the folder C:\Program Files\Schneider Electric\TAC Vista 5.1.6 10. In the menu, click "Session-->Log in" 11. In the menu, click "Services-->Create" 12. In the ID field, write "VistaServer-DatabaseExport" and in the type field write "FI_EXPORT" 13. Click "Create". 14. In the ID field, write "VistaServer-DatabaseImport" and in the type field write "FI_IMPORT" 15. Click "Create". -- Now we have to change the name of the created objects to $DatabaseExport and $DatabaseImport -- 16. In the menu, click "Services-->Access" 17. In "Enter ID:" write "VistaServer-DatabaseExport.$name" 18. Click "Request" 19. Write "$DatabaseExport" in the "New Value" field, and click "Poke". 20. In "Enter ID:" write "VistaServer-DatabaseImport.$name" 21. Click "Request" 22. Write "$DatabaseImport" in the "New Value" field, and click "Poke". 23. Reenter AB on each of the two lines in "objtmpl.cfg" previously edited in step 4, save and close.  

Issue The output of the actuator block in a MNB-Vx sometimes shows 'NaN' (Not a Number) instead of a valid position. The only way to clear it is to drive it fully open or fully closed. The issue is intermittent and it is not specific to the same installed controllers. It appears on different controllers at different times. Product Line TAC IA Series Environment MNB-Vx Cause The actuator can be initialized to avoid displaying 'NaN'. The setting in the VAV actuator block is called InitMode. Here's a description of this setting from the WorkPlace Tech Engineering Guide Supplement (F-27356): Abbreviation Configuration Property Description Range InitMode Initialization Mode Class: Enumeration - The initialization mode configuration property controls synchronization of the VAV object position output after a rest. 0 - No automatic synchronization of the position output. Synchronization occurs when normal control causes the actuator to drive full open or full closed. 1 - Actuator drives full closed after a controller reset to synchronize position output 2 - Actuator drives full open after a controller reset to synchronize position output 0-2 If InitMode = 0, and the actuator doesn't drive full open or full closed for a long period of time, the NaN value will continue to be displayed. Resolution Ensure InitMode is set to either 1 or 2 so that it synchronizes after a power cycle or database download.

Issue Can expansion boards P8UI4AOC and P8UI4AOV be used with a 7718? Product Line TAC INET Environment I/NET Seven P8UI4AOC Expansion Modules P8UI4AOV Expansion Modules 7718 Process Control Unit (PCU) Cause In addition to the eight inputs and eight outputs on the base card, the 7716 supports the control of additional relay outputs and the monitoring of additional AI, DI, and PI inputs connected via the expansion port. These inputs and outputs occupy point addresses 0100 through 0107. Due to address limitations of the 7718, these expansion boards are not compatible with the 7718. Resolution Expansion boards P8UI4AOC and P8UI4AOV cannot be used with a 7718. Refer to 7718 Process Control Unit - TAC INET - Installation Guide TCON106 regarding supported Expansion Modules.

Issue Cannot open a file from TAC Vista Webstation from a TGML graphic Environment Vista IV TGML Webstation graphics Workstation graphics File access Cause  The "OpenFile" command doesn't work in a web browser. Resolution For an alternative way of viewing the reports and other files, refer to this document on the Community: DOC-7604 Guideline on how to open the same file in both TAC Vista Workstation and TAC Vista Webstation. To achieve opening a PDF or DOC file from a TGML graphic both in TAC Vista Workstation and TAC Vista Webstation, typically in workstation there's no problem. Use the "OpenFile" button, and the file should open. "OpenFile" button function in Webstation is not the same.  The "OpenFile" command to open the document from a button in a TGML graphic doesn't work in a web browser.  To open a file from a dynamic TGML graphic in Webstation Define a "Hyperlink" in TAC Vista. Direct the hyperlink to a document located in the "C:\Inetpub\wwwroot" folder on the server. Call the hyperlink with http://ip_address/docName.   Typical graphic behavior Opening a PDF document: Can be viewed in Workstation. Can be viewed in Webstation, but will not open in a new window even defining target as _blank. Opening a DOC document: Can be viewed in Workstation, but opens an "extra" window which must be closed after viewing the document. Can be viewed in Webstation.

Issue BACnet controller objects that have not been overridden are displayed on I/A Series R2 graphic screens in the purple color as if they were overridden. Environment I/A Series R2 (Niagara) Graphic screens displaying values representing physical BACnet controller inputs. Cause Purple BACnet values (I/A Series R2 graphic override color) are internal BACnet points that can not be modified (display only).  This behavior is normal and began to appear in MNB controller firmware versions 1.2 and higher.  Per the BACnet specification, read-only type points must be set to indicate an override condition.  The root cause is a design change required by the BACnet specification to bring the controllers into compliance for BTL certification.  The ASHRAE BACnet Specification 135-2004 specifies that the "read-only" type objects (e.g. Analog Value, Binary Value, etc.) OVERRIDDEN flag is: Logical TRUE (1) if the point has been overridden by some mechanism local to the BACnet device.  In this context "overridden" is taken to mean that the Present Value property is not changeable through BACnet services. In this case, the override is meant to indicate to Niagara that the point is locally overridden (by the controller) and cannot be changed by the Niagara BACnet service (or user). Resolution There are several approaches that can be used to display these objects without the background showing the purple color. One approach is to use a native Niagara AI object to buffer the value where the override condition is not transferred.  In addition, if the BACnet points and Analog Input objects reside in a poll-on-demand container, the BACnet points will not be polled unless a gx type object is added and directly attached to the BACnet point.  The graphic page will have a gx type object linked to the Analog Input object (displaying the value without the override) and another gx type object (invisible) linked to the BACnet point to start the point polling. A second approach is to configure the GxText object so that the object property "statusColorEnabled" is false. 

Issue Material specification for stainless steel sensor pockets Product Line Field Devices Environment Sensor pockets Cause Some customers require a specification on the material used for the sensor pockets in stainless steel. Resolution Our stainless steel pockets are manufactured from V4A material (1.4571). - material constants: 1. VA   Material No. 1.4571   EN symbol (short) X6CrNiMoTi17-12-2   AISI/SAE 316 Ti   UNS S 31635   AFNOR Z 6 CNDT 17.12   B.S. 320 S 17, 320 S18, 320 S31   alloy —   Registered work's label —   Standards VdTÜV 454     Chemical composition C Si Mn P S* Cr Mo Ni Ti ≤ 0,08 ≤ 1,0 ≤ 2,0 ≤ 0,045 ≤ 0,015 16,5–18,5 2,0-2,5 10,5-13,5 5 x C ≤ 0,70                   * for long products S ≤ 0,30; for products to be processed S = 0,015–0,030                           Special characteristics Temperature range Dichte kg/dm³ Hardness HB 30 up to 550° C 8 ≤215  

Issue .DAT files and what their purpose is. Another good practice for the Removal of the "DAT" files is this:  Anytime a Tech goes to a site, it is wise to remove all the "DAT" files Prior to attaching a Laptop to a new site. This way you will not corrupt this site routing tables with bogus IPs and Links.  Environment I/NET site with profiles, DLA or non DLA architecture DAT, .dat, profile,  Cause Profile corruption or Reference host issues can be resolved by renaming and then recreating the .DAT file. Resolution .DAT files contain the routing table that the Netcon gets the data from. Profiles: The I/NET Configuration program allows you to specify and save more than one set of configuration specifications. These specifications are called profiles. The majority of host workstations only require one profile. However, multiple profiles are useful if you work with several different TAC I/NET Seven environments, because you can change system parameters simply by selecting a different profile. Most of the configuration parameters are saved in the system registry and IP routing information specific to each profile is stored in a .DAT file. Note: There may be differences in the routing data for each configuration profile; consequently, you should not change configuration profiles in a stable TAC I/NET Seven network. Reference Hosts A host workstation, NPR, or Xenta 527/527-NPR must have knowledge of the other devices on the network in order to communicate with them. This knowledge is stored in what is commonly called a routing table. A routing table will contain the IP address of the devices known to the host workstation. When the host has data to route to another TAC I/NET Seven device, it uses the addressing information contained in the routing table to determine the destination path. I/O Server stores the routing table in a .DAT file.

Issue When opening LonMaker the LonMaker Menu list is not shown in Visio. Product Line TAC Vista Environment Echelon LonMaker 3.xx Microsoft Visio 2002, 2003, 2007, 2010 Microsoft Windows XP SP3 Cause Echelon LonMaker was not installed with Administrator rights or some of the default security settings have been changed. Resolution Older versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Go to the Tools menu > Options and then select the Advanced tab. Click the File Paths button. (For LonMaker 3.1, go to Tools > Options > File Paths) In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. The next setting to check is the Macro Security. Go to the Tools menu > Options > and then select the Security tab. Make sure that all of the below options are selected. Enable Microsoft Visual Basic for Applications Enable Microsoft Visual Basic for Applications project creation Load Microsoft Visual Basic for Applications projects from text Enable COM add-ins Enable Automation events   Newer versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > All Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Select "Options" on the left hand side of the window. Click on the "Advanced" section and scroll down to the bottom. Verify that the "Enable Automation events" box is checked. Click on "File Locations..." In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should be DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. Uninstall LonMaker and reinstall with the administrator account used to log into Windows. The following articles have information about another problem that can cause the same issue: Visio menu not displaying properly after installing Lonmaker 3.1 with Visio 2002  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"  There are two other things you may try before uninstalling, that have solved the issue in some cases: Right-click any toolbar, Choose Customize > Toolbars tab, Choose the Menu Bar, Choose Reset Remove all registrations in the Tools menu, click Options, and then on the Advanced tab, click File Paths.

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 for assistance. Issue Seeing multiple losses of functionality starting to occur, such as controllers going offline, browsing with the client being slow, reports failing to run and events not being logged. Product Line EcoStruxure Security Expert Environment Security Expert SQL Server Cause In SQL Server the SecurityExpertEvents database has a very large LOG file ( hundreds of gigabytes) resulting in degraded performance in SQL and Security Expert.   The Recovery model of the SecurityExpertEvents database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size. Recovery model full New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution Reduce the size of the log file and prevent it from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpertEvents database from Full to Simple in SQL Server Management Studio. To do this, right-click on the SecurityExpertEvents database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery model simple Right-click on the SecurityExpertEvents database and select Tasks > Shrink > Files Shrink files In the Shrink File - SecurityExpertEvents window, change the File type to Log. Shrink log file Click OK Repeat steps 2-5 for the SecurityExpert database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue Running Windows XP, Service Pack 2 and I/NET Seven Configuration Instructions Product Line TAC INET Environment I/NET Site running XP Cause Windows XP Service Pack 2, it will be necessary to configure the Firewall feature which is on by default in the Service Pack Resolution Please see the following link to configure XP to allow I/NET Seven file equalization to function properly. XP SP2 Configuration and InetSeven.doc

Issue I have an I/NET 2000 system with ID Works Version 2.xx. How do I convert this ID Works Version 2.xx Project to run on I/NET Seven? Product Line TAC INET Environment I/NET 2000 site Cause I/NET 2000 system has been upgraded to I/NET Seven. Resolution Please see attached Document Link: Conversion of I/NET 2000.doc

Issue What are the differences between Standard Continuum Import/Export and Continuum BACnet COV? What issues can arise from programming a Bacnet system if you are using the Continuum Import/Export concepts. Product Line Andover Continuum Environment Standard Continuum Import/Export Continuum BACnet COV Cause Information on Continuum import/export and BACnet COV concept to help select the method that meet the environment. Resolution Using standard Continuum import/export where one or more controllers reference a point from another controller creates a relationship in the controllers such that whenever the exported value changes (or exceeds the threshold setting), the point value will be sent out in a broadcast to the network and the controllers that are looking at that point will intercept this single broadcast message and use the new value in their programs. It is very efficient in that no matter how many controllers on the network require a point value from a single controller, only one export message is required. The down side of that is that if there was a network interruption when the message was sent, one or more of the receiving controllers may miss the data update. For critical data exchange, especially if the value rarely changes, such as a schedule point, the use of a refresh program should be used to occasionally retransmit the value by setting the refresh attribute of the point to true. BACnet utilizes Change of Value (COV) data sharing. The main difference here is that for every controller that references a point from another controller, an individual subscription for that point is registered in the exporting controller. So if 10 controllers wanted the same point exported from one controller there would be 10 subscriptions made to that controller. When the point value exceeds the COV Increment (which is equivalent to threshold) there are 10 individual point to point messages sent to the 10 subscribing controllers. The benefit here is that the delivery of the data to all the subscribers is guaranteed. The down side is that there is much more traffic on the network and much more strain put on the exporting controller. Although the data exchange is very reliable, if you were, for instance, to have an MSTP controller possess a global OAT sensor, and 100 other controllers wanted that value exported, every change in value would require 100 point to point messages to send it to the 100 subscribers. MSTP devices default to a Max_Info_Frames of 2, which means that the controller can only deliver 2 of these messages when it gets a chance to talk on the network. The MSTP controller only gets a chance to talk after every other controller on the network has had a chance to, plus the BCX controller which is interlaced between each MSTP controller when using enhanced MSTP. So, if there were 100 MSTP controllers on the network, the exporting controller could only send updates to two of his 100 recipients every 200 token passes on the MSTP network. The data would get backed up, especially if the value was frequently changing, so the updates may never get out. If this amount of data sharing is required in BACnet, the best method to perform it would be to first set the COV Increment to a reasonable number to limit the amount of exports required, and then map the point in one or more BCX level controllers which have much more bandwidth on the network and capability of data sharing and let them export the COV's to the required recipients.

Issue I can not get my Xenta Groups to come online under my Echelon LTA in Vista classic or Xenta 911, or don't get any alarms from any of the Xenta's. The LTA is online and the LonWorks network is commissioned and online, but the Xenta groups will not come online. Environment Xenta Programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Echelon LTA Vista Classic network Cause The group master may be offline causing the entire Xenta group to also report an offline status. It may also be due to spaces in the naming conventions of the network. Resolution Verify that the Xenta group master controller is online Verify that no object has a name longer than 20 characters LTA name, LonWorks group name, or any Xenta group or Xenta name Verify that there are not spaces in the LTA name, LonWorks group name, or any Xenta group or Xenta name. Use underscores (_) instead of spaces. Verify that there are not \ or / in the LTA name, LonWorks group name, or any Xenta group or Xenta name. Use underscores (_) instead of back slash and forward slash.

Issue Advice on the configuration of a Sigma UNC 632, UNC 696 or UNC 796 controller, when connecting it to a "Subnetted" Ethernet network. Environment All Sigma controllers connected to flat ethernet network. Cause General advice. Resolution A "Subnetted" Ethernet network is a network that contains a number of subnets, for instance a network who's address is 10.158.1.0 Mask 255.255.255.0 will contain network addresses 10.158.1.1 to 10.158.1.254. The IP address 10.158.2.1 will be connected to another subnet of that network. On this type of network the Sigma controller will require an IP address, Subnet Mask and the subnet Default Gateway to be entered. This information and details of the controller's "Default Server" are added to the controller using the SDCU (Sigma Device Configuration Utility).  

Issue Some Netcontrollers support 32 I/O Modules, others only 16, how to find out what the limit is when adding more modules to an existing system. Environment Continuum Netcontroller CX9900, CX9940, Netcontroller II CX9680, CX9940 16IO-T X Driver Cause When a site is being extended by adding extra IOU Modules, it needs to be determined if the Netcontroller will support these additional modules. Resolution If the controller is online to Cyberstation, Edit the controller and check the value of "Max IOU Modules" on the Options tab, this will show 16 or 32. If the controller is not online the following apply: All Netcontroller II (CX9680) controllers support 32 IOU Modules. All Netcontroller 1 CX9900 with 8Mb RAM support 32 IOU modules, Most CX9940 with 4Mb RAM support 32 modules the only exception was the 4M-16I/O-T (now obsolete) that supported 16 modules. To determine if the CX9940 is a 4M-16I/O-T, check that the Model on the right side of the unit is defined as CPU-4M also that there are no connectors for the RS485 fitted to the unit on Comm1 or Comm4 (you will see holes where the connectors are not fitted). The CX9940 16IO/T can support an X Driver on RS232 Comm1, but no other port. The 4M-16I/O-T and 8M-32I/OT Do not support any Infinet nodes and cannot be upgraded to support them as the required hardware is not fitted as the time of manufacture.

Issue Is an Xdriver (X-Driver) needed for OPC integration? Product Line Andover Continuum Environment Continuum CX(99xx) Cause OPC server requirements Resolution An Xdriver is not needed to operate the OPC Server. Link to OPC Server Datasheet Link to OPC Server Software

Issue When a Netcontroller is powered off, resets or loses communication to the AC-1 IOU modules, the modules become stand alone. Product Line Andover Continuum Environment Netcontroller II (CX9680), Netcontroller (CX9900, CX9940) IOU Modules AC-1, AC-1A, AC-1Plus Custom Wiegand Events Cause Need to understand what functionality AC-1 IOU modules provide without a Netcontroller Resolution If using one of the standard Wiegand data formats i.e. Continuum 37 bit, 26 bit etc then the AC-1 module will operate in site code only: This is known as degrade mode and means any card from that site will be granted access to the door. The module verifies the presented card is of the correct data format and has the correct parity, The module checks the site code against one of the 4 possible site codes stored in NVRAM. The AC1 and AC-1A only support the first two site codes in degrade mode. The AC-1Plus can support all four site codes in degrade mode. There is no recording of events when the Netcontroller comms are lost. Programs that are controlling the module no longer work This is different to normal operation where both the card number and the site code are verified to ensure that the individual person has access to the specific area.   When using custom card formats and the module is operating in degrade mode: Refer to Setting Up a Custom Wiegand Format for information on the behavior of the AC-1, AC1-A and AC1Plus. Refer to Multi Custom Card Formats as the site codes also need to be saved in the AC1 module using a Plain English program, 

Issue Failing communications from a MicroNet View front end. Environment MicroNet View communicating to a MicroNet ARCnet or NCP  LAN. Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position.  Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Place switches 1 to 4 to ON for compatibility with NCP/ARCNET I/O- Server (MicroNet View versions 1.0 and later). Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.