Issue Converting the entries from an MPX controller error log can be useful when there has been a software revision change. Product Line EcoStruxure Building Operation Environment EBO MPX Cause There may be an entry in an MPX error log that shows as follows: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change Resolution The ability to extract the firmware revision numbers from the controller error log is useful especially if you do not have the device report. Take a look at the last 2 numbers of the following line: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change 0x10000134  == 1.00.01.00134  (please disregard the missing 01) 0x18061101 == 2018 06 11 (ignore the trailing 01 in the hex number)

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 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 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 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 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 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.

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.

Issue Mobile Apps for Access Expert Product Line Access Expert Environment Access Expert site desiring the use of modern technology Cause Unable to find or know where to look for the Mobile Apps for Access Expert Resolution Based on the version of software using Version 2 (V2) or Version 3 (3) the apps are different for each, so please understand the differences. These can be downloaded from the app store on iOS devices.  For Version 2, there are three Mobile Apps depending on what is needed by the client, these are: Go to the App Store, click on Search and enter Keep and download the following apps Keep Monitor - which monitors what is taking place like the events on the system Keep Notify - which notifies the user via emails and texts if there is an Alarm that has been generated Keep Personnel - where existing users can be verified or picture updated etc For Version 3, there is only one Mobile App called Keep Mobile, this gives a general oversight of the system and what is going on with it. Go to the App Store, click on Search and enter Keep and download the following app Keep Mobile - which gives you the ability to see all users, events and Hardware that are configured on the system

Issue The datasheet for DO-FA-12 says: Contact rating .......................250 VAC/30 VDC, 2 A, Pilot Duty (Power Factor 0.35) What does "Pilot Duty" mean? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Bundled (AS-B) Building Operation IO-module Cause The datasheet specifies the rating class of the relays.  Understanding what "Pilot Duty" means is needed in order to know what load can be controlled by the relay. Resolution A "Pilot Duty" rating means that this relay is made for a specific highly inductive load, such as controlling the coil of another relay or contactor. Contacts with a "Pilot Duty" rating have passed standardized testing to prove they can reliably control a "Pilot Duty" load. In another example the datasheet of a device may say: Relay contact rating 250 VAC / 30 VDC, 2 A Pilot Duty (C300) In this case C300 indicates the rating of the relay, according to the UL 508 standard. The start current of a motor could damages the relays in case the current is too high. The start current could be up to 8 times the rated current, or more.

Issue Setting up Visual Verification to track who has gained access to a door using Access Expert Product Line Access Expert Environment Access Expert v3 Cause Verification of access is a common feature request in access control integrations. The following steps show how to enable and access this feature within the Access Expert v3 product. Resolution Open and connect to the instance with the required credentials Select the Access Control Tab and click on the Visual Verification button Click on the Assign Reader button to Add the respective readers and click OK The Visual Verification Window opens up with the readers that were selected from the previous step on the right side of the screen. Select the necessary readers that will be used for the verification.                    Once someone scans a card on any of the selected readers, their saved image will then be displayed    *Note* If this Window is closed the configuration for Visual Verification will be lost and will need to be recreated

Issue With revision 1.0.37 and later, folders under the instance within the navigation tree are no longer there.   Product Line Access Expert Environment V3 Hosted Cause The 1.0.37 release of the Keep software removed the folders under the instance within Folder Explorer. Resolution Use the corresponding tabs at the top of the window.  

Issue Information concerning Linux releases used within the Automation Server.   Product Line EcoStruxure Building Operation Environment Linux Operating System (OS) Building Operation Automation Server Building Operation Automation Server Premium Cause Questions concerning Linux releases used within the Automation Server. Resolution AS versions to 1.4.1 run Linux kernel 2.6.25.1 AS versions 1.5 to 2.0.2 run Linux kernel 3.0.101 AS-P versions 1.7 to 2.0.2 run Linux kernel 3.5.0-lsp-3.3.1 For questions concerning what type of Linux...i.e. Red Hat, Ubuntu, openSUSE - There is no linux distribution in the automation server just vanilla linux kernel. For further reading, download some documentation about the kernel from their website www.kernel.org