Building Automation Knowledge Base

Issue Access Control Spec for Tender Offer which usually comes from the Product Marketing Division Environment I/NET Site with Access Control Cause Bidding a job and requests for Access Control Spec or Specification Requests for: General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Security Management System (SMS) specified For the Access/Security Control Contractor. Typically the SMS provides and explanation and integration for:   • Integrated Access Control • Alarm Monitoring • Integrated Digital Video Management • Interactive Alarm/Facility Graphics Display • Wireless Alarm and Video Transmission • Associated Access Control and Alarm Equipment Control • Multiple Language Operation • Multiple Tenant Operation • Access Initiated and Event Initiated Control  • Elevator Control • Workstation and associated equipment General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Resolution I/NET Seven Access Control Specification (Available in a MSWord format)  

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 Replacement for Satchwell DWT0001 or DWT1701 by the STP660 Immersion Temperature Sensor due to obsolescence. Product Line Field Devices Environment DWT1701 DWT0001 Cause Obsolescence of Satchwell DWT0001 and DWT1701 Immersion Temperature Sensor. Resolution The STP660 Immersion Temperature Sensor is the replacement for the DWT0001 and older DWT1701 The STP660 provides the same functionality as the Satchwell DWT0001 and DWT1701, differing only in its appearance, dimensions and terminal identification. A pocket or well is also required and is sold separately. 9121066000 - Brass 9121060000 - Stainless Steel N.B. In the case of a DWT0001 and only the sensor part is required, then the STP660 will fit into the existing pocket (and adaptor). or In the case of a DWT1701 and the sensor part is only required, then a pocket adaptor 9121058000 is needed.

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

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue Requirements / specifications on cables used in a LonWorks network Environment LonWorks Cable Wire Guide LonMark Cause There are special requirements on cables used for LonWorks networks between Lon devices. Resolution LonMark organisation is recommending cables according to their specification. An example of this is the Belden LonWorks cable guide. Also, Echelon has a Wiring Guideline and Users Guide.

Issue MNL-V1RVx, MNL-V2RVx and MNL-V1RVx-2, MNL-V2RVx-2 differences Environment I/A Series Micronet LON VAV controllers Cause Part number MNL-V1RVx has been replaced with MNL-V1RVx-2 and part number MNL-V2RVx has been replaced with MNL-V2RVx-2.  The datasheet F-26365 indicates the parts as MNL-V1RVx and MNL-V2RVx.  Resolution The MNL-VxRVx and the MNL-VxRVx-2 are functionally the same. The '-2' was added to the part number to indicate an enhancement to the VAV actuator assembly to reduce the operation noise level of the actuator. 

Issue When starting SigmaX, an error is reported, the error is: - This application failed to start because side-by-side-configuration is incorrect. Reinstalling SigmaX does not help. Product Line Satchwell Sigma Software Environment SigmaX Windows 7 Windows 10 Cause SigmaX error when trying to run on a Windows 7 or Windows 10 machine. Resolution Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps: Open an elevated command prompt. Click Start > All Programs > Accessories Right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Type the following command, and then press ENTER: sfc /scannow The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. More Information about SFC scan can be found in this document: http://support.microsoft.com/kb/929833 At the command prompt, type the following command, and then press ENTER: sfc /scannow The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows. Note: Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished. However Microsoft Visual C++ Redistributable may not be installed sfc /scannow will not detect this, the Visual C++ Redistributable will need installing. Please see Error when trying to run SigmaX.exe and RegSigmaX.exe for further information regarding this.

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 After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue Site looking to add some WorkStations with the ability to show Graphics but without the Graphic editor. Not sure which part number to order. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Documentation Resolution V2 or higher, Enterprise Server or Enterprise Central license includes three concurrent client licenses (WebSation or WorkStation). For additional clients, order one or more of the licenses below. These licenses do not include any editors, the WorkStation will show the graphics but will not allow editing, order below part numbers:   If graphic or programming editing is required, you can order professional WorkStation license, which will add extra WorkStation with editors, or order Programming & Graphics Editor licensing, which will add editors to existing WorkStation Standard license.  

