Building Automation Knowledge Base

Issue The automation server was added successfully; however, it never appeared in the server list. It did, however, get added to the communications tab. The System Tree server list varies from the Communication tab list of servers. No servers shown under "Servers" List in System Tree but is seen in Communications tab Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause This is typically caused by the Group account not having permission to access the root path.  To verify this is the issue, log in with the "admin" user account and verify that the server lists match.    Looking at the screenshot below: If the Add (+ icon) option has been used to add the ES-1 Path Permissions, no server will be visible.  Additional Path Permissions need to be added for each server. If the Add System (Hierachial icon) option is used (the default for the local admin account group), this is the System's top-level path. Then, all servers will be seen.       See online WebHelp topic User Account Group – Software Permissions Tab Resolution Depending on which method is required by the end user. If using the Add (+icon) option  Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add (+) the Automation Server(s) to the path permissions as shown below: Repeat the above step for every server Each time a new Automation Server is added, repeat all steps.  If using the Add System (Hierachial icon) option Login into the Enterprise Server with the local admin account Navigate to the Group(s) that need access to the server list and select the Permissions tab Add System (Hierachial icon) to the path permissions as shown below: Users must log off and log on to see any of the implemented changes.    

Issue  EBO can have license violation bar without a known reason. 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 Building Operation Edge Server - Standard Cause License enforcement is the process of checking whether a software application has a valid license available to it at runtime. If you do not have enough licenses, a license violation occurs. This is accomplished by a license violation bar in WorkStation and WebStation.   Firstly, the license violation will be yellow, and it can be hidden for 8 hours. You can use Hide to hide the License Violation bar for 7 days. After 7 days, the Hide function is disabled. After 30 days, the bar turns red. Resolution Below information can be collected to help in troubleshooting: Refer to the document Part Number Summary and Hardware Software Matrix for software and features that need licenses and note that some feature licenses can be inherited from parent server to child servers. Get a screenshot of the License information page in the control panel, make sure to have all content in license information page are shown in the screenshots, ex child servers' status. It can tell which feature needs a license or which child server needs a license, refer to License Information Get the License Diagnostics, and entitlement certificates to make sure that required licenses are activated. Install the latest CP/hotfix to make sure that the system is not affected by one of the known license related defects, Make sure that all EBO servers have correct date and time, incorrect date and time can cause license violation, as explained in: Incorrect Automation Server date and time leads to license violation - Schneider Electric Community Check Known issues community. Get screenshots for the following: In ES, "System/LicenseManager/LicenseStatus/ConnectedASLicenseStatus" will show all connected Automation Servers. Show the license violation tab to know which Automation Server has violation as Automation Server may have violation although license information doesn't show that, ex. if the "Change Control" feature is enabled in an Automation server and ES doesn't have a license for it. For parent server and any server that has violation, search in folder "/System/LicenseManager/LicenseStatus". In the object name, write "*" and add columns License Violation, Checked Out License, Available Licenses, Required Licenses, and Installed Licenses. Export the results to XLSX. Check license Metadata for the parent server and any servers have license violation, search in folder "/System/LicenseManager/LicensingMetadata". In object name, write "*" and add columns FeatureVersion, FatureName, ProductVersion, EntitlmentID and Activation ID. Export the results to XLSX.   Get screenshot from FlexNet Publisher web interface, localhost:8888, concurrent tab. Make sure all features are shown in the screenshot, and the entire webpage can be saved instead of taking screenshots. If the server has just started, wait for some minutes till all data is collected.   Collect the logs and configuration files listed below: Log files located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\logs Configuration file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\conf Using EBO WorkStation, go to module, '/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.licensemanager", set trace level to debug, reproduce the issue, if possible. Collect the server logs, then set the module trace level back to "information", refer to Collect logs from an Automation Server - Communities and Collect logs from the Enterprise Server and Enterprise Central - Communities.

  Issue The IoT alarm is being displayed, and acknowledging the alarm removes it temporarily, but it returns. Product Line EcoStruxure Building Operation Environment Building Operation EnterpriseServer Building Operation Workstation Lead/Shadow enabled System Alarms  Cause In Building Operation version 3.0.1, Cloud Connectivity was enabled at the Automation Server.  The alarm indicates that the Automation Server cannot connect to the Cloud server, whether attached to an Enterprise Server or Standalone, typically because there is no internet access.   By default, the option for Cloud Connectivity is set to Auto. Once the Automation Server is attached to an Enterprise Server, this option is applied in all sub-server settings and controlled from the lead object in the Enterprise Server. Resolution To prevent the alarm from triggering, Navigate to the Enterprise Server Control Panel Under the "Security and Communication" section, select Cloud Connectivity Switch the function from Auto to Disable. This change will be passed down to all sub-servers. Should the alarm not clear, a power cycle may be necessary to clear this alarm. See the following online WebHelp topic, Cloud Connectivity Overview, for further information. 

