Notifications

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

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 PCT project folder size increases when an object is deleted. Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT 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. Cause Any change made in PCT increases the size of PCT project folder. This is by design and it is a normal behavior of PCT. The reason for this is that a project is a virtual machine using a dynamically allocated image that grows when memory is needed, but the image will not shrink when something is deleted. Resolution The only way to reduce the folder size of a project is to backup all servers in the project, create a new project, restore the server backups to the new project and then delete the old project.

Issue After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above 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. Cause Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.

Issue How do I put a different application in an existing MNL controller under an AS? Environment AS with MNL controllers 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. Cause An incorrect application has been installed in a device. Resolution First, the correct application must exist in the WorkPlace Tech editor list. Expand the System Tree to expose the MNL device to be changed and the Application file under it. Right click on Application and select delete. Now right click on the MNL controller select MNL and Assign application and assign the correct application from the list. Once assigned right click on the controller select MNL and select Download application.

Issue When opening an XBuilder project with Menta objects referenced to Menta Library objects, the references are lost and all Menta objects are showned as disconnected from the library. Environment TAC XBuilder 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. Cause For some reason, the library definition in the project has become corrupted. Resolution 1: Browse to the XBuilder project file (*.xbp*) 2: Edit the file with notepad or similar 3: Search the file for all instances of "MENTALIBOBJ" 4: If the node doesn't have anything in "GUID=" that's the problem 5: For all instances that are wrong, copy the "MentaObjLibId" value to "GUID" 6: Save the file, and reopen the XBuilder project

Issue 'Com Addr' does not appear in list of SE7000 or SER7000 parameters, even when a BACnet or wireless network card is fitted. Product Line EcoStruxure Building Expert Environment SmartStruxure SmartStruxure Lite Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause 'Com Addr' only appears in the list of parameters when the controller recognises that a BACnet or wireless adapter card is fitted. If the parameter does not appear even when a card is fitted, there is a problem with the card, the connector or the controller motherboard. Resolution Remove the front cover of the controller and check that a BACnet or wireless adapter card of the correct type is fitted (there are several variants - see the table below for details). The BACnet/wireless card is piggybacked onto the controller motherboard via a plug and socket and two supporting pillars. If a card is fitted, remove it and check for bent pins on the plug, signs of damage to the motherboard or daughter board (e.g. scorching), or dry solder joints on the plug or connector. It may be possible to carefully straighten out any bent pins on the plug, but any other form damage is not repairable by the user and the whole comms card/ controller assembly should be returned for repair under warranty Communication Boards Part Number Description Compatibility VCM7000V5045W Wireless communication card SE7000 Series room controllers VCM72000V5045P Wireless ZigBee Pro communication card SE7200 Series room controllers VCM7300R5045P Wireless ZigBee Pro communication card SE7300 Series room controllers with RH VCM7300T5045B BACnet communication card SER7300 Series room controllers VCM7300V5045B BACnet communication card SE7200/SE7300 Series room controllers VCM7300V5045P Wireless ZigBee Pro communication card SE7300 Series room controllers without RH VCM7600V5045B BACnet communication card SE7600 Series room controllers VCM7600V5045P Wireless ZigBee Pro communication card SE7600 Series room controllers without RH VCM7607V5045B BACnet communication card SE76x7 room controllers (with RH options) VCM7607V5045P Wireless ZigBee Pro communication card SE7600 Series room controllers with RH

Issue The database files used by the WebReports SQL database need to be moved to another location. Product Line EcoStruxure Building Operation Environment WebReports SQL Server 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. Cause There are numerous reason for wanting to do this, but the most common reason is that there is not enough space on the disk where the WebReports databases are located. By moving to another disk this will allow space for future expansion. Note that this article only describes how to move the database files to another harddrive. The SQL server and database files must still be on the same PC where WebReports is installed. Resolution To move the database files, follow this process: Start by backing up everything. Stop the reporting agent service (name: ReportingAgentService). Open SQL Server Management Studio and locate the database. Right-click on the database and select Tasks-->Detach. Locate the SQL database files (*.mdf and *.ldf) in Windows explorer. Cut or copy these files and move them to the desired location. Go back to SQL Management Studio and select the Databases folder. Right-click and select Tasks-->Attach database. When the dialogue opens up, locate the 'ADD' button and click on it. Browse to the database files' new location and click on OK. Restart the reporting agent service.

