Notifications

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Mixing version of Sigma data Product Line Satchwell Sigma Environment Opening customer's Sigma data files in Sigma on another computer. For example: an engineer needs the site information on his laptop while carrying out a maintenance visit. Cause When a specific Sigma version is loaded onto a computer, only data files from the same Sigma version should be used. Resolution It is known copying over the whole Sigma folder from another version of Sigma to your computer can appear to work, this should not be done. Any files that have been looked at, on another computer, in this way should not be restored onto the customers machine. Some issues caused by doing this will not always be obvious as many of the Sigma tasks are completed in the background. The site could be left with a potential issue or corrupted files. Rather than uninstalling Sigma and re-installing the correct versions on the main computer operating system, Virtual machines each with different Sigma versions could be created. Further information, showing Sigma release numbers against Build numbers, can be found in How to identify the Sigma Version installed on a Computer.

Issue An error message indicates that EPICLM.exe can't be found in data1.cab using the Epi integration for badging or a 1309 when installing Cyberstation Product Line Andover Continuum Environment Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Kaspersky Anti virus is identifying and removing the file from the data1.cab during a scan. Resolution Place the cab file or the EPICLM.exe as an exclusion in Kaspersky's or EST NOD32 scan. For additional information see Kaspersky's website. http://support.kaspersky.com/4084 Note: The data1.cab file may need to be restored from the original CD or Continuum install zip file and then uninstall/reinstall EpiBuilder with the exclusion list in place to repair the problem. See Uninstalling and reinstalling EpiBuilder or error opening EpiDesigner configuration database for more information.

Issue Need to log a User off of a Continuum Workstation from a remote Cyberstation. Product Line Andover Continuum Environment Continuum Cyberstation Cause No documented solution on how to log off a remote Workstation. Resolution If you know the name of the User that is currently logged on, you can open that User object from another Workstation and disable the user. This will immediately log that user off of their current session in Continuum and lock them out of the system until their User object is re-enabled. To determine the name of the User, you can use the solution in Is there a way to determine who is actively logged into CyberStation and onto which workstation? to determine what users are currently logged on to Continuum using the Activity Log.

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 When Vista Server is started the startup process just hangs. Product Line TAC Vista Environment Vista Server 5.x Cause There can be several causes for this issue. A common issue with this situation is the Vista database has been restored from site without the Lonworks NL220 or LonMaker database. When the Vista server is opened it is unable to contact the Lonworks database and repeated attempts cause the server to hang. Resolution It is possible to prevent the Vista server communications as well as other parts of the Vista server communication. Reference TAC Vista dll Manager to download a tool from the Community that will allow you to disable DLL files and find the cause of the issue. If you are seeing the scenario as stated in the above cause, you would disable Option "10: Network communication" and "11: Field bus communication" in this tool then select the Update button You must remember to enable the options once you have finished with the site database. If you forget to do this the Vista server will not function correctly when you want to run a live database.

Issue Drop downs not visible on secondary monitor used with I/NET Product Line TAC INET Environment Windows XP I/NET Seven 2.41 Cause As of 2.41 I/NET is not intended to be a multiple monitor platform Resolution Modify the display settings to configure the monitor with the I/NET display as the primary monitor Upgrade to I/NET 2.41 using Windows 7 as this problem has not been seen with this specific installation Use I/NET on your primary monitor and AMT on your secondary monitor. If it doesn't work, please refer to Drop list of point control in I/NET summary on secondary monitor does not work.

Issue Launching Menta by opening an MTA file causes a Buffer Overrun Error The error message: "Buffer overrun detected ... A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated." Product Line TAC Vista Environment Menta Cause Menta's buffer for opening files is limited; if the file you are trying to open by double-clicking has a very long path (of 142+ characters), you will receive the Microsoft Visual C++ Runtime Library Buffer Overrun error message. Resolution Work arounds: Shorten the path to the Menta file. If it is possible to decrease the number of subdirectories or the length of the directory names to make the total path length less than 142 characters, this will correct the problem. Note: Never modify a Menta file name within Windows; only change Menta file names using the Menta application by using "Save As..." from the File menu. (See "Cannot open file" error when opening a Menta file for resolution if this occurs.) If it is not possible or practical to change the path to the file, files with long paths can still be opened by launching Menta using the Start Menu or a desktop icon. Select File > Open and browse to the Menta file, then click "Open". Opening the file via this method will expand the path length limitation to over 200 characters.

Issue Which substitution codes are available for write to file notification objects? Customer wishes to write dynamic values to file. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3/1.4 Cause When using write to file notification objects it may be desirable to have dynamic text containing actual values etc. Resolution For write to file notifications, the substitution codes can be used in the message but not in the file name. A substitution code for notifications has the form @([property]) where [property] is replaced by one of the alarm properties. If you use a substitution code that is invalid for the specific alarm event, the substitution code is replaced by an empty string. For alarm email notifications, see Displaying different properties of an alarm in an email notification.

Issue Cannot attach the Network interface to Lonmaker database when the Vista Server (Tacos) is started as a service. The error message is that the 'NIC interface is not connected'. Product Line TAC Vista Environment Echelon Lonmaker 3.1 Echelon Lonmaker 3.2 TAC Vista (all versions) Cause When updating Lonmaker and Vista databases as applications, it is important that Lonmaker be started first. Failure to do so can result in issues like this when Vista is reconfigured to start as a service. Resolution To get Vista and Lonmaker running together: Stop the Vista service and unregister it. If using a Loytec interface, set the Loytec Legacy Driver to run as a service (click the Advanced tab in LConfig). Start Lonmaker and attach the correct network interface. Ensure that Lonmaker is online. Start Vista Server as an application. From Lonmaker open the System Plugin. In the TAC Network properties, check that the correct network interface is selected. Update the Vista database. Start Vista Workstation and check that everything is online. Stop Vista and Lonmaker. Reregister Vista as a service. For details of these operations see Registering/Unregistering TAC Vista Server as a Windows service. Also see section 16.3 of the TAC Vista Technical Manual.

Issue Installing I/NET and Vista on the Same PC Using I/NET with MSDE for File Equalization Product Line TAC INET, TAC Vista Environment I/NET 2.31 with MSDE Vista 5.1.4 with SQL2005 Express Windows XP Cause When Installing I/NET and Vista on the same PC and MSDE is desired for use with I/NET, I/NET must be installed first. If you are not using MSDE, please see Installation guidelines for installing I/NET and Vista on the same PC. Resolution Completely Remove I/NET, Vista and all versions of SQL and MSDE from the system. See Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL and How to uninstall and completely remove TAC Vista 5 for more details. Begin the I/NET Installation Select MSDE for the database installation. Complete I/NET and MSDE installation Install Vista Start Vista Server Start I/NET Configure I/NET as a Filemaster Build Database or restore from a backup.

Issue Does Vista support virtualization? Will Vista run on a virtual PC, VMware, virtual environment? Product Line TAC Vista Environment TAC Vista all versions VMWare, Player, Workstation and Server Microsoft Virtual PC Cause For many companies, the largest benefit of server virtualization is in reducing the amount of hardware that is required to run all the software needed by the business. Consolidating servers using a virtualization process not only provides savings in terms of how many physical machines must be bought and maintained, but also potentially reduces the amount of physical space that a company needs for its servers or data centre. Resolution Virtualization is a term that allows software in emulating environments, such as VMware / Virtual PC. These software packages emulate a PC environment so that many computers appear to be running on one single machine, thus “virtualization”. The general impression is that the emulation packages work very well. The user must be familiar with the emulating product in order to be able to do the correct settings. No matter if it runs on PC hardware or in an emulating environment, the specific product is supported given the problems are related to the Software itself, but not for problems related to the environment it runs on. Particular note and understanding is required when dealing with multiple applications trying to access a single piece of hardware, such as serial ports, USB and the like. Please see the following TPA-MALI-09-0013.00 for additional information. Also note that Vista Licensing system is NOT supported when using Remote Desktop. Refer to the following article for further details: Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system.

Issue Xenta 102-AX temperature sensors reading in the range of 130°F (54.4°C) when they should be closer to room temperature. Wiring has been checked and everything appears correct. What kind of temp sensor do I use for a 102-AX? Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX ETD-1xx duct temperature sensors ETR-1xx room temperature sensors STR-1xx room thermostats Cause Every other Xenta controller uses a 1.8k-ohm thermistor as a standard. Because the Xenta 102-AX is a modified version of the I/NET MR-VAV-AX, it still uses the 10k-ohm thermistors native to the I/NET product line. Resolution The Xenta 102-AX uses 10k-ohm thermistors. See 10k Thermistor compatibility with Xenta controllers for detailed information on the thermistor curve that is acceptable. Approved sensors are: ETD-2xx duct temperature sensors ETR-2xx room temperature sensors STR-2xx room thermostats STD-2xx duct temperature sensors

Issue Using anti-passback and the transactions are delayed by 5 (or more) seconds after the actual card is presented to the reader. During this period (while LED is green) no additional transactions are been recorded to AMT Transaction window. As a result of this the anti-passback is not working for the concurrent swipes. The interval time between 2 swipes in the controller is configured to 2 seconds. We have tried changing it to zero, but we are not seeing more than transaction within this period come through to AMT. Product Line TAC INET Environment I/NET Seven 2.xx – with Anti-passback Cause When using anti-passback this is usually caused when you have defined the Door Sense setting in the Door Editor and it is either physically not wired or not working. By default this setting is set to Normally Open. If you have this setting set to normally open or normally closed - the strike will remain energized until the system detects that the door has opened through the sense switch or the strike duration has elapsed, whichever occurs first, the default strike duration setting is 5 seconds. This means any badges that occur during this time are ignored; (only when anti-passback is enabled). Changing the Intercard interval will not make any difference in this situation. Resolution If the door status is not been monitored, you must set the door sense to none. If you are monitoring the door sense then make sure that the door sense activates on each card presentation so that the system recognizes the individual as entering the ‘zone’, therefore allowing the next card to be read. Note: Implementing anti-passback also requires that you define access control zones. When you use Anti-passback in the true sense it is strongly recommended to use the door sense switch, this is to ensure the individual has actually entered that zone. In situations where this is not possible you can tell the system to ignore the door status by setting the door sense to none, it will then assume that the individual has entered the zone and provide the transaction thereof once the strike duration has expired. In this case the door strike must be configured to suit the environment. Anti-passback requires that a door controller have both an entry reader and an exit reader. An elevator door controller will support only an entry reader, and therefore, will not support anti-passback. Refer to TCON 300 Chapter 9 – Access Control Anti-passback section for further information. I/NET Anti-Passback (APB) rules may also be of assistance in setting up Anti-passback.

