Hello @msxgames this is great. Thank you for the detailed feedback. I am sure it will be helpful to others in the future. Thanks Felix

I switched over to this library https://github.com/tanakamasayuki/I2C_MPU6886 There is no modification of the EPD Library necessary. Now it works with there example code.

Hello @Berni4 the C3' TX (GPIO21) is connected to the USB UART RX pin; in other words the C3 is driving the line, therefore your code can blink an LED on GPIO21 just fine. However the C3' RX (GPIO20) is connected to the USB UART TX pin; in this case the USB UART and the C3 are both trying to drive the line and it looks like the USB UART is winning. In short, without hardware modification I don't see a way to use GPIO20 for anything else than UART functionality. Thanks Felix

Hello @Thomasx sorry to disappoint you, but sadly not every library has been written in a way that it can automatically adapt to a new product. Or sometimes the init() or begin() functions need to be provided with different parameters to account for a specific product which doesn't use default values. And I am afraid in some cases you have to directly modify the library yourself to make it work with a specific product. Thanks Felix

noOne?

Download all files from here: https://github.com/m5stack/TimerCam-arduino/tree/master/src (zip link: https://github.com/m5stack/TimerCam-arduino/archive/refs/heads/master.zip) And replace all files in your TimerCam Lib src folder to downloaded: @jmakiv /Users/************/Documents/Arduino/libraries/TimerCam-arduino-master/src/ @redbox @paloces C:\Users********\Arduino\libraries\Timer-CAM\src\

Hello @herb great, I am happy to read you figured it out. Thank you for letting me know. Thanks Felix

Hi I had the same problem, but the suggested (uint16_t) correction in M5EPD.cpp lead to another problem: in the files adc.h, the statement #include "soc/adc_channel.h" must be inserted after tge firts #include statement. Chris

@macsbug Many thanks, cheers!

Hello @Marco-Cantoni try FALLING instead of LOW when calling attachInterrupt(). Thanks Felix

Hello @rfaass yes, when I lookup the NB-IoT coverage of different providers the picture I get is that NB-IoT is available mostly in Europe whereas USA is mostly LTE-M. IoT Creators seems to offer NB-IoT in the USA. It is my understanding they work with Deutsche Telekom which I guess is T-Mobile. So the T-Mobile SIM you ordered should hopefully work. If not, maybe check them out directly. BTW: I think the SIM7020G is the most global variant SimCom offers; but yes, it's NB-IoT only. M5Stack offers a Unit and two Modules using the SIM7080G (NB-IoT and LTE-M) so maybe they are working on a variant that fits the M5Atom as well. Thanks Felix

Hello @hrsavla there are multiple issues to fix this for compilation with Arduino framework 2.0.1. I've attempted to solve those issues here - try it at your own risk. Thanks Felix

I think I figured it out. The problem was apparently the version of the board I had loaded in Arduino's Board Manager. I was using The official M5Stack 2.0.0 board file. This does NOT work. It has sending the LED data at effectively the wrong baud rate. Reverting to 1.0.9 solved the problem. How do I let the good people at M5Stack know they have this bug to fix?

@felmue said in Stamp Pico USB Serial: Or in other words, there is no way to directly connect D- and D+ from the USB-C breakout to the M5PicoStamp. Hi Felix, thanks alot for that information. Was hoping this converter could be easy be done by some ICs and restistors maybe but would be too difficult for me yet. So i think i will get another controller with built in or a cojntroller with onboard USBC connection. Makes no sense to spend much time and money if the device will be procudes 100 times each with MCU and a serial converter. Your help was great!!! Best regards Hannes

OK, I'm learning... So I don't just need ESP32 code, it needs to be Micropython. So let's say I can find an MQTT broker written in MicroPython, how will I go about adding this into a UI flow project? I want to use UI Flow to do the user interface components, and include an MQTT broker. UIFlow already has an MQTT Client, but it does not look like there is a broker.

Thanks Felix for the hint. Will try that and report about ... Regards Peter