Any remote deployment blog for Azure Sphere?

This is the one I used:

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

I the example code, you can modify the timing around Line 20 of build_options.h.  I believe the default is 1 second.  I made mine longer because the free trial was over and it can rack up quickly when developing.

// Defines how quickly the accelerator data is read and reported
#define ACCEL_READ_PERIOD_SECONDS 5  //originally 1 (second) this is how often it sends messages.
#define ACCEL_READ_PERIOD_NANO_SECONDS 0

This value may not take decimals, though.

The communication strategy is to send a block of JSON versus streaming bytes through a websocket.  So, I'm not sure how much quicker you can get with this example.

See ya',

Sean

Thank You, I see that it sends data within seconds but the IoT Hub / Central telemetry data is plotted very slowly.

And have you got any Idea with cloud deployment I want to do it, I am trying different ways but till now nothing worked for me.

I'm not understanding this question:  "And have you got any Idea with cloud deployment I want to do it, I am trying different ways but till now nothing worked for me."

Can you rephrase it?

For info, here is my blog for the challenge - still under works:

https://www.element14.com/community/groups/azuresphere/blog/2019/10/17/avnet-azure-sphere-coke-drum-health-monitoring-iot-ai

It has some good code tweaks for additional components and external API data calls.

Sean

HEY GUYS I FIGURED IT OUT I WAS TOTALLY WRONG ABOUT SOMETHINGS BECAUSE I WASN'T ABLE TO SEE SOME EXPECTED OUTPUT I THOUGHT IT WASN'T WORKING IN FACT IT WAS!

Alphons,

Looks like you made some progress.  In general telemetry data showing up on IoT Central is slow.  We've looked into ways to improve the performance but have never found any way to make it faster.

Regarding deployments . . . .

Once you sideload your application onto your device, it will remain there until you remove or overwrite it, and it will automatically start on powerup.  So you could just move your device from your development environment to your deployment environment and it should work.  However, one of the nice features of Azure Sphere is the OTA updates.  I recommend you set that up, it's easy.  I don't have a blog for this feature, but plan to write one up in the future.

The instructions for OTA deployments is here: https://docs.microsoft.com/en-us/azure-sphere/deployment/create-a-deployment

Brian

In general telemetry data showing up on IoT Central is slow.  We've looked into ways to improve the performance but have never found any way to make it faster.

Yeah I tried it many times but didn't work!

Once you sideload your application onto your device, it will remain there until you remove or overwrite it, and it will automatically start on powerup.  So you could just move your device from your development environment to your deployment environment and it should work.

I wasn't aware of this I had done this in the first part of Out of the box demo but really forgot about it and I was stupidly searching how to do it.

The instructions for OTA deployments is here: https://docs.microsoft.com/en-us/azure-sphere/deployment/create-a-deployment

Yeah I had done the OTA deployments its fun and easy!