Issue Network 8000 Ethernet networks experiencing the following symptoms should be upgraded: GCM panels reporting repeated off-line / on-line messages NIM lock-ups requiring power cycling to recover Loss of global data sharing with Network 8000 (RNET and SNET transmissions fail) Product Line TAC IA Series Environment Network 8000 GCM Ethernet NIM, part number GCM-ETH-001 Network 8000 GCM-86000 Series controller (GCM-86120, GCM-86110, LNC-100, SIM-CCN, SIM-MTECH, SIM-YORK, SIM-TRANE) 802.3U Ethernet (100 Mbps) or 802.3z gigabit Ethernet (1000 Mbps) backbone network Cause Ethernet NIM performance was enhanced in revision 11.2T. Resolution Upgrade all NIMs on the network to firmware revision 11.2T, with the single exception of any with revision 11.2P firmware. Click here to see Announcement 01-105 for more details. For details on the REVISED Flash clear procedure, see the NIM Networking and Configuration Guide, F-25955-4, Chapter 2, section titled "Special NIM Address Switch Functions". Click here to see the procedure. Please reference Verifying the current firmware revision of a Network 8000 GCM and if an upgrade kit is available regarding Network 8000 firmware, including current revisions and upgrade kit part numbers.

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 Not possible to see live values in a Xenta 700 Menta program from web interface or TAC Vista Can't see Menta online values in Xenta Server Control Applications graphical view The Menta application displays fine, but it's not possible to see the live values (true/false et c) Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause This is an uncommon error and the cause is not known, however it may occur when copying a HFB block within or between X700 Menta applications. Resolution In the Xbuilder projects folder, find the file [project name]\TargetImage\configdb\menta\mentablocks.xml and open it in Internet Explorer. Search for Menta blocks that have CodIndex='0' and note (copy) the GUID of those (for example 3C02F735-E375-45d0-99A8-6CFC402DE5D0). Now open the file [project name].xbp518 (in the project's root folder) with notepad or similar and search for these GUID(s). Note the Menta block(s) name (before the GUID) and the menta block type (just after the GUID), for example HFDI. Close all previously opened files (no save). Open the Xbuilder project normally, and open/edit the troublesome MTA. Search for the menta block(s) name and check that it also is the same block type (most likely a HFB block), then delete it. Create the block again with the same name (no copying from similar blocks!). Save and download the project to the X700. Now it should work fine viewing the live values in Control Applications. If still same issue, redo step 1-7, there may be other blocks with CodIndex='0'. Note: If you can't see the Menta application at all it's likely a different error, see Can't see the Xenta Server Menta program online in the browser.

Issue Replacement of the 7801 TAP. Product Line TAC INET Environment I/NET site with TAP configuration Cause Desire to upgrade or replace the old TAP configuration Resolution First of all, perform a good backup of the existing site. 7770, 7771, 7797, 7801 TAP replacement hardware explains the replacement of several TAP hardware devices. If the site has a 7801 TAP, the Xenta 527 would be a replacement choice. In I/O server instead of Link Type being Direct, it should be None. Then Enable the TCP/IP and put in the credentials for the Xenta 527. In Network Config, save Xenta 527 link Penetrate and save all below the Xenta 527 to DB Configure Host Mask for Host computer, as well as Xenta 527 The site technicians will need to follow the TCONs and manuals for the Xenta to Host pc, including the wiring and Host Computer configuration, and network connection. This is clearly explained. Also, for the sub controllers, Connect to the controller one at a time Select Edit, Controller, Configuration In the Distribution Parameters section, change the selection from Reliable Tap to None. Reset that controller by cycling power or pressing RED reset button Check the transactions window of AMT to ensure events coming in The site engineers/technicians will need to take time and looking through the material and changing out the TAP with a Xenta requires time and concentration so that it is a smooth transition.

Issue When using Send to Text to export controller points to a text dump, some points are followed by the following error. VidioId - The object type specified is invalid. Product Line Andover Continuum Environment Video Export Send to Text Cause These errors are usually caused by is a “null” value primed in the DB for those attributes Resolution These errors are benign and should be disregarded. See also Errors when exporting extended log points.

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier' field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue What are the different values for the Alarm Enable attribute on a Continuum object when viewed in a list view? Product Line Andover Continuum Environment Continuum Alarms All Infinity Controllers Cause The Alarm Enable attribute is a number that represents the binary combination of the 8 possible alarms that can be used on the "Alarm" tab of a Point or a Numeric. Resolution The screenshot shows a numeric that has 2 Alarms enabled, the binary combination of these 2 points would be 3 (Bit 1 + Bit 2). If a third alarm was added and enabled the Alarm Enable Value would change to 7 (1+2+4). If you disable the first alarm leaving just 2 & 3 Enabled the value would be 6 (2+4). The weighting of the 8 bits are: 1 2 4 8 16 32 64 128 When an alarm is not setup it defaults to 255, but if the alarm enables are all de-selected it will be 0. Although Plain English programs cannot write to this attribute you can change the alarm checking under different site conditions or by time of day using the Shunt alarm points 1-4, See Alarm Point Clarification.

Issue "Read-only because object refers to a standard file" when trying to change Menta application (.mta file) from TAC workstation. "File object is locked by another application" when trying to edit a Menta application (.mta file) (file is not marked as reserved) Product Line TAC Vista Environment Menta Workstation Cause If a standard file is used, it is not possible to edit the "local" Menta file. Other causes are explained in "File object is locked by another application" error when trying to edit Menta file. Resolution If the referenced file is supposed to be a standard file, locate and edit the file referenced. If the referenced file is not supposed to be a standard file: Click on the more button under the MTA tab in the properties for the device. Uncheck "Reference standard file object.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Opening customer's Sigma data files in Sigma on another computer

Error "1334 EPICLM.exe can't be found" when attempting to print preview, print a badge, or 1309 when installing Cyberstation

How to log a User off of a Continuum Workstation remotely

Vista Server hangs on startup

Using multiple monitors with I/NET

Launching Menta by opening an MTA file causes a Buffer Overrun Error

Available substitution codes for write to file notification objects

Error inserting a row in the database when refreshing a personnel template

Cannot attach the Network interface to Lonmaker when Tacos is started as a service

Installing I/NET and Vista on the Same PC Using I/NET with MSDE for File Equalization

Running Vista software on an emulated environment

Xenta 102-AX temperature sensors reading incorrectly, very high

Anti-passback (APB): Only receiving one / delayed transaction(s) even though multiple valid cards are presented to the reader

Upgrading Network 8000 GCM Ethernet NIM firmware due to network communication problems

Not possible to see live values in a Xenta 700 Menta program

Replacement of the 7801 TAP

Object type Specified is invalid when exporting points

How to change b3's device ID using the RoamIO service tool

How is the AlarmEnable attribute derived?

"Read-only because object refers to a standard file" when editing Menta from Workstation

Building Automation Knowledge Base

Related Forums

This is a heading