Building Automation Knowledge Base

Issue The MVB actuator is no longer available from Schneider Electric Replacing a Controlli S300 Actuator Product Line Field Devices Environment VMB valves MVB actuators S300 actuator Cause Only the actuator requires replacing but the MVB is no longer available from Schneider Electric. Resolution Note: The MVB actuators are still manufactured by Controlli, but not distributed by Schneider Electric. Use the AG52 valve linkage kit 880-0129-000. For the Controlli MVB22, MVB26 and MVB28 or S300 replace with the MV15B-230 actuator For the Controlli MVB46 replace with the MV15B-24 actuator For the Controlli MVB32, MVB52 and MVB56 replace with the M800 880-0310-030 actuator If a D36 auxiliary switch was fitted in the  the MVB actuator or if the auxiliary switch was used in the S300 actuator then the following auxiliary switch packs can be used: M800, use the 880-0104-000 kit or order the M800-S2 880-0311-030 actuator which includes 2 auxiliary switches. MV15B-24/230, use the 880-0469-000 kit. Note: if the valve also requires replacing see VSB, VSB..F, VMB, VMB..F Schneider Electric replacement valves.

Issue The default dynamic port range for TCP/IP has been changed with Windows Vista and later Microsoft operating systems. Product Line Field Devices, Satchwell Sigma Environment Microsoft Windows Vista Microsoft Windows 7 Microsoft Winsow 8/8.1 Microsoft Windows Server 2008 Ethernet communications Microsoft Windows 10 and server 2012, when Sigma is part of an SBO/EBO front end system. Cause To comply with Internet Assigned Numbers Authority (IANA) recommendations, Microsoft has increased the dynamic client port range for outgoing connections in Windows Vista, Windows 7 and in Windows Server 2008. The new default port range starting at port 49152 through to port 65535. This is a change from the earlier Windows configuration that used a default port range of 1025 through to 5000. Sigma used port 49152 as default for communications between Sigma server and Sigma controllers. Resolution You can use SE Legacy Port Reservation to reserve the port used by Sigma. Another resolution would be to redefine the dynamic port range Windows Server 2008 can use to 50000 to 65535, hence keeping the port free for Sigma. (Sigma port requirements can be found in What port numbers are used by the Sigma system?). You can view the dynamic port range on a computer that is running Windows Vista, Windows 7, Windows Server 2008 or 2012 by using the following netsh commands: netsh int ipv4 show dynamicport tcp netsh int ipv4 show dynamicport udp netsh int ipv6 show dynamicport tcp netsh int ipv6 show dynamicport udp Note The range is set separately for each transport and for each version of IP. The port range is now truly a range with a starting point and with an endpoint. Microsoft customers who deploy servers that are running Windows Server 2008 or 2012 may have problems with RPC communication between servers if firewalls are used on the internal network. In these cases, we recommend that you reconfigure the firewalls to allow for traffic between servers in the dynamic port range of 49152 through 65535. This range is in addition to well-known ports that are used by services and by applications. Or, the port range that is used by the servers can be modified on each server. You adjust this range by using the netsh command, as follows: netsh int set dynamic start=number num=range This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. The following are sample commands: netsh int ipv4 set dynamicport tcp start=10000 num=1000 netsh int ipv4 set dynamicport udp start=10000 num=1000 netsh int ipv6 set dynamicport tcp start=10000 num=1000 netsh int ipv6 set dynamicport udp start=10000 num=1000 These sample commands set the dynamic port range to start at port 10000 and to end at port 10999 (1000 ports). The minimum range of ports that can be set is 255. The minimum starting port that can be set is 1025. The maximum end port (based on the range being configured) cannot exceed 65535. To duplicate the default behavior of Windows Server 2003, use 1025 as the start port, and then use 3976 as the range for both TCP and UDP. This results in a start port of 1025 and an end port of 5000. Note When you install Microsoft Exchange Server 2007 on a Windows Server 2008-based computer, the default port range is 1025 through 60000. Click here to be linked to the Microsoft Knowledge Base Article Number 929851.

