Issue An update from 1.94 to 1.94 SP1 will generate an "Installation error! Microsoft ODBC SQL Server Driver SQL Server Implicit conversion from data type datetime to int is not allowed. Use the CONVERT function to run this query." Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A column in the db doesn't get converted properly SQL Server Implicit conversion from data type datetime to int is not allowed Use the CONVERT function to run this query. Resolution To correct this issue apply the following hotfix AFTER installing 1.94 SP1 but BEFORE running the database update Hotfix for DataBase Update Error

Issue SP-C-WEB Recommended Limits Product Line Security Expert Environment Security Expert SP-C-WEB Cause The SP-C-WEB limitations are mentioned in briefly in the SmartX Controller SP-C-WEB presentation but detailed information on this is not available in the current SP-C-WEB documentation.  Resolution Schneider Electric's recommended limits for the SP-C-WEB:Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000 Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000

Issue Not receiving SNMP point value in the Trap Message. Environment Windows XP BCX 4040 Hp Pro Tools Cause Current BACnet MIB's not installed Resolution Download and install the latest MiBs Version 2.0

Issue SNMP Flashing options for Netcontrollers and BCXs Product Line Andover Continuum Environment All Continuum master controllers Cause Documentation Resolution BCXs & Netcontrollers can be in 3 states: SNMP Standard is how all controllers are shipped by default. This means that the controller model and some other object info can be obtained via SNMP. SNMP Alarming Enabled means Standard SNMP as well as SNMP Alarming is enabled in order to send alarms to a network management system. This is a paid for option either initially when the controller is ordered or by contacting repair. To enable this option in the field, repair sends a file and instructions after payment. SNMP Disabled means that no SNMP information will come from the controller. Upgrading controllers with future firmware versions Depending on which SNMP option state the controller is in will determine the application flash that should be used going forward. Selecting the incorrect file can disable or re-enable SNMP options. Netcontroller v1.5300x SNMP Not Set means no SNMP options will be changed when upgrading firmware v1.5300x Standard SNMP means use with Standard SNMP (default) v1.5300x SNMP Alarming Enabled means use when SNMP Alarming is enabled (Not Set could be used also since it will not change the enabled option) v1.53 SNMP Disable means this will disable All SNMP traffic, Standard and Alarming BCX Use the default firmware upgrade after SNMP is enabled. If you use the BCX SNMP Disable flash files and then upgrade to a newer version of firmware, you will have to run the disable flash file again to disable SNMP. NOTE: The flash files used to disable SNMP are posted on The Exchange. Note2: If the flash file doesn't enable the options because it was sitting at resetting controller,  Reload the controller which will force a reset and then try the flash file again.

Issue Instructions are needed to configure the new SMTP configuration. Product Line Andover Continuum Environment Continuum Non-Microsoft Exchange/Outlook SMTP Email Cause Configuration for the SMTP Configuration for email alarming in Continuum 2.00 through 2.03 Resolution In Cyberstation 2.0 and above, you no longer need Microsoft Outlook and Exchange to send email alarm notifications. Other SMTP servers can be used on the network and other email clients can be used also to send email alarm notifications directly to an intended recipient. Note: Public SMTP servers such as Gmail SMTP and Yahoo SMTP do not currently work with this solution as they require SSL or certain unsupported port combinations. The connections these servers establish cause connection issues within the SMTP application. Private SMTP (In-house) servers can be set up and used.   Steps to Configure SMTP Email Alarming   Open and Event Notification Navigate to the Actions Tab Select which events to receive email alarms Select the Delivery Tab Click the Add Recipient button to open the recipient configuration Browse for the recipient Cyberstation by click the ellipsis Select the recipient Cyberstation Select the SMTP Configuration button in the Recipient Configuration window Fill in the Server Configuration fields in the SMTP Configuration window Specify the SMTP Server address, port and login information Fill in the Email Configuration Specify the sender's email address - this is the email address the email will be sent from and it is also the email address that failed emails will be sent to    Type in a Subject line if needed or the default Continuum email subject line will be used Alarm Option Settings - Fill in the RetryCount and Retry Time fields  Retry Count - once you pass this value the email is dropped. The maximum Retry Count is 10  Retry Time -  field is in minutes. The maximum is 1440 minutes (24 hours) Adding an email address to the recipient list Click the Display Master List to open the SMTP Master Email Configuration Dialog Place a check in the check box to add an email address from the existing Master List to the Event Notification's recipient list and then click OK Adding or deleting email addresses from the Master Email list Open the SMTPMasterEmail Event Notification in the templates folder In the opened SMTPMasterEmail Event Notification click the Display Master List button Click the Add Recipient or Delete Recipient button depending on what is needed After selecting Add Recipient supply the email address in the recipient field and click Add Recipient After selecting Delete Recipient, select the address to highlight it and then click the Delete Recipient button. Multiple Selection is supported To deliver email notifications to the added email address, select the check box next to it Testing to ensure email address recipients receive emails Select the address you wish to test and click the Test Selected button Successful email to SMTP Server test will display a pop-up Failed email to SMTP server test will display a pop-up to the Sender's email address Final address configuration Recipients Configuration Options Place a checkmark next to the option needed Ex. Primary or Backup  SMTP Email A checkmark next to Repeat. Repeat will function as if it were an Outlook email alarm and send until the alarm is acknowledged. Known issues: In order for BACnet controllers to use the new SMTP feature, the following hotfix from the following link is needed.  CyberStation v2.00 (Only) SMTP Emailing & BACnet Alarms - Hotfix 2.03 contains the hotfix listed above   For additional information, see the Cyberstation Help, search for SMTP.

Issue Cannot see a SE7300 Room Controller when connected to a BACnet MS/TP network. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SE7000 Series SE7000, SE7200, SE7300, SE7600, SE76x7 Ex Viconics branding VT7000 Series Viconics room stats with BACnet communications Cause Units are shipped from the factory with the BACnet network disabled. Resolution Power up the unit. Press the middle button down for 8 Seconds (It is either the Override or °C/°F Button depending on model). Enter the password if it has been set, or leave as the default 0 for no password (as shipped from the factory). Use the down key to find the "Comm Addr" value. By default this is set to 254 BACnet communications disabled. Adjust this to the desired value within the valid range of 1 to 127, but also ensure it is in the range of your BACnet Max Master setting on the connected system. Once set, power off/ on the unit to change the address to the new value. The unit should now be visible on the BACnet MS/TP network.    Note: The SE7xxx Room controllers will auto baud to match your MS/TP network, there is no baud rate setting to adjust. Also any password set on the SE7xxx controller must be temporarily disabled to allow the middle button to operate correctly. For further information on installing the Room Controllers please see SE7000 Series Installation Instructions.

Issue Where should door connection be made on a SCU1284 Termination, Terminal number, PIN, SCU1284 Environment I/Net SCU1284 Cause What output to use for door contact Resolution This information is taken from TCON 312.  

Issue Clarification on dip switch six and station addressing for the SCU1200, SCU1280, or SCU1284 Product Line TAC INET Environment I/NET Seven with Access Control using an SCU SCU1200, SCU1280, or SCU1284 Cause Clarification on SCU and dip switch settings being open, enabled for dual or single station addressing (2 or 4 doors) Resolution If the Device Type is SCU1200, SCU1280, or SCU1284: set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON). In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode. Though the TCON312 shows the dip switches for 1-6, there is still a bit of clarity which can be provided on how that looks on an actual SCU. The example from the TCON is shown here: And this is a photo below of an SCU which is setup as 0101 with dual addressing since Dip Switch 6 is in Dual Address mode shown in the picture below. When penetrating down to it using Edit, Host Computer, Network Configuration, SCU 1284 is shown with 2 Points with door addresses: 010108 Door1 010109 Door2 010208 Door3 010209 Door4 After checking MCU Configuration, I added the points in the Network configuration. The main point here is that Dip Switch 6 is up on the Open side of the Switch bar shown in red which is the dual point and 4 door configuration.   Note: Concerning the numbering scheme for addressing the SCU, it is important to number your SCUs with an address then skip the next number so in the event you dual addressing for four doors, the second address is available. Don't use addresses 28, 29,30, and 31 as those are reserved for the Remote Arming Terminal.  Overlooking this can result in future headaches of moving SCUs around in the addressing scheme which is never recommended. Example for a site containing 4 SCU door controllers: SCUa address 2, SCUb Address 4, SCUc Address 6, SCUd Address 8.  Another example configuration: One reader inputs to READER1 and READER2? Here is that wiring example. In order to use more than the first eight inputs on the SCU, you must configure the SCU as a double-address controller. When you enable the double-address mode (DIP switch S1-6 = ON), inputs 1 through 8 are monitored on the selected subLAN address (i.e., the primary address) and inputs 9 through 12 are monitored on the next consecutive subLAN address (i.e., the secondary address). The input points are defined in the I/NET host using two separate SCU controller assignments, the first providing eight input point definitions and the second providing 4 input point definitions. The SCU’s outputs are also divided across two LAN addresses when the SCU is operating in the double-address mode. The first four outputs are assigned to bit offsets 00 through 03 on the SCU’s primary address. The last four outputs are assigned to bit offsets 00 through 03 on the SCU’s secondary address.

Issue There is a compatibility issue between Revision 2 MNL controllers and S-Link sensors. This incompatibility is noticed when a later production S-Link sensor is connected to an older Revision 2 controller. When the sensor is connected to the controller, 88.8 appears on the sensor’s display window along with all of the other LCD icons. The display never recovers from this mode, which makes the sensor non-functional. Product Line TAC IA Series Environment MN-Sx sensors MNL-10Rx1 and MNL-20Rx1, where x denotes profile type (F, H, R) MNL-V1RV1, MNL-V2RV1, MNL-V3RV1 Cause New MN-Sx production S-Link sensor firmware is not compatible with older Revision 2 MNL controllers. Resolution Newer model S-Link sensors have been released to address this issue. The new part numbers are MN-S1-2, MN-S2-2, MN-S3-2, MN-S4-2, and MN-S5-2. The MN-Sx-2 model line was designed and verified to work with older Revision 2 controllers.  Reference TPA-RKFD-09-0028-00 for more details. Please note that the new MN-Sx-2 S-Link sensors are only for use with older Revision 2 controllers.

Issue S-E VZ29, VZ39 and VZ49 Unit Control Valve Open / Close status required relative to spindle position. Environment S-E VZ29, VZ39 and VZ49 Unit Control Valve installations. Cause Open / Close status of S-E VZ29, VZ39 and VZ49 Unit Control Valve is not visually apparent Resolution Observe S-E VZ29, VZ39 and VZ49 Unit Control Valve spindle position. S-E VZ29, VZ39 and VZ49  =  Spindle DOWN OPEN / Spindle UP CLOSE   Please check the latest catalog for current equipment.

Issue Does Vista support virtualization? Will Vista run on a virtual PC, VMware, virtual environment? Product Line TAC Vista Environment TAC Vista all versions VMWare, Player, Workstation and Server Microsoft Virtual PC Cause For many companies, the largest benefit of server virtualization is in reducing the amount of hardware that is required to run all the software needed by the business. Consolidating servers using a virtualization process not only provides savings in terms of how many physical machines must be bought and maintained, but also potentially reduces the amount of physical space that a company needs for its servers or data centre. Resolution Virtualization is a term that allows software in emulating environments, such as VMware / Virtual PC. These software packages emulate a PC environment so that many computers appear to be running on one single machine, thus “virtualization”. The general impression is that the emulation packages work very well. The user must be familiar with the emulating product in order to be able to do the correct settings. No matter if it runs on PC hardware or in an emulating environment, the specific product is supported given the problems are related to the Software itself, but not for problems related to the environment it runs on. Particular note and understanding is required when dealing with multiple applications trying to access a single piece of hardware, such as serial ports, USB and the like. Please see the following TPA-MALI-09-0013.00 for additional information. Also note that Vista Licensing system is NOT supported when using Remote Desktop.  Refer to the following article for further details: Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system.

Issue Upgrading  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Guidelines for upgrading to higher releases Resolution Non-Sequential Upgrades: Versions 1.9.1 and Newer Starting in version 1.9.1, non-sequential upgrades can be performed from versions 1.5.X and newer. Please refer to the "Upgrading" section of the Release Notes for the software version you are upgrading to. The "Upgrading" section will direct you to prior release notes that you need to read through before upgrading and point out items with limited runtime compatibility during the upgrade process.  NOTE: If upgrading a system at 1.5/1.6/1.7/1.8 with LON devices, please be aware that there are special steps that must be taken to prepare the database for upgrade. These steps can be found in the Release Notes as well.  Sequential Upgrades: Versions 1.8.1 and Older For versions 1.8.1 and older, the upgrade process is sequential. In other words 1.2.0, 1.3.0, 1.4.0, 1.4.0.4020, 1.5.0, 1.6.1 The upgrade process can be found in the System Upgrade Reference Guide. The primary released versions were 1.0.0.161 1.1.0.362 1.2.0.767 1.3.0.938 1.3.0.10100 SP1 1.3.0.20011 SP2 1.4.0.4020 1.4.1.68 1.5.0.532 1.6.0.250 (RC) 1.6.1.5000 1.7.0.255 (RC) 1.7.1.89 The minimum upgrade path would be: 1.0.0.161 Official Release 1.1.0.362 Official Release 1.2.0.767 Official Release 1.2.0.2207 1.3.0.938 Official Release 1.3.0.10100 1.4.0.4020 1.4.1.68 Official Release 1.5.0.532 Official Release* 1.6.1.5000 Official Release 1.7.1.89 Official Release Note: On one site, the AS would not upgrade from 1.5.0.532 to 1.6.1.5000. Going to the 1.6 RC resolved the issue.   1. In order to upgrade to 1.5 the site must be at 1.4.0.4020 or higher. Some sites may be still running at 1.4.0.818, which was the original 1.4.0 release. Although this is not officially supported and will not be tested, it is likely to experience the same upgrade as one from 1.4.0.4020. 2. An upgrade from 1.4.0.4020 to 1.5 will NOT offer any runtime compatibility, while an upgrade from 1.4.1 to 1.5 will offer runtime compatibility. Consequently, for a site to maximize its operational status through the upgrade, we have two different upgrade scenarios as described below. a. 1.4.0 to 1.5 – this process flow is designed to allow as much of the plant as possible to continue to operate through the entire upgrade. For the first three steps of the process the Enterprise Server will continue to aggregate the alarms from all of the 1.4.0 Automation Server. Once the halfway mark is reached the Enterprise Server can be upgraded and will begin to aggregate the alarms from the 1.5.0 Automation Server.              i. Upgrade one WorkStation in order to be able to communicate directly to any of the 1.5 Automation Server that are upgraded in b below.             ii. Upgrade 50% of the Automation Server             iii. Upgrade Enterprise Server and all but one WorkStation             iv. Upgrade the remaining Automation Server             v. Upgrade the remaining WorkStation b. 1.4.1 to 1.5 - In this process, we can take advantage of the support for runtime compatibility and the Enterprise Server will receive alarms from both the 1.4.1 and the 1.5 Automation Server.             i. Upgrade Enterprise Server and all but one WorkStation which can be used to talk directly to unupgraded Automation Server if configuration changes are needed             ii. Upgrade Automation Server             iii. Upgrade final WorkStation Note: some sites have experienced issues with the ES restart after upgrade because of the .Net Framework 4.5 upgrade and port 80 usage. Adjusting this port to an available port resolves the problem. The conversion log may indicate an upgrade warning similar to warning shown below, this warning can be safely ignored, and furthermore the upgrade program corrects the problem in the 1.5 database.           :02:11  WARNING:      Property PFE202_PF601.SI in (~/BACnet/Application/ELE/GRAPHIQUES/ECLUSES CD S4/PORTES_CE_S4) is not defined in the new system, skip           PFE202_PF601.SI. <script src="chrome://dce.addin/content/content_javascript.js"> </script>

