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

The frequently asked questions below provide information regarding SmartServer applications and references for more information:

Do I need a license to use my SmartServer, and if so, how do I get one?

License management is available with SmartServer 3.3 and higher. See Manage Licenses as well as Frequently Asked Questions - Licensing for more information.

How do I use the SmartServer as a self-installed IP-852 router?

The SmartServer can be used as a self-installed IP-852 router, which allows you to create an IP-852 network with two or more SmartServer IoTs (e.g., connecting two buildings together) without using a LNS network integration tool to add the SmartServers to the existing LNS network. This application is similar to the i.LON 600 self-installed router as repeater feature. In this case, the SmartServers are used as repeaters and repeat all the traffic on any FT-10/XF-1250/Power Line SmartServer to all the other channels connected to other SmartServers. This method is useful when a network integration tool does not support routers. In these cases, the SmartServers are physically connected to the existing network, but there are now two logical networks:

  • an IP-852 network, with only the SmartServers being configured by the IP-852 configuration server
  • a separate LNS network, which has all the other devices

See the Using the SmartServer as a Self-Installed IP-852 Router section in (Optional) Set up the IP-852 Configuration Server for more information.

Can the SmartServer automatically discover devices?

Yes, you can use the SmartServer to automatically discover BACnet, Modbus, and LON devices using the Discover button () on the Devices widget. Datapoint discovery is only supported for BACnet Devices. For LON and Modbus devices, you must import an XIF file prior to running device discovery.

  • BACnet – The SmartServer can automatically create a device type and discover the BACnet datapoints for each type of discovered BACnet device.  
  • Modbus – The Modbus protocol does not support device discovery, but the SmartServer has a mechanism that can be used to discover Modbus devices.
    • To discover Modbus devices using the SmartServer, you first need to create a MOD file with unique identifier for that Modbus device type, and then import the file using the Device Types widget. During device discovery, if a Modbus device has that unique identifier, then that device is automatically added to the Devices widget. 
  • LON  – If you import the device XIF before running device discovery, then any device that is discovered can be used. If you run discovery before importing the XIF, then the SmartServer will create a device type without datapoints, and you will need to remove these devices as they are not functional. 
    • There are two modes for discovering LON devices:
      • Using the SmartServer with LNS tools (IMM) – LON devices should be discovered with the LNS tool (e.g., IzoT CT or IzoT Net Server application). If you run discovery using the CMS Devices widget, then it may add any LON device that it discovers. Therefore, you need to run the iNex export anytime you run discovery using the CMS Devices widget. Otherwise, what you see in the SmartServer subsystem may be what you see in the Devices widget.
      • Using the SmartServer as a standalone integration tool (DMM) – device discovery will add any discovered devices.
    • For LON device discovery, you can specify a domain ID or use the Enable Domain ID Discovery option on the LON Configuration page to check all 1-byte domains. When using Enable Domain ID Discovery option, the domain ID of the first device discovered, or the first service pin message received, will determine the domain ID that is used for all subsequent device discovery. See (Optional) Add a LON Interface for more information.

See also Discovering, Defining, or Importing Devices for more information.

How do I only use the SmartServer with a BACnet tool?

The SmartServer BACnet server allows third-party BACnet tools to access LON and Modbus datapoints. To use this feature, you will need to:

  1. Enable BACnet using the BACnet Configuration page. See (Optional) Setting up BACnet for more information.
  2. Import a BACnet type map (BTM) file for each device type using the CMS Device Types widget. BTM files are used to define BACnet datapoint for the LON or Modbus device. BTM files are manually created, but can then be used on one or more SmartServers. See the Importing a Device Type section in Defining Device Types for more information.
  3. Use the SmartServer CMS to add and provision the LON and Modbus devices. See Site Provisioning for more information.
  4. For LON devices, you will need an XIF file, and any necessary resource file set. See (Optional) Creating a LON Device Interface (XIF) Definition for more information.
  5. For Modbus devices, you will need to manually create a Modbus XIF file that defines the Modbus datapoints. See (Optional) Creating a Modbus Device Interface (XIF) Definition for more information.

How do I access BACnet datapoints with the SmartServer CMS?

The SmartServer can be used to access BACnet devices either by performing device discovery, which discovers BACnet devices and their datapoints, or by manually creating the BACnet XIF file and defining datapoints that are used for each BACnet device.

