Issue List of Tables and Offsets for MicroNet 50 series, 100 series, and IACs Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment VisiSat VisiView MicroNet View Cause Need to define the Tables and Offsets for MicroNet 50 series, 100 series, and IACs. Resolution Click here to download the list of tables and offsets for the MicroNet range of controllers. Click here to download the list of tables and offsets for the IAC range of controllers. Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 and PA-00528 

Issue BACnet AlignIntervals Error when downloading b3 controller after a Continuum conversion Product Line EcoStruxure Building Operation Environment Continuum conversion b3 Controllers Cause After a Continuum conversion the b3 controllers will not download correctly and AlignIntervals error is seen. Resolution This is most likely a result of have older firmware in the b3 controllers. No exact EBO supported version is stated for the b3 controller, but it is advised to always use the latest firmware version. Early versions of SBO (v1.0 to v1.9) would have been tested with v4.500064 (June2010) and v4.500076 (Mar2014). Most EBO testing being done at v4.500077 (Nov2017). It is likely a b3 with firmware v4.500049(Jul2009) could operate correctly.   It is advised to use the current version of firmware in a b3 controller.   Continuum Conversion Tool Notes See Known Issue v3.0 See Known Issue v3.1 So for Continuum conversions, EBO v3.0.x, v3.1.1 and v3.1.2 up to CP4 should avoided. The work around for these versions is to convert using v2.0 then upgrade to the required version. Or for v3.1, use v3.1.2.6000 CP5 or later. The issues are fixed in v3.2.

Issue It is not clear which part of the license system handles the end-user license and which part handles the demo license. Having both TAC Vista and EcoStruxure Building Operation(EBO) installed on the same PC can cause conflicts in the license system. Product Line EcoStruxure Building Operation   Environment Building Operation Enterprise Server   Cause If an EcoStruxure installation is only used for engineering and therefore will only have demo licenses activated, you don't need to install the license server. The service "FLEXnet Licensing Service" is installed by any EcoStruxure software package, and that is the service that will handle the activation of demo licenses. Resolution If you will only use demo licenses on a PC and/or also have TAC Vista installed on the same PC, only install the license administrator and not the license server.   It is also possible to run TAC Vista and EBO using the same License server, please see Lesson Learned SmartStruxure license and TAC Vista license on the same PC

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 When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.

Issue Programming an application that requires a setpoint and deadband that operates in the same manner as the WorkPlace Tech Tool Thermostat object. Environment SmartStruxure AS or ES Cause No object exists in the Function Block library that is functionally equivalent to the I/A Series WorkPlace Tech LON/BACnet "Thermostat" object.   Resolution This is only one of several methods by which a differential type thermostat object can implemented in Function Block programming. The following Binary Expression (XPB) function block object can be used to simulate the differential type thermostat. Analog Input A is the "Input" Analog Input B is the "Setpoint" Analog Input C is the "Input Differential" Binary Input d is the "State Feedback"  This feedback link insures that the output state does not change when the input is within the range specified by the input differential The output of this object turns on when the Input value exceeds the Setpoint + 1/2 of the Input differential. The output of this object turns off when the Input value falls below the Setpoint - 1/2 of the Input differential. The xml file can be downloaded from here.

Issue This is a short guide to show the correct use of output blocks with forced values in Function Block programs Environment SmartStruxure AS using Function Block programs Cause There is a design difference between the Vista Menta function block programming and the new version for SmartStruxure. In the old Menta programs it is possible to connect the output from an output block and connect it to an expression block. The forced value from the output block was passed to an expression block connected downstream of the output block. This is NOT supported in SmartStruxure at the current release Ver 1.3 (April 2013) If this is done in SmartStruxure then should the output block be forced in any way the forced signal is ignored by the downstream block Resolution Follow the guidelines as detailed in the attached document.

