Posts made by felmue

Hi guys

works for me - tested with an M5Atom Matrix and an M5StickC Plus (both running UIFlow version 1.7.8).

Maybe a temporal or regional issue?

Thanks
Felix

Hello @sheepDog

to me it looks like both, the regular M5Core2 and the AWS version, are using identical hardware / same board revision - at least the ones I have do.

The difference is in the M5GO2 bottom: the AWS M5GO2 bottom adds the secure element.

That said, have you tried the AWS version w/o the AWS M5GO2 bottom attached?

Thanks
Felix

Hello @irokoi

have you considered using ext0 instead? E.g.

esp_sleep_enable_ext0_wakeup(GPIO_NUM_37, LOW);
esp_sleep_enable_ext0_wakeup(GPIO_NUM_39, LOW);

Thanks
Felix

Hello @ykpark1126

the error message actually tells you what's wrong. The SPI speed is too fast - have you tried to reduce it from 40 MHz to say 20 MHz? Works for me.

Thanks
Felix

Hello @rtrias

I don't have a Timer Camera X so my conclusions might be incorrect.

Reading though the schematics and the Timer-CAM Arduino example it occurs to me that the Timer Camera X only will shutdown completely when running from battery. In that state it can be woken up again by the RTC timer (or power switch or USB).

If USB is attached it cannot fully shutdown, but goes into ESP32 deep sleep. You are correct that ESP deep sleep power consumption is below 1 mA. However M5Stack devices have been notoriously bad in conserving power while ESP is in either deep sleep or light sleep due to all the additional voltage regulators etc. and I am afraid Timer Camera X is no exception.

Thanks
Felix

Hello @hide4849

sorry, I am out of ideas and I don't have the CAN-bus unit so I cannot test myself.

Good luck!
Felix

Hello @Burt

there is an example for M5StickC (not Plus) which might give you an idea.

Thanks
Felix

Hello @hide4849

you also need to make sure external I2C (using 32 and 33) does not get initialized, e.g. fourth parameter of M5.begin() should to be false (which is the default).

Thanks
Felix

Hello @anichang

just wondering - maybe the issue isn't specific to PSRAM but with the power supply? I'd try a different power supply and/or shorter USB cable.

Thanks
Felix

Hello @guardian5

you are welcome. I am happy to hear you got it working.

Cheers
Felix

Hello @hbenkel

you are welcome. I am glad to hear you got it working to your liking.

Happy Stacking!
Felix

Hello @mviewlab

yes, they are just GPIO pins. Please checkout the pinmap here.

Thanks
Felix

Hello @hide4849

the CAN bus unit uses a serial connection which by default is available on M5Stack Groove Port B. However M5Core2 (w/o M5GO battery bottom 2) only has a Port A which by default is used for I2C.

So you either can try to reconfigure M5Core2 Port A from I2C to serial or stack an M5GO battery bottom 2 to your M5Core2 which then gives you Port B (and C).

Thanks
Felix

Hello @guardian5

are you aware that the buttons, when pressed, pull their respective GPIO low (and not high)? Have you tried using ESP_EXT1_WAKEUP_ALL_LOW instead?

For reference: M5StickC schematic.

Thanks
Felix

Hello @hbenkel

the only way I see is to rewire RX to an unused GPIO. Maybe this GPIO overview I've put together a while back will help you.

Thanks
Felix

Hello @xxxa0c

you are welcome. Glad to hear you got it working again. And thank you for reporting back.

Cheers
Felix

Hello @xxxa0c

yes, it is possible to turn it on/off programmatically.

UIFlow: Hardwares - Power - Set bus power mode Disable/Enable M-Bus 5V output

Arduino: last parameter of M5.begin()

void begin(bool LCDEnable = true, bool SDEnable = true, bool SerialEnable = true, bool I2CEnable = false, mbus_mode_t mode = kMBusModeOutput);

Thanks
Felix

P.S. I believe it should be on by default though.

Hello @ajb2k3

I don't know for sure for which core the GoPlus2 was designed for, but I think it was meant for M5Stack (Gray, Fire, etc.).

All I can say (looking at the schematic) is that electrically it is not fully compatible with the M5Core2.

Also, all Arduino examples I can find are for M5Stack (Gray, Fire, etc.) and none for M5Core2.

And the GoPlus (first generation) is EOL.

BTW: I don't think the '2' is because it is meant for M5Core2. It's simply the successor of the first GoPlus module. Which, if I am correct, is an unlucky (and confusing) naming.

Thanks
Felix

Hello @shally1986

same here. I think the reason for the green light blinking is that when M5Stack (Gray) is turned off it doesn't fully turn of the 5 V. (I measure about 2 V when turned off.)

That said, I think GoPlus2 was designed for M5Stack (Gray, Fire, etc.) and not for M5Core2 since w/o electrical modification you'll loose external I2C on M5Core2.

Thanks
Felix

Hello @antimix

I see the same on my M5Stack (Gray) - when I turn it off manually I still measure about 2 V on the Groove port.
In contrast when I do the same with an M5Core2 the Groove port is properly turned off when M5Core2 is turned off.

Since there is no full schematic for the M5Stack (Gray) it's hard to tell why the Groove port isn't fully turned off and if there is a way to really turn it off.

BTW: even with the Groove port not fully turned off the battery should not have been depleted completely as the battery has a built-in protection circuit which in theory should prevent under- or overvoltage.

Thanks
Felix