Notifications

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

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 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.

Issue Getting error unhandled exception when trying to run a report of extended log data Product Line Andover Continuum Environment CyberStation Cause ACCTrace reveal workstation is handling excessive extended log data (>100,000 lines in ACCTrace in a couple minute) Resolution In the CyberStation properties, set the 'Download extended log data from Controllers on the LAN' to false. Reboot CyberStation If reports runs ok now the Extended logging configuration should be revised. See Extended Logging gaps, performance and load balancing for more information.

Issue The alarms in the UNCs stop archiving to the Enterprise Server database. The process was working before and nothing was changed. Product Line TAC IA Series Environment I/A Series R2 using the Cloudscape database Cause The size of the Cloudscape database has grown too large. This may cause issues with the system. Resolution Reduce the size of the Cloudscape database by deleting older alarms and logs. Refer to this document for details on how you can delete old alarms and logs. For details on the CloudscapeAdmin utility mentioned in the document, refer to How to remove data for all logs prior to a specific date in a Niagara R2 Enterprise Server. Switch to using a SQL database instead of the default Cloudscape database if there is a requirement to keep old alarms and logs for a longer period. There isn't a known limit where the size of the Cloudscape database can grow before the possibility of problems starting to occur. It is different for each site. As a guideline, it is recommended that SQL database be used if the size of the Cloudscape database has to be greater than 2GB.

Issue Require LonWorks shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11 Product Line TAC IA Series Environment I/A Series R2 Cause The lonDanfoss module prior to version r2.301.529 does not have the shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11. Some NCIs cannot be read if a DynamicDevice is used. Resolution The shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11 (VltFc100V121) is available in lonDanfoss JAR file version 2.301.529a. You can download the JAR file here. This is also available in I/A Series R2 version r2.301.532. Refer to How to install an I/A Series R2 JAR File for the procedure to install an updated JAR file to an I/A Series installation.

Issue Opening a graphic page, selecting an ATS, then modifying it to make changes or just clicking OK, the ATS disappears. Product Line TAC INET Environment I/Net Seven revisions 2.15 and higher but below 2.40. Cause The ATS editor comes up and allows the user to makes changes, once it is done and Okay is selected the ATS itself disappears because there is something on the OS itself that overwrites it. Resolution Uninstall I/NET according to Procedure for uninstalling I/NET Seven on a stand-alone host. Once removed, install I/NET according to Installing I/NET Seven MSDE on new Dell PCs and Laptops. Copy back all relevant pages and go through the sequence again to verify that it has resolved the issue. If the above steps do not work, then upgrade to the latest 2.4x version.

Issue When a BAS animation is created, the object assigned and the graphic is run, the animations do not move or rotate. Product Line Satchwell Sigma Environment Sigma Graphics Animations BAS Cause A legacy BAS animation has been used in Sigma (for a Sigma animation see Sigma Animations are not moving in Sigma Graphics). Resolution Identify the animation file in c:\sigma\data\graphics\animations\legacy\bas and open with Microsoft Paint and note the no. of frames across and no. of rows. Open the properties page of the animation. Change the Frames Across and Num Frames (rows x frames across). Example: ANI153 will be Frames Across = 4 Num Frames = 4

Issue A service that requires the system to be open has been accessed prior to successfully opening the System object. TAC Vista System Plug-In The system is not open. (Subsystem: LNS, #67) Error: LNS #67 lcaErrSystemNotOpen Product Line TAC Vista Environment LonMaker Vista LNS Cause There are many circumstances that could cause this. For example, if you call the Validate method to validate a network database before opening the system, or if you call the Backup method to copy a network database before opening the system, this exception will be thrown. Resolution If registering or launching the TAC System Plug-in results in the error "System is not open, LNS #67" followed by "TACOSSysPin.Document launch failure Exception occurred," and "lnsplugin.api launch failure," then your LNS credits may be corrupted despite indications that they are not. First reboot and try again. If still fails, replacement credits have to be reordered from Echelon. See description of LNS #147 in Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147). It is also possible to get LNS #67 without having corrupted credits. This has been seen a couple of times on databases that are upgraded from LNS 3.1 to LNS Turbo. It seems to be hit or miss whether the upgrade will cause this issue or not. The Licensing Upgrade 2006 discussed in LNS #147 should be installed. Defragmenting the computer can also cause this corrupted credits with no indication and a TACOSSysPin error. Replacement credits will fix the issue even though there is no indication that they are corrupted.

Issue Turned on the computer and the SigmaX is not working. It appears the registration has been lost as the SigmaX Id code has changed. Where can a new SigmaX code be obtained? Getting an error "No Seats Available" and the PC id has changed. Product Line Satchwell Sigma Environment Sigma SigmaX Cause SigmaX registration uses the leading Ethernet port Mac address to calculate the laptop (SigmaX) Id. Enabling or disabling any Ethernet adaptors will change the Laptop Id code. For example; Enabling or disabling a wireless connection. Placing the laptop into a docking port. Resolution SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. With the release of SigmaX 7.0.9 the following procedure is no longer required and will not be available in 2017 Reset the Ethernet connections and confirm the SigmaX Id Code is the same as before. -- OR -- Obtain the PC Id number by running the registration utility C:\SigmaX\Bin\RegSigmaX.exe. Request a new SigmaX unlock code by either; Registering on line at https://sigmaxregistration.schneider-electric.com/ Instructions on how to register for new SigmaX code can be found in SigmaX is requesting an unlocking code. Contact Product Support Services

Issue Preset isn't working, but video pops up Product Line Andover Continuum Environment Cyberstation Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause If record on alarm isn't selected for at least 1 second then the preset will not work Resolution Set record on alarm for at least one second Check that time between the DVR/NVR, Cyberstation and Controllers are in synch Teach Cyberstations and restart Cyber Ensure that none of the Cybers have an error or crash on accvideorecordingsrvc.exe, if so restart Cyber on that PC and try the PTZ alarm again If this is selected then configure the video.log to gather information for PSS For additional information, see How to create a log file for troubleshooting video integration issues in Continuum.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

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

Getting error unhandled exception when trying to run a report of extended log data

Alarms stop archiving to the Enterprise Server database

Require LonWorks shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11

ATS Disappearing from a graphic page

BAS Legacy Animations are not moving in Sigma Graphics

The system is not open. (Subsystem: LNS, #67)

SigmaX Code no longer works

Cyberstation PTZ preset is not working when a video alarm is triggered

Building Automation Knowledge Base

Related Forums

This is a heading