Issue LNS plug-ins are needed in order to configure certain application specific controllers. Product Line EcoStruxure Building Operation Environment Workstation Open LNS Server Cause Many application specific controllers can be configured through Workstation but this can be very time consuming. Starting with Version 1.4.0, SmartStruxure is now able to support LNS plug-ins. Key points and features Click SBO v1.4 Activation Key for OpenLNS Server - SmartStruxure solution - PA-00285 to download the StruxureWare Building Operation v1.4 - Activation key for OpenLNS Server product announcement. Echelon OpenLNS Server must be installed on the computer that plug-ins will be used. LNS Server plug-ins can be used at the workstation to configure TAC Xenta devices using TAC STR 350 plug-in 5.1.9 or later. (earlier versions won't work) LNS Server plug-ins can be used at the workstation to configure TAC Xenta devices using TAC 100 plug-in 5.1.9 or later. (earlier versions won't work) LNS Server plug-ins can be used at the workstation to configure third party LON devices. The LNS plug-in capability will only work if the device does not require to be online to configure. If the manufacturer's plug-in requires active communication with the device then the plug-in implementation will not work. StruxureWare Building Operation database is automatically updated to any changes created with the plug-in. Resolution For LNS plug-ins to work in SmartStruxure, Echelon OpenLNS Server must be purchased and installed on the computer where plug-ins will be used. Purchasing Echelon OpenLNS Server An activation key must be purchased in order to install Echelon OpenLNS Server. The activation key is available to purchase through Schneider Electric using the part number SXWSWLNSX00001. The activation key can be purchased through standard product ordering procedures. After ordering, the activation key will be sent to you via email within a few days. Installing Echelon OpenLNS Server WARNING: You can not install OpenLNS Server on the same computer as TurboLNS without upgrading Turbo to Open. You will now be converting any TurboLNS databases to OpenLNS if they are opened on this computer. Once you have purchased the OpenLNS activation key and received it via email from Schneider Electric then you can now install Echelon OpenLNS. Double click on the executable to start the OpenLNS install wizard. Click Next. Select 'I accept the terms in the license agreement' and click Next. Fill out the information and enter you activation key. Click Next. Click Install. Click Next. Click Finish. NOTE - At step 7 above, if the PC is not connected to the internet, the registration may require an email to be send manually to Echelon to register the licence code.  Uninstalling Echelon OpenLNS Server Make sure you reference the OpenLNS Server License Guide here for information on how to return the OpenLNS license in order to use it again.   Registering LNS Plug-ins Note: Before registering LNS plug-ins, they must be installed on the computer first. If working with TAC Vista Xenta 100 and TAC STR 350 controllers, the plug-ins must be version 5.1.9 or greater. ZBuilder is included in the TAC Vista 100 download. These can be downloaded off of the Extranet in the same place as the SmartStruxure software. See LNS plugins for SmartStruxure 1.4 are not included in the release, but downloaded separately for more information. In SmartStruxure Workstation, go to the Control Panel. Click on 'LNS Plug-in Registration'. In the 'Available LNS Plug-ins' field, select the plug-ins you want to register and then click the right arrow to move to the 'Registered LNS Plug-ins" field. Click the save icon on the System tab. Note: If registering the TAC Xenta 100 plug-in, you will be prompted to select the devices you want to register. Then click OK.   Using the LNS Plug-ins Note: All changes made in the LNS plug-ins are offline configuration changes. The LNS plug-in support in SmartStruxure will not support devices that are required to be online for plug-in use.  Right click on the controller, click Configure... The LNS server is checked for a matching device template and the current device configuration is saved to the LNS server. Click Next. Double click on the plug-in listed in the window. This will launch the LNS plug-in. Make configuration changes to the controller and then save or exit the plug-in. Click Next. Click Next. The configuration changes that have been made will be listed in the window while they are being saved to the LNS server. Click Finish. Now the configuration changes that were made in the LNS server need to be downloaded to the controller. Right click on the controller in Workstation and select 'Download device configuration'.

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on The Exchange Community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue There is no quick and efficient way to configure a TAC Xenta 102-AX controller after adding it to a LonWorks Network in Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC Xenta 102-AX controller is typically configured using the LNS plug-in that is currently not available in version 1.4.0 and newer. Resolution As an alternative to the LNS plug-in, the graphic page available on the Community [1] can be used. This zip file contains the TGML graphic, binding template, and a full import file with a Xenta 102-AX that is already bound. [1] Xenta 102-AX SXW TGML Plugin v1.6.1 (SBO 1.8.0 to 1.9.3) Example Plug-in TGML Graphic PageExample Plug-in TGML Graphic Page

Issue  Script error when navigating menu in TGML graphic in 1.4. Graphic was working fine in 1.3. Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Automation Server Cause In releases prior to 1.4, graphic objects were not unloaded when navigated away from. This has been fixed in 1.4. As a result of this change, If a TGML has a navigate in a script (by using invoke) this could cause a script error if there are scripts on parent elements. Resolution Open the graphic Navigate to the script and edit, or view in source mode Add evt.stopPropagation(); before the invoke in the Click() function. For an updated version of the component without the error, go to the community: Navigation Menu (JF/Denmark) rev 2.

Issue What sensors can be used in Clean Rooms  What sensors can be used outdoors for temperature measurement What sensor can be used in a swimming pool What sensor would be explosive proof What color is the wall sensor and are custom colors available Environment Building Automation System such as I/NET, Vista, or Continuum at a site containing a clean room, swimming pool, or outdoors Cause Questions concerning the uses of Schneider Electric sensors in Clean Room applications Questions concerning temperature sensors for Outdoor installations Questions concerning temperature sensors for swimming pools Questions concerning explosion proof sensors* Questions concerning color and custom colors for sensors Resolution All the Schneider Electric temperature sensors found in the HVAC Sensor Catalogue as well as on iPortal provide high accuracy and can be mounted on the wall, in ducts, or in a J-Box. Appendix A provides the accuracy for each of the temperature sensors. Color: STR series wall sensors are: Front Cover: White NCS S-0500 N Core Plate: White NCS S-0500 N and Gray NCS S-2500 N Base Plate: Gray NCS S 1502-R Manufacturing in custom colors in not available. One option could possibly to have the sensors locally custom finished to meet customer's requirements. While there is not a direct cross reference to RAL colors, our engineering team has found the closest alternates. Please see the attached pdf. Clean Room: Depending on the specified limits of the clean room, the variety of sensors offered by Schneider Electric are possible solutions. Thing you may want to research are the standards required for the site. Clean rooms are a controlled environment where products are manufactured. It is a room in which the concentration of airborne particles is controlled to specified limits. Eliminating sub-micron airborne contamination is really a process of control. These contaminants are generated by people, process, facilities and equipment and must be continually removed from the air. The level to which these particles need to be removed depends upon the standards required. The most frequently used standard is the ISO 14644 Standards, which were first formed from the US Federal Standard 209E Airborne Particulate Cleanliness Classes in Cleanrooms and Clean Zones.  ISO 14644 is a document that establishes standard classes of air cleanliness for airborne particulate levels in cleanrooms and clean zones. Strict rules and procedures are followed to prevent contamination of the manufactured product. The only way to control contamination is to control the total environment. Air flow rates and direction, pressurization, temperature, humidity and specialized filtration all need to be tightly controlled. Outdoor:  Schneider Electrics selection of Outdoor Temperature Sensors are the STO100, 200, 500, & 600. These outdoor sensors are intended for outdoor wall mounting. Variants are available for Vista, I/NET, Continuum and Satchwell systems. The body has a 20mm conduit entry and the product is supplied with a conduit gland. Range -40 to +90 °C Accuracy See Appendix A: Table A, C, F in the attached HVAC Sensor Catalog.pdf Outdoor Temperature Sensor STO100 Order Code 5141100010 Part Number STO100 System Vista, Xenta Outdoor Temperature Sensor STO200 Order Code 5123246000 Part Number STO200 System I/NET Outdoor Temperature Sensor STO500 Order Code 5141104010 Part Number STO500 System Continuum Outdoor Temperature Sensor STO600 Order Code 5126060000 Part Number STO600 System Satchwell Outdoor Temperature Sensor STO600D Order Code 5126000000 Part Number STO600D System Drayton Outdoor Temperature Transmitters STO300 The STO300 transmitter is supplied as a complete unit, comprising a sensing element and an amplifier mounted in a housing which is resistant to ultraviolet light. The transmitter is intended for mounting on an outside wall, on the north side where possible. The transmitter is connected over a 2-wire cable, which serves both as power supply and signal transmission. The reading of the measured signal is made over an external load resistance. Outdoor Temperature Sensor STO300 -50/50 Order Code 006920501 Part Number STO300 -50/50 System All Note for each of these outdoor sensors, find the Description, the Order Code, Part Number, and the System it works with for the iBAS (intelligent Building Automation System) Please note the difference in Weatherproof and Outdoor. I put a lot of these outdoor sensors in at a university in Texas, and always installed in places that were a little protected. I found that under porches, up under the eves and out of the sun, or along a loading dock out of the rain and ice gave me accurate readings. Swimming Pool: In the piping system of a swimming pool is a corrosive environment with steadily harmful and gradually destructive minerals and chlorine in the water which present a challenge finding sensors able to withstand for extended periods of time. Schneider Electric makes several immersion temperature sensors. Beginning on page 12 of the above HVAC Catalogue, there is a variety of immersion sensors for the different iBMS lines.  One example is the STP660 is a Temperature Sensor for the European market, and intended for immersion mounting in pipe or the circulating systems. The stainless steel probe is a good solution but remember,  if the sensor is to be installed in pool water that contains chlorine, the best bet is to use a stainless steel pocket. I suppose it all depends on if sensor is in pipe associated with the secondary pool side of the system or the heating side of the system. If the sensor head is in an area exposed to Chlorine, then there may be an issue.  Chlorine may attack the solder connections of the wired joints inside the sensor. In the old days products from Satchwell used to produce special sensors for such applications where the wire connections were varnished in order to prevent corrosion. I think at the end of the day, our sensor would have a similar life expectancy to other devices in the plant that were no designed for use in such corrosive atmospheres. Explosion proof sensors: Schneider Electric does not manufacture explosion proof sensors. We do not partner with another manufacturer who provides such sensors. The closest is an 3rd party explosion proof enclosure with one of our available sensors. Our sensors are designed for building installations and if in extreme environments, we suggest enclosures.  

