Issue Tooltip feature for TGML Graphics was hotfixed in Vista 5.0.3 (Hotfix 20) and was disabled later versions of TAC Vista based on customers requirement. Refer to TPA-MALI-08-0007.01 for more details Product Line TAC Vista Environment TAC Vista 5.0.3 and later versions. Cause By default, the tooltip feature in TGML Graphics was removed. Resolution To enable the Tooltip option in TGML graphics following these steps: The Tooltip snippet is available under Snippets > Basic Functions > Tooltip. If the editor does not have this snippet, download the attached Tooltip.zip snippet. Close all the TGML windows and Install the tooltip snippet Open the TGML editor and you can find the tooltip snippet under My Snippets Drag and drop the tooltip snippet on to the graphic objects window to see the tooltip feature. After drag and drop the tooltip snippet on to the graphic, the Metadata – TooltipContainer will be added to the object properties. Tooltip will now be available for this graphics Object. Repeat steps 4 and 5 for each other graphics Object.

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 TimescaleDB Installation Errors - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% - ERROR: could not get 'pg_config --pkglindir' : exit status 1 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.x External Log Storage TimescaleDB (third party)  Cause Missing environment variable paths in Windows is detailed in section 9.4.4 PostgreSQL and TimescaleDB Installation in the EcoStruxure Building Operation 3.0.1 Release Notes. Assistance in how to add these variables is described below. Resolution Using the EBO External Log Storage Installer tool available on the Community, there is no need to make any manual configuration, as the tool executes the installation without the need for e.g. environment variables. Alternatively, you can manually set these as detailed below: You can either view a video showing how it is done:  or follow the instruction below view, add and modify the environment variables from the Control Panel as follows:  In the Control Panel select System and Security Select System Select Advanced system settings Select Environment Variables. In System variables, highlight Path and click Edit. For the error - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% Add the New path 'C:\Program Files\PostgreSQL\11\bin' to the environment variable. For the error -ERROR: could not get 'pg_config --pkglindir' : exit status 1 Add the New path 'C:\Program Files\PostgreSQL\11\lib' to the environment variable. You should see something similar to the following after TimescaleDB has been successfully installed.

Issue Does I/NET Seven provide Time and Attendance functionality Environment I/NET Seven 2.xx and above Third Party Time and Attendance solution Cause Possible alternatives to Customers wanting to use or interface Time and Attendance solutions with I/NET. Resolution I/NET does not have a separate Time and Attendance ‘module’. There are three possible options which may provide a suitable alternative to your requirements: SevenReports: I/NET’s SevenReports provides a standard report called “Transactions Attendance”.  The report compares the time stamp for an individual and calculates the time within zones defined in I/NET.  I/NET doors must be configured with entry and exit readers and have defined Zones (i.e. Anti-pass back must be enabled).  It could be as simple as a single zone for the entire site or multiple zones if this is required. This report shows EACH transaction received, therefore if you badge multiple times on the entry or exit readers the system calculates the time difference from the last badge. This must be taken into account by any system when calculating the total time within the “Zone”. Automatic Report Generation (Export of SevenReports to CSV): Using the same report as mentioned above, I/NET is capable of automatically exporting this document to a CSV file. This can be scheduled to run as required for any third party system to use. Third Party Access to InetDb SQL database This option allows third party SQL connections to query the I/NET SQL Database (Read only access), utilizing a predefined login or the INetThirdParty login.  The third party software or application would query data from the InetDb SQL database. For further information and configuration of these features are all available in the same document, TCON301 – Database Connectivity and Reporting.

Issue Can I run third party software on my I/NET PC Environment I/NET Site Cause Third party software on same pc as I/NET Resolution TAC software is delivered for use on IBM and compatible PCs. While your PC is capable of running other third party software while running I/NET, trying to do so may present general operational difficulties. This is particularly true if the other third party software is memory resident. When used as it is intended, the TAC software is also memory resident. The use of more than one memory resident program at the same time may impose unresolvable PC system parameter conflicts and may cause one or more of the memory resident programs to fail. Refer to TCON 300.

