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 Receive "Initialization error" when trying to start I/NET with SQL 2008 When we installing SQL Server 2008 Standard for I/NET Filemaster, what are the main components we should include? When editing / adding a new I/NET Configuration Profile the Database Server section is blank DBCreate does not start. Appears in task Manager but no user interface is shown. Within DBCreate the restore option is grayed out Product Line TAC INET Environment I/NET Seven 2.4x Microsoft Windows Server 2003, Windows XP, Windows Vista, and Windows 7 families of operating systems. (both 32 and 64 bit) Microsoft SQL 2008 Standard or Express Editions Microsoft SQL 2008 R2 Standard or Express Editions Cause I/NET must have the SQL 2005 Backward compatibility file installed. If this is not installed I/NET will not locate the SQL Server and hence will issue an “initialization failure” error. This is can also be identified in either the DBCreate or I/NET Configuration application editors which will show no entries in their "Database Server" settings. The document also details information that is necessary for a Standard or Express editions of SQL 2008 / SQL 2008 R2. Resolution Follow the instructions below extracted from the document called "SQL2008 Expr Install Inst.pdf". This document is found on I/NET Seven CD under the 'SQLExpress' folder. For SQL 2008 R2 installations refer to the following document SQL2008 R2 Expr Install.pdf, also found in this same folder . Installing SQL Server 2005 Backward Compatibility SQL Server 2005 backward compatibility must be installed for SQL 2008. To install SQL Server 2005 Backward Compatibility Navigate to the SQLBcm directory on the TAC I/NET Seven installation CD. Launch the SQLServer2005_BC.msi file. Follow the prompts on each screen and accept all defaults. After the install check the SQL Server Services SQL Server Browser is RUNNING SQL Server (MSSQLSERVER) is RUNNING Check the SQL Server Network Configuration Protocols Enable Named Pipes Enable TCP/IP Completing the Installation Proceed with the installation of TAC I/NET Seven on your PC. For installation instructions, refer to TCON298, TAC I/NET Seven Getting Started. Note: Run Inetcfg.exe before starting TAC I/NET Seven for the first time. This is necessary to attach TAC I/NET Seven to the database and avoid an “Initialization failure” error. Note: Before file equalization will operate, the system must be rebooted or the INETEQZMERGE service must be manually started. Also refer to Installing I/NET 2.42 or higher and Vista 5.1.7 or higher on a 64-bit operating system for additional details on installing I/NET with SQL 2008 R2.

Issue Graphics not working in Webstation. Only the menu bar is shown. Some graphics might work. The graphics are working fine in the Workstation and in the editor. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation TGML Cause Some images (PNG, JPEG, BMP) can have wrong information in the image file. In some cases, this corrupted image information will block the graphic from being rendered in Webstation although it works fine in the editor and in Workstation. Resolution Make a copy of a graphic that is not working and delete all the images in the graphic. If the graphic can now be viewed in Webstation, delete the images one at a time viewing the graphic in Webstation after each save. This will allow the location of the image(s) having the issue. Open the image in a graphics editor such as PaintBrush and save it with a new name. Import the new image and save the graphic. Check that the graphic can be viewed in Webstation Another option to easier find the file image having the issue, is to extract the images from a graphic that is not working in Webstation with the "TGML Image Extract" tool, and run all the images through an image checker, such as "Bad Peggy" or "Corrupt JPEG Checker"

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.

