Building Automation Knowledge Base

Issue An error was detected while attempting to set an attribute in a remote Infinity object Infinity Controller error: No response from I/O module Environment 99xx 9680 Continuum Cause FTT-10 IOU modules are not compatible with RS-485 Netcontrollers RS-485 IOU modules are not compatible with FTT-10 Netcontrollers Resolution There are a few ways to determine what bus topology type was built into a IOU module or Netcontroller  Take a look at the original purchase order which will indicate the type Look at the inside cover of the IOU module(s) and in the model description RS-485 or FTT-10 may be indicated Inside the cover of the Netcontroller and the IOU module there is a black component on the circuit board that has Echelon FTT-10 on it near the comm bus connector if it is FTT-10 Get the serial number of each of the IOU modules and the Netcontrollers and let Product Support know what they are, PSS can cross reference the number to determine the topology scheme from when it was manufactured If this isn't the issue then try the IOU with only that IOU connect in a different part of the IOU bus or by itself on the Netcontroller Under the cover RS-485 version - CX9900 Netcontroller 1   Under the cover FTT10 version - CX9900 Netcontroller 1

Issue Xenta Server is offline in Vista and can not be reached via web interface. Product Line TAC Vista Environment Vista 5.1.9 Windows 7 Cause The PC has proxies configured. Resolution Open Internet Explorer Go to Tools > Internet options > Connections > LAN settings Disable "use a proxy server" Related Article: Xenta Servers are offline in Vista, although they can be reached via the web interface

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 Want to change the sound that is played in Workstation when an audible alarm is triggered Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Need to attach individual alarm sounds to different alarms. Resolution EBO V2.0 or higher: You can add a custom audible alarm alert to EBO, which is an audio file that is played when an alarm is triggered. Refer to: Custom Audible Alarm Alert Workflow   SBO V1.9 or lower: The alarm sound is hard coded to the file C:\Windows\Media\notify.wav, and can't be changed from Workstation. The solution is to replace the notfify.wav file with another wave file. Please be aware that if the file is deleted, Workstation will crash when an alarm triggers. To change the file, you need to take over the ownership of the file as described here. The procedure is also described below. Browse to the folder C:\Windows\Media Right click the file "notify.wav" and click "Properties" Click "Advanced" Click "Edit" Select "Administrators" and click "Save" You get the following dialog. Click "OK", and close the properties. Open the properties again, and set the "Administrators" group to have full control Now rename the "notify.wav" file, and paste the wave file you want into the Media folder and rename it to "notify.wav"

Issue The SP-C Controller was deleted and recreated with the Controller wizard to create default objects. The Controller had previously been online and downloads were successful. After being recreated with the wizard, downloads are failing with a failed loading dat file error message seen in the Controllers Download Diagnostics Window. Failed to load DAT file. Path = 'C:\ProgramData\Schneider Electric\SecurityExpert\Download\13.dat' , Error code = 80070002 Product Line EcoStruxure Security Expert Environment Security Expert Client SP-C Cause The Controller still had configuration settings from the previous setup that were causing a conflict. Resolution Clear the Controller by factory defaulting it, then reconfigure. For instructions on how to default a controller, refer to the Hardware Configuration section Defaulting a Controller in the SP-C Installation Manual - System Controller.

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue After doing a save to database from a controller an attempt to reload the controller results in "Invalid Handle ID" or "Object not found in database" for every object in the controller. Environment CyberStation CX9xxx controller. Cause Bad object instance ID in the database. In the Continuum database each object in a controller contains the instance id of its owner controller in the ObjectIdHi field of its instance ID, this is illustrated in the screen shot below, Num1 is an InfinityNumeric created in the controller named NC2.42. You can see that the ObjectIdLo of NC2.42 becomes the ObjectIdHi of Num1 Somehow during the process of reloading a CX9200 via HyperTerminal followed by a save to database, all the objects end up with the wrong controller id in their ObjectIdHi resulting in the aforementioned error on reload. Resolution Put CyberStation in offline edit mode. Send the controller to ASCII file. Delete the controller. Import the file created in step 2 to re-create the controller and its objects. Put CyberStation online Reload the controller.

Issue Get error message 0x80004002 when trying to access objects under an OPC server in the Vista OPC tool. It is possible to see the OPC server but get the error when accessing the object under it. Environment Vista 5.1.5 Vista OPC tool Cause For some reason some important DLLs for OPC were not registered on the client PC. Resolution Register the following DLLs: opccomn_ps.dll opc_aeps.dll opchda_ps.dll opcproxy.dll

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 No more address table slots for a device involved in the attempted connection. (Subsystem:  NS Connections, #15) Product Line TAC Vista Environment LonMaker 3.X NS Connections Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same.   Cause Every LON Neuron chip has 15 total address table slots inside, which store addressing information for SNVT communication.  Xenta programmable controllers utilize Address Table slots 0 and 1 for TAC and Xenta Group Binding information for reporting online status to the Vista Server and transferring TA Network Variables to each other.  This leaves 13 available address table slots in a Xenta programmable controller.  There are many scenarios by which address table slots are consumed (both in the sending and receiving controllers).  If you have exceeded the address table limitations, no further SNVT bindings (which would require additional address table slots) will be allowed.   Resolution The error message should indicate which controller has exceeded its address table limitations (sending or receiving).  First verify the current status of the address table. Right-click on the controller Select Properties Navigate to the Address Table tab.   This will tell you (a) if the address table is indeed full or (b) how many slots you have left.  Knowing this can help you determine the easiest recourse to the problem. If the address table is full in the sending controller: Information can only be sent via one-to-one bindings to 15 controllers (13 from a Xenta programmable).  Sometimes combining data into a one-to-many can save address table slots.  Instead of sending an individual occupancy to 20 VAVs, which consumes 20 address table slots, send them all the same one-to-many occupancy command, which consumes only 1 address table slot. Using a broadcast SNVT binding type will save on address table slots by only consuming one slot per receiving subnet instead of one per receiving controller.  This will increase network bandwidth, but allows one-to-one bindings to many controllers in the same subnet.  Xenta programmable SNVT output limits would be the only limiting factor. See Bind to more than 13 unique LON devices without running out of address table entries for details on creating Broadcast SNVT Bindings. If the address table is full in the receiving controller: If the binding is a one-to-one binding type: This is typically not an issue. The receiving controller does not normally have an address table slot consumed by a one-to-one SNVT binding. The only time a receiving controller has an address table slot consumed by a one-to-one SNVT binding is if that SNVT input is set to ""Poll."" (Unacknowledged, repeated, acknowledged profiles have no bearing on the number of address table slots consumed by one-to-one bindings.)   Unless dictated by the manufacturer of the device with which you are integrating, it is very rare to require polled inputs in a Menta file. Check the SNVT AI blocks in Menta and uncheck the "Poll" checkbox. Binding these inputs will no longer consume an address table slot in the receiving controller. If the binding is a one-to-many group binding type: Every member of the binding (sending or receiving) will have at least one address table slot consumed by the group binding. Freeing up address table slots may require some creative manipulation of the bindings. Options are: Convert to one-to-one bindings where the receiving controller will not lose an address table slot Do not customize every individual combination of group bindings (i.e. send the setpoint to the same controllers that are receiving outside air temp, even if they won't be using it). Every unique combination of controllers will constitute a new group and thus consume a new address table slot in each controller.

Issue Microsoft Outlook is not emailing alarms. Product Line Andover Continuum Environment Continuum 1.XXX Microsoft Outlook 2XXX Cause The created Contact folder used by Continuum Alarms to send emails was not being shown first.. Resolution Open Microsoft Outlook Select Tools > Address Book Select Tools > Options Once opened, select  "Show this address list first:" (It defaults to the Global Address List) Ensure the contact folder with the distribution list created for Continuum Alarms has been selected (Contact) Also see online help: Email, Creating an Event Notification List

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 for assistance. Issue Require details on how to migrate Users from an SP-C-WEB to Security Expert. Product Line Security Expert Environment SP-C-WEB Security Expert Cause Have a site that has outgrown it's SP-C-WEB installation and is upgrading to Security Expert to expand. Resolution Door configuration and programming cannot be migrated from an SP-C-WEB installation to Security Expert, but the User database can be exported to a CSV file and then imported into Security Expert to help with the migration. Exporting User database from SP-C-WEB to CSV file From the SP-C-WEB user interface navigate to Users | User Search. In the User Search page on the top right (under date) is the Export button. Clicking the Export button will generate a .csv file of all User details. (See attached example Exported Users.zip) Editing User CSV file for importing into Security Expert The Security Expert User import requires the CSV file to be in a specific format: FirstName,LastName,FullName,Facility,Card,PIN,AccessLevel The rules for this format are that: Each field must have a value however the firstname/lastname can be omitted if the fullname is used and vice versa. The facility can be omitted if it is prepended to the card number and separated with a colon (eg 123:4567). If a matching Access Level is not found, a new access level is created. The PIN and Card must be unique for each user. The file cannot contain a header row. Some examples of correctly formatted data are: Joe, Stanley,Joe Stanley,123,4587,1418,Warehouse Staff Georgia, Smith,,123,4654,6884,Warehouse Staff ,,Billy Randall,123,4727,3492,Warehouse Staff Frank,Powell,,,123:4639,3160,Warehouse Staff Importing Users from a CSV File into Security Expert In the Security Expert Client navigate to Sites | Import Users to launch the Import Users Wizard. Browse to and select the CSV File you wish to import the users from, then click OK. Figure 1 - User Import Dialog The Users records are created and a message is displayed to indicate the action was successful.

Issue When saving a Plain English program, Continuum shows error messages and cannot save the PE program. 'Error: Unable to lock an object because it is already locked', or 'Unable to find an object in the database' Environment Continuum system Plain English program Cause FiringOrder attribute of the controller (or the workstation) is editlocked PE is not registered in the FiringOrder attribute of the controller (or the workstation). Resolution When saving a PE program, Continuum gets error of 'Error: Unable to lock an object because it is already locked' followed by 'Error Text Undefined [TBD 0xc2ff1410]'. This happens when the FiringOrder attribute of the controller (or the workstation) is editlocked. Unlocking the FiringOrder (Set CXName\FiringOrder Editlock = False) will fix the problem. When saving a PE program, Continuum gets error of 'Unable to find an object in the database'. This happens when the PE is not registered in the FiringOrder attribute of the controller (or the workstation). In order to Verify, open the program in the PE editor, right click inside the program, select the Firing Order, check if the program is listed on the Member List page. In order to fix the issue, verify the FiringOrder Editlock is false (ie, print CXName FiringOrder Editlock), export the PE program to a dump file, delete the PE program, import the dump file of the PE program back to the controller (or, create a new program and copy the source code from the dump file.). 

Issue What are the new features that are available in the 3.xx firmware version of the DPU. Should we upgrade to the latest EPROM revision for the DPU 7910A / 7920A If we do not upgrade the EPROM will I/NET work properly. 7910 / 7920 DPU Transactions not showing up in AMT - including Disabled / Deny Entry Sel / Deny Entry Schd (Schedule) 7910 / 7920 DPU Door Editor changes not downloaded to controller. Editor changes revert back to None. Product Line TAC INET Environment I/NET Seven DPU 7910A / 7920A 2.23 and above. Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the DPU. The recommendation is too always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. If you have any additional concerns then please contact Product Support. Below are the New Features introduced in firmware revision 3.00: This release contains changes to support a real time clock and the ability to report messages with seconds. The DPU now supports generating an alarm for a card read of a card that has been disabled. The DPU now supports the use of User defined PIN numbers. The DPU now supports soft and graced APB. The DPU has been modified to handle the new user defined Duress scheme. The DPU now has the capability of generating a Reader Tamper Alarm by configuring a two bit DA at bit offset 4 for door 1 and 5 for door 2. Click Here to review the changes for EPROM firmware revisions 2.23 through to 3.04 for both the DPU 7910A and DPU 7920A. For SCU range of controllers refer to I/NET Security Control Unit (SCU) firmware releases. 

Issue When installing SE7000/SE8000 Room Controllers to connect them to a BACnet MS/TP network, multiple issues can arise: Leaving the Room Controller's COM address at 254 (default value out of the box) will make the room controller undiscoverable by the front end. Choosing a Com address value between 128 to 253 will cause the front end system to convert the com address to 127, causing duplicates when working with multiple Room Controllers. Room controllers with COM address set to 0 will prevent the front end from discovering any devices Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Other Environment SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350, SE8600 Viconics branding VT8000 Series SE7000 Series Controllers, VT7000 Series Controllers, 7600, 7300, 7200 Cause Master devices, those who participate in the token-passing protocol, must be addressed from 1 to 127. Addresses from 128 to 253 are reserved for slaves who do not participate in the token passing; however, they can occupy lower addresses as well. Resolution COM address must be changed to a value in the range of 1-127.

Issue MPM rebooting with message in the log like: MASTER_MAN (id= 9) 361893.721> FAULT: core_watch.c:333; code:0; time:2017-02-13 15:34:25; Message:Task ID 38:Lua_User_PGs expired at 361886.5; Top Of Stack:0x000000F3 0x20D4BE7C 0x71B73B76 0x0000007A 0x00000000 0x60000013 0x60000013 0x00000000 0x2084D224 0x08080808 0x09090909 0x10101010 0x11111111 0x00000015 0x2006FD91 0x2006FD91 0x20D48D3C 0x20062159 0x00000000 0x00000000 0x20EE8248 0x20D48D3C 0x00000000 0x00000000 0x22D50000 0x00000000 0x20D1E8E4 0x000007D0 0x00000000 0x2084D238 0x00000000 0x00000000 ; Product Line EcoStruxure Building Expert Environment MPM Cause This is an error in one of the PG object (user written Lua script) possibly an infinite loop. Resolution Disable or delete 1 by 1 your Lua PG's to identify the PG with the issue.

Issue EBO 3.2.x SNMP Engine ID seen in EBO 3.2.x is not the one used by the EBO 3.2.x system. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v3.2) Building Operation Automation Server (AS-P and AS-B) (from v3.2) SNMP Cause EBO 3.2.1 introduced a new SE3Linux operating system for the AS-P and AS-B servers. The engine ID: seen in Device Administrator or Workstation is the engine ID: contained in Linux, this is not the one used by EBO 3.2.x Resolution The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Device administrator: The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Workstation The engine ID used by EBO for this example would be: 0x80002a1d03005006042bd7 The difference is always 2a1d compared to 1f88 and the rest of the bytes are the same. For further information see the attached document SNMP SBO 3.2.x Engine ID Explained.

Issue Writing directly to a SR (set-reset) simple block in a Xenta 700 Menta application where that SR output is sent to a Delay block, the Delay block may not delay. The output on the Delay block will be set immediately, without any delays. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around by not writing to the SR block itself, but to a block in the logic before the SR block.

Issue Importance of correct selection / installation of Satchwell 3-port Valve Body to provide Mixing function or Diverting function. Environment Satchwell 3-port Valve Body to provide Mixing function or Diverting function in heating or cooling circuit.   Satchwell MB, MBF, MJF, MZ, MZF, MZX Cause Incorrect selection / installation  of Satchwell 3-port Valve Body to provide Mixing function or Diverting function may result in poor control, damage to the Valve Body, damage to the Valve Actuator or damage to the hydraulic installation. Resolution Determine which of the following types of hydraulic circuit the Satchwell 3-port Valve Body is to be installed in. Constant Temperature Variable Volume (CT) circuit e.g. AHU Heating / Cooling Coil or Calorifier Coil  Variable Temperature Constant Volume (VT) circuit e.g. Radiator System For Constant Temperature circuit application install Satchwell 3-port Valve Body as follows :- MJF, MZ, MZF, MZX install in RETURN pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Coil Return (IN) Port 1 - Connect to System Return (OUT) MB, MBF install in RETURN pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Coil Return (IN) Port 1 - Connect to System Return (OUT) OR MB, MBF may alternatively be installed in FLOW pipework Port 3 - Connect to Bypass (OUT) Port 2 - Connect to Coil Flow (OUT) Port 1 - Connect to System Flow (IN) For Variable Temperature circuit application install Satchwell 3-port Valve Body as follows :- MJF, MZ, MZF, MZX install in FLOW pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Boiler Flow (IN) Port 1 - Connect to System Flow (OUT) MB, MBF install in FLOW pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Boiler Flow (IN) Port 1 - Connect to System Flow (OUT) OR MB, MBF may alternatively be installed in RETURN pipework Port 3 - Connect to Bypass (IN) Port 2 - Connect to System Return (IN) Port 1 - Connect to Boiler Return (OUT) N.B. It should be noted that the alternative installation methods are valid for the MB and MBF Valve Bodies due to the ROTARY SHOE construction of the MB and MBF Similarly it should be noted that the alternative installation methods are not valid for the MJF, MZ, MZF and MZX Valve Bodies due to the PLUG AND SEAT construction of the MJF, MZ, MZF and MZX . Failure to install MJF, MZ, MZF and MZX Valve Bodies correctly in the pipework may result in VALVE VIBRATION in the pipework caused by WATER HAMMER    INSTALLATION OPTIONS - MJF, MZ, MZF and MZX 3-PORT PLUG AND SEAT VALVES MAY BE INSTALLED TO MIX IN THE FLOW VALVE BODIES USE TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT(Port 1)   3-PORT PLUG AND SEAT VALVES MAY BE INSTALLED TO DIVERT (BY MIXING) IN THE RETURN VALVE BODIES USE TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT(Port 1)   INSTALLATION OPTIONS - MB, MBF  3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO MIX IN THE FLOW USING TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT (Port 1) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO MIX IN THE RETURN.USING ONE “IN” PORT (Port 1) AND TWO “OUT” PORTS (Ports 2 & 3)) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO DIVERT IN THE RETURN USING TWO “IN” PORTS (Port 2 & 3) AND ONE “OUT” PORT (Port 1) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO DIVERT IN THE FLOW USING ONE “IN” PORT (Port 1) AND TWO “OUT” PORTS (Port 2 & 3)   RELATED INFORMATION - DIVERTING IN THE FLOW It should be noted that some manufacturers produce 3-Port Plug and Seat Valve Bodies specifically designed to DIVERT in the FLOW.  Such Valve Bodies have 1 IN Port and 2 OUT Ports   Please check the latest catalog for current equipment.  

Issue A replacement gland kit for a Satchwell 9.5mm valve spindle is required. Environment Satchwell Gland Kit 9.5mm spindle Cause Customer cannot identify the valve, but has accurately measured the spindle. Resolution A 9.5mm spindle was used on the VZF/MZF 65mm-150mm valve ranges, therefore the gland kit is the 626-9-311. To review the VZF data sheet please click HERE. To review the MZF data sheet please click HERE.