LON is supported for SmartServer Pi 4.3 and higher, with the exception of LON PL.
...
To clear the contents of the SmartServer database, select the Reset Database action from the System Configuration page. You do not have to remove any network interfaces for this action.
To restore the SmartServer to its factory default sate, remove all but one of your LON network interfaces and then select the Restore to Factory action from the System Configuration page. Once the reset is complete, reinstall each network interface that you removed one at a time as explained above.
...
- To create an RNI for an LNS application, select the checkbox for a lon0 interface to the channel to be connected to the IzoT, OpenLNS, or LNS Server. For SmartServer 4.3, disregard the vlon0 settings.
- As needed, you may change the port number of an RNI. Each RNI created on a SmartServer must use a different port number. By default, a lon0 RNI uses port 1628 (with SmartServer IoT release 2.8, this default port setting cannot be changed). If only one lon0 RNI is being enabled, and the LNS server only uses one RNI, the default port number may be used. If you plan on enabling more than one lon0 RNI on the SmartServer, or if your LNS server uses multiple RNIs, then you must change the port numbers so they are all unique. Any port number for each RNI that is not already in use by the SmartServer may be used. For example, you can use sequential port numbers after 1629. To change the port number for an RNI, enter the new port number for the RNI in the Port field.
- The SmartServer can be used with a single LON interface, or with up to eight LON interfaces. If multiple LON interfaces are being used, each interface that you plug in is assigned a new LON interface number, starting with lon0, lon1, lon2, etc. The interface name is associated with the unique ID of the interface so that if you power cycle the SmartServer, the interface numbers stay the same.
- For a single LON interface, any LON interface that you plug in will be assigned to lon0. This option makes it easier to replace a failed LON interface with a new one, without change to the interface name. If a single LON interface is being used, select the Single LONTalk Interface Mode checkbox on the LON configuration page. When this option is enabled, any LON interface that you plug in will be assigned to lon0. This option makes it easier to replace a failed LON interface with a new one, without change to the interface name. To use multiple LON interfaces, clear the Single LONTalk Interface Mode checkbox. To use multiple LON interfaces, clear the Single LONTalk Interface Mode checkbox on the LON configuration page.
- For an EnOcean LonScanner Protocol Analyzer, select the check box for Protocol Analyzer.
- As needed, you may change the port number of an RNI. Each RNI created on a SmartServer must use a different port number. By default, a lon0 RNI uses port 1628 (with SmartServer IoT release 2.8, this default port setting cannot be changed). If only one lon0 RNI is being enabled, and the LNS server only uses one RNI, the default port number may be used. If you plan on enabling more than one lon0 RNI on the SmartServer, or if your LNS server uses multiple RNIs, then you must change the port numbers so they are all unique. Any port number for each RNI that is not already in use by the SmartServer may be used. For example, you can use sequential port numbers after 1629. To change the port number for an RNI, enter the new port number for the RNI in the Port field.
After the RNIs are selected and the port numbers are entered, click Update to update the settings on the SmartServer.
Use the Service/Connect button to send a service message to provision SmartServer IoT interfaces.
...
LON DOMAIN ID DISCOVERY IS AVAILABLE WITH SMARTSERVER 3.4 OR HIGHER.
You can initiate LON domain ID discovery using one of the following methods:
- By specifying the LON domain ID – if the Enable Domain ID Discovery setting on the LON Configuration page is not checked, then you can specify the domain ID length and value. In this case, discovery only happens on the domain ID that is specified.
- By discovering the LON domain ID – if the Enable Domain ID Discovery setting on the LON Configuration page is checked, then you can initiate LON domain ID discovery.
You can manage the site from the SmartServer CMS when discovery is completed in DMM, including adding more devices, replacing devices, reconfiguring devices, creating connections and flows with the devices, and deleting devices.
You can initiate discovery multiple times at the same site. If there are already devices with a configured domain existing in the driver when you initiate discovery, then the discovery will be incremental. An incremental discovery is similar to an incremental export by IzoT Net Export. An incremental discovery uses the domain ID already in use and skips collecting data from previously discovered devices that have not been modified.
...
| Info |
|---|
Once you discover a device using either method, the domain is set. Therefore, whether you specify a LON domain ID or discover a LON domain ID, you should continue to only use that method. If you want to change the method that you are using, then you need to reset the SmartServer databases and select the new method. |
The following steps occur when you initiate LON domain ID discovery:
If there are no LON devices with a configured domain defined in the LON driver and the LON domain configuration method is enabled, then the LON driver will initiate a search for devices in every one byte domain followed by the zero-length domain. Only domains configured in domain index 0 will be considered, and any domains configured in a domain index other than 0 will be skipped. The LON driver will assign itself a subnet and node ID to itself in each domain, assigning high values for each to minimize the possibility of a collision with a medium size LON network. The search will stop in the first domain with a discovered device, and the LON domain ID length and value will be set to the domain. This step is skipped if the LON domain configuration method is not enabled.
The LON driver will discover and store the subnet ID, node ID, group IDs, connection selectors, unique ID, address table and alias table entry usage, and configuration property types and values for each device in the discovered domain if the domain ID configuration method is enabled, or in the configured domain if the domain ID configuration method is configuration method is not enabled. The LON driver is not required to discover connection topology, but is required to discover enough connection information on a discovered device to preserve those connections and support creating new connections that do not break the existing connections. The LON driver will discover both configured and unconfigured devices. Unconfigured devices will appear with blue icons in the CMS. The LON driver will skip hard-offline, soft-offline, and application-less devices in the discovery process.
If the discovered device has an NV with the SNVT_config_src type, the LON driver will update the NV with the CFG_EXTERNAL value, which is one, and reset the device. This disables self-installation, if any, on the device.
The CMS will create a device name and assign a device icon for each discovered device.
The sections that follow describe how to specify the LON domain ID as well as how to discover the LON domain ID.
Specifying the LON Domain ID
...
Discovering the LON Domain ID
The LON domain ID can be discovered by enabling the Enable Domain ID Discovery setting on the LON Configuration page and then initiating discovery using the Discover button (
) on the Devices widget. Discovery can be done in DMM or IMM, and the mode will not be changed.
With this method, you can discover a previously installed system, preserving all existing device configurations. The previously installed system may originally have been installed using any of the following methods:
IzoT Net Server or LNS-based tool such as IzoT CT. These systems may be imported from IzoT Net Export. In some cases, there may no longer be access to the original installation tool or database, so the option to use IzoT Net Export is not available.
Pre-configured devices that are assigned network addresses when they are manufactured.
Self-installed devices that use ISI or another self-installation methodology to assign themselves network addresses at installation time.
To perform LON domain ID discovery, follow the steps below:
...