Issue How do you determine how large a database will grow when using Continuum? How do you know if a Stand Alone or LAN install should be used? Which version of Microsoft SQL Server is needed? Product Line Andover Continuum Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 MSDE SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of controllers, points and logging should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called MSDE and SQL Server Express. The size limitations are 2 and 4 gigabytes respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Continuum database, to determine if a Stand Alone or LAN is needed and which version of SQL should be used. The Continuum database estimating spreadsheet takes into consideration 6 main areas: Extended Logs- total amount of logs, intervals and the number of days to retain Access Events- total amount of access events and the number of days to retain Alarm Events- total number of alarms and the number of days to retain Error Events- total number of Cyberstation errors and the number of days to retain Activity Events- total number of Activity events of all Continuum users and the number of days to retain Continuum Database objects- Total number of Netcontrollers, Infinet, BCXs , mstp controllers, total number of inputs, outputs and numerics. Any of the objects not mentioned above. Consider all objects not mentioned above The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate if a Stand Alone or LAN system is needed Indicate which version of SQL Server is needed Download the Continuum Database Size Estimation Tool.

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue Instructions and programming example for using nviEmergCmd to control the damper on the Xenta 102-AX Environment Xenta 102-AX Menta Cause In some situations it is necessary to have the Xenta 102-AX damper open to 100% for smoke control, or other sequence of operations specific tasks. There are different emergency modes which all perform a different function. Resolution The damper position on the 102-AX can be controlled to 100% or to 0% by using the SNVT input nviEmergCmd. Please see the attached Menta file as a programming example. The enumeration breakdown and controller actions of nviEmergCmd are as follows: 0 = Emerg Normal - Normal operation of the controller without any emergency command. 1 = EmergPressurize - 102-AX will control to its max cooling CFM setpoint. 2 = EmergDepressurize - 102-AX will control its damper to 0% and shut off all other outputs. 3 = EmergPurge - 102-AX will control the damper to 100% 4 = EmergShutdown - 102-AX will pause control on the damper and disable all other outputs. 5 = EmergNull - Null SNVT value NOTE: Any value change on nviEmergCmd will initiate a damper resynchronization. This will cause the controller to fully close its damper, fully close any floating control outputs, and disable any other hardwired outputs for their full stroke time (throttling range).

Issue Communications with other Lon network devices are lost after the IC-Lon/IC3-Lon has cold-started. Product Line Satchwell Sigma Environment Sigma IC-Lon Integration controllers IC3-Lon Integration controllers Cause The controller has been cold-started either manually or through the automatic process. Resolution The final part of the engineering process of the IC-Lon/IC3-Lon, is for the file named NVConfig.bin to be uploaded from the IC-Lon/IC3-Lon to the Sigma server. If this file is not uploaded, then the IC-Lon/IC3-Lon reverts to its non-bound state. The NVConfig.bin file contains information about the Lon bindings and is modified during the binding process when using LonMaker. To upload the NVConfig.bin, carry out the following: Open "System Diagnostics" on the Sigma server. Select the correct controller number. From the "Options" menu select "Upload Files" and NVConfig.bin This file will now be uploaded and overwrite the existing file in the controller folder, and therefore when the controller next cold-starts, the correct file will be downloaded to it. For more information on the Engineering process of an IC-Lon/IC3-Lon, please click here. The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue How can more than 50 globals be transmitted from a Sigma controller when I have a lot of digital objects states to pass between controllers? Environment Sigma Controller (all) Cause Sigma controllers are limited to 50 broadcast globals. Resolution Up to 16 Sigma Digital objects states can be reference in a single programmable object. By performing a binary count the various states can be represented by a single analogue value which can then be broadcast as global data. Sigma programmable object MASK command can be used to decode analogue representation of a single analogue value that represents up to 16 digital states (on/off). For example the value of 901 represents the state of a number of Sigma DI Objects where each bit indicates the on/off. Hence, this translate to the 16-bit binary value 0000001110000101 where 1 = on and 0 = off To set-up bit masking click here for details. 1. Create a program object in the transmitting controller that 'binary' counts up to 16 digital objects. 2. In the receiving controller create up to 16 programmable objects to decode the transmitted analogue value. e.g

