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?
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.
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
Hi all just to let you know my first book in the UIFLow series is now live on amazon.
https://amzn.to/3hHFmTu
The Precompiled binary is in the M5Burner firmware burner program along with other precompiled firmwares.
The non AWS core will work fine with AWS IOT services (I wrote a guide on it) the problem is that the AWS base has some security certificates programmed into it which are causing issues as they are out of date.
A quick guide to using the M5Stack ENVIII unit connected to the AtomS3 using UIFlow 2.0 Alpha 7
https://youtu.be/1G7tyrmuV0M
Unfortunately not. Arduino work on a lower level than MicroPython and so runs directly on the hardware. Micropython is an interpreted language and so need to install a boot loader/ interpreter to run.
It can be inconvenient to have to install the MP boot loader when you want to switch back but its now a simple process.
@alejandro_baup I have been asking for a few weeks but there looks to be an issue with sdxards at present
Burning UIFlow2X to the #M5Stack Core S3
https://www.youtube.com/watch?v=2K4hHGtskAU&lc=Ugxxk-YyuyuZmCRj5u94AaABAg
@lovyan03 are you still here?
@wsanders M5Stack hit the space limit for the MP firmware and had to remove several fonts. V2 firmware should fix this issue.
@windegg The desktop IDE hasn't been updated in a long time and (from what I was told) will not be updated until UIFlow2 reaches a stable (none Alpha test) version.
I have spent the last five months working on the English version of the handbook which is predominantly aimed at UIFlow however due to the ever changing world of electronics, nothing ever stays still for long which makes pinning down a completion date near on impossible.
I have decided to continue to release the Work in Progress version on the forums for people to give feed back and submissions with a print published version available near December.
I wont release updated versions of the print copy when new hardware is designed but instead will be releasing update volumes to accompany the print copy.
Electronic versions are planned for the many ereaders but will wait until the manuscript hits a stable release.
Each print copy will have a contributors section where I add interesting work done by the members of the forum if they give permission.
The decision to release it like this is down to the fact that the current manuscript is already at 100 A4 pages long and I am yet to cover all the basics!
All support will be gratefully accepted and to show the progress of the manuscript so far I have attached the current version on github.
https://github.com/Ajb2k3/UIFlowHandbook/blob/master/quickblockref290919.pdf
I'm slowly creating a book for UIFlow here https://github.com/Ajb2k3/UIFlowHandbook
so any feedback is appreciated.
BTW if you have Facebook you can see updates on the M5Stack facebook group.
The Atoms are not directly compatible as the bases and modules are 54X54mm and use the 30 pin MBus where as the atom is only 20x20mm and uses the Atom expansion port.
That said the modules communicate using I2C and can be driven but you would need to alter the I2C address of each module to use have separate address and separate power supplies as 24 servos will cause brownouts (I get brownouts with only 6 servos if I don't use a separate power supply. If you change the I2c address' they can be stacked together and use only one external power supply.
In UIFLow the Socket menu has only blocks for UDP. How do I can TCP sockets?
Are they supported or do I have to call them with a custom block?