Building Automation Knowledge Base

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 For various reasons sometimes it is necessary to clear the error log in the controllers.   NOTE: First generation controllers such as the CX9200 and CX9900 (NetController 1) and Infinet1 devices do not support the error log utility, this article does not apply to those controllers.   Product Line Andover Continuum Environment CyberStation bCX9640 bCX4040 bCX4000 CX9680 ACX5740 ACX5720 All b3 devices All i2 devices Cause Guidelines for clearing the controllers error log in the field. Resolution bCX4040, bCX4000, b3s Error log is cleared by setting the Errors system variable to 0 (zero)   IMPORTANT It s not recommended to set the errors system variable from within a Plain English program, doing so risks damaging the controller's flash memory which has a limited number of write/erase cycles. Only reset the errors system variable to 0 from the command line or from the system variable object editor.   If the Errors system variable has a non zero value all that is required is to reset it to 0   NOTE: In some older version of the firmware, if the Errors system variable is at 0 then it has to be changed to a non zero value before it can be reset to 0 One easy way to generate an error is to create an InfinityProgram that attempts a DIVIDE BY ZERO I.e. Program is AutoStart and FallThru Numeric N n = 1/0   Create the InfinityProgram above in the controller, once the program saves and runs it will be disabled and the Errors system variable will increment by one. Remember to delete the program as it is no longer needed bCX9640 CX9680, ACX5740, ACX5720 Use the controller error log tool to clear the error log.

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you make changes to RSTP the controller MUST be WARM START. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured properly per Configuring RSTP on a Managed Switch for SmartX IP Controllers Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Bridge Priority Considerations Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. First, configure the Root Bridge Switch (closest to the Automation Server) settings. Then, configure the additional Switches in order of increasing Bridge Priority. Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Consult the documentation or contact the vendor or manufacturer to assist with configuration for the items below. Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), each loop's size may be limited based on their site switch network configuration and architecture.  Determined the proper configuration (or disable) for the following features. DHCP snooping Dynamic ARP inspection Denial-of-service (DOS) mitigations BPDU Guard BPDU Filter RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION MUST BE EBO 3.1 or higher which includes ClientAPI support Frontline Fridays Episode 02 - Rapid Spanning Tree Protocol (RSTP) Date: 2022-11-11 Mike Botens posted the following in the thread: RSTP Status TGML dated 2022-11-09 PDF of the presentation Fusion Fridays - Session 07 ​​​​ Date: 2020-05-28 The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. bind Network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Offline controllers that are scattered are NOT an RSTP issue. Check to see if there is a possible DHCP issue by verifying controllers are still at their AUTO-IP address (IP 169.254.nnn.nnnn Subnet Mask 255.255.0.0). RSTP communications issues affect the entire RSTP loop or one contiguous group of controllers. Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, Warm Start, re-enable RSTP Mode, Warm Start, and check again. If Firmware 3.02.01 is installed, please upgrade to 3.02.02. SmartX is now SpaceLogic.

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.

Issue Cannot do a backup to flash on bCX4040. Distribution Properties indicates "The flash for this controller does not need to be backed up." Product Line Andover Continuum Environment bCX4040 Cause ACCStatusBackup is set to ACCBackupInactive when ACCRestartMode is set to ACCWarmStartOnly. This occurred when a bCX9640 was flashed to a bCX4040.  ACCWarmToCool is the default ACCRestartMode for the bCX4040. Resolution Change ACCRestartMode to ACCWarmToCool and then try the backup. For more information on the ACCRestartMode refer to Chapter 5 of the bCX1 Series Controller Technical Reference document # 30-3001-890.

Issue Verification of BBMD broadcast table list Product Line Andover Continuum Environment bCX CyberStation Cause Where is the location of BBMD broadcast table list. Resolution Using a web browser connect to the bCX using the IP address and login. Select the "BBMD Configuration" option to the left.  (If this in not available then BBMD is not enabled). The BBMD Configuration page lists the IP address, broadcast mask, and network port for each BBMD that the bCX knows of. After a successful "Save All To Flash" has been executed from the BBMD Configuration webpage the "Saved" buttons will be checked off. After a "Teach" has been executed from the BBMD Configuration webpage, the Teach Results webpage will be displayed. If there is an entry in the BBMD Configuration webpage that has a "rejected" status on the Teach Results webpage, either continue to troubleshoot until the teach is successful or remove that entry from the BBMD Configuration webpage.

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 Problems adding i2 or b3 controllers to systems and causing the network to go down or devices to not learn on. Product Line Andover Continuum Environment i2 Controller b3 Controller Cause Duplicate ID's,  incorrect baud rates or faulty controller Resolution Infinet and BACnet field controllers have the capability to autobaud and auto correct duplicate ID's on a network. They do this by listening to the network on powerup and determining what Baud Rate and currently operating controller ID's are on the network. If an existing controller is on the network and the newly added controller has the same ID assigned, the new controller will zero out its own ID so as not to cause a network problem with duplicate ID's. Then learning or manually commissioning the controller will give it a unique ID. It is therefore critical that when adding a controller to a network, that the controller is connected to the network before the controller is powered up.  Failure to do so could cause network problems such as duplicate ID's or conflicting baud rates which could bring the network down. If the new controller causes these types of problems it is recommended to power down the suspect controller(s) and re-power them to eliminate these issues.  Run acctrace when the learn is being done and there will be an indication of what is happening.  Send a controller error log to PSS.   If nothing else works even with a clean database then replace the Master and if that works send the controller in to repair.

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 If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it. The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016 in order to use TLS 1.2. A defect/hotifx QC#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS. Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Create a ContinuumDB backup Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Extract the OmsInst.exe from the hotfix zip file and copy the new file to the Continuum folder Do an update/initialized database Start Continuum

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 Customer request of a sample Plain English program to unlock a list of doors by toggling a switch. NOTES Sample program provided here as proof of concept only, and is not intended as a complete solution but rather as general guidelines, significant modifications maybe required to adapt the sample program to an acceptable solution per local site requirements. The sample program as written works with a "maintain position" toggle switch, if site is using a "momentary" switch then the program will need modifications. Resolution Sample PE Program in PE Editor   See attached text file