Building Automation Knowledge Base

Issue Using the OPT Block with a StruxureWare Time Schedule Object. Environment Function Block Editor Cause The Xenta Time Schedule which the OPT Block has the ability to send a positive or negative minutes till next change. The StruxureWare Time Schedule dose not include this item. This is the online help article that defines the parts of the OPT Block Resolution In the Function Block Editor, create 3 RI blocks. One will be bound to the Value attribute of the Analog Schedule One will be bound the ScheduleDefault attribute of the Analog Schedule One to the TimeToNextTransition attribute of the Analog Schedule Create an XPB block with the function "A!=B". Connect the Value RI to A and the ScheduleDefault RI to B. Label this XPB "Status". Create an XPI block with the function "a?B*-1:B". Connect the status XPB block to "a" and the TimeToNextTransition RI to B. This Block can be connected to the TmL input of the OPT block. This is an export of the demo application below which shows the bindings. (right click and choose Save link as...)

Issue The enhanced logging module in the 50 series does not continue logging once full if not configured to do so. Product Line Satchwell MicroNet Environment MicroNet VisiSat Logging Object Cascade Logs Cause The old logging object when the logs were full over wrote the oldest values automatically. The current 50 series logging object requires additional linked for the logging object to function the same way. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- The logging object has been enhanced. An example of the 100 series and IAC logging object is shown here. An example of the 50 series logging object is shown here. The original logging object defaulted to log and overwrite the older values and when configured looked like this. To achieve the same result with the 50 series type logging object, a couple of the logging object external nodes need configuring. and when configured looked like this. Further information regarding this object can be found in the VisiSat help file and engineering guide. VisiSat V1.2 Engineering Guide This document provides details for IAC 400, IAC 420, IAC 600 and IAC Touchscreen configuration. VisiSat V2.1 Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 Installation and User's Guide VisiSat V2.1 data sheet  See MicroNet 100 series controller MLi's and Data sheets See MicroNet 50 series controller MLi's and Data sheets See Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue Using Chrome and Webstation in EBO 2.0 for SmartX Advanced Displays generates an interface which is more open and less restrictive than the original Buildings Operation Technician's Tool it replaces. While this is a benefit, some users may require to have a 'Locked Down' interface Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display 2.0 and above Cause The Technician's Tool app on the SmartX Advanced Display was a separate purpose-built tool which was just designed for accessing SmartX Servers only, While Webstation, in this case is using Chrome has been recently updated for use on PCs Tablets and Smart Phones in general as well as the SmartX Displays.  It is therefore a much more open interface with the opportunity of accessing the EBO System Tree as well as other Chrome tabs for Google, news and weather etc. Resolution By default, Webstation 2.0 includes a System Tree for easier navigation and the latest version of SmartX Kiosk now includes a Chrome shortcut, designed to be used instead of the old Technician's Tool (which can now be uninstalled in EBO 2.0 installations).  The shortcut can open Webstation as one of multiple Chrome tabs as designed.  While the System Tree and extra tabs should be seen as helpful features, some users may still wish to simplify the SmartX display as much as possible, removing as many menus and tabs as possible to maximise screen size and continue the look of the older Technician's Tool.  To achieve this a couple of minor changes will need to be made. Firstly, the System Tree within Webstation can be hidden altogether, this will reduce system navigation but will also free up a portion of the screen. Secondly, creating a specific shortcut to Webstation 2.0, rather than using the standard Chrome shortcut removes the additional tabs. The new shortcut is added to the tablet's Home Screen but it also appears in Kiosk Mode. 1) Ensure the AD-Link is connected. 2) Open up the Chrome shortcut. 3) Connect to the pseudo IP address to connect via USB. 4) Log in using the same Username and Password as usual. 5) Select the Webstation menu icon. 6) De-select System Tree and then close via menu icon. This will then ensure the System Tree is no longer shown when logging into Webstation. 7) Access the Chrome Settings Menu 😎 Select the option to 'Add to Page to the Home Screen. This will then add a shortcut for Webstation to the tablet's Home Screen and will also appear in the SmartX Kiosk Home Screen. Using this shortcut instead of the standard Chrome shortcut will then open the Webstation in future without additional Chrome tabs or menu bars. Whenever you connect, menu pages and System Trees are now removed allowing the object selected to take up the maximum screen space.

Issue What does default.db contain? Which objects does config.db contain? Do i need to upload both files to the MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to download config.db from Building Expert; There are two files for the database Resolution When the database is saved using the "save database to flash" button, the MPM saves its data into two files; config.db and default.db 1 - Configuration Objects (config.db): The config.db file includes "system configuration objects" which show up in Building Expert when logging into a brand-new MPM. BAC1,C2G1, CFG1, EOC1, ETH1, MOD1, SNTP1 and ZBC1 Note: Depending on the model of the MPM, some objects in the above list may not be there. Note: CBC1 is part of default.db   2 - Control Objects (deafult.db): Objects that are manually added in Building Expert are part of the default.db database. Some examples are - Analog Values (AVs) - Binary Values (BVs) - Lua Programs (PGs) - etc...   The following items are also part of default.db: - Devices (ZigBee, EnOcean, Modbus etc...) - Dashboards - Permissions - Login Credentials (Username and password)   Backing up the database: The files can be downloaded by entering the following in the address bar of the browser: (assuming the IP address of the MPM is set to the default IP 10.50.80.3) 10.50.80.3/root/default.db 10.50.80.3/root/config.db   To upload the database to an MPM refer to Uploading Database files to an MPM (Cloning).

Issue The EWS interface in the SBO system tree shows as online but when browsing to the hardware folder all that shows up is the class folders, no objects are loaded.   When reviewing the settings in Security Expert EWS Manager.exe a prompt showing "Please set the password" is shown before loading the main configuration window.   You can then see that the Operator Password field is blank and that subsequent attempts to set this and save seem to work but when closing and re-opening the Configuration Manager that the password is not saved. Product Line EcoStruxure Building Operation, Security Expert Environment Security Expert Cause The current language for non-Unicode programs is set to a value other than English. In one specific case this was set to Chinese (Simplified,PRC). Resolution In the Region and Language settings for Windows go to the Administrative tab and select Change system locale... Set this to English, save and reboot the machine. The Operator Password should now be able to be set in the EWS Configuration Manager and EWS connection established.

Issue Unable to configure universal input from the thermostat Product Line EcoStruxure Building Expert Environment SE8000 Cause Universal inputs aren’t configurable at the thermostat Resolution There are two ways to configure inputs on SE8000; More often is via a BACnet front end and secondly is via a Lua script. The input shall be configured to Priority 3. SE8000 INPUTS: •       UI16 fixed as binary input •       UI17 fixed as binary input •       UI19 configurable as temperature sensor, binary input or 0 -10 VDC input •       UI20 configurable as temperature sensor •       UI22 configurable as temperature sensor •       UI23 configurable as temperature sensor •       UI24 configurable as temperature sensor, binary input or 0 -10 VDC input   For example UI19 configuration: UI19 LUA AnalogValue:202 ; this point is to write a Lua via Bacnet for UI19. LUA:  if not init then ME.MV6 = 2 -- set network units to imperial ME.MV145 = 2 -- room temp local ME.AV25_Desc = "UI19 TEMP" -- UI19 Present Value ME.AV26_Desc = "UI20 TEMP" -- UI20 Present Value ME.MV140 = 1 -- UI19 thermistor ME.MV141 = 1 -- UI20 thermistor init = true end ME.AV25 = ME.AV104 ME.AV26 = ME.AV105 ME.AV100_PV[16] = (ME.AV104 + ME.AV105) / 2 -- average UI20 remote sensor and UI19 remote sensor

Issue Where to go to download the Access Expert Device Administrator application. Product Line Access Expert Environment Server 2012 SQL 2012 and above Premise Install V2 Hosted V2 Applet V3 Cause There is no documentation on where to go to download the Device Administrator and how to program the SSC to communicate with the selected application. Resolution The following steps describe where to go and download the software and how to use it to program an SSC: Go to the EcoBuilding Exchange In the search field type Device Administrator Select the Access Expert Device Administrator and download to any location Browse to location and double click execute to run and install the program Accept Agreement and click next to continue installation Click Next to start installing the software Select the location where the file will be installed Successfully loaded software To complete installation, click on Finish Connect the device to a network switch that is open to the internet and launch the application by opening Access Expert device Administrator from the Schneider Electric group in All Programs Launch the application  Right click on the usb line or click on the green arrow to the top left to upgrade the software Once upgraded successfully, Right click again on the line and select properties then select the Ethernet 1 ConfigurationTab Select applicable choice whether it is DHCP or Static addressing being used and click on OK. Once the device comes back Online, select the DIP Switches Tab and check the box for Default User Using the IP address given from step number 13, open up IE and browse to that address Once opened, configure the SSC per Setting up an SSC (System Security Controller), EP1501 and EP1502 Mercury Controllers.

