Building Automation Knowledge Base

Issue Controllers underneath a LonWorks Interface are going offline, or values are taking long periods of time to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There could be a number of causes for Lon communication problems including running the communication wire near high voltage, the Lon is shorted out, or loose terminations. Resolution In EcoStruxure Building Operation (EBO) Workstation you can use the Diagnostics tab under each controller to help troubleshoot the communication issue. From here you can monitor the device state, packet errors, transaction timeouts, receive transaction full errors, lost messages, missed messages, last reset case, and the last error logged. To access the Diagnostics tab, select the controller in the System Tree, and click the Variables tab. Then click the Diagnostics tab on the right side of the screen. Here you will find the different device statuses and statistics. The Packet errors can be used to help identify controllers that are having severe problems and may need the communication wire to be physically checked. In order to test the Packet errors, first you will want to clear the current packet error count. You can do this by right clicking on the controller and selecting Advanced -> Clear Status. This will set the packet error count back to zero and now you can click refresh to monitor how fast the errors are building up. If this number is climbing quickly then there may be a physical layer communication problem. If a lot of packet errors is found, the next step in the investigation will be a deeper analysis of the Lon network, using, for example, a Lon Protocol Analyzer (LPA). Refer to the Knowledge Base Article Troubleshooting LON Network Communication.

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 BACnet devices not found but are visible in other third party BACnet applications An update may cause devices to go offline Product Line EcoStruxure Building Operation Environment BACnet IP Network Building Operation EnterpriseServer Building Operation Automation Server (AS, AS-P, AS-B) Cause According to BACnet routing rules, each BACnet Device should have a unique BACnet Instance ID and each BACnet Network should have a unique BACnet Network ID  When a BACnet interface is created on an EBO Server, a BACnet IP network is created with default Network ID of 1. This is a local Network address and in not published on the network, it is therefore not a problem if this is duplicated with other EBO Servers. On many site this will remain at 1 for multiple EBO servers with no problems. If a third party BACnet device uses a published Network ID that is identical to the EBO local Network ID, then it will be ignored. There will be a "Duplicate of local network"  System Alarm and line similar to below in the trace log "nsp.pin.BACnet Device <device name>claims to be router to Network #1234 but that is a local network (BACnetMain)" Resolution If the EBO Server is not finding a BACnet device on a different network type (via BACnet routing like MSTP or virtual IP) then it could be the Network ID is identical to the local EBO Server Network ID. If this is the case, then simply change the EBO local Network ID and retest. BACnet Devices on the same IP network, including those on different IP subnets and linked via BBMD or Foreign Devices are not BACnet routed and therefore will not have this issue (no BACnet Network ID route is involved) Some earlier versions of EBO did not ignore these duplicate Network IDs, thus when up grading some devices could go offline. The workaround would be the same. The correction to the BACnet operation occurred in v1.9.3 and v2.0.2

