@wwhite https://docs.m5stack.com/en/guide/realtime/openai/atomic_echo_base

Hello @obolland

according to the schematic GNSS_TX becomes M5-RXD which is then available (depending on set dip switch) on GPIOs: 3, 13, 16, 34 or 35 which translates to pins 13, 22, 15, 26 or 2 on the M5 Stack bus.

BTW: Since you are not stacking the module you can set all dip switches to 'on' at the same time (if you like).

Note: I do not have the M5Stack GPS Module v2.1 so I cannot test this myself.

Thanks
Felix

@l-roca
This is not a Micropython firmware. This firmware was used to post images through HTTPS to controllers which was programmed in UIFlow.

@l-roca
This is not a Micropython firmware. You might need to configure and flash the firmware yourself: https://micropython.org/download/

Hi guys

it looks like another unfortunate regression. If I burn UIFlow2 firmware 2.4.2 onto my M5StamPLC I can control the relay and LED just fine.

Unfortunately the UIFlow2 firmware source code in github repository uiflow-micropython (at the time of writing this) is still on version 2.4.2. So it's impossible to tell what has changed between 2.4.2 and 2.4.3 causing this issue.

Thanks
Felix

Hello @jhfoo2

well, in my experience and with my M5PaperS3 it takes a couple of readouts (e.g. M5.update()) until the return value from the touch controller goes back to 0.

Please let me know if you find a more elegant solution.

Thanks
Felix

Hi @jhfoo2

well, in my case, without the 1 second delay the UI label wasn't fully updated on the display. Or in other words, ESP32 already went into light sleep while in the background the display was still finishing to update. (In your case it might be ok without the delay as the print() takes some time.)

Edit:
I think the reason for not getting the touched X, Y is that internally the wake-up code already read the touch IC registers and by doing so cleared the values. But I could be wrong about that as it is simply a guess.

I updated my example M5PaperS3_Light_Sleep_Test_UIFlow2.4.3 in the UIFlow2 Project Zone to read touch coordinates after wake-up from touch. It's a bit tricky as M5.update() needs to be called repeatedly until the number of touch points drops back to 0.

Thanks
Felix

Hello @Wambo6000

maybe you are hearing what's described on the product page here: "Abnormal Device Noise".

Thanks
Felix

Hello @jhfoo2

please have a look at the UIFlow2 Project Zone example I created: M5PaperS3_Light_Sleep_Test_UIFlow2.4.3

Thanks
Felix

Hi guys

I looked at some of the comments - they are all dated from last year. I did not see anything recent. That makes me believe that the commenting feature has been turned off.

Thanks
Felix