Re: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry
Posted by
Jon Elson
on 2010-12-17 10:06:09 UTC
timgoldstein wrote:
what the following error is. The computer sends the steps, and ASSUMES
the drive has put the motor there. The old G320 had a fixed error limit
of +/- 128 encoder counts, which could be quite a large error. I had a
friend locally who had a G320 machine with high-resistance motors and
only 36 V supply, and it would not return to the servo null. You could
turn the motors 10-15 degrees and they would just sit there. Sometimes,
after seconds, they would go "grrnk-grrkn-grrnk" and move back closer to
the null point. This was not what I'd call tight servo control. Some
other drives like the Rutex at least had a way to hook up a computer and
get tuning and performance info out of the drive. (Not that I'm
recommending Rutex here, they have other problems.)
Another problem with the step/dir approach is you can't ever E-stop the
machine without having to rehome. I usually estop my machine whenever I
walk away from it, just click a button to bring it back online.
plate with several linear slides mounted to it in a plane. There are
links between these slides and the platform. This avoids having to make
extremely good telescoping rods.
expand usage in new areas. We do it in a different area, many of the
smaller enhancements are accomplished by finding new and ingenious ways
to reconnect stuff in HAL to bring out things to display on the
customizable part of the GUI. I added an MPG with a filter to prevent
the coarse MPG counts from "buzzing" the servos, and a spindle speed
display with filtering to stabilize the displayed value, and a
rate-of-change limiter to the spindle speed, mostly for use when rigid
tapping, all in HAL scripts, without touching a single line of the EMC
code base. HAL is the big new thing when EMC became EMC2, the
brainchild of John Kasunich. It is a scripted language and framework
that connects all the major components of EMC2 together, and allows you
to make new connections for all sorts of functions.
forces are quite predictable. Metal machining is just not that
predictable, so the only way to avoid position loss --EVER-- is massive
overkill. I'd mich rather have a wimpy machine that TELLS me when it is
overloaded than one that will just try to bull its way through concrete.
of the stuff there has links to the "back pages" with more
detailed descriptions. The PPMC (analog servo interface) has been
relatively unchanged since 2002, the Universal Stepper Controller
has been out since 2002, and my PWM controller and matching servo amps
have been out since 2004.
Jon
> For the sake of those just getting involved, I want to point out that there are different approaches to servos. One is driven like a stepper with pulses being sent to the drive with each step telling the drive to move the motor 1 increment (usually an encoder pulse) and then the drive electronics tracking the movement and adjusting accordingly. In this setup it is open loop as far as the computer is concerned. So the controller program does not actually know where the axis being moved really is. A very viable and low cost servo approach that gives you the acceleration and speed benefits of a servo. I have my Bridgeport series II (known by all the old timers on the group as Bridgett) running Gecko G320 drives which are this style.Right. The problem with Gecko-style drives is you have no way to know
>
what the following error is. The computer sends the steps, and ASSUMES
the drive has put the motor there. The old G320 had a fixed error limit
of +/- 128 encoder counts, which could be quite a large error. I had a
friend locally who had a G320 machine with high-resistance motors and
only 36 V supply, and it would not return to the servo null. You could
turn the motors 10-15 degrees and they would just sit there. Sometimes,
after seconds, they would go "grrnk-grrkn-grrnk" and move back closer to
the null point. This was not what I'd call tight servo control. Some
other drives like the Rutex at least had a way to hook up a computer and
get tuning and performance info out of the drive. (Not that I'm
recommending Rutex here, they have other problems.)
Another problem with the step/dir approach is you can't ever E-stop the
machine without having to rehome. I usually estop my machine whenever I
walk away from it, just click a button to bring it back online.
>I think the more-easily built ones are called hexaglides. They have a
>
> Speaking of hexapods, does anyone know of any hobby priced version or achievable DIY approaches? They are fasinating machines. If you don't know what one is you need to Google it. Maybe someone can post some links and we can talk about the pluses and minuses.
>
>
plate with several linear slides mounted to it in a plane. There are
links between these slides and the platform. This avoids having to make
extremely good telescoping rods.
>Well, adding a FUNCTION that wasn't available before certainly can
> But, I talked to Art about it once. Not sure if he would admit to it in public, but what he told me was every time he added a button or widget to the screen he sold more licenses.
>
>
expand usage in new areas. We do it in a different area, many of the
smaller enhancements are accomplished by finding new and ingenious ways
to reconnect stuff in HAL to bring out things to display on the
customizable part of the GUI. I added an MPG with a filter to prevent
the coarse MPG counts from "buzzing" the servos, and a spindle speed
display with filtering to stabilize the displayed value, and a
rate-of-change limiter to the spindle speed, mostly for use when rigid
tapping, all in HAL scripts, without touching a single line of the EMC
code base. HAL is the big new thing when EMC became EMC2, the
brainchild of John Kasunich. It is a scripted language and framework
that connects all the major components of EMC2 together, and allows you
to make new connections for all sorts of functions.
>Steppers are fine for things where the speed ratio is modest and the
>
> I have to disagree on this. I have full closed loop servo machines, open loop servo machine, and stepper machines. They all work and make fine parts. Different capacity and performance, but all capable of making a to tolerance piece.
>
>
forces are quite predictable. Metal machining is just not that
predictable, so the only way to avoid position loss --EVER-- is massive
overkill. I'd mich rather have a wimpy machine that TELLS me when it is
overloaded than one that will just try to bull its way through concrete.
> Jon, can you also post a link to where someone can get more details and pricing on your products for servos?Sure, http://pico-systems.com/oscrc4/catalog/ is my web store, and most
>
>
of the stuff there has links to the "back pages" with more
detailed descriptions. The PPMC (analog servo interface) has been
relatively unchanged since 2002, the Universal Stepper Controller
has been out since 2002, and my PWM controller and matching servo amps
have been out since 2004.
Jon
Discussion Thread
timgoldstein
2010-12-12 22:14:31 UTC
CAD experiment idea
Roland Jollivet
2010-12-13 03:34:22 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment idea
Jamie Cunningham
2010-12-13 03:56:18 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment idea
Ron Thompson
2010-12-13 05:24:40 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment idea
Tim Goldstein
2010-12-13 05:42:10 UTC
Re: CAD experiment idea
Ron Thompson
2010-12-13 06:09:06 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment idea
Kevin Martin
2010-12-13 07:04:00 UTC
RE: [CAD_CAM_EDM_DRO] CAD experiment idea
Stephen Wille Padnos
2010-12-13 07:06:33 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment idea
Roland Jollivet
2010-12-13 07:46:25 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment idea
R.L. Wurdack
2010-12-13 07:54:59 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment idea
Tim Goldstein
2010-12-13 08:17:23 UTC
Re: CAD experiment idea
Tim Goldstein
2010-12-13 08:53:42 UTC
Re: CAD experiment idea
Tim Goldstein
2010-12-13 09:00:17 UTC
Re: CAD experiment idea
Tim Goldstein
2010-12-13 09:02:56 UTC
Re: Re: [CAD_CAM_EDM_DRO] CAD experiment idea
Roland Jollivet
2010-12-13 09:06:29 UTC
[CAD_CAM_EDM_DRO] CAD experiment idea
timgoldstein
2010-12-13 09:17:38 UTC
Re: CAD experiment idea
Ron Thompson
2010-12-13 12:45:45 UTC
CAD experiment entry
timgoldstein
2010-12-13 12:49:59 UTC
Re: CAD experiment entry
Ron Thompson
2010-12-13 13:29:56 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
H & J Johnson
2010-12-13 15:16:30 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-13 15:34:13 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-13 15:39:54 UTC
Re: CAD experiment entry
Ron Thompson
2010-12-13 16:00:40 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
H & J Johnson
2010-12-13 16:02:54 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
H & J Johnson
2010-12-13 16:06:50 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-13 16:25:27 UTC
Re: CAD experiment entry
Michael Fagan
2010-12-13 17:05:04 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment entry
Andy Wander
2010-12-13 17:11:24 UTC
RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
R.L. Wurdack
2010-12-13 17:24:09 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
H & J Johnson
2010-12-13 17:29:58 UTC
Re: RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Andy Wander
2010-12-13 18:17:03 UTC
RE: RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Peter Homann
2010-12-13 18:48:08 UTC
RE: RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Andy Wander
2010-12-13 18:50:57 UTC
RE: RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-13 23:23:56 UTC
[CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-14 05:00:00 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-14 05:17:36 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-14 05:43:39 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment entry
Ron Thompson
2010-12-14 05:57:27 UTC
Re: [CAD_CAM_EDM_DRO] CAD experiment entry
timgoldstein
2010-12-14 08:44:40 UTC
Re: CAD experiment entry
timgoldstein
2010-12-14 09:25:58 UTC
Re: CAD experiment entry
H & J Johnson
2010-12-14 09:27:58 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-14 10:12:05 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-14 12:45:23 UTC
Re: CAD experiment entry
Ron Thompson
2010-12-14 13:39:41 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-14 15:08:47 UTC
Re: CAD experiment entry
Peter Reilley
2010-12-14 15:25:51 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-14 16:57:56 UTC
Re: CAD experiment entry
Brian Worth
2010-12-14 21:49:49 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Peter Homann
2010-12-14 22:03:54 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-14 22:46:21 UTC
Re: CAD experiment entry
William Thomas
2010-12-15 04:27:56 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-15 04:40:51 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Kevin Martin
2010-12-15 05:20:51 UTC
RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-15 06:23:27 UTC
Re: CAD experiment entry
timgoldstein
2010-12-15 06:33:51 UTC
Re: CAD experiment entry
Mike Payson
2010-12-15 06:54:41 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-15 07:00:39 UTC
Re: CAD experiment entry
Kevin Martin
2010-12-15 07:38:42 UTC
RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Swiss
2010-12-15 08:26:31 UTC
RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
CNC 6-axis Designs
2010-12-15 08:29:06 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Jon Elson
2010-12-15 10:45:31 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-15 17:05:59 UTC
Re: CAD experiment entry
Kevin Martin
2010-12-15 20:24:24 UTC
RE: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-15 21:16:03 UTC
Re: CAD experiment entry
timgoldstein
2010-12-15 21:17:14 UTC
Re: CAD experiment entry
timgoldstein
2010-12-16 08:37:58 UTC
Re: CAD experiment entry
Ron Thompson
2010-12-16 09:07:45 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Jon Elson
2010-12-16 10:08:36 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-16 14:34:40 UTC
Re: CAD experiment entry
timgoldstein
2010-12-16 15:17:46 UTC
Re: CAD experiment entry
timgoldstein
2010-12-16 16:28:39 UTC
Re: CAD experiment entry
Ron Thompson
2010-12-16 16:52:14 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
Ron Thompson
2010-12-16 16:57:49 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-16 20:45:14 UTC
Re: CAD experiment entry
William Thomas
2010-12-16 21:23:48 UTC
Re: [CAD_CAM_EDM_DRO] Re: CAD experiment entry
timgoldstein
2010-12-16 22:13:34 UTC
EMC, Was Re: CAD experiment entry
Stephen Wille Padnos
2010-12-17 05:28:36 UTC
Re: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry
Jon Elson
2010-12-17 09:24:52 UTC
Re: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry
Jon Elson
2010-12-17 09:31:09 UTC
Re: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry
Jon Elson
2010-12-17 10:06:09 UTC
Re: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry
Jeffrey T. Birt
2010-12-17 10:28:06 UTC
RE: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry
samcoinc2001
2010-12-17 11:05:31 UTC
EMC, Was Re: CAD experiment entry
Jon Elson
2010-12-17 19:57:50 UTC
Re: [CAD_CAM_EDM_DRO] EMC, Was Re: CAD experiment entry