Issue Temperature Sensor Location Valve Location Actuator Location Product Line Field Devices Environment Actuator Sensor Valve Cause Where to fit and locate field devices. Resolution Valves: If the valve is lift and lay type and the application is diverting, then the valve must be fitted in the return. If the valve is lift and lay type and the application is mixing, then the valve must be fitted in the flow. The rule of thumb for lift and lay valves is "2 ins and 1 out" Rotary (shoe) valves can be fitted in either the flow or return for either mixing or diverting applications. Use pipe unions, so that the valve can easily be removed. Actuators on Valves: If the heating medium is steam then the actuator/valve arrangement is not fitted vertically, tilt the valve/actuator to an angle so that heat can convect away vertically and the actuator is not subjected to as much heat. In all cases, do not fit the actuator/valve arrangement so that the actuator is vertically under the valve. If the valve leaks, it will damage the actuator. Temperature Sensor location, in both wet and air applications the sensor need to sense correctly the medium it is in. Where possible install in a location for easier maintenance e.g. at a height reachable from a fixed floor level. Pipe Temperature Sensors: The tip of the sensor needs to be in the core of the medium i.e. the centre. The sensor needs to be fitted where stratification does not take place or is reduced. This can be achieved by fitting after a pump or after a bend where turbulence provides a good mix. If the sensor is fitted on a bend, then the probe faces the flow of/oncoming water. In CHW applications, fit the pocket just off horizontal, so that any condensation forming in the pocket can drain away. Adequate insulation will prevent condensation forming in the pocket. If fitting vertically in the top of the pipe is unavoidable see Oil for the DWT0001 (or STP660) pocket sensor to prevent problems with condensation. Duct Temperature Sensor: Supply Air - If a probe type sensor is fitted, it needs to be ideally 3 meters downstream and in the centre of the duct from the supply fan and preferably after a bend fitted with turning vanes. Return Air - The temperature sensor needs to be fitted before/upstream of the extract fan. Frost Coils - Temperature sensor, due to the short distance available, probe sensors are difficult to locate, but try to be as far away from the coil e.g. on the other side of the pre-filter bank and in the centre of the duct/AHU. Even better is to use an averaging type temperature sensor. Frost Coils - Fan Hold Off thermostat. Allow sufficient capillary to cover the battery surface. Lace the capillary across the frost battery on the downstream side using the correct clips. If the thermostat body needs to be fitted on the external side of the AHU, then fit with the minimum of capillary on the external of the AHU. Use a grommet or stuffing gland to protect the capillary as it goes through the AHU skin. If the AHU is fitted outside or is in an unheated space then the thermostat needs to fitted internal to the AHU. Do not cut the capillary if it is too long. Tidy capillary ends so they do not flap in the airstream. Outside Temperature Sensor: Outside temperature sensors should be located correctly to the local region you are in and the application they are serving i.e. compensated outside sensor in the UK are fitted on a wall facing north. The sensor should not be fitted on flues, chimneys, near opening windows. They should not be fitted near to compounds containing plant expelling heat e.g. chiller compounds. The sensor should be fitted at a height that does not require the use of steps or ladders for maintenance. Room Temperature Sensor: Sensors should be fitted at an agreed height and not fitted on external walls, near opening windows and doors or above radiators. They need to be exposed to the area they are controlling and not be directly influenced by heat sources e.g. computers. Sensors with exposed setpoint adjust or controls need to be fitted at a lower height so that people with disabilities can adjust them. Sensors that are fitted onto partitioned walls or have a conduit need the hole plugging so that there are no draughts. Sensors that are fitted directly to concrete or steel beams should be packed out with a thermal insulating material. Valves and Sensor Wiring: Allow sufficient cable to allow removal of actuator or sensor without having to disconnect the device. See the full Building Controls Group - Control Sensor Installation guide.

