Windows Azure and Embedded Devices

of 40/40
Andy Cross @andybareweb Devices and Windows Azure The openness of Windows Azure
  • date post

    20-May-2015
  • Category

    Technology

  • view

    1.869
  • download

    3

Embed Size (px)

description

This talk will demonstrate the Internet of Things with Windows Azure. Using embedded devices that interact with Windows Azure cloud technologies, the Internet of Things ideology is enabled with scalable and resilient cloud systems that imbue the resource constrained devices with elastic, on-demand additional computing power that allows any network connected device to achieve amazing computational feats. The talk features three main device/cloud interactions: persisting unbounded data from sensors, communicating through resilient channels and interacting directly with the Windows Azure cloud to provision and control cloud based infrastructure.

Transcript of Windows Azure and Embedded Devices

2. Time until next coffee 3. Devices areeverywhere 4. Time until next coffeeOnly a scalable elastic computinginfrastructure can solve this scalabilitychallenge; such as Windows AzureDevices and Azure Copyright 2012 09 / 14 /12 4 5. Device ClassificationsDesktopDesktop PC and Laptops Background processes User interactions Background processesMobile Push notifications requiring Server contexts Location sensitive data Nike+Embedded Intelligent Housing RFID 6. Devices illustrated Capacity Cost Potential Capacity Cost Potential Capacity Cost Potential 7. Desktop Mobile Devices 8. How does Windows Azure Help Embedded? Compute provisioned on Scalable Resource demand Storage into 100s TBs easily Geo-locatable Mobile Services Infrastructure Services Media Services HPC and Big Data Windows Azure Storage Architectures Windows Azure Service Bus Service Management API 9. This is no Windows Azure Client forembedded devices. We will have to write ourown.This integration is only possible if the platform istruly open and device agnostic. There is no moreevident test of this than consuming and interactingwith Windows Azure from a device which does nothave an operating system. 10. Time until next coffee 11. Development, Devices, DeliveryWrite in C# or Visual Basic (recent) Open Source HardwareUse Visual Studio (Express inc)Arduino layoutsDeploy and debug via USB Custom NETMF boardsDebugging WORKS! Breakpoints,Design your ownimmediates, watches etcDotnet Gadgeteer /Netduino GOWhen complete, publish your software to a firmwareand distribute to your hardware vendor for delivery 12. NETMF architectureWhoWhatYou User CodeMicrosoft andcommunity.net Framework classesDevice vendors 13. Notice the class is standard C#with typical namespaces.There are additional usingstatements for device specificlibraries.The class looks almostidentical to a C# console app but without args[] on theMain()The AnalogInput class willdo most of our work, it takesa hardware address.We Read() to get a voltage and let whatever is on the pindo the work of generating this. 14. This class uses anOuputPort set tocommunicate with the onboard LED of the Netduino.We use the Write method tosend a binary (Digital) signalto the output device, in thiscase the on board LED.We use familiarSystem.Threadingnamespace to control theexecution flow, in this case,pausing for 200ms so thatthe LED flashes changingstate 5 times a second 15. http://www.microframework.nl/2009/09/05/shahmac-digest-class/ 16. Time until next coffeeDemo 1 17. TemperatureDeviceWindows Azure Blob StorageTrigger Button 18. Time until next coffeeDemo 2 19. OutputDeviceWindows AzureQueue Storage 20. Time until next coffeeDemo 3 21. Analog Input Device GatewayWindows AzureService Management 22. Time until next coffeeBig Data 23. Q&AThanks for Listening!