I'd like to update my question on M5GO Base. From a more careful reading of the schematic diagram the Vout on the IP5306 of the M5GO Base is not connected to the +5V. In this case the IP5306 of the base has no conflict with the one inside the M5Stack Core.
Here is an example (Korean but you can using code, Simple Chat Server)
And I will publish this document in English as soon as possible. :D
I had the same problem. But I did decide to rename all my APs and every device connected. 30 minutes later, still can't get a device code, and it seems like it got stuck booting into the "Press next for instructions" screen, so I can't change the wifi if I wanted to :(
@heybin I’m sorry, I don’t understand why when you have it working for the stick and the stack. Looks like it’s time for M5Stack to build a UIFLOW port of the firmware for the camera. If you build it from the sicks firmware then half the work is done for you!
@mrtarantl said in Pinout of TFT display:
Thanks :D i am aware of that... I was searching for a pinout of this
The contacts are not damaged, it should be easy to solder it again on the board and it will probably work again...
Of course, if you have minimal soldering skills...
@ajb2k3 yes I did use the cooling module as well.
My thought was that there probably is some electrical interference when using the stepper and the servo module together. My solution in that case will be that i disconnect the mbus from the voltage regulator +wire completely to only power the steppers with the external power supply and do the rest with usb power to the m5Stack, so i am safe :D
Have the ezTimeLog example loaded up. It is printing lines at the bottom of the canvas, and shifting previously printed lines up, indeed just like a terminal screen watching serial output. I think I misunderstood the scrolling functionality as the ability to use buttons to go back through the history at the top that had already scrolled off the screen. I see in issue #24 you say "canvas.print creates a buffer in memory that stores every print until it has scrolled off the screen", so that's not the way it works - sorry for my confusion.
Indeed, creating menu items that don't do anything would be a possible solution. I tried that early on, but found that once the menu was drawn (or run), it merely sits and waits for buttons. I have not tried creating a function that does an .addItem, then runs the menu again, and run that function with an .addEvent. I'll give that a try as soon as possible. Is there a limit to the number of menu items, other than memory constraints? If I'm successful getting the "menu" to redraw, I'll let you know, and I guess I'll see what the limits might be!
Thanks so much, @rop, your work is very appreciated!!!
@lukasmaximus said in Button Unit Issue testing help please.:
I have tested the blocks associated with the single button unit and they definitely need some work.
Button press c shaped block only allows for a single press or release and the jigsaw shaped block
when combined with an if condition it throws an error that btn0_wasReleased or wasPressed is not defined.
These issues will be resolved in the next update and hopefully some extra functionality added.
Yeh, I was getting the btn0 is not defined error.