Importing LON Devices from an LNS Network with IzoT CT

LON is supported with SmartServer Pi 4.3 and higher, with the exception of LON PL.

For SmartServer 4.1 and prior, see Importing LON Devices from an LNS Network with IzoT CT (Release 4.1 and Prior).

You can export LON device configuration information from a LON network created with IzoT CT to a SmartServer. You must use IzoT CT 4.2 or a newer version for this procedure. Prior releases will not work. To export LON devices from an LNS network using IzoT CT 4.2 or newer, follow these steps:

Switch the SmartServer to LON Independent Management Mode (IMM) as described in (Optional) Switch From LON Management. This procedure will not work with LON DMM.
Enable the appropriate SmartServer network interface that you plan to use to connect to your IzoT CT network.
1. For an RNI (remote network interface) connection using a U60, perform the following steps:
  1. 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
  2. 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
  3. Check the Enabled box for the interface in question (e.g., lon0 in the RNI Configuration section). For SmartServer 4.3, disregard the vlon0 interface.
  4. Click Update.
  5. Define a corresponding RNI connection in the LonWorks Interfaces Applet in the Control Panel.
2. For an RNI (remote network interface) connection using a IP-70, perform the following steps:
  1. 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
  2. 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
  3. Check the Enabled box for the Internal IP-70 Interface.
    
    SmartServer IoT LON tab
  4. Click Update.
    
    SmartServer IoT LON tab
  5. Define a corresponding RNI connection in the LonWorks Interfaces Applet in the Control Panel.
3. For an IP-852 connection, perform the following steps:
  1. 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
  2. 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
  3. Check the Enabled box for the IP-852 Router on the required IP Interface (eth0 or eth1).
  4. Click Update.
  5. Add the SmartServer’s IP-852 router to the IP-852 channel in the IP-852 Configuration Server and update the channel members.
  6. Define the IP-852 interface for the PC that will access the network in the LonWorks Interfaces Applet in the Control Panel.
Prior to running IzoT Net Export (INE), generate the XML resource files for any devices that you plan to export to the SmartServer that use custom resource files and import these files into the SmartServer.

Although the INE utility can export the device XIF files from an existing LNS network to the SmartServer, it is generally more efficient to also import into the SmartServer any device XIF files for devices that you intend to export as well. In this case, you can then use the /skipfiles option when running INE to speed up the export process. For details on generating XML resource files, see (Optional) Creating IAP Resource Definitions (XML). XML resource files and XIF files can be bundled as device type package files (DTP) to simplify the importing process into the SmartServer.
Launch IzoT CT and open the network to be exported in engineered mode without any network interface attached (i.e., uncheck the Network attached checkbox when prompted for the network interface).
1. Create a new subsystem to contain all the devices that will be exported to a single SmartServer. If your network has multiple SmartServers, then each SmartServer must be in a different subsystem. In this case, you will need to create separate subsystems for each SmartServer.
2. Add a new, unique IP-70 channel to the network in a root subsystem (e.g., Subsystem1 for each SmartServer that will be added to the network).
3. If your SmartServer will physically connect to the network using a U60 interface, then add an IP-70 to TP/FT-10 (or TP-1250) configured router to the network in Subsystem1. The A-side channel should be the IP-70 channel created in step 4b, and the B-side channel should be the physical channel in the network that the U60 will be connected to.
  
  or
  
  If your SmartServer will connect to the network using an IP-852 interface, then add an IP-70 to IP-852 configured router to the network in Subsystem1. The near-side channel should be the IP-852 channel, and the far-side channel should be the IP-70 channel created in step 4b.
4. Move the devices to be exported to a given SmartServer to the subsystem(s) created in step 4a. All of the devices to be exported to a SmartServer must be in the same subsystem with the SmartServer, or in a subsystem contained within the subsystem with the SmartServer. For example, if a network has three SmartServers in three subsystems called Building 1, Building 2, and Building 3, then all the Building 1 devices have to be in the Building 1 subsystem, or in a subsystem contained with the Building 1 subsystem such as Building 1.Floor 6.Room 6050.
  
  INE builds unique names that include the network, subsystem path, and device names so you should limit the characters in each name element.
5. Add a SmartServer IoT device to the IzoT CT drawing into each new subsystem that will be exported to a SmartServer using the SmartServer IoT.xif file as the device interface. The SmartServer IoT device should specify the correct IP-70 channel(s) created in step 4b.
Attach to the network using the network interface you enabled in step 2 above. You can either close and relaunch IzoT CT and specify the network interface, or go to Add-ins → Network Properties → Network Interface and choose the network interface name, check Network attached, and set the Management Mode to OnNet. If prompted, select Yes to upgrade the network interface.
1. If the network interface you are using differs from the original one in the network, then you may need to move the network interface to the correct channel. For example, if you are using the IP-70 RNI, then you would need to select the Open LNS Network Interface, right-click and choose Move Device → Change Channel, and select the appropriate IP-70 destination channel.
2. Commission the internal SmartServer router that you added to the network design in step 4c and make sure it is set to be online. To generate a service pin message for the internal router, perform the following steps:
  1. 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
  2. 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
  3. For an IP-70 to U60 channel router, use the Service/Connect button at the top of the page to generate the service pin message.
    
    SmartServer IoT LON tab
    
    For an IP-852 to IP-70 router, use the Service/Connect button adjacent to the enabled IP-852 router.
    
    SmartServer IoT LON tab
  4. Within IzoT CT, right-click the SmartServer IoT device and then click Commissioning → Commission.
  5. When prompted to press the Service button for the SmartServer, perform the following steps:
    1. Open the SmartServer Configuration page. The Network Configuration page appears.
    2. Click the LON tab. The LON Configuration page appears.
    3. Click the Service/Connect button near the top of the page.
Click the IzoT Net Export utility link to download the IzoT Net Export utility and then move it to your LonWorks bin. This utility is in Program Files (x86)\LonWorks\bin by default, but may be in a different location on your computer.
Use an SSH console application like PuTTY and log into the SmartServer using apollo credentials.
Enter the following command, replacing {SID} with the Segment ID for your SmartServer, to temporarily take the lon.sys component Offnet.
mosquitto_pub -t glp/0/{SID}/rq/dev/lon/lon.sys/if/system/0/mode -m '{"value":"Offnet"}'
```
mosquitto_pub -t  glp/0/{SID}/rq/dev/lon/lon.sys/if/system/0/mode -m '{"value":"Offnet"}'
```

Open a Windows console application as an administrator and run the IzoT Net Export utility with one of the following inex commands, depending on whether you are trying to export using standard mqtt or secure mqtts:

/skipfiles option can be used if the device interface files (XIF files) were previously imported (see step 3).

If you are exporting using standard mqtt with port 1883 enabled, then enter the following:

inex /n:"<Network Database Name>" /e:"Target Subsystem"/mqtt://<SmartServer IP address or Hostname>/<Segment ID> /direct:ine /v /skipfiles

If you are exporting using secure mqtts with port 8883 enabled, and are also using the SmartServer’s self-signed certificate, then enter the following:

Secure mqtts requires that you access the SmartServer using the Hostname only.

inex /n:"<Network Database Name>" /e:"Target Subsystem"/apollo:<Your Apollo Password>@mqtts://<SmartServer Hostname>/<Segment ID> /direct:ine /v /skipfiles

If you are exporting using secure mqtts with port 8883 enabled, and are using a signed certificate, then enter the following:

Secure mqtts requires that you access the SmartServer using the Hostname only. It also requires that you download the ca.pem certificate file from your SmartServer. See Importing LON Devices from an LNS Network. This example assumes you have placed a copy of the certificate file (ca.pem) in the same directory on your PC where IzoT Net Export is running.

inex /n:"<Network Database Name>" /e:"Target Subsystem"/apollo:<Your Apollo Password>@mqtts://<SmartServer Hostname>/<Segment ID> /direct:ine /v /skipfiles /ca:ca.pem

Parameter	Description
Network Database Name	LNS network name
Target Subsystem	LNS subsystem that you want to export
Your Apollo Password	The specific apollo password for your SmartServer
SmartServer IP or Hostname	SmartServer IP address or hostname. Secure mqtts only supports using the hostname.
Segment ID	Install code that is printed on the SmartServer IoT label

The IzoT Net Export tool supports a number of commands and options. For example, starting with IzoT Net Export 1.5, you can specify the /clear option to clear the LON devices defined in the target SmartServer and re-export all specified devices from the LON network. You can view a summary of available commands and switches by running the tool in a Windows console with the /help switch. If you specify a network name and export specification without a command, the IzoT Net Export tool defaults to execute the export command. Include double quotes for any arguments with spaces. For example, to specify Subsystem 1 as the target subsystem, specify the name as "Subsystem 1".

SmartServer IoT device in Subsystem 1 using standard mqtt

inex /n:"myDrawing" /e:"Subsystem 1"/mqtt://smartserver-17q3kd2/17q3kd2 /direct:ine /shortname /v /skipfiles

SmartServer IoT device in Subsystem 2, which is inside Subsystem 1 using standard mqtt

inex /n:"myDrawing" /e:"Subsystem 1.Subsystem 2"/mqtt://10.1.2.3/T6tWyfzj /direct:ine /shortname /v /skipfiles

SmartServer IoT device in subsystem Exp, which is inside subsystem S1 using secure mqtts. In this example the SmartServer is also using a signed certificate

inex /n:"myDrawing" /e:"S1.Exp"/apollo:myPassword@mqtts://smartserver-T6tWyfzj.echelon.cloud/T6tWyfzj /direct:ine /shortname /v /skipfiles /ca:ca.pem

Use an SSH console application like PuTTY and log into the SmartServer using apollo credentials.
Enter the following command, replacing {SID} with the Segment ID for your SmartServer, to take the lon.sys component back to Onnet.
```
mosquitto_pub -t  glp/0/{SID}/rq/dev/lon/lon.sys/if/system/0/mode -m '{"value":" Onnet "}'
```
You may need to reboot your SmartServer following the export process and may also need to test any devices in the SmartServer’s CMS that are in the unprovisioned (blue) state to see them transition to provisioned (green) state. See Rebooting Your SmartServer IoT or Rebooting SmartServer Pi.
Repeat this procedure for each SmartServer in your network and repeat it for all SmartServers whenever you make changes to the IzoT CT drawing.
Copy the inex commands for each SmartServer to a text box in your IzoT CT drawing for future use.