It is for M5StickC Plus. M5StickC is nearly the same:
https://docs.m5stack.com/assets/img/product_pics/core/minicore/m5stickc_plus/StickC_sch.webp

@jhonnytank

I apologize. I missed the fact that you were testing the hat. I only have the unit.

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

@felmue

I wouldn’t assume a change in the sticker also represents a change in hardware. For example, I have the initial release of the M5StickC (no copper nuts, which are actually copper mounting screw holes), red 5V IN on the sticker, and no “RTC” label on the sticker. However, my device actually has a functional RTC inside. So adding the RTC label on the sticker doesn’t mean they revisioned the hardware and added the RTC. It was always there.

I also cannot assume that the M5stack documentation is accurate 🤣. I think they make little revisions over time and don’t always communicate or document what was done.

If You already didn't, read this post:

https://community.m5stack.com/topic/1162/getting-longer-battery-run-time

Thanks for posting that info, djhopkins2, it's hard to come across!
I have found that this function keeps the board from shutting off after a few seconds, but I only started using an hour ago; I don't know if it has any adverse effects on the hardware yet:

void disable_shutoff() { return M5.I2C.writeByte(0x75, 0x02, 0x00); }

Also, here are the corrected voltage and current functions alluded to above; I don't think the voltage can go negative, but the current certainly does, and displays meaningless values without this correction:

int16_t readBatV(uint8_t Reg) { uint8_t dataV[2] = {0, 0}; M5.I2C.readBytes(0x75, Reg, 2, dataV); if(dataV[1] & 0x20) dataV[1] |= 0xC0; // 14 bit 2's complement to 16 bit return (dataV[1]<<8) | dataV[0]; } int16_t readBatI(uint8_t Reg) { uint8_t dataI[2] = {0, 0}; M5.I2C.readBytes(0x75, Reg, 2, dataI); if(dataI[1] & 0x20) dataI[1] |= 0xC0; // 14 bit 2's complement to 16 bit return (dataI[1]<<8) | dataI[0]; }

Hello @patf

I just ran a test with an empty program (empty setup and loop functions) and yes, with that M5StickC can be turned off, but not turned on again via power button.

Including M5StickC.h and instantiate M5.begin() fixes the power button and the device can be turned on again with a short press.

Background info: M5.begin() calls M5.Apx.begin() which then properly sets up the PMU AXP192 chip in the M5StackC.

Cheers
Felix

this is a very useful function. Looking forward to!

I solved the issue, I am getting the correct temperature now.

I changed the code to:

#include <M5StickC.h>
#include <math.h>

const int B = 4275;
const float R0 = 100000;
const int PIN = 33;

void setup() {
M5.begin();

Serial.begin(115200);

}

void loop() {

int a = analogRead(PIN);

float R = 4095.0/a-1.0;
R = R0*R;

float temperature = 1.0 / (log(R / R0) / B + 1 / 298.15) - 273.15;

Serial.println(temperature);

delay(500);
}

The correct pin was 33, and modified the 1023.0 to 4095.0 in the formula because esp32 is returning values between 0 and 4096. But anyway, the temperature readings were too high. Then, I modified the grove cable (as is explained here https://tinkerfarm.net/projects/the-m5stickc/the-5-volt-danger-with-the-m5stickc/) feeding the temperature sensor with 3.3v instead of 5v. And, now, (with no additional code changes) the temperature is correct.

Thats mean the pin where you connect relay is set to low state. So if you want to turn off your relay you must set pin to high mode or use for example transistor inverter (or use not logic gate) to invert your signal if you want activate it in high state signal.

0_1596220461992_bjt-amplifier-ce-positive-output.jpg

Awesome thanks all working

cheers

ATOM LITE don't have build-in any I2C slave device.

you could set any GPIO pin for i2c conmmuication.

@marsalkm This ability should work on M5StickC units with the MPU6886. There's more info on this thread here:
https://community.m5stack.com/topic/2039/wake-up-on-pick-up

You can try to reset your 'sick-C' by erase your flash and burn the firmware again?
(my older m5stickC bought at 2017 .it never 'died'. I erase and burn the firmware for about 1,500 times and it never 'sicked')

just like him said. don't comment the M5.begin();

Thanks! It worked.

In the REPL of any program you need to hit ctrl + c to kill any running processes in order to get to a command prompt

very nice fix @tehnolog it worked with my newer stickC but not the older one, M5atom also couldn't be recognised but they should be using the same chip i thought