Hello @sam_20
hmm, I don't think I understand you statement. Doesn't every electronic part that's faulty need to be swapped? What am I missing here?
Thanks
Felix
Hello @sam_20
hmm, I don't think I understand you statement. Doesn't every electronic part that's faulty need to be swapped? What am I missing here?
Thanks
Felix
Hello guys
it is listed in the specifications here.
RTC Chip: RX8130CE (supports timed interrupt wake-up), RTC supercapacitor specification: 70000μF/3.3V, size Φ4.8×1.4mm
Edit: If I am not mistaken RTC battery charging is enabled with this line in M5Unified library.
Thanks
Felix
Hello @mpuz00
the battery connector powers everything, including RTC. But, yes, when the external battery is fully drained RTC time is lost as there is no built-in battery for the RTC.
You can find the schematics here.
Thanks
Felix
Hello @easytarget
for me your current implementation to turn off M5Tab5 actually only does a reset.
The power off pulse needs to pulse to turn off M5Tab5. See here.
I modified poweroff_now function in your library like below:
def poweroff_now(self):
"""Instant full power off. Be sure you want to use this!"""
# self._e2.set_output(_PWROFF_PULSE_PIN, HIGH)
for x in range(10):
self._e2.set_output(_PWROFF_PULSE_PIN, LOW)
sleep(0.05)
self._e2.set_output(_PWROFF_PULSE_PIN, HIGH)
sleep(0.05)
and now my M5Tab5 turns off.
Thanks
Felix
Hello @astro_m5
have you tried to flash UIFlow2.0 or CoreS3 UserDemo using M5Burner? Does that recover the backlight?
Thanks
Felix
Hi guys
while there doesn't seem to be a Pin Interrupt block you can just put some code into an Execute mpy code block.
I created an example showing interrupts use on Pins. You can find it in the UIFlow Project Zone called: M5AtomS3_GPIO_Interrupt_UIFlow2.4.0
Thanks
Felix
Hello @easytarget
from what I can tell the schematic is correct.
In the source code for M5Tab5-UserDemo GPIO36 is initialized as clock (see here).
But when I modify function bsp_cam_osc_init() to immediately return (so that the clock setup code is not executed) the camera still works fine.
Thanks
Felix
Hi guys
I created an NB-IoT Cap for my M5CardputerADV putting a SIM7080G module into a LoRa Cap case. Link to project.
Thanks
Felix
Hello @HappyUser
M5Unified has built-in LED support. My guess is that the two, M5Unified and FastLED, are 'fighting' for the LED. Have a look here. There is an example at the end of the page.
Thanks
Felix
Hello @Safeware
you probably are not missing anything from the software side. The issue most likely is caused by the PWRKEY hardwired to the STATUS output of the modem. This 'trick' is used to auto-start the modem. However it also causes the modem to wake-up from PSM immediately.
See modem schematics here.
From SIM7070_SIM7080_SIM7090 Series_Low Power Mode_Application Note_V1.02 found here.
Section 3.1 PSM Wake-up states:
Wake-up conditions:
1) T3412 timer is expired
2) Pulling PWRKEY to low level
If above is not the issue, then there are some points to check:
Thanks
Felix
Hello @VashJuan
well, it looks to me that none of the listed devices are actually I2C devices.
Thanks
Felix
Hello @HappyUser
correct, M5Tab5 has an (empty) slot on its board which takes a stamp sized expansion like CatM or LoRa or ... - see backside picture of M5Tab5.
That said, afaik at this point in time only the Stamp CatM exists. See here.
In other words, you'll need to wait until M5Stack releases a Stamp LoRa.
Thanks
Felix
Hello @ProfHuster
yes, that is what I observed too. As long as edit mode in Python code window is enabled, changes on the blockly side get ignored. (I guess that's to prevent changes from being overwritten.)
Thanks
Felix
Hello @ProfHuster
below is an example filled with print("hello"):

Please also have a look at my example in the UIFlow2 Project Zone called: M5Tab5_ExecuteMpyCodeTest_UIFlow2.3.9
Thanks
Felix
Hello @magister
in the mean time you could try and copy the correct Python statement into an Execute mpy code block. You can find it under System.
Thanks
Felix
Hello @ProfHuster
hmm, works for me with M5Tab5 UIFlow2 v2.3.9. It also got translated into Python code window.
Thanks
Felix
Hello @BruderTom
the issue seems to be an I2C conflict. Internal I2C already uses Wire1; the PPS code initializes a second I2C instance (Wire) with the same GPIOs for SDA and SCL. The result is: both I2C instances (Wire and Wire1) fight against each other.
Try replacing below line so the correct Wire1 instance is used for PPS as well:
// while (!pps.begin(&Wire, M5.In_I2C.getSDA(), M5.In_I2C.getSCL(), MODULE_POWER_ADDR, 1000000U));
while (!pps.begin((M5.In_I2C.getPort() == I2C_NUM_1) ? &Wire1 : &Wire, M5.In_I2C.getSDA(), M5.In_I2C.getSCL(), MODULE_POWER_ADDR, 1000000U));
Thanks
Felix
Hello @BR123456
it looks like the internal scan in UIFlow 2.3.8 default scanner is broken - I do not get any results either.
However if I scan the internal bus via I2C blocks it picks up all internal I2C addresses and what's connected to the M-Bus. The example is called M5Tab5_I2C_Scan_Test_UIFlow2.3.8 and you can find it in the UIFlow2 Project Zone.
Thanks
Felix