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?
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.
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.
Burning UIFlow2.X Alpha to the AtomS3 https://www.youtube.com/watch?v=2w85U4XwGj4
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.
@noiseislife said in Looking for MicroPython module documentation:
Is there any comprehensive documentation for the python modules such as m5stack, m5ui and uiflow?
I would like to figure out what functionality exists outside of what is presented in the Blockly UI.
Thanks!
Noise
I'm working on it at present but I'm behind schedule.
You can access the current update of my book here :
https://github.com/Ajb2k3/UIFlowHandbook
@Zontex why have 2 seperate API's for the Coreink and the EPD, Could you not merge most of the API's into one unified e-ink api?
@m5stack what has changed in the firmware as i cant use thonny and UIFlow at the same time in the 1.7 branch.
@doubleness !
You need to have the "Set Screen Show" block as the information is only stored in memory and not drawn to the screen until set screen show or set screen partial show is called.
@urwaldfloh yes it possible and that would explain why it cant update because the terminal is busy
In M5 burner, did you try erasing the firmware before flashing? the erase button is sometimes hidden.!
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.
Try downloading M5Burner from the M5Stack and reinstalling the UIFlow firmware for Core 2 then try reloading arduino.
Have you tried unplugging and plugging or restarting the computer?
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.
Hi all just to let you know my first book in the UIFLow series is now live on amazon.
https://amzn.to/3hHFmTu
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.
@felmue
If you check out the Execute Code block the params are different.
For some reason there is an oddity with security lately that if SSL is set to true in MicroPython the the files are required.
Also the main program functions need to be run in a loop placed after the MQTT Start block.
You can't connect to Blynk 2.0 until there is a big rebuild of the firmware as blynk uses the Virtual twin aka template method to connect whereas the old Blynk just used the username password combo.
@felmue There is no batteries in the Station485
However you may have also found a bug.