Best posts made by SarahC

Right now in August 2021, there's two types of M5Go bottom, M5Go, and M5Go2.

The M5Go2 remaps Port C's pins that are used on the Core2 for the PSRAM. This means that there's no unsoldering needed on the Core2 to use Port C, and the PSRAM now stays enabled! Yay!
(If you DID try using your M5Go (not M5Go2) on a Core2... you'd break PSRAM support. Core2 NEEDS a M5Go2.)

Here are the pin positions for Port A, Port B, and the Grove port, for the Core and Core 2:

Core (M5Go):
Port A (Red) : Pins SCL 22, SDA 21 : I2C, Supports digital and I2C mode,
Port B (Black) : Pins DAC 26, ADC 36 : DAC/ADC, Is generic IO
Port C (Blue) : Pins TX 16, RX 17 : Supports UART mode however outside of UIFlow the IO pins of the esp32 support various different modes.

Core 2 (M5Go2 bottom):
Port A (Red) : Pins SCL 32, SDA 33 : I2C, Supports digital and I2C mode,
Port B (Black) : Pins DAC 26, ADC 36 : DAC/ADC, Is generic IO
Port C (Blue) : Pins TXD2 14, RXD2 13 : Supports UART.

https://github.com/Sarah-C/M5Stack_Core2_ScreenBrightness

You might have noticed that setBrightness() doesn't do anything on the Core2, and ScreenBreath() seems dodgy. (See this: https://github.com/m5stack/M5Core2/issues/20 )

So while the complexities of the AXP192 registers are ironed out, I've created a function called core2Brightness(). It's not in a library, you just copy and paste it into your Arduino .ino sketch file.

core2Brightness() physically turns your backlight off at level 0, and increases the dimmable range of the backlight all the way down to "barely visible in absolute darkness".
It uses the absolute minimum discrete brightness levels enabled by the AXP192 library, so every value from 0 through 20 produces an observable change in brightness, unlike other available functions. =)

If you're a rebel, it can also increase the brightness range using the "turbo mode", but the official M5Stack view is not to do it, or for very short periods only else overheating and LED damage can occur. It's obvious damage, it'll void your warranty. You can't send it back if you overdrive it and it pops.

It turned out to be my Ryzen Swift 3 USB drivers!

After updating them the problem resolved.

Support have contacted me, it's an MCX connector!
The one on the LoRa module is female, so the plug you buy needs to be an MCX Male connector.

I've bought these converters for SMA plugs:
https://www.amazon.co.uk/gp/product/B012THC0FO

The MCX connector is exactly the same one as on most of the SDR USB sticks... https://www.amazon.co.uk/TenYua-Digital-Receiver-RTL2832U-R820T2

So if you already have a USB software defined radio hanging around, the rubbish little twig antenna can be cut off the cable, and it reused as a J antenna cable!

https://shop.m5stack.com/products/atomu-esp32-development-kit-with-usb-a

It's the odd one out when everything else I've seen is a USB-C.

Do you think there was a certain use in mind to require this kind of plug?