Re: [CAD_CAM_EDM_DRO] Why calculate steps/unit? Just try it...
Posted by
CL
on 2003-02-15 18:31:01 UTC
Tim Goldstein wrote:
it be* rocket science to place the Settings for such, in a far more
understandable way for these newcomers in any control software. Instead
of requiring individuals to bring out their Abacus, fiddle around
getting all the wrong answers (because for the most part they quit
teaching math in schools - It's all "theory" these days), Software
developers need to let users put in the individual params you mention,
one at a time, and let the PC do the math !
In the case of " I don't know what my leadscrew does", At least they can
have all the other params set correctly, right off the bat. I mean,
likely one *would* know the degree steps of the motor, and to what
microstepping they set the drivers at, and IF they are running direct
driver or a simple ratio from motor to screw. If they want to guess
about the leadscrew then, well, they are only guessing with the one last
setting. All they need to do there is set a simple Dial indicator up and
turn the rascal one turn, Enter the results. Everything is done, and it
was easy.
FlashCut nailed this on the head if you ask me. Look at their "Machine
Setup" window. Foolproof.
I noticed in a friends WindeskNC-CNC WinCNC...... whatever it is called
again, as well as Mach1, that it looks for this one "magic" number per
axis, no matter what motor step degree, microstep setting, ratio or
"lead" one has. This method "requires" one to re-calculate, and possibly
goof up every time you adjust something.
So, instead of making the setup in the software a little more foolproof
by letting IT do the math, Developers clearly spend more time
explaining on how to arrive at the proper number. This is foolish, and
if I was a developer, I'd ditch the "magic" do it all number, for a
setup just like FC.
FC's method in this regard is not only better for the newbie, but also
TONS faster for us guys who regularly beta test software and hardware.
As we make settings changes to drivers, Swap leadscrews or change
ratios, we do not have to recalculate much of anything. All we do is
change the one param and we're set. Let the computer do the bulk of the
math.
others have been standing on a Soapbox.... I likely got nothing to stand
on :-)
Chris L
><Rant On>Your right on there Tim, It isn't rocket science. BUT, Neither *should
>
>All the required parameters are very
>easy to determine (lead screw pitch, reduction ratio, steps per
>revolution) and the math is simple.
>
><Rant Off>
>
it be* rocket science to place the Settings for such, in a far more
understandable way for these newcomers in any control software. Instead
of requiring individuals to bring out their Abacus, fiddle around
getting all the wrong answers (because for the most part they quit
teaching math in schools - It's all "theory" these days), Software
developers need to let users put in the individual params you mention,
one at a time, and let the PC do the math !
In the case of " I don't know what my leadscrew does", At least they can
have all the other params set correctly, right off the bat. I mean,
likely one *would* know the degree steps of the motor, and to what
microstepping they set the drivers at, and IF they are running direct
driver or a simple ratio from motor to screw. If they want to guess
about the leadscrew then, well, they are only guessing with the one last
setting. All they need to do there is set a simple Dial indicator up and
turn the rascal one turn, Enter the results. Everything is done, and it
was easy.
FlashCut nailed this on the head if you ask me. Look at their "Machine
Setup" window. Foolproof.
I noticed in a friends WindeskNC-CNC WinCNC...... whatever it is called
again, as well as Mach1, that it looks for this one "magic" number per
axis, no matter what motor step degree, microstep setting, ratio or
"lead" one has. This method "requires" one to re-calculate, and possibly
goof up every time you adjust something.
So, instead of making the setup in the software a little more foolproof
by letting IT do the math, Developers clearly spend more time
explaining on how to arrive at the proper number. This is foolish, and
if I was a developer, I'd ditch the "magic" do it all number, for a
setup just like FC.
FC's method in this regard is not only better for the newbie, but also
TONS faster for us guys who regularly beta test software and hardware.
As we make settings changes to drivers, Swap leadscrews or change
ratios, we do not have to recalculate much of anything. All we do is
change the one param and we're set. Let the computer do the bulk of the
math.
others have been standing on a Soapbox.... I likely got nothing to stand
on :-)
Chris L
>
>
Discussion Thread
vrsculptor <vrsculptor@h...
2003-02-15 10:29:47 UTC
Why calculate steps/unit? Just try it...
Tim Goldstein
2003-02-15 10:48:44 UTC
RE: [CAD_CAM_EDM_DRO] Why calculate steps/unit? Just try it...
CL
2003-02-15 18:31:01 UTC
Re: [CAD_CAM_EDM_DRO] Why calculate steps/unit? Just try it...
Tim Goldstein
2003-02-15 18:45:36 UTC
RE: [CAD_CAM_EDM_DRO] Why calculate steps/unit? Just try it...
Ray Henry
2003-02-16 06:28:00 UTC
Re: RE: Why calculate steps/unit? Just try it...
CL
2003-02-16 06:57:15 UTC
Re: [CAD_CAM_EDM_DRO] Why calculate steps/unit? Just try it...
CL
2003-02-16 07:41:22 UTC
Re: [CAD_CAM_EDM_DRO] Re: RE: Why calculate steps/unit? Just try it...