Issue The site has cloud connectivity issues, and R&D requires the trace log to see the communication. The trace logging for the cloud plugin (/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.Cloud) has been enabled and set to Trace, and there are no records of nsp.pin.Cloud referenced within the trace log. Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment EcoStruxure Building Advisor EcoStruxure Building Operation v3.0.3 or earlier  Cloud Connectivity Cause In versions before 3.0.4, by default, the cloud plugin does not report on the trace log. Enabling trace log reporting for nsp.pin.Cloud is a high-level procedure that requires support intervention.     Resolution This version (3.0.4) and lower are now out of support, so it is recommended that to upgrade to a supported version. Cloud messages are now recorded in the trace when enabling the logging level to TRACE on the /System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.Cloud object. 

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When viewing License Information, the Activated count still shows 0 for all features. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation License Server Cause There are multiple causes for this, as we are aware: Running Demo license License Server not running / uninstalled.  It is possible to activate licenses and then uninstall the License Server, and licenses will still be active and available to EBO components.   Firewall setting Recently, we have located an issue where multiple paths exist for the License Server in the Windows Registry. The specifics of how this occurs is still unknown, but it has been seen on a few installations.   Resolution Before starting, remove the demo license and restart the license server.  The systems, that is, the Enterprise Central/Server, will continue to run until the servers are restarted.   This will be necessary after completing the registry reset.    SBO License Server Reset Has been updated to check the known locations of the registry and provide the ability to make these entries the same as those entered in the License Administrator      A pop-up will appear during the initial running of the Reset Tool to indicate this, as shown below.   If the tool is unavailable or you wish to check this manually, then a Windows Registry search for the key TACLIC_LICENSE_FILE and its data should show its value and indicate the different (or the same) paths. Updating the TACLIC_LICENSE_FILE data to match the License Server path shown in the License Administrator should resolve the issues.     SBO License Setup This registry check is also included in the SBO License Setup tool.  In this instance, it automatically details the changes.  After selecting OK (in the screenshot below), you'll have the option to Apply (or cancel) any of the changes applied by the tool.        

Issue The properties of any server, Enterprise Server or Automation Server, in SmartStruxure has a Communication tab that will list the IP addresses of all associated servers on the network. Changing the IP address of an AS requires every other AS to know about the change in order to preserve any server-to-server communication. In the example below, the system has been engineered in-house on a 10.10.x.x network domain. It was then moved to site where the domain of the ES and all AS were changed to 10.159.x.x. Viewing the Communication tab on the ES shows all IP addresses have been properly updated: However, if the DNS/IP Address column is viewed from the Communications tab of one of the Automation Servers, the results vary as to which IPs have been properly updated: Automation Server A Automation Server B Automation Server C If there is any communication between two Automation Servers, and the IP addresses have not properly updated, then communication between them will break. 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 Building Operation Edge Server - Standard Cause Any change to an Automation Server's IP address must be represented in the Enterprise Server (if there is one). It must also be updated in all associated Automation Servers. It is best practice following the change of any IP address on the system to perform a refresh of the addresses from the Enterprise Server. Note: This is also applicable in a network with Enterprise Central hosting Enterprise Servers. Resolution Right Click on the ES. Select Advanced>Repair Server Communication. Refer to: Repairing EcoStruxure BMS Server Communication

Issue How to identify what ports are being used on a PC. Product Line All product Lines. Environment Any Windows OS Cause Running multiple applications on the same PC without managing TCP/UDP port assignments can lead to conflicts. Resolution TCPView will help you identify all ports and services to each application. Download from Microsoft's website http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx Detailed instructions are available at the site.

Issue Can an Automation Server operate as an MSTP device on a third party BACnet MSTP network? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Want to connect an Automation Server to a 3rd party system as an MSTP device, is this supported? Resolution An Automation Server operating as a device on a third party BACnet MSTP network is NOT a supported solution. An MSTP network needs to be managed and usually accessed from a network master, the AS is designed to be that device. The Automation Server is supported as the management and routing device for an MSTP network. From the PIC statement, an Automation Server will operate as a MSTP Master.

