This is mainly used to debug the motor model, and to quickly select the
feedback parameters. This is useful when adding or configuring new motor
types.
Reading the estimated speed can also be useful in advanced applications
where the user builds their own PID controller.
We may choose to hide this method from the documentation before the
release.
This makes it consistent with other hubs.
See: https://github.com/pybricks/support/issues/848
The IMU section was not included in V3.1 so it is not a breaking change,
but we add a versionchanged comment just in case.
Table of contents can't be hidden based on tags, so we just remove them.
Instead, add a note in the body of the standalone version.
Fixes: https://github.com/pybricks/support/issues/839
This updates how and when settings take effect. In this release, you can
change them even while the motor is moving. Some settings do not
take effect right away, as now indicated in the relevant methods.
See also https://github.com/pybricks/pybricks-api/issues/105
These used to be implemented as part of the Control object,
but now they are available directly on the motor.
This way they:
- Also give useful values when control is passive, via dc().
- Can be supported on Move Hub
- Give useful values for drive bases (see next commits).
Fixes https://github.com/pybricks/pybricks-api/issues/115
Also modify the categories given implicitly in the Python
file and make them explicit in the docs.
Most users are going to want to use `randint` or `random`, so
that basic category comes first.
This moves the per-hub storage size to the respective page.
This also clarifies that data is cleared when updating Powered Up hubs.
Also flip docstring signatures around to work around https://github.com/pybricks/pybricks-api/issues/117
Move it do a dedicated example instead of hardcoding it in the module docstring.
Also update changelog for missing previous changes while we are at it.
Previously, all renders were created and added manually when a newly
supported device was added to the documentation.
This commit revisits all diagrams by creating them using a single
LDRAW multi-file part model and LPUB3D building instructions file.
This makes perspective and resolution consistent across all images, and
we could update them all at once if needed.
It also removes the background from all images so they can be used
with different documentation themes.
Laurens Valk
David Lechner
Barry-Williams