Building Automation Knowledge Base

Issue "Database error. (Subsystem: LNS, #25)[DB#-2506]" After clicking OK there may be another error: "The global database is not open. (Subsystem: LNS, #64)". When the Echelon LonMaker Design Manager opened, there is nothing in the Database Name field. Product Line TAC Vista Environment LonMaker Vista LNS Cause This error can occur when ports that the LNS Database is trying to use are already being used by other applications. The ports in question are 6001 and 6002. Resolution To check which application is using these ports, use the following DOS command: netstat -bn Once you know which application is using ports 6001 and 6002, shut that application down and relaunch LonMaker or your LNS-based application. For further information refer to Echelon Support article kb481

Issue Device Template for trane Uc800 Product Line TAC Vista Environment Xbuilder Xenta Server MODBUS Cause Device Template Required Resolution Here is a MODBUS device Template for a TRANE UC800

Issue Error message generated when saving a graphic page as a Vista Object. Save Failed. Link contains invalid Vista characters. " ! # % & \ ' ( ) * + , - ; < = > ? and leading/trailing period is not accepted. There is also a limit of 40 chars between each period. Product Line TAC Vista Environment TAC TGML Graphics Editor Vista Workstation Cause A graphic page link or binding has invalid characters or contains more than 40 characters between each period. This error may occur when converting graphic pages from OGC to TGML. Resolution Open graphic page in TAC Graphics Editor. Click on the Links tab at the bottom of the page. In the Links pane there is a list of all links associated with the graphic page. Double click on a link that contains an invalid character (seen above in the error message) or more than 40 characters between periods. (All invalid links must be corrected before the graphic page can be saved) On the right side of the screen in the Properties pane, the name and address of the link can be found here. Remove the invalid characters from both fields. Perform a Save as Vista Object.

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121 and 122, which does not have a D1 input. Product Line TAC Vista Environment Xenta 122 STR-150 Cause The correct terminal for the mode input from the STR-122 is labeled differently on the Xenta 122 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 122 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 9 If you are looking for the wiring diagram for an STR-150 into a Xenta 121 the click here. The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 122. When the Xenta 122 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained is it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue No license is available for Vista Webstation Webstation installation issues ASP.NET Authority issue Product Line TAC Vista Environment Vista Windows 2003 Windows 7 Windows 2008 R2 Cause Sometimes it is not enough to let ASP.NET be run by NetworkServices. The user LocalSystem needs to be used instead. Resolution Windows 2003:  Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Expand application Pools Right click on  "SE ASP.NET v4.0 Classic" and choose Properties. Under "Identity" choose user "LocalSystem" from the Predefined drop list. Click OK and restart webstation. Windows 7: Right click on my Computer and choose "Manage" Go to Services and Application Click on Internet Information Services Click on application pools Right click on  "SE ASP.NET v4.0 Classic" and choose Advanced settings Under "Identity" choose user "LocalSystem" Click ok Restart webstation Windows 2008R2: Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Click Application Pools under the serve Right click on SE ASP.net v4.0 Classic and choose Advanced setting. See attachment IIS manager 1 Click the button beside Identity under the process model. See attachment IIS manager 2 Change the built-in account from networkservice to LocalSystem. Click OK and restart the webserver in Internet Information Services (IIS) Manager. If the problem persists, please see Problems installing Vista Webstation 5.1.5 or newer for additional helpful information.

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.

Issue Double click on a point in Vista. The Edit Properties window should pop up allowing you to view the value, set the Forced-By-Operator setting, and set the forced value. Sometimes double clicking it does not open any window. Product Line TAC Vista Environment Vista Workstation Double or dual monitor Cause The Edit Properties window is popping up off of the screen. Either it was dragged off of the screen accidentally or a second monitor was removed or is not accessible through remote connections. Resolution To display the dialog on the main screen: Double click a point in Vista. Do not click on anything else. The invisible Edit Properties window should be the current window. Press three keystrokes in this order: Alt + Space + X.  This is the Windows hotkey combination to the File menu, and will maximize the current window on the monitor. Possibly try hitting the Alt key twice. This brings the current window to the front. Alt + Space bar, then select Move with the mouse, after a tap of any arrow key, the mouse should lock onto the window allowing you to move it To prevent this from happening in the future: Download the TAC Vista Dialog Position Reset utility. Unzip and double click the executable file to run. Hit the Reset button.