Issue What port numbers do routers have to have open in order to run a Continuum system? Product Line Andover Continuum Environment Cyberstation Continuum BACnet / Infinet Controllers TCP/IP Cause There have been many questions on which network ports the Continuum system uses for communication. Below is a listing of the network ports along with what the port is being used for. Resolution The destination UDP port from the controller will always be one of the below port numbers. The source UDP port that the controller uses is completely arbitrary and will be anywhere from 32768 to 65534. (0x8000 to 0xFFFE) Controller/Cyberstation Application Packet type Decimal port number Hex Port numbers   Controller Error Log Tool - UDP 33487 0x82CF BACNet B4 controller Point Configuration UDP 33487 0x82CF BACNet B4 controller Alarm Configuration, Alarms, and COV UDP 47808 0xBAC0 BACNet B4 controller Controller flash TCP 33456 0x82B0 BACNet B4 controller Web Server TCP 80 NetController Point Configuration, Alarms, and Events UDP 33487 0x82CF Netcontroller Save from Controller TCP 33440 0x82A0 NetController Controller flash TCP 33456 0x82B0 Sending Email  TCP 25 NetController WebServer TCP 80 (but configurable) CX9702 ** Point Configuration, Alarms, and Events See Note 33487 0x82CF CX9702 ** Save from Controller See Note 33440 0x82A0 CX9702 ** Controller flash See Note 33456 0x82B0 CX9702 ** WebServer See Note 80 (but configurable) ** Note: UDP or TCP port (user configurable via the TransportType attribute) Remote View Remote view Video TCP 18772 0x4954 CyberStation Controller Alarms and Events UDP 33487 0x82CF CyberStation Peer Cyberstation communication UDP 44224 (1.4x and 1.5x), 47808 (all other revisions) 0xACC0 (1.4x and 1.5x), 0xBAC0 (all other revisions) CyberStation Workstation to SQL database TCP Determined by Microsoft, 1433 by default CyberStation BACNet communication UDP 47808 0xBAC0 CyberStation MSMQ TCP 1801 0x0709 CyberStation MSMQ UDP 3527 0x0DC7 CyberStation MSMQ UDP 1801 0x0709 CyberStation MSMQ RPC 135 0x0087 CyberStation MSMQ RPC 2101*,2103*, 2105* 0x0835, 0x0837, 0x0839 *Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801. The Message Queuing Independent Client multicasts a server discovery broadcast over reserved UDP port 1801. Message Queuing Servers listen on TCP port 2101* for RPC-based MQIS and Active Directory lookups. Message Queuing 3.0 independent clients and Message Queuing servers make MQIS requests directly to Active Directory by using LDAP on TCP port 389. Message Queuing Independent Clients and Servers listen on fixed TCP port 2103* and 2105* for RPC-based remote reads of their public queues and private queues. Also, the Dependent Client uses these two ports to communicate with its server for send and for receive. There is a dynamic RPC port that is assigned by the RPC layer for handshaking with an Independent Client or with an RPC server for the Message Queuing Server to determine the fixed ports. This is typically port 135. The internal "ping" mechanism for Message Queuing operates over reserved UDP port 3527. When you use HTTP messaging in Message Queuing 3.0, Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801. * These port numbers may be incremented by 11 if the initial choice of RPC port is being used when Message Queuing initializes. A connecting QM queries port 135 to discover the 2xxx ports. For more information on MSMQ ports check with Microsoft, http://support.microsoft.com/kb/178517 A .PDF document containing this Network Port information can be downloaded Here.

Issue There are "Local Network: and "By Network" options that allow to just connect to the local network or just a b3 Environment RoamIO2 Bacnet Windows7 Windows 2008 Cause By default, the RoamIO2 Bacnet Service Tool has "Local Network" and "By Network" options which may attempt to access all bacnet devices across the entire bacnet network depending on what is selected. This includes all controllers connected to a routing device (BCX/AS/ES). The amount of controllers and the size of the network can cause a long delay in bringing up controllers. Resolution Ensure that the RoamIO2 firmware has been updated to V1.110002 or greater. This version introduced the "Local network" and "By Network" selections in the Bacnet Service Tool. Download details of the Network Targeted Search with snapshots Download the firmware RoamIO2Appl2.000002) Download the Bacnet Service Tool and user guide(1.110003) (Download Center)

Issue A TAC Xenta programmable controller has issues, and more information is needed to analyze what is happening in the controller. Product Line EcoStruxure Building Operation Environment TAC Xenta 280 TAC Xenta 300 TAC Xenta 401 XentaErrorLogViewer Cause The TAC Xenta 280, 300 and 401 series has an internal Error Log, that in some cases could give more information about the way the device is acting, storing restart reasons etc. Resolution The XentaSystemErrorLogViewer is used to read out the internal error log file from a TAC Xenta 280, 300 or 401 device. The XentaSystemErrorLogViewer is a program that runs in your PC, and you have to connect to the TAC Xenta device by the use of a serial cable. You must have at least the same version number of the XentaErrorLogViewer as the device you want to read the information from. Please note that the XentaSystemErrorLogViewer program only works with released version of the TAC Xenta 280, 300 or 401 devices. 1. Download XentaSystemErrorLogViewer 2. Install the program 3. Connect the TAC Xenta to the PC using the TAC Xenta programming cable. Refer to the cable guide for further information. 4. In "Preferences", select the COM port to which you connected the serial cable 5. Check "Write System Error Log to file" 6. Click "Get new information" 7. The information is written to "C:\Windows\Temp\XentaSystemErrorLogg.txt"

Issue Are there resources for configuring a 7750 Building Manager? Product Line TAC INET Environment I/NET site Cause The Building Manager (BM) is based on a zoned programming approach. Zones are groups of points in a system which control related equipment. A good example of a zone would be a group of points that control the lighting, heating and air conditioning for a tenant that occupies 1 floor in a multi-story building. The major function of the building manager is to give the tenant control over this equipment (through a user friendly telephone interface) and to be able to accumulate statistics to be used for billing normal and after-hours energy usage. Resolution Good sources: TCON098 TCON209 (7-28 through 7-38) TCON237 (7-28 through 7-39) Tech Tip 038

Issue Is it possible to directly replace a TCX867 with an i2867? Environment TCX867, i2867 Triac Output negative, positive, load switching Cause The two products have different output circuitry and the i2867 will not always be a direct replacement. Resolution Both the i2867 and the i2867 have triac outputs that only switch AC loads.  The i2867 outputs internally have one side connected to ground, hence the terminals are labeled Outx (Out1, Out2 ..) and Gnd, this means that when switching electrical loads they must switch the return path from the load, not the power feed to the load. The older TCX867 has isolated outputs and could switch either the Power or ground side of the switched load. It has 2 terminals on each output both labeled with the channel name i.e. Out1 on both terminal 1 & 2. So you can replace a faulty TCX867 in the field with a i2867, but it may require changes to the plant wiring to ensure the -Ve side of the load is switched, failure to do this can result in damage to the i2867. See i2867 installation guide for full details on installing an i2867

Issue Satchwell "AL..S" series Spring Return Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell “AL..S” series Spring Return Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Cause Obsolescence of Satchwell “AL..S” series Spring Return Linear Actuator. Resolution Replace Satchwell ALMS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALMS Actuator. It should be noted however that the S-E M700 Actuator is suitable for use with 24 volt power supplies only, while the Satchwell ALMS Actuator is a mains voltage device. The S-E M700 Actuator has an average power consumption of 30 VA and the use of an independent 230 / 24 volt Transformer rated 50 VA is recommended.  S-E Transformer Type TR60 (341-3060-000)   Replacement of Satchwell ALXS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALXS Actuator. It should be noted however that where an existing Satchwell ALXS Actuator has been connected to a Satchwell Climatronic Controller via an independent Transformer, it is probable that the Transformer will have been rated to provide the level of power required by a single ALXS Actuator (23VA) In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E M700 Actuator (50VA) S-E Transformer Type TR60 (341-3060-000)   Replacement of Satchwell ALES Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALES Actuator. It should be noted however that where an existing Satchwell ALES Actuator has been connected to a Satchwell Climatronic Controller via an independent Transformer, it is probable that the Transformer will have been rated to provide the level of power required by a single ALES Actuator (26VA) In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E M700 Actuator (50VA) S-E Transformer Type TR60 (341-3060-000)   Please check the latest catalog for current equipment.

Issue Satchwell "AMS" series Spring Return Rotary Actuator requires replacement by S-E M700 Spring Return Linear Actuator due to obsolescence. (Actuator Wiring) Product Line Field Devices Environment Satchwell “AMS” series Spring Return Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  N.B. Where a Satchwell "AMS" series Spring Return Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. Please refer to Replacement of Satchwell "AMS" or "AMSH" (high torque) series Spring Return Rotary Actuator Cause Obsolescence of Satchwell "AMS" series Spring Return Rotary Actuator. Resolution Replace Satchwell AMS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell AMS Actuator. It should be noted however that the S-E M700 Actuator is suitable for use with 24 volt power supplies only, while the Satchwell AMS Actuator is a mains voltage device. The S-E M700 Actuator has an average power consumption of 30 VA and the use of an independent 230 / 24 volt Transformer rated 50 VA is recommended. S-E Transformer Type TR60 (341-3060-000) Please check the latest catalog for current equipment.

Issue Satchwell "AMS" and "AMSH" series Spring Return Rotary Actuator requires replacement by S-E M700 Spring Return Linear Actuator due to obsolescence. Product Line Field Devices Environment Satchwell "AMS" series Spring Return Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Satchwell "AMSH" series Spring Return Rotary Actuator installed on Satchwell MZF or VZF series 125mm and 150mm Plug and Seat Valve Body. N.B. Where a Satchwell "AMS" series Spring Return Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. See Replacement of Satchwell V V series Butterfly Valve Body Cause Obsolescence of Satchwell AMS and AMSH series Spring Return Rotary Actuator. Resolution The new actuator is 24Vac and the control signal will need to be converted from 230Vac to 24Vac, this could be achieved by a transformer and 2 off 230Vac relays. The old signals switch the coils of the relays. The relay contacts switch 24Vac to the new actuator. Replace Satchwell AMS or AMSH series Spring Return Rotary Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit: AMS = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up          ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down     ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AMS series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation. Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell AMS Spring Return Actuator. Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator. Please check the latest catalog for current equipment.