...
Set up the hardware platform as described in https://voxelbotics.atlassian.net/wiki/x/BIBHKg.
Install the release build onto the hardware platform as described in Installing SOM-NRF9151 Images.
3. Test Plan
3.1.
| Anchor | ||||
|---|---|---|---|---|
|
Validate the output of the SOM-NRF9151 application to the console device, as described in https://voxelbotics.atlassian.net/wiki/x/GwBCKg.
...
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.
From the nRF9151 console, confirm that the device data have been sent to the cloud:
Code Block [00:03:19.069,335] <inf> app_event_manager: DATA_EVT_DATA_READY [00:03:19.073,059] <inf> app_event_manager: DATA_EVT_DATA_SEND_BATCH [00:03:19.073,974] <inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS
In the Device Data card on the nRF Cloud, verify that the Location attribute has just been updated recently and has a proper value:
Click the Show Location card icon to see the graphical representation of the device location:
Click the View historical data icon and select appropriate time interval to see device location history:
...
Log into the NRF cloud account, go to the device page, and select the
"Info” level on the Logs device card:
Switch to the Log card on the NRF Cloud interface, then click the clock icon on the bottom right, then click the newly appeared
"Get Data"button:
Verify that the Log card was filled in with log data with
"3 - inf"log level:
Select the “
Disable"log level in the Log card on the NRF cloud interface.
3.18.
| Anchor | ||||
|---|---|---|---|---|
|
Validate FOTA update for the asset tracker v2 application as described in Performing FOTA updates on SOM-NRF9151.