Dynomotion

Group: DynoMotion Message: 5732 From: chrismd500 Date: 10/5/2012
Subject: InvDistPerCycle
Hi

Maybe I'm misunderstanding this, but isn't InvDistPerCycle supposed to allow you to specify the Move, MoveRel, etc, commands in a different position units than cycles?

The problem is that no matter what value I specify for InvDistPerCycle the move commands are just in cycles, i.e. unaffected by InvDistPerCycle.

I'm using Kflop+Kstep with stepper motors.
Group: DynoMotion Message: 5735 From: TK Date: 10/5/2012
Subject: Re: InvDistPerCycle
invDistPerCycle has no effect on step/dir mode. I suggest you leave KFLOP operate in uSteps and do any resolution multiplication in your application. But if necessary you can use the OutputGain parameter to scale the output.

Regards

TK

On Oct 5, 2012, at 4:42 PM, "chrismd500" <kristoffer.jensen@...> wrote:

 

Hi

Maybe I'm misunderstanding this, but isn't InvDistPerCycle supposed to allow you to specify the Move, MoveRel, etc, commands in a different position units than cycles?

The problem is that no matter what value I specify for InvDistPerCycle the move commands are just in cycles, i.e. unaffected by InvDistPerCycle.

I'm using Kflop+Kstep with stepper motors.
Group: DynoMotion Message: 5736 From: chrismd500 Date: 10/6/2012
Subject: Re: InvDistPerCycle
Oh ok, then it make sense, thanks. I was hoping to make it easy for myself by adjusting the InvDistPerCycle instead of in the application ;)

When you say uSteps you mean microsteps right? I'm a newbie so I just want to make sure I don't mix up any nomenclature...

Thank you.

--- In DynoMotion@yahoogroups.com, TK <tk@...> wrote:
>
> invDistPerCycle has no effect on step/dir mode. I suggest you leave KFLOP operate in uSteps and do any resolution multiplication in your application. But if necessary you can use the OutputGain parameter to scale the output.
>
> Regards
>
> TK
>
> On Oct 5, 2012, at 4:42 PM, "chrismd500" <kristoffer.jensen@...> wrote:
>
> > Hi
> >
> > Maybe I'm misunderstanding this, but isn't InvDistPerCycle supposed to allow you to specify the Move, MoveRel, etc, commands in a different position units than cycles?
> >
> > The problem is that no matter what value I specify for InvDistPerCycle the move commands are just in cycles, i.e. unaffected by InvDistPerCycle.
> >
> > I'm using Kflop+Kstep with stepper motors.
> >
> >
>
Group: DynoMotion Message: 5739 From: Tom Kerekes Date: 10/6/2012
Subject: Re: InvDistPerCycle
Yes.  By uSteps I mean units of microsteps.  With KSTEP 16x microstepping there are 200x16=3200 microsteps for one revolution of a standard stepper motor.  So you would do the math and convert the desired distance to microsteps and tell KFLOP to move that many microsteps.  Actually KFLOP isn't aware of any microstepping.  It just outputs step pulses to the stepper drive.  So for example if your system has a resolution of 10000 microsteps per inch and you wish to move 3 inches you would tell KFLOP to move 3 x 10000 = 30000 steps. 

Don't confuse this with the KFLOP "Microstepping" mode.  This is probably poorly named but in this mode is quite different where the actual current in the stepper's coils is controlled directly in a sinusoidal manner.  To use this mode KFLOP must have a means of directly controlling the coil currents such as with our SnapAmp.   KSTEP is different.  It is controlled by step and direction pulses in a more traditional manner

HTH
TK

Group: DynoMotion Message: 5775 From: chrismd500 Date: 10/10/2012
Subject: Re: InvDistPerCycle
Thanks! Yes I was a little confused with the microsteps-settings, but this made things very clear.

Thanks,
CHris

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Yes.  By uSteps I mean units of microsteps.  With KSTEP 16x microstepping there are 200x16=3200 microsteps for one revolution of a standard stepper motor.  So you would do the math and convert the desired distance to microsteps and tell KFLOP to move that many microsteps.  Actually KFLOP isn't aware of any microstepping.  It just outputs step pulses to the stepper drive.  So for example if your system has a resolution of 10000 microsteps per inch and you wish to move 3 inches you would tell KFLOP to move 3 x 10000 = 30000 steps. 
>
> Don't confuse this with the KFLOP "Microstepping" mode.  This is probably poorly named but in this mode is quite different where the actual current in the stepper's coils is controlled directly in a sinusoidal manner.  To use this mode KFLOP must have a means of directly controlling the coil currents such as with our SnapAmp.   KSTEP is different.  It is controlled by step and direction pulses in a more traditional manner
>
>
> HTH
> TK
>
>
>
> ________________________________
> From: chrismd500 <kristoffer.jensen@...>
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, October 6, 2012 3:47 AM
> Subject: [DynoMotion] Re: InvDistPerCycle
>
>
>  
> Oh ok, then it make sense, thanks. I was hoping to make it easy for myself by adjusting the InvDistPerCycle instead of in the application ;)
>
> When you say uSteps you mean microsteps right? I'm a newbie so I just want to make sure I don't mix up any nomenclature...
>
> Thank you.
>
> --- In DynoMotion@yahoogroups.com, TK <tk@> wrote:
> >
> > invDistPerCycle has no effect on step/dir mode. I suggest you leave KFLOP operate in uSteps and do any resolution multiplication in your application. But if necessary you can use the OutputGain parameter to scale the output.
> >
> > Regards
> >
> > TK
> >
> > On Oct 5, 2012, at 4:42 PM, "chrismd500" <kristoffer.jensen@> wrote:
> >
> > > Hi
> > >
> > > Maybe I'm misunderstanding this, but isn't InvDistPerCycle supposed to allow you to specify the Move, MoveRel, etc, commands in a different position units than cycles?
> > >
> > > The problem is that no matter what value I specify for InvDistPerCycle the move commands are just in cycles, i.e. unaffected by InvDistPerCycle.
> > >
> > > I'm using Kflop+Kstep with stepper motors.
> > >
> > >
> >
>