...

This section consists of the following:

...

1. Define the device interfaces for the devices to be discovered as described in Collecting or Creating Device Definitions.
   
   
2. For BACnet device discovery, you need to enable BACnet using the BACnet Configuration page as described in (Optional) 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 any discovered device that matches one of the included device types (XIF) will appear in the SmartServer CMS with only datapoints that are defined in the package. For BACnet, if a device type is not found, then a new BAC file will be created automatically (called datapoint discovery BAC file). For Modbus, only devices that match one of the MOD discovery files will appear in the SmartServer CMS. For LON, all discovered LON devices will appear in the SmartServer CMS, however, those that did not have a previously imported XIF will need to be removed.

   
   

4. /wiki/spaces/TEMP/pages/44041710Open the SmartServer CMS, Devices widget.

   Note
   Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 Expand button (  ).

   
   
   

5. Click the Discover button ().
   
   
   

   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
   
   

6. For LON, you can optionally press a service button on a device in the domain to be discovered. The LON driver will wait for a service message that is generated by the pressing of a service button. Next, the LON driver will read the domain index 0 configuration at the unique ID that is included in the service message, and if a domain is configured for domain index 0, then the LON driver will assign the configured domain ID as the LON domain ID to be discovered.
   
   

7. Once the device discovery is completed, you can provision the devices using the CMS Devices widget as described in Provisioning Devices.
   

   Note
   title For LON devices only
   If you are using IMM for LON devices then you are going to want to re-export (use iNex) to remove any additional devices not included in the IzoT CT/IzoT Net Server SmartServer IoT subsystem or child subsystem.

   
   

...

1. /wiki/spaces/TEMP/pages/44041710, Devices widget.

   Note
   Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 (  ).

   
   
   

2. Click the Create button ().
   
   
   
   

   The Create Edge Devices view appears.
   
   
   
   
3. Enter the device parameters as appropriate, including:
   
   • Name
   • Context – provides a digital representation of the physical world entities in the system with SmartServer 2.8 and higher
   • Select a method – Manual assignment or Guided discovery
     • For Manual assignment, you will need to select the driver type and device type, and define the UID.
     • For Guided discovery, press the service button for the LON device. The UID, driver type, and device type will be filled in through the guided discovery process.
   • Select a driver – BACnet, LON, Modbus, IAP, or custom driver name
   • Select a type of device

   • UID

     Info

     Each Modbus device that is added in the CMS must have a unique identifier (device UID). The UID is defined when a Modbus device is created using the SmartServer CMS in one of the following ways: Creating a single Modbus device Bulk loading multiple Modbus devices Importing devices from a file using a previously exported device CSV/DTD file  Importing device type information using a previously exported DTP file from the Device Types widget (see Defining Device Types)

     
     

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

       
       With SmartServer release 3.5 and higher, you can optionally specify the TCP port to be used for a Modbus TCP device using the form<channel type>:<IP address>[:<port>] [:<logical address>], where the <channel type> is 03 and the <IP address> is an IPV4 address. The [:<port>] parameter is optional for a Modbus TCP device and is only required if the target Modbus TCP device uses a port other than the standard Modbus TCP port (502). The 8-bit [:<logical address>] is also 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.
       
       
       • Examples:
         • Using the standard Modbus TCP port (502): 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 
           
           
         • Using a non-standard Modbus TCP port (1502): Modbus TCP device at IP address 192.168.42.42 with a logical address of 3, the UID is 03:192.168.42.42:1502:3
           
           
           
     • For BACnet, this field defines the Device Instance Number (also referred to as Device ID)
       • Example: 0130055
         
         
         
   • Tags
   • Description
   
   
   
   
4. Click SAVE.
   
   The new device appears on the Devices widget (e.g., DIO1 in the example below).
   
   
   
   
5. Provision the devices using the CMS Devices widget as described in Provisioning Devices.

...

1. /wiki/spaces/TEMP/pages/44041710, Devices widget.

   Note
   Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 (  ).

   
   
   

2. Click the Create button ().
   
   
   
   

   The Create Edge Devices view appears.
   
   
   
   
3. In the Count field, enter the number of devices to be created, and in the From field, enter the starting device number. (The Name field changes to Name Prefix.)
   
   
   
   
4. In the Name Prefix field, enter the prefix that is to be assigned to the name of device that is being created.
   
   
   
   
5. Enter the device parameters as appropriate, including:
   
   • Context (optional) – provides a digital representation of the physical world entities in the system with SmartServer 2.8 and higher
   • Select a method – Manual assignment or Guided discovery
   • Select a driver – BACnet, LON, Modbus, IAP, or custom driver name
   • Select a type of device
   • Tags (optional)
   • Description (optional)
     
     
     
     
6. Click SAVE. 
   
   The new devices appear on the Devices widget (e.g., TEST2, TEST3, and TEST4 in the example below).
   
   

...

Assigning a Device to a Context

With SmartServer 2.8 and higher, devices can be assigned to a context. A context provides a digital representation of the physical world entities in the system. Devices that are not assigned to a context appear with a yellow indicator on the device image . To assign a device to a context, perform the following steps:

...