Issue The FDA requires Building Automation systems to meet their standards which are outlined in Chapter 21 CFR and FDA Part 11. Environment Vista I/NET Andover Continuum TAC I/A-series Satchwell Sigma Cause Finding documentation on Schneider Electric Building Automation Systems which comply to The Food and Drug Administration rules. Resolution Vista 21CFRPart11 support in TAC Vista 5.pdf FL-VISTA-REGIND-A4 mod RO.pdf I/NET - currently unavailable Andover Continuum With the addition of the 21 CFR Part 11 compliance pack, Continuum can meets these requirements. Satchwell Sigma SoftwareOverview.pdf Advanced Security Module.pdf Note: Validation to 21CFR Part 11 can only be performed on whole operational systems and as such, a sub-system comprising the Satchwell Sigma building management system cannot be validated in it own right. Satchwell Sigma would normally be validated as part of a whole operational system. TAC I/A Series - currently unavailable

Issue Functional block names are shorter in XIF file, LonMaker or NL220 than the names defined in SmartStruxure Environment Automation Server Externally Managed LonWorks Network Cause LonMark defines how a xif file must be structured and written. There are especially three rules that comes into play when creating the functional blocks from an Automation Server in the externally managed LonWorks network. In the LONMARK® Device Interface File Reference Guide it states that: "If the static interface contains functional blocks, the device selfdocumentation string must be formatted as described in The LONMARK Interoperability Guidelines." In the LONMARK® Application-Layer Interoperability Guidelines it states that: "Manufacturers are free to assign any functional profile number to new non-inheriting profiles, as long as they are in the range of 20000 to 25000, inclusive; and as long as the number is unique for the program ID template and scope of the resource file set containing the functional profile." In the same document it also states that: "The device self-documentation string is a string of up to 1024 bytes (subject to device memory limits)" and also "If the name is text, it must consist of ASCII printable characters, be of no more than 16 characters in length". Due to the above mentioned rules, any functional block defined in the Automation Server will always start with a functional profile number from 20001 and up and the name of the functional block (excluding the 5 digit profile number) will not be longer than 16 characters. If the name defined in SmartStruxure is longer than 16 characters, the characters from 17 and up will be deleted. If the complete length of the self documentation string is longer than 1024 bytes, the maximum character length will be lowered by one until the complete string fits within 1024 bytes. Resolution The only way to get around this is to either make fewer functional blocks on the Local Node in SmartStruxure, or to make their names shorter.

Issue Modbus Register Groups feature can overcome some Modbus communication problems. It has been seen before where the Modbus controller falls offline for a few seconds then comes back online. This cycle will repeat every few seconds. When register groups are not used, there may also be issues with the amount of time it takes for a Modbus points to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause In a normal Modbus network, a Modbus polling device obtains data from a polled device by sending a query message to the device and then waiting for the response message that contains the requested value from the selected register. If data from another register is required, the polling device sends out a new query message and awaits the response message. This process is repeated until all subscribed points values have been read. The Modbus Register Groups are a batch read function to poll Modbus devices. Instead of reading each register individually, the batch read function reads registers in manually created groups. When all registers in a group have been read, the response message returns subscribed register values for the whole group. Register grouping provides a dramatic saving in the time taken to poll your devices. For more guidance and tips on this topic, see Section "Batch Read Function" in the EcoStruxure Building Operation Technical Reference Guide.  Note: When viewing a graphic containing Modbus values, those values will update at the same interval as their Modbus register group. Resolution When grouping Modbus points, it is important to keep in mind some of the following points. Try to ensure that as many Modbus points as possible are contained in as few groups as possible. This will reduce the overall time it takes the Enterprise Server or Automation Server to read all the subscribed points in each Modbus device. Network performance can be enhanced by choosing the method of grouping that is most suitable for each device in the Modbus network.  Network performance can be enhanced by selecting a different default poll time for each register group. Network performance can also be enhanced by grouping points that have the same or similar polls. Start with higher group poll times to ensure a stable system before reducing the poll time. Make sure to delete Modbus points out of a register group individually before deleting the group. If this is not done, it can cause system delays. See article Modbus Batch Read Multiple Registers Groups Creating a Modbus Register Group In Workstation, in the System Tree pane, right-click on a Modbus device and select New Object (1).  In the create object window select Modbus Register Group (2), provide a name and select Create (3). Now that the group has been created, existing Modbus points can be dragged and dropped into the group. New Modbus points can also be created in the group.  Right-click on the Modbus Register Group and select New Object (1).  In the create object window expand Modbus Point (2), select a point type (3), provide a name and select Create (4).

