I tried to fill this in but easily distr........
Ouuu Squirrel!
Hi, My name is Adam and as the M5Stack community grows everyday I thought I would be interesting to see who is active here and what part of the M5Stack environment is interesting to you the most.
For me is has to be UIFlow as it is the first environment that has allowed me to work with the ESP32 family without major difficulties.
I’m currently working on a UIFlow handbook and some STEM projects.
I have shared a little about me, is anyone else willing to join in?
Welcome, It is now 2024 and in China it is the year of the Dragon.
This year's challenge is to use M5Stack products in the garden / greenhouse / farm / or any other place where you may grow things.
M5Stack product a wide range of products for electronic development and design but I have yet to see much use in the agricultural sector.
Throughout 2024 and 2025 (dependent on the seasons) I would like to see what you can make or how you use M5Stack Products to improve or enhance gardening and growing.
There is no formal registration or signup and the only rule is that wherever possible only M5Stack products must be used.
This doesn't mean that only M5Stack products must be used as things like MQTT / IOT servers are required for collecting data or external weather stations for taking reading are acceptable.
The whole point is to use electronics in the garden and have fun.
I can't wait to see what you come up with.
When you install UIFlow and finish setting up the wifi, the API key will be displayed on the screen along with the mode and the network you have connected the device to.
HY2.0-4P or grove connectors,
VH3.96 for the orange connectors.
@chpaaa1 You will need to rebuild the firmware from scratch as the ESP32's in the Echo and S3 are not the same.
There are enough hardware differences that make them incompatible.
Grove is a standard of cable design created by seedstudio as you have noticed.
It uses a 4 pin JST-PH connector with a 2mm centre between pins.
There are 2 main cables latching and non latching. Latching is used for sensors and actuators that need to be connected to controllers where as non latching is needed to plug into the controller (M5Stack/ SeeedStudio Wio).
You just need to snip the latch off of one end of the cable to plug into controllers or devices tat have the clip covered.
There are also 2 varients of the cable on the market one has the colours Black, Red, White, Yellow, and the other has Black, Red, Yellow, White.
There are however additional Seeedstudio/M5Stack cables that are
Grove 2 Grove,
Grove 2 Stemma,
Grove 2 Dupont Male,
Grove to dupont Female.
You download M5Burner,
Connect the M5Stack,
Select the USB port,
Download the latest firmware version for the M5Stack,
Erase the software on the device with the erase button,
Write the UIFlow version to the device and wait for it to restart,
Close M5Burner,
Open wifi manager and connect to M5 wifi device,
Open web browser and goto the IP address on the screen,
Select your home wifi and type in password (spaces are not allowed in wifi SSID),
If you connect succesfully, the API with be shown on the screen as it tries to connect to the UIFlow web server.
Burning UIFlow2.X Alpha to the AtomS3 https://www.youtube.com/watch?v=2w85U4XwGj4
Where previous ESP32 based products only had one level for writing firmware (I will call this user Space Firmware) the ESP32S3's used in the S3 generation of products use a different access method more akin to the Raspberry Pi Pico based products.
What this means is that there are two USB Drivers needed to be installed in order to fully access and write Firmware to the ESP32S3 series.
The first driver is the JTAG/Series Com driver which allows firmware to be written into the user Space Firmware area and the second is the low lever modem access driver which allows access to the Bootloader level and is also used for making the ESP32S3 devices into HID devices (keyboards, mice, space knobs and joysticks).
Firmwares like the flipper/Maradar makes use of the serial/usb port blocking them from being able to burn new firmwares requiring the need to access the lower level boatload mode ignorer to wipe/burn new firmware.
Through my experiments I have discovered that on windows and linux based machines I have not been able to install the second (modem) driver resulting in the esp32S3 unable to be put into Bootloader mode. Bootloader mode access is shown on the S3 generation models by a green LED lighting up after 5 seconds.
I am still looking into this but I need a new Windows based computer to experiment.
This isn't an issue with the M5Stack products as it works perfectly on MAC OSX based machines and some other Windows/Linux machines used by the more Knowledgeable members. for the moment DO NOT USE the FLIPPER/MARAUDER based firmwares otherwise you will need to replace the StampS3's to continue use.
The Precompiled binary is in the M5Burner firmware burner program along with other precompiled firmwares.
@williamsmaith Thank you, Your question could have been interpreted in many ways but, now we know your base level of understanding we can give details.
One of my projects uses a Mio robot I got cheep from a toy store. I removed the circuit board and found the M5Stack core fits it perfectly (you can find the project on hackster).
The biggest none m5stack range you can try is technic lego, the options it offers is amazing. I use the pressure sensor to expand the ability of technic pneumatics.
I have an old lego computer interface that I can control from a core.
We had one member controlling DJI drones and RC cars.
@williamsmaith Do you know how to code?
do you understand electronics?
Have you tried any of the M5Stack accessories?
Have you looked in the documents and tried to replicate and of the M5Stack devices?
@PavelNDC Public (red) means that's it's not connected. normally this is an issue with the M5Stack server.
@Wizzy38952 Have you charged it?
Erase bruce and only burn UIFLOW2
@VVong_san_ Are you erasing the old firmware first before burning?
@wjcarpenter Standby voltage. the stick doesn't truly power off and there is always a small voltage present in the stick which is why the battery always runs out.
The voltage increasing with a cable plugged in is normal and thank you for pointing out this function.
@Slarck You should always Erase first because of this. never just burn only.
Thats the reason for the big red erase button being there!