Ok turning the cable 180º around it does work!
In my case, the brand label up.
So, now I'm curious what happened to the whole "it doesn't matter which way you plug your cable in" thing from USB-C here.
Thank you very much for your answers help me understand this hardware.
Yes, that's my question. Use M5stack regulator to power the M5Stack and not from charger .
In this case and, it is a last question about this, there will be no problems with the USB input if it is powered by an external battery. In some other case I have had problems connecting the USB, because both 5v sometimes are not exactly and that small difference produced power noises by connecting the USB, and sometimes reestorting the unit.
You should charge your battery to full. Do you tried to calibrate your sensor?
Press and hold the right C key to start the machine, and release the key after hearing the "drip" sound. The sensor will enter the calibration setting, and keep the host horizontal and still. After 3 seconds, the sensor calibration is completed, and it will automatically enter the balance mode after the calibration is completed.If you found that Bala cannot keep balance during use, it can be solved by trying to calibrate the sensor.
@kurthofman said in UIFlow : Units are not available:
I'm using M5 Fire with firmare 1.0.3 in Chrome.
The update sorted out a minor bug with the Unit box but the ones with the blue symbol over them are not working yet.
iIRC I seam to remember something on one of the Esp32 forums with a similar issue. I think it was something to do with bus clock speed issue. I think it was down to the clock being set to high for the psram.
@jpilarski said in issue with remote in 1.0.3:
Nice work on the adc, iic, and on adding more unit blocks. Unfortunately it looks like there are issues with the remote blocks. They look to be overlapping on screen and make it difficult to properly select remote blocks.
What web browser are you using to load UIFlow as it worked fine for me.
@felix42eu said in Hardware Variantion and Firmware Compatibility:
OK, I did not know that arduino was not fully supported. thanks.
is m5go and m5fire a different product? I do not think so.
where are the sources of the versions located if they are open source? or do you mean the binaries are free (I found them in the M5burner replease)
The espressif idf is a topic which I have too look deeper into.
All sources, documents and specs are found on github.
Some of the docs are a little out of date though.
some of the "grove connection" units are found on the seeedstudio grove website.
In your reply above you mentioned firmware 1.0.1 for the stick but in the M5-burner download it only has version 1.0 of the uiflow firmware for the M5stick. Can you please verfiy which firmware is the most recent. Also will the MPU9250 work with the M5stick in uiflow. thanks
Thanks this is helpful to see. Much appreciated. I still think it would be great at some point for you to add a section to the uiflow documentation that covers the blocks located under the advanced tab.
thanks it works great used this library
and this basic code to test
from machine import I2C, Pin
i2c = I2C(0, sda=21, scl=22)
sensor = tcs34725.TCS34725(i2c)
@jpilarski said in makey:
I am having some difficulty understanding the makey unit. I can make it beep if I put one end of a wire in the LED pin and touch other end of the wire to various pins. I get some sounds playing through the m5stack speaker and some on the makey's buzzer. Why are there multiple pins with the same number. Should I be able to just touch the pins with my hand and register a touch. Also can you explain how to use this device in UIFLOW. Again I can get a few beeps from the makey using UIFLOW but I'm not sure I understand the pins to use or how to work with the makey blocks. It did make some great beeps and I am excited to use. Last question is does the firmware on the mega328 ever need to be updated. thanks
This is the biggest issue that takes getting used to when moving from Atmega to esp32. The Atmega's pins are "Set function" in arduino however the esp32 using a mux controller to control the pins resaulting in a matrix of multi function I/O pins that need to have functions set in code.
I would like to request that color is defined in the blocks in a way that allows the user to select one of 2 color block options
you can add color by using a general color swatch selector like you have currently on most blocks
you can add an RGB block that allows color to be treated as variables.
I feel like these two color options should be broken out as two color blocks that can be added onto the blocks as needed. Currently you have color broken out as three variables in some of the ui blocks but in none of the graphics blocks and this is limiting. What I am suggesting is all tools requiring color require the user to add on a color block and the color block can be one of these two types (color swatch, or RGB variables). I think this can help make the interface cleaner since you don't have to have all these redundant blocks but rather a single block with the option to select how color is to be defined. This gives the user way more programming options since they can opt to use a swatch when needed or to use RGB number values or variables if needed.
Also I think you need a list block to define the length of an array. It would also be great to have a block for list pop.