Issue What is enabled on a Continuum Security Key? Product Line Andover Continuum Environment Continuum Security Key Cause There's a need to know what version of Continuum is enabled on the key. Resolution Note: The Excel method for viewing enabled key features mentioned below no longer works with Windows10 or greater and because of CyberSecurity issues ActiveX controls have been deprecated by Microsoft in favor of more secure web technologies.  This feature will not be updated for Cyberstation.   The supported version of the keys and what options are available on the key can be verified by doing the following using Microsoft Excel on a Workstation with Continuum and the key installed: Open MS Excel Select Insert> Object Select SecurityKeyreader Control and then Ok You will see an object inserted into the spreadsheet with a list of products on the left and options on the right. Example: Serial Number 1016019 Options Number of Points -1 Adv.WebServerEnable Number of Personnel -1 EpiSuiteEnabled Platform Lan(Multi) OPTxtLoggingEnabled Type Prog.Intg. PESourceCntlEnabled Max Version 1.79 Global 1 0 Global 2 0 Global 3 0 Global 4 0 Windows 7 64 bit will not support the MMC.exe option (mentioned below)   Use the command       mmc.exe /32     This will allow the ActiveX snap-in to be added and will work on a 64 bit PC   ActiveX controls in Excel 32 bit are not exposed by default. Use the following Excel spreadsheet (zipped) to read the security key instead. (Excel must be installed and must be on a 32 bit PC(64 bit shows this as blank) Security Key Reader Excel File You may be prompted to enable the ActiveX control Excel 2003 - The application is about to initialize ActiveX controls that might be unsafe. If you trust this document, select Yes and the control will be initialized. Excel 2007/2010 - Notice the Security Warning below the Toolbar                                   Click options                                   Select Enable this content Upgrading a key requires a call to repair (978-975-9464) for a cookie to update the key. In order to install the cookie, you must use the program, CyberKeyWriter2.exe to enter the new key which is on every Cyber CD in the Continuum\bin folder.    Note: Also see Accessing Continuum Security Key information using MMC instead of Excel that describes another method to see this information using MMC. This feature does not work with newer versions of Windows 10

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 How to truncate event tables in Continuum databases. Product Line Andover Continuum Environment Continuum 1.xx SQL 7 SQL 2000 SQL 2005 Cause Stand Alone Continuum Databases use Microsoft MSDE and SQL Express databases which have size limitations. Once these databases reach full capacity they will need to have data truncated from tables to try and reduce the size of the database. Databases should never exceed their size limitations, but if they do, reducing the size of some of the tables will in most cases allow the database to be functional again. Microsoft SQL MSDE database size limit is 2 gig Microsoft SQL Express database size limit is 4 gig Resolution Once logged into the SQL MSDE or SQL Express database, the queries below will reduce the size of the database. As with any database, make sure you backup the database before running any queries. The Usernames and Passwords used below are defaults, your UN/PW may differ. To log into SQL MSDE use the following commandline. osql -Usa -P To log into SQL 2005 Express us the following commandline with your servername sqlcmd -Sput_server_name_here\sqlexpress -Usa -Padminadmin Once logged in you'll be prompted with a 1> at which time you'll change the context of the database you'll be truncating information on. For example if your database name is ContinuumDB you would use the following. 1>Use ContinuumDB 2> Go 1>Now put in one of the queries below 2> type in Go to execute /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 ** To gain back the space after deleting rows SQL Express Right click on Continuumdb>Tasks>Shrink>Database MSDE(osql) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter)   To truncate from the Full SQL server or SQL Express non command line interface, see Removing unwanted entries from an Alarm log, Access Event log, Error log, and Activity log automatically.

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 Controllers may leave their network and join another if a nearby network has an identical "Extended network ID", "Channel" or "PAN ID" Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause Conflict in zigbee networks (Same "Channel", same "PAN ID" or Same "Extended Network ID") Resolution Before deployment, and in order to ensure having a reliable ZigBee network, one has to be aware of the best practices and the limitations of RF signals. Here are some key points to be considered Network Conflicts: Always change your Extended Network ID from the factory default. The best thing is to use a naming convention that makes sense. One suggestion would be to use "SSLLITxx," where "xx" is replaced by the floor the network is on. For example, floor 5 would be "SSLLIT05." If you have multiple networks on the same floor, adding a letter code helps denote them. For example, if there were 2 networks on floor 5, "SSLLI05A" and "SSLLI05B" can be used. Note: In Firmware 2.20.1, the ZigBee Extended Network ID parameter is set by default to a unique string based on the serial number of the MPM. This will eliminate the possibility of having duplicate Extended ID's in a new deployment. For existing installations, the Extended Network ID will remain unchanged if upgrading from a previous version.   Alternating Channels: Alternating channels between network will minimize interference ensure stability. For example, for a 5-story building, alternate between channels 20, 25, 20, 25, 20. Tx Power Upgrade: The default value for "Tx Power" is 5dBm which was designed in order to meet various regulations in certain countries (Europe). However, the "Tx Power" can be increased to 18dBm in other regions of the world (North America) to boost the transmission power of the MPM.   Interference: There are different types of interference when a wireless signal travels through a given space: Physical objects: The number of walls the wireless signal can pass through is determined by the density of the materials used in a building's construction. Concrete and steel walls are difficult for a signal to pass through. These structures will weaken or at times completely prevent wireless signals. Also, the presence of individuals or water will diminish the signal due to the water's ability to absorb the signal. 2.4Ghz Frequency Interference: Cordless Phone - operates on the same frequency as the ZigBee and can cause a significant decrease in performance. Microwave Oven - operates by emitting a very high power signal in the 2.4GHz band. Often emits a very "dirty" signal across the entire 2.4GHz band. Wireless Routers - Wireless Wi-Fi Networks that share the same channel will have a negative effect on ZigBee network performance. Distance: To ensure reliable communications, a suitable distance between two devices has to be calculated before installation. The distance depends on three factors; transmitter power, sensitivity of the receiver and the propagation path loss. The latter is dependent on the number of walls/physical objects obstructing the signal. Locations: The physical location where a router or coordinator is placed also has an impact on the signal. Place the devices in higher ground to reduce the impact of physical objects. Route Redundancy: It is critical that the signal has multiple routes to hop from one device to the other, from one edge of the network to the opposite edge. (See example in images below)