Issue Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue What is the unit load of a TC300 thermostat and what are the bias and termination requirements when used with a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment TC303-3A2LM TC303-3A4LM TC303-3A2DLMS TC303-3A4DLMS SmartX Server Cause Documentation does not state the RS-485 transceiver type for the TC300 range, making it unclear how many devices can exist under a SmartX servers RS-485 serial port ComA or ComB. Resolution The answers to the transceiver interface attributes below can be applied with to the Worksheet for Configuration of RS-485 Bus with generic RS-485 devices on Webhelp Q1 Failsafe Receiver The TC300 does not use an RS-485 transceiver with an integrated idle-state failsafe receiver. Q2 Data Transmission Speed TC300 thermostats manufactured from November 2018 onward can be configured to communicate at 9600 or 4800 bps. TC-300 thermostats manufactured before this date can only communicate at 4800 bps. Q4 Isolated Interface The TC300 does not provide an isolated RS-485 interface. Q6a Measured Resistance With no electrical connections to the TC300, the measured resistance between the RS-485 low-side (-) signal and the communications common is 10K ohms. Based on this the unit load of the TC300 is 1.2 (12.000/10,000) Bias requirements and number of devices If the length of the RS-485 bus is less than 150M (500ft) then Generic RS-485 Device Configuration 3 from Webhelp can be applied. Using this configuration the recommended 3300 bias resistors present a unit load of 3.6 (12,000 / 3,300). The SmartX server adds 0.5UL. The remaining node budget is calculated as: 32 - 3.6 - 0.5 = 27.9UL. Since the TC300 has a unit load of 1.2 the maximum number of devices that can be placed under each comm port using this configuration is 27.9 / 1.2 = 23.25 If the length of the RS-485 bus is greater than 150M (500ft) then Generic RS-485 Device Configuration 7 from Webhelp can be applied. Using this configuration the dual end-point bias configuration presents a unit load of 24UL (12,000 / (1,000 / 2) = 24). The SmartX server adds 0.5UL. The remaining node budget is calculated as: 32 - 24 - 0.5 = 7.5UL. Since the TC300 has a unit load of 1.2 the maximum number of devices that can be placed under each comm port using this configuration is 7.5 / 1.2 = 6.25 Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.  h

Issue Thread size/standard. Product Line Field Devices Environment Pocket Well Pocket STP 50mm Brass  9121040000    Pocket STP 100mm Brass  9121041000    Pocket STP 150mm Brass  9121042000    Pocket STP 200mm Brass  9121043000    Pocket STP 250mm Brass  9121044000    Pocket STP 300mm Brass  9121045000    Pocket STP 400mm Brass  9121046000   Pocket STP 50mm Stainl.steel 9121050000    Pocket STP 100mm Stainl.steel 9121051000 Pocket STP 150mm Stainl.steel 9121052000    Pocket STP 200mm Stainl.steel 9121053000    Pocket STP 250mm Stainl.steel 9121054000    Pocket STP 300mm Stainl.steel 9121055000    Pocket STP 400mm Stainl.steel 9121056000 Cause This information is necessary if an adaptor or similar is required for installation. Resolution The thread is of cylindrical type, and follows DIN 228 and BSP (British Standard Pipe) which both are identical. Size of thread is G1/2. For additional information on Pocket materials, please see Sensor pockets material specification Stainless steel and Sensor pockets material specification nickel plated brass.