Issue Security Expert database size increasing rapidly and getting large. SecurityExpert Database size From the screen capture below, it can be seen that the Security Expert transaction log file SecurityExpert.ldf has increased to a large size. SecurityExpert database log file Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Recovery model of the Security Expert database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size.   New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution For Security Expert, it is recommended that the Recovery model be set to the default of SIMPLE.   You can reduce the size of the logs and also prevent them from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpert database from Full to Simple in SQL Server Management Studio. To do this, right click on the SecurityExpert database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery Model Simple Right click on the SecurityExpert database and select Tasks > Shrink > Files Shrink In the Shrink File - Security Expert window, change the File type to Log. Shrink File Type Log Click OK Repeat steps 2-5 for the SecurityExpertEvents database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue To assist locating data sheets if you do not have access to the Schneider Electric BBE and other company storage areas. Product Line Satchwell MicroNet 100 series Environment MicroNet 100 series Controllers, Touchscreens, LCD, Mi and Slink data sheets. Cause To assist customers that do not have access to our internet or partner websites Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN300 Controllers MLi and data sheets for Satchwell MicroNet MN440 Controllers MLi and data sheets for Satchwell MicroNet MN500 Controllers MLi and data sheets for Satchwell MicroNet MN620 Controllers Download all of the above (file size 10.50 MB) The data sheets for MicroNet 50 series controllers ETC. can be downloaded from MicroNet 50 series controller MLi's and Data sheets.

Issue Modbus device in hand does not have a pre-configured widget in the device list of Building Expert. A script is required to communicate with the device Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Any modbus device Cause Pre-configured widget not available in the device list of Building Expert Resolution The MPM can only be a Modbus Master; meaning it can request information from other slave modbus devices, or write to them. Terminals A and B on the MPM correspond to modbus terminals (Serial +) and (Serial -) respectively. When using a script to communicate with modbus devices, the "Enable" box in the ModBus configuration object (MOD1) must be disabled to allow the MPM to communicate with the devices using a script. The modbus port should then be closed (in case it was left open) and re-opened using the following functions ******************************************************** @@@ Lua.modbus.close       (Description and example here) ******************************************************** @@@ Lua.modbus.open        (Description and example here) ********************************************************     The following are the standard modbus functions and their corresponding Lua functions used in the MPM Modbus Function Code Lua Function in MPM Function Code 01 modbus.coil_read Function Code 02 modbus.di_read Function Code 03 modbus.hr_read (16-bit) Function Code 04 modbus.in_read Function Code 05 N/A Function Code 15 modbus.coil_write Function Code 06 modbus.hr_write   The following are the 8 different modbus functions that can be used to read/write to registers from/to modbus devices ******************************************************** @@@ Lua.modbus.coil_read     (Description and example here) This function is equivalent to : [Function Code 01 (01 HEX)] ******************************************************** @@@ Lua.modbus.coil_write    (Description and example here) This function is equivalent to : [Function Code 15 (0F HEX)] ******************************************************** @@@ Lua.modbus.di_read      (Description and example here)   This function is equivalent to : [Function Code 02 (02 HEX)] ******************************************************** @@@ Lua.modbus.hr_read       (Description and example here) This function is equivalent to : [Function Code 03 (03 HEX)] ******************************************************** @@@ Lua.modbus.hr_write      (Description and example here) This function is equivalent to : [Function Code 06 (06 HEX)] ******************************************************** @@@ Lua.modbus.in_read      (Description and example here) This function is equivalent to : [Function Code 04 (04 HEX)] ******************************************************** @@@ Lua.modbus.fp_read     (Description and example here) ******************************************************** @@@ Lua.modbus.fp_write    (Description and example here) ******************************************************** To read a floating-point (32-bit) value, the fp_read() function can be used. (Download script) To read an unsigned long (32-bit) value the hr_read() function can be used, however, some data manipulation is required (Download script) To read a floating-point (64-bit) value, the hr_read() function can be used. (Download script)   Modbus errors can be found here

Issue After downloading a hotfix for Device Administrator, it is not possible to install a new database onto an Automation Server **. **Note, for this article "Automation Server" will be used as a general term. This applies to all Smart-X controllers (Automation Server, AS-P, and AS-B). Product Line EcoStruxure Building Operation Environment AS, AS-P, AS-B  SBO Device Administrator Cause When the Device Administrator hotfix is downloaded to the machine, it replaces the "Full-Installer" version that was already installed. The new hotfix version does not include the necessary firmware to push down onto the Automation Server. This can be misleading because Device Administrator still indicates the base firmware version is present, as shown below. Resolution A full installer (such as 1.8.1.87 or 1.9.1.95) of Device Administrator must first be installed on the machine and used to install the base firmware onto the Automation Server. Then the hotfix version may be downloaded to the PC and used to apply the hotfix to the Automation Server.  **Note - In some instances a hotfix can be a full installer, which will allow for the download of a new database. Such hotfixes will be released either as a full installer or as a maintenance build. The release notes for the particular hotfixes will indicate their full installer build. 

Issue After rebooting the PC, TAC Vista Server (TACOS) doesn't get a license. You need to restart TACOS after each reboot to get a license. Product Line TAC Vista Environment TAC Vista License Server TAC Vista Server Cause TAC Vista Server (TACOS) starts up before the license system is ready to serve licenses, and therefore everything is offline until you restart TACOS. Resolution Download these tools TAC Vista Run Mode TACLicenseServer Settings (only for TAC Vista 5.1.8 and later) First of all, make sure that you have a system that is working normally and has the appropriate default settings. For more information, watch this video on YouTube Make the following setting in TACLicenseServer Settings [1] Set the startup type to "Automatic" and the taclic port to 2170 [2] Click the "License Setup" button, and write the name or IP address of the local PC. Don't use "localhost" or 127.0.0.1 but the actual name or IP.   [3] Click the "License Files" button, and check that only valid license file(s) is present in the license files folder - no other files can be in this folder. [4] Start the license server Make the following setting in TAC Vista Run Mode [1] Enter the username and password of a user with local administrator rights that have at some point been logged in on the PC. LocalSystem can be used, but it is not recommended. [2] Set TACOS to run as a service [3] In "Service Tools" set the service to start type "Automatic Delayed" [4] Start the service Now reboot the PC If TACOS still doesn't get a license after a reboot, try making this additional setting in TAC Vista Run Mode [1] Stop the service [2] Make the service depend on the license server, and also the Loytec driver if it is used in the system. Now reboot the PC If TACOS still doesn't get a license after a reboot, try adding this environment variable to Windows [1] Open the properties for the computer (Click the Windows start button, right-click "Computer", click "Properties") [2] Click on "Advanced system settings" [3] Add a new system variable called "TCP_NODELAY" and give it the value 1 Now reboot the PC If TACOS still doesn't get a license after a reboot, contact Product Support Services and reference this article Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode

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 Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue The Project Configuration Tool is installed as a Server. A project can be created but when it should be saved, an error says, "Failed to open project," and "Failed to start VM." Product Line EcoStruxure Building Operation Environment PCT version 1.1.1 Cause When PCT is installed as a server PCT, and a project is opened, the computer running PCT must have a connection to the DHCP server in the network. Resolution Make sure that the computer running PCT has a good connection to the DHCP server in the network.

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 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 Troubleshooting LON Network communications. Product Line EcoStruxure Building Operation, TAC Vista, TAC IA Series Environment Xenta Controllers MNL I/A Controllers EcoStruxure Building Operation AS-P LPA Protocol Analyzer Cause Intermittent communication failures, high bandwidth, error packages, noise on the line -- these can be difficult to pin down and identify. Resolution These two documents attached produced by Loytec are invaluable resources in troubleshooting a LON network.  The first deals with common causes of noise on LON Wires.  The second details what to do once you've procured an LPA protocol analyzer -- how to use it and interpret data.   For a Vista system, also see Actions for reducing Bandwidth in a Vista network. For an EcoStruxure Building Operation system, also see Bandwidth Throttling.    If an LPA protocol analyzer is not available there is also an option to log the Lon communication to and from the ES, AS-P, or AS-B. To do that you change the debug level from "Information" to "Trace" for: /Automation Server/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon/nsp.pin.lon.comm After the investigation make sure to set the debug level back to "Information" again. For debugging assistance a Tool called SBO Lon Decoder can be used.

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue Need the UL Listings for Xenta Product Line Product Line TAC IA Series, TAC INET, TAC Vista Environment Xenta Cause UL Listings for Xenta Product Line Resolution Go to Exchange Online and log in Search for "TAC Vista UL Listings" (Example, Click Here) You can find more information in Xenta Hardware UL 864 Listing.

Issue In some projects there is demand for importing a large number of individuals from an existing spreadsheet for individual information at one time. Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft SQL Server Management Studio Express Cause In some cases the customers have a spreadsheet or database of employees and/or users which they want to quickly import into their I/NET Seven Access control database. Resolution The whole process is to import the data from the excel file to the IDWorksView table of SQL database of I/NET. The steps below needs to be followed: Prepare the Microsoft SQL Server Management Studio Express. Click here to down this tool for version 2005 free of charge. If for version 2008, click here to download. Then install this tool. Download the individual spreadsheet Excel template and SQL script here. Save to the C:\. Ensure that the Tenant, Group have been added in I/NET already. Also ensure that all the card numbers in the spreadsheet don't conflict the ones already in I/NET. Enter the individual information into this template. If there are photos for individuals, the folder of the photos also need to be entered. Open the Microsoft SQL Server Management Studio Express and connect to the database. Find the InetDb database, and open the SQL script just downloaded from the File menu. Click Execute to run the script. Then if without any problems, the successful result will be shown in the output message window. The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality.  There is also a method that download the imported data without any operation in I/NET software by a function called Automatic DPU Restore. Refer to Automatic DPU Restore and Individuals added via Datacard ID Works are not getting access to doors for detailed information about how to set Automatic DPU Restore in I/NET. This is the method using SQL Server Management Studio Express. The Microsoft Access can also be used to do the importing work. Refer to How to import a large number of Individuals into an I/NET Access Control database for detailed information.