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 Field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Product Line TAC IA Series Environment I/A Series MNB 1000 with firmware 1.510 and later only. Cause The field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Resolution The Web Service page has been removed from the MNB-1000 Plant Controller firmware effective with release version 1.510. All functions that were previously included on the MNB-1000 Web Service page are now included in the WorkPlace Commissioning Tool -- Device Properties window for MNB-1000 controllers. The changes to the Device Properties screens were documented in the WorkPlace Tech Tool 5.7.7 release notes, available here.

Issue Lookup table for the AIC Analogue Input Configuration for different sensors. What types of sensors can be used with the MPM controller? Product Line EcoStruxure Building Expert Environment Multi Purpose Manager AIC Cause A lookup table is required for a sensor that is not listed in the AICs. What sensors can be used? Resolution For the Satchwell range (new generation or T range) STP660, STC600, STR600 series. Note the engineering output is Celsius. For the TAC range STP100 series, STC100, STR100 series, STD100 series. Note the engineering units is Celsius. For the Andover range STP500 series, STC500, STR500 series, STD500 series. Note the engineering units is Celsius. AIC 1 to AIC 10 are empty Analogue Input Configurations, the remainder are pre-configured as below. For 10K Type II in Celsius use AIC 11 For 10K Type II in Fahrenheit use AIC 12 For 10K Type III in Celsius use AIC 13 For 10K Type III in Fahrenheit use AIC 14 For 1K PT1000 RTD Platinum in Celsius use AIC 15 For 1K PT1000 RTD Platinum in Fahrenheit use AIC 16 For 1K PT100 RTD Platinum in Celsius use AIC 17 For 1K PT100 RTD Platinum in Fahrenheit use AIC 18 For 1K NI1000 RTD Nickel in Celsius use AIC 19 For 1K NI1000 RTD Nickel in Fahrenheit use AIC 20

Issue Is there a template to help create the custom AccessFormat array? Product Line Andover Continuum Environment Creating a Custom Card, Access Format array for non standard Wiegand formats Cause As there is sometimes confusion on the way that the bits are counted from 0 or 1 and how to use a Plain English program to initialize the array an easy way to lay out the data would be useful. Resolution The attached Excel spreadsheet works as a template to enter the Access Format data. Click here to download Format Template.xls. Enter your required Wiegand format bit definition in the box at the top, then this will allow you to define the numbers to go in the AccessFormat array lower left, which automatically fills in the example program on the right. Also see: Setting up a custom Wiegand format access cardfor information on setting up an AccessFormat array. Determining Custom Card formats on Deciphering Custom Card formats. What is the range of Wiegand Card numbers and Site Codes I can use on Continuum? on maximum card numbers.

Issue Allowing write access from BACnet Product Line TAC IA Series Environment I/A Series G3 BACnet Integration Cause By default, the BACnet driver provides external BACnet (client) devices "read access" to all exposed (exported to BACnet) objects in the station. Access depends on a station user named "BACnet." If this user does not already exist in the station, the Bacnet driver automatically creates it, upon startup. The BACnet user is initially created without any permissions. Resolution See below which is extracted from the Niagara Ax BACnet Guide: To allow any external writes (from BACnet) to properties of exported components, including invoking commands (actions), you must assign the BACnet user the necessary permissions to those components. For example, to allow an invoked "Active" action from BACnet to an exported BooleanWritable, in addition to making it "BACnet Writable" at priority level 8 when exporting, you must configure the station’s BACnet user to have operator write permissions on that BooleanWritable, at a minimum. Or, if an exported NumericWritable has an alarm extension, and you want to permit external BACnet writes to its "alarm limit" values, configure the BACnet user to have admin write permissions on the exported NumericWritable. In either example, to allow an external BACnet write to a property like "Out Of Service" or "Notify Type," you must give the BACnet user admin write permissions on the BACnet export descriptors. For details about station user security, see "About Security" in the User Guide. Note: BACnet user permissions also apply to writes of any exported files and histories. Also, note that while a password for the BACnet user is technically not needed (for external BACnet access), you should assign one anyway, because of the write permissions typically assigned. Make it a "non-blank" password, and guard this password carefully.

Issue How to read the Modbus device's register and, via Menta in a Xenta 700, convert the value in to the 4 bytes required to bind these values to the SNVT_preset member Value. Environment Vista 5.1.X Communication with a Modbus device. Xenta 700 5.1.X (Menta) Cause SNVT_preset includes a member value[4] which is an unsigned long containing 4 bytes. Modbus contains only 16 bit registers. The SNVT member Value is shown as 4 separate bytes in Vista. Resolution Click here to download an Xbuilder project containing the correct Menta file to convert from a Modbus register to the 4 bytes that the member Value contains. Instructions: Download the zip file and extract the Xbuilder project. Open the Xbuilder project and change the IP address to your device's IP address. Download the project to the Xenta server and save to Vista.

