Building Automation Knowledge Base

Issue In EBO 2022 or higher the "Semantic Engineering View" button is grayed-out in EBO WorkStation and "Semantic DB authentication failure" is shown in Alarm View. "Semantic Engineering View" button is grayed-out and "Semantic DB authentication failure" alarm   Semantic db authentication error   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause  EBO user that connects to the Sparql database has the wrong username and/or password. Resolution Make sure that the user configured in EBO semantic settings matches the user created in the GraphDB web interface. In WorkStation, in the System Tree pane, select the EBO server. Click the Control Panel tab. Click Navigate to Sparql database, this will open the GraphDB web interface. Login with the admin user account.  In the top right corner, make sure that correct repository is selected, default name is "nsp".  Go to Setup -> Users and Access. Edit user "nspService". Set a password for the "nspService" account and make sure it has access rights to the "nsp" repository then click save. In EBO WorkStation control Panel, open Semantic Settings. Set the password for username "nspService" to match the password set in the GraphDB interface. For more information, please refer to the GraphDB help: Secure GraphDB — GraphDB SE 9.10.0 documentation (ontotext.com)

Issue There are missing serial ports (COM ports) when viewing the 'SerialPortService' under 'PlatformServices' in a station. Some or all COM ports will be missing. Local serial ports and/or serial ports of the attached modules do not function. Product Line TAC IA Series Environment I/A Series AX Jace 8000 Cause This could show up for several reasons. This was found during an upgrade to Niagara 4.2. It was also experienced when converting a Jace8000 running N4.2 (or lower N4 version) to AX. This can occur with a new out of the box J8000 to AX conversion if you do not first commission the Jace8000 to Niagara 4.4 or above before converting to AX. All of these problems are due to older version USBbinary files not being properly updated during commissioning. The LON option module (side-car) might stop communicating on the LON trunk due to the same binary file issue. Resolution This can be fixed via serial shell; either by direct connecting with a mini-USB cable or via ssh after it is enabled from the Platform Administration view. It is recommended that PuTTY.exe be downloaded and used as the terminal program to access the shell. The directions below are CASE-sensitive and must be entered exactly as shown. We recommend that you do not type these commands, but rather use copy-and-paste to avoid typographical errors. This is especially true of the usbSerialNumber itself -- it is case-SENSITIVE. By default, PuTTY.exe uses mouse-left-click-drag-and-highlight as an automatic shortcut for copy. Mouse-right-click is the automatic shortcut for paste. Once logged in type: Display the USB serial number(s) sh [hit enter] $ ls /etc/usb [this will display the USB serial number(s), if nothing displays see the note* at the bottom] 85091090FPGGS41 [this is an example serial number] Display the available binary files $ ls -Rp /sys/images/usb [this will display the available binary files] /sys/images/usb/applet-flash-sam4s16.bin* /sys/images/usb/vid03eb/pid2404/Tridium232-1_r03.bin* /sys/images/usb/vid03eb/pid2425/Tridium485-2_r04.bin* Note: You could also see '_r05' instead of '_r04'. If this is your result, make sure to update using the line below. /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin* The USB ports unavailable is due to the 'Tridium485-2_r04.bin' (or Tridium485-2_r05.bin) file was not written to the USB serial number file. This can be corrected by updating the USB serial number file with the correct binary file using the statement below. Make sure to replace the X in the statement with the highest number binary found in 'STEP 2' above. $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r0X.bin > /etc/usb/<usbSerialNumber> Update the binary file Using the example serial number and USB binary file found in STEP 2: $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin > /etc/usb/85091090FPGGS41 Make sure to use the serial number found when 'ls /etc/usb' was called. If there is more than one serial number found, write the command multiple times, once for each serial number found. Also, make sure to use the highest USB binary file number found. Currently r05 is the highest number. If '_r05' is returned as the available USB binary file, make sure to use '_r05' when updating the USB serial number. After a reboot, check the SerialPortService to confirm the ports are restored. *Note: if no usb serial number was found using ls /etc/usb another method would be to call for the slog by typing: $ sloginfo An error would have been logged here during the last startup and will display the serial number; example output: Oct 10 13:42:06 1 6 0 serusb_is_device_supported: Device 2 on bus 0 unrecognized. Using CDC-ACM Class Oct 10 13:42:07 4 11111 0 error opening /etc/usb/85091090FPGGS41 rc=-1 In addition to the symptoms listed above, the inability to communicate with the LON option module may cause the any of the following messages in the Serial Shell and/or the Platform Administration System Logs: error opening /etc/usb/<serial number here> rc=-1 U50Read returned unknown rc = 8!!! io_write failed ldvRC=7, length=<various numbers of bytes> The Station will most likely show that the LON network is up, but the LON devices are down. The device fault cause may show "unable to write" or something similar.

Issue How are the 'Advanced Polling Configuration' settings under the BACnet interface to be used? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause These settings can be used to reduce traffic on the BACnet networks that can overload both the EBO server as well as the devices being polled. Resolution The settings are used to specify an amount of time (in milliseconds) that the server should wait after completing a polling cycle on the applicable BACnet network before starting the next cycle. A polling cycle is the set of point being polled on a particular network interface. For example, lets assume that the Minimum polling interval for MSTPA network has been set to 1000 ms, if you are polling 30 points on MSTP port A then the BACnet plug in will do synchronous ReadProperty requests to poll each of the 30 points one at a time. Once the 30 points are polled, (one polling cycle) the BACnet plug-in will delay 1000ms before polling the 30 points again. (next polling cycle) NOTE: The settings apply to polling ONLY and do not affect communications done via change of value (COV) To find a proper value to use, it is recommended that you start with 1000 ms and then adjust the value up or down based on polling performance. If the polled values update fast enough, increase the minimum polling interval to reduce CPU usage. If the polled values become too sluggish, reduce the minimum polling interval until performance returns to satisfactory levels. It may take some trial and error to find the optimum balance.

Issue Satchwell FEU 4-port Unit Control Valve is obsolete. Product Line Field Devices Environment Satchwell FEU 4-port Unit Control Valve installations FEU4414 FEU4415 FEU4416 FEU4451 FEU4452 FEU4454 FEU4626 FEU4627 Cause Satchwell FEU 4-port Unit Control Valve requires replacement due to failure. Resolution Satchwell FEU 4-port Unit Control Valve may be replaced by Schneider Electric VZ419 series Unit Control Valve, although dimensional differences may apply.. It should be noted that VZ419 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required.   It should also be noted that any Actuator installed on the Satchwell FEU 4-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ419 4-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required. 

Issue The SmartX server has a "?" under the server name field and shows the error "SSL certificate validation failed!" as the server state in Device Administrator. In some instances, this may cause a failure to upgrade of the SmartX Server displaying these symptoms.  Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause The SmartX Server is added into Device Administrator over HTTPS 443 but does not have a valid SSL certificate installed. Resolution Change the connection from HTTPS 443 to HTTP 80 This can be done by clicking into the server settings (click on the "?") Select "Edit Connection"   Change the EBO Server Protocol from HTTPS to HTTP  Create a trusted chain between Device Administrator and the problem SmartX Server using a self-signed certificate by following this workflow

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10K Type 3 - SpaceLogic Sensors (as SLASXXX, SLAWXXX and SLABXXX), STx5xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type II (I/NET) – Thermistor 10K2A1 Dale/Vishay - STx20x Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 (No Longer Applicable for Satchwell sensors) Thermistor 10k Linearized (Satchwell DxT - Type T) - STx6xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type IV (FD) – Thermistor 10K4A1 type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 - STx1xx Sensors (see HVAC Sensor catalog for details) Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

Issue Documentation on the MSC-MPC Microsmart controller and its associated modules. Product Line TAC I/A Series Environment Microsmart controller MSC-MPC MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-MPC. Click each associated module part number below to view its installation instructions: MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO

Issue At times it is necessary to manually delete MSMQ messages Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Under certain conditions messages build up in queues and don't clear out from msmq (i.e. Cyberstation offline that is configured to receive alarms) Resolution To open MSMQ Go to Windows Control Panel> Administrative Tools>Computer Management Expand Services and Applications Expand Message Queuing Expand Outgoing Queues and select one of the entries Right Click on queue messages and select AllTasks>Purge Are you sure you want to delete all messages? Yes Repeat this for the queues that require purging Note: The IP of the Cyberstation is listed in the Outgoing Queue Channel (an offline Cyber will keep building up messages) Here is a snapshot of the queues below.

Issue Simple Modbus Lua Script Product Line EcoStruxure Building Expert Environment Lua Programming Cause Simple script to test Modbus function Resolution In each of the samples, the following needs to be observed: The Modbus port is closed and opened with the port settings. The samples can be combined but the port is only set once. The settings for the Modbus RS485 port requires an address, in this instance 99 is used. This must be different from the slaves. The nnn.MOD1 must be left unchecked so that it is not enabled. This will allow the Lua script ModbusB to work. For added functionality the "Print" command is used. The "print" command provides added functionality indicating a successful read / write in the output window. If the result = 0 then the read / write is successful. Anything else is an error code. Contact Product Support. The value = is the value that is either read in or written dependant on the function used. The following samples provide simple read / write functions.: Coil Registers Digital Input Registers Holding Registers Input Registers 32bit Floating Point

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue Network administrator needs a document explaining the impact of GCM NIM communications on his Ethernet network. Environment GCM-86xxx with GCM-ETH-001 network interface Cause Customer wants to know impact of adding GCMs to his Ethernet network. Resolution GCM NIM configuration information and general Ethernet networking information is in the "NIM Networking and Configuration Guide", F-25955-4.  This document is available via the Publication Zone on iPortal. Bulletin 96-42, provides answers to frequently asked questions regarding the GCM NIM communications. NOTE: This information is based on the use of firmware version 11.2T in the GCM-NIM-001 interface.

Issue Certificate for FDA regulations in the manufacturing of pharmaceuticals, 21 CFR Part 11 "Electronic Records / Electronic Signatures." Can Building Operation incorporate a comment section to capture a reason for change made by an operator/user? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Building Operation site in need of the compliance certificate for 21 CFR Part 11 "Electronic Records / Electronic Signatures." Usually, these are pharmaceutical manufacturing sites, and the full FDA document PRT11Elect.pdf is attached to this article. Resolution EcoStruxure Building Operation 3.2 and higher Compliance Pack enables 21 CFR Part 11 compliance for regulated industries. The Compliance Pack is an add-on module to EcoStruxure Building to help regulated industries meet the compliance requirements for Electronic Signatures & Electronic Records that are in place in the region.   This feature in our EcoStruxure Building Operation software provides facility-wide accountability and traceability of the environmental conditions that can impact the quality and safety of products developed in controlled environments in line with the 21CFR Part 11 regulation.   Compliance Pack is a licensed feature and compatible with EcoStruxure Building Operation V3.2.1 and later. Part Number Description SXWSWCMPLPK001 Compliance Pack – includes TimescaleDB, Digital PDF Signing, Change Control, For one Enterprise Server or one Enterprise Central For technical documentation and sales enablement tools for the Compliance Pack, please visit The Exchange Building & Power Extranet and use the search keyword: 21cfr ebo   EcoStruxure Building Operation 3.1 and below EcoStruxure Building Operation V3.1 and below has not addressed the pharmaceutical market and there is no electronic signature feature set that meets the FDA regulations 21 CFR part 11.   For sales issues surrounding FDA regulations, please contact through your sales channel to the local Category Manager. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue Troubleshoot Security Expert Controllers showing offline in the client. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require some common troubleshooting steps to help determine why controllers may be offline to the client. Resolution The main items to check are: Refer to the Troubleshooting Security Expert Controller Connectivity - Application Note on Exchange. If a controller has failed and the Replacement controller unable to be brought online then check if controller encryption had been enabled on the replaced controller. Restart the client software. Power restart the controller. Remove power Wait for all LED's on the controller to go completely off Apply power to the controller. In the controller web interface, on the Settings page, check that Event Server 1 has the correct IP address. Check that the Firewall is disabled. Check any Anti-Virus Firewalls/settings as well. If the Firewall cannot be disabled, ensure that all required ports are open between devices. See SX-SRVR Security Expert - Network Administrators - Installation Guide for details. Restart the Security Expert services under the PC's Services option in Control Panel. These need to be restarted when any changes are made. Confirm that the User Interface, Data Server, Event Server and Download Server module versions are all the same. Go to About  > Version and check there. If the database has not been upgraded to the same version as the client software, then this can cause communications issues. On the Security Expert Server check that MSMQ is installed as this is now a requirement   Security Expert MSMQ is required (Not showing live point status / shows "Unknown Status" error)   If MSMQ was installed after Security Expert, you'd need to reinstall Security Expert to allow it to run correctly. If MSMQ is installed and controllers are still not coming online (or the controllers are "bouncing" offline/online) then anecdotal evidence suggests enabling Windows 8 Compatibility Mode may help especially for Windows Server 2016 and Server 2019. Set the Windows 8 Compatibility Mode checkbox in the Properties page for C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertEvtSvr.exe   Also, note that if a database backup has been imported, then there is a need to check/change some other settings as well to ensure everything is set up for the specific server and controller.   Under Global > Download Server confirm that your computer name is the name of the PC where the download server service is running. Under Global > Event Servers ensure that the computer name is the name of the PC where the event server service is running. Under Sites > Controllers confirm the Serial number, IP Address, Download Port, Download Server and Control and Status Request Port match what is set in the controller's configuration web page (browse to the controllers IP Address to view). On that same General tab go to Diagnostic Windows and open the download and event server windows. Review the information contained and if there are any errors shown. Right click the controller and select Get Health Status. Review the status messages displayed.

Issue Integration to the Powerlogic CM4000 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic CM4000 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue What are the PinOuts for the RS-232 Connection of the older 1st Generation CX controllers to connect through Hyper terminal. Product Line Andover Continuum Environment Hyper Terminal Continuum CX Gen 1 CX9900 Continuum CX Gen 1 CX9940 Continuum CX Gen 1 CX9400 Continuum CX Gen 1 CX9410 Continuum CX Gen 1 CX9200 Cause Need to direct connect to a first-generation controller to configure its IP address and ACC Net ID. Resolution The Hyper Terminal cable needs to have the below pinouts. RJ Connector - - - - - - - - - - - - - 9 Pin RS-232 PC Controller Comm3 Pin 1 - DTR - - - - - - - - - - - - - Pin 6 - DSR Pin 2 - CTS - - - - - - - - - - - - - Pin 7 - RTS Pin 3 - CXD - - - - - - - - - - - - - Pin 1 - CXD Pin 4 - RTS - - - - - - - - - - - - - Pin 8 - CTS Pin 5 - GND - - - - - - - - - - - - - Pin 5 - GND Pin 6 - RD - - - - - - - - - - - - - Pin 3 - TD Pin 7 - DSR - - - - - - - - - - - - - - Pin 4 - DSR Pin 8 - TD - - - - - - - - - - - - - - Pin 2 - RD On the RJ connector for the controller's comm3, Pin 1 is the furthest to the left with the insert clip facing away from you and the gold teeth facing you (download drawing). For the CX9200 and CMX controllers download the pinouts here. Download Command Terminal Reference Guide here

Issue BACnet MSTP Wireshark capture Product Line EcoStruxure Building Operation Environment Schneider Electric StruxureWare Building Operation AS using MSTP for BACnet Cause Example of Wireshark capture and WriteProperty in MSTP    Resolution Using Wireshark, a bacapp.confirmed_service == 15 filter is applied which shows only BACnet WriteProperty packets Below is a screenshot of the Wireshark screen after applying the filter. I have Requests (REQ) and Acknowledgements (ACK) shown: Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be 0.00 Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be a value of 100.00 Filters which may be useful: Capture Filters   udp port 47808 BACnet/IP packets on UDP port 47808 udp port 47808 or udp port 47809 BACnet/IP packets on UDP port 47808 or 47809 Display Filters   bvlc || bacnet || bacapp all BACnet packets bacnet BACnet NPDU packets bacnet.mesgtyp BACnet Network Layer (router) packets bvlc BACnet/IP packets bvlc.function == 0x0b BACnet/IP Broadcast packets bacapp APDU packets bacapp.confirmed_service == 12 readProperty packets bacapp.confirmed_service==14 readPropertyMultiple bacapp.confirmed_service == 15 writeProperty packets bacapp.confirmed_service==16 writePropertyMultiple bacapp.confirmed_service==1 confirmedCOVNotification bacapp.confirmed_service==5 subscibeCOV bacapp.unconfirmed_service == 0 I-Am packets bacapp.unconfirmed_service == 8 WhoIs packets bacapp.unconfirmed_service == 2 unconfirmedCOVNotification packets bacapp.unconfirmed_service==3 unconfirmedEventNotification bacapp.unconfirmed_service==6 timeSynchronization     mstp.frame_type>2 exclude all token passing mstp.frame_type>127 view all proprietary traffic mstp.frame_type==0 only token passing mstp.frame_type==1 only poll for master mstp.frame_type==2 only poll for master responses bacapp.instance_number==[BACnet ID] all traffic from/to a specific ID mstp.dst==[MAC address] all traffic to a specific MSTP address mstp.src==[MAC address] all traffic from a specific MSTP address ip.dst==[IP address] all traffic to a specific IP address ip.src==[IP address] all traffic from a specific IP address      || (between filters) combines above filters (or)  && (between filters) combines above filters (and)   Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.

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 Some IO modules status showing as 'Blacklisted device detected" or "Address shift detected" or a system alarm is received indicating the condition. AS trace logs may show one of the following entries... 2015-08-18 17:41:02.675 [1256862784] nsp.pin.cio.IODevice Module at address 14 is reporting Internal Error Code 32 2015-08-18 17:41:02.757 [1256862784] nsp.pin.cio.IODevice Module at address 28 is reporting Internal Error Code 32 2015-08-18 17:41:02.825 [1256862784] nsp.pin.cio.IODevice Module at address 12 is reporting Internal Error Code 32 2015-08-18 17:41:02.869 [1256862784] nsp.pin.cio.IODevice Module at address 13 is reporting Internal Error Code 32 2015-08-18 17:41:02.951 [1256862784] nsp.pin.cio.IODevice Module at address 15 is reporting Internal Error Code 32   2015-06-18 10:05:13.912 [1255584832] nsp.pin.cio.CIOException Error: Bad_Address (0xb0000), module Automation_Server_Io_Bus(31), moduleCode 0, dispString "AS address is invalid", techString "nsp_servers/plugins/CentralIOPlugIn/CIO/source/IOManager.cpp line 460" 2015-06-18 10:05:20.789 [1255584832] nsp.pin.cio.IOBus IOBusServer::run: Caught CIO exception from slot 3   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause One or more terminal base may have to be replaced. Intermittent IO connection (typically in S-cable). Resolution Follow this document or Blacklisted Device Detected for steps to resolve the problem.

Issue Can the Continuum Software be downloaded from the web, or ordered on CD? Product Line Andover Continuum Environment Continuum Cyberstation software Cause Download of Continuum Cyberstation software Resolution The Continuum Cyberstation software is available for download from The Exchange Download Center. The link below will direct you to the Cyberstation software. CyberStation Software If specific older versions of software are required see Older CyberStation versions not found on the Extranet (Exchange Online). If a customer specifically requests the software on a CD, then these can be ordered through the regular Order Entry channel specifying the version required.

Issue Satchwell AR Series 7 Rotary Actuator requires replacement Product Line Field Devices Environment Satchwell AR Series 7 Rotary Actuators installed on Air Dampers, Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Actuator types :- ARE ARM ARX ARMS Cause Obsolescence of Satchwell AR Series 7 Rotary Actuators Resolution Replace Satchwell AR Series 7 Rotary Actuators with appropriate Schneider Electric MD Series Rotary Actuators and wire as follows :- Satchwell AR Series 7 Rotary Actuators installed on Air Dampers. ARE ARE Series 7 Wire Number 2 = MD20A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD20A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD20A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD20A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD20B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD20B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD20B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD20B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD20B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD20B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD20B-230 NO EARTH REQUIRED ARMS ARMS Series 76021Term 3 (Open) = MD10SR-TS Blue G ARMS Series 7602 Term 2 (L1) = MD10SR-TS Not used *1 ARMS Series 7602 Term 1 (N) = MD10SR-TS Brown GO ARMS Series 7602 Wire EARTH = MD10SR-TS NO EARTH REQUIRED ARMS Series 7603 Wire Number 2 = MD10SR-T Blue G ARMS Series 7603 Wire Number 1 = MD10SR-T Brown GO ARMS Series 7604 Wire Number 2 = MD10SR-TS Blue G ARMS Series 7604 Wire Number 1 = MD10SR-TS Brown GO *1 Disconnect from the supply, label, and make safe at the supply and actuator.   N.B. Should the Satchwell AR Series 7 Actuator (not applicable to ARMS) include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows:- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies. ARE ARE Series 7 Wire Number 2 = MD10A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD10A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD10A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD10A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD10B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD10B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD10B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD10B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD10B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD10B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD10B-230 NO EARTH REQUIRED N.B. Should the Satchwell AR 7 Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows :- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE ARE Series 7 Wire Number 2 = MD20A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD20A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD20A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD20A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD20B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD20B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD20B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD20B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD20B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD20B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD20B-230 NO EARTH REQUIRED N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows :- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Product Information. For details of AR Series 7 ARM ARX ARE please see here For details of AR Series 7602 and 7603 please see here. For details of the MD10 SR Damper Actuator please see here. For details of MD10A please see here For details of MD10B please see here For details of MD20A please see here For details of MD20B please see here For details of MD-S1 please see here For details of MD-S2 please see here

Issue When adding License Entitlements via Device Administrator using the online method. After clicking activate, a "Communication failed" message is displayed:   Could not establish contact with License Server using SmartX Server Followed by a "License Operation Failed" message:   Add entitlement failed. License Server is offline. Error code: 41 Error message: CURL error: Product Line EcoStruxure Building Operation Environment Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When activating a SmartX Server license online, the SmartX server will try to connect to the license activation server to activate the license. If it cannot resolve the license activation server site name and connect, it will show up as offline. Resolution Make sure that the SmartX Server DNS is properly configured in the AS-P.  In Device Administrator select the Ethernet 1 Configuration tab. Check the Primary, Secondary, and Tertiary DNS settings If unsure of the correct DNS address, enter the Google DNS address of 8.8.8.8 or 8.8.4.4. The example below shows a local router address as the Primary DNS and Google DNS as the Secondary and Tertiary DNS.   To confirm that the SmartX Server can resolve the license activation server address Open a Console session on the SmartX Server in Device Administrator. Enter the command: ping schneider-electric.flexnetoperations.com If the DNS is correctly set in the SmartX Server, the result should look similar to that shown below: Note: Ensure that the ASP is fully connected to the Internet in order to perform Online Embedded License Activation. You need to be connected to the Automation Server using IP (Not via USB) to activate the embedded license.