Issue This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.

Issue When trying to activate an embedded license on a SmartX Server using Device Administrator, the activation fails with the following error message: Failure (error) received when reclaiming an embedded license on an Automation Server   "Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created." Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) All of the above v. 3.0 or higher Cause The cause of this problem is that the trusted storage, i.e., the embedded license database on the SmartX server, is corrupt. The embedded licensing framework undertakes internal checking and if it determines there is a consistency problem, it will consider the trusted storage to be corrupt. This means that no operations to the trusted storage, such as activating licenses, will succeed. At the time of writing, it is unclear why the consistency problems happen. In the server log, you may also observe the following error message: 10:08:06: Executing licensing command 10:08:06: Executing embedded operation: Activate ActivationID: ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX 10:08:11: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created 10:08:11: Licensing command completed 10:08:11: Activating licenses failed (Real Activation ID replaced with ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX)   Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the steps shown in the resolution. Please attempt all steps before contacting support.   Resolution   Building Operation 2022 v4.0.4  and above Upgrading to the above versions will now resolve the trusted storage corruption and inhibit license activation. Building Operation 3.2.X and up to EBO 2022 v4.0.3   Note: Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the below steps. Please attempt all steps before contacting support.    Clear trusted storage within the server Using Device Administrator select the affected server and Open a PuTTY Console An alternative way of connecting to the server is to use WinSCP. Use File protocol SCP and the admin user. When connected, follow the instructions as per the Word Document also attached below Warm or Cold Start the AS-P If failures still occur, attempt the Offline Activation of Licenses Workflow; The key step is that the license is activated offline and then transferred to the server in two different steps, allowing the license activation process to complete successfully.   Warm or Cold Start the AS-P If there are still failures with either of these options, send a support request through your local support center including the errors seen with each activation attempt.     Building Operation version lower than 3.2.X   If the embedded license is a Client license, there is no need to activate the license. Install the EBO Hotfix 3.0.3.2001 (CP1) or later. This will remove the enforcement of SmartX server Clients in the licensing system. See also article Embedded WebStaion client license when logging directly into a SmartX server no longer needed. Other licenses like SmartDrivers, SNMP, and Personal Dashboards may still need to be activated. Contact your local support center to fix this problem.

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line TAC IA Series, TAC Vista, Satchwell Sigma Environment I/A Series MicroNet (LON) Controllers Satchwell Sigma MicroNet series LON Controllers Vista Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for the installation of the I/A Series MNL-100, 200 & VAV controllers as well as the Sigma MicroNet 440 and 620 controllers.  The Resolution, below, is a summary of the LON design rules presented in this document. Resolution FTT-10 LON network wiring must be installed using Echelon-approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted-pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International (http://www.connect-air.com).  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum-rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   1.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy chain and not as a stub connection. 2. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). 3. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  4. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet, and repeater and/or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.

Issue Modicon Switch Ordering options and how to configure the Ethernet Switch for RSTP for EBO Product Line EcoStruxure Building Operation Environment Modicon RSTP Switch (Not Connexium) Building Operation Automation Server Premium MPX and/or RPX Controllers Ethernet Switch Configurator Cause Schneider Electric Industry Offers an RSTP enabled Ethernet Switch that can be used with EBO instead of 3rd party Switches Resolution The following video will illustrate the following steps for Ordering and installing the Modicon Ethernet Switch with EBO The Modicon Connexium Ethernet Switch has been replaced by the updated Modicon Switch Modicon Switch Part Numbers and Email address for ordering Connect and use the SE Ethernet Switch Configurator executable for Switch configuration Set the Time and use the Syslog for troubleshooting Configure EBO and the controllers (MPX/RPX) for RSTP Test the Modicon Switch, EBO, and the MPX/RPX controllers for RSTP     Related Links: Modicon Switch Part Numbers and Ordering Information - (see attached Part Number slide) MCSESM Switch Installation Manual MCSESM Switch Configuration Manual Ethernet Switch Configurator Software - look for  SchneiderElectricEthernetSwitchConfigurator2303_Windows_x86.zip Other Modicon Switch documents RSTP Troubleshooting Community Thread TGML Graphic Setup Video (Training Department)

Issue SPU 1201 Universal Pressure Switch – Specification No. 131-1-201 SPU 1202 Universal Pressure Switch – Specification No. 131-1-202 Product Line Field Devices Environment Site requesting a Universal Pressure Switch Cause SPU1201 and SPU1202 obsolescence Original PDF specification sheet is available here: DS21602-0203.pdf. Resolution The SPU1201 and SPU1202 have been made obsolete per the supplier. The closest replacement options that we have are listed below: SPU1201 is a 0.2 – 4.0 Bar device. The replacement options are SPP920 Series SPU1202 is a 12 – 250 mBar device. The replacement options are SPP920 Series Refer to Product Announcement PA-00166 for the SPP920 series Differential Pressure Switches for neutral and slightly aggressive liquids and gases.

Issue WorkPlace Tech 5.8.x, 5.9.x, 5.10.x, and 5.11.x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, 5.10x, and 5.11.x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, 5.10.x, and 5.11.x? Resolution Microsoft Windows WorkPlace Tech Tool releases 5.8 through 5.8.6 are certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.9.1 to 5.9.4 are certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional (Workplace Tech 5.10.4 only) WorkPlace Tech Tool release 5.11.0 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 10 64-bit Professional Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.8 through 5.8.6 require one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio 2021 Microsoft Office Visio Office 365 Subscription Plans 2 WorkPlace Tech Tool releases 5.11.x requires one of the following versions of Microsoft Visio (64-bit version ONLY) Microsoft Office Visio 2019 64-bit Microsoft Office Visio 2021 64-bit Microsoft Office Visio Office 365 Subscription 64-bit Plans 2 Warning: WorkPlace Tech 5.11 is not compatible with EBO WorkPlace Tech Editor. Do not install WP Tech 5.11 on a PC that has EBO WorkPlace Tech Editor installed. Continue to use WP Tech 5.10 on PCs where EBO WorkPlace Tech Editor is required.   Note: Workplace Tech Tool 5.10.0 and later releases require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow the instructions in the article link for the security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.

Issue For further information, refer to the FLEXnet Licensing End User Guide, available on the Flexera website. Product Line TAC Vista Environment Vista 5 Workstation FLEXnet Licensing Cause If you get this error and attempt to find the End User Guide, you will discover that the company that produces the FLEXnet software has gone through several name changes: Macrovision to Acresso to Flexera. Resolution If you would like a copy of this document, you can find the FLEXnet License Administration Guide (previously called the End User Guide) here.

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue How can we exclude Hosts or Users from accessing the Workstation Professional license i.e. Script, Function Block and Graphic editors from another Workstation? Product Line EcoStruxure Building Operation Environment Building Operation License Server FLEXnet Cause When accessing various editors from within Workstation a particular license does not differentiate host or user who should have access to which editors. Using the option file taclic.opt allows you to exclude certain Host / Users of StruxureWare Building Operation from accessing these Workstation clients. The Workstation clients referenced are as follows: client.station (Workstation) client.script (Script Editor) client.functionblock.view (Function Block Editor) client.graphiceditor (Graphic Editor) Resolution FLEXnet Licensing provides the options file to be included in the License Server directory. Each time the License Server service is started this file is checked. Syntax and use can be found in the attached document - Chapter 13 The following option file must reside on the License Server in the following path: Building Operation 1.9 and below: C:\Program Files(x86)\Schneider Electric StruxureWare\Building Operation 1.x\License Server Building Operation 2.0 and above: C:\Program Files(x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Once this file is copied into the License Server folder, you must restart the license service (via the Windows Control Panel, Administrative Tools, Services). Examples: # The following text excludes the features from Workstation Professional # # Use the following 3 Exclude statements if you wish to exclude an entire Workstation from accessing editors # EXCLUDE client.script HOST enter_host_name EXCLUDE client.functionblock.view HOST enter_host_name EXCLUDE client.graphiceditor HOST enter_host_name # # Use the following 3 Exclude statements if you wish to exclude a Building Operation User from accessing editors # (remove #'s below as required) # # EXCLUDE client.script USER enter_user_name # EXCLUDE client.functionblock.view USER enter_user_name # EXCLUDE client.graphiceditor USER enter_user_name # Notes: The HOST can be defined by either DNS or IP Address The USER is the user name as defined in Building Operation, this may be the same as the Windows username if using Windows Domain.

Issue Troubleshooting LON Network communications. Product Line EcoStruxure Building Operation, TAC Vista, TAC IA Series Environment Xenta Controllers MNL I/A Controllers EcoStruxure Building Operation AS-P LPA Protocol Analyzer Cause Intermittent communication failures, high bandwidth, error packages, noise on the line -- these can be difficult to pin down and identify. Resolution These two documents attached produced by Loytec are invaluable resources in troubleshooting a LON network.  The first deals with common causes of noise on LON Wires.  The second details what to do once you've procured an LPA protocol analyzer -- how to use it and interpret data.   For a Vista system, also see Actions for reducing Bandwidth in a Vista network. For an EcoStruxure Building Operation system, also see Bandwidth Throttling.    If an LPA protocol analyzer is not available there is also an option to log the Lon communication to and from the ES, AS-P, or AS-B. To do that you change the debug level from "Information" to "Trace" for: /Automation Server/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon/nsp.pin.lon.comm After the investigation make sure to set the debug level back to "Information" again. For debugging assistance a Tool called SBO Lon Decoder can be used.

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. NOTE: It is best to only use the Domain (Netbios) name (as shown above) when adding the Windows Domain name to this property.  Using the full DNS Domain name, for example, eur.gad.schneider-electric.com will cause issues when utilizing other features that require active directory authentication.  One example where this has been identified is with Change Control.   Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials. When logged on to the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log-on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites that have restricted this in some way that may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account that has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. Must use HTTPS. Must enter your Windows username and password. Must enter the domain as the Windows domain as defined within Building Operation.  See below: An example log-on format is shown below when using the above configuration when using WebStation:    Alternatively, if the following is configured in Building Operation: WebStation log-on will look as follows:  Download a TVDA for Single Sign-On Instructions

Issue How to reset an ACX 57xx model controller Product Line Andover Continuum Environment ACX 57xx Cause While upgrading/downgrading the controller firmware, communications were lost and the controller is not communicating afterwards. Resolution Consult How to reset a ACX 57xx controller to reset the controller and then re-commission.

Issue A site is required to store Extended Trend Log historical data for an extended period of time, in order to make sure the system has enough capacity for all the data  it is necessary to calculate the storage needed ahead of time Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Cause Understanding the storage requirements for long term trend storage Resolution Formula to calculate the storage capacity needed for Extended Trend Log data. Storage in bytes (S)  = Number Of Records (N) x 70 bytes. EXAMPLE: Consider a trend log of 1000 records with a 10-minute interval, if the requirement is to keep 5 years of data, how much storage capacity will be required? The number of records would (N)  be... 6 records per hour times 24 hours per day times 365 days per year*** times 5 years (*** leap years must be taken into account) N =  6 X 24 X 365 X 5 = 262800 bytes This equates to: S = N X 70 S = 262800 X 70 S = 18396000 bytes or approximately 18 megabytes   Note - The calculations above are for the native SQLite database used by EBO. There are two alternatives to using the ES database for long-term trend storage. Report Server - See the WebReports Database Usage Calculator Knowledge base article for storage calculations External Log Storage is possible from EBO v3.0 using TimescaleDB database - The EBO External Log Storage Installer tool from the community provides a databases size estimator located under the Tools menu item

Issue Is it possible to use Sysman Alert Server with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Alarms and Events Cause Customers may wish to send important alarms to duty staff via SMS. Sysman Alert Server is one way of doing this and is easy to configure.  Resolution This is possible. The following document details the setup procedure: Sysman Alert Server with StruxureWare Building Operation The configuration will depend on the setup and location of the SysMan Server, but will generally involve "Write to File" Notifications if the Enterprise Server and Sysman Servers are installed on the same PC, or Emails to the SysMan Server (from Enterprise or Automation Server) More information can be found on Sysman's website. Part Numbers: SysManSMS ALERT SERVER: 900800600 SysManSMS GSM Modem: 900800610 In the UK when ordering please use the below part numbers. SysManSMS ALERT SERVER: 802000 SysManSMS GSM Modem: 100002

Issue Documentation on the MSC-MPC Microsmart controller and its associated modules. Product Line TAC I/A Series Environment Microsmart controller MSC-MPC MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-MPC. Click each associated module part number below to view its installation instructions: MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is:  https://schneider-electric.flexnetoperations.com ocsp.r2m02.amazontrust.com Ocsp.r2m02.amazontrust.com Ocsp.rootca1.amazontrust.com If the site of the old server has issues with non-secure communications or communications forwarding between the previous and the new server, a tool is available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

Issue How does the import/export (IE) system work in the Continuum controllers? Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller. The principle is that the value of a controller point that is referenced by other controllers on the network only needs to be sent out when it changes, much like the BACnet COV which stands for Change Of Value. The two parties involved in the IE transaction are the controller that owns the point (the owner) and the controller(s) referencing the point's value (the subscribers), a second CX controller may also be involved and acting as a router when a value is imported/exported from/to a remote field device under a remote CX. Resolution Read more in the attached document, Understanding Continuum IE System.  See how to correct Import Export tables KBA

Issue TGML graphic uses the NAM Standards component to display a SmartX Sensor Device with a dynamic cover model. The graphic always shows a blank faceplate instead of the correct face - 3 buttons, LCD, or Touchscreen. Product Line EcoStruxure Building Operation Environment SmartX Sensor Device (Living Space Sensor/Room Unit Device) NAM Standards Team Components TGML Library TGML Graphic Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Cause A script running inside the graphic component is expecting a well-formatted string representing the cover model on the cover model input binding. If that data is not delivered properly, the component defaults to a blank cover. Resolution Verify that the proper component is being used based on Sensor Firmware. Verify the proper IP controller firmware is installed to meet compatibility with the Host Server and also contain desired features. Once a controller is upgraded and the sensor has had time to upgrade, check the Sensor - Properties - Basic Tab - Application Software version. If greater than or equal to 1.02.05, then use Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Otherwise use Thermostat - SmartX Living Space Sensor - Dynamic   The TGML component should work as expected, but factors outside of the graphic can make it not work right. Click on the SmartX Sensor Device and look at Properties > Basic > Status Information > Cover model. Does that show a valid cover model (ex: SXWSCBXSELXX) or does it show ASCII gibberish? If showing nonsensical ASCII string, hotfix firmware is available to address this. Install firmware at or higher than 3.02.03.02109, which includes fix for Defect# 46054 and 47266 affecting the Cover Model SmartX IP Controller v3.02.03.02109 - Firmware Package File Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=6b61d413-5cf8-47c0-ac4d-135391d375bf&title=SmartX%20IP%20Controller%20v3.02.03.02109%20-%20Firmware%20Package%20File Release Notes v3.02.03 - SmartX IP Controller Firmware Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=1e29da8d-cf49-418d-92e5-e022bc4f33c7&title=Release%20Notes%20v3.02.03%20-%20SmartX%20IP%20Controller%20Firmware If the Cover Model is populated with a proper value, a previous firmware upgrade may have caused string values to stop writing properly through the TGML binding. There are two different resolutions to try in this order: Restart the AS-P Delete the SmartX Sensor Device (be sure to select "Keep references") and add it back as a new object with the same name and address.   The binding controlling the dynamic display of different cover models on the graphic can be overridden. Inside the TGML component are 3 groups named "3 Button," "LCD", and "Touchscreen." All are hidden. Find the proper face and change it to default to Visible. Find the Bind named "CoverModel" and delete the binding and script beneath it. This is what is responsible for auto-changing the cover and is no longer needed.

Issue Modbus RTU Serial Device (RS485 - Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus RTU Master RS485 Network Cause Third party Modbus device has an address range between 248 and 255. Resolution For Modbus master/slave RS485 networks, the third party device must be in the range of 1 to 247, this is the Modbus RTU standard. This would apply not only to EBO but to other Modbus master/slave networks.   The KB article Modbus basics explains this amongst other Modbus topics.   If the third party Modbus slave device cannot be changed to an address to within this range, then contact with the product vendor may be required.   For TCP devices see the KB article Modbus TCP Device (Slave) address greater than 247.  

Issue How Permissions works in EBO Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Software Permissions are used to control user activities in a software application. For example, permissions can be setup to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Resolution EBO software permissions comprise path permissions and command permissions. Path Permission: Path permissions give a user or user account group basic permissions to the objects defined in a path. The permission level set on a path applies to all sub levels unless you set a new permission level for a sub level. Command Permission: To make the system even more flexible and useful, you can assign a user account group with special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands. Command permissions will not restrict a user from specific properties of a given window. They function to remove items from Action or Right Click menus. EBO uses the following basic rules to interpret software permission priorities: The path permission settings of lower branches overrule the settings of higher branches within a user account group For example, a user account group has the Read permission to the path /Trend_Logs and Full Access permission to the subbranch /Trend_Charts. Users in the user account group have permission to modify the objects in the /Trend_Charts but can only view the objects in the superior /Trend_Logs. If the path /System has the permission level Read, and the subbranch /Alarms has the permission level Full Access, the users in the group have full access to the objects in the /Alarms path. The highest permission rule wins between user account groups. For example, if a user has inherited the permission to accept an alarm from one group, this overrules settings from other groups that deny the user the permission to acknowledge alarms. The software permissions for a single user account overrule the permissions of any inherited user account group permissions. The path permission rules also apply to the basic commands Create, Copy, Paste, Cut, Move, Rename, and Delete. For example, you only need the Read path permission level to copy an object but you need the Full Access path permission level to paste an object. See the table for more details.       Download Software Permission.pdf, the detailed guide about how permission works in EcoStruxure Building Operation (Formerly known as SmartStruxure) and how to make it work.  Check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.