Issue TAC Vista SQL transaction log file is very large and won't shrink. Product Line TAC Vista Environment Vista 5.1.X SQL server 2005, 2008 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. Cause An SQL transaction log consists of a number of virtual files whose size is defined in the database's properties. Once the virtual file is full, the next virtual file in sequence is used. These files are an essential part of the 'rollback' functionality, allowing SQL to roll back a transaction if for some reason (i.e. disk space runs out) it can't be completed. With the simple model, the virtual file will be marked as reusable once the transaction(s) contained within the file is complete. So a database may look like this, with the '2' in the status column indicating that the virtual file is still in use: With the recovery model set to a simple, a shrink operation will remove all the virtual files that aren't in use. With the full or bulk-logged recovery model shrink operations behave differently. A full description of this can be found here, but the most important point is that a backup of the transaction log must be made before any virtual files can be marked as reusable. A shrink operation may not remove all virtual files straight away either so multiple shrinks may be necessary to remove all unused/expired Resolution Run the following queries: DBCC loginfo This will show the file structure of the SQL log file. BACKUP LOG taclogdata TO DISK = 'c:\taclogdata.bak' Run DBCC loginfo again. Check to see if there is any change. Run a 'Shrink' command (via SQL Management Studio) and then run DBCCloginfo again. Check the size of the database: sp_helpdb taclogdata Keep repeating the process until the database logfile is as small as it can be.

Issue Confused by RF-Series sensor wiring instructions. Do the controller's input return and the supplied power ground connect to the same termination on the sensor? Environment RH-Series sensor Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Documentation Resolution *** If connecting to a voltage input on the controller then use the VOUT termination instead of the 4-20 mA

Issue Battery power on an MN50-RTC is low and needs to be replaced. Product Line Satchwell MicroNet Environment Controller PCB Power supply Timeclock Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Low power in battery Resolution The replacement battery is a standard CR1632 3 volt 125mAh Updated January 2014. The MicroNet 50 series range MN350,450,550,650 LCD and Touchscreen have been withdrawn from sale. Currently no direct replacement is offered.

Issue Process to restore MNB-1000 to factory default. Product Line TAC IA Series Environment MNB-1000 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. Cause If the IP address has been lost or unit has been misconfigured how can this be restored the factory default. *This step should only be taken if the data on the unit is not to be maintained * Resolution On the DIP switch settings, set all of the switches (1-8) to the ON position. Cycle power on the controller. Unit will boot up in reset mode (red flashing status light) Once completed the status light will be solid green. The unit is now in factory default mode The IP address will be 10.1.10.2 with a 255.255.255.0 subnet mask. BACnet IP will be disabled by default and BACnet Ethernet will be active.

Issue What is the best practice for migrating controllers from a stand alone Continuum system into an active LAN system? Product Line Andover Continuum Environment Migrating Continuum Database 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. Cause Controllers must be migrated from a stand alone system into an existing Continuum LAN system. The ACCID of some or all of the controllers on the stand alone system are already in use on the LAN system. Resolution All address conflicts should be dealt with before the controllers are brought onto the LAN system. With the workstation in Offline mode, each controller on the Stand alone system is manually created on the LAN system. If the controllers ACC ID will conflict with a controller on the LAN system an appropriate change must be made when creating the controller on the LAN database. Where the controllers are BACnet controllers and the intent is to have all controller on the same network, the Network ID (UDP) id must be changed to match the id of the LAN system. The Comm2 network ID of each stand alone controller should be noted and should be changed in cases where the id is already in use on the LAN system. Import files should be used to build the IP level controllers

