you are welcome. Glad to hear you got it working again. And thank you for reporting back.
yes, it is possible to turn it on/off programmatically.
Set bus power mode Disable/Enable M-Bus 5V output
Arduino: last parameter of
void begin(bool LCDEnable = true, bool SDEnable = true, bool SerialEnable = true, bool I2CEnable = false, mbus_mode_t mode = kMBusModeOutput);
P.S. I believe it should be
on by default though.
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.
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.
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.
works for me. Tried with an M5Stack (Gray) and M5Core2. Both motor ports A and B work in both directions just fine.
It could be a hardware issue. Each port uses a H-bridge which consists of four MOSFETs each. For one direction two of the MOSFET conduct and for the other direction the other two are in use. So if one MOSFET used for a give direction is broken, the other direction still works.
I stand corrected. You are right. Thank you for pointing that out.
The GPIOs of the second SPI connection I've mentioned above (18, 19 and 23) are only relevant if one needs SPI bus speeds above 40 MHz apparently. If the SPI bus speed is 40 MHz (or below) almost any GPIO can be used for SPI as you pointed out.
I assume you've tried this example as well?
This example should start of at the time (18:56:10) and date (3/22/2019) set in
setup() and then advance automatically. If the clock is stuck at that time and date, then I'd say probably something's wrong with the RTC in your M5StickCPlus.
charging the battery via USB-C is the preferred way.
When you say they are stuck at 3.7 V, is that the value your Arduino program displays or is that the value you measured between GND and BAT pin?
from the schematic there should be no difference whether you power M5Atom via 5V on the Groove connector or the 5 V pin in the back. Measuring for continuity between Groove and the respective pins in the back also shows they are connected 1:1 and are the same.
Running a simple sketch on my M5Atom Matrix, which only connects WiFi and is showing that by changing the LEDs from red to green, I see that working ok with voltages from 2.8 V to 5.2 V.
BTW: I am getting the same results with an M5Atom Lite.