@mb How do you get NTP time in UiFlow2? O cannot see NTP module. It was in previous UiFlow, but now I can't find it.

@mb this issue was fixed in 2.1.8-hotfix

@mb If the program runs normally, I don't think this should be a problem

Unfortunately as of today, my Battery isn't working again. I can update and run will using USB power but unplugging kills the M5Core.

Hi felmue, Thank you for your comment. I have done with M5.Axp.SetVibration command. Thank you!

Hello, @wsanders The app0 and app1 partitions are used for firmware update with rollback in case of failure. It is also used by the OTA function. https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/ota.html

Hello @macsbug there should be no need to cut traces in the GPS module. For M5Core2 defining GPIO13 and GPIO14 in UiFlow (instead of GPIO16 and GPIO17) should do the trick. Or am I missing something? Thanks Felix

Upon further testing and investigation, my original observation is incorrect. It seems that the blocks are mostly working correctly. It does not seem to be an issue with a specific version either. When I setup a simple UIFlow sketch to "Restart after 10 seconds", the first time I run it it correctly restart after 10 seconds. It then seems that the IRQ register isn't set right because it won't restart again if I immediately run the code again. If I instead power of the Core2 and then power it back on with the button on the side it will then run the code correctly and restart the device. It does not seem to be a hardware issue as the example wake on rtc code in the M5Core2 arduino library works correctly every time.

Hello @wa-berlin you can't. Functions w/o numTimer argument will return the internal number assigned to a specific timer. You don't have direct control about which timer gets which number, but you can keep a record of the number assigned to a given timer to further manipulate it. Below is an example with 2 timers (A and B). Timer A counts up ever 2 seconds, whereas timer B counts up every second and stops at 10. With button A you can enable and disable timer A. With button B you can restart timer B once it has stopped. #include <M5Core2.h> #include <utility/M5Timer.h> M5Timer M5T; int mytimerA = -1; int mytimerB = -1; int mycountA = 0; int mycountB = 0; void myTimerACB(void) { mycountA++; } void myTimerBCB(void) { mycountB++; } void setup() { M5.begin(); M5.Lcd.setTextSize(3); mytimerA = M5T.setInterval(2000, myTimerACB); mytimerB = M5T.setTimer(1000, myTimerBCB, 10); } void loop() { M5.update(); M5T.run(); if(M5.BtnA.wasPressed() == true) { if(M5T.isEnabled(mytimerA) == true) { M5T.disable(mytimerA); } else { M5T.enable(mytimerA); } } if(M5.BtnB.wasPressed() == true) { if(M5T.isEnabled(mytimerB) == false) { M5T.deleteTimer(mytimerB); mycountB = 0; mytimerB = M5T.setTimer(1000, myTimerBCB, 10); } } M5.Lcd.setCursor(0, 0); M5.Lcd.printf("Timer A: %s\n", M5T.isEnabled(mytimerA) ? "enabled " : "disabled"); M5.Lcd.printf("Timer A: %04d", mycountA); M5.Lcd.setCursor(0, 100); M5.Lcd.printf("Timer B: %s\n", M5T.isEnabled(mytimerB) ? "enabled " : "disabled"); M5.Lcd.printf("Timer B: %04d", mycountB); } Good luck! Felix

@felmue While I was writing to Core 2, I pressed the power button for a long time and the writing was successful. Thank you.

Hello @flex Sorry, I don't know if it's meant as workaround. M5Stack is not shy to use the term 'ultra low power' or 'very low power' for their products. And that is correct for several ICs used in M5Stack devices, like the ESP32 itself and yes, LoRaWan etc. Unfortunately however, in my experience, the way M5Stack integrates those low power ICs into their products very often isn't ideal to create a low power device. But to be fair, they also need to ensure, that stacking various modules to the older cores (Basic, Fire, etc.) and newer cores like M5Core2 do not destroy each other. So, it could very well be that the two diodes I mentioned before are a precaution. BTW: I myself asked this question a long time ago for M5Core2, but it never got an answer. Thanks Felix

@chriszang and another update. So I am happily working on my CAN receiver sketch and just noticed that I forgot to press the button that grounds INT-output of the mc2515 but the upload still worked. Gave it another try (w/o pressing the button) and it's still working - weird. Then I swapped this COMMU module for my 2nd COMMU Module and here the upload doesn't work. My explanation is that the grounding of the mcp2515 INT-output basically created a short circuit in the transistor that controls this pin and eventually burned it out. Not a big problem for me as a) I am not using interrupts in my sketch b) I have a 2nd COMMU unit I just wanted to warn you guys that grounding the INT output has unintended consequences.

Thank you!