Issue What is the proper procedure to use when swapping two previously installed Infinet controllers on the same Continuum network. Environment ACCID Infinet Controllers 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. Cause Must prove determine whether an Infinet Controllers flow sensor is damaged. Resolution It is important to recommission Infinet controllers before relocating them in the same system. Recommissioning the Infinet controller purges all object handles and ensures that the controller will be brought on line virtually as a new "out of the box" controller. Infinet controllers are recommissioned by setting the InfinetID to 0 using a RoamIO. Using a RoamIO, set the InfinetID of both Infinet controllers to zero. Verify that the controllers InfinetID has been set to 0. With the workstation in OffLine mode, change the serial number of each controllers to a fictional serial number that does not exist in Continuum. Remove both controllers and install them in place of each other with out powering the controller. Before the controllers are powered, connect them to the Infinet bus while the bus is connected to the infinet port. Switch the workstation to Online Mode. Power up the controllers. Enter the correct serial number for each controller in the controller editor. Both controllers should come online. Reload both controllers.

Issue Although Continuum 1.94 is installed, when the workstation is edited Version 1.73 is seen on the Details page under Software Revision and Firmware Revision. The Cyberstation startup splash screen shows Continuum 1.94. Continuum 1.94 is shown under Continuum Explore/Help/AboutContinuumExplorer. Environment Cyberstation. Warning Cause The erroneous version number is most likely an artifact of a Continuum upgrade that was done without fully uninstalling the previous version of Cyberstation. Resolution Uninstall Cyberstation from Control > Panel Add Remove Programs. Backup all profiles and graphic pin and background files, then delete the Program Files\Continuum folder. Delete all occurrences of the Andover Controls folder from the registry. HKEY_LOCAL_MACHINE/Software/Andover Controls and HKEY_CURRENT_USER/Software/Andover Controls Reboot the PC and install Cyberstation. Run Continuum Database Initialization and select Workstation to reinitialize the workstation. .

Issue How should the Micro Energy Power Supply voltage reading be checked? Can the Micro Energy Power Supply provide power to IOU only without CIU connected? Environment Infinity SX8000 Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Got the Micro Energy Power Supply repaired by 3rd party but the voltage reading seems to be incorrect. Resolution The voltage of the Micro Energy Power Supply should be checked with the load connected to the PS. For the port_A voltage check, have the CIU connected to the port_A of the PS. For the port_B voltage check, have the IOU connected to the port_B of the PS. Also the Micro Energy Power Supply can have either the port_A connected to CIU only or the port_B connected to IOU only or both ports connected to CIU and IOU respectively. For detail information of the voltage reading of each pin, please refer to page 2-86 ~ 2-88 of the AC256 Service Manual.pdf

Issue When many trend logs are linked to the same time object for emailing via a Receiver Group, some of the trend logs may not be sent. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 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. Cause The Xenta Server cannot send more than approx. 50-60 simultaneous emails before some are lost. The limit appears to be dependent on the size of attached trend logs and the number of addresses in the Receiver Group list. Resolution For a single email address, split the trend logs into groups of no more than 40. Link the logs in each group to a different time object and stagger the times at which they are sent. If the Receiver Group definition contains multiple email addresses, reduce the number of trend logs in each group accordingly.

Issue Trend logs are not being saved to SQL after upgrading the SQL database. There are no error messages and Vista can read old (pre upgrade) values from the taclogdata database. The insertlogvalues keeps growing. Product Line TAC Vista Environment Vista 5.1.X SQL 2005 or 2008 server with a database that has been upgraded to layout 2 (the new schema used from version 5.1.7). 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. Cause The database schema is out of date. The database schema is a blueprint of how a database will be constructed. Resolution Shut down Vista. Go to services and stop the TAC DSS writer service. Right-click on My Computer (Computer in Win 7 and Win Server 2008) and select manage. Locate services in the console that opens up. Locate the TAC DSS Writer service, select and then click on stop. This service is responsible for writing events and trend log data to the SQL database. Update the database schema. Open Vista sever setup and locate the SQL server tab. Click on the Custom radio button (if not already selected) and then change the name (e.g. add "_1" to the end of the current name) of the database in the SQL Server Name field. Click on Apply, OK and then Yes to create the new database. Once complete, change the name of the database back to the original name (or click on the Typical radio button if using default settings) and click on Apply. A message will appear "Log database found but needs to be reconfigured. Reconfigure Log database?". Click on Yes. The database schema should now be updated. Right-click on My Computer (Computer in Win 7 and Win Server 2008) and select manage. Locate services in the console that opens up. Locate the TAC DSS Writer service, select and then click on Start. This service is responsible for writing events and trend log data to the SQL database. Check to see that the logs are now being written to the log database. It may take some time to process the backlog.

