Building Automation Knowledge Base

Issue What controller models have full-wave and which have half-wave rectifier type power supplies? Environment All Controllers Cause What controller models have full-wave and which have half-wave rectifier type power supplies? Resolution   Updates Product Rectifier Type       Full  Half Built-in     Wave Wave Isolation   CC-8102-024 X   X   CC-8104   X     CC-8111-024 X   X   CC-8118 X   X   CC-8155   X     CP-25xx   X     CP-8142-024 X   X   CP-8161-333   X     CP-8161-701   X     CP-8261-333   X     CP-8261-702   X     CP-8301 X   X   CP-8301-024 X   X   CP-8391-913 X   X   CP-8511-024   X     CP-8511-102   X     CP-8511-103   X     CP-8513   X     CP-8552   X     PP-2000 Series   X     PP-8121   X     PP-8311-120 X   X   PP-8311-024   X     PP-8516   X     PP-8616   X     PP-8621   X     T155 Series X       T158 Series X       T167 Series X       T168 Series X       TC97-MHP   X X   TC97-S   X X   TC97-SHP   X X   TC-98-M   X X   TC-98-MHP   X X   TC-98-S   X X   TSP7xxx         TSP-8111       08.03.06 VER-PHx-07-S   X   08.03.06 VER-PHx-08-S   X   08.03.06 VER-PHx-09-S   X               i2/b3865   X     i2/b3866   X     i2/b3865-S   X     i2/b3866-S   X     i2/b3865-WL   X     i2/b3866-WL   X               i2/b3885   X     i2/b3885-WL   X               i2/b3867   X     i2/b3867-S   X     i2/b3867-WL   X               i2/b3865-V   X     i2/b3866-V   X     i2/b3885-V   X     i2/b3865-V-WL   X     i2/b3866-V-WL   X     i2/b3885-V-WL   X               i2/b3887   X     i2/b3887-WL   X               i2/b3887-L-115 X   X   i2/b3887-L-115-C X   X   i2/b3887-L-230 X   X   i2/b3887-L-230-C X   X   i2/b3887-L-115-WL X   X   i2/b3887-L-115-C-WL X   X   i2/b3887-L-230-WL X   X   i2/b3887-L-230-C-WL X   X             i2/b3850 X   X   i2/b3851 X   X   i2/b3853 X   X   i2/b3850-S X   X   i2/b3851-S X   X   i2/b3853-S X   X   i2/b3850-WL X   X   i2/b3851-WL X   X   i2/b3853-WL X   X             i2/b3800   X     i2/b3800-S   X     i2/b3800-WL   X               i2/b3804   X     i2/b3804-S   X     i2/b3804-WL   X               i2/b3810   X     i2/b3810-WL   X               i2/b3814    X     i2/b3814-WL   X               i2/b3608   X     i2/b3624   X     i2/b3608-S   X     i2/b3624-S   X     i2/b3608-WL   X     i2/b3624-WL   X               i2/b3920 X   X   b4920 X   X   i2/b3920-D X   X   b4920-D X   X   i2/b3920-S X   X   b4920-S X   X   i2/b3920-WL X   X   b4920-WL X   X   i2/b3920-D-WL X   X   b4920-D-WL X   X             bCX1 Family   X               NetController I   DC Input               NetController II   X               CMX9924  X   X             ACX-2   X               CX9702 X   X             I2200AC X   X   I2210AC X   X   B-LINK-AC X   X   BLINK-F-AC X   X

Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Cannot open the FlexNet License Admin, the TAC license server is not running as a service, or the vendor daemon is down. Product Line TAC Vista Environment Vista LMAdmin FlexNet License Administrator Cause If the TAC Vista Server installation option "Use the local TAC License Server" is not selected during installation, the license server will be installed but not successfully configured. When the license server is not running it will prevent the LMAdmin web interface from launching. If the license file is not in the correct location when the license server is started, then the vendor daemon must be started manually. For general information on the new license system, see LMTools Licensing Administrator program is replaced with LMAdmin in Vista 5.1.8 or greater. Resolution Remember that a valid and un-modified License File is necessary for the following troubleshooting steps to work. If the License file was manually manipulated in any way, please revert to a File specifically licensed for the machine where the License Server resides. Before proceeding, make sure the setup of the license system is made correctly following No license after reboot when TAC Vista Server (TACOS) runs as a service Check out this video about the new Vista 5 licensing system on the Community website. Check out the TAC License Server Setting tool below for the new license system. Click here to download the zip file.       Could not reliably determine the server's fully qualified domain name This is a bug in the lmadmin.exe file. Either replace the lmadmin.exe file with the newest available or install the newest version of the license system available. You can have a newer version of the license system installed than the TAC Vista version installed. E.g. TAC Vista 5.1.8 will work together with a license server version 5.1.9 Cannot Open the Flexnet License Admin Ensure that the TACLicenseServer is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services. Scroll down and select TACLicenseServer. Click Start in the top left corner of the window. Make sure that the site license is the only file in the license server path. If there is a demo license in the file path when trying to start the license server, it will fail to start. Sometimes you will get the following Windows error. Error 1067: The process terminated unexpectedly. Note: TAC License Server with spaces is not the correct license server. If TACLicenseServer is not found in the list then move on to the next troubleshooting section titled "Setting up the TAC License Server as a Service".   If the TAC License Server will not start then it may be due to another program using the 8080 TCP port. Use TCPView to search for programs running on local port 8080 and either stop this program or use the TACLicenseServer Settings tool at the top of this page to change the port that the TAC License Server uses. If the TACLicenseServer still does not run then continue to the next section below, Setting up the TAC License Server as a Service.    Setting up the TAC License Server as a Service LMAdmin.exe must be registered as a service. When first installing Vista the option "Use the local TAC License Server" should be selected. When this option is selected it will install the license server, register it as a service and start it. When "Use a license file" is selected it will only install the license server without configuring its settings. This can be corrected by reinstalling Vista and making the proper selection or by a manual configuration procedure. The manual procedure steps are listed below. Note: The option "Use a license file" only applies to a demo license, not a site license file. Manual Procedure to Register the License Server as a Service Start a command prompt as an administrator. To do this go to Start > All Programs >  Accessories and right-click on Command Prompt, then select Run as Administrator. In the command prompt go to path C:\Program Files\Schneider Electric\License Server\ (This can be done by entering "cd" and then the directory path listed here.) For 64-bit OS go to "C:\Program Files (x86)\Schneider Electric\License Server\" Run the command: "LMAdmin.exe -InstallService TACLicenseServer".   Manually copy the license files that are to be used to the new license file folder location. 32 bit - C:\Program Files\Schneider Electric\License Server\taclic\licenses 64 bit - C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses   In the command prompt type, the following command to start the license server "net start TACLicenseServer". Note: If the license files are not copied prior to starting the license server, the vendor daemon will not be started successfully and must be manually started after the license files have been copied to the new license file location. For instruction on how to do this, follow the steps in the next section Vendor Daemon is Down When the license server is installed but not configured, as mentioned above, the TAC Vista Server installer will not create a shortcut to the license administration tool in the start menu; since the shortcut will not work. A shortcut is created in the installation folder and can be used to create a shortcut in the start menu manually. The shortcut can be found here "C:\Program Files\Schneider Electric\License Server\FlexNetLicenseAdmin". For 64-bit OS the shortcut is found in "C:\Program Files (x86)\Schneider Electric\License Server". Vendor Daemon is Down   Note: If working on a 64 bit PC, replace "Program Files" with "Program Files (x86)" in the file paths below. Go to All Programs > Schneider Electric > TAC Tool 5.X.X > Flexnet License Admin. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password). Click on the Vendor Daemon Configuration tab and then select the taclic daemon. Verify that the path in the License File or Directory field matches the location of the site license. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start. If the Vendor Daemon still does not start after checking the file paths, verify that the site license has been hosted to the correct MAC address. For help finding the MAC address, see How to locate a computer's MAC address. NOTE: Also make sure there are no other Flexnet License Servers installed on this same machine (SmartStruxure, Power Manager, etc). If there is another license server running on the same machine then this can cause a conflict. SmartStruxure license and TAC Vista license on the same PC can walk you through merging them together. If IPV6 is enabled, you may need to disable it and reboot the machine. Switching from a site license to a demo license Log into LMadmin and stop the license server Save the Demo License file in C:/Program Files/Schneider Electric/License Server/Licenses Open the desired engineering tool and point Vista to the Demo file When finished, log into LMAdmin and start the License Server.  This will tell Vista to continue using the site license. A site that has worked with the installation from a remote desktop or the different user logged in Open task manager Check for process "lmgrd" of 2 of them are running the FlexNet server might try to read from the wrong server. Shutdown down both processes and restart the FlexNet server Log in to FlexNet admin and start the vendor Reread the license file Also, check License Administrator error "EXITING DUE TO SIGNAL 28 Exit reason 5"

Issue Using a Demo License with Vista, Demo will not run on site PC. Error: lc_checkout failed: Cannot find license file. FLEXible License Manager lc_checkout failed: Cannot find license file. The license files (or license server system network addresses) attempted are listed below. Use LM_LICENSE_FILE to use a different license file, or contact your software provider for a license file. FLEXnet Licensing error:-1,359. System Error: 2 "No such file or directory" For further information, refer to the FLEXnet Licensing End User Guide, available here. For instructions on using a Site License when encountering this error, refer to Switching from the Demo license to the site License in Vista 5.1.7 or older. Product Line TAC Vista Environment Vista Licensing Flexnet Lmtools lc_ Cause Unlike using a Vista Site License, the Demo license does not require the use of the Flexnet License Server. . Resolution Select a location to store the Demo License on the site PC Start Vista Menta At the prompt to select between License Server or License File, Choose "Specify the License File" Select Browse and navigate to location where you stored the license file in step 1. Highlight the Demo License and select Open. Verify that Menta starts. Start Vista Server Start Vista Workstation Verify Vista Workstation starts.

Issue Is it possible to use Sysman Alert Server with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Alarms and Events Cause Customers may wish to send important alarms to duty staff via SMS. Sysman Alert Server is one way of doing this and is easy to configure.  Resolution This is possible. The following document details the setup procedure: Sysman Alert Server with StruxureWare Building Operation The configuration will depend on the setup and location of the SysMan Server, but will generally involve "Write to File" Notifications if the Enterprise Server and Sysman Servers are installed on the same PC, or Emails to the SysMan Server (from Enterprise or Automation Server) More information can be found on Sysman's website. Part Numbers: SysManSMS ALERT SERVER: 900800600 SysManSMS GSM Modem: 900800610 In the UK when ordering please use the below part numbers. SysManSMS ALERT SERVER: 802000 SysManSMS GSM Modem: 100002

Issue Capability to import a BACnet device objects via an EDE file? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with BACnet Cause Questioning if StruxureWare Building Operation has the capacity to import a BACnet device objects via an EDE file? Resolution We do not support importing from EDE files. We would like to have a good solution for pre-engineering 3rd-party BACnet devices. This is a problem that R&D has looked at on several occasions. The Engineering Data Exchange (EDE) concept is one way to address this issue. Although the BACnet community is in favor of solving this problem, they are not aligned on using EDE files as the solution. The EDE file concept was introduced through the BACnet Interest Group Europe (BIG-EU) by Siemens as an attempt to mimic LonWorks functionality. For worldwide adoption it must become an official extension to the BACnet standard as an approved addendum via the ASHRAE BACnet committee SSPC 135. The BACnet committee has reviewed the EDE file concept and feels that the solution does not fit in with the BACnet roadmap and is not technically ideal. The EDE file is a CSV format and the BACnet committee favors a more modern standard that has extensive self-describing features such as with XML or JSON. For example, BACnet Electronic PICS (EPICS) and BACnet Web Services is XML based and their is an active XML Working Group within the BACnet committee. We understand the BIG-EU is looking to ASHRAE for guidance on this issue and would like to be aligned with the standard going forward. There is a deeper issue beyond adoption by ASHRAE and the technology choice. The reliability of the EDE file cannot be guaranteed. The BACnet Device and Network IDs and objects contained within must be set exactly in the EDE file or configured offline to match the actual device in the field. If these BACnet addresses and objects don't match you will most likely end up with major problems when the database is brought online. Packet captures will reveal duplicate messages and excessive network traffic and references will fail to work. EDE Files for application specific (ASC) devices are likely to have a longer shelf life then EDE files for free-programmable building controllers. However, if an ASC has it's firmware updated, even an ASC EDE file will become outdated and useless. It is rumored that EDE files have been used successfully in the field but want to point out that this is not a fail-safe method nor is it tested and supported. As we continue to participate in the ASHRAE BACnet working groups, we will activity engage ourselves in the pre-engineering solution discussions. Our hope is that a universally accepted solution that can address most of the concerns can become an approved addendum to the ASHRAE BACnet standard.  It turns out that the ASHRAE BACnet committee is further along than reported above. ASHRAE 135-2008 Addendum which added the XML file formats to the standard addresses this application: http://www.bacnet.org/Addenda/Add-135-2008t.pdf Looking at the rational section of this addendum you will see a list of the intended applications: This syntax is intended to be the core data representation for the following use cases: An electronic version of a PICS document, consumable by workstations and other tools, to describe the capabilities of a device. An XML version of an EPICS, defining not only the capabilities of the device, but also including the complete test database and other test-oriented data. An "as built" description of a deployed device, distributed either as a separate file or as a File Object resident in the device itself. Descriptions of proprietary objects and properties and datatypes (in any of the above three uses). These descriptions may be minimalistic, providing basic data sharing capabilities, or extremely rich, providing complete descriptions of the meaning and usage of the data to enable a comprehensive user interface, including the capability of providing such descriptions in multiple human languages. An export format for tools and workstations to export or publish their knowledge of the arrangement and configuration of a device or a complete system of devices and networks. Web services that exchange complex or constructed data With an official ASHRAE BACnet solution it is just a matter of determining which method to go with. Despite the format, it is possible to have a utility application that can automatically generate an export file. It would even be possible to convert an EDE file to XML. Albeit, I believe the EDE file would be less descriptive then an XML file generated from the actual device. It may be better to natively import via XML. We would then either get a BACnet XML file from the vendor or have a small external utility gather from the live device or convert an EDE file.

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 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 Wire colour coding for the SPP110 Product Line Field Devices Environment SPP110: 004702020 004702040 004702060 004702080 004702100 004702120 004702140 Cause Wire colour coding SPP110 required. Resolution Due to supply problems, between week 23 to week 32, there was a change to the sensor's cable and the wire colours. This was implemented by the manufacturer without Schneider Electric's knowledge. So no product announcement was produced.                      Original       Week 23 to Week 32 No. Function Colour                Colour 1     Y            Brown                Green 2    GO         Black                  White 3    G            Red                    Brown   Standard                                                                                           Week 23 to Week 32   Refer to the SPP110 Pressure Transmitter Wet Media Specification Sheet for more information.   The SPP110 installation sheet showing the standard wire colouring is available here The SPP110 installation sheet showing the wire colouring is attached.

