Building Automation Knowledge Base

Issue Ports are required to be open for I/NET to communicate Need to know the UDP TCP/IP port settings for I/NET. File Equalization failure or NPR devices not coming online Some links (NPRs) are showing offline and can not be connected too, while others work fine. Product Line TAC INET Environment I/NET NPR NPR-527 Cause A Firewall may be blocking ports required for File Equalization and I/NET communication to occur. Resolution You will need to work with the IT department to verify these settings. I/NET communications occurs through port 50069. When using File Equalization you will also need to ensure that ports 1433 and 1434 are open as these are used by SQL. Integral DVR communicates to I/NET on port 18772 For systems with 527 devices or other Xenta servers, please review Ports used by TAC Vista System.

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue Where can I find datasheets, install guides and other documentation on the HID SmartID, iClass, HID Proximity and Indala Proximity cards and readers? Product Line Andover Continuum, Field Devices, TAC INET Environment Electronic Access Control cards and readers for Continuum and I/Net products. Cause Additional product information from HID may be required that is not available on Schneider Electric's own websites. Resolution Schneider Electric supply a subset of the full HID range of cards and readers and these are detailed in the Electronic Access Control Catalogue or see How to determine the part number for the card format required for part number information. For HID product information this can be directly downloaded from the HID Global website. This contains  datasheets, installation guides, application notes, feature lists, brochures and other documentation. HID also have a "Knowledge Center" website that allows you to search for product information and help: HID Knowledge Base. Information on the specific ranges can be obtained from the following links: SmartID: SmartID Cards iClass: iClass Readers iClass SE Readers iClass Cards HID Prox: HID Proximity Readers HID Proximity Cards Indala Prox: Indala Proximity Readers Indala Proximity Cards

Issue Alarms stops coming into Vista from Xenta 280/300/401 in the Lonworks network under a Xenta 913 or a Xenta 701. Xenta 280/300/401 controller goes offline/online in Vista. Unable to disable an alarm from a Xenta 280/300/401 that are under a Xenta 913 running as Xenta Server in Vista. Product Line TAC Vista Environment TAC Vista TAC Xenta 913 TAC Xenta 701 TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 TAC Xenta 281 TAC Xenta 282 TAC Xenta 283 Cause There is no support for adding Xenta 280/300/401 to the Lonworks network under a Xenta 913/Xenta 701 running as Xenta Servers in Vista (even though if it is possible to do it in the software). Resolution Use a different Xenta Server that supports adding programmable Xenta controllers in the Lonworks network. Please see the table in chapter 1.1 of the TAC Xenta Server - Networks Technical Manual or Xenta Server version 5.1.5 and after Major Features.

Issue Gets error message "GCM Not responding" when he attempts to make a connection to a device on the ASD bus under the UNC. Product Line TAC IA Series Environment I/A Series R2 UNC I/A Series R2 TunnelAX jar file, version 2.301.534a or later I/A Series ibsASD jar file, version 2.301.534a or later I/A Series G3 Serial Tunnel 2.0 Client Cause Misconfiguration of tunnel name Resolution Before attempting to configure the AX Tunneling, verify that the correct versions of the R2tunnelAX and ibsAsd jar files have been installed as documented in How to install an I/A Series R2 JAR File. Tunnel Name in AX Tunnel Client must match the Tunnel Instance name in the ASD Service. When you add the AxSerialTunnel to the ibsAsdService, the identifier is automatically assigned based on the port defined in the communications configuration of the IbsAsdService itself.  This name is displayed under the Status tab of the AxSerialTunnel: Figure-1 When configuring the "Niagara AX Serial Tunnel 2.0", the following window is displayed. Figure-2 The tunnel name (See Figure 2) entered in this window must match the port identifier shown in the AxSerial Tunnel definition (See Figure 1).  If these identifiers do not match, the Ax Serial Tunnel Client will not be able to connect to the tunnel in the I/A Series R2 station. NOTE: When installing the I/A Series G3 Serial Tunnel 2.0 Client, no control panel applet is created as with the earlier version of the I/A Series R2 Serial Tunnel Client.   To configure the I/A Series G3 Serial Tunnel 2.0 Client,  run the program C:\niagara\VserAx\vseraxConfig.exe.  If you need to frequently reconfigure this client, you can create a Window Start Menu shortcut or Desktop shortcut pointing to this file.

Issue Managing the address table in a Lonworks device Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment I/A Series MNL TAC Xenta Third-party LON devices Building Operation Automation Server Cause A LonWorks device contains an Address Table which will hold a maximum of 15 addresses. Once this table is full, all bindings will only be able to use the broadcast setting which is not desirable. A Xenta 200,300 or 400 controller will have its first 2 address tables used with TAG 0 and TAG 1 binding. This leaves only 13 addresses for user bindings not the 15 addresses like other LonWorks devices. Resolution ​When you create a binding in LonWorks, you decide its behavior by selecting a binding profile. You either select a binding profile, or you use the default profile. There are basically three types of binding profiles: Acknowledged profiles Unacknowledged profiles Broadcast profiles Using an Acknowledged profile will consume one of the 15 available address table addresses on both the sending and the receiving device. The Unacknowledged profiles will only use one Address on the sending device's address table. Broadcast binds do not use an address but are not recommended. Use an acknowledged binding profile when the sending device should receive an acknowledgment from the receiving device indicating that the value of the bound variable was successfully sent. Binding profile Transmit timer Retry count Acknowledged Profile 96 ms 3 Acknowledged, Tx tmr 256, 3 retries 256 ms 3 Acknowledged, Tx tmr 256, 5 retries 256 ms 5 Acknowledged, Tx tmr 1024, 5 retries 1024 ms 5 Be careful of creating large, acknowledged fan-out bindings because they generate a lot of traffic, especially if the device of one of the recipients is offline.  Use an unacknowledged binding profile when the sending device should not receive an acknowledgment from the receiving device. Use this type when the value being sent is not critical and is of low importance to the control logic. Binding profile Repeat timer Repeat count Unacknowledged Profile   0 Unacknowledged Repeated Profile 48 ms 3 Unacknowledged Repeated, 5 repeats 48 ms 5 Use a broadcast profile when you do not want to use up an entry in the address table. The device address table has 15 available entries for bindings but the first entry is a reserved broadcast entry that all broadcast bindings can share. Binding profile Repeat timer Repeat count Broadcast Profile   0 Broadcast Profile, 5 repeats 48 ms 5 If no binding profile is selected, a default profile is used: Point-to-point bindings use the Acknowledged profile as default. Fan-out bindings use the Unacknowledged Repeated profile as default. Building Operation uses the broadcast profile as default when the device address table has run out of entries. If a point-to-point binding is changed to a fan-out binding, the binding profile is automatically updated to an Unacknowledged Repeated profile. If a fan-out binding is changed to a point-to-point binding, the binding profile is automatically updated to an Acknowledged profile.  This and other information about lon bindings is available on the online help guide Using a Lon Binding in StruxureWare Building Operation More information on the different tables used by each LON device

Issue Automation Server CPU usage goes between 80-100% even with few programs, trends or alarms. Product Line EcoStruxure Building Operation Environment AS Automation Server Cause Cause 1: BACnet into AS uses a lot of resources Cause 2: The AS has bindings from a point to a variety of places Also check out the AS CPU and Memory Loading Quick-Help video on the Exchange. Resolution Example Resolutions in order: The issue described is Functions as Design in StruxureWare Building Operation. The AS results with high CPU percentage with just one point from BACnet interface loaded; however, it had no effect on AS performance. Check the propagation of values. An example would be a Space Temperature which is required by the field bus, the BACnet interface, LON interface, etc. Make sure to properly disseminate this value so to avoid overloading the CPU.

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 1. Cyberstation PC Windows Application Event Logs showing SQL errors about being unable to allocate space for each of the event tables. Similar to the below errors. Could not allocate space for object 'dbo.AlarmEvent'.'PK_AlarmEvent' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Could not allocate space for object 'dbo.ExtendedLogReservation'.'IDX_EXTENDEDLOGRESERVATION' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 2. Controllers are online but unable to modify existing objects or create new ones. In addition; all events were not being logged to the database. This was seen by reviewing the AlarmEvent, ActivityEvent, AccessEvent, AlarmEvent, and ExtendedLog tables not having any new events being recorded at all. reviewing the distribution properties after performing tasks in Continuum showed no entries at all. Normally, user events initiated from the Workstation are shown in the distribution properties window as they occur. Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Cause 1. One of the Database files is set to not grow with Autogrowth set to none. This stops any new data from being able to be entered into the database. One example of this is when the ContinuumDev file was modified by the end-user to inhibit its growth by changing this setting to none. Check all of the following databases files (both the DEV and LOG file) to ensure that they are all set to either autogrowth or to an adequate restricted value so that they are able to write new entries. ContinuumDB MSDB TempDB   2. The disk where the database resides does not have enough available disk space. Resolution 1. Change this database file growth setting to "by 10MB, unrestricted growth" or to an adequate restricted value. Use SQL Server Management Studio Express, see Move / Backup / Restore a database on a Single User SQL2005 Express system on where to get this if it is not already installed on your SQL Server. It is highly recommended to backup the ContinuumDB before attempting any changes to the database, steps on how to do this are in the above article. Start up SQL Server Management Studio, or in my example, Management Studio Express. Log in with your SQL SA password or windows administrator. Expand the server tree, expand the Databases tree. Right-click on ContinuumDB and select "Properties" from the menu; this will show the Database Properties window. Select the Files tab on the RH side of this window and you are now where you need to be to check the Autogrowth setting.   2. If the problem is due to disk out of space your options are; a) Make room on the disk, b) Shrink the ContinuumDB,  c) Install a larger disk in the machine.

