npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

iotduino

v0.1.8

Published

Create Node.js IoT projects by using low level hardware access of the PCDuino boards.

Downloads

8

Readme

IoTDuino

Node module for IoT apps/web-apps created by using the PCDuino or other PCDuino compatible devices able to run Node.js.

The module uses native C/C++ code. Benchmarks with PCDuino v3 board reveals that a digitalWrite operation takes 6-7 microseconds (~ 140 - 160 KHz) and a digitalRead operation takes 4-5 microseconds (~200 - 250 KHz).

The tests were made by using one million (1.000.000) read/write operations. Run the tests/performance_tests.js script if you like to check the performance of your own board. The results may by different from board to board and also depends on the load of your CPU when the tests are executed (background processes, crons, services, applications, etc).

The code lets room for many optimizations. As it is now, can be used to:

  • read the HC-SR04 ultrasonic distance sensor without visible lags. The only limitation is the sensor itself and the measured distance (remember: the speed of the sound in air is approx. 343m/s, which means that one millisecond is required to measure every 34.3cm). Check tests/ultrasonic_hcsr04.js example.
  • read the DHT22 humidity and temperature sensor. It requires a custom 1-Wire communication protocol (the communication with this sensor is really time sensitive). Check tests/dht22.js example.

Features:

The following Arduino methods are supported:

  • pinMode( pin, state) - set the pin mode to INPUT (0x0), OUTPUT (0x1) or INPUT_PULLUP (0x2)
  • digitalRead( pin) - read the current state of the selected pin.
  • digitalWrite( pin, state) - set the pin state to LOW (0x0) or HIGH ( 0x1) after pinMode was called with OUTPUT as state parameter
  • analogRead( pin) - read the value of the analogous pin. Remember: pins A0 and A1 have 6 bits ADC resolution (so the method returns values in the interval [0, 63]) while the pins A2, A3, A4 and A5 have 12 bits ADC resolution (so the method returns values in the interval [0, 4095]). Also, keep in mind that the voltage reference is 3.3V (well, almost and depends on many factors), so we can only measure positive voltage up to 3.3V (resistor divider circuits may be used to measure higher values if needed).
  • analogWrite( pin, value) - create a PWM effect on the selected pin. The supported pins are GPIO3, GPIO5, GPIO6, GPIO9, GPIO10 and GPIO11. The value parameter is an integer number in range [0, 255]. The method is used in combination with setPwmFrequency method!
  • setPwmFrequency( pin, frequency) - set the PWM frequency for the specified pin. Pins GPIO5 and GPIO6 supports only: 195Hz, 260Hz, 390Hz, 520Hz and 781Hz while pins GPIO3, GPIO9, GPIO10 and GPIO11 supports integer values in the range [126, 2000]Hz.
  • pulseIn( pin, state, timeout) - read a pulse time for the specified pin and state
  • micros() - read the number of microseconds ( modulo unsigned long type in C/C++) elapsed from Epoch (01.01.1970, 00:00:00 UTC).
  • delay( milliseconds) - pause the code execution for the specified number of milliseconds. This method implementation is on the way to be improved.
  • delayMicroseconds( microseconds) - pause the code execution for the specified number of microseconds. This method implementation is on the way to be improved.

The following constant groups are defined (check the USAGE section for concret examples) :

  • PinMode - defines the pin mode states. Possible values: INPUT, OUTPUT and INPUT_PULLUP. Alternative: use 0, 1 and 2.
  • PinState - define the possible pin states. Possible values: LOW and HIGH. Alternative: use 0 and 1.
  • Pins - define the existing pins. Possible values: GPIO0, GPIO1, ... GPIO23, A0, A1, A2, A3, A4, A5. Alternative: use 0, 1, ..., 23 to identify GPIOs and 0, 1, 2, 3, 4, 5 to identify the analog pins.

Install:

Local installation (used for the application on which folder you execute the command):

npm install iotduino

Global installation (available for any node application):

npm install -g iotduino

For the global installation case, you have to use sudo or to login as root on linux systems to install this module.

In case you get the following error:

Error: Cannot find module 'iotduino'

check the NODE_PATH variable (use echo $NODE_MODULES) to verify if it points to the right location (normally this is /usr/local/lib/node_modules). You may also what to read the node modules official page for additional information. Usage:

The well known LED blink example by using the built-in PCDuino v3 LED connected to pin 13 ( same as for Arduino UNO and alike):

var duino = require( 'iotduino'),
    pinMode = duino.PinMode, pinState = duino.PinState,
    pins = duino.Pins, ledPin = pins.GPIO13;
    
// pin 13 (GPIO13) is set as OUTPUT
duino.pinMode( ledPin, pinMode.OUTPUT);
// repeat every 500 milliseconds, 2 times per second
setInterval( function () { 
  // alternate the pin state between HIGH and LOW 
  duino.digitalWrite( ledPin, !duino.digitalRead( ledPin));
}, 500);

Reading distance with the HC-SR04 ultrasonic sensor (requires hardware voltage level shifter from 5V to 3.3V and back since the PCDuino GPIOs are not 5V tolerant and the HCSR-04 sensor does not work if powered from 3.3V):

var duino = require( 'iotduino'),
    pinMode = duino.PinMode, pinState = duino.PinState,
    pins = duino.Pins, trigPin = pins.GPIO2, echoPin = pins.GPIO3, 
    distanceCm = -1;

// the trigger pin (GPIO2) is set as OUTPUT
duino.pinMode( trigPin, pinMode.OUTPUT);
// the echo pin (GPIO3) is set as INPUT
duino.pinMode( echoPin, pinMode.INPUT);
// read the sensor every 333 milliseconds, ~3 times per second
setInterval ( function () { 
  // the sensor receives LOW at the trigger pin, 
  // to prepare it for data reading
  duino.digitalWrite( trigPin, pinState.LOW);
  // wait for the sensor to get ready
  duino.delayMicroseconds( 2);
  // inform the sensor that we want to make a reading
  duino.digitalWrite( trigPin, pinState.HIGH);
  duino.delayMicroseconds( 10);
  // end the commands chain to the sensor
  duino.digitalWrite( trigPin, pinState.LOW);
  // read the value HIGH time period from the sensor
  // and compute the distance based on it and the physical laws
  distanceCm = duino.pulseIn( echoPin, pinState.HIGH, 100000) / 58.0; 
  // show the distance value in the console
  console.log( "Distance: " + distanceCm.toFixed(2) + " cm");
}, 333);

What's new:

v0.1.8:

  • added analogWrite method with support for pins: GPIO3, GPIO5, GPIO6, GPIO9, GPIO10 and GPIO11
  • added setPwmFrequency method with support for pins: GPIO3, GPIO5, GPIO6, GPIO9, GPIO10 and GPIO11
  • added test case for analogWrite and setPwmFrequency, see tests/analogWrite.js
  • various code improvements
  • multiple bug fixes

v0.1.7:

  • added analogRead method with support for analogous pins A0, A1, A2, A3, A4, A5
  • added test case for ADC reading, see tests/adc.js
  • various code improvements
  • some small few bug fixes

v0.1.6:

  • various improvements and bug fixes
  • the DHT22 temperature and humidity sensor works now (check the tests/dht22.js example).

v0.1.5:

  • bug fix: pinMode had issues to come back to INPUT after set to OUTPUT
  • added micros method
  • improvements in the native code for faster execution

Work in progress:

  • Serial support
  • SPI support
  • I2C support

Notes:

  • Improvements (and new features) are on the way, you may want to check for updates from time to time.
  • Future plans includes to port this module for BeagleBone White/Black and possible to other similar boards.