If you use the device discovery feature to access BACnet devices, then the SmartServer discovers BACnet devices and their datapoints, and automatically creates a BACnet XIF file if one does not already exist. The BACnet XIF file defines which datapoints are supported by a specific BACnet device type. Each type of BACnet device will have a unique BACnet XIF file. BACnet XIF files that are created by device discovery will have all the datapoints in the BACnet device. 

If you manually create the BACnet XIF file, then you can define which datapoints are used for each type of BACnet device. In this way, you can reduce the overall number of datapoints. Once you have manually created the BACnet XIF files, you can either use device discovery to discover and add the devices (not its datapoints) which use the BACnet XIF file you created to the SmartServer, or you can manually add the BACnet device to the SmartServer.

To access BACnet datapoint with the SmartServer CMS, you will need to perform one of the following as described below:

  • Use device discovery to discover BACnet devices and their datapoints
  • Manually create a BACnet XIF file (allows you to limit which datapoints are supported for each device type)

Use Device Discovery to Discover BACnet Devices and their Datapoints

  1. Enable BACnet using the BACnet Configuration page. See (Optional) Setting up BACnet for more information.
  2. Start device discovery using the CMS Devices widget. For each discovered BACnet device, the SmartServer will automatically create a BACnet XIF if one does not already exist. See Discovering, Defining, or Importing Devices for more information. 

  3. Provision the BACnet devices using the CMS Devices widget. See Provisioning Devices for more information.

Manually Create a BACnet XIF File

  1. Create a BACnet XIF file that specifies the BACnet datapoints and how they are represented in the SmartServer. See (Optional) Creating a BACnet Device Interface (XIF) Definition for more information. The SmartServer BACnet discovery feature can be used to automatically discover BACnet datapoints and to automatically create the BACnet XIF file. The BACnet XIF file can also be manually created. See the Importing a Device Type section in Defining Device Types for more information.
  2. Enable BACnet using the BACnet Configuration page. See (Optional) Setting up BACnet for more information.
  3. Import the BACnet XIF file using the CMS Device Types widget. See the Importing a Device Type section in Defining Device Types for more information.
  4. Add BACnet devices in one of the following ways:
    1. Use the CMS Devices widget to manually add the BACnet devices. See Discovering, Defining, or Importing Devices for more information. 
    2. Start device discovery using the CMS Devices widget. For each discovered BACnet device, the SmartServer will use the imported BACnet XIF file. If a BACnet XIF file is not found for a device type, then one will be automatically created. See Discovering, Defining, or Importing Devices for more information. 

  5. Provision the BACnet devices using the CMS Devices widget. See Provisioning Devices for more information.

BACnet datapoints cannot be accessed directly from IzoT CT or IzoT Net Server. To do so, you will need to use a SmartServer internal device to map the BACnet datapoints to LON datapoints so that you can use IzoT CT to monitor and control BACnet devices. Go to the How do I access BACnet or Modbus datapoints in IzoT CT / IzoT Net Server section for information on using an internal device to map BACnet-to-LON datapoints.   

How do I access Modbus datapoints with the SmartServer CMS?

The SmartServer can be used to access as Modbus TCP or RTU devices. To access these devices, you will need to:

  1. Create a Modbus XIF file that specifies the Modbus datapoints and how they are represented in the SmartServer. Modbus XIF files are manually created, but can then be used on one or more SmartServers. See (Optional) Creating a Modbus Device Interface (XIF) Definition for more information.
  2. For Modbus RTU, configure the SmartServer RS-485 interface using the RS-485 Configuration pageSee (Optional) Add a Modbus RTU Interface for more information. 

    The SmartServer IoT Pro EX Edition has two built-in RS-485 interfaces, and each IOX has its own RS-485 interface. For Modbus RTU, you can only use one of these RS-485 interfaces with a SmartServer. The other SmartServer, or IOX RS-485 interfaces, can be used for other protocols.

  3. Import the Modbus XIF file using the CMS Device Types widget. See the Importing a Device Type section in Defining Device Types for more information.

    Modbus datapoints cannot be accessed directly from IzoT CT or IzoT Net Server. To do so, you will need to use a SmartServer internal device to map the Modbus datapoints to LON datapoints so that you can use IzoT CT to monitor and control Modbus devices. Go to the How do I access BACnet or Modbus datapoints in IzoT CT / IzoT Net Server section for information on using an internal device to map Modbus-to-LON datapoints.  