Issue The C20 series cameras have the BNC and neutral ground for 24VAC tied to the same ground plane. This can cause a power supply short if the ground and hot are connected out of phase at the power supply. This can also cause ground loop bars in the video if connected to a supply that is not on the same ground plane as the camera. This also causes problems with some third party UTP brands connections. Product Line Field Devices, Pelco Environment C20 cameras connected to common power supply and/or ground planes that are different. Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Cause The 24 VAC on the C20 cameras are connected to a common ground plane and the BNC connection is grounded to the same ground plane Resolution When installing the C20 cameras use single isolated transformers for each camera, or make sure the wiring is tied with the same phase. This is done by making sure the same wire leg of each camera is connected to the same wire side of the transformer on the power supply. Also when connecting to the power supply use a meter to test for voltage potential differences. Check that the cameras will work with the third party UTP brand you are using

Issue For various reasons there will sometimes be a need to move a controller from its existing Continuum network to a different Continuum network. Environment CyberStation ALL CX master controllers 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. Cause Configuration Resolution WARNING: MAKE SURE TO HAVE A FRESH BACKUP OF THE CONTINUUM SQL DATABASE HANDY IN CASE YOU NEED TO REVERT THE CHANGES FOR ANY REASON. Moving a controller from its existing Continuum network to a different network consists of copying the controller and its children to the destination Continuum network and then deleting it from the source network. Place CyberStation in offline edit mode. In the 'Copy' options make sure to select to 'Copy child objects and the children's children, this will ensure that all field devices get moved with the parent CX. Highlight the controller to be moved then drag it to the destination network and select 'Copy Here', please note that the IP address on the destination will be set to 0.0.0.0 to avoid a duplicate. On the original controller highlight the InfinityInfinetCtrl folder, select all the objects on the right side and send to text file. Delete the original controller then set the IP address on the copy. Select the copied controller, right click and select import into and import the text file created on line 4. Return CyberStation to online edit mode, then reload the CX controller (not including the field devices) NOTES: a) After reload, the controller may have a different time if the original network was in a different time zone than the destination network. b) Controllers are only taught about other controllers in the same network, If you are moving multiple controllers move them all before reloading them. After reload controller will not know about any other controller that stayed in the old network and any references to such controllers will be lost.

Issue User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation 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. Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

Issue Error 'Operation was not performed' when trying to run a Graphic object. Environment CyberStation 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. Cause Corrupted Continuum installation Resolution Uninstall Continuum Delete Continuum folder (make sure to save any needed files such as pin, menu etc) Delete Continuum entries in the registry (Make sure to backup registry as a precaution) HKEY_CURRENT_USER\Software\Andover Controls\Continuum HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum Re-install Continuum

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Size of PCT Project folder is increasing

I/NET events alarms stop updating in EcoStruxure Building Operation

How do I put a different application in an existing MNL controller under an AS?

Menta objects in XBuilder disconnects from Menta Library

'Com Addr' does not appear in list of SE7000 parameters

Moving the WebReports SQL database to another hard drive

TAC Vista SQL transaction log file is very large and won't shrink

RH-Series Humidity Sensor Wiring Clarification

What is the replacement battery for the MN50-RTC

Restore MNB-1000 to factory default

Migrating Continuum controllers from a stand alone system into an existing LAN system

How to swap two infinet controller on the same system.

A previous version of Cyberstation is shown in the Detail page of the Workstation editor.

AC256 Micro Energy Power Supply voltage reading and the port connection.

Limit on number of simultaneous emails sent from Xenta Server

Trend logs are not being saved to SQL after upgrading the SQL database

C20 camera has AC neutral and BNC connected to same ground plane

How to move a net controller from one Continuum network to another.

EcoStruxure Building Operation WorkStation Auto Login feature locked

Error 'Operation was not performed' when trying to run a Graphic object.

Building Automation Knowledge Base

Related Forums

Welcome!