Issue Satchwell VZF 2-Port Flanged Valve Body requires replacement. Environment Satchwell 2-Port Plug and Seat Flanged Valve Body VZF1727 VZF 1727 VZF1777 VZF 1777 VZF1852 VZF 1852 VZF1902 VZF 1902 VZF1954 VZF 1954 Cause Obsolescence of Satchwell VZF 2-Port Flanged Valve Body Resolution A number of alternative S-E 2-Port Flanged Valve Bodies are available to replace existing Satchwell VZF 2-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E VG221F 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body. In such instances a S-E L9TVG Linkage Kit will additionally be required. Alternatively an Actuator from the S-E range of Actuators may be installed on the VG221F 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E V222 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body. In such instances a S-E L8TV Linkage Kit will additionally be required. Alternatively an Actuator from the S-E range of Actuators may be installed on the V222 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2-port Flanged Valve Body Similarly, the centre line to bottom of third port dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2port Flanged Valve Body As a result alterations to the pipework connected to the VZF 2-port Flanged Valve Body will be required. Details of the Satchwell VZF 2-port Flanged Valve Body may be viewed here. Details of the S-E VG221F 2 port Flanged Valve Body may be viewed here. Details of the S-E V222 2-port Flanged Valve Body may be viewed here. Details of the S-E L9TVG Linkage Kit may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue RM / XRM series Light Duty Rotary Actuator installed on MB Valve Body requires removal / replacement. Environment RM RM3601 XRM XRM3201 Light Duty Rotary Actuator MB Valve Body Cause RM / XRM series Light Duty Rotary Actuator installed on MB Valve Body requires removal / replacement. Resolution RM / XRM series Light Duty Actuator removal / replacement may be achieved as follows :- Removal :- 1. Beware! RM Actuator is connected to a Mains Voltage power supply. XRM Actuator is connected to a 24 Volt power supply. 2. Isolate Actuator power supply. 3. Locate Terminal Chamber - This may be found on top of the Actuator. 4. Remove Terminal Chamber Cover. 5. Locate Locking Plate Tab – This may be found inside the Terminal Chamber on the face nearest the Window housing the 0-10 Position Indicator Wheel. 6. Pull Locking Plate Tab up to disengage the Actuator from the Valve Body. 7. Separate Tongue of Actuator from Groove in Valve Body Spindle. 8. Actuator may now be removed by joggling Keyhole Slots in Actuator Base plate over Allen Bolts protruding from MB Valve Body. N.B. It is not necessary to remove the Allen Bolts from the MB Valve Body in order to remove the Actuator. Replacement :- 1. Joggle Keyhole Slots in Actuator Base plate over Allen Bolts protruding from MB Valve Body. 2. Insert Tongue of Actuator in Groove of Valve Body Spindle 3. Push Locking Plate Tab down to lock the Actuator to the Valve Body 4. Replace Terminal Chamber Cover securely. 5. Restore power supply. Details of the RM and XRM Actuators may be viewed here.

Issue Satchwell MJF 3-Port Flanged Valve Body requires replacement. Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MJF3426 MJF 3426 MJF3427 MJF 3427 MJF3476 MJF 3476 MJF3526 MJF 3526 MJF3576 MJF 3576 MJF3626 MJF 3626 MJF3676 MJF 3676 Cause Obsolescence of Satchwell MJF 3-Port Flanged Valve Body Resolution Replace Satchwell MJF 3-Port Flanged Valve Body with S-E V311 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MJF 3-Port Flanged Valve Body may be retained for installation on replacement S-E 3-Port Flanged Valve Body. In such instances a S-E L8TV Linkage Kit will additionally be required. Alternatively an Actuator from the S-E range of Actuators may be installed on the V311 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimension of the S-E V311 3-Port Flanged Valve Body differs to that of the Satchwell MJF 3-Port Flanged Valve Body Similarly, the centre line to bottom of third port dimension of the S-E V311 3-Port Flanged Valve Body differs to that of the Satchwell MJF 3-Port Flanged Valve Body As a result alterations to the pipework connected to the MJF 3-Port Flanged Valve Body will be required. Details of the Satchwell MJF 3-Port Flanged Valve Body may be viewed here. Details of the S-E V311 3-Port Flanged Valve Body may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue Cannot find any installation instructions documentation for the WorkPlace Tech Tool software, versions 5.8 or 5.8.1. Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.8 & 5.8.1 Cause An updated version of the document "WorkPlace Tech Tool Version 5.7 Installation Instructions" has not yet been released by our publications group. Resolution The existing "I/A Series WorkPlace Tech Tool Version 5.7 Installation Instructions", F-27367 can be used for installing the release 5.8 or release 5.8.1 of the WorkPlace Tech Tool software. There are two items applicable to the newer versions of the WorkPlace Tech Tool software that are not covered in the published installation instructions. The WorkPlace Tech Tool software, releases 5.7.7, 5.8 and 5.8.1 will run on the 32 bit versions of Windows-XP, Windows Vista or Windows-7. These releases of the software will also run in XP-Mode under the 64-bit version of Windows-7. See I/A Series (Niagara) R2 Windows Compatibility Matrix and the linked PA-00163 product announcement for more information on Windows 7 compatibility. Make sure that the computer meets or exceeds the recommended requirements, not the minimum requirements, for the operating system being used. Beginning with release 5.8.5 of the WorkPlace Tech Tool software, Windows 7 64-bit Professional and Microsoft Visio 2010 is supported (32-bit version only), in addition to the documented Microsoft Visio 2003 and Microsoft Visio 2007 (32-bit versions). The use of Visio 2010 and its ribbon bar menu system are described in the WorkPlace Tech Tool release 5.8 release notes. This same version of the release notes (5.8) is applicable to the use of Visio 2010 with the WorkPlace Tech Tool software release 5.8.1.

