RE: [CAD_CAM_EDM_DRO] Driver / Controller
Posted by
Carol & Jerry Jankura
on 2002-12-08 16:16:50 UTC
It's understandable that you're confused, as the term 'driver' can be used
in a couple of ways:
1. A driver may be a piece of software that provides a standard way for an
application program to interface with some piece of hardware. Examples of
drivers are found in how your program may work with files on a hard drive,
the screen on the CRT, or the printer port lines. MS-DOS (and its workalikes
such as DR-DOS or FreeDOS) don't require any drivers to access I/O ports.
Windows 9x still allows you to access I/O ports directly, but often requires
a software driver if the access is time critical. Windows NT, 2000, or XP
require that you write a software driver if you want to access any I/O
ports.
2. A drive (or sometimes it's called a driver) may be one of two things - it
may be a hardware box that converts step and direction signals sent to a
motor from a printer port into the necessary coil phase changes necessary to
sequence the coils and also provide the power to actually drive the motor
coils. Gecko drives are an example of this, as are the Mauch or Xylotex
drivers. Or, a drive may simply be the last stage that provides the current
necessary to drive the coils, but does no sequencing. I believe that the
hardware that's sold with the Taig CNC machne is an exampleof this second
type of drive.
3. A controller can be almost anything. It could be a complete box that
accepts a paper tape and sends signals to the motor coils. Or, it could be a
'black box' that fits between the printer port and the high current circuits
that actually drive a motor.
In another message, Tim Goldstein wrote:
"For the purposes of a step and direction system (steppers and servos
like Gecko G3x0) a controller is the software package your run on the PC
that reads G-code and outputs step and direction signals via the PC
parallel port (Mach1, TurboCNC, etc.) or it's own dedicated external box
(DeskCNC, Flashcut, etc.)."
I would normally call this software packge the 'G-Code interpreter'
-- Jerry
|
|I'm sorry but I'm still not "getting" one thing and I hope someone
|can help.
|
|The difference between a DRIVER and a CONTROLLER.
in a couple of ways:
1. A driver may be a piece of software that provides a standard way for an
application program to interface with some piece of hardware. Examples of
drivers are found in how your program may work with files on a hard drive,
the screen on the CRT, or the printer port lines. MS-DOS (and its workalikes
such as DR-DOS or FreeDOS) don't require any drivers to access I/O ports.
Windows 9x still allows you to access I/O ports directly, but often requires
a software driver if the access is time critical. Windows NT, 2000, or XP
require that you write a software driver if you want to access any I/O
ports.
2. A drive (or sometimes it's called a driver) may be one of two things - it
may be a hardware box that converts step and direction signals sent to a
motor from a printer port into the necessary coil phase changes necessary to
sequence the coils and also provide the power to actually drive the motor
coils. Gecko drives are an example of this, as are the Mauch or Xylotex
drivers. Or, a drive may simply be the last stage that provides the current
necessary to drive the coils, but does no sequencing. I believe that the
hardware that's sold with the Taig CNC machne is an exampleof this second
type of drive.
3. A controller can be almost anything. It could be a complete box that
accepts a paper tape and sends signals to the motor coils. Or, it could be a
'black box' that fits between the printer port and the high current circuits
that actually drive a motor.
In another message, Tim Goldstein wrote:
"For the purposes of a step and direction system (steppers and servos
like Gecko G3x0) a controller is the software package your run on the PC
that reads G-code and outputs step and direction signals via the PC
parallel port (Mach1, TurboCNC, etc.) or it's own dedicated external box
(DeskCNC, Flashcut, etc.)."
I would normally call this software packge the 'G-Code interpreter'
-- Jerry
|
|I'm sorry but I'm still not "getting" one thing and I hope someone
|can help.
|
|The difference between a DRIVER and a CONTROLLER.
Discussion Thread
volitan712003 <volitan@o...
2002-12-08 09:33:30 UTC
Driver / Controller
Tim Goldstein
2002-12-08 09:51:48 UTC
RE: [CAD_CAM_EDM_DRO] Driver / Controller
Chris L
2002-12-08 10:32:29 UTC
Re: [CAD_CAM_EDM_DRO] Driver / Controller
jeffalanp <xylotex@h...
2002-12-08 11:14:55 UTC
Re: Driver / Controller
Jens Swales <jipeess2000@y...
2002-12-08 14:51:08 UTC
Re: Driver / Controller (Chris L)
Chris L
2002-12-08 16:10:24 UTC
Re: [CAD_CAM_EDM_DRO] Re: Driver / Controller (Chris L)
Carol & Jerry Jankura
2002-12-08 16:16:50 UTC
RE: [CAD_CAM_EDM_DRO] Driver / Controller
volitan712003 <volitan@o...
2002-12-08 17:48:51 UTC
Re: Driver / Controller
Matt Shaver
2002-12-08 22:03:57 UTC
Re: [CAD_CAM_EDM_DRO] Driver / Controller
natchamp_87 <mark@h...
2002-12-08 23:12:29 UTC
Re: Driver / Controller
James Cullins
2002-12-09 06:33:14 UTC
Re: [CAD_CAM_EDM_DRO] Driver / Controller
timgoldstein <timg@k...
2002-12-09 07:52:02 UTC
Re: Driver / Controller
bjammin@i...
2002-12-09 08:15:21 UTC
Re: [CAD_CAM_EDM_DRO] Re: Driver / Controller
Ray Henry
2002-12-09 10:21:42 UTC
Re: Re: Driver / Controller
Ray Henry
2002-12-09 10:21:45 UTC
Re: Re: Driver / Controller
James Cullins
2002-12-09 12:08:18 UTC
Re: [CAD_CAM_EDM_DRO] Re: Driver / Controller
James Cullins
2002-12-09 12:08:27 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: Driver / Controller
CL
2002-12-10 05:58:12 UTC
Re: [CAD_CAM_EDM_DRO] Driver / Controller
Jon Elson
2002-12-10 10:14:49 UTC
Re: [CAD_CAM_EDM_DRO] Driver / Controller
Jens Swales <jipeess2000@y...
2002-12-10 13:44:27 UTC
Re: Driver / Controller (Chris L)
Chris L
2002-12-10 20:16:01 UTC
Re: [CAD_CAM_EDM_DRO] Re: Driver / Controller (Chris L)