OpenCores
URL https://opencores.org/ocsvn/steppermotordrive/steppermotordrive/trunk

Subversion Repositories steppermotordrive

[/] - Rev 20

Rev

Filtering Options

Clear current filter

Rev Log message Author Age Path
20 Added old uploaded documents to new repository. root 5541d 01h /
19 Added old uploaded documents to new repository. root 5541d 07h /
18 New directory structure. root 5541d 07h /
17 Repaired some things in response to Frank Fertitta's email on sept. 2005:

Frank,

> > what your intention is here. It appears as though you are
> > just energizing the windings after you stop. If this is so,
> > what's keeping the motor from advancing to the next position
> > to reach "1111"? If the last state sent to the motor was

Yes, this is not the best thing to do. I will update cvs this evening, hopefully.

What it should be doing is to simply leave the outputs in the last state unless provide_static_holding is '0', in which case it should turn all the outputs off.

outputting "1111" will not cause the motor to move, because it will cause the two sets of windings to "arm wrestle" each other, but it's not the best idea because it wastes power aka. heat.

Best,
Steve

> Hello Steve,
>
> I was looking at your code you wrote for controlling a 4 or 6
> wire stepper motor. I see how you have added what could be a
> means for providing holding current but I don't understand
> what your intention is here. It appears as though you are
> just energizing the windings after you stop. If this is so,
> what's keeping the motor from advancing to the next position
> to reach "1111"? If the last state sent to the motor was
> "1010" then you stop at "1111" the motor is going to move. Or
> is your code only going to stop at "1111"? If that's the
> case, then will this limit the resolution of the motor? As I
> see it your code doesn't stop at "1111" unless it just
> happens to stop there when the count is "0".
> Am I missing something?
>
> Thanks for your excellent contributions. I do indeed learn
> from reading your work.
>
> Frank Fertitta		 franksdevel 6720d 17h /
16 fixed bug in step-enable-vs clock divider that was hidden by use of code in feedback loop. franksdevel 7322d 18h /
15 static holding force re-implemented franksdevel 7322d 19h /
14 more xilinx intermediate ignores franksdevel 7322d 23h /
13 let's ignore the right things franksdevel 7323d 00h /
12 This commit was manufactured by cvs2svn to create tag 'v1_1_1_1'. 7323d 01h /
11 This commit was generated by cvs2svn to compensate for changes in r10, which
included commits to RCS files with non-trunk default branches.		 franksdevel 7323d 01h /
10 Static holding not yet functional franksdevel 7323d 01h /
9 This commit was generated by cvs2svn to compensate for changes in r8, which
included commits to RCS files with non-trunk default branches.		 franksdevel 7323d 18h /
8 get the repository up & running... franksdevel 7323d 18h /
7 This commit was generated by cvs2svn to compensate for changes in r6, which
included commits to RCS files with non-trunk default branches.		 franksdevel 7365d 18h /
6 get the repository up & running... franksdevel 7365d 18h /
5 This commit was generated by cvs2svn to compensate for changes in r4, which
included commits to RCS files with non-trunk default branches.		 franksdevel 7445d 01h /
4 get the repository up & running... franksdevel 7445d 01h /
3 This commit was generated by cvs2svn to compensate for changes in r2, which
included commits to RCS files with non-trunk default branches.		 franksdevel 7570d 21h /
2 get the repository up & running... franksdevel 7570d 21h /
1 Standard project directories initialized by cvs2svn. 7570d 21h /

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.