Skip to content

Latest commit

 

History

History
124 lines (70 loc) · 6.23 KB

Lab-4.md

File metadata and controls

124 lines (70 loc) · 6.23 KB

Lab-4: Visualize real world data on Azure IoT Central

Goals

  • Hands-on with Azure IoT Central configuration
  • Understand the basic feature of IoT Central offered as a IoT SaaS solution
  • Get familiar with I2C API to connect to external sensor device
  • Use Azure Sphere and Azure IoT Central work together to build a secured end-to-end solution with telemtery collection, visulization and remote control ability.

Steps

  1. After connect Azure Sphere development board to your PC, enable device debug and disable OTA in Azure Sphere utility by:

    azsphere device enable-development

  2. Make sure WiFi credential is configured and Azure Sphere is connected to the WiFi Access Point. If Lab-2 is skipped, please follow Step 1) and 2) in Ove-The-Air upgrade to configure the WiFi ssid and password.

  3. Follow Setup IoT Central page to setup cloud resources, the key steps are:

    • Login with your Microsoft account or Azure account (if you have)
    • Select 'Custom application (Legacy)' in application template drop box
    • Select 'Free' pricing plan when you do not have a Azure account. The app will last for 7 days.
    • Upload tenant CA certificate to IoT Central and finish Proof of Procession

  4. Go to your application in Azure IoT Central and click Create Device Templates on the home page, select Custom to start a blank template. Give a name to your template and click Create button.

  5. Click + New button and select Telemetry

    1. Set the Display Name and Field Name to Temperature. The Field Name must exactly match the name in the sample code, so this value is case-sensitive. Set Units to Degrees, and set the Minimum Value and Maximum Value to -40 and 85, respectively. Then click Save.

    2. Set one more telemetry Humidity, set range and unit to 0% to 100%

    3. Set one more telemetry Pressure, set range and unit to 300 to 1100 hPa

  6. Click + New button and select Event, Set the Display Name and Field Name to ButtonPress. Then click Save.

  7. On the left Side Navigation select Devices, click + to add a new device, and select Real from the drop-down menu. A dialog will prompt to ask for Device ID and Name.

  8. In an Azure Sphere Developer Command Prompt, type the following command:

    powershell -Command ((azsphere device show-attached)[0] -split ': ')[1].ToLower()

    Copy the lowercase device ID and paste it into the Device ID field of the Create New Device dialog box. Device name will be changed automatically using the device ID appended. Click Create button.

  9. Open AzureIoT project in .\azure-sphere-samples\Samples\AzureIoT folder. If you're using AVNET_MT3620_SK board, follow Step 4 in Lab-1 to modify hardware definition file first.

  10. Before build the project, there're three key information you need provide to the applicaton in app_manifest.json file.

    • The Tenant ID for your Azure Sphere device
    • The Scope ID for your Azure IoT Central application
    • The IoT hub URL for your Azure IoT Central application

    Tenant ID can be retrieve from Azure Sphere command line utility by azsphere tenant show-selected

    Scoep ID can be found in the Administration/Device connection page of IoT Central

    To get IoT Hub URL, there is a assist tool in .\azure-sphere-samples\Samples\AzureIoT\Tools\win-x64 folder can help. In Azure Sphere command line utility, go to above location, and run ShowIoTCentralConfig.exe, input 'n' and provide below information, the tool will output the IoT Hub URL.

    1. Scope ID
    2. device ID
    3. device primary key (the key can be found by enter CONNECT dialog on the top right of the device page)

    Fill these information in app_manifest.json file as below:

  11. If you're using MT3620_RDB, connect BME280 sensor board to I2C pins of ISU2 on H4. GND and 3V3 can be provided via H3.

  12. If you're using AVNET_MT3620_SK, connect BME280 sensor board to I2C pins of ISU2 on MikoBUS header as below picture shows.

  13. Grant ISU2 I2C access permission to applicaiton in app_manifest.json.

  14. By default the Azure IoT sample project send simulated temperature sensor data to Azure IoT. Hack the code to visualize your real world data!

    BME280 driver is provided in Code/Lab-4 folder. There're only two API exposed in bme280_uesr.h will be needed by your application.

    int bme280_component_config (int isu_port);
int bme280_component_getdata(struct bme280_data* pData);

    Update CMakeLists.txt file to add bme280_driver.c and bme280_driver.c to the ADD_EXECUTABLE before build.

  15. After code hack, select GDB Debugger (HLCore) and Press F5 to build and run the applicaiton. Go to the device dashboard to check your data.

  16. (Optional) If you're using AVNET_MT3620_SK and you do not have a BME280 sensor board. You can use the LSM6DSO and LPS22H sensor to send accelemeter, gyrometer and pressure data to IoT central. In Step 5, you need add gX, gY, gZ, aX, aY, aZ and pressure as telemetry in device template.

    Drivers and hint are provided in Code/Lab-4/alternative. Also, you need update CMakeLists.txt file to add i2cDevice.c, lps22hh_reg.c and lsm6dso_reg.c

Read more