I get a strange pattern on the display on the hardware when using setbrightness(0)

setbrightness does not work

The simulator and the real hardware seem to work differently.


There is a bug in the currently deployed display driver, in that if the number '0' is used for brightness, the display driver code returns prematurely. This prevents it from updating the display, you might see only some of the LEDs turned on depending on which of the 3 ROW multiplexes was active in the driver at the time the set_brightness() was called


Use setbrightness(1) instead


These two .hex files demonstrate the problem, and the workaround. They are written in blocks ( so just drag and drop them onto your MICROBIT drive, or drag and drop them onto the editor to see the source code program.


18/04/2017 DW