Building Automation Knowledge Base

Issue Satchwell AZ2401 Rotary Actuator requires replacement. Product Line Field Devices Environment Satchwell AZ2401 Rotary Actuator installed on Satchwell MBF Series Rotary Shoe Valve Body. Cause Obsolescence of Satchwell AZ2401 Rotary Actuator Resolution The Satchwell AZ2401 actuator would normally have been installed on a Satchwell MBF Valve Body. The Actuator comprised a 6 wire electrical connection enabling it to be operated from a Satchwell Z Monotronic or CZT Climatronic Proportional Controller as follows: Terminal 1 – Open signal Terminal 2 – Close signal Terminal 3 – Common Terminal A – 135 ohm Feedback Potentiometer – winding Terminal B – 135 ohm Feedback Potentiometer – wiper Terminal C – 135 ohm Feedback Potentiometer – winding If all 6 wires are connected then the AZ2401 actuator may be replaced by following SE actuators: MD20B-24 + Linkage Kit 914-1070-000 from Schneider Electric and an accessory kit   P140A from Belimo If only 3 wires are connected, that is to terminals 1, 2 and 3 then the P140 accessory kit is not required.

Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue Is there an option to disable the Forta actuator zero point check/adjustment on power up?  Environment Schneider Electric Forta actuators Cause The Forta actuator running the zero point check/adjustment on power up is causing an issue in the control sequence of the plant.  Resolution It is not possible to disable the zero point check/adjustment on power up of the the Forta actuator by any configuration of the dipswitches. The function is coded into the actuator firmware. 

Issue Trying to create a Lon binding from two or more nvo's in one Lon device (hub) to two or more nvi's in many Lon devices (targets), a so-called fan-out binding. The binding between the first Lon devices works fine, but when trying to create the binding from the Hub Lon device to the second Lon device (target) it does not work. The binding window for the second Lon device (target) is opened; the Lon device (hub) is chosen in the browser window on the right side; and the nvo in the hub is dragged to the nvi in the second target device. But the binding tool will not accept this binding. It is not possible to release the nvo from the Hub Lon device on the nvi in the second target Lon device. Product Line EcoStruxure Building Operation Environment Building Operation Workstation LON Devices Cause Normally when creating a binding using the EBO binding tool you open the binding window for the target (receiver of the value). But in this particular case you need to do it the other way around and open the binding window for the hub (sender of the value) instead, and then drag the target to the hub. Read more about Fan-out Bindings in the Webhelp. Resolution Go to the Lon device with multiple ins or outs (hub) and open the bindings window In the browser window on the right side find the target Lon device Drag the nvi from the target device to the nvo in the hub Lon device

Issue How to use bit masking to decode on/off states from a Modbus analogue registers e.g. Holding or Input registers. Where each bit is required to be read individually to indicate the status of a coil. Product Line Satchwell Sigma Software Environment Sigma IC Modbus and IC3 Modbus controllers Cause Configuration technique to read 16-bit Modbus registers for on/off states. Resolution Each modbus holding or input register is 16 bits, where each bit can be on or off i.e. 0 or 1. For example the Sigma analogue input value of 901 represents the state of a number of coils where each bit indicates the on or off.  Hence, this translates to the 16-bit binary value  0000001110000101  where 1 = on and 0 = off Create a Sigma analogue input object to read the Modbus value. Click here for the  Sigma Modbus 4.06 release Note Create a programmable object for each of the required bits (max of 16 for each register) to be read as below.  (Highlight, copy and paste into each programmable object). For Example starting with the Least Significant Bit (LSB) and where point 0|222 is the Modbus value created, the programmable objects are; Bit 1 (LSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "Bit 1 = on" 40 RETURN FALSE "Bit 1 = off" Bit 2 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "Bit 2 = on" 40 RETURN FALSE "Bit 2 = off" Bit 3 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4 ) 30 IF YINT = 4 THEN RETURN TRUE "Bit 3 = on" 40 RETURN FALSE "Bit 3 = off" Bit 4 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8 ) 30 IF YINT = 8 THEN RETURN TRUE "Bit 4 = on" 40 RETURN FALSE "Bit 4 = off" Bit 5 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16 ) 30 IF YINT = 16 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 5 = off" Bit 6 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32 ) 30 IF YINT = 32 THEN RETURN TRUE "Bit 6 = on" 40 RETURN FALSE "Bit 6 = off" Bit 7 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 64 ) 30 IF YINT = 64 THEN RETURN TRUE "Bit 7 = on" 40 RETURN FALSE "Bit 7 = off" Bit 8 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 128 ) 30 IF YINT = 128 THEN RETURN TRUE "Bit 8 = on" 40 RETURN FALSE "Bit 8 = off" Bit 9 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 256 ) 30 IF YINT = 256 THEN RETURN TRUE "Bit 9 = on" 40 RETURN FALSE "Bit 9 = off" Bit 10 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 512 ) 30 IF YINT = 512 THEN RETURN TRUE "Bit 10 = on" 40 RETURN FALSE "Bit 10 = off" Bit 11 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1024 ) 30 IF YINT = 1024 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 6 = off" Bit 12 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2048 ) 30 IF YINT = 2048 THEN RETURN TRUE "Bit 12 = on" 40 RETURN FALSE "Bit 12 = off" Bit 13 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4096 ) 30 IF YINT = 4096 THEN RETURN TRUE "Bit 13 = on" 40 RETURN FALSE "Bit 13 = off" Bit 14 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8292 ) 30 IF YINT = 8292 THEN RETURN TRUE "Bit 14 = on" 40 RETURN FALSE "Bit 14 = off" Bit 15 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16384 ) 30 IF YINT = 16384 THEN RETURN TRUE "Bit 15 = on" 40 RETURN FALSE "Bit 15 = off" Bit 16 (MSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32768 ) 30 IF YINT = 32768 THEN RETURN TRUE "Bit 16 = on" 40 RETURN FALSE "Bit 16 = off"

Issue Unable to download MP-V Flow Balance Data object to a controller using download all Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose VAV Cause The inability to use download all is a protection added to prevent overwriting any flow balance data inadvertently Resolution All Flow Balance Data Object properties are downloaded by explicitly downloading the Flow Balance Data Object as shown in the video below    

Issue On a cold start, the i2 or b3 controller does not retain the configuration stored in flash memory. The controller error log shows a 0x000014fb error.   12     E      01/01/1989 00:02:10.00     0x000014fb     0x0928ab00     0x019085a6    0x1442000c Product Line Andover Continuum Environment Continuum b3 Controller Continuum i2 Controller Cause i2 and b3 controllers must compile the controller configuration prior to backing the configuration up to flash memory.  An invalid configuration will prevent the compilation process from completing, thus preventing the backup process from succeeding.     The most common causes of OMS Backup failures are Plain English programs that contain errors. Input or Outputs that are configured without a channel number.   Resolution Correct any configuration errors.  Initiate a backup of the controller configuration to flash memory. Verify that the backup has been successful.  There should be no 0x000014fb  errors in the controller error log. 

Issue Connecting to an ES that is on another machine through WorkStation and trying to force a BACnet input or output point located on a b3, connected to an AS-P, causes WorkStation to freeze. The only way to get out of freeze is by ending the system task in Windows.   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server v2.0.2.x Building Operation Automation Server v2.0.2.x Building Operation Workstation v2.0.2.x Continuum b3xxx Controller any version Cause EBO v2.0.2.x has communication issues when connecting to an ES that is not on the machine you have WorkStation on.  Resolution Upgrading to 2.0.3.45 or later will resolve this

Issue How to bind BACnet Objects with Priority Levels Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet MPX, RPC, MPC Cause Servers (ES, AS) and other native devices (MPX, RPC) have slightly differing binding options. EcoStruxure Building Operation BACnet binding offers many options and the information below gives an example of how it can be achieved, it is not the only method. Resolution When binding between BACnet objects in EcoStruxure Building Operation (either external or within the device) it is usually better to utilize the BACnet Priority based control, often this facility is not fully exploited. Object Force and Overrides will use set priorities as in the BACnet Interface setting for the site (see System/Interface Manager/BACnet), the defaults are below. The example below shows a simple bind from a BACnet Schedule-value to a BACnet Binary-value Priority 16 (or other priority as required, as binding at Priority 16 can interfere with simple manual overrides). A BACnet datetime_value has no Priority array, so if you bind, for example, from a "BACnet Schedule Next transition" to "BACnet datetime_value Value" the bind to a Priority cannot be achieved, as below. In addition, the MPX & RPC have some constraints that Servers do not have. If you bind "Transfer Value to" an Object Value Property (rather than a Priority) then further bindings "Transfer Value to" binding to a Priority is inhibited. The screenshot below shows the error that is seen. This promotes using Priorities to control BACnet Objects.

Issue Unable to find Schlage Xdriver file on Exchange Download Center. Product Line Continuum Environment Xdriver add-on Cause It is unclear of where to download the Schlage Xdriver for Continuum.  Resolution All Schlage Xdriver .xdr files, as well as their accompanying documentation, can be found in the Schlage Wireless Lock Resources Kit on the Schneider Electric Exchange Download Center.

Issue When creating a BACnet trend log in an offline IP controller (e.g. an MP-C), the following properties are visible and can be adjusted: Delta Align intervals Interval offset Before download to the MP-C: After downloading to the MP-C these properties are not visible anymore. After download to the MP-C: Product Line EcoStruxure Building Operation Environment SmartX IP Controller Building Operation Workstation Cause Before downloading a “generic” object to a BACnet device, Workstation doesn’t know what BACnet properties the device supports and which it does not support. Therefore it will display the full super-set of BACnet properties for the given object type to the user. When the object has been downloaded, any property not supported by the device will be removed from the editor. Resolution This is by design.

Issue When viewing WebReports within WorkStation or Internet Explorer the report data is not shown. All that is seen is a blank screen even though the menu items are still displayed (as shown in Figure 1 below). Figure 1:: Report viewed through WorkStation (Or Internet Explorer) When viewing the same WebReport through a different browser, Chrome or Firefox the report displays correctly Figure 2:: WebReport viewed using other Browsers (such as Chrome and Firefox) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebReports EcoStruxure Building Operation WorkStation Cause The issue has only been seen with Internet Explorer since the other browsers appear to work. Since Building Operation WorkStation uses Internet Explorer as its internal browser, the problem is seen when displaying WebReports within WorkStation. To confirm that this is the issue you can check the Windows Event Log contents (Application Log Warnings) related to: <Provider Name="ASP.NET x.x.xxxxxxx.x" /> ... <Data>/LM/W3SVC/1/ROOT/SchneiderElectric/WebReports-1-131958191596842252</Data> <Data>Full</Data> <Data>/SchneiderElectric/WebReports</Data> <Data>C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation WebReports\WebReports\</Data> <Data>CultureNotFoundException</Data> <Data>Culture is not supported. Parameter name: culture 4096 (0x1000) is an invalid culture identifier. at System.Globalization.CultureInfo.InitializeFromCultureId(Int32 culture, Boolean useUserOverride) at Microsoft.Reporting.WebForms.ReportDataOperation..ctor(IReportServerConnectionProvider connectionProvider, Boolean requiresFullReportLoad) at Microsoft.Reporting.WebForms.HttpHandler.GetHandler(String operationType, IReportServerConnectionProvider connectionProvider) at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)</Data> Resolution To correct this issue ensure that the Windows Regional Language, found in the Windows Control Panel matches between the Workstation PC and the Reports Server.

Issue Satchwell "AL..S" series Spring Return Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell “AL..S” series Spring Return Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Cause Obsolescence of Satchwell “AL..S” series Spring Return Linear Actuator. Resolution Replace Satchwell ALMS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALMS Actuator. It should be noted however that the S-E M700 Actuator is suitable for use with 24 volt power supplies only, while the Satchwell ALMS Actuator is a mains voltage device. The S-E M700 Actuator has an average power consumption of 30 VA and the use of an independent 230 / 24 volt Transformer rated 50 VA is recommended.  S-E Transformer Type TR60 (341-3060-000)   Replacement of Satchwell ALXS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALXS Actuator. It should be noted however that where an existing Satchwell ALXS Actuator has been connected to a Satchwell Climatronic Controller via an independent Transformer, it is probable that the Transformer will have been rated to provide the level of power required by a single ALXS Actuator (23VA) In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E M700 Actuator (50VA) S-E Transformer Type TR60 (341-3060-000)   Replacement of Satchwell ALES Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell ALES Actuator. It should be noted however that where an existing Satchwell ALES Actuator has been connected to a Satchwell Climatronic Controller via an independent Transformer, it is probable that the Transformer will have been rated to provide the level of power required by a single ALES Actuator (26VA) In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E M700 Actuator (50VA) S-E Transformer Type TR60 (341-3060-000)   Please check the latest catalog for current equipment.

Issue TAC Xenta I/O modules that are added as LonWorks units in TAC Vista, are converted to Xenta I/O modules belonging to a Xenta Base unit (SlaveSpeak devices) in EcoStruxure Building Operation, after conversion using TAC Vista Conversion Tool. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista Server TAC Vista Conversion tool Xenta Xenta I/O-modules Cause In TAC Vista, the Xenta I/O modules are normally located on the same subnet as the Xenta Base unit, and belong to the Xenta Base unit, communicating as SlaveSpeak devices. If a Xenta I/O module is located on another subnet than the Xenta base unit, it could instead be added as a LonWorks Unit in Vista, and therefore communicating via LonWorks bindings to the Xenta base unit using SNVTs. Vista Conversion Tool does not handle this configuration. In the conversion tool, all Xenta I/O modules are expected to be connected directly to a Xenta base unit, located on the same Subnet, and are therefore always treated as SlaveSpeak devices. Resolution After running the Vista Conversion tool, you have to re-build the LonWorks Bindings between the Xenta I/O module and the Xenta Base unit manually in EBO, as the Conversion Tool does not handle the actual configuration setup.

Issue When an attempt is made to create or save a new schedule, you get the following error:       Product Line Access Expert Environment AccessXpert Hosted software v3 (all versions) AccessXpert Premise Software v3 (all versions) Cause Mercury has a limit of 255 schedules, which you can customize up to 254 schedules as there is the default "Always" schedule already built in. This is a limit on the Mercury hardware. Resolution It is highly encouraged customers to avoid utilizing all 255 unless absolutely necessary as you will run into the case below of not being able to add a new one should you need to (or a one-off). Folders, and all objects within them, apply towards the instance limitations. If there are 6 folders, ALL schedules in the folders plus the schedules in the instance all count towards your 255 limit.

Issue When editing an EBO graphic in Webstation rather than Workstation, there is an inherent feature which allows a user to zoom in and out of the graphic using the mouse scroll. They can also pan around the page by holding down the left mouse button as they move. In many cases however, this feature is not wanted and makes the graphic more difficult to use. Image Zoomed Out  Image Zoomed In and Panned Right Product Line Building Operation Webstation Environment Graphics Cause Pan and Zoom in Webstation are features that are enabled by default in all TGML Graphics Resolution Edit the graphic object and select the top TGML root of the page properties. There is a 'Disable Pan and Zoom' option which by default is set to False.  Setting this option to True and then saving turns off the Pan and Zoom functions for that graphic

Issue I/A Series G3 version 3.8 and N4 version 4.2 Weather Service not following redirects Product Line TAC IA Series Environment I/A Series G3 3.8.x I/A Series N4 version 4.2 or older  Cause The National Weather Service (NWS) started recently redirecting from an HTTPS to an HTTP connection. Current conditions are not updated in Weather Service. The following messages appear in station output:  TRACE [15:05:30 27-Feb-18 EST][weather] Redirect to https://www.weather.gov/xml/current_obs/KBIV.xml WARNING [15:05:30 27-Feb-18 EST] [weather] Updating current conditions failed for WeatherReport javax.baja.sys.BajaException: Unable to get NWS Current Conditions feed at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:71) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) ... 12 more java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Note: The issue does not occur in I/A Series N4 version 4.3 or higher. Resolution For I/A Series G3 version 3.8 and newer, patched weather.jar modules resolve this issue. The weather module patches are available for download from the Schneider Electric Exchange as:  weather 3.8.311.1 - G3 Firmware weather 3.8.213.3 - G3 Firmware weather 3.8.112.1 - G3 Firmware weather 3.8.41.3 - G3 Firmware    To resolve the issue in Niagara 4.2 and/or versions of G3 not covered by the patches, Clear the hidden flag on the conditionsServer slot of the weather provider and change the value to w1.weather.gov.  After making this change, the current conditions will update.  The conditionsServer slot for each weather report will need to be modified if more than one is being used.  The following is a screenshot of the provider slot sheet. The Conditions Server slot is highlighted. Select Config Flags.   Config Flags dialog. Uncheck the Hidden flag and save.   View the Property Sheet for the provider and modify the Conditions Server to be w1.weather.gov

Issue Easy Lobby is compatible with limited Continuum versions Product Line Andover Continuum Environment Continuum Cyberstation Cause The Easy Lobby integration is developed and supported by HID. There has been no further development for integration amongst other revisions. Resolution Easy Lobby is only compatible with Continuum version 1.94 SP1.

Warning   Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Issues upgrading Automation Servers (AS, AS-B, AS-P) connected to an Enterprise Server (ES) from versions prior to 2.0.x to a version that is 2.0.x. ES and one Automation Server will upgrade but no others connected to that same ES will upgrade and will show an error while attempting to download the new software.  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v1.9.x Building Operation Enterprise Server v1.9.x   Cause If the Automation Servers within the ES environment are not uniquely named, and/or are the same name as the ES, an error will be received if upgrade is attempted stating "Deploy upgraded database failed". Resolution As found within the Enterprise Central section of the 2.0 Release Notes, "All servers must have unique names".   *NOTE* Renaming the Automation Server will break any paths to that Automation Server, as such they will need to be corrected.   Follow these steps to address this issue: Prior to upgrading any devices within the environment, check for and find any servers with non-unique names Detach the Automation Server (with the naming identical to the ES or any other server) from the ES Rename the Automation Server with a unique name Correct any binding path issues Reconnect Automation Server to the ES Upgrade the environment to 2.0.x

Issue Copying objects from one MP-X device to another results in a validation error. "Property value '<object type>' already assigned"     Product Line MPx series EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause The Object ID is already used within the destination device Resolution This functions as design. To resolve this:   Manually enter the Object ID when creating files that may be copied to other MP-X devices. One may choose to use blocks of IDs up to 64,999.   2. Utilize the import/export function within EBO which will import the BACnet objects using the next available Instance IDs.