Cannot see third party LON devices when using the I/A Series Lon Device Manager to find and learn the devices on the LON Network.

Issue

Cannot see third-party LON devices when using the I/A Series Lon Device Manager to find and learn the devices on the LON Network.  The third party devices are known to be defined with a specific Lonworks Domain address.

When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers with specific a Lonworks Domain address, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the third-party device.

Product Line

TAC I/A Series

Environment

I/A Series R2 (Niagara) WorkPlace Pro

UNC 520

Third party LON controllers

Cause

When a third-party network management tool is used to define and configure / 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

Perform the following steps using WorkPlace Pro to configure the LON interface of the UNC and to learn the LON network.

  1. Open the Netmgmt page for the Local Lon Device then set the domain length and domainId to match the domain address of the device.  Apply the changes.  (See example here).
  2. Open the Properties page for the LocalLonDevice and select the Engineering tab.  Set the subnetId to match the subnet address of the devices.  (See example here).
  3. Recommission the Local Lon Device.
  4. Use the Lonworks Device Manager to find and learn the devices on the LON network.