Issue Does EcoStruxure Building Operation support virtualization?  Can the Enterprise and Reports server be on a virtual machine? Can EcoStruxure Building Operation be installed in cloud environments? Product Line EcoStruxure Building Operation Environment VMWare Hyper-V Microsoft Azure Amazon Web Services EcoStruxure Building Operation 2.0 through current release. Cause Desire for virtualization or cloud environment. Resolution Emulating environments Virtualization has several interpretations. In this article, we'll specifically address running EcoStruxure Building Management software in emulating environments like VMware or Hyper-V. These emulating environment software packages replicate a physical PC environment, allowing multiple computers to operate on a single machine, hence the term "virtualization". Several software vendors offer emulating systems, with VMware and Hyper-V being the most prominent. The advantages of running an emulating environment include reduced physical machines, minimized space requirements, and lower maintenance costs.   It's important to note that other potential meanings of "virtualization" such as remote desktop, remote control software, terminal server environment, or cluster environment are not covered in this article.   EcoStruxure Building Management in emulating environments Currently, numerous installations are running EcoStruxure Building Management on VMware and Hyper-V without significant issues. Some challenges have been observed related to Veeam setup, which doesn't seem to integrate seamlessly with ES (and possibly EC).   VMware is utilized internally in R&D and Product Support teams with positive feedback on its performance. Users should have familiarity with the emulating product to configure settings correctly, ensuring network functionality. It's important to highlight that no specific efforts have been made to develop EcoStruxure Building Management to comply with emulating environments. Additionally, there are no specific tests to verify its functionality in emulating environments. Certain issues have been seen with the License system used by EcoStruxure Building Operation when running on specific emulating environments due to limitations in the license system's support for these environments.   Support for EcoStruxure Building Management installations running in emulating environments Product Support provides support for EcoStruxure Building Management software, irrespective of whether it runs on PC hardware or in an emulating environment. Support is provided for problems related to the EcoStruxure Building Management Software itself, but not for issues related to the environment it runs on. Except for approved operating systems and minimum memory requirements, Product Support does not offer guidance on configuring specific PC hardware or emulating environments. Cloud environments Cloud computing environments such as Microsoft Azure and Amazon Web Services provide on-demand availability of computer system resources without direct active management by the user. Cloud computing relies on sharing of resources and typically uses a pay-as-you-go model, which can help in reducing capital expenses.   One of the challenges of cloud computing is reduced visibility and control. Cloud users may not have full insight into how their cloud resources are managed, configured, or optimized by their providers. They may also have limited ability to customize or modify their cloud services according to their specific needs or preferences.   Support for EcoStruxure Building Management installations in Cloud environments EcoStruxure Building Operation has not been developed or tested with Cloud environments in mind and it is therefore not currently a supported environment.  

Issue Unable to locate data sheet for the MD-S1 and MD-S2 auxiliary switch Product Line Field Devices Environment MD-S1 auxiliary switch MD-S2 auxiliary switch Cause No data sheets can to be found. Resolution Data sheets for the MD-S1 and MD-S2 auxiliary switches are not available. To review the MD-S Auxiliary Switch Installation Sheet, please click HERE.

Issue Drayton Theta ll EC Compensator Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Compensator Controller :- Theta ll EC Cause Obsolescence of Drayton Theta ll EC Controller. Resolution Replace Drayton Theta ll EC Compensator Controller with Satchwell CSC Compensator Controller. N.B. Two models of the Satchwell CSC Compensator Controller are available. CSC5252 without programmer details of which may be viewed here. CSC5352 including programmer details of which may be viewed here. It should be noted that the Actuator / Valve Body assembly connected to the Drayton Theta ll EC Compensator Controller may be retained for connection to the Satchwell CSC Compensator Controller. It should also be noted however that the associated Drayton Theta ll EC Compensator Controller Sensors are also obsolete. These Sensors are not compatible with the Satchwell CSC range of Compensator Controllers and must also be replaced. Satchwell CSC Compensator Controllers are compatible with the following Sensors :-   STO 600 Outside Air Temperature Sensor, details of which may be viewed here. STR 600 Room Temperature Sensor.(Optional), details of which may be viewed here. STC 600 Surface Mounting Temperature Sensor, details of which may be viewed here. or alternatively :- STP 660 Immersion Temperature Sensor, details of which may be viewed here. plus DWA 0005 Immersion Temperature Sensor Pocket, details of which may be viewed here.

Issue Need to replace an AVUE, AVUX or AVUM Mark 5 Actuator Product Line Field Devices Environment AVUE5305 AVUE5355 AVUE5304 AVUE5354 AVUX5202 AVUM5601 Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Cause Need to find a replacement for the obsolete AVUE, AVUX or AVUM Mark 5 actuator, that will allow the valve to be retained. Resolution The AVU* Mark 5 range of actuators can be replaced from the MZ300S range. AVUE5305 replace with MZ300S-24M AVUE5355 replace with MZ300S-24M AVUE5304 replace with MZ300S-24M AVUE5354 replace with MZ300S-24M AVUX5202 replace with MZ300S-24F AVUM5601 replace with MZ300S-230F The AVUE, AVUX, AVUM Mk 5 Datasheet is attached   MZ300S Specification sheet   MZ300S-24M Installation Instructions MZ300S-24F Installation Instructions   MZ300S-230F Installation Instructions

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.

Issue Instructions are needed to configure the new SMTP configuration. Product Line Andover Continuum Environment Continuum Non-Microsoft Exchange/Outlook SMTP Email Cause Configuration for the SMTP Configuration for email alarming in Continuum 2.00 through 2.03 Resolution In Cyberstation 2.0 and above, you no longer need Microsoft Outlook and Exchange to send email alarm notifications. Other SMTP servers can be used on the network and other email clients can be used also to send email alarm notifications directly to an intended recipient. Note: Public SMTP servers such as Gmail SMTP and Yahoo SMTP do not currently work with this solution as they require SSL or certain unsupported port combinations. The connections these servers establish cause connection issues within the SMTP application. Private SMTP (In-house) servers can be set up and used.   Steps to Configure SMTP Email Alarming   Open and Event Notification Navigate to the Actions Tab Select which events to receive email alarms Select the Delivery Tab Click the Add Recipient button to open the recipient configuration Browse for the recipient Cyberstation by click the ellipsis Select the recipient Cyberstation Select the SMTP Configuration button in the Recipient Configuration window Fill in the Server Configuration fields in the SMTP Configuration window Specify the SMTP Server address, port and login information Fill in the Email Configuration Specify the sender's email address - this is the email address the email will be sent from and it is also the email address that failed emails will be sent to    Type in a Subject line if needed or the default Continuum email subject line will be used Alarm Option Settings - Fill in the RetryCount and Retry Time fields  Retry Count - once you pass this value the email is dropped. The maximum Retry Count is 10  Retry Time -  field is in minutes. The maximum is 1440 minutes (24 hours) Adding an email address to the recipient list Click the Display Master List to open the SMTP Master Email Configuration Dialog Place a check in the check box to add an email address from the existing Master List to the Event Notification's recipient list and then click OK Adding or deleting email addresses from the Master Email list Open the SMTPMasterEmail Event Notification in the templates folder In the opened SMTPMasterEmail Event Notification click the Display Master List button Click the Add Recipient or Delete Recipient button depending on what is needed After selecting Add Recipient supply the email address in the recipient field and click Add Recipient After selecting Delete Recipient, select the address to highlight it and then click the Delete Recipient button. Multiple Selection is supported To deliver email notifications to the added email address, select the check box next to it Testing to ensure email address recipients receive emails Select the address you wish to test and click the Test Selected button Successful email to SMTP Server test will display a pop-up Failed email to SMTP server test will display a pop-up to the Sender's email address Final address configuration Recipients Configuration Options Place a checkmark next to the option needed Ex. Primary or Backup  SMTP Email A checkmark next to Repeat. Repeat will function as if it were an Outlook email alarm and send until the alarm is acknowledged. Known issues: In order for BACnet controllers to use the new SMTP feature, the following hotfix from the following link is needed.  CyberStation v2.00 (Only) SMTP Emailing & BACnet Alarms - Hotfix 2.03 contains the hotfix listed above   For additional information, see the Cyberstation Help, search for SMTP.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