Issue Is there a native solution in Continuum to totalize the hours of presence of a person in an area? Or must I do a PE program for each personnel which will calculate the time between the arrival time and the leaving time?   Environment Time and Attendance CyberStation ACX and/or AC-1 family of controllers Cause Is there a native solution in Continuum to totalize the hours of presence of a person in an area? Or must I do a PE program for each personnel which will calculate the time between the arrival time and the leaving time? Resolution There is no native solution in Continuum to totalize the hours a person has spent in a given area. It will require PE programming and entry and exit readers. The Security COE has a Continuum add-on called TimeTracker that may work for some applications. Learn more about Continuum Time Tracker.

Issue There is an adapter which allows for connection between the USB port of a laptop or computer to Micronet via a MicroNet 2000 MN-Sx sensor. Environment MicroNet 2000 software (MN-CI, MN Flow Balance) MicroNet 2000 controller with attached sensor (MN-S, MN-SO, MN-SDK) Cause Computer without a serial port Resolution This connection requires the use of both part numbers MN-CIM (MicroNet Controller Interface Module) and UC232A (USB to Serial Adapter). The UC232A adapter can be attained from B&B Electronics. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Steps: Load the UC232A driver Select unused Com port in setup (can not conflict with any other ports being used) Reboot computer

Issue The new program interface does not match the previously defined program interface. (Subsystem: NS, #59) Product Line TAC Vista Environment LonMaker 3.1 LNS Version <3.2 Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 104-A Square D Altivar 61 Xenta 102-AX Cause The steps defined in this article only relate to the NS #59 error when it is received on an attempt to commission a controller in an LNS environment. It does not cover when this error is shown as a result of a download attempt in the TAC Vista System Plug-in. For information on the download error, see NS Errors #59, #64, #51 in a row on download attempt through System Plug-In. The new program interface does not match the previously defined program interface; i.e., the number of network variables, message tags, or the structure of self identification data is inconsistent even though the Program IDs match. This generally happens when a newer firmware of a controller is introduced that uses the same SNVT inputs and outputs as the old controller, and therefore shares a device template even though something below the surface may be different. Resolution The appropriate resolution to the NS, #59 error depends on the LNS version and type of controller that is failing to commission. Select from the categories below which best describes the situation. LNS Version <3.2 Check the existing Version of LNS. Open the Echelon® LonMaker™ Design Manager Right-click on the title bar of the Design Manager and select "About Echelon LonMaker..." In the About Echelon® LonMaker™ Design Manager Professional Edition window, look under Additional Information.   If the LNS Version is below 3.2, then upgrading the LNS to 3.2 or later (also referred to as LNS Turbo, not to be confused with LonMaker Turbo) may fix the error. The later LNS versions are less sensitive to program interfaces not matching. Navigate to Echelon Downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks. If you cannot install the LNS update, proceed to the following solutions organized by controller type. Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) You get this error when two controllers share a device template (XIF file) if one has a system program version (.MOT) below 3.5 and the other has a system program version above 3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and its own template. Open the application from the System Plug-in by right clicking on the controller and selecting Configure>Edit. To give the application a new XIF, either add a dummy SNVT or go to Device Configuration and uncheck the box for "XIF header generated according to LonMark standard." Go to Options>Simulate (F12), select Commands>Generate. Options>Edit (F12) and save the application to the hard drive by selecting File>Save as. In the System Plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and Vista Database. If you are asked to resynchronize, do so. Download Applications and Parameters. Commission in LonMaker. Another cause of the error for a Xenta programmable is if the system program version (.MOT) is newer than the version of Vista System Plug-In being used. For example, if visiting a 4.2.5 Vista site and attempting to add a much newer 3.8 firmware Xenta programmable. It will fail on attempts to commission. The firmware must be downgraded to a version that is compatible with the older Vista system. See Download an .MOT file into a Xenta Programmable controller for information on loading a different .MOT file. Xenta 104-A (follow steps below) If there are TAC Xenta 104-A v1.10 (or older) commissioned in an LNS database, it is not possible to add a TAC Xenta 104-A v1.20 or newer in the same database. Nor is it possible to do a replace. This is due to a change of size of the SNVT declaration area residing in the device memory. For the same Program ID, LNS requires this size to be identical as previously commissioned devices. Download NXE v1.20A from The Exchange Download Center. This is an NXE file which should be used to upgrade v1.20 to be able to coexist with v1.10. (It is not possible to upgrade 1.10 to 1.20/1.2A, due to memory configuration.) The download of v1.2A to the device is selected in the “New device wizard” in LonMaker. Check the “Load application image” and browse in the NXE as the image file. Note : The same process must be performed while dealing with the 104-A v1.21. In addition to the same issues above, v1.20A will not be compatible with v1.21. For more information on the Xenta 104-A firmware versions see Xenta 104-A firmware version compatibility. Square D Altivar 61 (choose an option below) Square D Altivar 61 drives have undergone a similar update of the firmware. Newer LON drives cannot reside concurrently on a network with older drives. A new NXE must be loaded into the newer drives so they can coexist with the older drives. This NXE file is on the Product Support SharePoint, or can be obtained by contacting Square D drive support directly at drive.products.support@schneider-electric.com. Xenta 102-AX Two Xenta 102-AXs, one that is hardware version 1, and one that is hardware version 2, cannot co-exist on the same LNS network. Whichever one is commissioned first will work fine, the second will result in an NS, #59 error.

Issue SmartStruxure uses two different function block programs. Menta Editor is used for Xenta programmable controllers while Function block editor is used in the Automation or Enterprise server. The two programs are not interchangeable and do have several differences. Product Line EcoStruxure Building Operation Environment Function Block Editor Menta Editor Cause There are several differences between Function Block Editor and Menta Editor that are important to know. Resolution Download the relevant version of the Function Block Editor and Menta Editor Difference Guide from Exchange. This guide will cover the following topics: An overview of Function Block programming The programming differences Function Block Editor and Menta Editor differences Program Conversion Importing Xenta programmable controller programs Building function block programs to I/Os Binding values Binding values using a binding template Time schedule and alarm blocks Trend logs Overview of Function Block Editor Block differences

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 The Station buttons are missing in the MCU Configuration dialog box Environment I/NET 2000 Site Cause The Station buttons are missing in the MCU Configuration dialog box. What happened? Resolution To provide you with the ability to configure or hide the statistical features of I/NET 2000, there are three .reg files included in the I/NET 2000 application root directory. When you double-click the desired *.reg file, it will update the DiagnosticFlag in the registry to the associated condition. Each file and its function is as follows: NoStats.reg - No statistics dialog shown, Stats.reg - Shows statistical data but does not allow back-ground ASC resets or manual MR/ASC resets, Stats&Reset.reg - Shows statistical data with ability to perform background ASC resets or manual MR/ASC resets.  For more information see TCON 217.

Issue The MNB-70 firmware upgrade displays version v1.130 during the upgrade process when upgrading to v1.430   The firmware included with WorkPlace Tech 5.8.5 will display the correct filename (MNBU70-01430.bin) however the version will indicate v1.130 within the WorkPlace Tech Commissioning Tool. The firmware included with the MNB Series v1.430 Firmware Pack extractor will display an incorrect filename (MNBU70-01130.bin) as well as indicate v1.130 within the WorkPlace Tech Commissioning Tool. Product Line TAC IA Series Environment I/A Series MNB 70 I/A Series WorkPlace Tech 5.8.5 I/A MNB Series v1.430 Firmware Pack extractor Cause An incorrect version of firmware for the I/A Series MNB-70 controller has been included with the WorkPlace Tech 5.8.5 distribution and the MNB Series v1.430 Firmware Pack extractor both released in mid-July 2013. Resolution Replace the existing MNB-70 firmware file with an updated version: Locate and delete the existing MNB-70 firmware files (where applicable): MNBU70-01130.bin MNBU70-01430.bin The firmware files are typically located … Windows XP \Documents and Settings\All Users\Application Data\WorkPlace Tech\Firmware Windows 7 \Program Data\WorkPlace Tech\Firmware Download the updated MNB Series v1.430.A Firmware Pack extractor from The Exchange Download Center: MNB Series v1.430.A Firmware Pack - BTL Compliant.exe Execute the extractor and the files will be extracted to the firmware directory for use with the WorkPlace Tech Commissioning Tool.

Issue When the GCM has been configured to send a COS alarm, a null pointer exception similar to the one shown below is seen in the output window when an alarm is activated. “ERROR [17:15:39 16-May-13 CDT][gcm.unsolicited.com1] Exception java.lang.NullPointerException in Unsolicited message processing” The alarm is not processed by the ENC nor sent to the alarm console with the COS alarm’s message. The return from alarm is processed and seen in the alarm console. The return from alarm does not have a COS message associated within the GCM COS block. Environment I/A Series G3, GCM driver Cause The alarm is not being processed and routed properly by the tacGcm driver. Resolution The tacGcm 3.6.47.4 module corrects driver's alarm processing.  The tacGcm 3.6.47.4 module can be downloaded from The Exchange Download Center.

Issue When the GCM has been configured to send a COS alarm, a null pointer exception similar to the one shown below is seen in the output window when an alarm is activated. “ERROR [17:15:39 16-May-13 CDT][gcm.unsolicited.com1] Exception java.lang.NullPointerException in Unsolicited message processing” The alarm is not processed by the ENC nor sent to the alarm console with the COS alarm’s message. The return from alarm is processed and seen in the alarm console. The return from alarm does not have a COS message associated within the GCM COS block. Environment I/A Series G3, GCM driver Cause The alarm is not being processed and routed properly by the tacGcm driver. Resolution The tacGcm 3.6.47.4 module corrects driver's alarm processing.  The tacGcm 3.6.47.4 module can be downloaded from the Buildings Download Center.

Issue Error Messages: Windows - Delayed Write Failed Windows was unable to save all the data for the file D:\VISTA DB _23032011\$queues\insertevents. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Windows - Corrupt File The file or directory \VISTA DB _23032011\$queues\insertevents is corrupt and unreadable. Please run the Chkdsk utility. Product Line TAC Vista Environment TAC Vista Cause Problem with Operating System (or) Hard Disk Fault (or) Link between $queues with Vista Database. Resolution As there may be several issues that are causing this, there are three options to look at: OPTION 1: Restore the OLD TAC Vista Data Base Backup. Refer to TAC Vista Technical Manual chapter 26 for re-storing database procedure.   OPTION 2: There might be a linking problem with this folder and Vista.  Here are the steps to check if this is the problem: If the problem still exists, Check for hard disk errors. Find the $queues - folder in existing database folder ( \DB\$queues) Copy the files to an other location and delete current folder (Refer to An efficient method for deleting all queued files in the $queues folder) Recreate it with same folder names and copy back the files into $queues-folder. If the problem still exists, Check for hard disk errors.   OPTION 3: Check for hard disk errors, follow the below procedure: Go to "My Computer", Right click on Hard Disk Drive – typically - C, and Click on Properties. Go to Option "Tools" and Click on "Check Now" under "Error-Checking"

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue The Discrete Input readings are incorrect on a 7780, what causes that? Environment 7780 Cause Input resistors are incorrectly configured. Resolution Configure Resistors according to TCON100

Issue Cannot connect to video server when creating a VideoServer object in Continuum and Test Connection is selected. Product Line Andover Continuum, Pelco Environment Continuum DSConnex Digital Sentry Cause Patch not installed for DSConneX versions 4.3 and 7.x not working with Andover Continuum 1.91 or 1.92 or LAN connection problems Resolution Install v1.91 DSConneX Video Patch hotfix for issue with DSConneX versions 4.3 and 7.x not working with Andover Continuum 1.91. For 1.92 these files are included, so if the error is still occurring, then there are LAN connection issues.

Issue Fluctuating temperature readings where they jump up to +327 randomly. Product Line Andover Continuum Environment Continuum controllers i2866-V Cause Readings like that are usually caused by wiring or power issues. There was also a Firmware fault that caused this in an old version of the i2866-V Firmware. Resolution Confirm the following wiring considerations:   That your input and output cables shield is wired to Earth ground at one end of the run only (preferably the controller chassis). That your controllers power supply is earthed on the secondary side of the 24vac transformer to ensure a proper controller ground to Earth. Confirm that the power supply is not being shared with any field devices, especially field devices feeding inputs back into the controller. One way to troubleshoot if it is a cabling or controller problem is to replace the sensor cable with a 10K ohm resistor. See Temperature inputs not reading the correct value for details. Also, in i2866-V controllers with firmware versions less than v3.501049, temperature inputs could randomly go to +327 when Analog Outputs were changing value frequently. Uprev your controller. See TPA-BOST-09-0007.00 for details.

Issue Tap not communicating with Host. (Refer to TCON 101 and TCON 226) Environment I/NET 7801 Tap Cause Multiple causes are possible.  Resolution Check connections at the host port Verify Switch settings Ensure you are using the correct cable Check the Tap version Check the Baud rate set in the set up Check the Comm Port defined in setup