LON is supported for SmartServer Pi 4.3 and higher, with the exception of LON PL.
...
As a self-installed IP-852 router. This method allows you to create an IP-852 network with two or more SmartServer IoTs SmartServers without using a network integration tool to add the SmartServers to the network (similar to the i.LON 600 "Self-install router as repeater" feature). This method is useful when a network integration tool does not know how to use routers. In this case, the IP-852 network is separate from the device network.
This method can only be used if you are using the SmartServer IoT for IP-852 routing. That is, this method cannot be used if you want to use the SmartServer for monitoring, controlling, logging, alarming, or scheduling of the devices' datapoints.
A self-installed IP-852 router is used as a repeater and all traffic on one LonWorks channel (e.g., TP/FT-10) is sent to all other channels. Since many LonWorks channels are half-duplex, you need to make sure that traffic on one channel does not drastically affect bandwidth on all channels.
See the steps described in installation example 1 for more information about setting up self-installed IP-852 routers.- With a network integration tool (e.g., IzoT CT and IzoT Net Server). This method requires you to add the SmartServer IP-852 routers to an IzoT Net Server network using a network integration tool (e.g., IzoT CT).
See the steps described in installation example 2 for more information about setting up IP-852 routers with a network integration tool.
The diagram below shows the SmartServer IoT IP-852 Router network architecture.
...
There is also a video on the SmartServer Training Videos page that shows you how to enable the LON IP-852 channel routing on your SmartServer IoT, how to manage it in the IP-852 Config Server application, and how to create a VNI RNI attachment point for software that uses the EnOcean OpenLDV driver layer. Click here for the LON IP-852 Setup video.
| Note | ||
|---|---|---|
| ||
Re-imaging the SmartServer system, resetting databases, or restoring the settings to factory defaults may cause the MAC IDs (also referred to as neuron IDs) to change in the SmartServer for the IP-852 and U60 routers, SmartServer IoT device (used for IMM), and any internal devices that get their neuron IDs assigned by the SmartServer. If you are using the IP-852 Config Server, after you reset/restore/re-image the SmartServer, you many need to delete the SmartServer device shape in IP-852 Config Server and then add it again. If the SmartServer is used in an IzoT CT or IzoT Net Server database, after you reset/restore/re-image the SmartServer, you will need to decommission the IP-852 and U60 routers (removing the neuron ID as it has changed), the SmartServer IoT device, and any SmartServer internal devices, and then commission these devices with the new neuron IDs. |
...
To use the IP-852 feature, you must:
- Set up IP-852 routing in IzoT CT as described on this page
- Enable the SmartServer
...
- to support IP-852 as described on this page.
- Define devices on the IP-852 channel
...
- and define a VNI interface in the LonWorks Interfaces (32-bit) control panel
...
- applet as described in (Optional) Set up the IP-852 Configuration Server.
- Switch to IMM in the SmartServer CMS as described in (Optional) Switch From LON Management.
- Commission devices using IzoT CT as described on this page.
The procedure that follows provides the necessary steps to enable and define IP-852 devices, beginning with the IzoT CT design and ending with commissioning devices.
...
Continue setting up the IP-852 feature following the steps in the section below: Enabling IP-852 in the SmartServer IoT Configuration Pages.
Enabling IP-852 in the SmartServer
...
Configuration Pages
- Open 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 Pi LON tab - Enable the IP-852 Router Configuration → eth0 option and click Update.
SmartServer IoT LON tab - Enable the IP-852 feature as described above for each SmartServer in the system.
Continue setting up the IP-852 feature following the steps in the section below: Defining the IP-852 Channel Devices.
Defining the IP-852 Channel Devices
To define the IP-852 channel devices, see (Optional) Set up the IP-852 Configuration Server, and then continue setting up the IP-852 feature following the steps in the section below: Switching to LON Independent Management Mode (IMM).
Switching to LON Independent Management Mode (IMM)
LON Device Management Mode (DMM) is the default SmartServer IoT setting where the SmartServer managed the configuration of all the LON devices provisioned by the SmartServer.
Since IzoT CT is used as the network management tool to manage the network configuration of the LON devices, this setting must be changed to LON Independent Management Mode (IMM), where the SmartServer acts as an independent device in the LON network. The steps below describe how to change this setting from LON
To change from DMM to LON IMM using the SmartServer CMS.
...
Continue IMM, see (Optional) Switch From LON Management, and then continue setting up the IP-852 feature following the steps in the section below: Commissioning Devices using IzoT CT.
...
- In IzoT CT, select the Add-ins tab → LonWorks Network → Network Properties actions.
- Connect to the interface that was defined as your VNI.
Doing so changes the network interface to solid green.
- Select the router devices, working outward, and then select the Commissioning → Commission actions.
- Click Finish from the Router Application State window.
- Use the IzoT CT right-click actions to initiate commissioning.
- Return to the SmartServer IoT SmartServer LON Configuration page.
Click the IP-852 Router Configuration → Service/Connect button to generate service connect messages for commissioning the router entities inside SmartServer while using IzoT CT.
Note icon false title Commissioning an IP-852 router
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- Return to IzoT CT and repeat the steps above to commission the next routing layer.
- Return to the SmartServer IoT LON Configuration page.
- Click the LON Interfaces → Service/Connect button to generate service/connect messages to commission the next routing layer. For SmartServer 4.
3, disregard the vlon0 interface.
SmartServer IoT LON tab - Return to IzoT CT.
- Once the LON routing infrastructure is set up, the target devices that have peer-to-peer connections defined between the switch and lamp objects of the two devices can be commissioned.
IzoT CT Device Installation
IzoT CT Device Commission - Use LonScanner to monitor traffic between devices with a previously defined LonScanner RNI interface as shown in the example below.
...
For direct replacement, perform the following steps:
- Change the SmartServer IP address settings on the Network Configuration page (see Configure Your SmartServer) for the Ethernet LAN or WAN ports you are using to Static IP Address or DHCP.
Do not leave the IP address interface set to Startup Mode - DHCP with rapid fallback to static.- For SmartServer IoT release prior to 2.7, clear the Startup Mode setting.
- For SmartServer IoT release prior to 2.7, clear the Startup Mode setting.
- Verify that the LON/IP Class A Network Override Standard setting is not enabled on the LON Configuration page, as described in Adding a LON Interface.
- Reboot the SmartServer IoT or SmartServer Pi.
Switch the SmartServer to LON Independent Management Mode (IMM) (see Switch off LON Management) using the CMS Devices widget.
Warning The installation will fail if you skip this step.
- Verify that the IP-852 setting is enabled on the Adding a LON Interface page. For SmartServer
...
- releases prior to 2.7 Update 1, see Features Configuration.
- Add the SmartServer to the IP-852 Config Server. When all the devices are green, right-click the channel and click Update Channel.
- Replace the i.LON 600 with the SmartServer in the network integration tool.
- Press the IP-852 router service button on the Adding a LON Interface page. For SmartServer releases prior to 2.7 Update 1, see Features Configuration.
Example 3 - Multi-port IP-852 Routing
...
You can use the SmartServer to monitor and control datapoints on field devices while also acting as an IP-852 router. To enable monitoring and control at the same time as IP-852 routing, add a SmartServer IoT device on the SmartServer IP-70 backbone channel. The SmartServer IoT devices are used by the SmartServer to read and write to external devices. It is important to switch the SmartServer to LON Independent Management Mode (IMM) (see Switching off LON Management) before provisioning the SmartServer IP-852 and U60 routers, and using most of the SmartServer built-in functions.
...
Configuring IP-852 CRC Support
The ability to enable or disable IP-852 CRC support is available with SmartServer 3.1 Update 3 and higher.
SmartServer releases prior to 3.1 Update 3 require IP-852 CRC support. SmartServer release 3.1 Update 3 and higher provides the Enforce CRC validation option to support edge servers that do not implement IP-852 cyclical redundancy checks (CRC). By default, the IP-852 CRC validation option is disabled.
Enable the Enforce CRC validation option and click Update for IP-852 CRC support.
SmartServer IoT LON tab
...