Issue Wiring a MD10B-24 / MD20B-24 actuator to a Climatronic CXT / CXR / CSC Actuator Environment MD10B-24 MD20B-24 Actuator Climatronic CXT CXR CSC Cause The Climatronic controller switches the O volt side of the 24 volt supply, but the actuators shows that it requires 24 volts to open and close. Resolution The Satchwell range of Climatronic controllers have always switched the 0 volt side of the 24 volt supply to control the actuator position. CXT Controller - Terminals 13 and 14 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CXR Controller - Terminals 23 and 24 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CSC Controller - Terminals 33 and 32 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. The MD10B-24 / MD20B-24 datasheet shows the wiring as follows; For the complete MD10B datasheet, please click HERE. For the complete MD20B datasheet, please click HERE. The above actuator wiring shows a 0 volt connection to the common connection (1) and a switched 24 volt connection (2 or 3). To connect the MD10B-24 / MD20B-24 actuator to any of the above controllers it will be necessary to connect the actuator as follows. Controller 24 volt (37) to connection wire (1). Controller Open signal (14, 24 and 32) to connection wire (2). Controller Close signal (13, 23 and 33) to connection wire (3). Please note that the actuator direction can be changed by repositioning the switch on the front of the actuator.

Issue What are the differences between the IAC 400 and the IAC 420 controllers? Product Line Field Devices, Other, Satchwell MicroNet, Satchwell Sigma Environment IAC 400 IAC 420 Cause The IAC 400 controller is obsolete and its replacement is the IAC420. Resolution Hardware differences; The IAC 400 has 3 Temperature, 2 Analogue and 1 Digital input, where as the IAC 420 has 6 Universal inputs. Communications differences; The IAC 400 controller uses terminal 3 to earth the communications cable screening, on the IAC 420 the screening must be connected to a good earth and not terminal 3. Tables and offsets; Because the IAC 420 has different inputs that tables and offsets are changed, please review IAC Controllers - Tables and Offsets. IAC 400 Wiring details. For the full data sheet please click HERE. IAC 420 Wiring details. For the full data sheet please click HERE.

Issue TAC 200 OTP User Guide TAC 239W DHW User Guide Environment TAC 200 OTP TAC200 OTP TAC239W TAC 239 W Cause Information required regarding the TAC200 OTP Optimiser/Compensator Controller. Information required regarding the TAC239 W DHW Controller. Resolution Download here the TAC200 OTP guide. Product Part Number: 200-1005-000 Download here the TAC239 W guide. Product Part Number: 239-1010-800

Issue "Relock upon Door Closure" option is greyed out and feature is not available. Environment Continuum Access Control Cause The "Relock upon Door Closure" feature is not implemented at this time. Resolution For this "Relock upon Door Closure" functionality you will need to use Plain English code. The code located here is a sample of how this can be accomplished.

Issue The EGWW sensor is obsolete and needs to be replaced. Environment EGWW: EGWW 120 Cu 5122720000 EGWW 120 St 5122720010 STP100: 5123102010 5123104010 5123106010 5123108010 5123110010 5123112010 5123114010 Cause Obsolete sensor needs to be replaced. Resolution There is no direct replacement, as the old EGWW had 2 sensor elements and was designed to be used with controllers like TA 219WB (Data sheet here). Also, the EGWW was designed to be mounted directly into the pipe work using a well, and not using a pocket as with the STP100. If only one sensor element is required by the application, the STP100 series sensor is recommended. However, please note that the EGWW well was 120mm or 220mm (see data sheet here), while the STP100 sensor probe and pockets are available in 50, 100, 150, 200, 250, 300 and 400 mm lengths. For more information and details on the STP100 and its different configurations, please see data sheet here. If the 2 sensor configuration is required, you will have to install 2 parallel sensors.

