Re: [CAD_CAM_EDM_DRO] Re: How to go from 2.5 D to real 3 D ??

Howdy Art,
Well this stuff boggles my mind............ Someday I hope to try some simple
programming. What you are doing seems pretty indepth.

I am a bit amazed when I think back a few years to the early days of Windows CNC
control. It was an incredibly challenging thing with many saying it was just
impossible.

I find it quite interesting that you have been able to pull this off without an
external timing chip like others have had to use.

The only thing I can relate it to is Indexer LPT as that used the timing from
the processor to send out the pulses but really was a tsr, with a Windows GUI
initiating it. Indexer had run very smooth, and very "In Windows" short of no
G-Code interface. Do you have any idea why others have not used this same
technique ? As I recall they had a pretty high pulse rate initially. That pulse
rate grew substantially with the current version.

Some that I have been chitchatting with, have pointed out that your control is
pretty impressive. Make sure that it is on a Sherline at NAMES next year so Fred
can run a test on it.

Art Fenerty wrote:

> Hi Chris:
>
> As for Master5 and line,arc differences. After doing many experiments and
> try many different methods, I kept coming back to the way EMC does it.
> (Those NIST guys are geniuses) Small segment, long segment, arcs, are pretty
> much the same thing. Basically a kinematic engine is asked the question,
> Where will each axis be in 100uSeconds? Being that the maximum speed is
> 8192Hz, the fastest an axis can pulse is 100uSeconds from the last puilse.
> So , the engine calculates whether or not a moving point on a toolpath
> specified by the G-Code will have moved or not on any axis 100uS from now.
> If so, pulse, if not, what about the next 100uS period. In this way an arc
> is just an extension of the linear toolpath and creates a constant contour
> movement. Of course acceleration, deceleration and feed speeds are kept in
> mind to calculate the next 100uS periods reach point.
> It is more complicated to calculate maximum velocities and blend
> acceleration profiles during an arc, so generally, an arc is slower to
> calculate, but runs as fast as a series of line segments when pulseing out
> of the buffers. The buffers keep the time profile clean by allowing the
> engine to slow calculations on an arc, while pulseing the line calculated
> from a few moves ago. The engine will catch up while the motors are
> decelerating or accelerating or doing straight line segments. Hence,
> constant velocity contouring.
>
> Art
> Master5 Software
> http://users.andara.com/~fenerty/master.htm
>
> Addresses:
> FAQ: http://www.ktmarketing.com/faq.html
> FILES: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO/files/
>
> Post messages: CAD_CAM_EDM_DRO@yahoogroups.com
> Subscribe: CAD_CAM_EDM_DRO-subscribe@yahoogroups.com
> Unsubscribe: CAD_CAM_EDM_DRO-unsubscribe@yahoogroups.com
> List owner: CAD_CAM_EDM_DRO-owner@yahoogroups.com, wanliker@...
> Moderator: jmelson@... timg@... [Moderator]
> URL to this page: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO
> bill,
> List Manager
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/