Hi Jeff, we’ve added a block to exit the program. Since MakeCode is an evented system, it’s not clear when the program is done.
Unfortunately, we do not have the bandwith to test this feature on Android. The Bluetooth support has been tested on MacOS and Windows successfully.
Thank you for your answer.
Then I guess the same goes for Chromebook, or could it possibly work on that platform? I have tried and gotten the Bluetooth-button to appear in MakeCode, but unfortunately the bluetooth-connection keeps dropping so I’m not able to transfer anything.
I’m wondering if anyone has succeeded with Chromebook? The reality today is that few students have PC or Mac, while many are using Chromebooks or iPads, which I guess is due to the considerable price difference.
We pushed a fix for the BT connection over the weekend. Could you try again?
I tried again but did not get it to work. I have no problem getting it to work in the Lego app so the EV3 brick should be setup correctly for bluetooth transfer. I also have the latest 1.10E firmware installed.
I do the following steps in MakeCode for EV3:
- Make a simple test program
- Press the Download button.
- Press the Bluetooth button in the “Download to you EV3” dialog.
A small window opens up that is supposed to show available units to connect to, but instead it writes “no compatible units found” and the “Connect” button is greyed out.
Do you have any idea what could be wrong?
Did you pair your EV3 brick with your computer before trying this in the browser? You should see the device once this is done.
Windows or Mac, what version? The WebSerial APIs are still in a beta quality phase so something might be up too there.
Rob. I found that my Bluetooth dongle needed to have it’s settings changed: in Windows 10, Settings, Devices, Bluetooth, More Bluetooth Settings, Comm Port. Here you need to add your PC to the list of Comm ports.
Hi,
I paired EV3 with my Windows 10 using 4-digit pair code (1234) and connection is successful. Then I ran MakeCode, did simple program and tried to upload it via bluetooth. All the time I receive errors like “download failed” (in attachments). I tried every combination of COM ports, pairing again, restarting brick, even stopping LabView Windows service and nothing helps. Can anyone help me with this issue?
For anyone having the same issue as mine, the oldest fixing procedure works best: turn off and on again After restarting Windows (with stopped EV3 Device Manager service, startup type: manual) everything gone smooth
I’m trying to make upload via Bluetooth but nothing works.
I had EV3 Device Manager service is Running. After switching to Manual and even restarting a computer I still can’t connect.
Does it work for anybody in 2022?
We are currently using MakeCode for Mindstorms in school, which work mostly fine, but still not able to download programs via Bluetooth.
Using Chromebooks, tried both regular and iOS mode on the EV3, tried different connection orders and able to choose the EV3 serial connection in the Chrome browser, but download doesn’t work and we get the same error message as in @maciejmrozinski’s image above.
Might it already have been fixed through this PR and issue by someone called @THEb0nny and approved by @peli, but not published to https://makecode.mindstorms.com yet?:
Check out the beta version. It’s included there. But it worked on my computer, and when I tried it on the computer at school, for some reason it didn’t work there, but I haven’t figured it out yet.
There are a lot of changes in beta. Most likely the beta will never transition to a stable version, because… the developers no longer support the project themselves.
Thanks again for your quick reply and information about the beta version, @THEb0nny!
So, the stable version is fixed forever at some time in the past(could @MakeCode confirm?), while the beta continues to get community updates and now includes a lot of snacks, like new core with function parameters etc., and other stuff like fixed bluetooth support and so on?
Very good to know and thanks for your efforts working on the beta!:
The beta version, although a modern editor, also has new functions. Now you can even program in static python. But there are bugs that are not in the stable version. The biggest problem is that the first port does not work with UART sensors, but it works with analog sensors (for example, a touch sensor) and i2c protocol sensors. This is the biggest bug that I couldn’t solve, maybe I’ll come back to it later, but there’s a bug not only in pxt-ev3, I think there’s a pxt-common-packages bug when working with Linux. Everything else is small stuff. But I’m still trying to add what was missing, i.e. new features.