Issue In Niagara G3, the SNMP driver reference manual refers to three MIB files required so that the SNMP Point Manager can "discover" and "add" SNMP points as needed. The filenames are: TridiumR3-MIB.my RFC1155-SMI.mib RFC1213-MIB.mib Where can they be found? Environment Niagara G3 Cause The three files are not easily located. Resolution The TridiumR3-MIB.my file is installed with the version of Niagara G3 installed on the host computer. The other two files (RFC1155-SMI.mib & RFC1213-MIB.mib) can be found on the World Wide Web by searching using their specific filenames. All three files are available here: SNMP_Files_for_G3

Issue There is a need to be able to calculate and estimate the amount of power being consumed by IOU modules and their readers Environment 99xx 9680 IOUs Cause Power supplies have a wattage limit and adding to many modules can cause the bus to become unstable Resolution To estimate the amount of wattage being consumed by IOU modules, please download the following Excel Spreadsheet. Continuum I/O Module Power

Issue Replacing a DC3000 controller. Environment Drayton DC3000 Cause The DC3000 is now obsolete. Resolution The DC3000 controller is obsolete, and there is no direct replacement available. Our current range of discrete controllers cannot provide the same functionality as the DC3000, assuming that functionality has been used. To provide the same controller functionality a programmable controller such as the Micronet or Xenta ranges will be required To upload an overview of the Micronet range, please click HERE. The Xenta controller range is listed as part of the TAC Vista Product Catalogue which can be downloaded from Schneider Electric but a table of the controllers and their I/O are shown below.

Issue The documentation on The Exchange differs from the documentation included in the packaging. Neither document shows the full capabilities or wiring options of the transmitter. Environment STO300 Cause The supplier recently changed the PCB and as a result, all of the 300 model plantroom type sensors now offer dual outputs (current and voltage). Since the part number designation is for current only the documentation included in the packaging only shows this configuration. To further complicate matters the specification and installation materials on The Exchange have not been updated to reflect the changes at this time Resolution The installation instructions included in the product packaging should always be referred to when installing these transmitters. The latest installation instructions can be downloaded here. If the new 0-10VDC output feature is required please follow the diagram below for wiring and DIP switch configuration.

Issue How do points map from a i2 controller and the xP expansion modules to Infinity SX8000? Environment Using Continuum i2 controllers and xP modules on SX8000 Infinity systems. Cause The I/O channels on expansion modules are different from Infinity to Continuum. Resolution You can add an i2 controller to your Infinet networks on Infinity and it will co-exist with the other Infinity controllers. The controller will be seen as a equivalent infinity controller i.e. a i2850 will be seen as a TCX850. Also you will not be able to use any of the additional features that a i2 controller has like the flash memory or the smart sensor connection. For Expansion modules you could however use the xP modules (not including the xP display) the attached spreadsheet that shows how the i2 controllers I/O channels will be seen by the Infinity Controller. Download the spreadsheet here.

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.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Cannot access Web Service page in MNB-1000 controller.

Lookup table for the AIC Analogue Input Configuration for different sensors. What types of sensors can be used with the MPM controller?

Custom Wiegand Template

Allowing external third party writes (from BACnet) to properties of exported components

Handling the SNVT SNVT_preset in Xbuilder Menta when values come from a Modbus device.

Replacement of Satchwell VZF 2-Port Flanged Valve Body due to obsolescence.

RM / XRM series Light Duty Rotary Actuator removal from / replacement on MB Valve Body.

Replacement of Satchwell MJF 3-Port Flanged Valve Body due to obsolescence.

Installation instruction documentation for WorkPlace Tech Tool versions 5.8 or 5.8.1.

Field Devices - Wiring a MD10B-24 / MD20B-24 actuator to a Climatronic CXT / CXR / CSC Actuator

Differences between IAC 400 and IAC 420 controllers

TAC 200 OTP User Guide, TAC 239W DHW User Guide

In a Door object, the tick box "Relock upon Door Closure" is greyed out on the Channels tab. Is it possible to activate this feature?

Replacement sensor for obsolete EGWW from TAC

In Niagara G3, the SNMP driver reference manual refers to three MIB files required so that the SNMP Point Manager can "discover" and "add" SNMP points as need...

IOUs going offline intermittently - estimating the power consumed from IOU modules

What is the replacement for the Drayton DC3000 controller?

STO300 current and voltage modes and wiring

What are the available I/O point channels when using an i2 controller on an Infinity system?

Alarms stop archiving to the Enterprise Server database

Building Automation Knowledge Base

Related Forums

Welcome!