Issue The user logged into Windows doesn't have permissions to the folder that contains the Continuum.mnu file, the file is set to read only or the path in the continuum.mnu is incorrect. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Permissions are restricted to the Continuum.mnu file or the path in it is incorrect. Resolution One of the follow solutions will resolve this: Click to download an edited default path Continuum.mnu and Menu.bmp (links for the default path C:\Program Files (x86)\Continuum) Copy these files to each workstation that has an incorrect path Manually edit the file yourself if you have a path that is other than (C:\Program Files (x86)\Continuum) Grant permissions to the folder. The folder that contains the Continuum.mnu can be located by editing the Cyberstation in Continuum Explorer. WS Edit> Preferences tab> The file name of the main menu Ex. c:\program files\continuum\userprofile\continuum.mnu Right click on Continuum.mnu and select properties. Deselect Read Only if it is selected. Change the path to the Continuum.mnu file to a folder that you have access to and copy the continuum.mnu to it. Ex. c:\program files\continuum\continuum.mnu While in edit mode, right click on each of the buttons and select Properties Use the browse button to select the correct x86 path (C:\Program Files (x86)\Continuum) Repeat this for each of the buttons and then save the Continuum.mnu file Copy these files to each workstation that has an incorrect path Also see Continuum.mnu file with C:\program files (x86) on 64 bit PCs points to C:\program Files and shows a blank screen.

Issue How to load up archived data in a report using Seven Reports Product Line TAC INET Environment I/NET Seven SevenReports Archiving Cause Reports show nothing or have one blank page and fail to show data that meets the date window specified Resolution When using Seven Reports to view data, archived data can be viewed and put into a report. From the Archives pull-down menu, Mount/Dismount the archive files. Files, by default, are stored in the c:\INET Seven Data\Arch folder. After mounting the needed reports (look at the date of the files in the archive folder), the report used must have the word ARCHIVE in the file name. This specifies that the reports will be pulled not from the current database but rather from the mounted files and on the dates specified. The reports should now be from the Archived files mounted. Archive Reports are located on the install CD under CD\Program Files\INET Seven\Reports To download, click on the link below and select to save the report to your hard disk in the c:\INET Seven Data\Reports folder: I/NET Seven Release 2.20 and Prior files: ArchiveOverrideBillingSamples.rpt ArchiveRuntimeSamples.rpt ArchiveTransactionsDoors.rpt ArchiveTransactionsIndividuals.rpt ArchiveAnalogSamples.rpt ArchiveConsumptionSamples.rpt ArchiveDemandSamples.rpt ArchiveDiscreteSamples.rpt I/NET Release 2.21 to current: ArchiveAnalogSamples_xi.rpt ArchiveConsumptionSamples_xi.rpt ArchiveDemandSamples_xi.rpt ArchiveDiscreteSamples_xi.rpt ArchiveOverrideBillingSamples_xi.rpt ArchiveRuntimeSamples_xi.rpt ArchiveTransactionsDoors_xi.rpt ArchiveTransactionsIndividuals_xi.rpt Tip: In some instances, while the report is running and the data is being compiled, if you move the mouse or strike a key, the process starts all over. The solution is to start the report and wait for a few minutes if you have input a broad range of data to search and produce.

Issue As part of a site power feed problem investigation where varistors are being blown, how are they connected to the power feed? Environment i2920, b3920, b4920. Cause When a site is experiencing power problems and the mains input varistors blow, it is required to know how the damaged varistor is connected. Resolution The 3 varistors are connected between: Live and Earth, Neutral and Earth, Live and Neutral. The attached sketch shows how the 3 varistors are connected. The connections are the same for the i2920 and b4920.

Issue When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address. When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.

Issue How can I run Windows programs from a workstation plain english program? Environment Cyberstation Plain English Windows programs Cause Launching windows programs from Continuum Resolution Please see this link for information on using the Shell plain english function NOTE A Plain English script can be added to some graphics objects (Plain English Script tab), so for example you could run a batch file (in the continuum directory) from a graphics button using Shell "test.bat"

