Posts made by Cognitive5525

@NVERD

I have burned my camera with the latest firmware (1.1.0) and the the long press on the side to get access to the config does not work by me either. But if I burn it with version 1.0.0 the long press works:

However, if you can see an IP on the serial interface you have probably connected the camera to a network with a DHCP and you should be able to stream if your PC is connected to the same network.

But note that the urls are:
http://<CAM_IP>/stream for v 1.0.0.
and
http://<CAM_IP>/ for v 1.1.0.

@nzmikec said in EXT unit to measure engine RPM:

..... i2c device to count these pulses and send my device an RPM value.

What is the device you're going to use to receive the values on I2C?

Maximum RPM (and pulses per minute) would be 11,000RPM.

Maybe you don't need an external device for counting. 11,000 RPM with 1 pulse pr revolution is about 190 Hz which an ESP32 should be able to count directly by it self via one of its GPIO's.

The RTC (BM8563) is a separate chip on the M5Dial board (it is also used on some other M5Stack products).
It is literally hardwired to the battery which means you can keep track of the clock even while the M5Dial board is shut down - that is as long as you always keep an un-depleted battery connected to the board. The BM8563 chip consumes less than 3 µA@"stdLiIonVoltage"

@felmue said in M5Dial, no wake up with button:

please find my measurements here.

What voltage did you use?

M5Dial.h includes M5Unified.h. See here.

Ah OK! I see you are using a "dedicated" library for M5Dial which in term relies on the "general" M5Unified library. I found a similar "dedicated" for the CoreINK but that seem not to use M5Unified.
So I stick with using M5Unified "directly"..

@felmue said in M5Dial, no wake up with button:

please find my example here.

I can see you import M5Dial.h is this supposed to be a part of M5Unified?
I use M5Unified.h in my code for my Core INKs..

@felmue said in M5Dial, no wake up with button:

BTW: as an experiment to prove the above I removed the 5 V connection between M5Stamp and M5Dial board and now I can power M5Dial from the green connector and it does a proper shutdown (same as when powered from battery) and can be woken by the wake button.

Excellent! Now I'm curious : what is the current consumption on the external power input when the board is powered off or "sleeping"

@felmue said in M5Dial, no wake up with button:

everybody can call any of the sleep / shutdown modes as they like. I try to be consistent in writing deep or light sleep when I mean the sleep modes of the ESP32 and shutdown mode when I mean it is done via MOSFET.

Agree and I know you are. Unfortunately M5Stack are not very consistent! They call it "sleep" when the board is shut down. Their timerSleep() function is supposed to shut down their boards with BM8563 RTC.

I also agree the M5Dial should be able to "shutdownsleep" (new term 😜) when powered from the green power terminals (P5 ?).
However, where does this one lead?

@happyuser said in M5Dial, no wake up with button:

external power.

External power as-in via the green power terminals?

@felmue said in M5Dial, no wake up with button:

On the other hand when M5Dial is in shutdown mode the MOSFET is off (the only thing still running is the RTC IC). So then either the wake button or the RTC can power the M5Dial back on.

Agree!
This is completely similar to the CoreINK, but as I mentioned in this post: when the board is shut down but the BM8563 RTC is setup to wake it up then this is in "my book" also a kind of sleep mode.

The M5stack way of "sleeping" is not possible if you power via the USB..
Unless there is a bug in M5Unified library for the M5Dial I'm pretty sure M5.begin will take care of keeping G46 high.

@happyuser said in M5Dial, no wake up with button:

digitalWrite(GPIO_NUM_46,HIGH);

If you have M5.begin(); in your setup it shouldn't be necessary to pull pin 46 high, this should be done by the begin() function.

Also to wake with the "wake" button you might need to keep it pressed for a short while.

@happyuser said in M5Dial, no wake up with button:

Thank you, to be honest, no idea, but it is not an option.

I understand that it might not be possible to use the reset button in your final solution, but it is still interesting to know for the ongoing troubleshooting....

@happyuser This might also be related to your power consumption problem.

What happens if you press the reset button just before pressing the "start" button?

Cheers, I'll be interested in your findings!

As you might have seen in this small "saga" here, I have a similar problem with some (but not all) of my 30+ CoreINK devices which have a similar power control circuit.

From this Arduino example the answer is yes.

Note I think there is a typo in line 49.

Serial2.write(start_scan_cmd, sizeof(stop_scan_cmd));

should probably be

Serial2.write(stop_scan_cmd, sizeof(stop_scan_cmd));

Here is a workaround for UIFLow2.0:

import M5
import hardware
import time

# UIFlow2.0 workaround for M5.Power.timerSleep() not working properly
# on SOME CoreINK devices. On these decvices the board-power is not
# proberly turned off. However, the M5.Power.powerOff() does work
# for these devices, i.e. turning board-power properly off
 
M5.begin()
#init i2c bus with pins connected to the RTC
i2c0 = hardware.I2C(0, scl=hardware.Pin(22), sda=hardware.Pin(21), freq=400000)

##### Put your code here.
time.sleep(3)      


##### code substitution the timerSleep() function
# Set registers of the RTC. ref datasheet for BM8563 RTC for further info
# reg 0x00  always 00h
# reg 0x01  bit 2-7: always 0, bit 0: enable/disable timer int
#           0x01 = timer enabled           
reg00_01 = bytearray([0x00, 0x01])

# reg 0x0D  always 00h - clock out disabled
# reg 0x0E  bit 7: endable/disable timer, bit 0-1 timer resolution
#           10=sec  11 = min
#           0x82 = int enabled and seconds resolution
# reg 0x0F  timer value 0-255
#           0x14 = 20d = 20 sec. if reg 0x0E = 0x83 then 20 min
reg0D_0F = bytearray([0x00, 0x82, 0x14])

# i2c device address of RTC is 0x51
# Write to register address 0x00-0x01
i2c0.writeto_mem(0x51,0x00, reg00_01)

# Write to register adsress 0x0D-0x0F
i2c0.writeto_mem(0x51,0x0D, reg0D_0F)

M5.Power.powerOff()
##### end of code substitution the timerSleep() function

Have you read this document?

Update.
After many tests I think I have pinpointed where it goes wrong but not exactly why.

With the "bad" devices when driving pin 12 low the device does not turn off as expected while the "good" devices do. With the "good" devices I even get a serial monitor message saying "Brown??" (or sometimes partly, like "Bro") which I assume is a "Brown out" message generated "deep" in Espressif's libraries. I think that make sense since the power supply is kind of "brutally" removed from the ESP when pin 12 is driven low.

So basically on some "bad" M5 Core INK devices this piece of C++ code that should shut down the board by driving pin 12 low does not work:

m5gfx::gpio_lo( pwrHoldPin );

(Line #672 in PowerClass.cpp)

I have also verified it in UIFlow2.0 by "manually" pulling pin 12 low:

import M5
import time
import hardware

M5.begin()

pin12 = hardware.Pin(12, mode=hardware.Pin.OUT, pull=hardware.Pin.PULL_UP)
time.sleep(3)
pin12.off()

With above UIFlow2.0 python code the "good" devices shut down completely as expected, while the "bad" ones does not.

But there is more. While troubleshooting I (for other reasons) updated the platform.io version from 6.3.0 to 6.6.0 (I'm using Platform.IO with Vs-code to compile C++ code for the CoreINK) and then the "bad" devices began to work as expected i.e. they were shutting down by pulling pin 12 low. I noticed that the ESP-IDF version is 5.2.1 in Platform.io version 6.6.0 but t is version 5.1.1 in version 6.4.0 (for some reason Platform.io V 6.3.x is not listed on GitHub).

One more thing: Check that the 5Vout goes off when the M5dial is sleeping and when it is powered off.

I haven't studied all the details of the M5Dial schematic and I don't have one for testing myself so these are just some suggestions shot from the hip:

Check what the power consumption is when it is powered down. There should be a similar function called powerOff(). Referring to my previous explanations in your other thread about the RTC, the power consumption after powerOff() and timerSleep() should the same. If you see a difference there might be a problem with the timerSleep() in the firmware.

You could also try to cycle the 12V externally and see what the consumption is before the M5Dial is switched on. This however, will only work if the power logic is not made so that the device switch on as soon as external power is applied.

Above tests should be done without an "internal" Li-Ion battery attached, but you could also try to measure the consumption from this battery without the external 12V power source. This will tell you whether the power consumption is from the power circuit for external power (buck conv. and Li-Ion Chg.) or from the main part of the M5Dial (ESP, display etc). Again you should measure the same three things as above: powerOff(), timerSleep() and just after having connected the battery.