To drag and drop devices from a lon<Vendor> palette

As noted above, you can simply drag and drop devices from the opened palette of any lon<Vendor> module, as described below.

1. In Workbench, open the Palette side bar, if not already open.

2. Open any of the lon<Vendor> palettes with devices of interest, for example, lonHoneywell.

   Available devices are listed by default names matching the source .lnml file name.

3. Open the target view of the target LonNetwork, or of the target Lon Device Folder (under the LonNetwork). This may be the device manager view or the wire sheet view, for example.

4. Drag a device from the palette into the target view (or if desired, from the palette onto the LonNetwork node in the Nav tree).

   A popup Name dialog appears, in which you can enter a meaningful name.

5. Click OK.

   The device is added to the station database.

   At the time of this document, you should also perform additional steps below if programming a station in a remote JACE, and it does not have the same lon<Vendor> module already installed (as the local module palette that you are copying from). At some future time, these additional steps may not be needed.

6. Right-click the newly-copied device, and on its popup menu select the ImportXml command.

   The ImportXml dialog appears, showing “module://lon<Vendor>/<device>.lnml”, corresponding with the device you just dragged from the palette.

7. Click OK.

   Data is read from the local .lnml file into the device component in the remote station. The device is now ready for offline programming, or if online with the JACE (and LON network), ready for matching with an actual device.

   See To match a Lon device to a previously managed device or To match a Lon device to a discovered unmanaged device.

To add a DynamicDevice

You can add a DynamicDevice using the New button in the Lon Device Manager, as described here.

You can also simply drag and drop a DynamicDevice from the lonworks palette, naming it as you wish. In either case, after adding it, an extra task is required to make it useful. See To import Lon Xml into DynamicDevice.

To add a DynamicDevice using the New device wizard:

1. In the Lon Device Manager, click the New button.

   This brings up the New device wizard dialog.

   • In “Type to Add,” select Dynamic Device.

   • Enter the number of devices to add (default value is 1).

   • Click OK.

2. When the next New dialog appears, edit the name of the component as you wish to see it in the Niagara station.

3. For purposes here, leave all values at defaults and click OK.

   The component is added to the station, listed in the Database pane as type “DynamicDevice.”

   In the New device wizard, alternate “Types to add” may appear beside “Dynamic Device,” for example, “Q7300,” “Xl10 Chc1” and “Xl10 Hyd2.” These are special subclasses of a LonDevice. If you select one of these, its Lon Xml (lnml) file association is already made.

To import Lon Xml into DynamicDevice

1. Right-click the DynamicDevice, and on the popup menu select the ImportXml command.

   The ImportXml dialog appears, showing “null” for the Xml File (if not previously specified).

   (Alternatively, you can also click the folder icon beside the Lon Xml File entry in any device’s Add or Edit dialog, for the File Chooser, and continue with step 3 below.)

2. Click the folder icon for the File Chooser dialog. The File Chooser opens.

3. In the File Chooser, click to navigate to the location of the lnml file needed, for example a “jar’ed” lnml file in a lon<vendor> module jar: (example: My Modules, lonSiebe). Or, another lnml file previously made using the Lon Xml Tool.

4. If selecting a “jar’ed” lnml in the File Chooser, double-click that lon<vendor> jar.

   Its available lnml files are listed by name, for example: Mnlrh2.lnml, Mnlrh3.lnml, and so on. (Each lnml file name corresponds to the known .xif file name for any device.)

5. Click an lnml file, then click Open.

   The File Chooser closes, and the Import Xml dialog shows the selected lnml file.

6. Click OK to import the lnml file into the DynamicDevice component.

   Now, the component lists showing a type other than DynamicDevice, for example, “Mnlrh3.”

   After you do this, you can use the Lon Point Manager under that device to add (offline) proxy points, because data items are now known. See Create Lon proxy points.

To match a Lon device to a previously managed device

If online with the Lon network, you can match a manually added Lon device to a discovered node using the Device Manager’s Match button. This copies address data (learned in the discovered device) into the selected Lon device component. See Lon Device Manager key points.

To match an existing DynamicDevice to a discovered (previously managed) node:

1. If the Discovered node table is empty, perform a Discover. See To discover Lon nodes.

2. Click to select (highlight):

   • One device in the Discovered table.

   • One device in the Database table.

3. Click the drop-down control on the Match button to select the following:

   • Use Net Subnet/Node — This specifies to upload address data from the node.

4. Click Match.

   This brings up the Match dialog. As needed, edit any property required. For specific details, see About Lon devices.

5. Click OK to match the discovered device to the DynamicDevice component.

   The device is removed from the Discovered table, and remains selected in the Database table.

6. Right-click the device, and select ActionsUpload.

   In the popup Upload dialog, check all (recursive, transient, persistent).This retrieves current configuration data from that device.

7. Repeat this process (steps 2 through 6) for each previously-managed device.

8. When all devices are matched, click the Learn Mode tool  to toggle out of learn mode.

9. Click to select (highlight) all the devices just matched.

10. With the matched devices selected, click the Quik Learn  button.

    A popup Learn (links) dialog appears. Click OK.

    A learn links job is launched, where Lon bindings are learned.

11. When the learn links job completes, all devices should appear listed with a “Config Online” state, and with unique subnet/node addresses.

To match a Lon device to a discovered unmanaged device

If online with the Lon network, you can match a manually added Lon device to a discovered, unmanaged node using the Device Manager’s Match button. This copies address data assigned by Workbench into the selected Lon device component. See Lon Device Manager key points.

To match an existing DynamicDevice to a discovered (previously unmanaged) node:

1. If the Discovered node table is empty, perform a Discover. See To discover Lon nodes.

2. Click to select (highlight):

   • One device in the Discovered table.

   • One device in the Database table.

3. Click the drop-down control on the Match button to select the following:

   • Use Db Subnet/Node — This specifies automatic assignment of subnet/node address.

4. Click Match.

   This brings up the Match dialog. As needed, edit any property required. For specific details, see “DynamicDevice properties.”

5. Click OK to match the discovered device to the DynamicDevice component.

   The device is removed from the Discovered table, and remains selected in the Database table.

6. Right-click the device, and select ActionsUpload.

   In the popup Upload dialog, check all (recursive, transient, persistent). This retrieves current configuration data from that device.

7. Repeat this process (steps 2 through 6) for each previously-unmanaged device.

8. 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 occurs. See Commission for more details.

9. When the commission job completes, all devices should appear listed with a “Config Online” state, and with unique subnet/node addresses.