Issue Integration to the Powerlogic CM4000 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic CM4000 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue When logging into TAC Vista Webstation or ScreenMate, error message: Error Information The following errors have occurred. Please correct these errors and/or contact the system administrator. The Vista.Server.WebApps.Access license is missing. This license is required for the Vista Server to allow connections to the Web Applications. Product Line TAC Vista Environment TAC Vista 5.1 Vista Webstation 5.1 Vista ScreenMate 5.1 Vista Standalone package license Cause If the customer purchased the Vista Standalone license package, the Server-to-Server network and ability to be used with Webstation and ScreenMate is disabled. Two licenses are required in order to use Webstation or ScreenMate. Vista Server web function ability license: This license is required for Vista Server to communicate with Vista Webstation or ScreenMate. This license comes with the Vista Server license or some Vista package licenses, and cannot be purchased individually. It should look like something below in your license file: INCREMENT Vista.Server.WebApps.Access  taclic 5.1   Actual Webstation or ScreenMate seats. This license is required for users to log into Webstation or ScreenMate. This license comes with the Vista Enterprise package license or being purchased separately. It should look like something below in your license file: INCREMENT Vista.Webstation taclic 5.1, or INCREMENT Vista.ScreenMate taclic 5.1 Vista Standalone license package does not include the first type of license; therefore, when user log into the Webstation or ScreenMate, license is missing error message is displayed. Resolution Customer has two options to solve this issue: Purchase a full version of  Vista 5.1 Server license. Part number: 000882501 Part name: VISTA 5.1 SERVER   Purchase another package license which includes the full version of Vista Server license and replace it with the Vista standalone license. The standalone license can be rehost to another computer which does not need the web function for future usage. Read additional package license information in the “Software License Packages” document.

Issue It is possible to have a timing issue with the start up of the license server as it relates to the start up of the TACOS.exe.  If TACOS starts before the license server the license server may not be able to read the license file and access to the your Vista products may be denied. Sometime the Workstation or other components can be launched, but all the points are offline. An error "No license for LonWorks communication" will show up. Product Line TAC Vista Environment Vista License Server TACOS.exe Cause TACOS.exe starts before the license server fully started.  When this happens, the License Server may not be able to read the license file properly and access to the your Vista products may be denied. Resolution This tool is a part of TAC Vista Run Mode TACOS Startup Delay is developed to help you set the startup delay for TAC Vista Server, whether it is running as an application or a service. You might find it necessary to delay the startup of TACOS to ensure that the license server or 3rd party software is fully started, before TAC Vista server starts. NOTE: This program allows you to set a delay from 0 to 240 seconds. Click Here: TACOS Startup Delay Utility Download the .zip file by clicking the link above Double click the TACOS Startup Delay 1.0.0.2 Application file When the window pops up you can enter up to 240 seconds into the delay field   Click "Set" button Reboot PC

Issue Integration to the Cummins ModLon 2 gateway with the Xenta 500 / Xenta 700 / Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Cummins ModLon 2 Gateway Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev files as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes. One generator: .dev file Two generators: .dev file   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Replacing an older style 400 I/O with 400A series hardware, the Digital Inputs need changed to reflect the newer style of Universal Input. Product Line TAC Vista Environment Xenta 400 I/O Xenta 421, 422, 451, 452 Xenta 421A, 422A, 451A, 452A LonMaker Replace Cause Hardware changes in the Xenta 400 "A" series I/O will not function as a replacement to a non-"A" series without additional changes to Menta and LonMaker. Resolution Part 1- Changes needed within Menta Open the controller’s application (a Menta file). For ES projects, this file should be stored within C:\TAC\Vista\Applications. Note the I/O module that needs to be replaced. A list of I/O modules can be found under the Options menu on the Device Specification page:   Find and record all input points on the I/O module to be replaced. This list is found in the I/O Configuration Table under the Options menu. For example, write the "Name" and "Bound To" address for every point referencing M2.   After you have noted all of the addresses for input points on the I/O module that will be replaced, you can edit the device type for the I/O module to reflect the new type (421A or 451A). Making this change WILL remove all DI mappings (421: X1-X4) and all thermistor mappings (451: B1-B4) affected by the change in module type.   Double-Click on each DI block from the 421 (X#) or on each AI thermistor input block from the 451 (B#) that you are updating to a 421A or 451A.   The following window will appear. Click the Bind button.   Update Menta FOR 421A POINTS: The controller’s DI points are now UI points. Select the Terminal Ref based on the old mapping: X1-U1, X2-U2, X3-U3, X4-U4 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. FOR 451A POINTS: The controller’s thermistor inputs (B#) are now additional Universal Inputs. Select the Terminal Ref based on the old mapping: B1-U5, B2-U6, B3-U7, B4-U8 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. **Repeat step 7 for all affected points on the I/O module you’ve updated. Repeat steps 2-7 for every I/O module that needs to be replaced by a 421A or a 451A. PART II - Integration Within LonMaker locate the controllers that you want to change out for a 421A or 451A   Right click on them one by one, a click "Delete."   Open the Vista System Plug-In. Right click on the controller in which you want to change the .MTA application. Click "Configure."   Click "Browse," and locate the updated .MTA file you saved   Click "NO" when asked if you want to remove the devices   Click "Add and Match"   Click "Apply"   Re-Synchronize LonMaker   Your controllers should now be 421As or 451As

Issue The device is applicationless, or is not associated with a program record. (Subsystem:  NS, #5) The target device does not have a valid application loaded. To correct this problem, right-click on the device and select the "Load" option. Then, if necessary, repeat this operation. The device was discovered to be applicationless, or not associated with a program. If you encounter this error, load the application into the device. For host-based nodes, ensure that the host application is running Product Line Other, TAC Vista Environment LNS LonMaker Vista NL220 Cause Interrupting a download can cause the download to fail and render the controller applicationless.  Also, a corrupt Menta file can sometimes successfully download, but cause the controller to go into an applicationless state. Resolution An application must be downloaded through Menta while directly connected to the controller through the RS-232 serial port.  A blank Menta file with just one PVR is sufficient to restore an application to the controller and allow it to be downloaded; however, downloading the actual Menta file is better because it can expose parsing errors in the Menta file that need to be fixed before downloading it through the System Plug-in again. In some cases, an attempt to direct download can not establish communications to the controller and "timeout". In this event, download a new .mot file to the system using the Download Wizard. Instructions are located in Instructions on how to download an .MOT file into a Xenta Programmable controller. If the Download Wizard  is not able to establish communications with the device, the program should first be cleared using a Xenta Hardware Reset Tool. You can make one by following the instructions located in Xenta Controller Will Not Download / How to Clear the Xenta Application. If the Xenta firmware is older than 3.61, the method to clear the Xenta application is to power cycle the controller 10 consecutive times.

Issue When trying to log into Workstation you get "Access is denied". Environment Vista Workstation Windows 10 (not supported) Cause First verify that the licensing is installed and working properly on the machine. If running Vista on a Windows 10 machine and the message "Access is denied" still appears when logging in to Workstation then there may have been Windows updates applied to the PC causing the issue. Microsoft has identified an issue with their updates and have plans to correct them in future updates.  Note: Windows 10 is not a supported operating system for TAC Vista.  Resolution If using Windows 10 with TAC Vista, then check to make sure that the following updates have not been installed (updates depend on the Windows 10 build being used).  If one of these builds have been identified then remove the Windows Update and restart the PC. After the reboot, the operator should now be able to log in to Workstation.   Windows 10 1709: KB4056892 Windows 10 1703: KB4056891 Windows 10 1607: KB4056890 Windows 10 1511: KB4056888 Windows 10 1507: KB4056893   Note: There has been a couple of instances where the Windows Upload and blocked access on a Window 8 PC as well.  If the same error is seen in Windows 8 then check for recent Windows updates. Click Here if you are having issues with the updates coming back.

Issue After rebooting the PC, TAC Vista Server (TACOS) doesn't get a license. You need to restart TACOS after each reboot to get a license. Product Line TAC Vista Environment TAC Vista License Server TAC Vista Server Cause TAC Vista Server (TACOS) starts up before the license system is ready to serve licenses, and therefore everything is offline until you restart TACOS. Resolution Download these tools TAC Vista Run Mode TACLicenseServer Settings (only for TAC Vista 5.1.8 and later) First of all, make sure that you have a system that is working normally and has the appropriate default settings. For more information, watch this video on YouTube Make the following setting in TACLicenseServer Settings [1] Set the startup type to "Automatic" and the taclic port to 2170 [2] Click the "License Setup" button, and write the name or IP address of the local PC. Don't use "localhost" or 127.0.0.1 but the actual name or IP.   [3] Click the "License Files" button, and check that only valid license file(s) is present in the license files folder - no other files can be in this folder. [4] Start the license server Make the following setting in TAC Vista Run Mode [1] Enter the username and password of a user with local administrator rights that have at some point been logged in on the PC. LocalSystem can be used, but it is not recommended. [2] Set TACOS to run as a service [3] In "Service Tools" set the service to start type "Automatic Delayed" [4] Start the service Now reboot the PC If TACOS still doesn't get a license after a reboot, try making this additional setting in TAC Vista Run Mode [1] Stop the service [2] Make the service depend on the license server, and also the Loytec driver if it is used in the system. Now reboot the PC If TACOS still doesn't get a license after a reboot, try adding this environment variable to Windows [1] Open the properties for the computer (Click the Windows start button, right-click "Computer", click "Properties") [2] Click on "Advanced system settings" [3] Add a new system variable called "TCP_NODELAY" and give it the value 1 Now reboot the PC If TACOS still doesn't get a license after a reboot, contact Product Support Services and reference this article Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode Now reboot the PC If TACOS still doesn't get a license try making this additional setting in TAC Vista Run Mode

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 Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

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

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue Need the UL Listings for Xenta Product Line Product Line TAC IA Series, TAC INET, TAC Vista Environment Xenta Cause UL Listings for Xenta Product Line Resolution Go to Exchange Online and log in Search for "TAC Vista UL Listings" (Example, Click Here) You can find more information in Xenta Hardware UL 864 Listing.