Index | Prev | Next

Setting up device tables

The Commission button in the Lon Device Manager sets up a device’s internal tables to a functioning but unbound state. You perform this on any newly-added Lon device except those created by a Quik Learn of a previously managed network, where the initial state of the device is already set to Config Online.
Prerequisites: The network is an unmanaged network. The Lon Device Manager view is open and you have already discovered devices.
  1. Before clicking the Commission button, you can examine the device’s (discovered node’s) internal tables by right-clicking the LonNetwork node in the Nav tree and clicking Views > Lon Utilities Manager.
  2. Select the device from the drop-down list at the bottom of the view.
  3. To return to the Lon Device Manager view, double-click the LonNetwork node in the Nav tree.
  4. Click to select all unconfigured devices, and click the Commission button.
    A progress bar appears at the top of the view, and updates as the Lon Commission job executes.

The job initializes the device domain table as follows:

  1. For a DynamicDevice with which you are using a service pin, the job waits for a service pin message to obtain the node’s Neuron Id, otherwise, it uses the Neuron Id already stored. Then it reads from the device (for example: hosted, two domains, address count, address of snvt self-doc table). These two actions do not occur when commissioning a Local Lon Device.
  2. The job sets the domain index 0 to the Lon network’s working domain.
  3. If the device has two domains, it sets domain index 1 to not-in-use. If the network’s Always In Zero Length Domain property is set to true, and the Lon network’s working domain is not the zero-length domain, the job sets the second domain entry to the zero-length domain.
  4. Next, it configures the Netmgmt Authentication Key and the device’s subnet/node address in all active domains.
  5. Continuing, the commission job sets all entries in the address table to not-in-use.
  6. For DynamicDevices, it sets all entries in nvconfig to unbound selector (0x3FFF - nvIndex). If under LonNetmgmt, it sets VerifyNvDir and checks to ensure that device and database nv’s have matching direction.
  7. If there is a configSrv nv, the job sets it to external.
  8. The commission job updates device data:

    Channel ld: per property under LonNetmgmt.

    Node Priority: per Lon device property.

    Location: per Lon device property.

    Authenticate: per property under LonNetmgmt.

  9. Finally, the commission job sets Node to the state of: Configured, online.

Related Links

  • Device network management (Parent Topic)

    • Index | Prev | Next