@hallinen Yes, I saw your comment over on https://github.com/m5stack/M5AtomS3/issues/23 The solution to my identical issue/14 was to burn-back (erase all) to 'Arduino15/staging/packages' and re-install the M5 latest board definition. Tinyu-Zhao's solution was: "Perhaps there is a local cache package that is not downloading the latest M5Stack version definition Please delete the following path, uninstall the M5Stack 2.0.6 definition and try again /Users//Library/Arduino15/staging/packages"

Ah, thanks. Now I realise that I will develope the sketch further.

I have found out how to use the fonts within the M5GFX library; #include <Arduino.h> #include <M5GFX.h> M5GFX display; void setup() { display.begin(); display.setTextDatum(middle_center); uint16_t x = display.width() / 2; uint16_t y = display.height() / 2; display.setFont(&fonts::FreeMonoBold24pt7b); display.drawString("Test", x, y); } void loop() { }

Hmm, I get that. And appreciate that some of what we are doing here is frontier work, but when breaking changes result in the most obscure error messages know to man it's still a bit painful. The catch to response to repair time is perhaps something the community could work on, with and without GitHub. I'll cheer up after a nights sleep. I've still no idea on a fix for the fault posted. Likewise, I have had to swap from M5Core2 to M5Unified for an error earlier this am, so any other thoughts gratefully received. Update: same Arduino v2.2.1 --> PC fine, macOS the above error [groan], again.

I found a solution. An example you can find at https://www.waveshare.com/wiki/BMM150_3-Axis_Magnetometer_Sensor (the one linked from Example Demo) with a proper modification worked with BMM150 in Env II Hat. Here is the procedure. Download the zip file from the Example Demo link. Open bmm150_Arduino.ino under Arduino > bmm150_Arduino Search Wire.begin() in the code (you can find one in the line 149) Change it to Wire.begin(0, 26) This is necessary if you are using a Hat version of ENV II HAT, which is connected to the GPIO pin side of the M5Stick variants. If you are using ENV II Hat connected the Grove port, you don't need to change it. After this modification, the code should work.

I used this website http://www.rinkydinkelectronics.com/t_imageconverter565.php to convert to I think RGB565 from PNG

Add line sht30.init(); straight after Wire.begin(26, 32); // Pins 19, 22 if using Atom-Mate and hats. For the StickC and ENVII hat example it needs the following change as well. SHT3X sht30; // Changed from SHT3X sht30(0x44, 1) Swap the StickC library out for Atom and comment out the LCD lines, it works perfectly as well with the Atom-Lite/Atom-Matrix. Two lines above need changed in the examples.

Yes, M5StickC (non-Plus). With the changes above it has been perfectly robust. Happily turns on/off and stays connected to Arduino IoT Cloud.

There is an A & B pulse from each wheel. I think you'll need to acquaint yourself with Quadrature Encoders. A quick check to do: Try to make two temporary but firm mechanical stops with say 100 degrees distance (not important to know the exact angle between them) and then repeatedly move the wheel between the stops. You should get the same two values (+/- 1 or 2) every time at each stop.

It works!! Thank you for the suggestion @gavin67890! The temperature is about 6 over and the humidity is 10% less than what my desk station is showing me, but I am glad that the hardware is ok. Now, to inspect the Python code and see where is the problem. [image: 1695909439290-20230928_164927_resize_resize-resized.jpg] Also, one important aspect I was missing: the GitHub code was trying to read a SHT20 while the PM2.5 (K023-B) has a SHT30.

@felmue That was the problem Thank you very much!

@alan-zhang said in SIM7080G Module speed and stability: I've tested the SIM card from a phone and it's 1MB/s download and upload. Your phone might be using 3g/4g/5g/LTE and not NB-Iot or Cat-M. In fact Ive never seen a phone that uses NB-Iot or Cat-M (Doesn't mean they might not exist though) M5Stack does sell an LTE module if you want LTE speeds though.