Issue What is the process for converting a Continuum Single User system to a Continuum LAN system. Product Line Andover Continuum Environment Continuum CyberStation ContinuumDB SQL Cause Site wants to upgrade from Continuum Single User system to a Continuum LAN System. Resolution PRELIMINARY WORK Order Continuum Key Upgrades from all Continuum CyberStation workstations and WebClient Servers. Coordinate with customers IT department Order all TCP/IP node addresses Coordinate the purchase and installation of all software Order all necessary domain accounts Make sure all domain accounts have sufficient permissions to support the installed systems. PREPARE THE NEW CONTINUUM DATABASE ON SQL SERVER Set up your server and install SQL Server 2005 or 2008. SQL must be configured with the proper collation sequence.  (See CyberStation SQL collation) SQL must allow Name Pipes (See After installing Continuum 1.93 LAN, failure to initialize a new database) Install CyberStation on a service Laptop or PC . Disable all virus protection software Disable all spyware software Disable all firewall software. Install Continuum CyberStation Run Database Initialization on service laptop Create new Continuum database..  NOTE: The new database should be given a name that differs from the existing database. Create the service Laptop workstation with a unique Device ID and Network ID. Launch Continuum Logon and verify that Continuum appears to be running normally. MOVE FILES FROM EXISTING SU WORKSTATION TO THE SQL 2008 SERVER Backup PinFiles on original stand alone Cyberstation and move them to New Graphics Files folder on the new database server. Backup Background image files on original stand alone Cyberstation and move them to the background image files folder under New Graphics Files on the new database server. Backup the existing database and move it to the backup folder under SQL on the new Database server. Restore backup to Continuum database in SQL on the new database server.. Shut down all the Cyberstation workstations that are attached to the old database. Change DB Owner Run query on new Continuum database Enter the text SP_ChangeDBOwner Andover97 Execute this query.   Query should return Success. Run Database initialization on the service CyberStation and update the new SQL 2008 Continuum database. Launch CyberStation on the service laptop and verify that the system is fully functional. Shut down service laptop. CONNECT EXISTING WORKSTION TO THE NEW DATABASE SERVER Startup Existing CyberStation PC Launch Database Initialization Under Server, Update the new Continuum database with the same information entered via the service laptop..  Under Workstation update the server information and apply. Launch Continuum. Configure Graphic File Location From Start Programs Continuum, run Pinpoint Under the View menu select Options. Enter the path on the new Continuum database server for the Graphic (Pin Files) Enter the path on the new Continuum database server for the Image files Enter the path on the new Continuum database server for the Background files Select Check and verify that no errors appear (Red X) Ideally uninstall SQL Express or MSDE or at least stop the service from running. Delete the Windows Scheduled tasks: CS_Distn, CS_Hrly, CS_ Minute as these are now performed by Jobs on the SQL server. Test all Continuum functionality. Setup a scheduled automatic db backup routine in SQL. Setup a scheduled trend log truncation routine in SQL.

Issue An error occurred while installing DSS: MSDTC 2 Product Line TAC Vista Environment DSS Installation MSDTC Cause Users that get the following error message when installing Vista ‘Error occurred when installing DSS’ can be caused by the MSDTC (Distributed Transaction Coordinator) not being able to start. In the service list Distributed Transaction Coordinator (MSDTC) is not started and it fails when you try to start it. Resolution Check the windows event log. If you see the following error events logged in the Application log:  Event Type: Error Event Source: MSDTC Event Category: LOG Event ID: 4163 Description: MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file. Event Type: Error Event Source: MSDTC Event Category: TM Event ID: 4185 Description: MS DTC Transaction Manager start failed. LogInit returned error 0x5. Follow the steps in http://support.microsoft.com/kb/916926 to fix the problem. For other possible causes for this problem see: An error occurred while installing DSS: MSDTC An error occurred while installing DSS: The account already exists An error occurred while installing DSS:COM+ installation corrupt An error occurred while installing DSS: Cannot Start Service

Issue MESSAGE [08:29:10 31-May-13 CDT][sys] *** Station Started (203ms) [1919ms total] *** niagara>MESSAGE [08:29:12 31-May-13 CDT][history.db] Starting async warmup of history config index... MESSAGE [08:29:12 31-May-13 CDT][history.db] Async history config index warmup completed in 15 ms. ERROR [08:29:16 31-May-13 CDT][web.server] HTTP Server failed to bind to port. Address already in use: JVM_Bind ERROR [08:29:21 31-May-13 CDT][web.server] HTTP Server failed to bind to port. Address already in use: JVM_Bind Product Line TAC IA Series Environment I/A Series G3 Enterprise Server, all versions Cause Another service on the pc is using port 80, conflicting with the Enterprise Server. For example, Skype will use port 80 as an alternative unless you uncheck the box in Skype options. As a second example, another Niagara station may be running on the same computer. See Changing the HTTP, HTTPS, or TCP ports of the Enterprise Server for a similar port conflict issue with SmartStruxure. Resolution In the Skype menu > Tools > Options > Advanced > Connection, uncheck the box for "Use port 80 and 443 as alternatives for incoming connections"

Issue "No license for LonWorks communication" - LonMaker Recovery Folder Product Line TAC Vista Environment Echelon LonMaker Cause Vista software detects the installation of commissioning tool for the LonWorks communication license. At times LonMaker will improperly shut down and store bad data in the Lm\Db\Database name\recovery folder. This invalid data will stop the LNS server from running properly. Resolution If using LonMaker and "No License for LonWorks Communication" error message appears: Shut down Vista software Open the drawing in LonMaker If it requests the contents of the recovery folder be removed, follow those instructions. Once the contents of the recovery folder are removed, open the drawing in LonMaker Launch Vista Server, and the license problem should be gone.  Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Lost the password to login to the different media I/NET, SQL, SAV Environment I/NET site Cause Lost Password Resolution I/NET login: Please send the database with version number and SQL version used to ProductSupport.BMS@schneider-electric.com. SQL login: Please see Loading I/NET on a PC that has full SQL and the Password is not known and Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. DCU login: Please see Recover an I/NET Controller's DCU Password.

Issue After the TAC Menta file has been downloaded all other IO modules operated normally but one IO module will not come online Product Line TAC Vista Environment Xenta401 XENTA301 XENTA281 Cause If the IO module that will not come online has IO points set up in it, then chances are one of the points is set up incorrectly. For example, it may be referencing a Universal Input, but in an Analog Output only IO controller. This is typically caused by changing the IO module from its original type. The TAC Menta was not updated correctly after the change and an analog input was left referencing an analog output in the new controller. Resolution Check all the points in the affected controller for correct and valid references. Once corrected download the controller. TAC Xenta I/O modules do not come online after a download from System Plug-In is a related article.

Issue Experiencing issues with I/O modules that may include: Backplane failure causing modules to assume wrong module ID Input filtering problems on RTD modules Stability due to electrical noise Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation StruxureWare Building Operation Automation Server I/O Modules Cause The latest I/O module firmware version will correct known issues while also ensuring that the system is up to date and compliant. Resolution The latest I/O module firmware can be located on the Exchange by searching for I/O Module firmware. Each firmware download zip file will contain a ReadMe file that explains what was corrected in that version.  Refer to Upgrading SmartStruxure IO Module Firmware for the procedure to upgrade the I/O module firmware. 

Issue Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents

Issue The status of a Forced BACnet value is not reflected in a Graphic or the Watch Window. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause This is functioning as designed. It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. Resolution It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. For a workaround using a PE Script program to show the forced icon for a BACnet value see How to show the forced icon for a BACnet value in a Graphic. In EBO version 3.0.1 and later this issue only occurs on internal BACnet points, points which are located in the Application folder under the BACnet interface for the SmartX server.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment WorkPlace Commissioning Tool Cause There could be a Niagara R2 station running on the computer configured for BACnet/IP. Since the Niagara station also uses UDP port 47808 by default, the Niagara service prevented WorkPlace Commissioning Tool from "binding" to the UDP port. Resolution There are two ways to resolve this issue: Disable the Niagara service when using the WorkPlace Commissioning Tool In Workplace Pro, stop the station that has the BACnet/IP service enabled, and configure it so that it does not auto-start. NOTE: If this procedure does not correct the issue and the WorkPlace Tech Tool software is being run on the Windows 7 operating system, refer to WorkPlace Commissioning Tool Windows 7: "A critical error occurred in the communication server rtmonitor.exe" for information on how to correct what may be a program security settings issue.

Issue "No license for LonWorks communication" error when using a non LE dongle. Product Line TAC Vista Environment Non LE dongle (LE= Limited Edition which has no Webstation or multiserver functionality) Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause One would normally expect this error message when trying to run Webstation server with a Vista LE license. If the system is not using a Vista LE dongle/license, but the error "No license for LonWorks communication" appears, then the problem may be in the Privilege Server service.   Resolution Shut down Vista Server and Workstation. Right click on My Computer and select Manage. Expand Services and Applications. Click on Services. Find the service Privilege Win32 Server. Right click on the service and select Stop. Right click on the service once more and select Start. Restart Vista Server and Workstation and verify that the error went away. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.