fivdi / onoff Goto Github PK

Is PWM supported?

I am having an issue with a nosy input.

The interrupts are firing very fast but reading the same value (I think because of the noise).

For example I have an input the is low but the watch listeners are firing always reading 0.

I have tried setting debounceTimeout but this only delays the interrupt and cause them to occur less often.

Can the code be changed to add a readSync after the timeout and fire the watch listeners if the value changed.

Also don't know if the help but it is on a bealge bone black.

This may be worth noting in the documentation since it took me a long time to figure out. The latest Raspbian comes with a faulty Node v0.10.29 which is missing a UTF8 patch. This results in your epoll dependency failing to compile. Note gcc is v4.9.2.

The error shown is:

../node_modules/nan/nan.h:328:47: error: 'REPLACE_INVALID_UTF8' is not a member of 'v8::String'
static const unsigned kReplaceInvalidUtf8 = v8::String::REPLACE_INVALID_UTF8;

The only solution I found is to upgrade to a newer version, eg:

curl -sL https://deb.nodesource.com/setup_0.12 | sudo -E bash -
sudo apt-get install -y nodejs

This allows onoff to install as expected. It's unfortunate that the out of box Raspbian has this issue but hopefully others won't have to run into this issue too.

The latest onoff version does not work anymore on my arm machine. this is the simple code is use:

const GpioOnOff = require('onoff').Gpio;
const button = new GpioOnOff(239, 'in', 'both');
button.watch(function(err, value) {
  console.log('jo');
  console.log(err, value);
});

-> the button watch function is never triggered.

when reading directly cat /sys/class/gpio/gpio239/value is see that the values are populated correctly.

any hints?

If I start my ARM machine (note: GPIO 239 is NOT exported yet), start node REPL and enter this code:

const GpioOnOff = require('onoff').Gpio;
const button = new GpioOnOff(239, 'in', 'both');
button.watch(function(err, value) {
  console.log('jo');
  console.log(err, value);
});

everything works as expected. Now if I close the Node REPL and restart Node REPL (note: GPIO 239 is now exported due the first run on onoff) and use the same code as above, the example code does not work anymore. When I cat the GPIO value I can see that the value change if I press the button.

When I unexport the GPIO port manually and restart the Node REPL and run the code above, it works again. So it looks like onoff has some issues when the GPIO pin already is exported.

Possible options to fix this issue:

• unexportAlways option: if onoff is started with this option, it will try to unexport the GPIO pin first
• fix the actual issue, might be hard due alot of different systems

Can you reproduce this issue?

I'd love to see this module support gpio-admin for exporting and unexporting pins instead of needing to be root.

An example of another node gpio module that does this: https://github.com/rakeshpai/pi-gpio (however that module doesn't seem to support interrupts like this one does)

Error while trying: node-gyp configure on beaglebone black

hi
im not getting correct value when using read(err,value) or readSync functions.
im using Gpio 3 for IR sensors output
pls help
thanks in advance

The first time I launch a node application (as sudo) that uses onoff.js, I get this error:

fs.js:540
  return binding.write(fd, buffer, offset, length, position);
                 ^
Error: EIO, i/o error
    at Object.fs.writeSync (fs.js:540:18)
    at Object.fs.writeFileSync (fs.js:987:21)
    at new Gpio (/home/pi/nodeplay/node_modules/onoff/onoff.js:103:10)
    at Object.<anonymous> (/home/pi/nodeplay/process.js:15:16)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)

Subsequent launches are fine, until the next reboot.
Any ideas?

Use the epoll module rather than the built in gpiowatcher for interrupt detection.

Everything was working fine, until out of the blue I started getting this error which crashed my app:

fs.js:476
  var r = binding.read(fd, buffer, offset, length, position);
                  ^
Error: EAGAIN, resource temporarily unavailable
    at Object.fs.readSync (fs.js:476:19)
    at Object.fs.readFileSync (fs.js:310:28)
    at Object.exports.readAIN (/usr/local/lib/node_modules/bonescript/hw_capemgr.js:214:30)
    at Object.f.analogRead (/usr/local/lib/node_modules/bonescript/index.js:229:15)
    at null.<anonymous> (/home/debian/node_modules/thing-client/beagle1.js:647:18)
    at wrapper [as _onTimeout] (timers.js:252:14)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Any idea how I can get through this?

