-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature, Bug] Remote close method. #802
Comments
Laurens, would using ThisHub make this program easier to be used on different hubs? Or is ThisHub not to be promoted? (You lack "<----" on the PrimeHub import above) |
We're not advocating for it due to the difficulties we have seen in ev3dev. One class to fit all sounds good, but often leads to confusion over time as functionality diverges. It also gives problems with autocomplete, since it wouldn't know which hub it is. |
While thinking about discussions entry #975
Have been looking through "Actions" in github.com/pybricks/pybricks-micropython/actions Is that the firmware you refer to, Laurens? |
This was also requested in https://github.com/orgs/pybricks/discussions/1445 |
Is your feature request related to a problem? Please describe.
This was proposed in pybricks/pybricks-micropython@a2b2e44 but never merged, so I had a look at how well it works.
Describe the solution you'd like
With
close()
included, you can quite easily make programs that allow the remote to hop between hubs.For example, take a Prime Hub and a Technic Hub, each with a motor on Port A.
They both run this program, modified on the lines indicated with
<----
Expected behavior:
VID_20221114_160958.mp4
problem
This uncovers a few interesting Bluetooth problems that may help us identify underlying bluetooth bugs seen elsewhere.
This only works well if the Prime Hub is connected to Pybricks Code. This was new to me.
When not connected, we get all sorts of strange conditions happening. Usually it will not jump to the Prime Hub, or the Prime Hub freezes.
So my vote is not to merge this for 3.2 but include it in the next big Bluetooth release (3.3 or 3.4).
The text was updated successfully, but these errors were encountered: