-
-
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] PoweredUp Light (item #88005) uncontrollable on Move Hub (item #88006) #913
Comments
Firmware version? |
I'm able to reproduce with v3.2.2. |
Thanks for the report. Who knows how long it has been like that. I guess not many people are using the light on the move hub. 😄 You can grab a firmware with the fix from https://github.com/pybricks/pybricks-micropython/suites/10297481669/artifacts/506150765 if you don't want to wait for the next release. |
how do you install that firmware? or what do you do with that zip file? |
Please see https://pybricks.com/install/technic-boost-city/#installing-the-latest-build-advanced |
Thanks for the quick turnaround! Love it! |
… offset This was using the I/O port offset instead of using the motor port offset. Since it controls the motors, it needs to use the motor port numbering. This was only noticed on move hub since it is the only hub where there are motor ports without I/O ports. Fixes: pybricks/support#913
it works awesome! thanks! |
Describe the bug
Running "Making the light blink" example from the Light object documentation connected to
Port.C
on a Move Hub results in the motor onPort.A
starting, stopping, starting, stopping, etc. ("blinking").To reproduce
Run the following example code (modified to use
Port.C
for the LED module):Expected behavior
The expected behavior is for the LEDs on the 88005 PoweredUp Light to blink on and off.
Screenshots
https://user-images.githubusercontent.com/2899323/211683271-866a9e6f-c2f6-445b-8875-33f472988464.mov
The text was updated successfully, but these errors were encountered: