Building Automation Knowledge Base

Issue The Domain was upgraded to Windows Server 2008 and now the Workstations Windows firewall causes Andover  Controllers to go Off line. Product Line Andover Continuum Environment Windows 7, Windows Server 2008 R2 9680,9640 CX 75XX  9900, 9200 Cause Enhanced Security in the MS Server 2008 series domain enforces port blocking above ports 5000  and above. Resolution Add components , ports to the firewall exception list for Windows Firewall and for Anti-Virus Download List:

Issue Alarms need to be sent to specific Workstations and then escalated to other Workstations if they have not been acknowledged within a specific amount of time. Product Line EcoStruxure Building Expert Environment Security Expert Cause Documentation does not describe specific steps for how to configure alarm escalation. Resolution You will be able to do the alarm escalation with Security Expert by using the Alarm Routing options under the Events Menu. 1. Create your Workstations by going to Events | Workstations. The name of the new Workstation object in Security Expert will need to correspond to the actual Windows PC name for alarms to be routed properly. 2. After you have created all of the Workstations you will need to create Workstation Groups under the Events menu. One group for each level of alarm routing that you want to do. If you have three workstations and want to route from one to the next to the next, then you would need to create three Workstation Groups and add one Workstation to each of them. 3. Next you will need to create an alarm routing list under Events | Alarm Routing. On the Workstation Groups tab add the time for Transfer After (this is in seconds) which is when the alarms will be routed to the Workstations in the next Workstation Group. Set the Routing Order for those groups, the first group is 0. Next set the Transfer Priority if you have specific alarms that are to be routed to these Workstation Groups, leave blank if all alarms are to be routed. Set the routing group active to enable routing. 4. The last bit is to go to your Alarms that you want to route and add the routing list you created in step 3 to the Alarm Routing List field. This will now route these alarms to the Workstations you've configured.

Issue How and where to get the API client for V3 Product Line EcoStruxure Access Expert Environment Access Expert V3 Premise Hosted Cause Need to know where to go to get the API file for V3.  Remember, it is only supported on Win 8.1 and above. Resolution Version 3 (V3) does not use a URL to access the instance but an Application Programming Interface (API). In order to get this file, the user would follow these steps: Complete the V3 Online Training by Feenics From the course go to the last section named Downloads,  https://www.feenics.com/training/lesson/downloads/ Select the Access Expert (USA) and click on Download Save the file and then install it on a Win 8.1 or above PC When the Connection Details come up, insert the respective credentials to access your instance Once logged in, now program the system accordingly.

Issue When viewing a TGML graphic from Webstation the text and values are not aligned correctly. In Workstation the text and values are aligned fine. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.5 Cause In the Control Panel\Appearance and Personalization\Display it is possible to change the size of text and other items on your screen. If this is set  to larger than 100% the text and Values will not be aligned in in the TGML graphic in Webstation. Resolution Set the value for Control Panel\Appearance and Personalization\Display to 100% and not more. Windows 10 Right click or press and hold on your desktop, click/tap on Display settings. Click/tap on Display on the left side. If you have more than one display connected to your PC, then select a display at the top on the right side that you want to change the DPI of. Under "Change the size of text, apps, and other items", select the DPI percentage and set it to 100% and not more. Windows 7 Open Control Panel Open Appearance and Personalization Set Display to 100% and not more

Issue SEC-TE (TE2) smart terminal controller / SED-0 (DA2) smart wireless actuator will not come online in an MPM controller. Product Line EcoStruxure Building Expert, Field Devices Environment SmartStruxure Lite Multi-Purpose Manager Smart Controllers Cause The Zigbee network configuration parameters in the MPM have been entered incorrectly. Resolution The application version of the SEC-TE/SED-0 must be determined before proceeding forward. Sticker on device should read V13 or V14. To check/modify the current settings, navigate to the "ZigBee Configuration" object (ZBC) under the MPM. For Application Version 13: Stack profile should be set to "Custom" and Security profile should be set to "None." For Application Version 14: Stack profile should be set to "ZigBee Pro" and Security profile should be set to "Home Automation."

Issue Integration to the Cummins ModLon 2 gateway with the Xenta 500 / Xenta 700 / Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Cummins ModLon 2 Gateway 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 files 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. One generator: .dev file Two generators: .dev file   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 Unable to change set point from the thermostat when adjusting the value from a BAS Product Line EcoStruxure Building Expert Environment Smart Struxure Lite Cause Misconfiguration of the object and BACnet priority level Resolution 1)     When discovering the object from the BMS, it will integrate as; type: numeric point | Property ID: Present value | Name: Occupied cool Setpoint as an example. The variable will be for reading only the actual value set.   2)     To change values from the BMS and thermostat, the object shall be configured as follow: ·        Type: numeric WRITEABLE ·        Enabled: True ·        Property ID: RELINQUISH DEFAULT   From the thermostat, If the value is highlighted in RED by going to set point page 1/2, the object is misconfigured repeat step 2  

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 How can I clone an MPM? How can I upload config.db to an MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to upload config.db to an MPM Resolution An MPM can be cloned from Building Expert by exporting default.db from one MPM and importing it to another (using the "Export Database" and "import Database" buttons) Note: Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. If it is necessary to clone the system configuration objects as well, refer to the procedure below: This procedure show you how to upload the Database to an MPM. To download a backup of the database, refer to MPM database information. Power up the MPM and ensure either its IP address can be pinged or Building Expert is accessible. In address bar of browser, enter 10.50.80.3/test.html. (assuming IP address of MPM is set to default) In Remote Path field of File Upload section, enter config.db. Click Browse and Navigate to the backup config.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Note: Uploading the config.db file first does not cause the MPM to reboot; which is why it is uploaded first On Browser, click to return to previous page. In Remote Path field of File Upload section, enter default.db. Click Browse and Navigate to the backup default.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. Note: MPM must not powered off during this time In address bar, enter 10.50.80.3 to connect to Building Expert and validate Database upgrade is correct.

Issue SER8000 series room controllers communications options Environment SER8000 series room controllers Cause Integration to SER8000 room controllers via Modbus is required.  Resolution Currently, the SER8000 series room controllers communications options are Zigbee Pro or BACnet MS/TP. Refer to the SER8300 datasheet.  To communicate on Modbus RS-485, an option would be to use the multi purpose manager (MPM-UN) as a gateway device.    * Updated July 2015 As per Product Annoucement PA-00428, the SE8000 with firmware 1.3 can now act as a Modbus slave using the RS-485 port. 

Issue When using the Roam IO 2 tool, you are unable to connect to the controller using the infinet tool, but you can connect using the BACnet tool. Bluetooth has connected fine using both tools. Environment Windows 7 Roam IO 2 Infinet BACnet Cause This issue is due to a firmware mismatch. Resolution There is a new version of the RoamIO tool firmware available,  You must update to this version for the tool to connect correctly. Download the update RoamIO tool here. Using a 3rd party unzip program, Unzip the file. Update the Roam IO 2 tool with the Roam IO 2 connected Using the BACnet RoamIO software, goto tools and then update. Select the update .UPD file you have just downloaded, this will flash upgrade the Roam IO 2 to the latest firmware

Issue Service Pack 2 provides the following correction: MicroNet VisiSat import file replaces all non-ASCII chars with replacement character( Defect 31467). Fix applied so that the characters are converted correctly.  Fix applied so that points with alarms and trends results in the import file being generated. Product Line Satchwell MicroNet Environment VisiSat 2.1 Build 196 201 Cause Correction of raised defects. Resolution This Service Pack should only be added to VisiSat 2.1.196 or 2.1.200 if service pack 1 has been installed. Note: When installed, the VisiSat 2.1.96 or 200 installation (200 if service pack 1 has been installed), the build number increases to 2.1.201. (due to one of the files in 'Program Files'). VisiSat will still show as Build 2.1.196 in Control Panel - Programs - Programs and Features - Uninstall or change program. Installing VisiSat Service Pack 2 =============================== Shutdown VisiSat and the VisiSat-Server. Run "VisiSat 2.1.196 Service Pack 2.exe". Extract to VisiSat installation root drive. (or extract to another location and move the Satchwell folder, created when extracted to the root of the C: drive). To the question 'Would you like to replace the exiting file', select 'Yes to All' Restart VisiSat. Download VisiSat 2.1 Build 196 Service Pack 2. See VisiSat version 2.1 Build 196 service pack 1 where information on VisiSat 2.1 Build 196 Service Pack 1 can be found and the service pack downloaded.

Issue Issue1: Unable to use some of the function blocks in the Graphical Editor when creating a graphical program. Issue2: Unable to find some of the function blocks in the Graphical Editor Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Description of each function block is not available in Building Expert Resolution Resolution 1: A detailed explanation of each function can be found in the StruxureWare Building Expert Graphical Block Programming User Guide. Resolution 2: Upgrade MPM firmware to 2.16

Issue Replacing an older style 400 I/O with 400A series hardware, the Digital Inputs need changed to reflect the newer style of Universal Input. Product Line TAC Vista Environment Xenta 400 I/O Xenta 421, 422, 451, 452 Xenta 421A, 422A, 451A, 452A LonMaker Replace Cause Hardware changes in the Xenta 400 "A" series I/O will not function as a replacement to a non-"A" series without additional changes to Menta and LonMaker. Resolution Part 1- Changes needed within Menta Open the controller’s application (a Menta file). For ES projects, this file should be stored within C:\TAC\Vista\Applications. Note the I/O module that needs to be replaced. A list of I/O modules can be found under the Options menu on the Device Specification page:   Find and record all input points on the I/O module to be replaced. This list is found in the I/O Configuration Table under the Options menu. For example, write the "Name" and "Bound To" address for every point referencing M2.   After you have noted all of the addresses for input points on the I/O module that will be replaced, you can edit the device type for the I/O module to reflect the new type (421A or 451A). Making this change WILL remove all DI mappings (421: X1-X4) and all thermistor mappings (451: B1-B4) affected by the change in module type.   Double-Click on each DI block from the 421 (X#) or on each AI thermistor input block from the 451 (B#) that you are updating to a 421A or 451A.   The following window will appear. Click the Bind button.   Update Menta FOR 421A POINTS: The controller’s DI points are now UI points. Select the Terminal Ref based on the old mapping: X1-U1, X2-U2, X3-U3, X4-U4 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. FOR 451A POINTS: The controller’s thermistor inputs (B#) are now additional Universal Inputs. Select the Terminal Ref based on the old mapping: B1-U5, B2-U6, B3-U7, B4-U8 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. **Repeat step 7 for all affected points on the I/O module you’ve updated. Repeat steps 2-7 for every I/O module that needs to be replaced by a 421A or a 451A. PART II - Integration Within LonMaker locate the controllers that you want to change out for a 421A or 451A   Right click on them one by one, a click "Delete."   Open the Vista System Plug-In. Right click on the controller in which you want to change the .MTA application. Click "Configure."   Click "Browse," and locate the updated .MTA file you saved   Click "NO" when asked if you want to remove the devices   Click "Add and Match"   Click "Apply"   Re-Synchronize LonMaker   Your controllers should now be 421As or 451As

Issue Customers question the time sync function in AS-P for BACnet devices Environment SE8650, Viconic, SBO, AS-P, SmartStruxure, Room Controller, MSTP, 3rd Party BACnet Devices Cause It is important to understand what happens when AS-P or Room Controller lose power. Resolution SE8650 firmware version 1.7.1-56d and SBO 1.9.3.24 were used in the test. The testing was done with the fieldbus speed at both 38400 and 76800 baud. 1. The first test was to confirm AS-P sends out time sync signal 38 minutes after each hour periodically. A review of all the timeSync data packets during the capture reveals that the time sync packets are sent every hour when the time in AS-P is 38 after the hour minutes mark. 2. The second test was to confirm that the AS-P will send out a timeSync data packet if a device comes back online after a power outage. First the time was synchronized between the SE8650 with AS-P. SE8650 was then powered down and the AS-P server time changed so that the times in the two devices would not match.   A review of the time synchronization packets in the packet capture confirms that the AS sends out a time synchronization once the SE8650 is powered and boots up. 3. If the AS-P and SE8650 both lost power the SE8650 will boot up before the AS-P. The AS-P will then sends out a timeSync once the BACnet communication is settled.

Issue Cannot select data points of remote nodes to be references in a graphic on the monitor MPM Environment SmartStruxure Lite Multi-Purpose Manager MPM-VA MPM-UN MPM-GW Cause Feature not built-in Resolution When building dashboards on monitor MPMs, only local points can be used in the graphics. To be able to select points of remote MPMs, The Object_Copy script must be used. The script will copy points from the remote nodes to the monitor and make them local to that monitor MPM. This method can be used in ZigBee, Canbus and UDP networks. For example, to copy a point from each of the remote MPMs to the monitor, the script would have to be modified as follows object_list[1] = {tag = "zone1", source_device = "DEV200", source_point = "AV11", destination_device = "ME", destination_point = "AV1"} object_list[2] = {tag = "zone2", source_device = "DEV300", source_point = "AV22", destination_device = "ME", destination_point = "AV2"} object_list[3] = {tag = "zone3", source_device = "DEV400", source_point = "AV33", destination_device = "ME", destination_point = "AV3"}   Important notes: This script increase the monitor's CPU % usage and increases the traffic on the network. Therefore, depending on the size of the network, it is critical not to use more than a couple of points per remote MPM

Issue SE(R)8000 series short and long messages Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SE8000 Series Room Controllers SER8000 Series Room Controllers Ex. Viconics branding VT8000 Series EcoStruxure Building Operation Cause Configuration of the SE(R)8000 series short and long messages Resolution The short and long messages are set via BACnet. Take note that the short and long messages do not hold when power to the SE8000 is turned off. This is because currently, the messages are stored in RAM. The workaround is to change the name (from the AS) and back again then save to get it to display on the unit again. Below is the procedure to change the short and long messages in EcoStruxure Building Operation. Short Message: The Short Message can be written to the SE8000 room controller by populating the "Location" Property with the message   Long Message: The Long Message can be written to the SE8000 room controller by populating the "Description" Property with the message The message however will not get displayed until the "Display Long Screen Message" has been activated. Optional: you can also choose the color of the long message background by changing the "Long Message Background Color".     Discrepancy on the text written to the device, and the text shown on the device In some cases when using non-English characters in the messages, the text on the SE8000 will not be rendered as expected. The issue is caused by SE8300 not conforming to BACnet standard in string encoding and decoding. The workaround is to set "BACnet string encoding" property of the device to "ISO 8859-1(Latin-1)", or other encoding the device supports. SE8300 claims to support BACnet protocol revision 10, which requires the conforming device to interpret Character Set 0 as UTF-8 string. In 1.9, SBO started to write to devices using Character Set 0 for unicode strings, but the SE8300 fails to decode it. Setting the "BACnet string encoding" to Latin-1 for the devices fixes the problem. 

Issue The Pelco Endura system with cameras at a location and integrating with the TAC I/NET Seven system. Product Line TAC INET Environment Check the system requirements for the version of TAC I/NET Seven and Pelco Endura  Cause Configuration requirements of the Pelco Endura and TAC I/NET Seven are specific for the functionality in I/NET. Resolution Once your Pelco Endura system is configured and the Workstation has discovered all the devices and the System Manager is online with the cameras correctly configured, there are four basic requirements to connect TAC I/NET. Cameras have to have a unique friendly name other than default. Cameras have to have a unique camera number. Netframework 3.5 has to be installed. Windows Media Player 11 has to be installed.   If using I/NET Seven Release 2.40a then the following applies: Once INET and the requirements above are installed the Endura Install can be run. The installer for these files is located on the INET CD in the folder: Support\EnduraSDK. Note: Endura video does NOT work on Windows Vista or Windows 7.   If using I/NET Seven Release 2.40 or above: Dual NIC support is now available. For Endura, 100GB NIC and Router are suggested. 1 for I/O Server, 1  for video   Equipment used: NSMS200 Pelco Endura Network System Manager & Network Video Manager SM5000 Pelco Endura System Manager WS5070 Pelco Endura Workstation with Advanced Management Software WS5000 Pelco Endura Work Station Software package NET5301T Pelco Endura Video Encoder Spectra IV Pelco Camera Visit Pelco.com for more information. Click here to view an extended compatibility matrix for Endura and I/NET.

Issue The SX-KLCS Keypad is offline in the Client and shows ' Keypad 256 error address size' on screen If you attempt to adjust the Keypad Address in the Client it is not even visible Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS-B, SX-KLCS-W Cause SX-KLCS Keypads are normally delivered brand new to site with a default Keypad Address of 256 which the SP-C controllers cannot use and the Security Expert Client cannot even recognize to change the address via software Resolution The Keypad's address must be manually changed to a value between 1 - 254 using its touch pad. Keypad Address   Please refer to the full SX-KLCS_Security_Expert_Touch_Sense_LCD_Keypad_Installation_Manual from which this extract was taken.   Once the Keypad Address has been set to a value between 1- 254 the Keypad should then be visible to the Client and you should be able to bring it online as usual.       The SX-KLCS Keypad will now display 'Security Expert by Schneider' by default.

Issue If one Input is required to activate an Output and another Input to de-activate the Output, this Output can be defined by Input Types. The below is a simple scenario where when the first Input turns ON the Control Output turns ON, when the second Input turns ON the Control Output turns OFF. In this scenario we are activating a Duress alarm when an Input goes on and resetting that Alarm when the reset Input is triggered. Product Line Security Expert Environment Security Expert SP-C Cause Require detailed instructions on how to program a latching duress alarm scenario. Resolution Objects required:   1x Area - "Duress_Area" 2x Input Types - "Duress Enable", "Duress Reset" 2x Inputs - "VI Duress Trigger", "VI Duress Reset" 1x Output - "VO Duress Alarm"   Note: The above object names are what is used in this example, you can set these to whatever you require.     Instructions:   Creating the Area 1. Navigate to Programming > Areas. Add a new area (Duress Area), set the Entry and Exit Delay Times to 0. All other settings can be left default.   Creating the Input Types 1. Navigate to Programming > Input Types. Create a new Input Type (Duress Enable) 2. Set the Control Output to your Output (VO Duress Alarm). 3. Under Options 1 enable Generate Alarms. 4. Under Options 2 enable Activate Control Output on Alarm . 5. Set any other options that may be required. 6. Create a new Input Type (Duress Reset) and redo steps 2 - 5 above except under Options 2 enable Deactivate Control Output On Alarm.   Configuring the Inputs 1. Navigate to Programming > Inputs select the Input (VI Duress Trigger) and set the following: 2. Set the Area to the Dummy Area (Duress_Area) created earlier. 3. Set the Input Type to the Input Type (Duress Enable). 4. select the Input (VI Duress Reset) and set the following: 5. Set the Area to the Dummy Area (Duress_Area) created earlier. 6. Set the Input Type to the Input Type (Duress Reset).   Testing 1. Arm both portions of the Area 2. Activate the Input (VI Duress Trigger) to confirm Alarm is generated and Output Activates. 3. Activate the Input (VI Duress Reset) to confirm Alarm is generated and Output Deactivates. 

Issue The Drayton Theta YBL3 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBL3 Cause The Drayton Theta YBL3 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL3 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL3 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL3 Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL3 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M7 – M1 made to M7 when YBL3 Fully Closed (24Vac) Terminal M8 – M2 made to M8 when YBL3 Fully Open (24Vac) Where external wiring is connected to YBL3 Transfer Switch Terminals M7 or M8 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here. Where external wiring is connected to YBL3 Terminal M7 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 24Vac power source Terminal S2 (Normally Closed) - connect to 24Vac device previously connected to YBL3 Terminal M7 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M8 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 24Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 24Vac device previously connected to YBL3 Terminal M8   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL3 Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL3 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M7 – M1 made to M7 when YBL3 Fully Closed (24Vac) Terminal M8 – M2 made to M8 when YBL3 Fully Open (24Vac) Where external wiring is connected to YBL3 Transfer Switch Terminals M7 or M8 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here Where external wiring is connected to YBL3 Terminal M7 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 24Vac power source Terminal S2 (Normally Closed) - connect to 24Vac device previously connected to YBL3 Terminal M7 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M8 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 24Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 24Vac device previously connected to YBL3 Terminal M8   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL3 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.