@DaveAstator If you're still interested in this topic, you now have the "Custom" Block designer.

907c6842-910f-4e71-adf0-8494fed5ec8a-image.png

@ajb2k3 I'm not so sure. It is a fairly large request, and probably needs funding. It needs to be initiated by the suppliers, only then it will be directed to the micropython writers.

@felmue said in StamPLC: Replace RTC battery?:

Hello @nvko23

after opening my M5StamPLC I found that the RTC battery is located at the underside of the CPU board. It is soldered to the board. So yes, I'd say it is replaceable, but the proper soldering tools are required.

BTW: the RTC battery in my M5StamPLC seems to be completely flat as I measure 0 volts.

Thanks
Felix

Thank you so much

@simondid have you even tried to look it up yourself? Google's first hit is literally this thread from April, including a full ESPHome config.

ESPHome also has a draft PR for including EPDiy as a generic display platform, and EPDiy itself has a PaperS3 pull request, which will allow the BMI270 component from the above thread to work (currently EPDiy tries to import some legacy code that breaks I2C, as patrick3399 used a custom fork of EPDiy that isn't exactly up to date).

@martincollett said in M5Stack 4IN8OUT connectors:

M5Stack 4IN8OUT

those are not usual ones

2pterm0.PNG 2pterm.PNG

@Bat21hello to tod@s
There are no answers to this incident?

Am I doing something wrong?

@holofloh

Thank You,
Rob

@felmue Yes thanks this is my current workaround (I did have the battery so I just take it out). Speaker is very loud. I guess I just have to avoid any crashes : )

@felmue Thanks.
I thought of doing this, but it is a kind of a patch, not a fix. The whole advantage of having callbacks functions that perform distinct operations outside of the main loop is almost eliminated by doing this. The main loop need to be as clean as possible, otherwise very quickly it becomes very long and messy.
Functions outside the main loop should be working properly, unless there is a fundamental reason why they cant access the display libraries properly.
It looks like a fundamental bug in how the firmware on the TAB5 treats the external functions.

Hello @eleonorafontana16

I don't know whether it will affect one or the other or both long term. The fact that both use the same I2C address is like talking to two people with the same name. Some answers might get lost due to both people responding at the same time with different answers.

Thanks
Felix

@wsanders said in Paper S3 questions:

So I think we're stuck with ESP deep sleep for now. It would be interesting to see the code for the PMS150G. I'm not sure what all that FET logic around it is for, maybe an AXP192 wouldn't fit on the board. (And why a USB chip that would prevent the device from frying when plugged into a USB PM port wasn't included.)

Yeah, just like the OG M5Paper, the PaperS3 has a bunch of shortcomings that stem from, well, I don't want to say bad design... Just not properly thought through.

The PMS150G for example is OTP, so one can't change its behaviour. Using a slightly smarter, programmable MCU would've allowed for things like forwarding of interrupt signals based on logic, and deeper management of power states or their handling.

I would've also included the following changes:

Full quad SD data pins (there's enough free pins on the S3 according to the schematics) separate MCU (like an RP2040 or similar low power MCU) for EPD handling, similar to how the M5Paper used the IT8951 (which itself was a mistake, as that MCU is super power hungry, and there was no way to reprogram it either), with open firmware, to offload display update tasks USB hub controller so both the S3 and this EPDC MCU could be natively connected to a host for flashing/debugging Better charge controller (the one used won't let the battery charge faster than 250mAh@5V, which is why you need to keep it on charger for hours). Utilising the GT911 capacitive touch "buttons" similar to the ESP32-S3-BOX, with three or four zones available on the display bottom (fat) chin

@sok Your config is mostly correct. However, due to some changes in EPDiy make it incompatible with regular library import - you need to add is as an ESP-IDF component to the project.

This sadly at the moment isn't too straightforward to do - you need to manually clone the git repo into your project's components folder (and potentially create it if it doesn't exist, it's not a default folder created by the PIO init command), and add its path to the root CMakeLists.txt

Here is an example repo and project. I recommend focusing on the aforementioned components folder and CMakeLists.txt (specifically the list(APPEND EXTRA_COMPONENT_DIRS part of the latter).

Alternatively, you can use M5Unified as a lib_dep.

@alexxai
This is precisely what I'm looking for! Unfortunately, I haven't been able to get the code to run.

Could you upload a working setup to GitHub?

@sistar_hh and every one who reads this in the future )))

If you set in your program:

Boot option set to 'Run main.py directly'
set_boot_option(0)

it will be executed by default on boot.

But! If you press G0 (BtnA) button as soon as the device is powered on, then the default UIFlow2 app will be started.

I've found it in https://github.com/m5stack/uiflow-micropython/blob/master/m5stack/fs/user/boot.py

""" boot_option: 0 -> Run main.py directly 1 -> Show startup menu and network setup 2 -> Only network setup Quick reference: when use uiflow2.m5stack.com website, click RUN button to run workspace code, boot_option won't change, if you click DOWNLOAD button to download workspace code to device, boot_option will change to 2, it means after download code done, device will auto reboot and won't show startup menu, only do the network connect, but after network connect success, you can still download or run workspace code. If you don't want do anything after boot, you can delete this whole file. If you want show startup menu again, you can hold BtnA(most device) and click reset button or repower device until show the startup menu(for those devices with screens, and this is a temporary method and may change in the future), after that the boot_option will change to 1, so next time still will show the startup menu. BTW, the network connection time has a default timeout (60s), you can modify the following definition to change this default value. """