Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE StruxureWare Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Checking if a port is open Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution It is possible to check if a port is open in a network by issuing the Telnet command. Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet. If a port is open, a blank screen will be seen after issuing the command: telnet [domainname or ip] [port] where [domainname or ip] is the domain name or IP address of the server being checked [port] is the port number the server application is listening on For example: telnet 192.168.0.20 9001 (to a closed port would display a connect failed message)   telnet 192.168.0.20 9003 (to an open port would display a blank screen)   To exit the Telnet session, type Ctrl + ] and then type "quit".   For how to enable Telnet in Windows 7 please see Enable Telnet Client on a Windows 7 PC

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

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

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue ISO 9001 certificate for Schneider Electric Buildings Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices,Other, TAC INET, TAC Vista Environment Management Certification Certificate for the Design and Manufacture of Building Management System Controllers, Devices and Electronic Systems Cause ISO9001 certificates are sometimes requested for different projects. Resolution Download the ISO 9001:2015 certificate here.

Issue Microsoft Visual Studio causes Just-In-Time Debugging Environment Windows Operating System Cause Visual Studio is installed on the PC and when attempting to perform a task, an error appears claiming Just-In-Time Debugging.  Resolution To disable Just-In-Time debugging: On the Tools menu, click Options. In the Options dialog box, select the Debugging folder. In the Debugging folder, select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key. Click OK.

Issue What does that controller/device look like Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Site with TAC or Schneider Electric Controller(s) Cause Questions concerning what a controller looks like, or if there are no labels on the controller which help identify. Are photographs or drawings available? (This is an article in progress. Have one that is not listed? Please help by taking a good picture(s) and including or send to Product Support) Resolution I/NET: 7728 7728 Left side 7728 Right side  7790 7790 side 7790 older model  7790 older model side  7798C Top 7716 7920 7920 side  MR-AHU MR-AHU left side MR-AHU right side P8UI8DO Expansion board  SCU1284 SCU1284 side Continuum: ACX5720 ACX5720 Open CX9702  b4920 b4920 Open BCX1 BCX1 open i2-600 Series i2.600 Series Open  i2_850 i2_850_Open i2_887_L_115  i2_920 i2_920_open CX9400 with three 32s and two 16s in 8 card rack CX9400 CPU front CAD Drawings for the Continuum controllers are also available on The Exchange Download Center: Link Here.

Issue Unable to determine whether the Enocean device in hand is compatible with MPM controllers Unable to add more devices to a MPM controller Product Line EcoStruxure Building Expert Environment Multi-Purpose Manager Cause Some pre-configured icons in the "Add Devices" list have a name but do not have a specified Enocean profile or vice versa. Resolution The Following devices are embedded in the MPM firmware and require no scripts to integrate with an MPM. All Devices in the below list (except for Enocean relay) are outbound devices (i.e. devices that are only able to send telegrams to other devices) MPM Sub-device list Description Compatible Schneider-Electric Products CO2 Sensor A5-09-04 CO2 Sensor SR04 CO2 (LSS442510) (868MHz) Door/Window Sensor D5-00-01 Single Input Contact SED-WDS-U-5045 (902MHz) 10020032 (LSS10020032) 10020042 (LSS10020042) 10020047 (LSS10020047) Double Rocker Switch F6-02-01 Light and Blind Control – Application Style 1 EDRPU-W-EO (902MHz) 10020048 (LSS10020048) (868MHz) Enocean Relay Inbound profile   Enocean Switch Light and Blind Control – Application Style 2 ESRPU-W-EO (902MHz) 10020049 (LSS10020049) (868MHz) Enocean Thermostat Obsolete   KeyCard Switch F6-04-01 Key Card Activated Switch SED-KCS-U-5045 (902MHz) Light Sensor A5-06-01 Light Sensor Range 300lx to 60.000lx 10020047 (LSS10020052) Light Sensor A5-06-02 Light Sensor Range 0lx to 1.020lx SED-LLS-U-5045 (902MHz) LSS10020053 (868MHz) Motion Sensor A5-07-01 Occupancy Sensor with Supply Voltage monitor SR-MDS Bat SED_CMS_U_5045 (902MHz) Thermostat A5-02-05 Temperature sensor Range 0°C to +40°C SED-T00-U-5045 (902MHz) 10020046 (LSS10020046) 10020033 (LSS10020033) Thermostat A5-04-01 Temperature & Humidity sensor Range 0°C to +40°C and 0% to 100% SED-TH0-U-5045 (902MHz) 10020041 (LSS10020041) SR04 rH Thermostat A5-08-01 Light, Temperature and Occupancy sensor Range 0lx to 510lx, 0°C to +51°C and Occupancy Button SR-MDS Thermostat A5-10-03 Room Operating Panel: Temperature Sensor and Set Point Control SR04 P (LSS226172) Thermostat A5-10-05 Room Operating Panel: Temperature Sensor, Set Point and Occupancy Control SED-TS0-U-5045 (902MHz) Thermostat A5-10-10 Room Operating Panel: Temperature and Humidity Sensor, Set Point and Occupancy Control SED-THS-U-5045 (902MHz) Thermostat A5-10-12 Room Operating Panel: Temperature and Humidity Sensor and Set Point SR04P rH(LSS252331) Thermostat A5-10-19 Room Operating Panel: Humidity, Temperature Set Point, Temperature Sensor, Fan Speed and Occupancy Control   -The maximum number of devices added to each MPM is 49 -The maximum number of EnOcean devices added to each MPM is 49 -The maximum number of EnOcean devices with the same EEP added to each MPM is 49 .This only applies to firmware 2.13.1 and later, the limit for previous firmwares is 20. An Exception is the following limits for devices/widgets per MPM 20 EnOcean Switches 20 EnOcean Relays 4 EnOcean Thermostats The Devices in the next table do not have a pre-configured icon in the devices list, however, scripts can be used instead and can be found below (Please read PDF first) Enocean Scanner Enocean device driver Valve driver Enocean profiles supported in script EnOcean Equipment Profile (EEP) Description Example of Compatible Devices (EEP A5-38-08) Central Command Gateway Plug-in 15 Amp 120V 902Mhz 5-Wire 6A Relay 24V 902Mhz 3-Wire 6A Relay 120/240/277V 902Mhz (EEP A5-11-01) Lighting Controller 15A-20A 120/277/347V 902Mhz (inbound profile: A5-11-01) 15A 120-277V 902Mhz (inbound profile: A5-11-01) (EEP A5-10-04) Temperature Sensor, Set Point and Fan Speed Control Thermokon SR04PS (EEP A5-02-14) Temperature Sensor Range -20°C to +60°C Thermokon SR65TF (EEP F6-03-01) 2 to 4 Rocker Switch (Light and Blind Control) Push-button, 2-gang (EEP A5-20-1) Battery Powered Actuator Thermokon SAB02/SAB05     Din Relay 1 channel (inbound profile: F6-02-02)     PWM 230V valve driver (inbound profile: A5-02-05) PWM 24V valve driver (inbound profile: A5-02-05)

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue Device ID / Device Instance of SE8000 series BACnet controllers Duplicate BACnet Network Address alarms How to have 254 SSL Room Controllers on an Automation Server (AS) as shown in the SBO Automation Server and SE7000 and SE8000 - Architectural Guidelines Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Room Controller BACnet Cause There can be confusion from the difference in naming between SmartStruxure Lite(SSL) Room Controller(RC), SmartStruxure Building Operation and even Niagara(JACE). Bacnet Instance number in SSL = Object ID in SmartStruxure Building Operation COM Address in SSL = MAC Address in SmartStruxure Building Operation Resolution On the AS, considered is the Object ID of the two Comm Ports (as with all object IDs) they need to be unique across the system. A common ID is 1001 for CommA and 1002 for CommB of the first AS, then on the second AS CommA 2001, CommB 2002 etc. The key thing with BACnet is that every object (point, device, program, port etc) must have a unique Object ID. The SE8000 uses the Com Address referred to as the BACnet MAC Address in the AS. This, as detailed in BACnet COM Address of Room Controller SE7000 and SE8000, is the address range on just that one MS/TP bus. 1 – 127 are valid addresses, the AS (or bus master) will be address 0. If a second AS is on the same system this could use 83001 – 83127 for CommA, 84001 – 84127 CommB etc. Also SE8000 uses the BACnet Instance number which is called the BACnet Object ID in the AS. (This is the ID which must be unique across the whole system) So if you have the 2 ports used on one AS all 254 devices must have unique ID’s. When changing the Comm address in the SSL SE8000 to any value between 1 and 127, the Instance number will change as well. For example Comm address 9 would result in an Instance number of 83009. These will cover 127 stats that will go on CommA, and result in Instance numbers between 83001 and 83127. Any value above 127 will keep the Instance number unchanged. For CommB however, a site would need to change the Instance number manually. For example the first RC connected to CommB would be the 128th and would default to address 83127. So it is required to manually change the Instance number to 1083001 (up to 1083127). This defines unique Comm Addresses for ComB on the remaining 127 RC. When using an Automation Server (AS) you can find the Object ID and MAC address for devices on MSTP by using WorkStation and going to AS > System > Hardware > BACnet devices > Network_xxxx. A screen shot is below with the added columns Status, System Status, Object ID, and MAC address. In this first example, b3 controllers use the Object ID or Device ID of their serial numbers so each b3 is unique across the network. B3 controllers with serial numbers greater than 4194302 (the maximum allowed Object ID in BACnet) will be assigned a Device Object ID using a hashing algorithm to ensure it is unique. From an SE8000 series RC, BACnet network set-up screen shows when BACnet is detected in models. Select desired parameter and use up or down arrow to set parameter to desired value. The default BACnet instance number is generated by the model number and COM address of the controller. For example, The instance number of a SE8300A5B00 with a COM address of 57 is generated as "83057." The default instance number appears first. To change the instance number, use number pad and press Accept and Save. Below is a screenshot of the WorkStation logged into an AS, with the BACnet Interface and the MSTP network. The added columns show the Object ID and MAC address. Below is a screen shot of the WorkStation logged into the AS, with the System > Hardware Devices > Network_xxxx. The added columns show the Object ID and MAC address.  The screen shot below is the AS > BACnet Interface > MSTP Network > Configuration Settings.

