Bert

Maybe not 100% on this item, but as a simple user I would expect **True** as the result of ```motor.stalled()``` after running ```motor.run_until_stalled(500)```. Currently running this on ```('primehub', '3.3.0b8', 'v1.20.0-23-g6c633a8dd...

It does not. Not with V3.2.3 and not with v3.3.0b8. Should I make another discussion to not pollute this one further?

> Was this without Pybricks Code or other Bluetooth devices connected? Correct, just the cityhub without PC connection, no devices connected, no BT connection. > Does this also occur on...

Just over a hundred attempts did **not** show this on a Technic Hub on the same CI-build firmware.

Just to be sure all at github hash `f3f6ccbe` retested Cityhub hit at ~ 50 attempts (was getting affraid it might be more than 100) Tested the rest with just...

The Power Function connector I might call it a plate, but it is a bit thicker, so forget it. But an important thing about this connector is that it can...

> > **was** at the time > > The RCX/brick connector system is also capable of this. Is this simply in contrast to the newer motors which cannot stack? yes....

Not sure if **this** is the correct place to report, but commits here might have to do with power-on / power-off. Test: install on **CityHub**: ```Pybricks MicroPython ci-build-4577-v4.0.0b3-66-gfcfdf4e0 on 2026-01-02;...

Ran this slightly adapted program (print after disconnect, so I know) on the cityhub. Firmware ```Pybricks MicroPython ci-build-4577-v4.0.0b3-66-gfcfdf4e0 on 2026-01-02; Powered Up City Hub with STM32F030RC``` ```python from pybricks.pupdevices import...

Keep in mind that a powerbank to feed the RaspberryPi and a battery holder with rechargables for the BuildHat have their cost too.