Hi @Skink

here is a Python solution. Button A decreases, Btn C increases intensity. Btn B turns vibration motor on and off:

from m5stack import *
from m5stack_ui import *
from uiflow import *
import i2c_bus

screen = M5Screen()
screen.clean_screen()
screen.set_screen_bg_color(0xFFFFFF)

label0 = M5Label('Text', x=52, y=67, color=0x000, font=FONT_MONT_24, parent=None)

from numbers import Number

motorOnOff = None
motorValue = None
temp = None

def setMotorValue():
  global motorOnOff, motorValue, temp
  label0.set_text(str(motorValue))
  temp = (i2c0.read_u8(0x28)) & 0xF0
  temp = temp | motorValue
  i2c0.write_mem_data(0x28, temp, i2c_bus.UINT8LE)

def buttonA_wasPressed():
  global motorOnOff, motorValue, temp
  if motorValue > 0:
    motorValue -= 1
  setMotorValue()
  pass
btnA.wasPressed(buttonA_wasPressed)

def buttonC_wasPressed():
  global motorOnOff, motorValue, temp
  if motorValue < 15:
    motorValue += 1
  setMotorValue()
  pass
btnC.wasPressed(buttonC_wasPressed)

def buttonB_wasPressed():
  global motorOnOff, motorValue, temp
  motorOnOff = not motorOnOff
  power.setVibrationEnable(motorOnOff)
  pass
btnB.wasPressed(buttonB_wasPressed)

i2c0 = i2c_bus.easyI2C(i2c_bus.PORTA, 0x34, freq=400000)
motorOnOff = False
motorValue = 7
setMotorValue()

Cheers
Felix

Hello @Skink

that is not very surprising. To set the vibration intensity an underlying function SetLDOVoltage() is used which currently is broken in M5Core2 library as pointed out by @veryalien :
https://github.com/m5stack/M5Core2/issues/4.

I've proposed a fix in a pull-request which got closed as it should be fixed in the near future anyways as @Hades2001 pointed out:
https://github.com/m5stack/M5Core2/pull/5

Cheers
Felix

@rop said in M5Core2 library fork that supports multi-touch and provides Arduino-style virtual buttons.:

@felmue I'll meet you in the middle: I raised it to 200 because it was a bit tight indeed. 250 felt like too much because then it takes just a little too long for my taste for single taps to register.

Hi @Rop

thank you for all your hard work. I like the gestures and I like your coding style, very clear and well documented.

I fully understand your reasoning about not having a too long delay for double tap to not compromise single tap too much - 200 is fine for me too.

Cheers
Felix

Hi guys

@vkichline : interesting. I guess your hack makes Wire releasing the clock and data lines and that allows Wire1 to work properly.

Another way to fix the issue (I think, not tested) without touching the libraries could be the following change in Core2_Factory_test.ino:

current code:

M5.begin(true, true, true, true);

modified code:

M5.begin(true, true, true, false);

with the last parameter set to false Wire doesn't get initialised and Wire1 should work properly.

But yes, I fully agree, the issue should be properly resolved in the libraries. Hopefully we'll see those issues cleared up soon.

Felix

Hello @sheepDog

the M5Core2 library initialises two i2c instances (Wire and Wire1) using the same pins (21 and 22) and that leads to collisions. Have a look at the following pull-request which changes the pins for Wire making Wire1 work.

https://github.com/m5stack/M5Core2/pull/3/files

As for the far left icon: I think if you insert an SD card with pictures on it you'll be able to view them through that icon. I have not tried that myself though so I might be wrong.

Cheers
Felix

Hi @Rop

very cool stuff indeed. Thank you very much for sharing. Hopefully the M5Stack guys will pick it up rather sooner than later or at least let us know their intentions.

For me swipe down worked after some 'training' to not do the swipe too fast.

Double tap almost never worked until I've increased MAX_BETWEEN_TAP from 150 to 250. With the extended time it's very reliable.

Cheers
Felix

Hi Uwe

You are welcome!

I am using Visual Studio Code / PlatformIO (platform: espressif32; framework: arduino). Which is similar to the Arduino IDE.

Cheers
Felix

Hello @F3l1x

AFAIK MPU6886 reports 0x19 as WHO_AM_I. I think you already might have a newer M5Stack Fire which uses an MPU6886 - please see version history here:

https://docs.m5stack.com/#/en/core/fire?id=version-change

Have you tried below code? Looks like it can deal with all IMUs ever used in stacks.

https://github.com/m5stack/M5Stack/blob/master/examples/Basics/IMU/IMU.ino

Good luck!

Felix

Hi @m5stack

the Core2 advertisement on https://m5stack.com/collections/m5-core announces Ultra Low Power Consumption in Sleep Mode.

Would you mind sharing the exact numbers you guys measured in your lab and point me to the source code you used to achieve those numbers?

Thank you very much in advance.

Cheers
Felix

Hi @AucT

did you check out the M5StickC microphone sample? There is a GAIN_FACTOR which I would guess is probably what you're looking for.

https://github.com/m5stack/M5StickC/blob/master/examples/Basics/Micophone/Micophone.ino

Cheers
Felix