Re: [CAD_CAM_EDM_DRO] Re: parallel port

Hi Jan, List,

Yeah, that's it! Simple DOS does not "slice up" the CPU time with it's
own tasks (if you're not calling it's functions). And if no EMM type
drivers or managers are loaded, then it's mostly out of the way. The
keyboard and timer do give interrupts, but these can be managed.

In your case, GWBASIC can write to the I/O, and make steps just fine,
although as I recall, you aren't generating steps at a high speed. That
would further entail acceleration/deceleration code. Multiple axis
(which you may do?) require further enhancements to develop clean pulse
streams. Next add arcs, and put them in three planes! Canned cycles
will also make your programming exercises easier. And last but not
least, add a parser to interpret Gcode.

Yes, a "DOS application" can get away with things! That's why I like
STEP4, which is my 'C' controller program for DOS. To get a taste of
these DOS applications, try TurboCNC. Inexpensive, and source is available!

Alan KM6VV

JanRwl@... wrote:

> In a message dated 5/20/2004 1:45:11 PM Central Standard Time, KM6VV@...
> writes:
> DOS keeps out of the way (for the most part). Why not work in DOS?<<
>
> I assume, then, that this is why MY "CNC" programs written in GWBASIC, which
> is CALLED a "DOS application," work with no problems. I use only a simple
> assembly-code "patch" which is CALLed from BASIC to strobe selected bits on the
> printer-port, and this works fine! Jan Rowland
>