Wiki / Other software
BuWizz app
The maker's own app for the BuWizz brick, and the reference implementation of that brick's protocol: whatever it does is by definition correct for the hardware.
What it reaches
| Capability | State | Note |
|---|---|---|
| Drive a BuWizz brick over Bluetooth | works, untested here | the vendor's own client |
| Reach every power level the brick offers | works, untested here | the level is a separate frame from the motor values, and it has to be sent first |
| Drive Powered Up motors on a 3.0 Pro | works, untested here | that generation carries Powered Up ports as well as Power Functions ones |
| Anything that is not a BuWizz | out of reach | it is the vendor's client for the vendor's brick |
| Anything optical | out of reach | Bluetooth only |
The vendor's client is the control
When a brick does something odd, this app is what tells you where the fault is: if it fails here too, the brick or the wiring is at fault and not the client.
The power level is its own frame
On a BuWizz 2 it goes out before the motor values rather than alongside them — measured here: with the current-limit frame queued ahead of it, the brick ignored the level and stayed on whatever it had. A client that sends them in the wrong order reports one level and runs at another.
Links
- BuWizz — the brick, its generations and its status bytes
- BrickController2 — a third-party client whose source documents this protocol
- Third-party hubs over Bluetooth