I have always have had a sweet spot for GPS technology. Back in 2005 already, I did some projects with tracking vehicles using a ‘GPS mouse’ and smart phones with GPRS. A GPS was not built in by default in those devices. We used Bluetooth to connect. I still have warm feeling about what I managed to do back then…
Nowadays, GPS is available everywhere. Just count the number of GPS receives you have in your mobile devices, car or even your pets collar. Within my family we easily reach up to 12 systems with free and accurate global positioning.
I wanted to experiment with GPS over USB cable. So I was checking out this GPS receiver on Ali express with this promising title: “BEITIAN Auto-adapted baud rate USB GNSS GPS Receiver 1Hz 4M FLASH 5.0V Double-sided tape NMEA-0183 BN-85U better than BU-353S4”
I used a Sirfstar III chipset for GPS, fourteen years ago. I have no clue about the ‘BU-353S4’ or even the better ‘BN-85U’ 🙂
Let’s check out if this one just works OK as a reliable GPS receiver.
This year the new FutureTech event was organized for the first time. The focus is on innovative Microsoft technology. This event shows technology which you probably do not know off yet or which you do not use yet. But you will likely use within a year or so…
The CFS is available at sessionize.com and it closes december 31, 2019.
IoT is one of the major tracks. So drop your paper on Azure IoT Device provisioning, DigitalTwins, IoTCentral, AzureSphere, IoTEdge, workshops, hacks for makers, real world examples, architecture, ASAP
This event will not collide with the MVP summit 2020.
Testing IoT Edge at scale has some practical challenges. Where do you get all the hardware from if you want to test on two, or five, or twenty, or more devices?
The Azure cloud provides a simple solution: just spin up a bunch of Virtual Machines each running the IoT Edge Runtime. As long as you can provide the VMs access to simulated sensors instead of physical sensors, you are good to go.
Let’s dive a little bit deeper into the preconfigured VM that Microsoft recommends for these situations.
In the past, it was already possible to add a location to your IoT Central devices. And these locations were shown on a map. But these locations were fixed, part of the device template properties. So it was only present in the metadata.
But now we can pass a location in the telemetry which is produced by your device.
Let’s see how it’s done and how the location is integrated into the various IoT Central dashboards.