Issue Upon rebooting an MP-V, that has not yet gone through a Flow Balance, the Box Flow data goes to zero. Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV Cause When a box is not yet balanced, the Balanced K-Factor is zero. Part of the calculation of Box Flow is based on the Balanced K-Factor. Resolution There are two workarounds for this issue: Workaround 1: Balance the box Workaround 2: Enter in a number for the Box measured maximum flow and the Hood measured maximum flow. Either option will update the Balanced K-Factor to being a non-zero value.   This has since been fixed and first consolidated in IPC Hotfix 3.01.02.02000 (CP1), and fixed in release firmware release v3.02.01. See details in Box Flow goes to zero on restart, warm start, or cold start in the Known Issues and Solutions community page.

Issue Debugging SpaceLogic MP and RP controllers Modbus RTU Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RP-C) Building Operation RP-V VAV Building Operation EZLogic RP-C Building Operation EZLogic RP-V Cause There is no packet data can be logged or viewed for Modbus MP and RP controllers and RP controller has no transmit and receive LEDs for the Modbus and no packet data can be logged or viewed. Article Modbus in the MP and RP Controller Introduction provides information on the differences between the Automation Server and MP and RP controllers Modbus operations. Resolution There are a couple of options, but they involve using another device connected to the Modbus network to view the packets Use a PC based Modbus slave simulator Use an Automation Server set up as a Modbus RTU slave, the packets can be sent to the trace log then viewed in the usual way.  Note: A defect with v3.2.1 EBO means this solution cannot be used to monitor a Modbus RTU bus because the AS replies to all requests and may cause conflicts on the network. All versions 3.1.2 and earlier work fine, as well the EBO 2022 (v4.0.1) as detailed in the Known Issue Modbus Slave incorrect response Can use Picoscope to perform Serial Decoding for Modbus RTU as detailed in Picoscope Configuration for Modbus RTU capturing and decoding

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

