Skip to main content

[IoT Home Project] Part 1 - Initial Setup

I started some time ago to play with Raspberry PI and GrovePI sensors. After playing for a few weeks I said that I need to do something more interesting.

Mission
Why not combine Raspberry PI and GrovePI sensors with Azure IoT Suite and detect if somebody is at the desk, show STOP sign if the given person is busy and so on. I'll start with very basic use-cases, that will evolve in time. The scope of the projects is to learn different technologies that can be used together

Raspberry PI configuration
The code that will run on Raspberry PI will not be to complex, or this is what I expect now (smile). In this context it doesn't make sense to try to use Windows IoT. Also, the support for GrovePI is better for Node.JS in comparison with .NET.
In the context of my past experience with Debian on Raspberry PI that was good I decided that I will use Debian on Raspberry PI.

Development Environment
First thing is to make the initial setup of development environment. For backed, the story is pretty simple. We can use easily Visual Studio 2015 or Visual Studio Code.
Initially I wanted to run Visual Studio Code on my development machine and do a remote deployment on Raspberry PI. Because Visual Studio Code supports Remote Debugging for Node.JS, this should be pretty simple.

But, why not run Visual Studio Code directly on Raspberry PI. There is already support for ARM processors... so why not?
A few months ago there was a nice post from Scott Hanselman that describes how you can build your own build of Visual Studio for Raspberry PI - http://www.hanselman.com/blog/BuildingVisualStudioCodeOnARaspberryPi3.aspx 
Meanwhile, Jay Rodgers created an automatically night build that created builds of Visual Studio Code for ARM - https://code.headmelted.com/. In this way, only with a few clicks we can have Visual Studio Code installed on our Raspberry PI.


GrovePI Setup
The hardware setup is not complex. If you follow the steps from their web site or from the instruction book that comes with GrovePI box, you'll not have any kind of problems. Now, it is a good moment to take run a sample of an application written for GrovePI. Any kind of problems (hardware or software can be detected easily.

Next
The next step will be to attach the temperature and humidity sensor to the board and display the information to the LCD.

Next post: http://vunvulearadu.blogspot.ro/2016/12/iot-home-project-part-2-visual-studio.html

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see