Can my puck interrupt on both BTN and TILT?

[espruino-discuss3]

Posted at 2020-09-18 by HeneryH_(Henery_Hawk)

Looking at the tilt library it seems to be using INT1.

The setWatch(button) isn't clear on which interrupt it is using.

Each of these two separate tests work independently but when I combine them they must conflict.

var pressCount = 0;
var tiltCount = 0;
var batt = 0;

var redLEDOn = false;
var greenLEDOn = false;
var blueLEDOn = false;

function swapBlue() {
  blueLEDOn = !blueLEDOn;
  LED3.write(blueLEDOn);
}

function swapGreen() {
  greenLEDOn = !greenLEDOn;
  LED2.write(greenLEDOn);
}


# Tilt detection works by itself, fails when combined with Button watching.
require("puckjsv2-accel-tilt").on();
Puck.on('accel',function() {
  batt = Puck.getBatteryPercentage();
  tiltCount++;
  swapGreen();
  NRF.setAdvertising({
    0x1821 : [tiltCount],
    0x180f : batt,
    });
  }
);

# Button watching works by itself but fails when combined with tilt detection.
setWatch(function() {
  batt = Puck.getBatteryPercentage();
  pressCount++;
  swapBlue();
  NRF.setAdvertising({
    0x1812 : [pressCount],
    0x180f : batt,
    });
}, BTN, { edge:"rising", repeat:true, debounce:50 });

[gfwilliams]

Posted at 2020-09-21 by @gfwilliams

The two things will work fine together - Puck.js has a bunch of different interrupt sources and chooses them such that they don't conflict.

However probably what you're hitting is that setAdvertising isn't additive - so when you call the button one you'll end up removing the 0x1821 service that the tilt listener added?

Easiest thing to do is to create one function called updateAdvertising that sets everything, and then call that whenever something changes.

Also just FYI, but swapBlue/etc can be replaced with LED3.toggle() if you want to swap the LED state