Regards
Guy

Can't get onoff to compile on BBB:

node-gyp rebuild

gyp ERR! configure error
gyp ERR! stack Error: Python executable "python" is v2.7.3, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:118:14)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:107:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:538:7)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:99:17)
gyp ERR! stack at maybeClose (child_process.js:638:16)
gyp ERR! stack at Socket.ChildProcess.spawn.stdin (child_process.js:815:11)
gyp ERR! stack at Socket.EventEmitter.emit (events.js:96:17)
gyp ERR! stack at Socket._destroy.destroyed (net.js:358:10)
gyp ERR! stack at process.startup.processNextTick.process._tickCallback (node.js:245:9)
gyp ERR! System Linux 3.8.13
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/root/downloads/GettingStartedWithNFC/NodeTagToLedPi/node_modules/onoff
gyp ERR! node -v v0.8.22
gyp ERR! node-gyp -v v0.8.5
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! sh "-c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the onoff package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls onoff
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.8.13
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/root/downloads/GettingStartedWithNFC/NodeTagToLedPi
npm ERR! node -v v0.8.22
npm ERR! npm -v 1.2.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/root/downloads/GettingStartedWithNFC/NodeTagToLedPi/npm-debug.log
npm ERR! not ok code 0

Thoughts?

The signature for lubuv "after work" callbacks in Node.js v0.8.0 is:

typedef void (uv_after_work_cb)(uv_work_t req);

in v0.10.0 it's:

typedef void (uv_after_work_cb)(uv_work_t req, int status);

Update onoff to take this into account and ensure that it functions with both v0.8.0 and v0.10.0.

I configured a GPIO ( GPIO 25 to be exact and pulled up)
I watch the pin for state change, the following error occurs when the switch is pressed.

node: symbol lookup error: /home/pi/mytools/gateway/node_modules/onoff/node_modules/epoll/build/Release/epoll.node: undefined symbol: _ZN4node12MakeCallbackEN2v86HandleINS0_6ObjectEEENS1_INS0_8FunctionEEEiPNS1_INS0_5ValueEEE

I tried upgrading wheezy but still did not resolve the issue. Current version I am at :

Linux version 4.1.7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 PREEMPT Sat Sep 19 15:25:36 BST 2015

onoff version is 1.0.3.

The Linux 3.13 kernel dropped support for detecting changes on GPIO output pins per hardware interrupt.

See raspberrypi/linux#808 and torvalds/linux@d468bf9

This means that onoff can no longer use hardware to detect output changes. Software should be used to detect the changes instead.

Attempting to unexport a GPIO on the BeagleBone Black when using the Debian 8.4 2016-05-13 image results in errors. Here's an example:

fs.js:613
    return binding.writeBuffer(fd, buffer, offset, length, position);
                   ^
Error: EINVAL, invalid argument
    at Error (native)
    at Object.fs.writeSync (fs.js:613:20)
    at Object.fs.writeFileSync (fs.js:1108:21)
    at Gpio.unexport (/root/lcd/node_modules/onoff/onoff.js:302:6)
    at Lcd.close (/root/lcd/node_modules/lcd/lcd.js:219:11)
    at process.<anonymous> (/root/lcd/node_modules/lcd/example/digital-clock-8x1.js:19:7)
    at process.emit (events.js:104:17)
    at Signal.wrap.onsignal (node.js:655:46)

I have no idea what's going on, it worked perfectly before.
I can read a GPIO but watching doesn't work and no error is thrown.
I can see via gpio utility that the value of the GPIO changed but onoff won't execute my watch callback.

Any idea?

Arch Linux

3.12.28-1-ARCH

would be great if one could configure pullup/pulldown for the ports via the api

Running the interrupt-example on a raspi (except with pin 17 and not 18), the callback for the watch-function never fires.
Manually reading the gpio at /sys/class/gpio/gpio17/value the value is changed on buttonpress (from 1 to 0).

The connection is made with a 10Kohm resistor between the gpio-pin and 3.3V and the gpio-pin has a 1Kohm protector resistor in front. The button is connected between gnd and 3.3v.

Running on latest raspbian and node 0.8.23.

Support pull-up and pull-down naively as other libs do...
no real info how to use the tree and really it should be transparent to user, just set flag

tx

Sean

I'm getting

Error: EACCES, permission denied '/sys/class/gpio/export'

when I try your first example on my raspberry pi

when installing the module with npm I get

npm http 404 https://registry.npmjs.org/epoll/-/epoll-0.1.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/epoll/-/epoll-0.1.0.tgz
npm ERR! Error: 404 Not Found

It seems like epoll is not available on npmjs

I'd be very interested in knowing on which computers people use onoff.

The Raspberry Pi?
The BeagleBone or BeagleBone Black?
Maybe something else?

If you happen to read this and use onoff, I would be very, very grateful if you posted a comment below saying on which computer you use onoff.

installing onoff on raspberry pi 2 model B, NOOBs v1.4.1 seems to hang at the terminal for very long. Is there any resolve in this? Usually install via 'npm install onoff --save'

Hi,

Is there a way to "unwatch" the inputs?

The things is, I want to watch 5 buttons and when one is pressed, no others should be able to press there buttons.

The README.md file talks at long about gpio export requiring root access.

On my 2014-01-07-wheezy-raspbian image (Rapberry Pi B), /sys/class/gpio/export is indeed owned by root, but gives access to group gpio as well (and user pi is member of the gpio group).

When I start my node.js application as user pi, the onoff export works, but setting the direction fails with EACCES. When I look at /sys/class/gpio, I see the gpio4 directory matching my pin 4. I can set the direction from the shell, and then set the output. Never been root.

I experimented with a script, and I found that I have to sleep for at least 0.2 second before I can access the direction file. I tried to wait until the direction file was created, with no success: the script still needs to wait after that.

Then I tried parallelism: export all 8 pins, wait and then set all 8 directions. It worked if it waits at least 0.4 second.

Do you have ever noticed such a peculiar thing?

Working onoff I am trying to use a Hall Effect Sensor position (0-off, 1-on) to control a motor. My raspberry pi is giving me the below error. Not sure what to do next.. thank for the help.

fs.js:613
return binding.writeBuffer(fd, buffer, offset, length, position);
^
Error: EBUSY, resource busy or locked
at Error (native)
at Object.fs.writeSync (fs.js:613:20)
at Object.fs.writeFileSync (fs.js:1108:21)
at new Gpio (/node_modules/onoff/onoff.js:82:8)
at Object. (/home/1-28-2016/door.js:3:14)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)

Great library 👍

Not really an issue, more like a feature request.

When a pin is registered at the start of the script using
var led = new Gpio(14, 'out');

The state of pin 14 is set to LOW (0), regardless of what it was before. If a previous script has set the pin to HIGH and then finishes, or the script restarts for whatever reason, the pin is always reset to LOW.

Is it possible to have the pin registered, but not have the start altered until it is done so manually using write or writeSync?

I appreciate your time.

I am getting a resource unavailable error which I think is related to onoff. Have a look at the error message. I have checked all my other modules, and they are not causing the error.

fs.js:476
  var r = binding.read(fd, buffer, offset, length, position);
                  ^
Error: EAGAIN, resource temporarily unavailable
    at Object.fs.readSync (fs.js:476:19)
    at Object.fs.readFileSync (fs.js:310:28)
    at Object.exports.readAIN (/usr/local/lib/node_modules/bonescript/hw_capemgr.js:214:30)
    at Object.f.analogRead (/usr/local/lib/node_modules/bonescript/index.js:229:15)
    at null.<anonymous> (/home/debian/node_modules/thing-client/beagle1.js:648:18)
    at wrapper [as _onTimeout] (timers.js:252:14)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Your help will be appreciated.
Thanks
Regards Guy

I updated gcc and g++ versions to 4.8 but It still gives error pointing bindings.js

I followed https://github.com/fivdi/onoff/wiki/Node.js-v4-and-native-addons

Any advice?
Thanks in advance!

Hi there, firstly well done on this submission. I'm working on a project and this is going to help a lot.

I am using a Beaglebone Black running the latest Debian Wheezy.

The install seems to freeze halfway through, and I'm wandering if this is normal and it just takes really long to install. Or what might be causing it to freeze..

Here is the output:

debian@debian-armhf:~$ sudo npm install onoff
npm http GET https://registry.npmjs.org/onoff
npm http 200 https://registry.npmjs.org/onoff
npm http GET https://registry.npmjs.org/onoff/-/onoff-0.3.1.tgz
npm http 200 https://registry.npmjs.org/onoff/-/onoff-0.3.1.tgz
npm http GET https://registry.npmjs.org/epoll
npm http 200 https://registry.npmjs.org/epoll
npm http GET https://registry.npmjs.org/epoll/-/epoll-0.1.3.tgz
npm http 200 https://registry.npmjs.org/epoll/-/epoll-0.1.3.tgz
npm http GET https://registry.npmjs.org/nan
npm http 200 https://registry.npmjs.org/nan
npm http GET https://registry.npmjs.org/nan/-/nan-0.8.0.tgz
npm http 200 https://registry.npmjs.org/nan/-/nan-0.8.0.tgz

> [email protected] install /home/debian/node_modules/onoff/node_modules/epoll
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/0.10.22"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/debian/node_modules/onoff/node_modules/epoll/.node-gyp"
gyp http GET http://nodejs.org/dist/v0.10.22/node-v0.10.22.tar.gz
gyp http 200 http://nodejs.org/dist/v0.10.22/node-v0.10.22.tar.gz

Your input will be greatly appreciated.
Thanks in advancef

The persistentWatch option was introduced in onoff v0.1.2 as all watches up till then were single shot, they only got called once. By setting the persistentWatch option to true, it was possible to have watchers that always got called. persistentWatch had a default value of false for backward compatibility.

As of onoff v0.2.0, the persistentWatch option is no longer strictly required. Watchers could always be persistent and the single shot effect can be achieved by calling unwatch the first time the watch handler is called. unwatch was added in v0.2.0.

This will be a breaking change for programs that set persistentWatch to false, either explicitly or implicitly as false is the default value.

So, unless someone can come up with a good reason not to, the persistentWatch option will be removed in onoff v0.3.0.

Use nan to isolate the gpiowatcher addon from V8 modifications and make it compatible with node v0.8 through v0.12.

I'm using RPi 2 with onoff. On my machine I cannot read gpio no matter I export the pin using gpio-admin or not. However as soon as I use python to read the same pin, node.js can get the value even if I unexport the pin with gpio-admin. How can this happen?

The code I'm using:

var gpio = require('onoff').Gpio,
    http = require('http'),
    button = new gpio(18, 'in', 'both');

function exit() {
  process.stdout.write('\n');
  button.unexport();
  process.exit();
}
process.on('SIGINT', exit);

button.watch(function(err, state) {
  if (err) {
    throw err;
  }

  process.stdout.write(button.readSync() + '');
});

http.createServer(function(req, res) {
  res.end(button.readSync() + '');
  process.stdout.write(button.readSync() + '');
}).listen(8080);

import RPi.GPIO as GPIO
import time

print('Setup GPIO pin 18')
GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)

print('Setup LED')
f = open('/sys/class/leds/led1/trigger', 'r+')
f.write('gpio\n')
f.close()

print('Ready')

while True:
    input_state = GPIO.input(18)
    if input_state == False:
        f = open('/sys/class/leds/led1/brightness', 'r+')
        if f.read() == '1\n':
            f.write('0\n')
        else:
            f.write('1\n')
        f.close()
        print('Button Pressed')
        time.sleep(0.2)

Hi,

Firstly I'm loving On/Off... for me it works the best out of all the others that I tried.

Is there any chance you can add PWM features... I was looking at Webiopi and they use PWM ratio and PWM angle and was wondering if it was something you would be able to add.

Many Thanks

A lot of times the io is connected to relays the reverse the output. E.G. Gpio goes low, relay closes. It would be nice to have a "reverse" parameter in the constuctor.

There is no option to persistently watch and initiate a callback each time it is pressed as it is currently a one-shot watch.

Someone can explain why it returns always 'off' in stato? It can't toogle.

var Gpio = require("onoff").Gpio;
led = new Gpio(17, 'out');

   led.read(function (err, value) { // Asynchronous read.
        if (err) throw err;

        led.write(value ^ 1, function (err) { // Asynchronous write.
          if (err) throw err;
          var stato = (value == 1) ? "on": "off"; 
          console.log('Pin new value: '+stato);
        });
  });

For example, when i turn on the pin with a write method, everything seems to work fine, but when i try to read the pin status, the pin turn OFF and the value printed on the console is 0/off.

The weird thing is that it happens even with the rpi-gpio.js library: JamesBarwell/rpi-gpio.js#24

Couldn't be possible to extend it to support also the C.H.I.P board?

The package doing it (chip-gpio) is actually inspired by onoff :) https://github.com/jeremyscalpello/chip-gpio

There is an option to initial them as 1? becuase if they are connected to something all are sync zero at the same time and its annoying..
any suggestion?
thanks

I'm using onoff to control a relay board with LEDs. When I start the app script, all LEDs turn on automatically. Is there a way to prevent onoff from turning all my relays on when initializing them?

Hi,

I'm using you package to listen to button event and I noticed that sometimes (don't know how to 100% simulate it) I receive more than once the same value.
Below is my code.
When running it and start pressing the button, I get sometimes twice the value 1 (in a row).

button.watch(function(err, value) {
console.log(value);
});

Are you aware of such issue ?

Btw, great package :)

Thanks !

If my app accidently closed without led4.unexport(); so now I have Error: EBUSY: resource busy or locked, write error for each start. How to avoid it? Raspberry restart does not help.

pi@raspberry-black:~/dev/homesen $ node test-gpio.js
fs.js:706
    return binding.writeBuffer(fd, buffer, offset, length, position);
                   ^

Error: EBUSY: resource busy or locked, write
    at Error (native)
    at Object.fs.writeSync (fs.js:706:20)
    at Object.fs.writeFileSync (fs.js:1234:24)
    at new Gpio (/home/pi/dev/homesen/node_modules/onoff/onoff.js:82:8)
    at Object.<anonymous> (/home/pi/dev/homesen/test-gpio.js:3:12)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)

var Gpio = require('onoff').Gpio;
var led4 = new Gpio(4, 'out');
blink(led4, 500);

function blink(led, period) {
    led.write(1, function () {
        setTimeout(function(){
            led.write(0);
        }, period);
    });
}

Hi,

I'm trying to watch 5 inputs at the same time using "persistentWatch : true" and debouncing time 250 and it's not working as it should.

If I watch 4 inputs, everything works fine. I can push the buttons several times, they keep working. But if I use 5 inputs, some things are messed up. I cannot press the same button twice, I have to press another one first before I can press it again.

Is there some kind of limit to the number of inputs that can be watched?
Is there something I can do about it?

Thanks,
Sam

Hi there, first of this is a greata library you have made. I use it a lot!

I have two questions, first of all: I am trying to read from a 2wire temperature sensor (LM75A) using I2c on pins P9_19 and P9_20. I understand that the beaglebone pin functions can be altered depending on what mode it is set to. However, I don't see anywhere in your library where the pin mode can be set.

I have had a little bit of success with the temp readings which leads me to believe that the pin mode is automatically set. I just want to rule this out as a possible cause of my issues with the temp readings.

Secondly, does your library accommodation for analog readings using the AIN pins?

Thanks in advance
Regards
Guy

Hi,
I'm using onoff for FirmataPi and have hit a snag. I've been developing on osx, running tests on osx and linux, and have "production" on my raspberry pi. I know onoff can't work on anything but linux but in my tests I'm mocking out onoff as I don't need to test its functionality, just that I'm calling it correctly.

So here's my question, how can I install it on other platforms?

Hi, I'm just trying the functions out and I'm currently trying to write to pin 4, but getting the above error message. Here's the code, it's pretty basic..

var Gpio = require('onoff').Gpio,
led = new Gpio(4, 'out');

led.write(1);

Has anyone come across this before?

NOTE: Running Raspbian Jessie and Node.js 6.3.0

Hi, I'm just trying the functions out and I'm currently trying to write to pin 4, but getting the above error message. Here's the code, it's pretty basic..

`var Gpio = require('onoff').Gpio,
led = new Gpio(4, 'out');

led.write(1);`

Has anyone come across this before?

Disregard

Hi there,

Nice GPIO library !
Is there any internal mechanism for debouncing the hardware interrupts watch() function? I am having issues with this, and found nothing to get rid of it.