Issue The EWS Interface is working and object status updates show in SBO but no alarms come in. Alarms are being triggered and showing in the Alarms Status Page in Security Expert Client but these same alarms are not showing in SBO. Product Line EcoStruxure Building Operation, Security Expert Environment Struxureware Building Operation Workstation Security Expert EWS SOAP Cause The authentication for the interface is not set up correctly. Resolution In the EWS Configuration Manager set the Authentication to Digest and define the SBO User Name and SBO User Password that the interface will use. These same credentials need to be used in the Web Services Interface when it is setup in SBO.

Issue Moving from SBO 1.9 to EBO 2.0 and above does not allow the Tech Tool to be used on SmartX Displays. Product Line EcoStruxure Building Operation Environment EBO 2.0 Cause The SmartX Display Tech Tool is being discontinued in EBO 2.0 in favour of a completely overhauled Webstation which is now designed for use on Tablets and Smart Phones as well as PCs. Resolution Tablet used here is the T580 First of all, the tablet itself will need to be brought up to Android OS 7 minimum (OS 8 works as well). Depending on how long it has been since the tablet was last connected online, the Android OS may require a number of updates before it reaches Android OS 7. Most importantly, when finished the tablet must have a firmware number ending with T580XXU2BQL1 or above.  (E.g. T580XXU2BQI9 is lower than T580XXU2BQL1). If for some reason this is not the case then please manually update the software instead. Next contact the Schneider Electric Global Expert Support Team, to obtain the latest versions of SmartX Kiosk and AD-Link application. One visible change in the Kiosk is that it now includes a Chrome shortcut as standard. The AD-Link is still required to establish the connection between the Tablet and the SmartX Server over USB using IP address 192.168.42.116. It is only the Tech Tool itself, that is discontinued. Once the AD-Link has been opened and connected, Chrome can then be used to connect to the SmartX Server using the same 192.168.42.116 Address. Successful logon can then be achieved using the same Username and Password as the Tech Tool. The new and improved Webstation interface can be accessed that is optimised for Tablet and Smart Phone screens In some cases, the customer may not want Chrome's open browser interface and may instead wish to lock down the appearance of the browser to be closer to that of the older Tech Tool. If this is the case, please refer to 'Locking Down' Chrome and Webstation in EBO 2.0 for SmartX Displays.

Issue Why does the PID example function in the Script editor library not operate like the bPID? Product Line Andover Continuum, EcoStruxure Building Operation Environment Script/ Plain English differences Cause PID example does not operate as expected with regard to the integral action. Resolution The Script Program editor contains various library functions that can be selected from the "Library" tab at the lower right of the editor screen. Plain English program/ function examples were available and used in Continuum and known as the "Andover Controls Standard Modules" ACSM, they are available in Where can I obtain standard Plain English example functions? This document also contains further information about the PID use and application. In both the script PIDLoop (Long version) library function and the bPID function as used in Andover Continuum the Proportional component is the same, they both use Proportional Gain which is defined as 1 / Proportional Band. In the Script Editor Library PID function this requires the Integral Gain constant, this is defined as 1 / Integral Action Time as used in the Continuum bPID function. In the Script Editor Library PID function this requires the Derivative Gain constant, this is defined as 1 / Derivative Action Time as used in the Continuum bPID function. Either of the functions may be used in the SmartStruxure Script editor, but you need to ensure your calling program is passing the correct arguments for the PID function used.

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

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

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

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

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

Issue How to share the thermostat data (room temperature, setpoints) among Xenta 102-AXs? Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX with or without plug-in Cause Using the wrong SNVT in Xenta 102-AX or sending the nvoEffectSetPt incorrectly will result in different unit behavior among Xenta 102-AXs. Resolution Assign the Xenta 102-AX wired with the thermostat to be the master (A), and other Xenta 102-AXs to be slaves (B to N). Use the built in SNVTs to transfer data from the master to slaves as shown in the diagram below. Sharing space temperature Bind master's nvoSpaceTemp to slaves' nviSpaceTemp. Make sure set Node Minimum Send Time and Node Send Heartbeat to be a non-zero number. (Read more information in Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller.) Sharing setpoint It is recommended to share the setpoint through the normalized nvoEffectSetpt in order to have the same unit behavior between the master and slaves. Read more information about how the nvoEffectSetPt is calculated and displayed in Xenta 102-AX Effective Setpoint (nvoEffectSetPt) Calculation. The steps of sharing the setpoint among Xenta 102-AXs are listed below: Set occupied/unoccupied heating and cooling setpoints on the master and slaves. The suggestion is to use the same setpoints setting on the master and slaves if want all rooms to operate in the same manner. In Xenta 102-AX plug-in Select Operating Parameters tab. Set the Cooling Setpoint and Heating Setpoint to desired value Without Xenta 102-AX plug-in Find SCPTsetPnts under VAV_Controller. Set the Cooling Setpoint and Heating Setpoint to desired values.   Set master's nviSetpoint under VAV_Controller to a desired temperature (eg. 72 °F or 22 °C).   Set the nvoEffectSetpt to be normalized. In Xenta 102-AX plug-in Select Operating Parameters or I/Stat Configuration tab. Under Effective Setpoint Source choose Norm of Heating and Cooling Setpoint Without Xenta 102-AX plug-in Find UCPTvavSelection.ESS under VAV_Controller Set UCPTvavSelection.ESS to 1. (Default is 0: Actual Setpoint).   Bind master's nvoEffectSetpt to slaves' nviSetPoint.   Make sure set Node Minimum Send Time and Node Send Heartbeat to be a non-zero number. (Read more information in Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller.)   Additional Suggestions: If the number of slaves is more than 30, it is better to tier up the transaction as shown below.

Issue After installing an update to SmartXKiosk, an error message is shown when trying to launch the app License file not found. Please contact Schneider Electric. Product Line EcoStruxure Building Operation Environment SmartX Advanced Display SmartXKiosk Cause The SmartXKiosk update (apk file) needs to be installed on top of the factory delivered version. If the current version of SmartXKiosk is removed before installing the update, some files are missing on the tablet. Also refer to Which address and port does the SmartX Controller Advanced Display use for activation for additional information regarding license activation. Resolution A full installer of the app is needed. Contact Product Support and request a full installer.

Issue A site has to replace a legacy device with newer hardware and wants a continuity of values being read into trend logs. Product Line EcoStruxure Building Operation Environment This has been tested for I/NET hardware replacement, but the process will work for any device which has values stored in the Extended Trend Log Cause The Extended Trend Log allows users to change the Monitored trend log attribute as needed for continuity of data. This process can be used to ensure that regulations are met regarding requirements for trend data. It is important to ensure that the new trend log is created in such a way that no significant time is lost between samples on the old log and samples on the new log. The Extended trend log will be the warehouse for the long term data of the two source logs to be stored.  Resolution In this example we are looking at an Extended Trend Log which has been collecting values for some time. To Ensure all values are transferred from the Old Log to the Extended Trend Log, Right-Click on the Extended Trend Log and select Activation>Force Transfer Edit the Properties of the Extended Trend Log and delete the Monitored Trend Log which was monitoring the old input value. Save the change to the Extended Trend Log. At this point the log will no longer collect data from it's original input source Locate the new location of the value being monitored. This could be the input an Automation Server, Field device or a logical output of a program. NOTE: Steps 6-9 show the basic process for creating an Interval Trend Log. This may change depending on the new device type or location. For creating I/NET trends, please see Using I/NET trends in StruxureWare Building Operation   Right Click on this new object and select New>Trend Select the identical type and use the identical (or similar) configuration settings. Click OK View a Trend Log list of the new Trend log to verify that it is functional. Edit the Properties for the Original Extended Trend Log Click on the ellipsis to change Monitored Trend Log setting so that the Extended Trend Log now references the newly created trend log. Save the Changes Right click on the Extended Trend Log object and select Activation>Force transfer. View the Extended Trend Log list. You should see the new values after the record of the property changes.

Issue Can a BACnet Automation Server and b3's be programmed offsite with temporary IP addresses? Are there any considerations to be made when moving the system to site and configuring with new IP addresses for the Enterprise Server and Automation Server? Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server b3xxx Controllers Cause Do not have complete IP address details for the new project but need to start programming the controllers in the office. Not sure if there will there be any issues when moving this to site. Resolution You can do this programming with a temporary IP address for the AS and then when you get to site Change the AS IP address to whatever is required. See Changing IP address of Automation Server that explains how to change the AS IP address.

