Wake up on pick-up

felmue

In my M5Stack Grey the two ICs (MPU6886 and BMM150) are on a small daughter board which was soldered to the underside of the Groove connector (GND, 5V, SDA, SCK). An additional pin provides 3.3V for the two ICs. But I am afraid the interrupt line coming out of the MPU6886 is not connected at all.

Please note: My M5Stack Grey board reads 2018.3, so maybe the daughter board was merged with the main board in later revisions?

Felix

Desoldered daughter board:

Tristar

hey @davesee

I have the latest version of the M5Stack gray, but the board also reads 2018.3. I am going to try out your code that you used for M5StickC on my M5Stack Gray with PlatformIO.

I will report back how it went. All I want is a wake up on movement :). The same thing you got running on your M5StickC.

felmue

@Tristar

Just curious - how did your try out go? Have you been able to get @davesee code running on your M5Stack Grey?

Thanks
Felix

Tristar

Not yet, but I will invest tomorrow the whole day and try to get his example working on the GREY.
I have the problem that the GREY just restarts on its own every few seconds. Looks like the GPIO35 is always triggering the wake up call from deep sleep.

felmue

Hi @Tristar

How's it going? My two M5Stack Gray and Fire did exactly the same, they would restart on their own. The reason is, as we already expected, that the interrupt output from the MPU6886 is not connected to the GPIO35 (at least not in my two M5Stacks).

I've fixed that by soldering a wire from MPU6886 pin12 (INT) to GPIO35 and now my M5Stacks properly go to sleep and only wakes up on motion again.

Cheers
Felix

felmue

Hi @davesee

Thank you very much for your WOM code which I am using on my M5Stack Fire.

Just curious about the following code lines for WOM step 2:

The read regdata are not actually used. Maybe by mistake?
Comment says 32 samples, but actually only 16 samples are selected. Typo?

/*
Step 2: Set Accelerometer LPF bandwidth to 218.1 Hz
        • In ACCEL_CONFIG2 register (0x1D) set ACCEL_FCHOICE_B = 0 and A_DLPF_CFG[2:0] = 1 (b001)
*/
I2C_Read_NBytes(MPU6886_ADDRESS, MPU6886_ACCEL_CONFIG2, 1, &regdata);
regdata = 0b00100001; // average 32 samples, use 218 Hz DLPF
I2C_Write_NBytes(MPU6886_ADDRESS, MPU6886_ACCEL_CONFIG2, 1, &regdata);

Thanks
Felix

Tristar

@felmue
yeah, you are right. On the M5Stack Grey there is no wiring between the pins. Could you provide some images of the board where one can see how you did the soldering? time to rip my m5stack grey open and do some soldering too :)

For the next version of the M5Stack there has definitelyto be a wiring between the IMU (mpu9250) and a pin like 35!!

felmue

Hi @Tristar

The daughter board with MPU6886 and BMM150 are the same for M5Stack Gray and Fire. So the picture I've attached to my previous post (#15) also applies for M5Stack Gray.

Good luck!
Felix

P.S. you'll find the same information also through the link in my signature below.

felmue

Hi guys

Just a heads up on the new M5Core2 which has the IMU and mic on a micro board attached to the M5bus. As far as I can tell the interrupt pin of the MPU6886 doesn't seem to be connected to GPIO35 or any other pin on the M5bus which is a bit disappointing.

Cheers
Felix

doublep

Does anyone know what the trigger values of registers ACCEL_WOM_THR represent? For example, for the ADXL345, 1 LSB of trigger register is the equalavent of 0.065 G. However, there is no information about this in the datasheet of the MPU6886 and the value also seem to be effected by setting a different value for A_DLPF_CFG in the ACCEL_CONFIG_2 register.

If anyone can help with this that would be nice.

Zontex

@doublep hello, could you refer me to where you read that value from?