-
Notifications
You must be signed in to change notification settings - Fork 32
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
How to get index pin pulsing? #63
Comments
Hi, set the bit Not sure if this library can do this, need to check |
Hi, Thank you. Figured out this in the meantime too. But the value should be 0. The library does not support it. Therefore added in library as below. It works by calling e.g in the setup: stepper_driver.useIndexPin(); !
|
Well, I did get it to work with the additions to the library as shown above. It gives a pulse per 4 full steps. See page 66 of the datasheet. (rev 1.09) |
Hi the datasheet say the following:
How is it possible to detect microstep position if it guves one pulse per 4 fullsteps? |
Hi, first of all thanks for such a detailed reply.
Does this mean, it toggles per each fullstep, or does it toggle per each microstep |
That will be dependent on what you set the index_step bit and the index_otpw bit too, if you want it to output a pulse at the starting position of each full step you need both bits set to 0. If you want a pulse per step the you need only need index_step set to 1(as this overrides index_otpw). I haven't looked at the output of the index pin when both bits are set to 0 yet, I'll test it and edit this with the results for you. |
Thanks a lot, what does the datasheet mean by
Shows first microstep position of sequencer? |
Hi,
My configuration is Bigtree TMC2209.
The datasheet talks about a possibility of pulsing the index pin for each step. But I believe it is set now differently, because I see no output on the scope.
I need use of the index pin to get posistion while using internal pulsgenerator.
How do I get the index pulsing in each step?
Your help is appreciated.
The text was updated successfully, but these errors were encountered: