When you meet problems using M5Stack, we help you solve it.
@androidspa said in LEGO+ Issue:
I think I may have found a solution for controlling the LEGO+ module.
It turns out that when you install the arduino library for the M5Stack, there is an example to interface the LEGO module. It is located in File>Examples>M5Stack>Modules>LEGO_PLUS>LEGO_test
From that example code the I2C commands can be figured out. I hope this information is useful to anybody facing the same issue as me
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.
@watson 在 Arducam (arduino) Can't find OV2640 module! 中说：
Here's the pinmap about camera supplied by m5stack.
That doesn't tie up because the arducams arduino_pin.h has D2 as I/O12
and slave select as I/O17
Not with the Adafruit-GFX library that is the display driver in the M5Stack library. You can rotate the display, but only the whole display, not show text in multiple orientations at the same time.
It would be a cool modification though...