Skip to main content

[IoT Home Project] Part 3 - Node.JS Module that reads sensor data

By
Previous post: http://vunvulearadu.blogspot.ro/2016/12/iot-home-project-part-2-visual-studio.html
GitHub source code: https://github.com/vunvulear/IoTHomeProject/tree/master/nodejs-grovepi-azureiot

In this post we will continue developing the IoT Home Project, by creating a module for Node.JS that reads the sensor data.

Why we create a Node.JS module?
We want to group all the logic that reads sensor data under the same roof. We design the module in a such a way that it will allow us to initialize an instance of an object that can read all sensors data.

GrovePiSensors Module
The module was is called GrovePISensors and expose 5 functions:
  • getSoundData - Gets Sounds data
  • getTempAndHumData - Gets Temp and Humidity data
  • getDistanceData - Get Distance data from Ultrasonic sensor
  • getLightData - Get Light data
  • getAllSensorsData -  Get all sensors data that can be read
The getAllSensorsData returns an object, where all this information are available. The sound information are not collected because it seems that personally I have some problems with the sensor. I'm not able with my board to collect data from sound sensor.

As you can see in the constructor, I have some predefined pins for each sensor. I have the following configuration:
  • DHT Sensor - pin 2  (digital)
  • Ultrasonic Sensor - pin 4 (digital)
  • Light Sensor - pin 2 (analog)
  • Sound Sensor - pin 0 (analog)
, but the constructor allow us to configure the pins as we want. Be careful, not to mix analog with digital pins and sensors. 
By default I log all the information that is read from the sensors in the console, but you can disable this from the constructor if you specify debug to false (default value is true).

From app.js I just initialize the board and read the sensors data. For now, I don't use this.



Lesson learns at this step
  1. I forgot to write an 's' to 'module.exports' and I spent around 2 hours trying to figure our why the module is not working.
  2. There are two types of sensors, digital and analog. If you don't connect them on the right pin, you'll get random data. 
  3. If you are careful you can connect/disconnect sensors while your app is running.
  4. Try to test each sensor after you write the first lines of code that read data from it.
  5. The light sesor show a high value when the light is low. A lower value means that the light level is high.
Next step
Connect to Azure IoT Hub and push this data to cloud.

Next post: [IoT Home Project] Part 4 - Sending temperature data from Raspberry PI to Azure IoT Hub

Comments

Post a Comment

Popular posts from this blog

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

By
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(
Post a Comment
Read more

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

By
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
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more