I like this question and I think another question should be on the features of the software that are most powerful.

sensors

For the sensors, after M5 with display, we are mainly using the M5Atom and then connecting the various plugin sensors (like QR scanner, Speaker, GPS, or others) - and the GROVE cable to stand along like sensors for LUX, Motion, Buttons (especially for disabled users). But either GROVE or directly into the M5Atom using the pins to control things like buzzers, and motors. For Motors, we need the 5v power.

software features

As for software, I've built a really cool framework that incorporates the BLE, and the WIFI (with MQTT and web POST/GET) messaging. But for us, the ability to update already fielded systems requires the OTA capability. So any partition scheme without OTA isn't used.

Object Oriented Design

I still code entirely in C and now C++. I feared C++ was too heavyweight for that small M5Atom - but it turns out it works nicely - and let me wrap those various sensors in an Object Oriented (plug compatible) feature that is adaptable at runtime via BLE/MQTT messages - basically tell it to use the GPS or QR OO Class, and also pins 28 and 32, etc. This is without modifying the installed code (or use OTA to add new sensor options). (I also use Xcode as the editor)

backend web and message processing

Note for the MQTT and other to work, there needs to be cloud processing. I have the ability to send any messages to all my devices. So the web needs the MQTT host, and if you want HTTP GET messages to work, there should be a node.js based controller (I use node-red.org). - Also for OTA, there needs to be an "http" host (not https).

If anyone is interested in more of our projects, which we are open sourcing, let me know. We are using 3d printed housing as well.
Check out at least:
https://github.com/konacurrents
https://github.com/konacurrents/SemanticMarkerAPI
and more..

Cheers,
scott

@felmue said in PbHub 1.1 on STAMPLC - Couldn't find Pbhub on PortA:

Hello @bensonwhlee

try adding a delay(500) before calling pbhub.begin(). My above linked code fails to initialize PbHub without a delay.

Thanks
Felix

“Thanks @felmue, that’s a helpful tip about the delay. I’ve seen similar I2C issues where peripherals don’t initialize properly without a short wait after boot. Good to know it applies to the PbHub too!”

@hacxx Dear hacxx, Thanks for your help.

@Salam-Rashid said in No enciende la pantalla.:

A quien pueda interesar: Problema solucionado. He desmontado el aparato le he desconectado la batería "es muy fácil, tiene un conector blanco de dos pines, con un cablecito Rojo y uno Blanco que se puede conectar y desconectar", con la batería quitada, lo he conectado al ordenador a trabes de su cable USB Tipo C y se ha encendido la pantalla. He desconectado el cable USB y lógicamente el modulo se ha apagado porque no tenia la batería puesta. He vuelto a conectar la batería he apretado el botón de encendido y ha vuelto a funcionar. así que problema resuelto. No se ni como ni porque surgió el problema, pero ya esta resuelto. La solución la he encontrado en este mismo foro en el idioma Japones, por el compañero @mongonta555. Gracias.

helpful！

Thanks for responding.

I tried a different machine on a different network: same error.

@kuriko

Thank you so much for your help Kurikio. And for your crazy fast response. This is exactly what I needed to get myself back on the right path. I through together a quick test this morning and everything is now running smoothly and I'm able to change between different lighting setting with out the program crashing or getting stuck in a endless loop.

Here's what I ended up putting together. Three buttons on the display that could change between three preset colors and a effect pattern, the A and B buttons mirrored the first 2 button and the C button turned off the lights.

Thank again so much for your help. Here are some photo of my end result:

Screen 1.1.jpg

Screen 2.1.jpg

Screen 3.1.png

@kuriko
早速のご回答ありがとうございます。テンプレートダウンロードさせて頂きました。
こちらのテンプレートと設定値を比較しながら再度ビルドとアップロードを試みます。

100-sudoku.png

Hello @wjcarpenter

the battery charging IC is TP4057 and battery voltage is measured via R40 / R41 into GPI38. See second page of the schematics here.

Thanks
Felix

@PavelNDC Public (red) means that's it's not connected. normally this is an issue with the M5Stack server.

@Nooblearns what error?

@Wizzy38952 Have you charged it?
Erase bruce and only burn UIFLOW2

Welcome aboard! Great starting point with Python and the M5Stick/Flipper - hands-on tools make learning fun. For cybersecurity, focus on networking basics (try CompTIA Network+), then dive into Linux, bash, and tools like Wireshark or Nmap. Use your old computer for practice: install Kali Linux and start with safe, local labs like TryHackMe or Hack The Box. Keep learning, stay curious, and always practice ethically. You’re on the right path - just take it one step at a time!

@VVong_san_ Are you erasing the old firmware first before burning?

Hello @teastain

I am afraid I cannot help, sorry. I exclusively use Visual Studio Code with PlatformIO / pioarduino (which so far doesn't have this issue).

Note: Visual Studio Code / PlatformIO doesn't use M5Stack boards and setting up new Cores (M5Stack and others) can sometimes be quite difficult as well.

Thanks
Felix

Hi! As of now, there isn’t an official Eagle library specifically for the M5StampS3. You can try using a generic ESP32-S3 footprint or create a custom library based on the unit’s datasheet. Hopefully, M5Stack or the community will release official libraries soon.

If you’re unable to run UIFlow or M5Burner on Windows 10, try running the app as administrator and ensure all necessary USB drivers (like CP210x or CH340) are installed. Disable antivirus temporarily, update your .NET framework, and check if the device is recognized in Device Manager. Reinstall the latest version from the official M5Stack site. Compatibility mode and checking firewall settings can also help resolve startup or connection issues.