Versions Compared

Version Old Version 8 New Version 9
Changes made by

Dmitry Starchenko

Dmitry Starchenko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Check the board uuid from the nRF9151 console (it is assumed that the nRF Device provisioning procedure has been performed earlier):

    Code Block
    uart:~$ nrf_provisioning uuid
50343959-3733-4c71-806b-202470cee0bf

  2. Check that the board has successfully connected to the cloud over LTE:

    Code Block
    [00:00:02.824,615] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:04.110,168] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
[00:00:15.095,916] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:15.234,283] <inf> cloud_module: DEVICE CERTIFICATE IS PRESENT
[00:00:15.236,907] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:00:15.237,426] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:15.237,915] <inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED
[00:00:22.080,871] <inf> net_mqtt: Connect completed

  3. Login to the nRF Cloud and go to the DEVICE MANAGEMENT / Devices page. Find the board by the uuid ID and open the board page.

  4. Click the Manage Cards button and check the Device Data checkbox so that the Device Data card is displayed on the board page.

  5. In the Device Data card, check the Last connected attribute to make sure that the board has recently connected to the cloud.

  6. From the nRF9151 console, confirm that the Battery sensor has been read successfully:

    Code Block
    [00:00:27.001,281] <inf> app_event_manager: SENSOR_EVT_FUEL_GAUGE_READY

  7. Wait 110 seconds for the device data to be updated on the cloud. The default timeout of 110 seconds can be reduced for convenience: click the View Config button, then Edit Configuration. If activeMode is false then the timeout is no greater than movementResolution, otherwise, it is no greater than activeWaitTime.

  8. From the nRF9151 console, confirm that the device data have been sent to the cloud:

    Code Block
    [00:02:16.997,283] <inf> app_event_manager: DATA_EVT_DATA_READY
[00:02:17.002,197] <inf> app_event_manager: DATA_EVT_DATA_SEND_BATCH
[00:02:17.002,868] <inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS

  9. In the Device Data card on the nRF Cloud, verify that the Battery attribute has just been updated and has a proper value:

    image-20250228-142808.png

  10. Click the Show Battery card icon to see the graphical representation of the battery values on the time scale:

    image-20250228-143139.png

  11. Click the View historical data icon and select appropriate time interval to see the battery status history:

    image-20250228-143543.png

3.13.
Anchor
ntga0zbd
ntga0zbd
Ambient Temp Sensor

...

Test

  1. Check the board uuid from the nRF9151 console (it is assumed that the nRF Device provisioning procedure has been performed earlier):

    Code Block
    uart:~$ nrf_provisioning uuid
50343959-3733-4c71-806b-202470cee0bf

  2. Check that the board has successfully connected to the cloud over LTE:

    Code Block
    [00:00:02.824,615] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:04.110,168] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
[00:00:15.095,916] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:15.234,283] <inf> cloud_module: DEVICE CERTIFICATE IS PRESENT
[00:00:15.236,907] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:00:15.237,426] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:15.237,915] <inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED
[00:00:22.080,871] <inf> net_mqtt: Connect completed

  3. Login to the nRF Cloud and go to the DEVICE MANAGEMENT / Devices page. Find the board by the uuid ID and open the board page.

  4. Click the Manage Cards button and check the Device Data checkbox so that the Device Data card is displayed on the board page.

  5. In the Device Data card, check the Last connected attribute to make sure that the board has recently connected to the cloud.

  6. Wait 110 seconds for the device data to be updated on the cloud. The default timeout of 110 seconds can be reduced for convenience: click the View Config button, then Edit Configuration. If activeMode is false then the timeout is no greater than movementResolution, otherwise, it is no greater than activeWaitTime.

  7. From the nRF9151 console, confirm that the device data have been sent to the cloud:

    Code Block
    [00:02:16.997,283] <inf> app_event_manager: DATA_EVT_DATA_READY
[00:02:17.002,197] <inf> app_event_manager: DATA_EVT_DATA_SEND_BATCH
[00:02:17.002,868] <inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS

  8. In the Device Data card on the nRF Cloud, verify that the Temperature attribute has just been updated and has a proper value:

    image-20250228-144540.png

  9. Click the Show Temperature card icon to see the graphical representation of the temperature values on the time scale:

    image-20250228-144324.png

  10. Click the View historical data icon and select appropriate time interval to see the temperature history:

    image-20250228-144446.png

...