Re: [CAD_CAM_EDM_DRO] Windows timing subroutines, how do they work?

Hi Alan,

That is right. Each entry in the buffer holds the axis velocities for
each time segement. I don't know what the time segments are, at a guess
proably around 500us or so. I haven't actually seen any of the Windows
code. My information is taken from things that Art has mentioned and
hacking the G2002 code that he published. Presumably there is another
communications channel for status and current position data etc.

Art did try to do a direct port of this system to the G2002. In fact the
code is still available in the files area of the Gecko Yahoo group. I
think there was some concern about USB timing with this system. I
believe Art is also working with someone else on a mix of EMC style low
level routines running on a G101 (renamed G2002) with Mach2/3/whatever
providing the high level parsing and path planning.

Les


Alan Marconett wrote:

>Hi Les,
>
>Thanks for the additional information. Sounds like the Mach driver does a
>good job, as long as the competing programs you describe are kept out.
>
>I can see how a circular buffer would be used for communication with the
>driver. I gather that it passes blocks (structures) of velocity (or steps?)
>and step counts for the driver to generate? Are there any return messages?
>
>Any thought to running this circular queue out a USB, and into a hardware
>pulse generator device (G2002 comes to mind)?
>
>Alan KM6VV
>
>
>
>