›

Tap config values

legionaryulegionaryu
in Android
Hi,
I'm trying to explore the Metawear API by using and configuring the basic events that are available.
Right now I'm stuck in the Accelerometer Tap event, I was trying to test the Tap event using extremes configuration values like 0 and 2000, but my test didn't show much difference between the two configs.
Example, with the value 0 in the Tap Latency the Metawear don't send another tap event in less than 100 ms, but using 2000 as value the Metawear sends the Tap right away.

There are limits on the Tap config values? Does anyone have a example that uses different configs for the Tap event?

Thanks in advance,

Comments

  • LauraLaura
    Which api are you using, ios or android? Can you send us some code snippets?
  • legionaryulegionaryu
    edited April 2015
    Hi Laura,

    I'm using the android API.
    Here is my code:

    public void onConfigClick(View v){
    mdAccel.stopComponents();
    mdAccel.disableAllDetection(false);
    mdLed.stop(true);
    mdLed.setColorChannel(LED.ColorChannel.GREEN).withHighIntensity((byte)31)
               .withHighTime((short)250).withPulseDuration((short)500)
               .withRepeatCount((byte)3).commit();
    mdLed.play(false);
    mdAccel.enableTapDetection(Accelerometer.TapType.SINGLE_TAP,Accelerometer.Axis.Z)
                  .withLatency(seekbarTapLatency.getProgress())
                  .withDuration(seekbarTapDuration.getProgress())
                  .withWindow(seekbarTapWindow.getProgress())
                  .withThreshold(seekbarTapThresh.getProgress());
    mdAccel.startComponents();
    }

    All SeekBars use a range from 0 to 2000.

    Thanks,

  • EricEric
    The latency parameter is for configuring double tap.  For how the API configures single tap, latency does not affect single tap.
  • legionaryulegionaryu
    Thanks Eric!
This discussion has been closed.