@felmue That actually worked. Not an ideal situation as I cannot use the newer units, but for now the Lego motors turn again which is awesome!
Thanks a lot! I downgraded the UI, but it never occured to me that I should downgrade the firmware too.

Re: LegoBoard

Having updated everything (v1.7.2 for the firmware, and using the beta as well as the non-beta v1.4.5 of the uiFlow), I cannot seem to make the Lego+ (AKA DC Motor in the newer UI) work. All I get is "legoBoard not support in uiflow" on the LCD of the M5 Core unit.

I remember it did work a long time ago. What changed, and more importantly: how to fix this?

Hi,

the ToF sample program does not work when running via ampy. But it works from the UIFlow.

How to reproduce:

• Connect a ToF sensor to the M5 stack (Firmware UIFlow 1.3.2)
• Get the sample ToF program
• Run via UI. Should work fine.
• Copy&paste the Python code into a file named tof.py
• Disconnect M5Stack
• Run ampy reset to get the M5Stack into non-UIFlow (ampy v1.0.7 used)
• Run ampy run tof.py

You'll see that the distance is and stays 0

After testing other units, it seems ToF is the only one broken. All the other ones work just fine when copy&pasting the Python code and running via ampy.

Looks like a bug report is in order.

Hi,

I like the UIFlow firmware as it's a neat way to test small (less than a screen full of code) samples. I don't care about Blocky in particular.
In short: I like to use MicroPython primarily, but UIFlow secondarily.

However I cannot make a simple example work though:

from m5stack import *
from m5ui import *
from uiflow import *
import unit

setScreenColor(0x222222)
tof0 = unit.get(unit.TOF, unit.PORTA)

for count in range(100):
  lcd.print('        ', 0, 0, 0xffffff)
  lcd.print((tof0.distance), 0, 0, 0xffffff)
  wait(1)

This is the output from a very simply Blocky block. Works fine in the UIFlow UI.
But sending the same code via ampy does not work: the tof0.distance is always 0. But the screen clearing works just fine.

Is there a way to send Python code to an M5Stack with UIFlow firmware
What's the difference between running UIFlow code and the equivalent Python code?

BTW other examples with other external units work fine. So maybe this problem is limited to the ToF unit...

Found this thread from 3 months ago. Re: python back to blocks not working

The problem (for me) is that I see why Blocky is nice: no syntax errors, and it's usable to teach simple programming. Also I like the general UIFlow interface. Very approachable.

Looking at the Python code is neat. However if you edit it and you click back to the Blocky code, all your Python changes are gone. Saving your code saves the Blocky code only.
You can send the Python code to the M5Stack unit though and it's correctly executed.

Basically the Python code is unsavable and very easy to wipe out by looking at the Blocky page.

This is not expected behavior and it leads to a confused user.

Possible fixes in order I'd prefer:

• Adjust Blocky code according to Python code. Haha! Joking. For simple stuff this might be ok, but have fun converting classes and lambdas into Blocky...
• Remove the Blocky button or disable it once the Python code is modified. Saving then saves the Python code (not the Blocky one)
• Warn me about "Your changes in Python will be wiped out. Do you want to proceed?" when clicking on the Block button.

Doable?