Issue After creating the MSTP network from an imported XML file, all devices under the network are offline and the network is unreliable. Product Line EcoStruxure Building Operation Environment BACnet Cause The MSTP network number is not included in the XML and must be reset manually. Resolution In the MSTP network property window set the Network ID to the appropriate number. Note: To bring the devices online see Importing an exported MSTP network back into StruxureWare Building Operation.

Issue How and when does a Xenta 121 resynchronize floating control outputs? Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 121 - All versions Cause Documented reasons for floating control resynchronization on a Xenta 121 controller. Resolution There are 3 events that cause a Xenta 121 to resynchronize its floating control output logic. These reasons are: After a restart of the controller from a power cycle or reset command. The resynchronization is randomly initiated within the first 42 minutes after this restart. Testing shows an average of 20 minutes. After the controller is powered up and has done it's initial resynchronization, it will resynchronize every 18 hours there after. Commanding the snvt_switch input nviDOResync value member to  >0, and the state member to =1 Please see Programming SNVT_Switch in Menta for instructions on how to program snvt_switch in Menta.

Issue Making all Binary/Digital point types appear the same in a TGML graphic Product Line EcoStruxure Building Operation Environment TGML Cause When bringing multiple devices into the same system, 2-state values can be expressed in many different ways.  On/Off 0/1 True/False etc. Resolution Use this snippet Binary Corrector.zip to normalize the text content of all 2-state objects on a single graphics page. Delete existing binds Add this snippet to any text object and set the bound attribute as "Content" Change the True/False properties of the bind to the desired values Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue Can a Webpage be embedded in a TGML Graphics like in Continuum? Environment Workstation Cause Documentation Resolution As of version 1.4 web pages can not be embedded in graphics, however a similar solution maybe achieved using panels, see discussion in the community... https://community.se.com/message/8203

Issue Xenta 102-AX temperature sensors reading in the range of 130°F (54.4°C) when they should be closer to room temperature. Wiring has been checked and everything appears correct. What kind of temp sensor do I use for a 102-AX? Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX ETD-1xx duct temperature sensors ETR-1xx room temperature sensors STR-1xx room thermostats Cause Every other Xenta controller uses a 1.8k-ohm thermistor as a standard. Because the Xenta 102-AX is a modified version of the I/NET MR-VAV-AX, it still uses the 10k-ohm thermistors native to the I/NET product line. Resolution The Xenta 102-AX uses 10k-ohm thermistors. See 10k Thermistor compatibility with Xenta controllers for detailed information on the thermistor curve that is acceptable. Approved sensors are: ETD-2xx duct temperature sensors ETR-2xx room temperature sensors STR-2xx room thermostats STD-2xx duct temperature sensors

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue Is serial tunneling, using XPSI to Network 8000 controllers, possible through an Automation Server? Environment Automation Servers (all revisions) Cause Remote connectivity to Network 8000 controllers in a building is a desired feature Resolution There is no serial tunneling with XPSI available from Schneider-Electric. The Communities website may offer an option:  https://community.se.com/message/19507?commentID=19507?sr=search&searchId=b7102b14-5f13-4971-8a5d-ef0a0e591271&searchIndex=2#comment-19507

Issue Sometimes it is required to gather a trace log between the I/Net USB adapter and the AS or AS-P it is connected to for deeper troubleshooting investigation.  Product Line EcoStruxure Building Operation Environment Automation Server  Automation Server Premium  Workstation  Cause The I/Net adapter trace log may be requested by Product Support to help identify problem experienced in the field.  Resolution How to collect the I/Net interface adapter trace log In the Workstation System Tree, go to System > Modules > Trace > Loggers > nsp > nsp.pin > nsp.pin.inet-nsp.pin.inet.IoPort Right click on nsp.pin.inet.IoPort and go to properties. Under the Basic tab > Settings > Level, set the Level to Trace. Click OK.  Let the system run for the desired amount of time (usually 10-15 minutes). To collect the log, in the system tree go to System > Modules > Trace > TraceSettings Right click on TraceSettings and select Trace Settings and then Get trace log. Finally go back to System > Modules > Trace > Loggers > nsp > nsp.pin > nsp.pin.inet-nsp.pin.inet.IoPort, right click on nsp.pin.inet.IoPort and go to properties.  In properties under the Basic tab, change the Level back to Information.    Parse the Trace Log You can use the TAC INET LANMon Decoder tool found on the Community site.