...

For LON devices, the SmartServer can be used in one of the following ways:

• LON Independent Management Mode (IMM) – use IzoT CT or other tool based on IzoT Net Server to add and commission all SmartServers and other LON devices. You must switch to IMM mode (see (Optional) Switch Off From LON Management) before using IzoT CT or IzoT Net Server.  You cannot add or provision LON devices using the CMS with IMM.
• LON Device Management Mode (DMM) – use the SmartServer CMS to add and provision LON devices.  You can create LON devices as applications that run on your SmartServer.  These are SmartServer internal devices.  If you do not add or provision any external LON devices, you can manage your internal LON devices from an external tool such as IzoT CT.  If you add or provision any external LON devices to your DMM SmartServer, you cannot add or provision the LON devices using an external tool such as IzoT CT.
• LON IP-852 Self-installed Repeater – use the Network and LON Configuration pages with LON DMM to configure IP addresses and enable IP-852. An external tool such as IzoT CT and the SmartServer CMS are not required for a SmartServer used only as an IP-852 router.  You must use an IP-852 Configuration Server to configure the IP-852 routers in your network.

If you will be using your SmartServer on a LON network managed with an IzoT Net Server or LNS Server, then you can continue to define and commission the devices using a tool based on the IzoT Net Server or LNS Server such as the IzoT Commissioning Tool (CT) and then export the device definitions from the IzoT Net Server or LNS Server to the SmartServer as described in Importing LON Devices from IzoT Net Server or IzoT CT using IzoT Net Exportan LNS Network with IzoT CT. This section consists of the following:

...

1. Define the device interfaces for the devices to be discovered as described in /wiki/spaces/TEMP/pages/2951230 Collecting or Creating Device Definitions.
   
   
2. For BACnet device discovery, you need to enable BACnet using the BACnet Configuration page as described in (Optional) Setting up Add a BACnet Interface.
   
   

3. Define CMS device types for the devices to be discovered as described in Defining Device Types.
   

   Note
   Note: If you import device type definition files (.dtp file) prior to device discovery, then only the datapoints that are defined in the package will be available in the CMS.

   
   

4. In the SmartServer CMS, click the Discover button () on the Devices widget.
   
   
   

   When you click the Discover button, the SmartServer initiates discovery for BACnet, LON, and Modbus devices. The SmartServer adds each discovered device that is not already defined in the SmartServer, first identifying or creating a CMS device type as follows:
   

   • If the SmartServer discovers a program ID in the device, the CMS searches for a CMS device type using the discovered program ID.  If the SmartServer finds multiple CMS device types with the same program ID, the SmartServer uses the first one found with a the default property set to true, and if there are no default device types the SmartServer uses the first device type found with the matching program ID.
   • If there is no matching CMS device type but there is an XIF file with a matching program ID, the SmartServer creates a CMS device type for the XIF file with the same name as the XIF file.
   • If there is no matching CMS device type or XIF, the SmartServer creates a CMS device type for the driver/program ID pair named <driverName>-<programID> and assigns it to the device. For example, if a device is discovered with a program ID of 9FFF:FF05:0184:0460, and there is no CMS device type or XIF file for the program ID, the CMS creates a new device type called LON-9FFF:FF05:0184:0460.

   Device discovery remains active from the time you start discovery until 3 minutes pass without a discovery event. 

   The SmartServer creates a name for each discovered device that is not already defined in the SmartServer using the following naming format: Discovered-<deviceType>-<installCode>-<instance>, where

   • <devicetype> is the CMS device type name assigned above
   • <installCode> is the last five hex digits of the unique ID
   • <instance> is the instance number for this device type/install code pair (ordinal starting at 1 for each CMS device type/install code and increments forever without re-use for each CMS device type/install code)

   For example, if three devices are discovered for the LON-9FFF:FF05:0184:0460 device type with unique IDs ending in 07F07, 07F08, and 07F09, then the three devices will be named:

   • LON-9FFF:FF05:0184:0460-07F07-1
   • LON-9FFF:FF05:0184:0460-07F08-1
   • LON-9FFF:FF05:0184:0460-07F09-1
   
   
5. Once the device discovery is completed, you can provision the devices using the CMS Devices widget as described in Provisioning, Deprovisioning, and Replacing Devices.
   

Creating Devices

You can manually create devices as described in this section, and you can manually bulk create devices as described in Creating Devices in Bulk. 

...

1. With SmartServer IoT 2.7 or higher, to create devices in bulk, click the Bulk Create button () on the Devices widget.
   
   
   
   or
   
   Click the Action button () on the Devices widget and select the Bulk Create Devices action.
   
   
   
   
2. Enter the edge device properties as appropriate, including:
   
   
   • Name
   • Count
   • From
   • Context – provides a digital representation of a real world region, area, or space, available with SmartServer 2.8 and higher
   • Select a category (Segment Controller or Edge Device)
   • Select a customer – not used with SmartServe 2.8 or higher
   • Latitude
   • Longitude
   • Timezone – used for Segment Controller
   
   
   
   
3. Click NEXT.
   
   
4. Enter the Segment Controller parameters as appropriate, including:
   
   
   • Asset Tag
   • Description
   
   
   
   or
   
   Enter the edge device properties as appropriate, including:
   
   
   • UID

     • For Modbus RTU (RS-485) devices, this field uses the form <channel type>:<logical address>, where the <channel type> is always 01 and the <logical address> is an 8-bit station address. 

       Example: for a Modbus RTU (RS-485) device at address 4, the UID is 01:4
       
       

     • For Modbus TCP devices, this field uses the form <channel type>:<IP address>[:<logical address>], where the <channel type> is always 02 and the <IP address> is an IPV4 address. The 8-bit [:<logical address>] is optional for a Modbus TCP device and only required if the target Modbus TCP device also resides at a specific Modbus logical address at this IP address.

       Example: for a Modbus TCP device at IP address 192.168.42.42 with a logical address of 3, the UID is 02:192.168.42.42:3

       
       
     • For BACnet, this field defines the Device Instance Number (also referred to as Device ID)
       
       Example: 0130055
       
       
   • Select a method (Manual Assignment or Guided Discovery)
   • Owner
   • Select a driver – BACnet, LON, IAP, or Modbus
   • Asset Tag
   • Description
   
   
   Manual Assignment or Guided Discovery
   
   
5. Click SAVE to bulk create the new devices.

...

You can import device definitions from a CSV file as described in this section.  If you have devices that were defined and commissioned using a tool based on the IzoT Net Server or LNS Server such as the IzoT Commissioning Tool, you can import the definitions from the IzoT Net Server or LNS Server as described in Importing LON Devices from IzoT Net Server or an LNS Network with IzoT CT using IzoT Net Export.  To import device definitions from a CSV file, follow these steps:

...