-
Notifications
You must be signed in to change notification settings - Fork 85
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
Startup repeatability #5
Comments
In order to find position faster after power up in an unknown position, a set of index pulses, instead of just one, could be used. If the gap between index pulses is different on the two sides of the center "home" index pulse, then the correct direction to rotate to reach home. E.g. if there are an odd number of regular sized eyes between index pulses on one side of home and an even number on the other side, a small movement in any direction from any position should tell us which way to move to reach home. If the count of regular sized eyes between index pulses increases as you move away from home, then the exact position can be found faster. E.g. on one side, there might be 4, then 6, 8 regular eyes between indexes and on the other side, 5, 7, and 9. |
Clever!
_____
Lots of games could be played here.
For instance, the idea of partially covering a slot means
we effectively get 2 bits from it, ie "that it is a slot"
and that it is "partial or full".
But can we get more bits out of it? ie
1/4 covered, 1/2 covered, 3/4 covered?
and apply that to James N's trick to tell
how far a slot is from home?
Maybe this interferes too much with the normal accuracy.
A 2nd row of slots, closer to disc center, lower rez but
more bits per slot as I describe above?
Transparently colored slots?
Just throwing some more cards on the table.
…On Sun, May 19, 2019 at 1:09 PM JamesNewton ***@***.***> wrote:
In order to find position faster after power up in an unknown position, a
set of index pulses, instead of just one, could be used.
If the gap between index pulses is different on the two sides of the
center "home" index pulse, then the correct direction to rotate to reach
home. E.g. if there are an odd number of regular sized eyes between index
pulses on one side of home and an even number on the other side, a small
movement in any direction from any position should tell us which way to
move to reach home.
If the count of regular sized eyes between index pulses increases as you
move away from home, then the exact position can be found faster. E.g. on
one side, there might be 2 then 4, 6, 8 regular eyes between indexes and on
the other side, 3, 5, 7, and 9.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AAJBG7JFNWNNQBNYBRNI5OLPWGCT5A5CNFSM4FMTH5MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVXGLCA#issuecomment-493774216>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJBG7IK6IDYLXHCTC3QHXDPWGCT5ANCNFSM4FMTH5MA>
.
|
this issue is effectively closed for the HDI robots. |
Kamino cloned this issue to HaddingtonDynamics/OCADO |
Having a way for Dexter to find "home" position automatically would be a wonderful help. This will both allow it to accurately interact with a work surface or other object via "dead reckoning" (no need to touch or be guided to a starting point). It will also removed the need to calibrate Dexter on startup because the prior calibration can be applied immediately.
Currently, the solution to this is to add a "dial" or little knob to each motor shaft. The robot is set to a perfect zero position once during manufacture (with a test stand) then the dials are installed and their correct positions marked. While powered off, the robot is move close to the home position, then each dial is turned until it lines up with the known home position.
Automated methods of solving this problem include:
The text was updated successfully, but these errors were encountered: