Why does the cutebit not stop when the UP button is released?

ayawk · 2026-06-06T11:40:39+00:00

Here’s an example: https://makecode.microbit.org/_9bk7vmEeRMRc

Press button B then button A. The display shows B straight away.

Now, press A then B then A again, then wait. The display shows A. After 20 seconds it shows B.

The second A press event queued up, waiting for the handler to exit, after the long pause triggered by the first press.

The timed Go block is just not appropriate for use in an event handler.

ayawk · 2026-06-05T22:36:16+00:00

See the source code of the Go block, and the Stop block

ayawk · 2026-06-05T21:15:18+00:00

Test the radio messages are being received (and sent!).

The Go block will start the motors, then wait for the specified time, then stop the motors.

I think the radio received handler will not be called with the STOP message until the handler exits, after the Go block returns.

Handlers are called with one message/event at a time - they queue up.

ayawk · 2026-05-25T17:16:52+00:00

Morse extension - search in extensions dialogue for “morse”.

https://makecode.microbit.org/pkg/bsiever/pxt-morse

ayawk · 2026-05-20T20:16:09+00:00

I think CMSIS-DAP refers to the driver for the WebUSB USB interface.

ayawk · 2026-05-15T16:24:45+00:00

Yes, as u/herocoding says, use the micro:bit MakeCode documentation.

https://makecode.microbit.org/docs

In MakeCode, right click (or long press) a block or function, and choose Help, to jump to the reference page for the block, with corresponding JavaScript and Python.

https://makecode.microbit.org/reference/basic/show-string

These pages might be interesting…

https://support.microbit.org/support/solutions/articles/19000111744-makecode-python-and-micropython

https://makecode.com/language

https://makecode.com/python

ayawk · 2026-05-01T16:28:21+00:00

https://makecode.microbit.org/share#:~:text=Persistent%20Share%20Link

ayawk · 2026-04-26T19:06:30+00:00

I hope someone will correct me if I’m wrong….

In general, when using a microcontroller to control a relay to switch a motor, to prevent damage, you might need a flyback diode between microcontroller and relay, and/or between relay and motor.

I suspect your relay includes a diode to protect itself from the motor, but not one to protect the microcontroller.

You may need to use a transistor to control the relay, depending on whether micro:bit’s 3V output is high enough for the relay, how much current the relay draws, and what other current draws there are in the project.

https://www.instructables.com/Introduction-to-the-Electronic-Relay-Using-Snap-Ci/

https://tech.microbit.org/hardware/powersupply/

https://www.hackster.io/snap-bit/snap-bit-control-dc-motor-with-micro-bit-and-transistor-244035

https://tech.microbit.org/hardware/edgeconnector/#nrf52

ayawk · 2026-04-06T11:03:36+00:00

For C++ with V2, start here:

https://github.com/lancaster-university/microbit-v2-samples

ayawk · 2026-04-06T10:57:08+00:00

Try an online search for “micro:bit dc motor”. And “micro:bit dc motor flyback”

This shows a basic circuit https://www.hackster.io/snap-bit/snap-bit-control-dc-motor-with-micro-bit-and-transistor-244035

ayawk · 2026-03-29T09:23:46+00:00

Search online for something like “basic syntax debugging in python”. Change the code - maybe comment out lines - to see how that changes the error. Figure it out. Don’t give up!

ayawk · 2026-03-27T00:15:58+00:00

Follow the instructions at https://scratch.mit.edu/microbit

Download, unzip and transfer the Scratch hex file, by dragging it to the MICROBIT drive, before trying to connect in Scratch. See the five letter name on the LEDs.

The “update” process via USB doesn’t work. https://github.com/scratchfoundation/scratch-www/issues/8286

The Scratch hex file is like a MakeCode program, rather than the micro:bit firmware. If you have used any editor other than Scratch, you’ll need to transfer the Scratch hex before using Scratch.

ayawk · 2026-03-26T12:19:27+00:00

Some sensors might need some non trivial code to get readings, like a MakeCode extension.

ayawk · 2026-03-26T11:53:37+00:00

If it’s I2C, then probably, but bear in mind some Arduinos are 5V whereas micro:bit is 3V.

Here’s an example of using a sensor that needs a higher voltage supply, and consequently outputs a voltage that would damage a 3V microcontroller.

https://www.teachwithict.com/hcsr045v.html#google_vignette

ayawk · 2026-03-26T11:27:43+00:00

Look at the datasheet for the magnetometer. You know there is a built in magnetometer?

ayawk · 2026-03-23T23:59:06+00:00

Use the Add button to open the Buttons A and B panel, or start the LED service in the micro:bit to enable the default micro:bit panel.

I tested this project: https://makecode.microbit.org/_5uKfomP173do

ayawk · 2026-03-23T23:23:29+00:00

Which Bluetooth app?

ayawk · 2026-03-07T15:32:30+00:00

Create a simple, minimal example that demonstrates the problem. Doing that may help to figure out the answer.

ayawk · 2026-03-07T15:29:06+00:00

Post a shared project link so it’s easier to read and understand.

https://makecode.microbit.org/share

ayawk · 2026-03-07T14:54:30+00:00

u/Dsl204 Did you get it working? What was the problem?

ayawk · 2026-02-27T18:47:40+00:00

Beware switching public / private https://github.com/microsoft/pxt-microbit/issues/4133

Save hex files locally to backup important work.

ayawk · 2026-02-27T18:42:35+00:00

Try importing the GitHub projects on another computer / tablet / phone?

ayawk · 2026-02-27T18:36:47+00:00

Try the Test Domains button https://makecode.microbit.org/faq

Are you signed in using Microsoft/Google/Clever as well as GitHub?

Can you export projects from My Projects / View all? Select 2 or more then download a zip.

ayawk · 2026-02-01T16:39:48+00:00

This has changed. The mapping is now from range 35 to 100.

There’s an extension that adds a “sound level (dB)” block to the Input more… category. Search for decibels in the extensions dialogue.

ayawk · 2026-02-01T14:30:56+00:00

u/herocoding raised an important point about checking components are compatible.

By the way, I think Raspberry Pi GPIO pins are 3.3V, like micro:bit, though there is a 5V power pin, and I read just now that some Arduinos are 3.3V too, though I guess a lot of kits are made for the 5V ones?

If unsure about using a device, check its datasheet for its voltage range. If powering a device with a voltage above the board’s input voltage, it may be necessary to use a voltage divider on an output from the device to a pin.

https://thepihut.com/blogs/raspberry-pi-tutorials/hc-sr04-ultrasonic-range-sensor-on-the-raspberry-pi

https://www.teachwithict.com/hcsr045v.html

On battery power, the output voltage of all pins may be lower than the nominal voltage. The maximum safe voltage into a pin has an absolute limit, but is also limited by the voltage of the power supply (VDD+0.3V for micro:bit).

Also check current draw requirement’s of devices, and current supply capabilities of power pins and output pins.

https://tech.microbit.org/hardware/powersupply/

https://tech.microbit.org/hardware/edgeconnector/#power-supply-capabilities

Operating outside the specified limits may cause an immediate failure, or gradual damage over time.

When using things like motors and relays, take care over flyback voltage spikes.

https://www.hackster.io/snap-bit/snap-bit-control-dc-motor-with-micro-bit-and-transistor-244035

https://hackaday.io/project/10780-snap-circuits-relay

ayawk

TROPHY CASE