-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Bug] PUPdevice on TechnicHub reports ID=8 when no device is attached #230
Comments
Does the same thing happen on other hubs or only the TechnicHub? |
David, I only have the TechnicHub, MoveHub, PrimeHub and InventorHub. I do not know for the other hubs. |
Sorry, I was just looking at the title of the issue. |
Thanks for reporting this and for taking the time to test this on all hubs. Possibly related: I recently noticed that it was possible to initialize |
Funny, may be related, but not on a technichub: from pybricks.pupdevices import DCMotor
from pybricks.parameters import Port
from pybricks.tools import wait
# Initialize a motor without rotation sensors on port A.
example_motor = DCMotor(Port.A)
# Make the motor go clockwise (forward) at 70% duty cycle ("70% power").
example_motor.dc(70)
# Wait for three seconds.
wait(3000)
# Make the motor go counterclockwise (backward) at 70% duty cycle.
example_motor.dc(-70)
# Wait for three seconds.
wait(3000) But also on the TechnicHub... |
So maybe it's a different issue then. Thanks! |
(off topic) Python tip: Always use |
Thank you, David. (more on topic) I now have a "powered-up leds" device that should be reported as "8". |
Found build artifact and this issue is fixed. trimmed extra
And with leds attached to port C and D:
|
Describe the bug
On a TechnicHub PUPDevice(port) reports device.info as id = 8
See pybricks technical-info: list of identifications
Part of it:
To reproduce
Steps to reproduce the behavior:
Expected behavior
Would have expected the hubs all to response the same or similar at least.
. Either return an OSError ENODEV
or
. return a device ID of '0' zero
Priority
LOW
Screenshots
None now
Source used
Console log
The text was updated successfully, but these errors were encountered: