Troubleshooting

Discovery is not working even though all my devices are physically connected and configured in the station.

You may need to configure the working domain before can communicate with your devices. If you are unable to discover nodes that are physically connected to the station, they may be configured on a different domain. This involves gaining access to a device by use of its Lonworks Service pin.

Discovery is unable to find the nodes in my network.

The nodes are likely configured on a different domain. If the network was previously managed and you wish to maintain the current network management configuration (addresses, bindings) using Quik Learn. You must change the working domain of the LonNetwork to match.

When commissioning and binding I am getting errors. The commission or bind reports that it failed.

Sometimes, certain Lon devices may process Lon messages more slowly than normal, resulting in errors when you do commissioning or binding operations. To confirm such problems use the Lon Utilities Manager (afterwards) and run a verify report. This report lists inconsistencies between the bindings on the devices and the bindings that the Lon network management determines should exist.

In an example with a Lon network containing such slow responding devices, operation may improve with Lon Comm properties adjusted upwards to:

In this case, it may also be necessary to adjust link descriptors under the Lon Netmgmt container from default values.

No matter what I try, my LonIpNetwork remains in fault.

Your LonIpNetwork may not be licensed.