Issue Controllers may leave their network and join another if a nearby network has an identical "Extended network ID", "Channel" or "PAN ID" Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause Conflict in zigbee networks (Same "Channel", same "PAN ID" or Same "Extended Network ID") Resolution Before deployment, and in order to ensure having a reliable ZigBee network, one has to be aware of the best practices and the limitations of RF signals. Here are some key points to be considered Network Conflicts: Always change your Extended Network ID from the factory default. The best thing is to use a naming convention that makes sense. One suggestion would be to use "SSLLITxx," where "xx" is replaced by the floor the network is on. For example, floor 5 would be "SSLLIT05." If you have multiple networks on the same floor, adding a letter code helps denote them. For example, if there were 2 networks on floor 5, "SSLLI05A" and "SSLLI05B" can be used. Note: In Firmware 2.20.1, the ZigBee Extended Network ID parameter is set by default to a unique string based on the serial number of the MPM. This will eliminate the possibility of having duplicate Extended ID's in a new deployment. For existing installations, the Extended Network ID will remain unchanged if upgrading from a previous version.   Alternating Channels: Alternating channels between network will minimize interference ensure stability. For example, for a 5-story building, alternate between channels 20, 25, 20, 25, 20. Tx Power Upgrade: The default value for "Tx Power" is 5dBm which was designed in order to meet various regulations in certain countries (Europe). However, the "Tx Power" can be increased to 18dBm in other regions of the world (North America) to boost the transmission power of the MPM.   Interference: There are different types of interference when a wireless signal travels through a given space: Physical objects: The number of walls the wireless signal can pass through is determined by the density of the materials used in a building's construction. Concrete and steel walls are difficult for a signal to pass through. These structures will weaken or at times completely prevent wireless signals. Also, the presence of individuals or water will diminish the signal due to the water's ability to absorb the signal. 2.4Ghz Frequency Interference: Cordless Phone - operates on the same frequency as the ZigBee and can cause a significant decrease in performance. Microwave Oven - operates by emitting a very high power signal in the 2.4GHz band. Often emits a very "dirty" signal across the entire 2.4GHz band. Wireless Routers - Wireless Wi-Fi Networks that share the same channel will have a negative effect on ZigBee network performance. Distance: To ensure reliable communications, a suitable distance between two devices has to be calculated before installation. The distance depends on three factors; transmitter power, sensitivity of the receiver and the propagation path loss. The latter is dependent on the number of walls/physical objects obstructing the signal. Locations: The physical location where a router or coordinator is placed also has an impact on the signal. Place the devices in higher ground to reduce the impact of physical objects. Route Redundancy: It is critical that the signal has multiple routes to hop from one device to the other, from one edge of the network to the opposite edge. (See example in images below)

