@HappyUser Found it in the Meshtastic app on OSX under device settings. Btw, IOS app does not allow for tcp connections as it seems.

For future reference to people who search for M5 burner shows nothing... Go into your app data folder in C:/Users/appdata/roaming Delete the M5 stack folder Also delete m5 burner and its associated files from where you keep it/run it. Re-extract the files to the place you keep your m5 burner program and run it, log-in again.

Hi guys I looked at some of the comments - they are all dated from last year. I did not see anything recent. That makes me believe that the commenting feature has been turned off. Thanks Felix

@doop4 I'm not familiar with the M5Unified driver; but I've worked with the bmi270 and written a micropython driver for it.. Despite your pillow; you will still get a bit of bounce.. (I've spent time testing this chip, it's very hard to not get any bounce when you do this sort of test.) But, I think you are seeing the device going out of range; at which point you get weird/invalid readings. I dont see anywhere in your code setting the acceleration range; the max is +/- 16G, but it defaults to +/- 8g, which is where your readings appear to fail. I guess M5Unified has a method for setting this? Try the biggest range. Also; you can set filtering based on an average mode; the default is to average 4 readings (the sensor runs at 20MHz) but this can be set all the way up to 128. The M5Unified driver is using 'direct readings' (just like my driver), do not confuse this with 'FIFO' mode; which is an automated, IRQ triggered high-speed burst capture method. You read the dataset out from the chip buffer after the event has ended. AFIK the M5 drivers do not support this.

@robski If I set them manually in the GreenSwitch and whiteSwitch it works fine

At the end I used switches and it works. [image: 1773171278412-picture1.png]

Hi. Sorry but I don't use Meshtastic. The software I've written is written from scratch and is deliberately less involved than using Meshtastic's menus. There are lots of videos and articles out there to help you with the menus though.

Hi. Have you tried reading bytes from the GPS and displaying them on a serial monitor as they arrive as below, just to show you are getting data (if the serial setup is incorrect you should still receive data but it will be gibberish): // Serial is the serial monitor // Serial1 is the GPS data int intChar; char charChar; intChar = Serial1.read(); if(inChar != -1){ charChar = (char)intChar; Serial.print(charChar); } I have been using the M5Stack GPS v1.1 and it was set to 115200@7N1, not the advertised 115200@8N1 so might be an issue there (I got gibberish at first) Finally my M5Stack GPSv1.1 works fine with an Adafruit Itsy Bitsy 3v controller and an ESP32S3 based controller but not with the Seeed Wio Terminal. With the Seeed Wio Terminal I get nothing at all - no gibberish, absolutely nothing. It's as if the signal is not there (but it is !!).

On the cores3 (module connected through port A), I see no devices found on i2c scan when using esphome. It finds OK on the atom-lite. If using the "Cores3 test" binary from m5stack, I can see the address found on the i2c scan app.

Hello @alex9 it looks like yes, GPIO0 is TX pin for RS485. See pinmap here. The platformio.ini example can be found here. Running a quick search I did not find an RS485 example, sorry. Edit: Maybe try this RS485 library. Thanks Felix

Hello @JohnSal I think you only need to add one RGB unit but with number set to 6 instead of 3. Thanks Felix

Hello @HappyUser just curious, which SIM module did you settle on? Thanks Felix

Hello @hotellonely yes, it looks like the drop-down box needs fixing. In the mean time you can use all GPOs on the 14 pin header via some custom code blocks. I created an example in UIFlow2 Project Zone called M5CardputerAdv_ExtPin_Test_UIFlow2.4.2 Thanks Felix