Building and Managing the Example Network

In this section, you will use the SmartServer IoT CMS to first import resources associated with the example network, and then create and provision actual devices.  To follow these steps you should have two or more FT 5000 or FT 6050 EVBs networked and loaded with the provided Simulation applications, as described in Setting up an Internal Application Program Example Network.

This section consists of the following:


To ensure consistent results, you need to restore your SmartServer IoT to a known starting condition. If you are not clear about the starting condition of the SmartServer, follow these steps:

  1. Use putty.exe or a terminal emulator of your choice to connect by SSH or Serial console (settings: 115200-8-N-1). 

  2. Login as user apollo with the password marked on the back of the unit, or whatever you changed it to previously.

  3. Type: sudo apollo-reset normal [pwd] . If you connect to the SmartServer console using SSH, you will be prompted to continue shortly after the re-image script starts.

  4. The re-image script will take about 8-10 minutes to complete and concludes with a reboot of the SmartServer.

  5. Use the SmartServer IoT configuration interface to enable the RNI for your Lon[n] device connected to your test network.

  6. Click the CMS tab to log in to the SmartServer CMS as user apollo.

Configuring Your CMS Dashboard

When you connect to the CMS for the first time after apollo-reset, most of the Widgets will be configured to the user apollo dashboard.

  1. Click the Settings button () and select the Edit action to /wiki/spaces/TEMP/pages/44631776.

  2. Select the following widgets to be displayed on your dashboard:
    1. Devices
    2. Alarms and Events (previously called Alarms)
    3. Datapoint Properties
    4. Device Types 
    5. Datapoints (previously called Datapoint Browser)

  3. Click the Settings button () and select the Edit action to resume normal dashboard activity. 

  4. On the Device Types widget, click the Import button ().  

    You will see a shaded area that can be used for drag-and-drop actions.

  5. Click the DROP FILE HERE area. You will see a file explorer dialog that you can use to select a file. As shown in the following figure, a file explorer dialog can be used to navigate to the folder SmartServer Support under the local copy of the Izot/SmartServer-IoT repo. 

    In this step, you are importing the four files from the resource report by dragging-and-dropping to the Device Types widget DROP FILE HERE area.

  6.  Click IMPORT FILE.

    A series of blue toast notifications in the upper-right area will appear indicating that these files were imported successfully. You can dismiss each of these messages.

  7. On the Device Types widget, click the Import button () again and then click the DROP FILE HERE area. This time, drag each file with .png and .xif extensions to the DROP FILE HERE area and then click IMPORT FILE.

  8. Allow time for the CMS to create device types. For each XIF file imported, it will take 20-30s to complete the device type creation. You may need to scroll to the toast notification area to see this, but you are looking for messages confirming the operation is completed/loaded.

  9. Click BACK to return to the Device Types widget. For each device type shown, you can optionally click the Action button and assign one of the imported .png images. 

  10. Use the Devices Types widget to create a package which includes XIFs, PNG, and the definition of these device types. To do so, click the Select All button () to select all of the device types, and then click Action button () and select the Export Selected Device Types action. Doing so creates a DTP file that can be reused in future projects that use these device types.

  11. Using the Devices widget, click the Action button () and select the Import Devices action. In the SmartServer Support folder, there is a file VAV Sim External Devices.csv  you can use to create a system with one DAC device, and three simulated VAVs. You must delete what does not exist on your bench and modify the UIDs to match your target network.  

  12. For each imported device, use the Devices widget to add the UIDs for each EVB board:
    1. Click the device in the list.
    2. Click NEXT to edit and save the UIDs as they exist in your system.

  13. Select the target devices by clicking their icons, and then click the Devices widget Action button () and select the Provision Selected action.

At this point, you have the external LON devices provisioned and ready, so you can continue developing an internal device.  Each device icon in the Devices widget should have a green fill. 

Next Step

Return to Internal LON Application Example.