Skip to main content

[IoT Home Project] Part 2 - Visual Studio Code and the first node.js app

Previous post:

In this post we will take a look on the initial setup of Raspberry PI, GrovePI and a sample code that helps us to check if node.js and GrovePI works as expected. Before we talk about the initial setup of the device.

Useful tools for Raspberry PI
I recommend to start with a fresh installation of OS. You can download the OS image from I am a big fun of NOOBS, but feel free to use other versions of OS. To write the image on the memory stick you can use Win32 Disk Imager. A basic tools that do his job.

Once you wrote the image on a stick, don't forget to connect it to a monitor and activate SSH. By default SSH is disabled. You can do this from the console, but you can use raspi-config, a nice tools that allow you to do different configurations on your device
sudo raspi-config 
The SSH options is under 'Advanced Options'. From this tool, you can activate also VNC. A restart is needed after you do this change.
For VNC, the default resolution is not very high. This can be solved easilty if you run:
vncserver -geometry 1600x1200 -randr 1600x1200,1440x900,1024x768
From now, you can access your device using VNC Client or Putty. Default user is 'pi' and the default password is 'raspberry'.
The last tool that you should run is PI Finder. This tool will install the base packages, like node, vim, git and so on. It has a nice UI and it will search automatically for the raspberry in your private network. The default name of the raspberry is 'raspberrypi'.
Why I like at this tools is that it creates a file that can be accessed from PC or from any card reader where you can specify the WiFi SSI name and password. This is very useful when you end-up in a location where you don't have a network cable but you know WiFI password and name.
# hostname for your Raspberry Pi:

# basic wireless networking options:

Visual Studio Code on Raspberry
In the last post I show you how you can compile your own version of Visual Studio Code. The good think is that others already done this. Headmelted offer us the package ready to be installed on our device. Thank you for that!
Once you downloaded and installed Visual Studio Code Package, the only think that you need to do is to run 'code-oss'

Initial Test Code
The code that I used for tests can be found on GitHub. Before running the code, froma shell, you need to run the below command that will install the GrovePI node package.
npm install node-grovepi
Once you done, you'll need to connect the humidity and temperature sensor on port D1 and the LCD on I2C 2. Now you are ready to run the code.
If in the future we will play more with the LCD, I promise that I will write a module for node that will help us to communicate with the LCD.

What's next?
The next step is to connect also others sensors for Raspberry PI and read all the data.

Next post:


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…