It’s been around 4 months since we release our official hardware and SDK as v1.0 last September right on Ignite 2017. In that event, the MXChip IoT DevKit was used on a couple of Azure IoT break-out and keynote sessions for demonstrations and together with announcement with new services released such as IoT Hub Device Provisioning Service.
IoT Application Development is naturally more complicated than regular application development, in that even the simplest E2E IoT application involves a long chain from device layer, to communication layer, then to the cloud and beyond. This makes the development especially the testing and debugging difficult.
After a month work of stabilizing the code, fixing bugs and adding more samples, we are happy to release the v1.0.0 for our IoT DevKit. You can download the latest package by following the get started guide or from direct link here.
Have you ever wanted to try IoT development but had no device at hand? From a recent survey, more than 70% developers who come to learn Azure IoT don’t have a physical device so that they can not go on from the beginning.
Debugging Arduino application is a challenging task as the debugging feature has not been officially supported in Arduino IDE.
Many modern IDEs have debug support that developers are used to, using Breakpoints, Steps, Call Stack, Watch, Local/Global Variables, etc. Arduino developers often have to explore many alternative methods and tools to debug Arduino code.
This post first explains the different connection strings in Azure IoT Hub, then gives a simple IoT Hub solution Integrate Azure Functions with Azure IoT Hub using all three connection strings.
There’re three types of connection strings in Azure IoT Hub:
IoT Hub connection string
IoT Hub’s Event Hub-compatible connection string
IoT Hub device connection string
IoT Hub Connection String
Used mainly for device registration/un-registration.