@QuiqueMartinez We don't have any camera model with night vision

@felmue Thank you! I learned something today by downloading the PDF's and applying what you explained :)

@anubisdarkwatch said in Cardputer keeps restarting.: @robski So with another firmware it was showing as having 98% charge, I just loaded UIFlow2 and it showed as 22%. Weird. So I have it charging now, hopefully that is the issue. think it charges battery when connected and ON/OFF switch in ON position

@felmue You're absolutely right about VBUS. When I flashed the example firmware from the Arduino IDE, the power supply worked normally. However, the factory firmware did not. How the hell is it possible that such a thing isn't described anywhere in the documentation? Thank you, you really helped me a lot.

Hello @wsanders this issue has been fixed in recent M5Unified and M5GFX libraries - see here. Make sure you are using the latest versions of these two libraries. BTW: I am using this feature in my non flickering RTC clock example - see here. Thanks Felix

Unfortunately you did not post your code so no one knows how you try to send the midi messages. Check first: does the device apear as USB-MIDI-Class in your computers device manager? Probably it is shown as a USB-Serial-Class device (which MIDI indeed is) but your MIDI application (seems to be a top secret application as you don't wrote which one) expect a MIDI-Class device. Maybe this helps: https://github.com/esp32beans/ESP32USBMIDI

Hello @cepics try changing the line to: Serial2.printf("AT+CSTT=\"%s\",\"%s\",\"%s\"\r\n", apn, user, pass); Thanks Felix

Looks like it has to do something with the bootloader. I previously flashed the full factory-firmware which comes out of ESHome(platformio) build, but if I just flash the firmware to 0x10000, then it boots up all the time from battery as well. Needs more digging what could go wrong with platformio bootloader.

@LordInchcape Using M5CoreS3_SDCard_read_dir_UIFlow2.0.4 the following micropython will work:- *import machine import os card = machine.SDCard(slot=2, sck=36, miso=35, mosi=37, cs=4, freq=1000000) os.mount(card,"/sd") print(os.listdir("/sd")) f = open("/sd/test.txt", "w") f.write("Hello world\r\n") f.close() g = open("/sd/test.txt", "r") print(g.read()) g.close() os.unlink("/sd/test.txt")** Still to determine if it treads on something else.

Hello @silentrain23 I think you probably just need to wait a bit longer for it to register. From the AT Command document (link here) the 2 in the AT+CREG 0,2 response means: Not registered, but MT is currently searching a new operator to register to Thanks Felix

@felmue I did not see that error. The afterimages have gone away. Leaving the screen all black and powered off a few minutes will help clear it, this is common EPD behavior.

I got the bar graph demo to work: Using the latest M5 board package, you should see a board "M5PaperS3", so the requirement to downgrade the esp32 board package to 3.0.6 is not necessary. Use the "M5PaperS3" board definition instead of the generic ESP32S3 one. The instructions to install epdiy are somewhat vague. Simply clone the epdiy library to your arduino library directory and it will work, doing a "make" is not necessary. Follow the rest of the instructions at https://docs.m5stack.com/en/arduino/m5papers3/program, pay careful attention to the special board settings for OPI PSRAM, etc.

@PharkieB My idea, above, works! Now, I can turn ON my Lipo-powered M5Stack Dial with the "Wake" (front button), it loads my UI Flow program, and then I can tell the software (btn A) to switch it OFF, when that's appropriate: [image: 1734885872623-screenshot-2024-12-22-at-16.40.40.png] [image: 1734885873073-screenshot-2024-12-22-at-16.40.54.png] This is using the "System >> Execute mpy code" block with this for on: hold_pin = Pin(46, Pin.OUT) hold_pin.value(1) and this for off hold_pin = Pin(46, Pin.OUT) hold_pin.value(0) Ideally this would be a standard UI Flow block for the M5Dial (keep device on once awake and on battery). It seems odd I've had to invent it, based on detail in the documentation.

@ScheduleDisplay Connecting to always ON USB Power will permanent charge your battery and hold it at fully charged level. Not the best state to store a lithium battery over longer time. Best will be to remove it (or at least disconnect).