Issue To assist locating data sheets if you do not have access to The Exchange or other Schneider Electric storage areas Product Line Satchwell MicroNet Environment MicroNet 50 series Controllers Micronet Touchscreens Micronet LCD SLink sensor Cause To assist customers that do not have access to our internet or partner websites. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MN 50 Series MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN350 Controllers MLi and data sheets for Satchwell MicroNet MN450 Controllers MLi and data sheets for Satchwell MicroNet MN550 Controllers MLi and data sheets for Satchwell MicroNet MN650 Controllers Download all of the above (file size 12.0 MB) Data sheets for MicroNet 100 series controllers ETC can be downloaded from MicroNet 100 series controller MLi's and Data sheets.

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue Will the Multi-Purpose Manager (MPM) act as a BACnet IP BBMD? Product Line EcoStruxure Building Expert Environment Site using BACnet and one or more SmartStruxe Lite Multi-Purpose Manager (SSL MPM) Cause Can the MPM act as a BBMD Resolution The MPM cannot act as a BACnet Broadcast Management Device (BBMD), but it can be a foreign device to another BBMD BACnet protocol includes broadcast traffic which does not pass through on-site routers. For BACnet devices to network across a wide area or across multiple separate sites connected by the Internet, it is necessary to register the BACnet devices with a Schneider BBMD using the Foreign Device Registration function in Building Expert. For a Multi-Purpose Manager (MPM) running Building Expert to function as a BACnet device, when being managed remotely over a standard TCP/IP network, it must be configured as a Foreign Device. It must also be registered on an Automation Server (AS) on the remote network that acts as a BBMD. Once done, BACnet devices can send messages to the BBMD, which are translated by the BBMD so they can pass over a standard on-site router. Then BBMD forwards the messages to the appropriate destination MPM controlling the Devices for which the BACnet messages were originally intended. Then the MPM translates the messages received over the network from the BBMD into standard BACnet messages and passes them on to the intended Devices as if they were direct BACnet messages. This Foreign Device Registration feature allows a single user with a StruxureWare Building Operations (StruxureWare Building Operation) terminal to remotely oversee multiple disparate sites simultaneously using BACnet, without having to install expensive direct connections to each site. You must have Firmware release version 2.9 or higher installed on your Manager to use Foreign Device Registration function. Here is the BACnet-Specifications-PIC-Statement.pdf And the explanation on how to setup the DR-ForeignDeviceRegistration.pdf

Issue How are the bits allocated in a 26bit Wiegand card format? Environment Access control peripherals data format Cause Although this is an openly published data format, sometimes the actual data bit format is required. Resolution The Wiegand 26 bit format consists of 24 bits of data and 2 Parity bits (Odd and Even) The 24 data bits are split between 8 bits for the Site code and 16 bits for the card number. Giving a card number range of 1 to 65535, and a site code range of 1 to 255. A spreadsheet defining the format can be downloaded here.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

I/NET Seven with SQL 2008

Graphics not working in Webstation - only the menu bar is shown

XBuilder Device Editor Modbus register formats

Continuum Database Sizing and SQL Server selection

"Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681".

Recommended USB to Serial RS-232 adapter

Controlling the damper on the Xenta 102-AX to 100% with nviEmergCmd.

Sigma - IC-Lon/IC3-Lon - Communications with other Lon network devices are lost.

Enable a Sigma controller to broadcast more than 50 globals (bit mask)

Access denied error when editing the Continuum menu or the x86 path is incorrect

Accessing archived data and obtaining reports from archived data

How are the i2/b3920 controllers internal varistors connected to the power input?

How to use the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100

Satchwell D?T sensor temperature to resistance

Plain English Shell statement to run Windows programs from a workstation

MicroNet 50 series controller MLi's and Data sheets

Using WireShark to analyse communications on an Ethernet network

LDAP (Lightweight Directory Access Protocol) Integration of G3 (Niagara) Users with Active Directory

Multi-Purpose Manager (MPM) as a BBMD

What is the format of the 26 bit Wiegand standard format?

Building Automation Knowledge Base

Related Forums

Welcome!