Issue Continuum i2 and b3 devices share the same hardware platform, however, power consumption on the devices IO Expansion Port differs depending on the communication protocol firmware (Infinet or BACnet) running in the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment All i2 devices All b3 devices Cause Even though the hardware of an i2 device is identical to that of its counterpart b3 device, the difference in firmware causes variation in power consumption on the device's Expansion IO port, specifically, it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  Now that conversion of devices from one protocol to another is occurring in the field, it has become evident that there are cases where the 180 mA limit is exceeded in an i2 device without any negative results, but once the i2 device is converted to a b3 device, all IO on the expansion port stop working. Resolution Before converting an i2 device to a b3 device in the field, it is crucial to review the Expansion IO Datasheet (attached) to ensure that the configuration does not exceed the specified power consumption limit. If the configuration exceeds the 180 mA limit, take the following steps: Remove any additional xP module causing the limit to be exceeded. Reconfigure the xP modules to ensure that the configuration does not consume more than 180 mA.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue When upgrading to 1.8.1 a Xenta Central Schedule that resides outside the LonWorks network it is not upgraded to the current version. If the upgrade is attempted it breaks all the Xenta time schedule bindings with the Xenta Cental Schedule. Product Line EcoStruxure Building Operation   Environment StruxureWare Building Operation 1.8.1   Cause During the LonWorks Pre-upgrade only the objects under the LonWorks networks are upgraded. If the Xenta Cental Schedule is located outside the LonWorks network this is not included in the upgrade process. Resolution Options to resolve this issue. Before upgrading to 1.8.1 If the site uses Xenta Central Schedules, then use the server Hotfix 1.8.1.5101 to upgrade all the servers. Please contact Product Support and request Hotfix 1.8.1.5101. After upgrade to 1.8.1 There are two options in this case: You can delete the Xenta Central Schedule and add a new Xenta Central Schedule. You are then able to bind the Xenta Schedules to the new Xenta Central Schedule.   If there are many Xenta Schedules that refer to a Xenta Central Schedule you can use the export function to resolve the problem as shown here Export the  Xenta Central Schedule as shown here Once you have exported the Xenta Central Schedule you need to edit the exported XML file with Notepad++ and change the Xenta Central Schedule attributes from "lon" to "lon2".  This is what the change should look like Once this change has been made the XML File can be saved ready for an import to the Server. Delete the existing Xenta Central Schedule from the database, making sure you check the box keep references. Then import the edited XML to the server and this will re-establish the Xenta Central Schedule binding with the Xenta Schedules.

Issue Opening the Vista SmartStruxure Interface setup, found in the status box, message "service not found" is displayed. Product Line EcoStruxure Building Operation Environment TAC Vista server Vista SmartStruxure interface Cause Some dll may be missing causing the service could not start. Resolution Manually run the VistaInterface execution file. By default TACVistaSmartStuxureInterface.exe file is stored in C:\Program Files\Schneider Electric\TAC Vista SmartStruxure Interface 1.0.5. Double click on the TACVistaSmartStuxureInterface.exe file, if the service could not be started, it will pop out an error message window. If it is a dll file missing, can find the corresponding dll on the internet, and solve this issue. If the error message shows some other error, please make a copy of the error message and contact the local support team for further assistance.

Issue Replacement screw terminals for an Automation Server (AS/AS-P) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause The screw terminals are missing on an Automation Server Resolution The AS-P Screw Terminals are 5.08mm pitch and are available from RS Components:- 3 way plug part no. 189-6026 4 way plug part no. 189-6032 5 way plug part no. 189-6048 Or alternatively from  Farnell:- 3 way plug part no. MOLEX 39530-0003 4 way plug part no. MOLEX 39530-0004 5 way plug part no. MOLEX 39530-0005

Issue After 2000 backups an attempt to perform a backup to flash results in the error 'Flash backup for this controller has been disabled.' Product Line EcoStruxure Building Operation, Andover Continuum Environment b3 controller i2 controller Cause Flash memory has a limited write count; Controllers implement a flash circuit breaker that trips after 2000 backup operations in order to protect the flash device from damage. Resolution (Applies to all b3 and i2 controllers) EcoStruxure Building Operation In EBO, a command has been added that will re-enable backup to flash after the circuit breaker has been tripped (2000 backups) From Workstation, in the object tree, right-click the i2/b3 device. From the context menu select, DEVICE->ENABLE BACKUP TO FLASH     Andover Continuum From CyberStation command line set the ACCStatusBackup system variable of the device to ACCBackupEnable. NOTE: The flash circuit breaker CANNOT be reset from Script/Plain English.  This is by design as it was deemed too risky to allow resetting it programmatically.  A poorly written program could very quickly cause damage to the flash device.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. One way conversion: Conversion of b4920 to b3920 is not reversible, once the b4920 controller has been converted to b3920 device, it cannot be converted back to b4920. Issue A b3920 device has failed in the field and the only available replacement at hand is a b4920 Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b4920 Cause The b4920 is a Continuum BACnet router its hardware is almost identical to that of the b3920 device, the only difference is the Ethernet port in the b4920, which is not populated in the b3920. When a b3920 must be replaced, and the only available replacement is a b4920, use the steps outlined in this article to convert the b4920 to a b3920. Resolution Before starting the procedure, you need the following items: The b4920 device to be converted. The serial number of the b4920 device to be converted. Continuum Cyberstation with b4920 to be converted, configured, and online. (***) A RoamIO2 and BACnet Service Tool A special firmware b4920 application upgrade file provided by Product Support A b3920 bootloader file provided by Product Support Steps to convert b4920 into b3920 Contact Product Support and request the b4920 to b3920 conversion files. You will be provided with an application file (e.g. b4920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd). From Continuum Workstation, take note of the baud rate of the MSTP operating under the b4920 (In Comm1 settings) From Continuum Cyberstation, edit the b4920 controller object and take note of the BACnet Device ID and the controller Serial Number, typically they will be the same but this is not always the case. In the "General" tab, click 'Update OS' and send the Application file provided by PSS. Please note that once the application file has been sent and the controller re-starts, its MSTP will shut down and RoamIO2 is required to re-start the MSTP for operation as a b3920, the reason for this is Continuum uses mac id 0 (zero) for router controllers such as the b4920 and the bCX4040, in Continuum, b3 devices are not allowed to use mac id 0. Disconnect the Ethernet cable from the b4920, the Ethernet port is now unusable. Connect the RoamIO2 directly to the b4920's Service Port then cycle power to the b4920. Start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from b4940 to a b3920 causes the now b3920 device to come up with an unknown baud rate and an invalid (for b3s) mac id 0, so now need to find out the baud rate the converted b3920 is using From the "View" menu, select "RoamIO2 Properties and take note of the MAC ID the RoamIO2 is using   From the 'Tools' menu, select 'Set b3 baud rate' and set it to Baud9600, and click apply    From the 'Tools' menu, select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC ID ( DO NOT ENTER ZERO NOR THE MAC ID IN USE BY ROAMIO2), then click on 'Apply'   If you get the message below, repeat the steps above for the next baud rate... when you have found the correct baud, you will see the message below after setting the MAC ID   Once the baud and MAC id have been set successfully, the device will automatically pop up in the tree, but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right-click on the device, then select 'Update OS' and send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, click 'Done' button to dismiss, select the device, right-click and select 'Cold start device', and click 'Yes' on the confirmation window   You should now be able to commission the converted device as a b3920, either as a new device or as a replacement device, following the steps for replacing a b3 device. (those steps are not in the scope of this procedure) *** b4920 controllers are not easily defaulted to factory settings. If one gets an old b4920 from the shelf, use the steps below to find out the controller's current IP address and ACCNetId which are needed to put the controller online in Continuum. IP ADDRESS Upon start-up the b4920 sends a gratuitous ARP, use Wireshark to connect directly to b4920 controller using a crossover Ethernet cable, restart the controller, and inspect the gratuitous ARP to determine the IP address configured in the b4920 ACCNetID Once you have the IP address, use the attached utility tool to discover the ACCNetID of the b4920. Unzip the attached file and use the Windows Command Line to execute FindEnodeID.exe as seen below  

Issue Error message "Unable to display events. To view or change, go to Text view on the Advanced tab." in a Schedule in Workstation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The error message appears when attempting to view events with a duration of five minutes or less in the graphic view of Schedules in Workstation. Additionally, the message can also occur when the time between two events is five minutes or less.  The screenshot below shows an event with a duration of four minutes that causes the error message to be displayed. Resolution Two potential solutions are available to address this issue: Utilize Webstation: Webstation does not have the same limitations as Workstation. Users can leverage Webstation to view and edit events with a duration of five minutes or less, or where an event starts five minutes or less after another event ends. Switch to Text View: As indicated in the error message, users can switch to the Text view on the Advanced tab to list short-duration events. To do this, navigate to the Advanced tab (1), then click on the Text view button (2) to switch to text view.

Issue An Enterprise Central has two Enterprise Servers, both connected to External Log storage as pictured below. How can the EC access trend logs in both External Log storage locations when it is only connected to one of them? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause It is only possible to specify a connection to one External Log storage location in the EC Resolution When a user needs to access trend data from a specific log located in, for example, an AS-P while the Workstation is connected to the EC, the following process occurs: The EC contacts the specified External Log storage for the log data using the trend log ID. If the trend log ID is not found in the specified External Log storage, the EC then contacts the Enterprise Server (ES) associated with the AS-P to request the log data. The ES connects to the External Log storage specified within it and retrieves the log data using the trend log ID. The ES delivers the log data to the EC, which in turn delivers it to the Workstation for access. This process ensures that the EC effectively manages connectivity to External Log storage systems and retrieves the required trend data for users.

Issue When using mstpcap.exe to capture, it automatically stops after 65535 packets. Similarly, when using Wireshark, it will stop capturing if the dissector encounters an issue. This article provides a solution to continuously capture BACnet MS/TP traffic in a ring buffer and store it as files. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Wireshark Any BACnet MSTP RS-485 network Cause Analyze BACnet traffic via capture files. Resolution Install Wireshark. Ensure TShark is checked when installing options.  Ensure Wireshark is installed with Npcap (default) or WinPCap has been installed by IA Series Workplace Tech. Install mstpcap.exe referencing BACnet MSTP Capture Application. Ensure that mstpcap.exe has been configured for the correct port and baud rate. Here is an example for Command Prompt and PowerShell: # Command Prompt cd "C:\Program Files\Wireshark\extcap" mstpcap.exe com3 38400 # PowerShell cd 'C:\Program Files\Wireshark\extcap' ./mstpcap.exe com3 38400 Run Tshark to determine the interface being used by mstpcap so that one can reference it by number. For this example, we are going to choose 9. COM3 (BACnet MS/TP on COM3). Please change the number below to the number of your interface.  Start Tshark capture by entering the following command, updating as needed. The commands below save Test01.pcap to the Username's desktop. Please store to a location that the user has access to write.  # Command Prompt cd "C:\Program Files\Wireshark" tshark.exe -i 9 -b duration:3600 -b files:72 -w "C:\Users\Username\Desktop\Desktop\Test01.pcap​"​ # PowerShell cd 'C:\Program Files\Wireshark' ./tshark.exe -i 9 -b duration:3600 -b files:72 -w 'C:\Users\Username\Desktop\Desktop\Test01.pcap​' Note: Change  -i 9  to the number of the interface on the capturing machine. Change  -b duration  to time in seconds (3600 is one hour). Change  -b files  to the number of files to cycle through (72 is 3 days of 1-hour captures, 3x24). Change  -w  to write to the location and filename you choose. Change  \Username\  to your Windows User, if you want to save to that user's Desktop Reference: tshark(1) Manual Page (wireshark.org)

Issue Does SHD2/SCD2 have galvanic isolation? Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Cause Galvanic isolation is a principle of isolating functional sections of electrical systems to prevent current flow; no direct conduction path is permitted. Resolution The SHD2XP2A/SCD2XPXAVX does not have galvanic isolation.

Issue ES is connected to a remote server via EWS; when loading a graphic in a web browser or workstation, the values take a long time to read. (a few minutes.) It makes no difference what the settings for polling are configured for. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Every time the graphic is brought up, the ES needs to subscribe to all values from the external EWS server, this is the cause of the delay. Resolution Workaround Solution: Maintaining Active Subscriptions The recommended workaround solution involves maintaining active subscriptions. This can be achieved through the following methods: Persistent Graphic Display: Always keep the graphic displayed on a client. This is crucial as the subscriptions are terminated when the graphic object is closed. By keeping the graphic open, the subscriptions remain active. Watch View Creation: Create a watch view that includes the values displayed in the graphic. This ensures that the values are constantly monitored and updated. As long as a client subscribes to these values, the update process will be expedited when the graphic is launched. This is because the subscriptions remain active, and the values do not need to be re-initialized. However, if there are no active subscriptions to the values, all values must be set up each time the graphic is opened. This can potentially slow down the process. Therefore, maintaining active subscriptions is highly recommended for efficient operation.

  Issue The WebStation menu used to create new calendar dates and values is not visible. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Building Operation Enterprise Server Cause The panel used to display the calendar schedule is incorrectly configured Resolution In Workstation, right-click on Panel and go to Properties, go to Show Toolbars, and choose Yes.    Now when you log in to Webstation, you will see the toolbar including the menu on the top of the calendar in the panel.