How do I only use the SmartServer CMS to add and provision devices?

The SmartServer can be used as a standalone network integration tool. In this application, you will add all devices and provision them only using the SmartServer CMS. While BACnet and Modbus devices are always added and provisioned using the SmartServer CMS, the CMS can be used to add and provision LON devices as well. In the case of LON devices, you will use Device Management Mode (DMM), which is the default.

See Provisioning Devices for more information.

How do I use the SmartServer with IzoT CT / IzoT Net Server?

To use the SmartServer with IzoT CT or IzoT Net Server, you will need to:

  1. Configure the SmartServer to use Independent Management Mode (IMM) for LON devices using the CMS Devices widget. Device Management Mode (DMM) is the default. See (Optional) Switch Off LON Management for more information.
  2. Export the LON database that has been created, or a subset of the database, to the SmartServer using the iNex Export tool in order to access the LON devices in the SmartServer CMS. See Importing LON Devices from IzoT Net Server or IzoT CT using IzoT Net Export.
  3. If you are using iNex, then you will need to add a SmartServer IoT device to the LON network. The SmartServer IoT should be added to an IP-70 channel. A separate IP-70 channel should be added for each SmartServer.

    Use-case considerations

    1. If you are only using the SmartServer for IP-852 routing, then the iNex Export tool is not needed in this application. Instead, you will need to:
      1. Use the CMS Devices widget to change the SmartServer to use IMM for LON devices. See (Optional) Switch Off LON Management for more information.
      2. Enable IP-852 using the SmartServer LON Configuration page. Doing so allows you to use the SmartServer like an IP-852 router. See (Optional) Set up the IP-852 Configuration Server for more information.
      3. To support multiple U60s, configure the SmartServer routers to reduce traffic on the U60 channels by adding an IP-70 channel for the SmartServer backbone and connecting a router for IP-852, as well as a router for each U60, to the IP-70 channel.
    2. If you are using the SmartServer for scheduling, then consider using an internal device that is controlled by the scheduler. The iNex Export tool is not needed in this application.
    3. If you are only using the SmartServer to access Modbus or BACnet datapoints, then the iNex Export tool is not needed in this application.
    4. If you are using LON devices, and the built-in CMS features (i.e., scheduling, alarming, data logging, etc.), then you will need to use the iNex Export tool to export some, or all, of the LON database.

      iNex requires that you use IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version.

Because BACnet and Modbus datapoints are not LON datapoints, they cannot be directly accessed by IzoT CT or IzoT Net Server. However, you can use a SmartServer internal device to map the BACnet or Modbus datapoints to LON datapoints so that you can access them with a LON integration tool (e.g., CT Browser). Go to the How do I access BACnet or Modbus datapoints in IzoT CT / IzoT Net Server section for information on using an internal device to map BACnet/Modbus-to-LON datapoints. 

How do I use the SmartServer with IzoT CT, IzoT Net Server, and a BACnet tool?

To see BACnet datapoints in IzoT CT, you will need to:

  1. Enable BACnet using the BACnet Configuration page. See (Optional) Setting up BACnet for more information. 
  2. Create a BACnet XIF file (either using device discovery or manually). See (Optional) Creating a BACnet Device Interface (XIF) Definition for more information.
  3. Import the BACnet XIF file using the CMS Device Types widget. See the Importing a Device Type section in Defining Device Types for more information.
  4. Use the SmartServer CMS to add and provision the BACnet device. See Site Provisioning for more information.
  5. Use an internal device to map the BACnet to LON datapoints.

To see Modbus datapoints:

In IzoT CT /IzoT Net Server:

  1. Enable BACnet using the BACnet Configuration page. Se(Optional) Setting up BACnet for more information. 
  2. Manually create a Modbus XIF file. See (Optional) Creating a Modbus Device Interface (XIF) Definition for more information.
  3. Import the Modbus XIF file using the CMS Device Types widget. See the Importing a Device Type section in Defining Device Types for more information.
  4. Use the SmartServer CMS to add and provision the Modbus device. See Site Provisioning for more information.
  5. Use an internal device to map the Modbus to LON datapoints.

For a BACnet Tool:

  1. Create a BACnet type map (BTM) file for each device type in order to access the Modbus datapoints in the BACnet tool. See (Optional) Setting up BACnet for more information. 
  2. Import the BTM file using the CMS Device Types widget. See the Importing a Device Type section in Defining Device Types for more information.

To access LON devices that you added and provisioned (commissioned):

In IzoT CT/IzoT Net Server:

  1. Configure the SmartServer to use Independent Management Mode (IMM) for LON devices. Device Management Mode (DMM) is the default. See (Optional) Switch Off LON Management for more information. 
  2. Use the iNex Export tool to export the LON database, or a subset of the database, to the SmartServer. See Importing LON Devices from IzoT Net Server or IzoT CT using IzoT Net Export.

For a BACnet Tool:

  1. Create a BTM file manually for each LON device type. See (Optional) Setting up BACnet for more information. 
  2. Import the BTM file using the CMS Device Types widget. See the Importing a Device Type section in Defining Device Types for more information.

Using the IzoT Net Export (iNex) tool

If you are using iNex, then you will need to add a SmartServer IoT device to the LON network. The SmartServer IoT should be added to an IP-70 channel. A separate IP-70 channel should be added for each SmartServer. 

Also, you may want to limit the export to only those devices that you want to monitor and control in the SmartServer CMS. You can do this by limiting which devices are in the SmartServer IoT subsystem or child subsystem.

iNex requires that you use IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version.

How do I access BACnet or Modbus datapoints in IzoT CT / IzoT Net Server?

BACnet and Modbus datapoints cannot be directly accessed by IzoT CT or IzoT Net Server. To do so, you will need to perform the following steps:

  1. Use an internal device to map the BACnet/Modbus datapoints to LON datapoints, which can be accessed with your LON integration tool. See (Optional) Setting up BACnet for information on how to do the mapping.
  2. Use the localDev.exe application from the Renesas github repository to create an internal device with 64 empty LON Functional Blocks (FBs).
  3. Use your integration tool, such as IzoT CT, to dynamically add datapoints to the internal device. If the LON and BACnet/Modbus datapoint types are similar, then you can use a connections (CON) file to do the mapping between the LON and BACnet/Modbus datapoints.

    For example, a float datapoint for the BACnet/Modbus translates directly to SNVT_temp_p. You can use shadowConnect.exe (from the Renesas github repository) if you have similar datapoint types.

    Considerations for BAC and MOD files

    There are some limitations for BACnet XIF and Modbus XIF files when using shadowConnect.exe. Additionally, there are limitations for the names of dynamic datapoints added to IzoT CT/IzoT Net Server database. Once you add a dynamic datapoint into IzoT CT/IzoT Net Server, you cannot rename the datapoint. In this case, you must delete the datapoint and add a new datapoint with a new name. See Naming Considerations for BACnet XIF and Modbus XIF Files in the (Optional) Setting Datapoint Names for more information.

What older products can the SmartServer replace?

You can use the SmartServer IoT to replace the following old or discontinued products:

  • i.LON 100s, i.LON SmartServer, and SmartServer 2.0 – you will need to purchase a SmartServer IoT and separately purchase a U60/U70 for each channel (i.e., XF-1250, FT-10, or power-line) that you want to support. If you are only using BACnet or Modbus devices, then you do not need to purchase a U60/U70.
  • i.LON 600 and i.LON 700 – you will need to purchase a SmartServer IoT and separately purchase a U60/U70. See Migrating from the i.LON 600 to the SmartServer IoT and Migrating from the i.LON 700 to the SmartServer IoT for more informationSee also i.LON 600 and i.LON 700, as well as Documents Archive and search for i.LON 600 or i.LON 700 for additional resources. 
  • LPR-10 and LPR-12 – you will need to purchase a SmartServer IoT and separately purchase at least two U60/U70s. See Migrating from the LPR Router to the SmartServer IoT for more information. 
  • MPR-50 – you will need to purchase a SmartServer IoT and separately purchase at least one U60/U70 for each channel (i.e., XF-1250, FT-10, or power-line) that you want to support.

How can a third-party tool access the SmartServer data?

The SmartServer CMS can be accessed in the following ways:

How can I customize the SmartServer?

You can customize the SmartServer in the following ways:

How do I set the location of my SmartServer device (i.e., latitude and longitude coordinates)?

You can configure your SmartServer's location by following the steps in the Verifying the Device Location section found in Configure Your SmartServer.


  • No labels