-
Notifications
You must be signed in to change notification settings - Fork 19
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
add Technic Medium Angular Motor Grey (mindstorms set 51515) #110
Conversation
Can you add here an output of the |
device list output for good measure:
|
Mmmh ... Do not like that. Have you tried the test pattern once or multiple times? Try to check out if GotoRealZero is a stable function from its implementation perspective. |
I tested this a couple of times.. I'll do some more testing side-by-side, executing the same things on both devices on a single hub. |
sharpbrick#75 non-breaking
9096a66
to
94d7ceb
Compare
I investigated this, and the low speed (5) is the cause of the GotoRealZero not working. If I changed this to 10, it works, and returns to the marked position correctly. At 5 it does not move at all (whereas the technic large angular motor does) Now simply changing the speed to 10 works, but maybe this (or a minimum speed value) should be parameterized so different absolutemotor's can a specific minimum required to actually move the motor. What do you think @tthiery ? |
Awesome investigation. Thanks. I will merge this. Regards the minimum speed: File a issue. Let us park this. Enough stuff to finish up right now. |
added this motor, it does however behave differently compared to the large technic angular motor, GotoRealZeroAsync() does something different (it stays in the same spot, you can hear the motor whine slightly though, unsure if it is unable to move because power is too low or that it is actually not moving because it is in the 'correct' spot already)
see also #75