Posts made by felmue

Hi guys

even though I read the warning about not using certain types of chargers with M5PaperS3 I managed to do so anyways.

Suffice to say, M5Paper released some magic smoke and wouldn't start anymore.

I cracked it open from the back (as I think the eInk display is glued in) to get access to the board. (I do not recommend doing that as it is a destructive process.)

With the eInk display and touch disconnected I started to inspect the board.

I found the charger IC USB-C protection diode pack being dead from the look of it. I removed the charger IC (as it is not strictly needed to run) I replaced the USB-C protection diode pack and found the MosFet IC getting pretty hot. So I removed the MosFet as well and injected some voltage (4.2 V) after the MosFet which revealed that the 3.3 V regulator took some hit as well. I replaced the 3.3 V regulator with a similar one I took from an M5Atom.

With two ICs MosFet removed and the 3.3 V regulator replaced M5PaperS3 took a reasonable small amount of current. I also measured ok voltages for the eInk display so I dared to reattach the display and touch screen and yo and behold - M5PaperS3 is alive again.

Now I need to order some replacement ICs MosFet.

You can see the opened M5PaperS3 and the dead ICs here.

Thanks
Felix

Hello again

just wondering. There is actually a check in M5GFX.cpp about whether epdiy.h is included or not. Do you remember, did you see this error in the log (I do not):

#if !__has_include (<epdiy.h>)
              ESP_LOGE(LIBRARY_NAME, "M5PaperS3 need install EPDiy library");

Thanks
Felix

Hello @wsanders

I am sorry I scared you and I am glad you figured it out. Thank you for letting me know.

I am using Visual Studio Code and for me it works/worked without this include. But yes, you are correct it is mentioned in the docs to include <epdiy.h> and when I do that on my end it still works.

Thanks
Felix

Hello @wsanders

please see PR on how to get rid of the crash.

BTW: I like the little blinking dot.

Thanks
Felix

Hello @wsanders

the function of the M5PaperS3 power button is described here.

With USB connected I can power off my M5PaperS3 with a power button double-click. I am running a simple program periodically reading the battery voltage and printing it into the log. And the log stops when I double-click the power button.

Thanks
Felix

Hello @os-ronald

hmm, both options (Run and Download) work for me (via USB connection).

Which UIFlow2 firmware version did you install on your M5PaperS3? I used v2.2.0-hotfix-2.

Thanks
Felix

Hello @kuriko

just curious - why are your setting GPIO5 to input? This disables the display - is that what you intended?

Thanks
Felix

Hello @digiajay

ok, understood.

Well, you cannot set a different EOL character and therefore you cannot use UART block read line.

However you can use block count of available and read 1 bytes etc. to read chars sent from your device. As long as the char received is not your EOL char, append them into a buffer. And when you receive your EOL char do something with the chars accumulated in the buffer, then clear the buffer and start over.

Thanks
Felix

Hello @romor001

please check out my example in the UIFlow2 Project Zone: M5Paper_Read_Intern_Temp_Humid_UIFlow2.0.9

Thanks
Felix

Hello @ioamas

thank you for reporting back. I am glad to hear you got it working.

And sorry you had to sort out a not so well assembled Battery Bottom2.

Thanks
Felix

Hello @ioamas

I'd say if you place just the Battery Bottom2 (without M5Core2 stacked) onto the Battery Bottom Charging Base and neither red or green LED light up then something's faulty.

I tested the above setup and while the battery is being charged the red LED lights up and when the battery is full the green LED is on.

If that is not the case in you setup then you could check if the pins labelled 5 V and GND on the Battery Bottom Charging Base actually deliver the 5 V from the USB-C charger. Next is checking if the pins make good contact with the Battery Bottom2.

Thanks
Felix

Hello @Marc-SKIL

unit EXT.IO2 can only control one (1) RGB LED per output. So what you get is correct. Have a look at the protocol here.

Thanks
Felix

Hello @digiajay

you can use UART x write "" block which will send data without line end and then use UART x write raw Data 0x7E to send the special line end.

Thanks
Felix

Hello @BertM

I get the same error using platform 6.4.0 which supports Arduino 2.0.11.
You can see the used platform / Arduino version in your log:

PLATFORM: Espressif 32 (6.4.0) > M5Stack StampS3
framework-arduinoespressif32 @ 3.20011.230801 (2.0.11)

Try modifying the platform parameter to:

platform = espressif32@6.9.0 ;  6.9.0 - 2.0.17

This should download platform version 6.9.0 with Arduino version 2.0.17 and with that the error is gone for me.

Thanks
Felix

Hello @laursena

unfortunately I don't know the answer to your question about the power consumption and if M5Core2 can handle it.

However what I can tell you is that you do not necessarily need the PaHubs. The M5Stack I2C weight measurement units allow for the I2C address to be modified - so you could give each unit its own I2C address and simply connect them in parallel.

Thanks
Felix

Hello @ScheduleDisplay

I am glad to hear it works for you now.

Yes, the battery will drain much faster when using ESP32 deep sleep or light sleep compared to a full shutdown.

You can find the currents for all three modes here.

Thanks
Felix

Hello @ScheduleDisplay

in order to use ESP32 deep sleep ESP32 and external power to the Grove ports need to stay on. Grove power is required for the pull-up resistors in the button unit. (Internal pull-up is too weak.)

I can get your sketch to work if I comment the following lines:

//    M5.shutdown();                    // Shutdown the display and peripherals

//    M5.disableEXTPower();             // Disable external power supply

and adding this line:

gpio_hold_dis((gpio_num_t)M5EPD_EXT_PWR_EN_PIN);

after the other gpio_hold_dis() line.

Plus adding this line:

gpio_hold_en((gpio_num_t)M5EPD_EXT_PWR_EN_PIN);

after the other gpio_hold_en() line.

Thanks
Felix

Hello @HappyUser

have you tried to connect the RFID2 to another channel than 0? Does it show up then?

Do you have other I2C units which you could connect to any channel just to see if they get picked up?

For a scan an I2C device doesn't need to be initialized.

Thanks
Felix

Hello @SB12345

ok, have you tried to only connect one TOF4m to port C? Does that work?

Thanks
Felix

Hello @ScheduleDisplay

maybe below lines are the issue?

pinMode(WAKEUP_PIN_26, INPUT_PULLUP);  // Enable internal pull-up for stability
esp_sleep_enable_ext0_wakeup((gpio_num_t)WAKEUP_PIN_33, LOW);  // Wake when pin goes LOW

you enable wakeup on GPIO33 while the pullup is set for GPIO26.

Thanks
Felix