Hi guys
corresponding github issue for reference.
It seems there isn't an easier way just (yet) than using Espressif Library Builder.
Thanks
Felix
Hi guys
corresponding github issue for reference.
It seems there isn't an easier way just (yet) than using Espressif Library Builder.
Thanks
Felix
Hello @peolsolutions
please stop posting mostly irrelevant information. This topic is about how to remove the magnets - not about what the magnets are good for.
Thanks
Felix
Hello @alexcap
according to the schematic, your SW2 setting and the code example I would say that you should be able to receive GNSS data on GPIO16 with baud rate 38400.
Note: I don't have the M5GNSS module to test myself, so my conclusion could be incorrect. I also do not know if the uBlox GNSS module needs to be activated via software commands in any way.
Thanks
Felix
Hello @paydogs
my M5PaperS3 running the factory test shows about 4.19 V when fully charged and still on USB-C. When I remove external power it drops to about 4.12 V.
Thanks
Felix
Hello @paydogs
I was just about to suggest that from your video it looks like the battery might be flat.
Glad you figured it out.
Thanks
Felix
Hello @scroggyg
the added 5 V power switch I use to fully turn the modem off when I want to use M5Tab5 without modem (without the need to de-solder it.
The other modification to control the POWERKEY of the modem via GPIO (instead of the default auto power on) of the modem is required for two cases:
Thanks
Felix
Hello @kuriko
thank you for this information. I just retried M5StampPico with UIFlow1 and changed the Start Mode to USB Mode and back to Internet Mode. In both cases I get the blue light. So I guess it's not connected to the server.
Thanks
Felix
Hello @scroggyg
in UIFlow2 under Hardware you can find the Watch Dog Timer (WDT) module.
I created a example in the UIFlow2 Project Zone: M5Tough_Watchdog_Test_UIFlow2.2.8
Thanks
Felix
Hello @marnix201
I can confirm there seems to be an issue with UIFlow1 firmware for M5StampPico as I get the same result: solid blue light.
I also tested with M5AtomLite / UIFlow1: same issue - blue light.
However when I use an M5StackCore it connects ok to UIFlow1.
Note: above tested with UIFlow1 firmware 1.14.5
BTW: Any reason you are using UIFlow1? I tried M5StampPico with UIFlow2 and that worked for me.
Thanks
Felix
Hello @hacxx
please stop posting incorrect / not very useful information. W5500 is different from ENC28J60 and therefore EthernetENC or UIPEthernet library cannot be used for W5500. Thank you.
Thanks
Felix
Hello @hacxx
please refrain from posting in year old threads which are already resolved. Thank you.
Thanks
Felix
Hello @toffifee
your code works for me using an M5AtomS3 (non R).
That said, M5AtomS3 uses a different IMU chip (MPU68860) than M5AtomS3R (BMI270 / BMM150). So my best guess would be that UIFlow2 is not fully adapted to M5AtomS3R (yet).
@hacxx : FYI @toffifee is using UIFlow2 - there is no Imu.begin()
.
Thanks
Felix
Hi guys
I now have the LTE-M modem fully integrated into M5Tab5 (including proper external antenna). Info here.
Thanks
Felix
Hello @Boomvalt
I do not have an M5AtomS3R, but with my M5AtomS3 it works for me. See M5AtomS3_PaHUB_EnvIII_EnviV_UIFlow2.2.8 example in UIFlow2 Project Zone.
Make sure you power-cycle everything after changing the I2C address of PaHub. And maybe try another channel for the EnvIII unit?
Thanks
Felix
Hello @Boomvalt
PaHub and ENV III unit share the same I2C address 0x70 by default. See here.
Thanks
Felix
Hello @wrs642
from this and your previous post I would guess that there is no battery connected or it is not charged (enough).
Thanks
Felix
Hello @Schnoble
clever! Maybe you could put your modified version into an Execute mpy code (eg. import)
? This block can be found under System
.
Thanks
Felix
Hello @Schnoble
you are not doing anything wrong I think. The issue is with UIFlow2 firmware for M5AtomLite. As far as I can tell the default pins are for M5AtomS3 (Lite) and there is one additional pin, which cannot be set from the init block and it is set to a GPIO (8) only available in S3. See here.
BTW: I've created a PR for the issue. So hopefully it will be fixed in a future firmware version.
Thanks
Felix
Hello @smily77
I believe SDIO2 is used so the communication between ESP32P4 (master) and ESP32C6 (slave) can be exclusive, e.g. not shared with other slaves.
Thanks
Felix