Issue Attempts to change the buffer size on an existing BACnet trend result in the following error. Saving Changes Property write access denied '~/BACnet Interface/IP Network_2/VAV01/Application/Trends/RmTmp/Buffer_Size' BACnet Product Line EcoStruxure Building Operation Environment BACnet Trend Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause The buffer size cannot be changed on an enabled trend. Resolution Right-click the trend in question and open the Properties window. Set Log enabled to False. Click OK Open Properties again and change the buffer size to the desired size. Click OK. Open Properties a final time to set the Log to enable back to True. Click OK.

Issue "Communication failure due to routing device not available" errors when trying to view BACnet controllers or the objects they contain. Product Line Andover Continuum Environment Continuum v1.74 and above. Cause The Cyberstation is unable to route to the desired device(s). This can occur due to changes in the network, network settings, or blocking software on the PC.  Resolution Check that the IP settings of all devices are configured so they can see each other. Specifically that the subnet mask configured for each device allows them to be seen on the same logical network. Also see the following articles: Communication failure due to routing device not available Eaton IP BACnet Lighting Panels go offline with error "Communications failure due to routing device not available" Simple BBMD setup

Issue Knowing the types of licenses, differences between each one, and the revisions supported by the license. Product Line TAC Vista Environment Vista 5.X Cause There are three different types of licensing for a Vista system. Resolution There are three types of TAC Vista software licenses. TAC Vista Demo License This type of license is for temporary use. It expires every thirty days. It is the full version license excluding OPC server licenses. The demo license is available on Schneider Electric buildings business extranet. (Products >TAC Vista > Vista Software > Evaluation License File). No activation required, ready to use after downloading. (Store the license file into C:\Program Files\Schneider Electric\License Files, by default.) Monthly demo licenses only work locally for the PC where they are installed.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. For remote Workstation usage, please use the TS version of demo license instead. Demo licenses contain unlimited TAC Vista Webstation seats which allow multiple people log into Webstation simultaneously on the server PC and other computers.   TAC Vista Engineering Dongle This type of license is for Schneider Electric engineers or partners use. It comes with the full version license besides the OPC server licenses.  Please read Part number for Vista 5 engineering dongle for more purchasing information. No activation required, ready to use after receiving. Simply put the engineering dongle into one of the USB ports. You may be asked to install some software upon first time use. Note:  Insert the engineering dongle prior to starting the TAC Vista server. Engineering dongles only work locally for the PC where they are plugged in.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. Engineering dongles contain only one (1) TAC Vista Webstation seat. In addition, user can log into Webstation only on the sever PC.   TAC Vista Customer License This type of license is for end user use. Depending on the customer needs, different features of Vista software can be purchased standalone or in packages. For more information about each software feature or packages, please read the Vista 5 Software license packages and Vista 5 product catalog. Customer licenses are restricted to the minor revision of the Vista software or lower. A Vista 5.0 license will not function on a Vista 5.1 installation. However a Vista 5.1 license will work for all 5.1.x installations as well as all 5.0.x installations. Maintenance agreements ( XXXX 1 year licenses) are available for most TAC Vista 5.1 software modules. An active maintenance agreement ensures that the license has access to any new, minor and major, versions. Maintenance agreements are automatically renewed at the end of each 12 month period. The termination notice is three months. Minimum agreement time is three years. Activation of the license is required. You can generate the license on the https://schneider-electric.flexnetoperations.com website with the entitlement ID received via email after purchasing. The license needs to be locked to: Computer MAC address If you lock the license to a computer's MAC address, the license needs to be stored on this particular computer (C:\Program Files\Schneider Electric\License Files, by default), and it can only be used on this computer.   An onsite dongle (end-user dongle) The dongle needs to be purchased separately (name: Vista 5 Hardware Dongle, part number: 000857510 on the iPortal).  If you lock the license to the onsite dongle, you can use TAC Vista software on any computer as long as this dongle is plugged in. You can re-host the license to another MAC address or onsite dongle up to 4 times in a 1 year period. If you exceed this re-hosting limit you will need to contact Product Support with a valid reason why this occurred, and the limit can be reset. For additional customer licensing information please read TAC Licenses Installation Manual and TAC Vista 5.0 to 5.1.7 license does not work after installation for how to use LMTOOLS to manually read site license.

Issue Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) Product Line TAC Vista Environment LonMaker 3.X NS Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same. Cause A Program ID is a unique identifier assigned to each XIF (or device template) in an LNS database. Controllers with different XIFs cannot share the same Program ID. When a device is created in an LNS database, its Program ID is extracted from the XIF and stored in the database. When a controller is downloaded, the Program ID is transferred and stored in the controller. If the Program ID that resides in the controller differs from the one stored in the LNS management tool, the commission command will fail due to the Program ID mismatch. Resolution The appropriate resolution to the NS, #38 error depends on which controller is failing to commission. Select from the categories below which best describes the offending controller.  Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) Download the controller through the Vista System Plug-in before attempting to commission. If the error remains after a download, then the download did not go through, despite all indications that it did. Connect to the RS-232 serial port of the controller and attempt to download the Menta file directly. This will often bring to light parsing errors that are not detected by the System Plug-in. Find and correct the errors to allow the file to download properly. See Menta Parser Errors for more information on parser errors. The controller should then commission successfully. --- If the error persists, continue ---   Open the Menta file of the controller that will not commission. Under Options > Device Specification, uncheck the box for "XIF-Header generated according to LonMaker standard." (You may have to temporarily assign a System Version to activate this checkbox.) LonMark standard headings only use 255 combinations of IDs. It may be that two controllers just happened to be assigned the same Program ID. After unchecking this box, go to Options > Simulate, Commands > Generate to regenerate a new Program ID without using the LonMark standard header which opens up many more Program ID combinations and lessens the already low probability of two being the same. Download the new Menta file with the new XIF and new Program ID into the controller. It should now commission successfully.   Xenta 5/7/9XX Xenta 511, 527, 701, 711, 721, 731, 913 The XIF in the LNS database must be updated. See How to update a modified Xenta 5/7/9xx XIF file in LonMaker for detailed instructions.   ASCs/LON Devices (choose an option below) Xenta 100 series, third-party devices Replace the device using the correct XIF obtained from the manufacturers website. Replace the device using the correct XIF obtained from https://www.lonmark.org/. Replace the device with a generic device. Commission with the option of getting the XIF from the device.   Xenta 400 Series I/O Module (choose an option below) Xenta 42X(A), 45X(A), 47X, 49X Be sure the correct module is defined in Menta if adding I/O modules automatically. If adding I/O modules manually, be sure to use the correct stencil on the LonMaker drawing. You will get this error if you try to commission a 451A module with a 451 stencil.

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 Process to restore MNB-1000 to factory default. Product Line TAC IA Series Environment MNB-1000 Cause If the IP address has been lost or unit has been misconfigured how can this be restored the factory default. *This step should only be taken if the data on the unit is not to be maintained * Resolution On the DIP switch settings, set all of the switches (1-8) to the ON position. Cycle power on the controller. Unit will boot up in reset mode (red flashing status light) Once completed the status light will be solid green. The unit is now in factory default mode The IP address will be 10.1.10.2 with a 255.255.255.0 subnet mask. BACnet IP will be disabled by default and BACnet Ethernet will be active.