Issue How can objects of a SmartStruxure™ Lite network be made available as BACnet points to third party BACnet building management system (BMS)? Product Line EcoStruxure Building Operation Environment SmartStruxure Lite BACnet Cause The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet and this will need to be changed if BACnet over IP is required. Resolution The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet. To verify or to change which BACnet protocol is currently in use, select the SmartStruxure Lite Manager that you want to configure from the left-side Network panel. Then choose the BACnet configuration list item. Define the Network Number (if the protocol selected is BACnet IP). Note: The Network number must be defined only on the monitor Manager. It shall be different then the Parent Network where the monitor is connected. A BACnet Device is uniquely located by a network number and a MAC address. Creating two or more B/IP networks, each with a unique network number, can be useful for limiting the propagation of local broadcast messages and for providing security by confining traffic to a particular geographic or logical area. Select the desired protocol type from the drop-down list between BACnet IP and BACnet Ethernet. Then choose an optional port number (if the protocol selected is BACnet IP). Default is 47808. Select the BACnet Priority of the BACnet write action of the SmartStruxure™ Lite's network monitor. Default is 10. Note: SmartStruxure™ Lite does not support BACnet Write Priority, per se. However, in Firmware version 2.4.x and newer, it is possible to assign the write priority for all SmartStruxure™ Lite BACnet points. Default value is 10, except if you upgrade a Manager using a version 2.3.x or older, BACnet priority will be 8, but can be changed. Click the Save button to apply the configuration changes. Click hit the Save All button to make the modifications permanent and reboot the Manager for the new options to enter into effect. Change the BACnet instance number of the Manager if required. IMPORTANT Each Manager must have a unique BACnet device instance number. A Manager device instance number can be changed by selecting the top-left icon inside the left-side Network panel.

Issue Using BACnet IP to add a SmartStruxure Lite MPM to a StruxureWare Building Operation Enterprise Server or Automation Server Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Workstation Cause SmartStruxure Lite systems may desire an Enterprise Level Solution to bring multiple sites into one system. Resolution Configure the SmartStruxure Lite MPM for BACnet IP as shown in MPM BACnet Integration. Ensure that the BACnet Network ID is Unique to the system and does not match the Network ID in use by the Enterprise Server Save the BACnet Configuration Be sure to Right Click on the Root Object of the MPM and save the database. Open StruxureWare for Building Operation Workstation Right Click on the Server Object and add a BACnet Interface Ensure that the BACnet interface has a unique BACnet Network ID which does not match the Network ID used by the MPM Expand the BACnet Interface Click on the Server Object and select the Device Discovery Tab Select BACnet Devices NOTE: There have been instances of Skype causing interference with this process. Please completely close Skype if you are using it and unable to discover any devices. ALSO NOTE: There may be 2 instances of the MPM shown. If so, use the MPM that is part of the Enterprise Server BACnet Network Drag the MPM to the BACnet Interface/IP Network object in the Enterprise Server System Tree Right Click on the Device and Upload it If any devices are connected to the MPM such as a Zigbee Wireless State or Enocean switch, these will be discovered in the BACnet Network configured in the MPM Add these devices to the Enterprise Server by dragging and dropping them to the BACnet Interface/IP Network object Right Click and upload all devices.

