Troubleshooting EV3 and MakeCode

I am a big fan of Lego Mindstorms and MakeCode. However, the firmware is a bit buggie. The main issues that I have had is that after a while, the EV3 drive does not map and no amount of restarts seem to fix it. The other is that there must be an issue with adding programs with the same filenames or something. Certainly, you can’t delete from the brick. This means that when you tweak a setting and upload your program again, the old version runs and not the new. Given the rate of prototyping cycles involved in Robotics, I hope they solve this one soon. Some guidance to solve these issues is below.


RoboCup Soccer with EV3 and MakeCode Mindstorms

RoboCup Soccer

Next year, Lego Mindstorms coding will be no more; to be replaced by a scratch-like coding environment. My students are about to finish the First Lego League season and will be looking for the next challenge to work on. Now is a good time to transition them to a block-based coding environment. As the new Mindstorms is not available, I am going with MakeCode.

I have already made RoboCup Rescue Line resources available as PDF or OneNote. I have just finished whipping something up for RoboCup Soccer. It comes with the caveat that I have not beta-tested it with students and my logic may be all over the place. Also, the MakeCode API does not have blocks for the HiTechnic sensors, so LEGO Infared and Gyro sensors are used instead. This has resulted in significantly different solution algorithms. The resource is available as PDF or OneNote.

RoboCup Rescue Line with MakeCode Mindstorms and LEGO EV3

MakeCode Mindstorms and LEGO EV3

The current version of Mindstorms is going to be replaced with a Scratch-based version, mid 2020, so I thought I would get the jump on preparations for RoboCup Junior by using MakeCode for Mindstorms.

I have only developed a curriculum for RoboCup Rescue Line and the rest will follow when my clone has the time to spare. I have only desk-checked my algorithms, so please send me corrections and modifications. I figure that reasonable logic errors can only spur deeper learning as students prove their resilience through multiple prototyping cycles.

My thanks go to the following sources, as I have only edited their insights together and re-interpreted them for Makecode:


The OneNote or PDF can be found here: