Skip to main content

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

Previous post: http://vunvulearadu.blogspot.ro/2016/12/iot-home-project-part-1-initial-setup.html

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 https://www.raspberrypi.org/downloads/. 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:
hostname=raspberryPI

# basic wireless networking options:
wifi_ssid=vunvuleawifi
wifi_password=radusecret

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: http://vunvulearadu.blogspot.ro/2016/12/iot-home-project-part-3-nodejs-module.html

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...