Issue What features are included in Building Operation evaluation (demo) licenses? Product Line EcoStruxure Building Operation Environment Building Operation evaluation license Cause The features included in evaluation licenses are not shown in the documentation. Resolution License Administrator (Software Evaluation License) After adding the evaluation license in License Administrator,   Click on the "Diagnostics" Tab. Click on "Refresh the list". Local licenses list generates. Example of generated list: Local licenses: -------------------------------------------------------------------- Trust Flags: FULLY TRUSTED Fulfillment Type: TRIAL Status: ENABLED Fulfillment ID: LOCAL_TRIAL_FID_498 Activation ID: SC_57LRIHRFBOXC28SGYTPKCH98WIRKMWE Product ID: NAME=EcoStruxure Building Operation Demo License;VERSION=5.0 Suite ID: NONE Expiration date: 01-Feb-2024 Concurrent: 0 Concurrent overdraft: 0 Hybrid: 0 Hybrid overdraft: 0 Activatable: 1 Activatable overdraft: 0 Repairs: 0 Feature line(s): server.mssql (Version 5.0) client.zoning (Version 5.0) client.dashboard (Version 5.0) server.ec.auth.saml (Version 5.0) server.ws.generic.consume (Version 5.0) server.dig.signed.docs (Version 5.0) server.alarms.snmp (Version 5.0) server.ec.es (Version 5.0) server.device.es (Version 5.0) server.ws.ews.history (Version 5.0) Sigma.Server (Version 4) server.mqtt.rw (Version 5.0) graphdb.base (Version 1.0) server.esignature (Version 5.0) server.enterprise.base (Version 5.0) server.ws.ews.consume (Version 5.0) client.cad.import.tool (Version 5.0) smartdriver.license (Version 5.0) server.timescale (Version 5.0) client.script (Version 5.0) server.es.as (Version 5.0) client.graphiceditor (Version 5.0) server.device.as (Version 5.0) server.ws.ews.serve (Version 5.0) server.es.auth.saml (Version 5.0) server.enterprise.central (Version 5.0) client.functionblock.view (Version 5.0) client.station (Version 5.0)   Refer to the Webhelp EcoStruxure Building Operation Software Feature License String Description topic for an explanation of the license feature strings. Device Administrator (Embedded Evaluation License) After adding the evaluation license to the Device Administrator (see the article How to activate a demo license on an Automation Server at EBO 2022) follow the steps to view the available features: Click on the Entitlements. Click on Product Licenses. - The individual features are then shown as column headings The best way to see all the features available is to right-click on the license name under Product Name and choose Add/Remove columns.   A Select columns popup is then shown, and the available features are much easier to read.  

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

Issue How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

Issue Looking for more information on the Schneider Electric Advanced Display offering from the Smart X family of controllers. Product Line EcoStruxure Building Operation Environment SmartStruxure SmartX Controller Advanced Display Technician Tool Mobile App Cause Unsure where to locate more detail about the Advanced Display and do not know the part numbers to order the products. Resolution The Advanced Display is a convenient option for users to access, monitor, and service their SmartStruxure system. For additional information please reference the SmartX Controller - Advanced Display documents found on the The Exchange. Applications The Advanced Display comes with the SmartXKiosk application already installed on it. This app, when launched, limits which other applications may be accessed on the tablet. The only way to exit the Kiosk mode is to enter a six character PIN. Any of the available Schneider Electric apps found on the Google Play Store can be added to the SmartXKisok. Technician Tool mobile app AdaptiApps custom user apps WebStation The Technician Tool provides a simplified user interface for operation and maintenance of the SmartStruxure solution.   Communications and Wiring Options Communication Options Available Availability Wi-Fi to the BMS network (requires straight USB cable) All SmartStruxure versions USB direct communication to the Automation Server (requires Y-shaped USB cable) Versions 1.7 and newer Wi-Fi or USB direct communication to the Automation Server Premium (requires straight USB cable) Versions 1.7 and newer   The Advanced Display communicates with the SmartStruxure servers through an access point or starting in version 1.7 directly to the Automation Server via the USB port with the application named SmartX-Ad Link. If using an Automation server, the Y-shaped cable must be used to connect to a locally sourced power supply as well as to the Automation Server. The power required is 5 VDC with a minimum of 500 mA up to 1.3 A. The USB port on the Automation Server Premium (AS-P) has the ability to power the tablet directly thus only requiring a straight USB cable.    Ordering Part number Description SXWADTAB410001 Advanced Display 7 - inch - - No longer available! SXWADBUND10002 Advanced Display 10 - inch Bundle Includes Advanced Display tablet unit, mounting frame, bezel, and Micro USB 2.0 data cable 1 m (3 ft) SXWADUSBA10001 USB cable, Straight 1.5 m (5 ft) for connection to AS-P or AS-B SXWADUSBA10002 USB cable, Straight 3.0 m (10 ft) for connection to AS-P or AS-B SXWADUSBB10001 USB cable, Y-shaped 1.5 m (5 ft) for connection to Automation Server SXWADUSBB10002 USB cable, Y-shaped 3.0 m (10 ft) for connection to Automation Server   Note: The Advanced Display 10 - inch Bundle does not include a power adapter.  For configurations where the external power adapter is required the appropriate power adapter must be ordered separately for the country in which it will be installed.

Issue How to locate and download the latest firmware image versions for Sigma Controllers and Integration Controllers (ICs). Product Line Satchwell Sigma Environment 3.46.57 3.46.66 3.46.80 3.46.89 3.46.100 3.46.104 3.46.105 3.46.106 3.46.107 3.46.108 3.46.110 3.46.111 3.46.131 Cause Users may need to identify and download the correct firmware image version for their specific Sigma hardware (e.g., UNC, IC, IC3) to ensure compatibility and optimal performance. Resolution Refer to the table below for the latest firmware versions and associated release notes for each Sigma controller and integration controller type: Device Firmware Version Release Note Sigma UNC (V53) 6b UNC596 6.b – Release Note Sigma UNC3 (ARM7) 1.p.0 UNC3 1.p.0 – Release Note UNC 532 (V25) 6b UNC532 6.b – Release Note IC-Modbus V5h IC-Modbus v5h – Release Note IC3 Modbus 1.n.2 IC3 Modbus – Release Note IC SNP 5d IC-SNP v5d – Release Note IC3 SNP 1.g.1 Sigma 4.05 Firmware Supplement No specific release note available IC York V3e (Not available for download) IC-York v3e – Release Note  IC3 York 1.d.0 IC3 York 1.d.0 – Release Note IC3 Unifact 1.d.0 IC3 Unifact (RTC) – Release Note IC3 Unifact Pro 5h IC3 Unifact Pro 5h – Release Note   🔗 Note: Some firmware files or release notes may not be available for direct download. Please contact Schneider Electric support for assistance if needed.