Issue Satchwell "M 1301" Actuator forming part of combined Actuator / 3-port Valve Body assembly requires replacement. Product Line Field Devices Environment Stand alone Satchwell “M 1301” Actuator forming part of combined Actuator / 3-port Valve Body assembly M 1301 Actuator 3-port Valve Body Cause Obsolescence of Satchwell "M 1301" forming part of combined Actuator / 3-port Valve Body assembly. Resolution There is no direct replacement for the "M 1301" Actuator and as a result both the "M 1301" Actuator and the 3-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1301” combined Actuator & 3-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1301” combined Actuator & 3-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. It is possible that the "M 1301" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue GSM modems that can be used with the Remote Alarm Manager. Product Line Satchwell BAS & Sigma,Satchwell MicroNet,TAC Vista Environment Remote Alarm Manager. BAS Sigma Micronet Vista  GSM RAM Siemens TC35i Siemens MC52i Multi-Tech MTCBA-G-F4-GB/IE Cinterion MTX-65+G-V53 Cause Not all GSM modems will allow the full functionality of message acceptance in the Remote Alarm Manager. Resolution The following GSM modems are known to provide the full message acceptance of the Remote Alarm Manager. Siemens TC35i GSM modem terminal. In the Remote Alarm Manager configuration select the C35i driver. This modem is now being replaced be the Cinterion (Siemens) MC52i GSM/GPRS Dual band modem terminal, which has not been tested, but appears to be a direct replacement with added functionality. TC35i GSM/GPRS modem terminal data sheet MC52i GSM/GPRS modem terminal data sheet Multi-Tech MultiModem MTCBA-G-F4-GB/IE modem terminal. In the Remote Alarm Manager configuration select the Brodersen UCM 91/92. This modem is still available, but seems expensive and difficult to source. MultiTech MultiModems MTCBA-G-F4 data sheet Cinterion MTX-65+G-V53 modem terminal.In the Remote Alarm Manager configuration, allow the software to locate the modem and use a generic driver. Cinterion MTX-65+G-V53 modem terminal data sheet   Remote Alarm Manger is no longer a support solution, it is recommended transitioning or upgrading to EcoStruxure Building Operation.

Issue Getting an Error 1001 near the end of the EcoStruxure WebReports Installation Reports not functional from WebReports Product Line EcoStruxure Building Operation Environment Web Reports SQL 2008 R2 Windows Server 2008 Windows Server 2012 Cause This error is caused when the WebReports installer is unable to reach SQL Server Reporting Services to configure the WebReports Interface Resolution After a failed install of WebReports you will need to follow the general workflow:   Clean of the Pieces of the failed install. Use the uninstall process listed in the WebReports Reference Guide or Uninstall Process for Web Reports. Correct all possible causes of the failed install Verify that you can connect to the ES using http from the Reports Server PC Verify that you can connect to http://localhost/Reports_SQLInstanceName  Re-install WebReports. NOTE: You may be able to correct the issue without having to remove and re-install WebReports. Possible Issue: The Microsoft Reporting Service SQL databases are not registered Check through SQL Management Studio that the 2 databases "ReportServer$instance" and "ReportServer$instanceTempDB" are registered. If not, the SBO Web Reports installed have nowhere to place the report pack files. If they are not there, you need to add them through "Reporting Services Configuration Manager". Click "Database" and then "Change Database". Here you can chose to create new databases. Possible Issue: Insufficient User Access Log out of Windows and Log back in using a PC admin account. The account logged in for the installation should have full access to Windows and be a DB admin in the SQL Server. Set the User Account Control Settings to Never notify. Possible Issue: PC Configured as a Domain Server In the Server Manager, check that the IIS Role is configured and that there are no Domain Roles assigned to this PC Possible Issue: Another Application is using a Required SQL function Uninstall any application which use SQL on this PC. (The Enterprise Server does not Use SQL) As a Best Practice, the Reports Server should be installed on its own, dedicated PC. Possible Issue: Incorrect Version of SQL Server or Windows Server Check the Reports Server Specification Sheet for your build and verify that you are on the Correct Version of Windows and SQL. Possible Issue: Secure Connection Level set too high This issue typically also results in not being able to log into http://localhost/Reports_SQLExpress. Log into the Reporting Agent Configuration Manager Application Click on the Report Manager URL on the left-hand column Click on the HTTP URL This will give you the correct URL for your installation of SQL If this fails, browse to C:\ProgramFiles\Microsoft SQL Server\MSRS10_50.SQLEXPRESS\Reporting Services\ReportServer (this may vary based on SQL Installation)   Modify the CONFIG file "rsreportserver" Change the Secure ConnectionLevel to "0" Save the file and attempt to log into http://localhost/Reports_SQLExpress again. For more details on this property see: http://technet.microsoft.com/en-us/library/aa179559(v=sql.80).aspx Possible Issue: .NET Framework is not operating correctly. Download the correct version of .NET framework for your version of EBO (The correct required version can be found on WebHelp Reports Server under EcoStruxure Building Operation Software Requirements) Run the installer in "Repair" mode Possible Issue: The Windows account "appuser" is not created because the default password does not meet password policy requirements Temporarily disable password policy on the server and try reinstalling. For clarification of the use of 'appuser', refer to the following article, Report Server "appuser" clarification 

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

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

Issue 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 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 Working with a 3rd-party lon controller with no existing shadow object available.  Niagara G3 provides the ability to create a shadow object on the jobsite using the Lon Xml Tool. Environment Niagara G3 Cause A shadow object is not available for a specific 3rd-party controller and a dynamic device fails to interface properly.  Resolution The Lon Xml Tool provides the ability to create a Lon Xml file (.lnml) file for a device, using the source .xif file and (if necessary) other resource files, as made available from the device's manufacturer.  Review Appendix A of the Lonworks Integration Guide for Niagara G3.  The Lon Xml Tool is described starting on page A-1.  This section describes the need for custom Lon Xml files as well as an overview of the process and the steps to create one. docLonworks.pdf

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.

Issue Automation Servers go OFFLINE Alarms received about duplicate device name and/or duplicate network identifier. Product Line EcoStruxure Building Operation Environment Enterprise Server, ES Automation Server, AS, AS-P, AS-B BACnet Cause In the BACnet interface duplicate information has been entered for the BACnet IP network for 2 or more Automation Servers. Resolution Make sure the BACnet IP network and broadcast address in the BACnet interface of the ES and all the Automation Servers  are set to a unique value and they match the IP address of the Server (AS, ES) You may have to physically disconnect the units from the network and then connect one at a time in order for Workstation to be able to communicate with the AS and change the configuration of the BACnet IP network.  

Issue Sometimes just looking at the error message you get from e.g. TAC Vista or SmartStruxure when you try to send an email and it fails can lack information. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure WireShark Cause It is not necessarily all SMTP error messages and their explanation that are implemented in the software. Resolution For general information on WireShark usage read Using WireShark to analyse communications on an Ethernet network. If McAfee antivirus with HIPS is installed on the PC, use RawCap to capture the communication, as you will not see traffic originating from your PC online in WireShark. Additional reference for this article: Enhanced SMTP status codes   First of all when working with WireShark logs, it's a good idea to filter and focus the communication type you want to look at. In this case it's SMTP, so simply type smtp in the display filter and hit enter.   The easiest way to isolate a single smtp "conversation" between client and server, is to find one of the packets in the conversation, and in the "Analyze" menu click on "Follow TCP Stream".   This will give you the complete conversation in a separate window.   When you have used "Follow TCP Stream" be sure to set the display filter to "smtp" again when closing the window.   This is what happens if authentication is needed by the SMTP server but the client is not using authentication.   Here is the same attempt to send an email, but this time the client has enabled authentication   A little trick when using authentication is that WireShark can actually decrypt the Base64 encoded username and password. Simply right click on any SMTP packet, click "Protocol Preferences" and click "Decrypt AUTH parameters".   He are the packets decrypted   An error not easily detected by e.g. TAC Vista is error 535 "Incorrect authentication data". As stated in the enhanced status code table linked above, it simply means that either username, password or both is incorrect.   Though the product used may not have support for SSL and TLS, you can encounter SMTP server requiring it. Here is an example of a SMTP requesting SSL     For further info on troubleshooting sending emails from TAC Vista, please read Troubleshooting Sending Emails from a Vista Server.

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

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.