-
Notifications
You must be signed in to change notification settings - Fork 2
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
Investigate TechnicLargeAngularMotor (grey) STATS mode #9
Comments
I tried the MultiValueMode thing, but it never returns a value. It is possible to call SetupNotificationAsync for the STATS mode, but regardless of the notification setting it never returns a value. I tried to send an PortInformationRequest to get the port value to no avail and if I interpret the lego wireless protocol document correctly, that only works if it's actually an Input mode, which it isn't. So i'm unsure how to actually get a value to be sent by the device. Also, the |
As a wider community we desperately need a channel to the LEGO group. I mean, this is not critical ... but in 10 years when LEGO moves on, the community needs to understand every detail of it and not only a part of it. |
I tend to agree with you on this. Although I could somewhat understand that they would not be interested in documenting their own devices like this. How do you suggest we try and get this information? Contacting Lego through the LWP github repo seems of no use (or at the very least you can wait months if not years for a reply). Maybe simply writing to Lego support and hope to somehow get trough to the people that know? |
I hope with the Spike/Mindstorms Hub there will be a spec dump soon. I also hope that one day we have a direct line to their dev team. Do not worry about this right now. It is named stats ... so not really a big concern about the functionality. For me open issues are not a concern. There are not bugs (which are labeled) but ideas what to do next. |
The
TechnicLargeAngularMotorGrey
has a non-understood STATS mode. Investigate it and extend model.Discovered as part of sharpbrick/powered-up#75 and sharpbrick/powered-up#108
The text was updated successfully, but these errors were encountered: