Page tree
Skip to end of metadata
Go to start of metadata

You can use the SmartServer to integrate and manage LON devices. If you are using LON IP-852 or IP-70 devices or routers, you can interface with them using the SmartServer's built-in LON driver and the built-in LAN and WAN Ethernet interfaces. If you are using LON FT, LON TP-1250, or LON PL-20 devices, add a U60 FT, U60 TP-1250, or U70 PL-20 network interface to communicate with them. 

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.

You cannot install more than a total of eight network interfaces (U60 or U70) and three IOX modules in a single SmartServer. If you have more than four USB devices, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub. 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:

  • 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).

This section consists of the following:

Overview

Following are guidelines for using the SmartServer LON interface:

  • If you are using the SmartServer IoT for IP-852 routing only, then all you need to do is commission the IP-852 router (that is, you do not need to commission the U60 router). Doing so makes the SmartServer IoT a direct replacement for the i.LON 600, although the setup is different than the i.LON 600. 
  • To use multiple U60s or U70s, BACnet, Modbus, or SmartServer IoT devices, you will need to add one U60/U70 router for each U60/U70 being used. 
  • To use any of the other SmartServer features (such as datapoint monitoring, logging, REST/MQTT API) you will need to 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.
  • To monitor or control BACnet or Modbus devices from CT or your LNS application, you will need to use a SmartServer Internal LON device to map the BACnet/Modbus datapoints to LON datapoints.

      IzoT CT IP-852 LonWorks Network using Two SmartServer IoTs

You can use the SmartServer as a 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 Dialog LonScanner Protocol Analyzer to monitor all LON network traffic on one of the SmartServer channels.

The LON Configuration page is shown below.

Using Multiple U60s

Initial U60 Installation

When using only one U60, it can be plugged into the SmartServer regardless of whether the SmartServer IoT is powered on or off.

When using multiple U60s, only the first U60 can be plugged into the SmartServer regardless of whether the SmartServer IoT is powered on or off. You cannot plug in additional U60s while the SmartServer is powered off. To plug in any new U60s, you must do so only when the SmartServer is fully powered up, plugging in each U60 one at a time.

If you are plugging the U60s into a powered hub, then first plug in the powered hub with no U60s plugged in, and then plug in the U60s one at a time.

Once you have plugged in all the U60s into the SmartServer, you will see all the U60s in the Step 5 - (Optional) Secure Your SmartServer page. You can then power off the SmartServer, and power it up again, and the SmartServer and U60s will continue to work.

The process is only necessary during initial U60 installation.

Reset to Defaults (applies only after U60s are installed)

U60s can remain plugged in if you are going to do a reset to defaults (Reset Database) from the System Configuration page. 

All but one U60 must be unplugged before issuing a reset to defaults if you are going to do a reset to defaults (Restore to Factory) from the System Configuration page. Once reset to defaults is complete, reinstall each U60 one at a time as explained above.

See the Resetting the SmartServer to Factory Defaults section for more information about these reset operations using the System Configuration page.

RNI Configuration

The LON RNI Configuration area is described below. For more information about how to set up the SmartServer RNI feature, see (Optional) Add a Remote Network Interface (RNI)

  1. 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. 

    • 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 a Dialog LonScanner Protocol Analyzer, select the check box for Protocol Analyzer.

  2. After the RNIs are selected and the port numbers are entered, click Update to update the settings on the SmartServer.

  3. Use the Service/Connect Send button to send a service message to provision SmartServer IoT interfaces.

Once the RNIs are enabled, you can use the LonWorks (32-bit) Interfaces control panel applet to define RNIs managed by the SmartServer for use by external tools through OpenLDV driver layer.

IP-852 Configuration

The LON IP-852 Configuration area is described below. For more information about how to set up the SmartServer IP-852 feature, see (Optional) Add a LON IP-852 Router

If you are using the IP-852 interface, an IP-852 Configuration Server must be used and configured to manage the IP-852 channel. Also, all devices on the same IP-852 channel must be added to the IP-852 Configuration Server. Any IP-852 compliant configuration server may be used. The Dialog IP-852 Configuration Server is available for free download here. For more information on how to set up an IP-852 channel with the IP-852 Configuration Server, refer to the IP-852 Channel User's Guide.

Up to six native LON interfaces can be added to a SmartServer, and a LON/IP-852 interface can also be added to a SmartServer. 

  1. To add a native LON interface, connect a Dialog 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.  

    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.

    More than two TP-1250 interfaces cannot be connected. If you have more than one PL interfaces attached, you must connect each PL interface to a PL channel isolated from the other PL channels connected to the same SmartServer. To connect more than four interfaces, connect a powered USB hub to the SmartServer and connect the U60 and U70 interfaces to the hub.

  2. Select the checkbox for IP-852 Router Configuration.

  3. 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).

  4. After the IP-852 configuration is set, click Update to update the settings on the SmartServer.

  5. Provision the IP-852 router by clicking the Service/Connect Send button.

  6. Provision each U60 router by clicking the Service/Connect Send button for the specific U60.

    Each SmartServer IoT must have its own IP-70 channel.

    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.


    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 

Internal IP-70 Extent Configuration

For internal IP-70 extent configuration, use the dropdown list to set Internal Only or Internal + eth0. 

Save your changes by clicking the Update button.

LON Interface Settings

The LON Interface settings are described below. For more information, see (Optional) Add a LON IP-852 Router and (Optional) Add a Remote Network Interface (RNI).

The LON Configuration page displays LON interface information (transceiver type, install ID, and MAC ID). Use the Send button to send a service message for provisioning LonTalk interfaces.

If you plan to use your SmartServer with only a single LON adapter, select the Single LonTalk Interface Mode checkbox. 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 interface adapters, connect each device so that you can identify the channels lon 0 through lon n. Once the channels are enumerated, disable the Single LonTalk Interface Mode option.

The attached network interfaces appear in the LonTalk Interfaces table.

LON/IP Class A Network Settings

If you are managing an IP-70 network channel extent externally, you have access to the second octet of the Class A subnet to manage the domain ID used in the LonTalk address space. 

You can enable or disable the LON/IP Class A Network override standard option and specify the Class A Network prefix setting (1-126) in the designated field. Save your changes to LON/IP Class A Network settings by clicking the Update button at the bottom of the page.

LON Domain ID

You can change the LON domain ID if your LON management mode is set to DMM as described in Switching off LON Management.  By default, the SmartServer uses a LON domain ID that is allocated at random from a small pool.  If you have a network with multiple SmartServers with LON devices using DMM, each SmartServer must be configured to use a different domain to prevent LON address conflicts.  If you use the default random domain assignment, it is possible that two SmartServers will be assigned the same random domain ID.  To change the LON domain ID in DMM open the LON Configuration page and 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 the Update button to save your changes.



  • No labels