Devices Are Not Appearing

When the Discover button () shows that device discovery is complete, it means that the SmartServer is finished the process of looking for devices. However, it will still take some time for the SmartServer to fully add all of the devices. This process can take more than 10 minutes, after the Discover button appears with a line though it (), for all the devices to appear in the CMS Devices widget.

You may also need to run device discovery multiple times in order to discover all of the devices (particularly in the case of BACnet networks).

1. SmartConnect

   1. Make sure that the drivers for which you are running device discovery are enabled. By default, drivers are disabled in SmartConnect.
      
      

2. BACnet

   1. Make sure you enabled BACnet using the BACnet Configuration page prior to running a device discovery.

      1. Each time you run device discovery, the discovery process will create new devices for unknown devices, and check existing BACnet devices to make sure that the datapoint information has not changed. If it has, then a new device type will be created for these devices.  
         
         

3. Modbus

   1. Modbus protocol does not have a built-in way to discover Modbus devices, but the SmartServer can discover then if you specify a marker value in the MOD file.

   2. Verify that you configured the Modbus using the RS-485 Configuration page prior to running a device discovery.

   3. Verify that you imported the MOD file prior to running device discovery.
      
      

4. LON

   1. Review the following cautions pertaining to LON devices and DMM device discovery:

      1. Discovering previously installed LON devices

         If you discover and provision a previously installed LON device when using DMM, then the SmartServer may modify the configuration of the device. If the device is part of an operational system, then the system may no longer function as expected due to the change in the LON device configuration. Discovering and/or provisioning a discovered device may change the device's subnet/node IDs, and set the existing datapoint values to default value, and delete all existing connections to devices. In order to restore the site back to normal operation, perform one of the following:

         1. Restore the network using integration tool that was originally used to create the site network.

         2. Reconfigure discovered LON devices using the SmartServer CMS.

      2. Deleting LON devices

         Deleting a discovered LON device (using the Remove action in the Devices widget) will cause the SmartServer to try to decommission the device and set the subnet and device ID to 0 before deleting the device from the SmartServer. This process may cause a previously working device to stop working. In order to delete a discovered LON device, first make sure that the device is no longer connected to the network (e.g., FT channel), or disconnect the SmartServer from the network (such as disconnect the U60), and then delete the device in the CMS Devices widget. Performing a database reset will not affect the existing devices.

   2. Verify that you imported all device XIF files and any necessary Resource File Set XML files prior to running device discovery.

   3. Devices that appear in the CMS but are not working are generally devices in which the device XIF, or necessary Resource File Set XML files, were not imported prior to running device discovery. These devices are not usable.

      1. Delete these devices and the corresponding device types.

      2. Import the device XIF, or any necessary Resource File Set XML files, and re-run device discovery.