Replacing a device

The Replace action in the Lon Device Manager downloads network management config data to a selected device. You use it when physically replacing a device (you have removed the old device, and replaced it with an identical type device). You may also use this procedure if running a verify report from the Lon Utilities Manager on a device that has generated errors.
Prerequisites: The old device has been removed and the replacement device is installed and ready. The kitLon palette is open.
Replacement can use the service pin method or the direct entry of the new Neuron Id. This component may be useful in appliance scenarios, where you access the system primarily using a browser and Px pages.
Perform the following steps:
  1. Drag the LonReplace component from the kitLon palette to the Lon device (or devices).
  2. Double-click the LonNetwork node in the nav tree.
  3. Select the device to replace in the Database pane and click the Replace button.
The replace job performs these steps:
  1. If you are using a service pin, the job waits for a service pin message to obtain the nodes Neuron Id, otherwise, it uses the Neuron ID already stored.
  2. The job verifies that the new (replacement) device’s Program Id matches the Program Id stored in the existing Lon device.
  3. It initializes the device’s domain table as follows:

    It sets Domain index 0 to the Lon network’s working domain.

    If the device has two domains, it sets domain index 1 to not-in-use.

    If the network’s Always In Zero Length Domainproperty 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.

    It configures the Netmgmt Authentication Key and the device’s subnet/node address in all active domains.

  4. Continuing, it sets all entries in the address table to match the station database.
  5. It sets all entries in nvConfig to match the station database.
  6. It updates configuration device data as follows:

    Channel ld: per property under LonNetmgmt.

    Node Priority: per Lon device property.

    Location: per Lon device property.

    Authenticate: per property under LonNetmgmt.

  7. Finally, the commission job sets Node to the state of: Configured, online.
     NOTE: You can examine a device’s/discovered node’s internal tables using the Lon Utilities Manager