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:

Preparation

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

Open the SmartServer Configuration page as described in Accessing the SmartServer IoT Configuration Page.
Clear the SmartServer databases.
Use the SmartServer LON Configuration page to enable the RNI for your Lon[n] device connected to your test network.
Click the CMS tab. Login 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. Configure your CMS dashboard by following the steps below.

Customize your dashboard selecting the following widgets to be displayed on your dashboard:
1. Devices
2. Alarms and Events (With SmartServer 3.4 and prior, this widget was called Alarms.)
3. Datapoint Properties
4. Device Types
5. Datapoints (With SmartServer 3.3 and prior, this widget was called Datapoint Browser.)
Import the following .xml files using the SmartServer CMS:
1. cps.xml
2. enums.xml
3. fps.xml
4. nvs.xml
  
  A series of blue toast notifications in the upper-right area will appear indicating that these files were imported successfully. You can dismiss these messages.
Import the following .png and .xif files using the SmartServer CMS:
1. DAC.png
2. DspSpController.xif
3. VAVsim6000.XIF
4. DAC6000.XIF
5. VAV2.png
  
  A series of blue toast notifications in the upper-right area will appear indicating that these files were imported successfully. You can dismiss these messages.
Use the Devices Types widget to create a package, which includes XIFs, PNG, and the definition of these device types. Doing so creates a DTP file that can be reused in future projects that use these device types.
Optionally, click a device's Action button () on the Device Types widget and select the Edit action to assign one of the imported .png images.
Optionally, you can create a system with one DAC device, and three simulated VAVs. To do, go to the SmartServer Support folder and import the file called VAV Sim External Devices.csv. You must delete what does not exist on your bench and modify the UIDs to match your target network.
For each imported device, use the Devices widget to add and save the UIDs for each EVB board.
Provision the target devices using the Devices widget.

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.

Browser not supported