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

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

piercalderan — Sun, 18 Oct 2020 19:54:30 GMT

Hi, great job.

Everything works well.

A question: Is it possible to have a GUI (e.g. button) in Azurre to send C2D messages to Twin devices?

Thanks.

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

brikeler — Thu, 20 Feb 2020 15:27:44 GMT

Issues when I execute the "Build and run the application" section.

azsphere device wifi show-status returns the following (X's added for obscurity):

SSID : Verizon-SM-G920V-xxx

Configuration state : enabled

Connection state : connected

Security state : psk

Frequency : 2462

Mode : station

Key management : WPA2-PSK

WPA State : COMPLETED

IP Address : 192.168.43.218

MAC Address : 00:02:b5:03:xx:xx

When I run the application I get IOTHUB_CLIENT_CONNECTION_NO_NETWORK errors:

Remote debugging from host 192.168.35.1, port 49309
Setting Azure Scope ID 0ne000C7xxx
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_OK'.
SSID: Verizon-SM-G920V-xxx
Frequency: 2462MHz
bssid: 8e:45:00:96:35:19
[MCU] Updating device twin: {"ssid": "Verizon-SM-G920V-xxx"}
[Azure IoT Hub client] INFO: Reported state as '{"ssid": "Verizon-SM-G920V-xxx"}'.
[MCU] Updating device twin: {"freq": 2462}
[Azure IoT Hub client] INFO: Reported state as '{"freq": 2462}'.
[MCU] Updating device twin: {"bssid": "8e:45:00:96:35:19"}
[Azure IoT Hub client] INFO: Reported state as '{"bssid": "8e:45:00:96:35:19"}'.
[MCU] Updating device twin: {"versionString": "AvnetStarterKit-Hackster.io-V2.0"}
[Azure IoT Hub client] INFO: Reported state as '{"versionString": "AvnetStarterKit-Hackster.io-V2.0"}'.
[Azure IoT Hub client] INFO: AzureIoT_DoPeriodicTasks calls in progress...
[Azure IoT Hub client] INFO: IoT Hub connection is down (IOTHUB_CLIENT_CONNECTION_NO_NETWORK), retrying connection in 5 seconds...
[Azure IoT Hub client] IoTHubDeviceClient_CreateWithAzureSphereDeviceAuthProvisioning returned 'AZURE_SPHERE_PROV_RESULT_OK'.
[Azure IoT Hub client] INFO: AzureIoT_DoPeriodicTasks calls in progress...
[Azure IoT Hub client] INFO: IoT Hub connection is down (IOTHUB_CLIENT_CONNECTION_NO_NETWORK), retrying connection in 5 seconds...

LSM6DSO: Acceleration [mg] : -0.8540, -0.1220, 17.9340
LSM6DSO: Angular rate [dps] : 0.00, 0.00, 0.00
LSM6DSO: Temperature1 [degC]: 27.61
LPS22HH: Pressure [hPa] : 974.73
LPS22HH: Temperature2 [degC]: 25.28
[Azure IoT] Using HSM cert at /run/daa/eb6512e4-7083-4e68-a480-10eeed898ea4
[Azure IoT] Using HSM cert at /run/daa/eb6512e4-7083-4e68-a480-10eeed898ea4
[Azure IoT] Using HSM cert at /run/daa/eb6512e4-7083-4e68-a480-10eeed898ea4
[Azure IoT] Using HSM cert at [Azure IoT Hub client] IoTHubDeviceClient_CreateWithAzureSphereDeviceAuthProvisioning returned 'AZURE_SPHERE_PROV_RESULT_OK'.
[Azure IoT Hub client] INFO: AzureIoT_DoPeriodicTasks calls in progress...
[Azure IoT Hub client] INFO: IoT Hub connection is down (IOTHUB_CLIENT_CONNECTION_NO_NETWORK), retrying connection in 5 seconds...

I tried troubleshooting using the guide and conducted internet searches. The closest I could find is that this is somehow a Certificate issue, even though it registered in my IoT Hub. It may be related to time, but it is not clear how to set the time nor if it is actually the issue.

I am using Visual Studio 2019. Code was downloaded on 02/19/2020.

azsphere device show-os-version:

Your device is running Azure Sphere OS version 20.01.

Thank you.

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

brikeler — Thu, 20 Feb 2020 15:17:33 GMT

In the section "Update Initial Device Twin State by adding three userLed entries as shown below, ie."

userLedRed: false,

userLedGreen: false,

userLedBlue: true

I would suggest adding the necessary double-quotes at the beginning and end of the three keys listed. I copied from the article and kept getting failures not realizing I was missing the double-quotes in the key, even though they are displayed in the screenshot.

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

xeonaj — Wed, 30 Oct 2019 10:49:23 GMT

Breakpoint 1, main (argc=2, argv=0xbeffde74) at main.c:485

485 {

[Inferior 1 (process 43) exited normally]

The program 'AvnetStarterKitReferenceDesign.out' has exited with code 0 (0x0).

Version String: Avnet-Starter-Kit-reference-V1.0

Avnet Starter Kit Simple Reference Application starting.

LSM6DSO not found!

Closing file descriptors.

Application exiting.

Child exited with status 0

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

pmossel — Sun, 20 Oct 2019 01:12:48 GMT

Don't give up when something fails the first time. Revisiting the Avnet Demo Part 1 and 2, I was able to get Time Series Insights to display real sensor data!. When I tried one or two weeks ago, I was not able to get the gX, Gy and gZ in TSI but today it worked. Not sure what made it work this time, but I suspect (1) the small fixes to the Avnet Starter Kit source in GitHub, (2) working carefully through the steps again, (3) the Azure Sphere SDK updates (19.09), or the Visual Studio 16.3.5 "small fixes."

[View:/resized-image/__size/1600x839/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-2f1f1843-3061-4102-aa19-bc8b0ffa0f94/contentimage_5F00_191992.png:1600:839]

Cool stuff! Thanks Brian for reviewing the pain points and somehow making it work.

One thing changed in Azure on the "IoT Hub - IoT Devices - Device Details" blade since you did your screenshots: instead of "Connection String (primary key)" the caption is now "Primary Connection String."

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

ale4684 — Fri, 04 Oct 2019 09:42:31 GMT

Hi all,

first of all thanks for this nice tutorial.

Unfortunately I am not able to reach IoT Hub from my AVNET Azure Sphere MT3620, I can see the sensors data in the output window and a "IoTHubClient accepted the message for delivery" message.

I cannot see the IOTHUB_CLIENT_CONNECTION_OK message... any idea ? I've also tried to run your code as admin and checked Log in Azure, no data have sent to the cloud :-(

Below my iothub-diagnostics result and the output from debug in VS.

Thanks

Alessandro

C:\WINDOWS\system32>iothub-diagnostics "HostName=MT3620-IOTHUB.azure-devices.net;DeviceId=AvNetStarterKit;SharedAccessKey=*********************="

2019-10-04T09:07:59.981Z - info: *******************************************

2019-10-04T09:07:59.987Z - info: * Executing the Microsoft IOT Trace tool. *

2019-10-04T09:07:59.994Z - info: *******************************************

2019-10-04T09:07:59.998Z - info:

2019-10-04T09:07:59.998Z - info: --- Executing network tests ---

2019-10-04T09:08:00.035Z - info:

2019-10-04T09:08:00.037Z - info: Starting DNS resolution for host 'www.microsoft.com'...

2019-10-04T09:08:00.101Z - info: --> Successfully resolved DNS to 92.122.253.175.

2019-10-04T09:08:00.104Z - info:

2019-10-04T09:08:00.114Z - info: Pinging IPV4 address '92.122.253.175'...

2019-10-04T09:08:00.156Z - info: --> Successfully pinged 92.122.253.175

2019-10-04T09:08:00.158Z - info:

2019-10-04T09:08:00.170Z - info: Sending https request to 'https://www.microsoft.com/'

Remote debugging from host 192.168.35.1

Version String: Avnet-Starter-Kit-reference-V1.0

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.

SSID: FASTWEB-6VNDPL

Frequency: 2437MHz

bssid: 94:91:7f:12:86:90

[MCU] Updating device twin: {"ssid": "FASTWEB-6VNDPL"}

[Azure IoT Hub client] INFO: Reported state as '{"ssid": "FASTWEB-6VNDPL"}'.

[MCU] Updating device twin: {"freq": 2437}

[Azure IoT Hub client] INFO: Reported state as '{"freq": 2437}'.

[MCU] Updating device twin: {"bssid": "94:91:7f:12:86:90"}

[Azure IoT Hub client] INFO: Reported state as '{"bssid": "94:91:7f:12:86:90"}'.

[MCU] Updating device twin: {"versionString": "Avnet-Starter-Kit-reference-V1.0"}

[Azure IoT Hub client] INFO: Reported state as '{"versionString": "Avnet-Starter-Kit-reference-V1.0"}'.

[Azure IoT Hub client] INFO: AzureIoT_DoPeriodicTasks calls in progress...

LSM6DSO: Acceleration [mg] : -0.1220, -0.3660, 14.3960

LSM6DSO: Angular rate [dps] : 0.00, 0.00, 0.00

LSM6DSO: Temperature [degC]: 26.36

LPS22HH: Pressure [hPa] : 1013.81

LPS22HH: Temperature [degC]: 23.25

LSM6DSO: Acceleration [mg] : 8.2960, -17.0800, 993.0800

LSM6DSO: Angular rate [dps] : 0.07, -0.07, 0.00

LSM6DSO: Temperature [degC]: 26.41

LPS22HH: Pressure [hPa] : 1013.78

LPS22HH: Temperature [degC]: 23.29

[Info] Sending telemetry: {"gX":"8.2960", "gY":"-17.0800", "gZ":"993.0800", "pressure": "1013.78", "aX": "0.07", "aY": "-0.07", "aZ": "0.00"}

[Azure IoT Hub client] INFO: IoTHubClient accepted the message for delivery

LSM6DSO: Acceleration [mg] : 8.6620, -16.8360, 992.9580

LSM6DSO: Angular rate [dps] : 0.07, -0.07, 0.00

LSM6DSO: Temperature [degC]: 26.48

LPS22HH: Pressure [hPa] : 1013.80

LPS22HH: Temperature [degC]: 23.31

[Info] Sending telemetry: {"gX":"8.6620", "gY":"-16.8360", "gZ":"992.9580", "pressure": "1013.80", "aX": "0.07", "aY": "-0.07", "aZ": "0.00"}

[Azure IoT Hub client] INFO: IoTHubClient accepted the message for delivery

LSM6DSO: Acceleration [mg] : 8.5400, -17.2020, 993.2020

LSM6DSO: Angular rate [dps] : 0.07, -0.07, 0.00

LSM6DSO: Temperature [degC]: 26.43

LPS22HH: Pressure [hPa] : 1013.81

LPS22HH: Temperature [degC]: 23.35

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

bwilless — Mon, 09 Sep 2019 19:21:30 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

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

mark_sample — Thu, 05 Sep 2019 22:02:10 GMT

Hello, I got as far as hitting the "Remote GDB Debugger" and I got the following output.

Remote debugging from host 192.168.35.1

Version String: Avnet-Starter-Kit-reference-V1.0

Avnet Starter Kit Simple Reference Application starting.

LSM6DSO Found!

LPS22HH not found!

Failed to read LSM22HH device ID, exiting

Closing file descriptors.

Application exiting.

Child exited with status 0

I think I did all the edits correctly. Tried resetting the board. Tried cycling the USB connection. No luck. Do you think I have a hardware issue with the board because it can't communicate with the LPS22HH barometer sensor?

Thanks,

Mark

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

silver2row — Fri, 16 Aug 2019 04:49:01 GMT

Hello,

Me again. I followed along. Nice! The "dirty details" section was fun to read after all that complicated back and forth.

Seth

P.S. Keep up the work, man. Keep 'em comin'.

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

tantrantho — Sun, 28 Jul 2019 21:30:02 GMT

Copying application to the device

Device would not sideload app: Application manifest Capabilities field 'AllowedConnections' or 'AllowedApplicationConnections' is not parseable (DeviceClientException)

Got this error message. What could it be the cause of this error?

Thank you,

Tan

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

Sean_Miller — Sat, 27 Jul 2019 20:58:53 GMT

Nice guide.

A few things:

When setting up the IoT hub, I had to visit the Size and Scale tab to select the Free Tier. Otherwise, it appeared it would charge $25 a month.

Instead of clicking "Add" to add a device to my IoT hub, I had a "New" button instead. It appears this has changed on the portal since this guide was made. Everything worked the same, though.

When I go to set up the Time Series Insights, It states my estimated costs are $150/month. I'd love to include this in my project, but I'm reluctant to proceed at that cost, so I skipped down to the part in the guide that shows you how to delete your resource group.

See ya',

Sean

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

eklime — Sat, 27 Jul 2019 17:22:20 GMT

Hi there,

I walk throughout the steps and it didn't work for me. I have Azure Sphere 19.05 version.

I got stuck on step "IOTHUB_CLIENT_CONNECTION_OK"

I do not see any information about that - like device not trying to connect to IoT Hub.

I do not see any errors in debug and device is connected to the Internet.

What could be wrong?

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

DAB — Thu, 09 May 2019 18:44:43 GMT

Nice detailed walk through.

DAB