Issue Once the occupied cooling and heating setpoints are written from a BMS, the user is not able to change the setpoint from the room controller Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Series Room controller Viconics branding VT8000 Series Multi Purpose Manager (MPM) BACnet Cause By default, the occupied setpoint value is written to Room Controller with priority level 16 by the BACnet front end. Attempting to change the setpoint locally using the up and down arrows on the SE8000 Room controller will not be allowed since the Room controller uses the relinquish value internally (priority 17) which will be automatically overwritten by the BACnet front-end. Resolution The work around is to release the BACnet front-end control over the BACnet object using a LUA4RC script. The script can be uploaded using one of the following two methods: 1 - Uploader Tool A USB cable is required to upload the script. The uploader tool can be downloaded from the Exchange Download Script Download Uploader Tool   2 - BACnet The script can also be directly uploaded via BACnet using the "Description" field as shown in the image below if (ME.AV92 == 6 or ME.AV92 == 7) then ME.AV39_PV[16] =nil ME.AV39_PV[10] =nil ME.AV40_PV[16] =nil ME.AV40_PV[10] = nil ME.AV92_PV[17] =0 end Where, ME.AV92 is the Keyboard value ME.AV39 is the Occupied Heating Setpoint ME.AV40 is the Occupied Cooling Setpoint Using this method, the script can be uploaded to multiple SE8000 Room Controllers by following the steps in Bulk Lua4RC upload via BACnet (Mass upload) For more information about Lua4RC, refer to the Lua4RC Programming Guide

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 Need a description of Zigbee error codes Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause No list of error codes available Resolution Here is a list of all possible error codes Error Code (HEX) Error Code (Decimal) Error Description   -2 Device offline (communication initialization after changing Ext. Network ID in ZVC)   -1 Device not bound 0x00 0 Success. Operation was successful. 0x01 1 Failure. Operation was not successful. 0x02 - 0x7d 2 - 125 Reserved by Ember 0x7e 126 Not authorized. The sender of the command does not have authorization to carry out this command. 0x7f 127 A reserved field/subfield/bit contains a nonzero value. 0x80 128 Malformed command. The command appears to contain the wrong fields or invalid field. 0x81 129 Unsupported cluster command. The specified cluster command is not supported on the device. Command not carried out. 0x82 130 Unsupported general command. The specified general command is not supported on the device. 0x83 131 Unsupported manufacturer cluster command. A manufacturer specific unicast, cluster specific command was received with an unknown manufacturer code, or manufacturer code was recognized but command is not supported. 0x84 132 Unsupported manufacturer general command. A manufacturer specific unicast, ZCL command was received with an unknown manufacturer code, or the manufacturer code was recognized but the command is not supported. 0x85 133 Invalid field. At least one field of the command contains an incorrect value, according to the specification. 0x86 134 Unsupported attribute. The specified attribute does not exist on the device. ( Zigbee Module not fully compatible with Room controller and FW of MPM) 0x87 135 Invalid value. Out of range error, or set to a reserved value. 0x88 136 Read only. Attempt to write a read only attribute. 0x89 137 Insufficient space. An operation failed due to an insufficient amount of free space available. 0x8a 138 Duplicate exists. An attempt to create an entry in a table failed due to a duplicate entry already being present in the table. 0x8b 139 Not found. The requested information could not be found. 0x8c 140 Unreportable attribute. Periodic reports cannot be issued for this attribute. 0x8d 141 Invalid data type. The data type given for an attribute is incorrect. Command not carried out. 0x8e 142 Invalid selector. The selector for an attribute is incorrect. 0x8f 143 Write only. A request has been made to read an attribute that the requester is not authorized to read. No action taken. 0x90 144 Inconsistent startup state. Setting the requested values would put the device in an inconsistent state on startup. No action taken. 0x91 145 Defined out of band. An attempt has been made to write an attribute that is present but is defined using an out-of-band method and not over the air. 0x92 - 0xbf 146 - 191 Reserved by Ember 0xc0 192 Hardware failure. An operation was unsuccessful due to a hardware failure. 0xc1 193 Software failure. An operation was unsuccessful due to a software failure. 0xc2 194 Calibration error. An error occurred during calibration. 0xc3 - 0xff 195 - 255 Reserved by Ember   256 Device offline   257 Device profile does not match selected device widget in Building Expert

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 Under rare circumstances, resetting your Manager to its factory defaults may be necessary.  For example, if you have forgotten your Manager's IP address, or if you are experiencing login problems.  Environment SmartStruxure Lite Web Browser SmartStruxure Lite MPM Cause All SmartStruxure Lite™ Managers are equipped with a bootloader, accessible via a special IP address that lets you access several Manager firmware functions, among them, a factory reset.  Resolution WARNING: Restoring your Manager to factory settings should only be performed as a last resort; doing so will erase all its objects and devices, requiring you to reconfigure your Manager from scratch. Accessing the Bootloader As its name suggests, you access the bootloader at boot time, i.e., when you power up your Manager. To perform a factory reset: 1. Disconnect electrical power from your Manager by unplugging its power connector or unplugging its power supply from the AC outlet. 2. Ensure that your computer's TCP/IP settings are on the same subnet as the bootloader IP address:10.50.80.X.     IMPORTANT: Upon restarting your Manager, you will have only a brief interval–approximately 5 seconds–during which you will be able to access the bootloader. As such, we recommend that you perform the following steps 3.  Open your browser and type the following IP address into the address bar, but do not click the browser's Go icon or press any  key on your keyboard: 10.50.80.2 4. Reconnect your Manager's electrical power. 5. Within approximately 5 seconds, click your browser's Go icon or press the key to navigate to the  bootloader's IP address.  The bootloader screen displays.    6. In the Restore factory defaults area, click Submit. The Manager begins restoring its settings to the factory defaults. When completed, a success message displays.  7. Restart your Manager by clicking the Submit button in the Restart system area. 8. You may now log in to the Manager using its restored IP address: 10.50.80.3. If you cannot connect successfully to the bootloader using the above steps, chances are you are not navigating to the bootloader's URL within the defined 5-second window.       As an aid, some users may find it useful to do the following:      Open a command window and type the following: ping 10.50.80.2     As soon as you see a ping reply, return to your browser window and press the key to navigate to the address previously entered into the address bar.   Restoring your Manager to Factory Settings download as PDF.

