Interrupt misfire about onoff HOT 3 CLOSED

Possibly related to fivdi/epoll#26 ?

@edit: I tried to keep application working and looks like after long idle time I still missing 1/2 interrupts on first data broadcast. Just like described in epoll issue linked above

from onoff.

Possibly related to fivdi/epoll#26 ?

This could very well be the case.

I have never used the Wiegand protocol, but googling says the Wiegand pulse width time is between 20 uS and 100 uS, and the pulse interval time between 200 uS and 20 mS.

If the pulse interval time for your reader is close to 200 uS, I can imagine interrupts being missed, especially at the start of the first read. For example, the JavaScript interpreter may have a lot of work to do for the initial few bits compared to later bits.

from onoff.

Refreshing timer without allocating a new object thus minimalizing time spent in the watch function seems to help:

const Gpio = require('onoff').Gpio

var data = [];
var timeout = setTimeout(() => {
	if(data.length == 0)
		return;
		
	console.log(data.join(""));
	data = []
}, 30);

function handleBit(pin, val) {
	pin.watch((_, value) => {
		data.push(val)
		timeout.refresh();
	});
}

var d0 = new Gpio(23, 'in', 'rising', {debounceTimeout: 0});
var d1 = new Gpio(24, 'in', 'rising', {debounceTimeout: 0});
handleBit(d0, 0);
handleBit(d1, 1);

Initially I tried to set one interval and save date of last bit broadcasted, but timeout = Date.now() seems to be not fast enough and still caused interrupts to be missed.

from onoff.