@teastain I try to be helpful!

I managed to solve this issue with this custom block

@isamalatby Do you have a new device or second hand device?

@ajb2k3
I learned that the browser does connect to the Core2 by WiFi and the IDE connects using USB.

Thanks

@german-figueroa2000 What you did was to run the code on the core2 in test mode. You need to download the code to the core 2 from which it will be run on boot.

There are some differences between running in test mode and running in app mode and the biggest is that in app mode you may need to add blocks to initialise wifi communications where as in test mode, the wifi is auto magically run for us.

Thanks Teastain
I have the expansion module for CORE 2
I am looking for advice on the mode of communication to use to transfer from CORE2 to the ATOM Display, and how to transmit around 20 digital variables?

I agree quite frustrating, when you follow the sample and get no results.

Any pointers in the right direction would be fantastic.

The problem is not just “hot features” it’s hardware support and MP version upgrades. M5Stack are aware of issues with the current firmware as I keep annoying them about duplicates and bad libs

@felmue Thank you very much!
Exactly what I need. Indeed, I was using the v2.5 stable version of the M5Burner, which doesn't have this option. I'm glad they added this option in the "next" version.

bump

Hi guys

@democrazia : thank you, adding from easyIO import * solved the issue. Thank you!

@ajb2k3 : you are correct, the 485 stock version doesn't have batteries. However I don't think M5Stack engineers are planning to separate the two versions in UIFlow as there is only one M5Station to select from in UIFlow. So yes, it is a bug - instead of the error we should get 0.

Thanks
Felix

Try (str(str(setcourse)))
Putting the str in a second time sometimes works as it would appear that the original str sometimes get ignored.
Why, I don’t know but I’ve used this trick myself a few times now.