Issue Solid red light Blinking red light Blinking green light Product Line TAC Vista Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The indicator lights on the face of the Xenta controllers can help explain the state of the controller with different actions.  Resolution There are two LED indicators – one red and one green on the Xenta programmable controllers.   The red service diode is primarily an error indication. It also lights up if the Service pin is activated. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below. Use a reset dongle to wipe the controller then reinstall the firmware and menta program. If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing. NOTE: The hardware may need to be replaced if the solid red light continues after these steps. If the red indicator light is blinking once per second this will indicate a non-configured node. If the controller has been commissioned you might try to decommission the controller and try again. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly. The green status diode blinks once per second to indicate that the program is running properly.

Issue How to exchange EBO data via a SmartConnector enabled REST endpoint. Product Line EcoStruxure building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled SmartConnector Cause Need to serve EBO data in a RESTful manner. Resolution The following video will illustrate how to: Create user account group and user with permissions required for web service client access. Enable the EcoStruxure Web Service server in the EBO server. Create and configure REST endpoint in SmartConnector framework. Use Swagger interface to review the API documentation. Test the Web service using a 3rd party testing tool. Things you need: Software EBO server with valid license (Enterprise Central, Enterprise Server or Automation server) EBO WorkStation. SmartConnector with valid license Tools SoapUI (to be used for testing)   For more information check "SmartConnector RESTful EWS Gateway" document at SmartConnector Server download center, and Troubleshooting Smart Connector SoapEwsRestProvider connection with EBO - Communities (se.com)

Issue What is the difference between an EBO SmartDriver and Smart Connector? Product Line EcoStruxure Building Operation Environment Building Operation SmartDriver Cause SmartDriver and Smart Connector enhance the openness for the EcoStruxure Building Operation, EBO, BMS system. They enable integration between EBO and 3rd party systems, even via not supported or nonstandard protocols. Resolution SmartDriver: SmartDriver enables you to create a customized interface to monitor and control 3rd party devices from the EBO server. The following block diagram shows a SmartDriver Interface and a SmartDriver Driver. The SmartDriver Interface (similar in concept to other protocol interfaces such as Modbus and BACnet) is part of EcoStruxure Building Operation software and enables you to create SmartDriver objects in the System Tree pane. The SmartDriver Driver is installed on the server drive and provides the network communications control. More information at Web Help SmartDriver Overview. Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions that extend and enhance EcoStruxure Building solutions. The Smart Connector itself runs outside the EBO server and consume or server data to EBO server via the EcoStruxure web services "EWS". Watch short explainer video for more information: https://www.youtube.com/embed/DXHvRRL4ycY   For more information, visit the Smart Connector Developer Community on the Exchange: https://community.se.com/t5/SmartConnector/ct-p/smart-connector   For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com   Smart Connector shop at Exchange:  https://shop.exchange.se.com/en-US/home 

Issue A warning banner is displayed at the top of the Workstation window that states "A license violation has been detected." even though a valid evaluation license has been activated on the machine or site. The user will also find another warning message on the LicenseManager screen, under the System folder, that provides greater detail. This message will state specifically what is missing, for example "An additional X automation server license(s) are required. Please purchase the required licenses." Product Line EcoStruxure Building Operation Environment EBO Enterprise Server 2.X and newer EBO Workstation 2.x and newer Cause The new scalable licensing structure established in version 2.0 requires licenses for each automation server device (and field devices if the system is a new database). The evaluation (demo) license will account for the required licenses as long as it is valid but sometimes can be stuck in a state where it has not been validated.  Resolution In the majority of situations, simply rebooting or performing a warm start of the Enterprise Server will clear this warning as long as there is a valid evaluation (temporary) license hosted in the license administrator the ES is referencing. Troubleshooting Steps: Restart the Enterprise Server. Restart the License Server (if on a different machine as the ES). If required, restart the ES again. Check for any errors in the License Server and verify that the Vendor Daemon is up and running. See Unable to log into WorkStation due to license error codes -12, -15, -18 or -97 for more details around this troubleshooting step. If these steps have not resolved the issue, then open a support case with your local country support organization.  For more information about the enforcement of licenses see the EcoStruxure Building Management WebHelp article, Licensing Enforcement.