Posts made by felmue

Hello @gordsh

it looks like this warning/error has been fixed a while ago - see here.

Thanks
Felix

Hello @achayne

I understand your frustration. However all IP addresses you provided are listed as spam and/or brute force attacks when checking on CleanTalk from which we have the information which IPs to block.

May I ask you to reach out to CleanTalk to have those IP addresses deleted from their database and then report back here so I can adjust our list accordingly?

Thanks
Felix

Hello @LordInchcape

not that I know of. That said, have you tried to see what Micropython code UIFlow2 produces?

Thanks
Felix

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

Hello @plackettsj1

the PPS 13.2 module is meant to be used with an ESP32/ESP32S3 based M5Core like M5Stack, M5Core2 or M5CoreS3 - see PPS documentation here.

Thanks
Felix

Hello @wsanders

you answered your question yourself - power off functionality is not implemented yet on M5PaperS3 and therefore RTC alarms do not work.

Some background (as I understand it). Some M5Stack devices - like M5Paper (non S3 version) - can not power off while being powered from USB so the current code in Power_Class does the following: it sets up both, RTC alarm and ESP sleep functions (e.g. deep sleep and light sleep). It then first attempts to power off - which works when powered from battery, so the code execution ends here. However when powered from USB, power off does nothing and the 'backup' ESP sleep functions take over.

So with M5PaperS3 and the current state of Power_Class when you call timerSleep(int seconds) it works because ESP sleep function is setup and can take over. However when you call the other timerSleep() functions nothing happens as the ESP sleep functions are not setup here and power off isn't implemented yet.

And when you call setAlarmIRQ(30) and powerOff() manually nothing happens either - same reason again - power off is not implemented yet.

BTW: you can still test your code though - during the 30 seconds you can double-click the side button to actually power off M5Paper and when the time is up it should power on again.

Thanks
Felix

Hi guys

Update: M5PaperS3 fully restored and as good as new. :-)

Thanks
Felix

Hello @nelll

have you tried to not use M5AtomS3 library and only use M5Unified library and replace all AtomS3. with M5.? Note: not tested myself - just an idea.

Thanks
Felix

Hello @nelll

it looks like the crash is happening when AtomS3.BtnA.isHolding() is called.

Now the strange part. When I modify below two lines in put_asleep() the crash goes away.

//    M5.Display.sleep();
//    M5.Display.waitDisplay();
    AtomS3.Display.sleep();
    AtomS3.Display.waitDisplay();

I can only guess that while put_asleep() isn't called anywhere it still confuses somehow the namespaces - but that is really just a wild guess.

Thanks
Felix

Hello @marnix201

thank you for reporting back. I am glad you figured it out.

If the broken PPS modules no longer show up in an I2C scan (which I guess also means they can no longer be updated via M5CoreS3) you could try to copy the STM32 firmware from a working PPS module to the broken ones.

You'll need STM32CubeProgrammer SW and STLink HW for that though. And make sure to not overwrite the last sector as it holds the calibration data. See here.

Thanks
Felix

Hello @marnix201

hmm, do you have another M5Core device (not M5CoreS3) to test with?

I recreated your setup, M5CoreS3 (with UIFlow2.0.0-hotfix-2 firmware) stacked with PPS 13.2 Module. I run an I2C scan and turning PPS off and on in a loop and it hasn't failed so far.

You can find it in the UIFlow2 Project Zone: M5CoreS3_PPSModule_Test_UIFlow2.0.0

Thanks
Felix

Hello @marnix201

is the PPS 13.2 module securely stacked to the M5CoreS3? E.g. by using screws. It could be a shaky connection causing the issues you are seeing.

Thanks
Felix

Hello @NickMaddock

please have a look at the schematics (top right corner). To me the 120 ohm resistor R16 looks permanent and I can see no switch to disable it.

Thanks
Felix

Hello @wsanders

above measurements are with IMU off. You can find all numbers here.

Thanks
Felix

Hello @claudiu

eInk devices are a bit tricky as the screen keeps showing the last image even without power which makes it difficult to know if the device (e.g. MCU etc.) is actually running or not.

As for tips: keep in mind that M5PaperS3 is a very young product and I found that not all functions are fully implemented yet. So if something doesn't work as expected this could be the reason.

Thanks
Felix

Hello @wsanders

you are correct, rtc_time_t is not the limiting factor, it's the 8 bit register in the RTC holding the time for the timer functionality.

Well, it depends on what you consider "almost as good". With M5PaperS3 fully powered off (with my PR) at the battery I measure about 9.6 uA (which is close to the advertised 9.28 uA) whereas in ESP32 deep sleep I get about 5.1 mA (which is about 550 times higher).

Thanks
Felix

@claudiu

like @kuriko already mentioned, that is the nature of an eInk screen - it retains the last picture, even w/o power.

That said, I created a example in the UIFlow2 Project Zone called: M5PaperS3_LED_PowerOff_UIFlow2.2.0 which turns on the green LED on the backside, waits 5 seconds and then powers off. (And as an indicator the green LED also turns off.)

Thanks
Felix

Hello @MatChr

M5CoreS3SE doesn't have a battery, or am I missing something here?

Thanks
Felix

Hello @wsanders

there are two issues I can see with M5.Power.timerSleep(time):

1. calls M5.Rtc.setAlarmIRQ(time) which can only handle up to 255 minutes. See comment here.
2. calls _timerSleep() which calls _powerOff(true) which never really powers M5PaperS3 off as this functionality has not yet been implemented and therefore uses ESP32 deep- or lightsleep as fallback. See here.

The first point is probably responsible for the premature wake-ups you are seeing.
The second point is probably the reason for the status LED not always turning off.

Edit: I've created a PR to fix the power off functionality.

Thanks
Felix

Hello @aleekwen

well, looking at the schematics there shouldn't be a difference about whether M5PaperS3 is running from USB or battery.

That said, is the battery of your M5PaperS3 charged? My M5PaperS3 battery was fully depleted when I got it and it took several hours for it to be fully charged.

Thanks
Felix