Issue What is the unit load (UL) of the SpaceLogic SP90 PIBCV Actuators that will help me to calculate how many SP90 PIBCV Actuators can be added on ComA and ComB of a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic SP90 PIBCV Actuator SmartX Server Cause Require the Unit Load (UL) of the SpaceLogic SP90 PIBCV Actuator to calculate the number of actuators allowed on the RS-485 network.  Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SpaceLogic SP90 PIBCV Actuator range uses the SN65HVD1780DR transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/10 UL. In addition, there are no local bias resistors and therefore the 1/10 UL of the transceiver would be the total UL presented to the bus by the SpaceLogic SLP Room Unit. Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus SN65HVD1780DR 0.1 Yes None None 0.1 No Based on the above the total number of devices can be calculated as 32/0.1 = 320. The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore a SmartX Server is limited to 127 devices per com port (254 total per Server) so this should effectively be the limiting factor. However, the documentation recommends using only up to 64 devices with the same RS-485 transceiver, or 32 devices with different RS-485 transceivers.   Since the SpaceLogic SP90 PIBCV Actuator does not have an isolated RS-485 interface it conforms to Generic RS-485 Network Device Configuration 1 in EBO Webhelp.  A network consisting of only SpaceLogic SP90 PIBCV Actuators should only require a 120-ohm termination resistor at each end of the bus and not require any bias resistors. Also, check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue Step by step instructions to configure the Lonworks Network Interfaces application to communicate over IP-852 to a Loytec L-IP router using the Echelon driver Product Line Field Devices, Other, TAC Vista Environment LNS Turbo Lonmaker turbo Lonworks Network Interfaces Loytec L-IP  Cause Instructional how to document steps through the necessary set-up to get a Loytec L-IP to communicate in a Vista system using the Echelon driver Resolution It is preferred to use Loytec's own driver rather than Echelon's driver, and also the Loytec driver is the only one supported in SmartStruxure, how ever it is possible to use Echelon's driver following the guide below. To learn more about the L-IP and understand the difference between two drivers, check this video: https://www.youtube.com/watch?v=cLNBv6tEDXg or Loytec L-IP 101 Note 1: The first steps would be to verify the IP addresses needed for both the computer and the Loytec L-IP router. In this example, we will be using 10.159.5.39 for the L-IP and 10.159.3.26 for the computer running LNS. The default IP address of the Loytec L-IP router is 192.168.1.254. In most cases the default IP needs to be changed to match the system network. Please reference the L-IP Users Manual page 20 for instructions on how to change the IP address of the device. Note 2: In our example there is only one L-IP, so it is configured as the configuration server. Remember: One L-IP within any Vista Server system has to be configured as the configuration server. Please reference page 52 of the L-IP users manual for instructions on how to set a L-IP as a configuration server. This document has the web instructions in step 12. Navigate to the windows control panel and open the Lonworks Interfaces application. In lonmaker 3.1 with LNS 3.1 the program will be lonworks IP channels: Within the Lonworks Interfaces application choose the IP-852 tab: Under network interface click the Add button: In the Network Interface Add window you will need to name your connection. In this example it is just simply named IP for the IP channel within LNS. The IP Address should be set to the local IP of the computer. The IP Port should be left at the default 1628 and Channel Timing should be LAN. Click OK: Back within the LonWorks Interfaces application you should now see the named IP network, the IP address, and the IP port number: Next, Click the Test button to test the communications from LonWorks Interfaces to the L-IP configuration server: Check the box to Set the Configuration Server Address and type in the IP address of you configurations server L-IP router. The default IP port used in network interfaces is 1628 so requesting a communication test from the L-IP requires the configuration server return port to be set to 1629. Then click the Start Test button: After clicking Start Test you will see a message verifying the test has started. If your test is successful you will see the following message: Your Lonworks Network Interfaces is now configured for a TCPIP connection and properly setup to communicate to a Loytec L-IP router configured as a configuration server. If you never receive a message showing a successful test, please proceed to step 9. Login to the L-IP web interface by opening a web browser and typing the IP address of the device. In our example it is http://10.159.5.39. This is the default web page within the L-IP web interface: Click the Config button: You will now be prompted to login to the controller. The default username is Administrator and the default password is admin Note: for new version of L-IP, its username is admin and password is loytec4u. Click on EIA-852 Server and make sure the Config server status is enabled and the Config server port is 1629. If any changes are necessary, a message will appear at the bottom of the web page to reboot the device for the changes to take effect. And if there are more than one LIP in this network, all the other LIPs apart from the first one need to choose disabled option for the Config server status. Click on EIA-852 Ch. List. In the channel list you should see your local L-IP device and IP address. The next step is to add the IP address of the HOST PC running the Lonworks Network Interfaces application. Click the Add Device button. Name your device. In this example it is named PC. Then type in the IP address and the port number of the HOST PC and click save. Click in the Recontact button and go back and repeat step 7. You should now see a successful test from your configuration server. If there are more than one LIP in the network, add all the other LIPs in this list. Now your Loytec L-IP router is communicating to the Lonworks Network Interfaces program. This will allow your LNS server to communicate on the IP channel connection within Lonmaker or NL220 and use this Loytec L-IP as its connection to the Lonworks network. Additional setup information is available here in the L-IP Users Manual.

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue Some Windows OS do not come with Hyperterminal installed. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Cause Hyperterminal was not included in the Operating System software package. Resolution Installing Original XP HyperTerminal Download this .zip file which contains the necessary executable and dynamic link library for running hyperterminal Unzip to local hard drive. Double click the hypertrm.exe to launch hyperterminal See Connecting a serial cable to a Xenta 5/7/9xx controller for proper cable connection and hyperterminal settings if needed. Alternatively, extract the two files from any XP installation and copy them to the new Windows OS. hypertrm.exe default installation is in C:\Program Files\Windows NT hypertrm.dll default installation is in C:\Windows\System32. Alternatively, from a Windows XP CD, both files reside in the i386 directory.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. In cases where multiple BACnet networks containing SE7000 BACnet room controllers are connected to the same BACnet internetwork there could be duplicate ID's when using this schema. In these instances a T7600 Device Configurator Tool can be used to change these fields. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. For example when a VT7200F5000B room controller with a MAC address of 41 is connected to a network, its default Device Name will be VT7200F5x00B-41 and its default Device ID will be 72041. The device ID and name will change as soon as the MAC address is changed at the controller. The MAC address is set in the Installer configuration parameter menu using the Com Addr parameter. These fields can also be set by any BACnet management tool that can access these properties. Resolution The goal of this document is to give simple instructions on how to change the Device Instance of the VT7000 series thermostats using the T7600 Device Configurator tool and the recommended connections and wiring. 1. Converter (can be other models): Model 485OT9Lor USOTL4 from B&B Electronics. A USB-to-RS485 converter, like one used for MSTP captures, will work as well.  2. Recommended wiring for the configuration of Device Instances: The SE7000 room controllers have to be connected only to the converter (which has to be powered up) and disconnected from the network controller. The EOL resistors should remain at both ends of the trunk. 3. Setting up the software The software is supplied as a simple installer file download the software from here and run the installer. Prior to running the program for the first time setup steps 4 and 5 must to be accomplished. 4. Setting Windows Compatibility mode The T7600 Device Configurator Tool is legacy tool and therefore is only supported in a Windows 9X operating system, It has been tested and found to work in later versions of Windows by setting the compatibility mode to Windows 95 Locate the executable file T7600_MSTP_Config.exe in the C:\Program Files\Fastek\T7600 Config\ folder. Right click the file and select properties Go to the compatibility tab and change select Run this program in compatibility mode for: "Windows 95" from the drop down menu then click OK 5. Set the PC communications port Open the BACDOCM.ini located in the C:\Windows folder and enter communications port number in the line highlighted below and save the file. If a valid com port is not entered here the program will generate errors when launched and will not operate. Instructions on how to use the converter (file T7x00 MSTP Config.exe): 1. Open the configuration Tool 2. Double click on the BACDOOR icon in the icon tray on the bottom right of the PC. 3. On the window BACDOOR OEM MSTP Client status, click configure and in the configuration window set the Device instance to any number that does not conflict with any other device instance on the network.: 4. Close the BACDOOR configuration window and in the T7000 Device Configurator, click refresh device list. 6. All the devices on the trunk should appear and you can start changing the device instances one after the other. To do that: a. A- Select the first device.     B- Click Connect to device. The connection process can be long, wait for all the objects to be discovered.     C- change the instance ID using the keyboard.     D- click Apply changes. b. Select the next device and do the same. c. Repeat this action for all the discovered devices. 7. After making all the recommended changes, remove the RS-485 to 232 converter and reconnect the network.

