LON is supported for SmartServer Pi 4.3 and higher, with the exception of LON PL.
...
You can use the SmartServer as a LON remote network interface (RNI) for an application or tool using an IzoT Net Server, OpenLNS Server, or LNS Server. Using the SmartServer as an RNI, you can run your application or tool on a remote computer connected to the SmartServer and its attached LON networks via a LAN connection. You can also use the SmartServer as an RNI for the EnOcean LonScanner Protocol Analyzer to monitor all LON network traffic on one of the SmartServer channels.
If you are using a U70 PL-20 network interface to communicate with LON power line devices, you can optionally enable power line repeating to extend the range of the power line communication. Power line repeating requires power line repeating support in all the power line devices to be provisioned by the SmartServer. When you enable LON power line repeating on a SmartServer, the SmartServer is limited to a single U70 power line interface and you cannot add any additional LON network interfaces. You also cannot use the remote network interfaces (LON RNI ) or LON routers . in the SmartServer. LON PL is not supported for SmartServer Pi.
If you are not using power line repeating, you can add up to four U60 FT interfaces, one U60 TP-1250 interface, and four U70 PL-20 interfaces. To attach more than four USB interfaces to a SmartServer, add a powered USB hub to get additional USB interfaces. Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.
You can manage the network of LON devices using any of the following methods:
...
. If you have more than one U70 PL interface attached, connect each U70 interface to a PL channel isolated from the other PL channels connected to the same SmartServer.
If you install more than one LON network interface, plug in the first interface while the SmartServer is unpowered, and then apply power to the SmartServer. After the SmartServer starts up, plug in any additional U60 or U70 LON networks interfaces. Wait for each network interface to appear in the LON tab of the Configuration page before plugging in the next. This typically takes approximately four seconds per LON interface. This process is only required once per SmartServer. Once completed, you can power cycle the SmartServer with all LON network interfaces attached.
You can manage the network of LON devices using any of the following methods:
- Use the SmartServer to manage the network. This mode of operation is called SmartServer LON device management mode (DMM). This is the default LON management mode.
- Use another tool such as the IzoT Commissioning Tool (CT) to manage the network or allow the LON devices to manage themselves using self-installation. This mode of operation is called SmartServer LON independent management mode (IMM).
...
- A SmartServer internal router is required for each LON network interface you plan to use. Each U60 or U70 that you attach to the SmartServer creates a new internal router from an internal IP-70 channel in the SmartServer to the channel attached to the network interface. If you enable IP-852 routing, the SmartServer creates an IP-852 to IP-70 router. If you are using LON DMM, the SmartServer automatically provisions all the routers. If you are using LON IMM, you must explicitly commission the routers you require from an external network management tool such as the IzoT Commissioning Tool (CT).
- If you are using LON IMM, add a SmartServer IoT device on the SmartServer IP-70 backbone channel. The SmartServer IoT device allows the SmartServer to monitor and control edge devices.
...
The LON Configuration page is shown below.
| Note | ||||
|---|---|---|---|---|
| ||||
When commissioning an IP-852 router, you can either use the IP-852 Router Configuration → Service/Connect button on the LON Configuration page, or you can use IzoT CT to manually enter the IP-852 router's MAC ID that appears on the LON Configuration page. |
...
Using Multiple Network Interfaces
Initial U60 Installation
If you are using a single U60 or U70 network interface, you can attach it to the SmartServer regardless of whether the SmartServer is powered or not.
If you are using LON power line repeating, you cannot use more than one network interface.
If you not using LON power 
SmartServer IoT LON tab
SmartServer Pi LON tab
Using Multiple Network Interfaces
Initial U60 or U70 Installation
If you are using a single U60 or U70 network interface, you can attach it to the SmartServer regardless of whether the SmartServer is powered or not.
If you are using a U70 with LON power line repeating enabled as described in (Optional) Set up LON Power Line Repeating, you cannot use more than one network interface.
If you not using LON power line repeating and you are using multiple network interfaces, after attaching the first network interface, attach the additional interfaces while the SmartServer IoT is powered.
...
Once you have attached your network interfacers and the SmartServer completes their configuration, you can power cycle the SmartServer at any time and your LON network interface configuration will not change.
Reset to Defaults (applies only after
...
network interfaces are installed)
You can clear the contents of the SmartServer database. Alternatively, you can restore your SmartServer to its factory default state.
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.
...
If you are not using LON power line repeating, you can add up to six native LON interfaces and one LON IP-852 interface to a SmartServer.
To add a native LON interface, connect an EnOcean U60 FT DIN, U60 TP-1250 DIN, or U70 PL DIN USB Interface Module using a USB cable connecting one of the USB ports on the SmartServer to the U60 or U70 module.
...
| title | Notes: |
|---|
When more than one U60/U70 is being used, the first LON interface can be plugged in before powering up the SmartServer. Power up the SmartServer before plugging in the remaining U60/U70. You need to wait up to 4 seconds (or until you see the new U60/U70 appear) before plugging in the next U60/U70. This process only needs to be done once during the initial U60/U70 installation. You can then power cycle the SmartServer with the U60/U70s plugged in.
...
repeating, you can add up to six native LON interfaces and one LON IP-852 interface to a SmartServer.
To add a native LON interface, connect an EnOcean U60 FT DIN, U60 TP-1250 DIN, or U70 PL DIN USB Interface Module using a USB cable connecting one of the USB ports on the SmartServer to the U60 or U70 module.
- Select the checkbox for IP-852 Router Configuration.
- Specify the port in the Port field. The default port is 1628 (with SmartServer IoT release 2.8, this default port setting cannot be changed).
After the IP-852 configuration is set, click Update to update the settings on the SmartServer.
Provision Commission the IP-852 router by clicking the Service/Connect button.
Note icon false title Commissioning an IP-852 router using IzoT CT. To commission by Service message, click the Service/Connect button on the LON tab of the Configuration page
, or you can use IzoT CT to manually. To commission manually, enter the IP-852 router's MAC ID that appears on the LON tab of the Configuration page.
Provision each U60 router by clicking the Service/Connect button for the specific U60.
Each SmartServer IoT must have its own IP-70 channel.- A Add a SmartServer IoT device (as shown in the figures below) needs to be added when using built-in SmartServer features (e.g., CMS, alarming, data logging). The SmartServer IoT device is not needed if the SmartServer is only used for IP-852 routing.the IzoT CT drawing for each SmartServer that is used for features other than LON routing or LON RNI.
IP-852 Network with Single SmartServer IoT and Single U60
IP-852 Network with Single SmartServer IoT and Two U60s, an i.LON 600 and an i.LON 700
...
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.
For example, you can initiate discovery and discover 50 devices. Later, you do site maintenance from the SmartServer and make changes to the discovered devices. At the same time, you realize there were some devices that were not powered at the time of the initial discovery. You can then initiate a second discovery that results only in the newly powered up devices that are discovered and added.
...
Once you discover a device using either method, the LON domain for the SmartServer is set. Therefore, whether you specify a LON domain ID or discover a LON domain ID,
...
do not change the LON domain ID once it has been set. To change the LON domain ID, reset the SmartServer databases, select the domain ID assignment method, and then select the new
...
LON domain ID as described in reset the SmartServer databases.
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:
...