Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

Prasham — Wed, 15 Jun 2022 13:38:46 GMT

great resource!!! really helped to start with iot

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

Prasham — Wed, 15 Jun 2022 11:09:27 GMT

After entering the API tokens my cmd Exists what shall I do?

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

tongd2002 — Tue, 10 Nov 2020 02:30:44 GMT

Today it suddenly stopped working. It connects to wifi, but does not seem to be sending any data, nor receive the RGB LED command from IoT Central. The LCD screen is blank. Any idea please?

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

andyhawker — Mon, 27 Apr 2020 13:07:59 GMT

Hi,

Are there any alternatives to using ShowIoTCentralConfig.exe? I am attempting this demo with a Linux machine and I can get all the info I need except the IoT Hub URL. Is it possible to get this info via CLI etc?

Thanks,

Andy

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

brikeler — Thu, 20 Feb 2020 18:35:02 GMT

I am receiving 'AZURE_SPHERE_PROV_RESULT_PROV_DEVICE_ERROR' error.

I have followed the troubleshooting guide and verified my network connectivity, port accessibility for the URLs, and validated my build_options.h and app_manifest.json are updated as listed.

Debug Output (X's to obscure items):

Remote debugging from host 192.168.X.X, port 62737
Setting Azure Scope ID 0ne000XXXXX
Avnet Starter Kit Simple Reference Application starting.
LSM6DSO Found!
LPS22HH Found!
LSM6DSO: Calibrating angular rate . . .
LSM6DSO: Please make sure the device is stationary.
LSM6DSO: Calibrating angular rate complete!
Opening Starter Kit Button A as input.
Opening Starter Kit Button B as input.
[Azure IoT] Using HSM cert at /run/daa/eb6512e4-7083-4e68-a480-10eeed898ea4
[Azure IoT Hub client] IoTHubDeviceClient_CreateWithAzureSphereDeviceAuthProvisioning returned 'AZURE_SPHERE_PROV_RESULT_PROV_DEVICE_ERROR'.
ERROR: Failed to set up IoT Hub client
ERROR: Verify network connection and Azure Resource configurations
SSID: Verizon-SM-G920V-XXXX
Frequency: 2462MHz
bssid: 8e:45:00:96:35:19
[MCU] Updating device twin: {"ssid": "Verizon-SM-G920V-XXXX"}
[Azure IoT Hub client] ERROR: client not initialized
[MCU] Updating device twin: {"freq": 2462}
[Azure IoT Hub client] ERROR: client not initialized
[MCU] Updating device twin: {"bssid": "8e:45:00:96:35:19"}
[Azure IoT Hub client] ERROR: client not initialized
[Azure IoT Hub client] INFO: AzureIoT_DoPeriodicTasks calls in progress...
[Azure IoT Hub client] IoTHubDeviceClient_CreateWithAzureSphereDeviceAuthProvisioning returned 'AZURE_SPHERE_PROV_RESULT_PROV_DEVICE_ERROR'.
ERROR: Failed to set up IoT Hub client
ERROR: Verify network connection and Azure Resource configurations

LSM6DSO: Acceleration [mg] : -0.7320, -0.6100, 17.9340
LSM6DSO: Angular rate [dps] : 0.00, 0.00, 0.00
LSM6DSO: Temperature1 [degC]: 36.52
LPS22HH: Pressure [hPa] : 975.31

Any ideas?

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

brikeler — Thu, 20 Feb 2020 18:30:58 GMT

In the section:

To review. The modifications we made to the source code . . .

We enabled the IOT_HUB_APPLICATION define in build_options.h

Change "IOT_HUB_APPLICATION" to "IOT_CENTRAL_APPLICATION"

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

mtrobregado — Thu, 05 Dec 2019 13:04:32 GMT

I try to create a new IOT Central Application Dashboard. Everything is different now creating a new Azure IOT Central Dashboard.

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

xeonaj — Sun, 03 Nov 2019 06:54:19 GMT

hey [mention:ef292582443548cc97f58584df5b81e8:e9ed411860ed4f2ba0265705b8793d05] My IoT Central shows missing data!

It worked successfully yesterday but not today!

[Azure IoT Hub client] INFO: IoT Hub connection is down (IOTHUB_CLIENT_CONNECTION_NO_NETWORK), retrying connection in 5 seconds...

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

xeonaj — Sat, 02 Nov 2019 10:53:44 GMT

COMPLETED THIS TUTORIAL!

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

arufi — Sun, 27 Oct 2019 14:19:30 GMT

I am getting the following error when trying to create the string in PowerShell

Azure IoT DPS Symetric Key Generator v0.3.3

ERROR: You haven't defined neither the master key or device key.

PS C:\WINDOWS\system32>

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

mtrobregado — Thu, 10 Oct 2019 11:08:57 GMT

Hi,

I already made my own IOT Central Dashboard and I have been using it for about 10 days. I bookmarked it at google chrome. But today I go to IOT Central and it says "The page you requested can't be found". I go to https://apps.azureiotcentral.com/ and I can not find my work. Why does this happen. My subscription is pay as you go and I have 200$ credit.

Regards,

Markel

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

mtrobregado — Mon, 30 Sep 2019 11:44:19 GMT

From IOT Central can I send a value for example 3000 to my Azure Sphere Board? From what I see is always sending sensor data from Azure Sphere Board to IOT Central.

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

kedar1 — Sun, 29 Sep 2019 07:07:02 GMT

Hello,

I have purchased an 1,3" OLED from Aliexpress.
Tested OK on Rpi using Python and SH1106 driver.

Is there anybody who is able to port SD1306 driver to work with SH1106 on Azure Sphere?

Thanks

Radek

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

tmandin — Fri, 20 Sep 2019 14:26:41 GMT

Hi Peter,

I wanted to try the "advanced" tutorial with the relay and the OLED. I soldered my OLED to my board, and afterwards this demo stopped working for me. I get the following message:

Real Time Core disabled or Component Id is not correct.
The program will continue without showing light sensor data.
OLED found!
ERROR: platform_read(write step): errno=110 (Operation timed out)
LSM6DSO not found!
Closing file descriptors.
Application exiting.

Child exited with status 0

Any thoughts on what is up? Perhaps a bad soldering job? I am no expert.

RE: Avnet's Azure Sphere Starter-Kit (Out of Box Demo) Part 3 of 3

bwilless — Mon, 09 Sep 2019 19:21:56 GMT

Title “LPS22HH Not Found, GitHub code update”

Azure Sphere developers,

Some of you have run into issues with your Starter Kits where the LPS22HH sensor could not be read. When the original Out of Box application encountered this error, it would try to read the WhoAmI value from the device 10 times, and if it never clears, then the application would exit. We realize that this behavior has stopped many of you from progressing, and to that end I’ve modified the application code to continue to run if the LPS22HH device can’t be read. In this case, there is debug output stating that the error was encountered, and the code will default to LPS22HH pressure and temperature reading to zero. Please pull the latest changes from the GitHub repository to get these latest changes.

The bullets below describe the changes . . .

· Detect LPS22HH failures (it did this already)

· On LPS22HH failure, don’t exit, but instead . . .

o Output debug

§ Failed to read LPS22HH device ID, disabling all access to LPS22HH device!

§ Usually a power cycle will correct this issue

o Skip over the code that reads the LPS22HH sensor

o Default the LPS22HH readings to zero

o Output debug when reading all sensors

§ LPS22HH: Pressure [hPa] : Not read!

§ LPS22HH: Temperature [degC]: Not read!

o LPS22HH sensor variable are still sent as telemetry but are always 0

I’m exploring other options to programmatically clear this issue, but since I can’t reproduce this issue, it will be difficult to test the “bad path” to see if my changes clear the issue.

I’ve seen this issue myself a few times when I first started working with the Starter Kit. The only way I’ve found to clear the issue is to power cycle the starter kit. Since the power cycle clears the error, it’s been very difficult to debug this issue. If you have a starter kit that encounters this issue frequently, please send me a private message so that maybe we can utilize your hardware to understand the root cause of the issue.

Thanks for the help,

Brian