Versions Compared

Version Old Version 2 New Version 3
Changes made by

Nina Cardillo

Nina Cardillo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The frequently asked questions below provide information regarding SmartServer applications and references 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.

...

Yes, you can use the SmartServer to automatically discover BACnet, Modbus, and LON devices using the Discover button (Image Modified) 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.

...

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

...

  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 page. See (Optional) Add a Modbus RTU Interface for more information. 

    Info

    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.

    Info

    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.   


...

  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 an LNS Network using IzoT Net Export/wiki/spaces/TEMP/pages/2198670.

  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.

    Info
    titleUse-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.


...

  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.

...

In IzoT CT /IzoT Net Server:

  1. Enable BACnet using the BACnet Configuration page. See (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.

...

  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 an LNS Network using IzoT Net Export/wiki/spaces/TEMP/pages/2198670.

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.

...