By default, each Lon device has available actions, with right-click menu access from the Nav side bar, LonNetwork wire sheet, Lon device property sheet, or Lon Device Manager (see Figure 42).
Lon device actions include the following:
Similar actions exist for the Local Lon Device, with exception of “Learn Nv” and “Trim.” For more details, see LocalLonDevice actions.
A Ping action attempts communication with device. If successful, the device status is ok. If this fails, the device status is set to down.
Upload reads transient (nvs) and persistent (ncis and cps) data from the device and writes to the station database (Lon device). An Upload dialog box (Figure 43) allows you to select the type of data.
Typically, you leave dialog parameters at defaults (true)—recursive is always recommended. After using and to create a new Lon device (and assigning the device a Lon Xml file), you can use to populate current LonData in the device’s LonComponents (nvs, ncis, cps).
If using Quik Learn, an “Upload Config” option is already included, as shown in Figure 20. This uploads all current LonData into the device’s LonComponents, making another upload unnecessary.
An action is also available at the LonNetwork level—with the same Upload dialog selections as shown in Figure 43. This provides a “global upload” from all Lon devices.
Download writes persistent data (ncis and cps) to the device from values in station database (Lon device). A Download dialog box (Figure 44) allows you to select recursive writes.
Typically, you leave recursive at default (true), to write to all child data items. Use Download to restore nci and cp values to “known good” values, as previously saved in the station.
An action is also available at the LonNetwork level—with the same Download dialog selection as shown in Figure 44. This provides a “global download” to all Lon devices.
Learn Nv builds the Lon device’s child LonComponents as a collection of nvs, ncis, and (if available) cps based on the Lonworks self documentation that resides in the device. See LonComponents for more details. As such, the Lon device will be represented with nvs that are implemented with SNVTs, and ncis and cps that are implemented with SCPTs. Use Learn Nv only if there is no available Lon Xml (lnml) file for a device, or if the device has a programmable (changeable) external interface.
Be aware that if you perform a Learn Nv on any Lon device previously using a Lon Xml file, LonComponent data from any manufacturer-defined type info is removed (lost). Workbench does not allow a Learn Nv if the Lon device has an “Xml File” property that is not
“null.” Instead, a popup error message appears, saying that you must clear the Xml File entry and retry.
Starting in AX-3.3, a Learn Nv can group the device’s LonComponents in one or more LonObject 
containers under the Lon device, by selecting the “Use Lon Objects” option in the Learn Nv popup dialog (Figure 45). See LonObjects for more details.
If you perform a Quik Learn and associated lon<Vendor> modules are not installed on that JACE platform (to supply lnml files), the “Learn Nv routine” is automatically used to build
DynamicDevices, as needed.
Trim can be used to automatically remove a Lon device’s LonComponent nvi and nvo slots that do not have an associated Lon proxy point, or that are not linked or have a Px bind. This can conserve station memory and allows database support for more devices. See LonComponents for details about a device’s LonComponents.
Note that the Trim action is simply a convenience—alternately, you can manually delete individual nvi/nvo LonComponent slots that have no interest. Typically, you would use Trim (or manually delete) only after adding all Lon proxy points and making any LonComponent binds, perhaps before duplicating the Lon device in multiples.
If you perform a Trim, and then later find you need access to deleted nvis and nvos, you can perform an ImportXml command on the device to add back deleted LonComponents.