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

How to audit an Azure Cosmos DB

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

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more