Issue There is a need for a single Compatibility Matrix that shows EBO, PME, Energy Expert and relevant software versions all in the same location.   Product Line EcoStruxure Building Operation, Other   Environment EcoStruxure Energy Expert (formerly Power Manager) ETL tool Cause Energy Expert version compatibility information is currently available but is stored in many different places such as release notes and online documentation, rather than one single matrix.   Resolution The full ETL for EBO compatibility matrix is shown in the following table. Energy Expert  PME EBO ETL Integration Utility .NET Framework Power Manager 1.0 7.2.3 1.6.1 3 1.0.14304.2 4.5 Power Manager 1.1 8 1.6.1  1.7.1 4.1 1.0.15306.1 4.5 Power Manager 1.2 8.1 1.6.1  1.7.1  1.8.1 4.3 2.1.16081.1 4.6 Power Manager 1.3 8.2 1.8.1 1.9.x  4.6 2.2.17056.2 4.6 Energy expert 2.0 9 2 5 3.0.18215.3 4.6 Energy expert 3.0 2020 3.0 3.1 6 3.1.19319.1 4.6 Not commercialized  - (n/a) 2021 3.2.3 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2022 4.0.2/2022 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2023 5.0/2023 6 Integrated - (n/a) 4.8   Great care must be taken when choosing the correct version of ETL to use when integrating Energy Expert and EBO, as there are actually two families of ETL in production.  One ETL designed and tested for PME use only and ETL for EBO designed and tested with an EBO Extract Task specifically for integrating the two systems.  (For example, a version of ETL 4.7 exists, but this is not ETL for EBO and therefore does NOT contain an EBO Extract Task, even though it is a valid version of ETL for the Power Community) New PME 2023 now offers EWS Client 1.2 which can be used to transfer data from EBO to PME instead of ETL.  The merits for and against using this new EWS Client rather than ETL are discussed at length in the PME 2023 System Guide

Issue Common card vendors, types and formats commonly used by Continuum Product Line Andover Continuum Environment Continuum HID Indala Corporate 1000 Cause There is a wide range of card formats available. It's necessary to understand the most commonly used options for Continuum. Resolution Credential Card Format H50932 - Schneider Corporate 1000(35) Format A10202 - Andover 37-bit Wiegand Format 4041X (ASP-ANDINF) - Andover 37-bit Indala Format 40045 (ASP-CSI) - CSI Indala Format Indala Reader Format (FP3511A, FP3521A) 10723 (ASP-ANDINF-1L) - Andover 37-bit Indala Format 1009X (ASP-CSI-2L) - CSI Indala Format 10022 (ASP 26-bit Wiegand-1L) - 26-bit Indala Format HID MultiCLASS Reader (9xx Series) 4041X (ASP-ANDINF) - Andover 37-bit Indalat Format For additional  information on other HID formats, see the following article: Which HID card formats are supported by Continuum?

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network Cause A better understanding of the I/NET network architecture and communication components can help to avoid the need to troubleshoot issues later. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others including resistor termination. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN Wiring Specifications are available here as a PDF document. Selecting the link Network Definition CLAN SubLAN downloads and opens the pdf document shown below.

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

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 After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue Using the EGL, EGRL, EGLL5 which are obsolete Environment Vista Cause temperature/resistance data of EGRL, EGRLL, EGRL5 temperature sensors, or customer needs data to calibrate the sensors. Resolution EGL is replaced by the STD100-250 EGRL - STR100 EGLL  (2 thermistors) was not really replaced, as the average temp calc nowadays is done in the controller. The room version was named EGRLL. All these are for the Vista series. For more information regarding sensors, please visit Exchange Extranet.    Click here for the temperature/resistance chart for the old EGL, EGRL, EGLL5 Click here for the original Product and Installation pdf.

Issue To assist locating data sheets if you do not have access to the Schneider Electric BBE and other company storage areas. Product Line Satchwell MicroNet 100 series Environment MicroNet 100 series Controllers, Touchscreens, LCD, Mi and Slink data sheets. Cause To assist customers that do not have access to our internet or partner websites Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN300 Controllers MLi and data sheets for Satchwell MicroNet MN440 Controllers MLi and data sheets for Satchwell MicroNet MN500 Controllers MLi and data sheets for Satchwell MicroNet MN620 Controllers Download all of the above (file size 10.50 MB) The data sheets for MicroNet 50 series controllers ETC. can be downloaded from MicroNet 50 series controller MLi's and Data sheets.

Issue Platform connection using TLS fails. Standard HTTP connection of port 3011 successful. Product Line TAC IA Series. Environment I/A Series Enterprise Server Cause TLS platform connection fails immediately and throws an exception in Workbench. Note that the Niagara Daemon is running and a non-TLS HTTP connection is successful. No station is currently running on the PC. All stations are stopped.   Example exception- SEVERE [08:45:58 02-Sep-20 CDT][wb.shell] Error connecting to platform daemon at localhost: GET /platformInfo javax.baja.naming.UnresolvedException: platformssl: Resolution A possible cause is a zero-byte file size bog file in the Daemon Home 'stations' folder. Check all of the station folders in Daemon Home, searching for any bog file that is zero bytes in size. Look for 'Config.bog.lock' files as one could be orphaned when a station running in the Niagara daemon were to stop unexpectedly, such as the system reboots suddenly or the PC is powered down. Remove all files that are zero bytes in size. Remove any 'Config.bog.lock' files. Test the TLS connection for a successful connection.