Learning Lon devices

An available Quik Learn feature (misspelling intended) populate a new Lon network with the proper device components. In a managed network, Quik Learn preserves the original Lon network management configuration. In an unmanaged network, Quik Learn applies unique and contiguous subnet-node addressing to the learned devices.
Prerequisites: For the best possible results, make sure that any needed Lon modules are installed on the host platform before running Quik Learn.
  1. Double-click the network node.
    The Lon Device Manager view opens.
  2. If you see a split-pane (learn mode), click the Learn Mode tool (Image) to toggle out of learn mode.
  3. You may select devices before clicking the Quik Learn button or click without selecting devices.
    If you clicked Quik Learn with no devices in the database selected, a window asks about previous network management, and whether to learn links, with config upload preselected.Image

    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.

    Image
  4. Do one of the following:
    • For a managed network with no devices selected, leave the top option cleared, and either check (or clear) the bottom options Learn Links: add links to the database and Upload Config: upload ncis and cps, then click OK.
    • For an unmanaged network with no devices selected, check Unmanaged Network: ignore subnet/node conflicts, and Upload Config: upload ncis and cps, then click OK.
    • For any network with devices selected, clicking Cancel aborts the job. Clicking OK initiates the learn job.
    A progress bar appears at the top of the view, and updates as the Lon learn job runs.

    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.

  5. For unmanaged networks, click to select all devices, and click the Commission button.

    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.

  6. To view links and learned bindings, right-click the network node and click Views > Lon Link Manager.
    The Lon Link Manager view opens.
  7. To see a device’s ncis values, right-click the device and select Views > Nc Manager.
The following lists in detail what happens during a Lon learn job when no devices are selected:
  1. A discovery occurs for all nodes on the working domain (only). As each device is discovered:

    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.

  2. Continuing, the Quik Learn job processes the remaining unmatched devices. For each unmatched device it:
    • Attempts to match the programId match (with neuronId=0) with existing device.
    • If no match is possible, the job creates a new DynamicDevice, where it uses the node’s Program Is to find the appropriate Lon Xml file among the host’s locally installed lonvendor modules.
  3. As the job matches or creates each device, it synchronizes the database’s device data with the data read from the physical node.
  4. If learn links were selected, the job configures these data:

    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.

  5. If upload config was selected, for each device the job uploads the values of its ncis and cps.
 NOTE: At this point forward, the station must become the only Lonworks network manager. Otherwise, proper network management cannot be successfully maintained.