...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
LON is
...
supported for SmartServer Pi
...
4.
...
3 and higher, with the exception of LON PL.
| Info |
|---|
For SmartServer 4.1 and prior, see (Optional) Add a LON Interface (Release 4.1 and Prior). |
...
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 network interfaces. You also cannot use the remote network interfaces (RNI) or routers. 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.
...
- 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.
IzoT CT IP-852 LonWorks Network using Two SmartServer IoTs
...
| 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. |
...
SmartServer IoT LON tab
SmartServer IoT Pi tab
Using Multiple Network Interfaces
...
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.
See the Resetting the SmartServer IoT to Factory Defaults section for more information about these reset operations using the System Configuration page.
...
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
...
- Log into the SmartServer Configuration page as described in Accessing the SmartServer IoT Configuration Page.
Click the LON tab.
Set the domain length and ID in the Domain Length (bytes) and Domain ID (hex) boxes.
You can set the domain length to 1 or 3 bytes, and you can set the domain ID to a hex value with two characters for a 1-byte domain or six characters for a 6-byte domain. If you select a 3-byte domain, select a 3-byte value as follows: - The last byte must be 00.
- The first byte cannot be:
- 00 - the network IP addresses are reserved.
- 0A - the 10/8 network IP address block is reserved for one-byte domains.
- 7F - the 127/8 network IP address block is reserved for the Internet host loopback.
- 2C - the 44/8 network IP address block is reserved for one-byte domains.
- The first two bytes cannot be:
- C0A8 - the 192.168/16 network IP address block is reserved for the zero-length domain.
- A9FE - the 169.254/16 network IP address block is reserved for the link local purpose.
ExC0xx (where x is any hex digit) is not allowed - the 224-239.192/16 network IP address block is reserved for multicast. - Click Update to save your configuration.
Continue with device discovery using the Devices widget as described in Discovering, Defining, or Importing Devices.
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:
- Log into the SmartServer Configuration page as described in Accessing the SmartServer IoT Configuration Page.
Click the LON tab. The Network tab appears as the default SmartServer Configuration page. Once the network settings are configured for the SmartServer system, then the System tab will appear as the default.
SmartServer IoT Network tab
SmartServer IoT System tab
For SmartServer Pi, open the SmartServer Configuration page as described in Accessing the SmartServer Pi Configuration Page. The Configuration page view that appears depends on your cache data. As needed, click the SmartServer IoT tab (left-side). The System tab (top) will appear as the default as shown below.
SmartServer Pi System tab - Click the LON tab.
SmartServer IoT and SmartServer Pi LON Configuration pages are shown below. The examples that follow are shown using SmartServer IoT.
SmartServer IoT LON tab
SmartServer IoT Pi tab - Set the domain length and ID in the Domain Length (bytes) and Domain ID (hex) boxes.
You can set the domain length to 1 or 3 bytes, and you can set the domain ID to a hex value with two characters for a 1-byte domain or six characters for a 6-byte domain. If you select a 3-byte domain, select a 3-byte value as follows:- The last byte must be 00.
- The first byte cannot be:
- 00 - the network IP addresses are reserved.
- 0A - the 10/8 network IP address block is reserved for one-byte domains.
- 7F - the 127/8 network IP address block is reserved for the Internet host loopback.
- 2C - the 44/8 network IP address block is reserved for one-byte domains.
- The first two bytes cannot be:
- C0A8 - the 192.168/16 network IP address block is reserved for the zero-length domain.
- A9FE - the 169.254/16 network IP address block is reserved for the link local purpose.
- ExC0xx (where x is any hex digit) is not allowed - the 224-239.192/16 network IP address block is reserved for multicast.
SmartServer IoT LON tab
- Click Update to save your configuration.
Continue with device discovery using the Devices widget as described in Discovering, Defining, or Importing Devices.
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:
- Log into the SmartServer Configuration page as described in Accessing the SmartServer IoT Configuration Page. The Network tab appears as the default SmartServer Configuration page. Once the network settings are configured for the SmartServer system, then the System tab will appear as the default.
SmartServer IoT Network tab
SmartServer IoT System tab
For SmartServer Pi, open the SmartServer Configuration page as described in Accessing the SmartServer Pi Configuration Page. The Configuration page view that appears depends on your cache data. As needed, click the SmartServer IoT tab (left-side). The System tab (top) will appear as the default as shown below.
SmartServer Pi System tab - Click the LON tab.
SmartServer IoT and SmartServer Pi LON Configuration pages are shown below. The examples that follow are shown using SmartServer IoT.
SmartServer IoT LON tab
SmartServer IoT Pi tab - Select the LON Domain ID Enable Domain ID Discovery option.
SmartServer IoT LON tab - Click Update to save your configuration.
Continue with device discovery using the Devices widget as described in Discovering, Defining, or Importing Devices, Discovering Devices section.
...
Once device discovery is initiated using the Devices widget → Discover button (), you can optionally press a service button on a device in the domain to be discovered. The LON driver will wait for a service message that is generated by the pressing of a service button. Next, the LON driver will read the domain index 0 configuration at the unique ID that is included in the service message, and if a domain is configured for domain index 0, then the LON driver will assign the configured domain ID as the LON domain ID to be discovered.