Issue Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Controllers: ENC-410-1 ENC-410-1-N ENC-520-2 ENC-520-2-N Cause There maybe a need to access the ENC via its serial port if the IP address of the ENC is unknown or for troubleshooting purposes when the ENC's Ethernet port is not functioning. Resolution Hardware required for connection to ENC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors. RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430). A functioning COM port on your computer. A 2-pin jumper for connection to the ENC's 'Mode' connector. Refer to the Installations Instructions for ENC-410 (pages 10 & 11) or ENC-520 (pages 10 & 11) for details on the cable and adapter.  Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC also refers to these pin outs. Connection to ENC's serial system shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the ENC’s RS-232 port and the RS-232 COM port you are using on your computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to ENC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port you are using on your computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 57600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. On the ENC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 7 of the ENC-410 or ENC-520 Installation Instructions for position of the Mode connector. With your HyperTerminal session active and configured to log to a file, remove power from the ENC, let it cycle down, then reapply power.  The easiest way to power cycle the ENC is to unplug the 6-pin power plug from the circuit board, wait 15 seconds and plug it back in.  After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... Do not press any key, wait for the login prompt. If you did press a key to stop auto-boot, select option 1. At the login prompt, enter the platform user name, and at the password prompt, the platform password. The default user name is 'tac' and password is 'niagara'. The system shell menu should now appear. You should able to see the IP address of the ENC now. When finished using the serial system shell, do the following: Remove the 2-pin jumper from the Mode connector of the ENC. From the system shell menu, select the Reboot option. Type 'y' at the 'Are you sure you want to reboot [y/n]' prompt, and press Enter. Shutdown-related text appears in the HyperTerminal window, and then the connection is dropped. Press the Disconnect button on the HyperTerminal tool bar. Exit from the HyperTerminal application, selecting to Save if you wish to reuse this HyperTerminal setup for future connection to an ENC. If you are troubleshooting the ENC, send the HyperTerminal start up messages to Product Support for analysis.

Issue The Drayton CRL 240 Actuator / Valve assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve CRL 240 Cause The Drayton CRL 240 Actuator / Valve is obsolete Resolution The Drayton CRL 240 Actuator / Valve assembly is obsolete and there is no purpose built replacement. The associated Drayton Valve Body was available in numerous sizes.  These sizes are not available in current combined Actuator / Valve designs. To replace one of the above Actuator / Valve Body combinations the following are required :- Valve sizes ½” – 2” Valve – MB(1/2" - 2") Actuator -  MD10B-230 (  MD20B-230 could  be used if MD10B-230 is not available) Auxiliary Switch - MD-S1 ( MD-S2 could be used if MD-S1 is not available) Linkage Kit - LMD/AR-MB or the RM3601 actuator without the need for a linkage kit Linkage Kit Select S-E LMD/AR-MB Linkage Kit. (914-1071-000) MBF Valve sizes 65mm – 100mm Could be replaced by the VTRE range To view the MB Valve Data Sheet, please click here. To view the MD10B Actuator Data Sheet, please click here. To view the MD-S1 Auxiliary Switch Data Sheet, please click here. To view the LMD/AR-MB Linkage Kit Data Sheet, please click here. To view the LMD/AR-MBF Linkage Kit Data Sheet, please click here. To view the RM 360 data sheet please click here

Issue MNB Controller firmware upgrade failed, which resulted in the device showing a blinking-red status LED. Product Line TAC IA Series Environment I/A Series MNB Controllers (ASC) (All firmware revisions) Note: This does not apply to the MNB-1000 Cause A blinking-red status LED means the MNB controller is in Boot Loader mode and it cannot reboot. It is now a "slave" unit, listening to traffic, not initiating communication. Resolution Using the WorkPlace Commissioning Tool, click on the File pull-down menu and select "Add MS/TP Slave". If asked to select from IP, Ethernet or MS/TP, select MS/TP. (Note: It's a good idea to have the controller isolated from the trunk, so the firmware upgrade process runs less risk of being interrupted.) At the prompt for the address, enter the address set on the controller DIP switch. The controller should get added to the list. If it is already in the list, a message will indicate that there's a duplicate address. Answer prompts in such a manner to get the controller added to the list. The 'slave' controller may show up with a blank name. Do the firmware upgrade again. This procedure works 80% of the time. If the upgrade fails, put the controller into Dedicated Boot Loader Mode. Take the controller off the MSTP trunk, set the DIP switch address to 254, cycle power, and try another firmware upgrade (keep it addressed as 254). Following a successful firmware upgrade, set the DIP switch back to the correct controller address and cycle power to the controller.

Issue There are many issues that can happen at Cyberstation and some methods are needed to troubleshoot. Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are a number of steps and tools that can be used to troubleshoot Cyberstation Resolution This subject encompasses software and hardware. It isn't a comprehensive list but should offer some methods and tools to help troubleshoot Cyberstation or webClient. Typically errors that are Cyberstation or webClient related will display some sort of an error message on the screen which can be used to diagnose the problem. Isolated or System Wide - Is the issue happening on 1 or multiple Workstations? If so, it could be a system wide issue, but if it's just one workstation then it is isolated to this PC and could be an install, Windows OS, hotfix or hardware issue. Continuum Compatibility Matrix - A number of issues can happen if Continuum Service Packs or hotfixes or Windows Operating System (including Service Packs), Microsoft SQL Server, Internet Browser version and the version of Continuum or webClient do not match the matrix. See document Software and Firmware Compatibility Matrix Version 2.03 Cyberstation Error - Is there an error message that is being displayed. A list of some Cyberstation specific errors can be found by pressing F1 with Cyberstation open, select index, type in Error, select error messages, Cyberstation How do you locate error messages in Cyberstation? Windows Error - Is there an error showing in the Windows event viewer? This step can be very useful when troubleshooting Cyberstation problems from issues installing Cyberstation or SQL to problems happening because of a Windows Operating System issue. Typically there are errors, event ids, and details that occur at the time of an issue that can be used to search the web for a solution. These can also be sent into support for some help analyzing the issue. Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Windows Service Pack or hotfixes- Were any Windows Service Packs or hotfixes recently applied to this PC that could be affecting this installation? To display all the hotfixes on a PC, see the following MS article: Windows: How to List All of the Windows and Software Updates Applied to a Computer Installed Software- Since the issue started happening has any additional software been installed on the PC. Take a look in Start> Settings> Control Panel> Add/Remove programs(XP) or Programs and Feature (Windows 10) and see what may have been recently installed. Antivirus / Malware -  On some occasions, we have seen Cyberstations or webClient PCs affected by viruses or malware. If an issue is specifically related to one PC and particularly if that PC is exposed to the internet, but doesn't have any Anti-Virus software installed, it could be infected. Updating Anti-Virus definitions and Malware/Spyware programs and running scans is recommended to clean up the PC. Hardware Issues - PCs will break over time from wear and power bumps, etc. Memory, NIC cards and Hard Drives are typically what goes first. *Memory - Many PC manufacturers supply memory diagnostic features in the system bios to detect if a RAM module is bad. This will often show in a certain spot every time in a certain program, not necessarily Cyberstation and can actually indicate that is can't access a memory reference. *Hard drives - drives can crash or certain files can become damaged. Checkdsk and the Windows OS attempts to keep the drive clean, but sometimes reformatting the Hard Drive and reinstalling the Windows OS will be required to correct the issue. If it's a physical issue with this drive then the problem could come back and a new hard drive may be needed. *NIC (Network Interface Cards) - can cause connection issues and affect system performance. Not all NIC cards are created equal and at times integrated NICs(built into the motherboard) can be less robust than a third party NIC card. See the following for extensive troubleshooting advice, but often swapping the card is easier. Advanced network adapter troubleshooting for Windows workstations *Graphics Displays - Some issue are more related to Pinpoint or Video. Check the graphics display and see if the most up to date video driver has been installed. Run any diagnostic that may be supplied by the video card manufacturer or swap out the card. Windows Device Manager - In Windows device manager you may see a black exclamation point on a yellow field which indicates the device is in a problem state. There can be many reasons this can happen and is beyond the scope of this article. See the following MS article for more information. Error codes in Device Manager in Windows System Info and Belarc Advisor - These tools can be used to see what hardware and software are installed on the PC. System info is installed with Windows. Description of Microsoft System Information (Msinfo32.exe) Tool This can be sent into Product Support as a .nfo file and can be brought up with details. This information can be difficult to work with. Belarc Advisor - This is a free tool that can be installed on a PC and will display the information in a very readable browser format. This tool will often find things that may have shown in System Info but was difficult to find. Belarc Advisor Restore Point - Windows XP, Vista and Windows 7 all have the ability to restore the system to a previous place in time by using Windows Restore Point. This is a Windows Operating System function and has some risks associated with it, but can be very useful to get back to especially when the issue is happening on a Stand Alone setup. What is System Restore? If the restore point doesn't work then a reinstall of Cyberstation or the Windows OS could correct the issue. Lastly, a reformat of the hard drive and a complete reinstall of the Windows Operating System and then reinstall Cyberstation or webClient may be needed.

Issue Communications failure due to transaction timeout when reloading b3 device. b3's version number as seen from the Infinity side reads 0.0000 Product Line Andover Continuum Environment CyberStation bCX4040 b3 Cause A b3 BACnet controller is found to exist in the BACnet folder under an MSTP Network which is different from the Network specified in the bCX's comm2 Port. Resolution Delete the MSTP network under the BACnet folder and perform a 'Find new BACnet devices'.  A new MSTP network should be created with the right network ID.