Issue Unable to upload the same Lua script to multiple Room Controllers at the same time Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Automation Server Premium SSL SE8000 (all) Cause The alternative method of uploading the script to each of the room controllers using a USB cable Resolution To upload a script to multiple Room Controllers, follow the below steps: (This procedure assumes the BACnet MSTP network is already setup) 1 - Log in to Building Operation Workstation 2 - Right-click on MSTP network and click "Search" 3 - Search for "Lua program 1" or any other Lua program object 4 - Highlight all the Room Controllers that the script will be transferred to then click on the "show/hide property grid" button. 5 - Expand the "Basic" tab and copy the Lua script in the "Description" field then click Save. 6 - The script will be uploaded to each of the Room Controllers one at a time and will be played automatically. Recommendations & Limitations: - Each Lua Program can take up to 460 bytes of text (per script). (Total of 10 Lua programs) - Script must be placed on a single line. Use semicolons ( ; ) as carriage return - Use multiple Lua programs if the 460 bytes limit is exceeded - Encapsulate logic inside the following if statement if the logic is intended to run once: if not init then    ---Script logic here    init = true end For general information about Lua programming for SE8000 Room Controllers, refer to the following guide: Custom Programming Guide for SE8000 Series Room Controllers - Application Guide

Issue Unable to gain access to Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager MPM-GW MPM-UN MPM-VA Cause The admin password has been changed and the user has lost the password Resolution For MPM with firmware 2.14 and earlier: Send the MPM 'default.db' file to Product Support.  From a web browser, you can save the default.db file to the local drive by typing the address http://[ip_address]/root/default.db (replace [ip_address] with the actual IP address of the MPM, or 10.50.80.2 if bootloader is used) For MPM with firmware 2.15 and later: Send the MPM Node ID or MAC Address to Product Support. Refer to the document StruxureWare Building Expert Password Recovery When Accessing MPM - Reference Guide for the procedure to obtain the MPM Node ID or MAC Address.