Issue Resource Advisor platform, which serves as a repository for water, gas, and electric invoices, enabling customers to focus on evaluating metered data. Assisting organizations that are committed to sustainability. Setup information. Product Line EcoStruxure Building Operation, EcoStruxure Resource Advisor Environment Building Operation Automation Server Premium Building Operation Enterprise Central Building Operation Enterprise Server Cause Information on setting up Resource Advisor is not available for download Resolution Click this link for an overview of Resource Advisor. Attached is a more detailed document including EBO Setup Guide and links for additional Resource Advisor information.

Issue Instructions and programming example for using SNVT_Switch as an input or output in Menta Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The attached programming example is intended to clarify how to properly use SNVT_Switch in Menta. SNVT_Switch is a structured SNVT with two attributes, or members, State and Value. Programmatically this will be one SNVT in the device template, but it will be programmed as two separate analog points in Menta. These two public blocks will have different names in Menta, but they will share the same SNVT name with the exception of one of the points being the state member, and the other being the value member. It is important to remember that these points must always be programmed as analog points in Menta. AI's for input points, and AO's for output points. The state attribute is intended to be used for a binary on-off signal, but also contain the value -1 for Invalid value. The value attribute is intended to be used as a 0-100% signal. This SNVT is typically used in the market for starting and stopping a VFD drive and sending a speed reference with the same SNVT. The 0,1 value on the state member will start and stop the drive, and the value member will send a 0-100% speed signal. Resolution Please see the attached Menta macro as a guide to using SNVT_Switch in Menta. This example shows you SNVT_Switch as an input and as an output to the Xenta controller. To use this macro please follow these steps: Download the attached macro from above. Unzip the file and extract the SNVT_Switch.MTA from the archive to the local hard drive. Open Menta Right-click in Menta and click Load Macro Browse to the SNVT_Switch.MTA on the local hard drive and open it. It should import into the Menta file that is open.

Issue External resistors are required for Biasing and Terminating RS-485 trunks connected to an Automation Server (AS) Product Line EcoStruxure Building Operation Environment SmartStruxure Automation Server (AS) with  RS-485 trunk(s) under it. Field controllers on the RS-485 trunk; for example, the Network 8000 ASD controllers (MZ2, PEM1, etc)  Cause Bias and terminating resistors are not built into the AS hardware. Resolution External resistors are required for Biasing and Terminating RS-485 trunks connected to an  Automation Server (AS). See the Technical Reference Guide, revision 1.3, pages 2723, 2724, and 2771. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange. Biasing and Termination details are now found in the "RS-485 Communications" chapter of SpaceLogic - Hardware Reference Guide

Issue EBO 3.2.x SNMP Engine ID seen in EBO 3.2.x is not the one used by the EBO 3.2.x system. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v3.2) Building Operation Automation Server (AS-P and AS-B) (from v3.2) SNMP Cause EBO 3.2.1 introduced a new SE3Linux operating system for the AS-P and AS-B servers. The engine ID: seen in Device Administrator or Workstation is the engine ID: contained in Linux, this is not the one used by EBO 3.2.x Resolution The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Device administrator: The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Workstation The engine ID used by EBO for this example would be: 0x80002a1d03005006042bd7 The difference is always 2a1d compared to 1f88 and the rest of the bytes are the same. For further information see the attached document SNMP SBO 3.2.x Engine ID Explained.

Issue The TGML JavaScript methods alert(), confirm() or prompt() do not work on Advanced Display when using the Webstation app. Nothing happens when the methods are used, and the modal window that is expected is not displayed. See attached TGML file for a graphic example using the JavaScript methods. Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V2 Building Operation Advanced Display V3 Cause The embedded browser in the Webstation app does not support alert(), confirm() and prompt(). Resolution Use other ways to interact with the user that do not use modal windows. It is also likely that the usability of your graphics will benefit from removing the above mentioned JavaScript methods.