I made a quick reader nothing special and this is on a Basic Core unit
quick video showing it working
The Tags I use are these ones
make sure the port is correct otherwise the bytes out of range error pops up
from m5stack import *
from m5ui import *
from uiflow import *
uhf_rfid_0 = unit.get(unit.UHF_RFID, unit.PORTA)
epc_bool = 0
label0 = M5TextBox(128, 59, "Tag #", lcd.FONT_Default, 0xFFFFFF, rotate=0)
label1 = M5TextBox(22, 106, "waiting ... ", lcd.FONT_Default, 0xFFFFFF, rotate=0)
# while not temp:
temp = uhf_rfid_0.single_polling()
it looks like using the arc block only one color (either outline or filling) can be defined at the time. The color which is not defined seems to be random, causing the unwanted outline.
So instead of using the arc block directly you could use the Advanced - Execute code block which then allows to define both colors together like this:
lcd.arc(120, 160, 100, 50, 0, 90, color=0xff0000, fillcolor=0xff0000)
@janulr I have found the same issue - unable to open M5F files after saving and closing. But looking at the clues above I found a workaround.
I have a custom block for DS18B20 in the original file. If I add the custom block back in to UIFlow again and then open the file IT WORKS. Otherwise I get a blank Blockly screen and most of the pyton code is missing, Display screen is also blank. Hope this helps.
Developers need to find a way of warning when the M5F is opened that a "Custom Block is Missing". That way we can load the block and continue.
Have you burned the correct Core2 UiFlow firmware ?
sometimes this happens if you use Core or Core fire firmware instead of Core2 firmware.
Also, are you including any graphical elements? If you run a program without GUI elements set then the screen will go blank!
Thank you for answering!
The firmware of my M5StickC Plus is v1.9.1, which seems to be outdated.
When I wrote v1.10.2 with the presented M5 burner, it worked properly.
It was rudimentary.
Thank you very much.