Issue
When upgrading a TAC Vista site to EcoStruxure Building Operation (EBO), LonWorks devices may not be discovered during the device discovery process in the AS-P.
Product Line
EcoStruxure Building Operation
Environment
Building Operation Automation Server Premium (AS-P).
Cause
This issue typically occurs when the original TAC Vista database was configured using a third-party network management tool such as LonMaker or NL220. These tools can assign a custom domain ID to the LonWorks network.
- Default Domain ID in TAC Vista:
1/11 - Default Domain ID in EBO:
1/254
If the domain ID used during the initial setup differs from EBO’s default, the AS-P will not detect devices on that domain.
Resolution
- Identify the Current Domain ID
- Use the existing TAC Vista database to determine the domain ID configured on the LonWorks devices.
- Alternatively, use NodeUtil to identify the domain ID. Refer to the article: Finding LON devices under a different domain length with NodeUtil
- Configure a Spare AS-P
- Set the domain ID on a spare AS-P to match the existing domain ID used in the site.
- For guidance, see: How to locate and change the LonWorks domain ID
- Discover Devices
- Use the spare AS-P (now configured with the matching domain ID) to perform device discovery.
- The previously undetected devices should now appear and be accessible.
- Decommission Devices
- In the AS-P, navigate to the Actions menu for each discovered device.
- Select Decommission to revoke the device’s address and stop communication.
- Reintegrate Devices
- After decommissioning, re-add the devices to the LonWorks network.
- They should now be discoverable by an AS-P configured with the standard EBO domain ID (1/254).
