
You use Quik Learn to populate a new Lon network with the proper device components. You can also use it to add new devices to an already configured Lon network, in which case, you would select the Unconfigured network option.
Quik Learn operation differs depending on if you have devices selected or not when you issue the command. If you click Quik Learn with no devices in the database selected, a popup window asks about previous network management, and whether to learn links, with config upload preselected.
For the best possible results, make sure that any needed Lon modules are installed on the host platform before running Quik Learn.
If you clicked Quik Learn with one or more devices in the Database pane selected, a window asks if you wish to learn links.

Learn Links: add links to the database and Upload Config: upload ncis and cps, then click OK.
Unmanaged Network: ignore subnet/node conflicts, and Upload Config: upload ncis and cps, then click OK.
For selected devices, the job verifies Subnet, Node Address, and Domain Id. If they do not match it aborts the job. Then it retrieves device data, including Program Id, Node State, Authenticated, Two Domains. Working domain, and Channel Id. Finally, it uploads Address, nvConfig, and Alias Tables.
When the learn job completes, the Database pane displays the learned Lon devices. All devices in a managed network should appear listed with unique subnet/node addresses.
A progress bar appears at the top of the view, and updates as the Lon Commission job runs. When the commission job completes, all devices should appear listed with a Config Online state, and with unique subnet/node addresses.
If you specified a managed network, the job ignores unconfigured nodes, and checks for duplicate subnet-node address conflicts. If it finds conflicts, it aborts the learn.
Device data is retrieved for each node, including neuronId, programId, nodeState, authenticated, twoDomains, workingDomain, and channelId.
The job attempts to match with the existing device (subnet, node, programId with neuronId=0). If it cannot match the device, it saves device data for the node until all devices are discovered.
Program Is to find the appropriate Lon Xml file among the host’s locally installed lonvendor modules.For each device, Upload Address, nvConfig, and Alias Tables.
For each device it adds links.
It configures Location per the Lon device property.
It configures Authenticate per the property under LonNetmgmt.