Issue Room controller shows up in the Discovery (Bind) window but will not go online after clicking on “Bind device”. Status in the ZVC object shows “offline (-2)” error. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 SSL SE7000 Cause An invalid value is being overwritten continuously to a local point (to the Room Controller) by a dashboard widget or a third-party device(e.g. via Bacnet). Resolution The invalid value must be corrected before proceeding with the binding process. Example: A value of 0 is being written to the Occupancy command point which only take values of ([1 = Local Occupancy], [2 = Occupied] or [3 = Unoccupied]). The write and read traffic generated prevents other room controllers from joining the network.

Issue Product specifications and application details for the SE 7000 or SE 8000 range of room controllers are required. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE8000 • SSL SE7000 Cause Full details of the products are required. Resolution The best source of information is in the online Product Selection: Room Controller Selector Tool This tool will allow you to select the correct unit for your application, then from the different tabs you will be able to see: Product Overview, Spec's, Dimensions, related accessories and to download the required documentation from the Links tab. Note: The installation guide can be downloaded from the Links tab and contains detailed application setup, product specification and dimensions. For BACnet versions of the controllers the PIC's statements can currently be downloaded from the Viconics section of the BTL official site using the corresponding VT7xxx part number, see link: BTL Listings for Room controllers Note: The SE8000 and SE8300 Series BTL Certification Listing is anticipated for late 2015.

Issue The client is inquiring if SE7000 series controllers with LonWorks communications are compatible with TP/FT -10 channels Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause The datasheet indicate network compatibility with Echelon LonTalk but there is no mention of the compatibility with TP/FT-10 channels / networks. This may be unclear to some.  Resolution The SE7000 series is compatible with LonWorks TP/FT-10 channels. Refer to the datasheet for 14240R which is the free topology transceiver used in the SE7000.  capacitors, LPT-10 Link Power Transceivers Free Topology Transceivers, and, with suitable DC blocking capacitors, LPT-10 Link Power Transceivers FT 3120 / 3150 s mart Transceivers, FTT-10 and/or FTT-10A Free Topology Transceivers, and, with suitable DC blocking capacitors, LPT-10 Link Power Transceivers

Issue Sometimes, switching 230V with the SE7000 controller is requested and/or necessary, but no such product is listed in the current portfolio. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause No product that matches the requests are currently listed in the portfolio Resolution Two relay boards for fan coil units will be released late 2012.  These will allow the SE7000 devices to be used with 230V systems.

Issue Some controllers in the SE7000 range and all of the current SE8000 range cannot be supplied with a LON interface. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause Some controllers in the SE7000 range (e.g SE7600E) are not shown with a part number for a factory-fitted LON interface in the Schneider Electric documentation.  Although they can be supplied in a 'network ready' version and there is a part number for a separate LON interface listed, the two are not compatible.  There is no LON network interface for the SE8000 range. Resolution Only the controllers currently available with a LON interface as per the Schneider Electric documentation are available to communicate with a LON system. There are no plans to add a LON card option to the other SE7000 series controllers or any of the SE8000 range and they cannot be fitted separately.   The only communication options for these controllers is BACnet or Zigbee.

Issue The client is inquiring about the availability of  I/A Series R2 and G3 objects for interface with the SE7000 Series Room Controllers Product Line TAC IA Series, EcoStruxure Building Expert Environment I/A Series R2 UNC I/A Series G3 ENC SSL SE7000 Cause Not able to locate shadow objects with matching LonWorks program IDs within the existing I/A Series R2 and G3 modules. Resolution A set of new modules have been generated for use with the new SE7000 Series Room Controllers.  The new objects interface with the following program IDs. R2 objects: Se7273         (80:00:10:55:00:04:04:20) Se76Pir         (80:00:10:55:00:04:04:21) Se76RhPir    (80:00:10:55:00:04:04:22) Click to download ... lonSchneider-2.301.330.zip Click to download ... lonSchneider-2.301.431.zip Click to download ... lonSchneider-2.301.534.zip G3 objects: Se72_73.lnml (80:00:10:55:00:04:04:20) Se76Pir.lnml (80:00:10:55:00:04:04:21) Se76RhPir.lnml (80:00:10:55:00:04:04:22) Click to download ... lonSchneider-3.5.39.1.zip Click to download ... lonSchneider-3.7.17.zip The 3.5.39.1 module should be used with G3 versions 3.5 and lower. The 3.7.17 module should be used with G3 versions 3.6 and higher.

Issue The SE8000 documentation states that the power supply voltage is 7 Volts DC but the circuit board sticker says 7 VDC/24 VAC. Can the controller be powered from 24 VAC? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause An incompatible relay pack might have been used. Resolution Typically the SER8300 range are intended to have power supplied by the SC3000 relay pack which supplies the 7VDC. If an SC3000 relay pack is not used, for example, if the SER8300 is just being used as a wireless device then it is acceptable to power it from 24VAC.

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below: