Re: Driver / Controller

Hello David,
The Xylotex stepper DRIVER (is not a controller) accepts step &
dir signals from a CONTROLLER (like a PC running Mach1 or Master 5)
as in this example:

> PC -> Driver -> Stepper

PC(Mach1) -> Xylotex-> Vexta

Alternatively you could also have a system where a PC does
coordinated motion calulations, and sends individual motion commands
to a CONTROLLER (through serial, USB, parallel ports). This
CONTROLLER carries out proper pulsing of the stepper DRIVER:

> PC -> Controller -> Driver -> Stepper
> PC(DeskCNC) -> DeskCNC -> Xylotex -> Vexta

Some stand alone packages could have both. Such a system
(controller & driver) would, for example, get an index signal. This
would cause the CONTROLLER to calculate the proper number of pulses
to be sent to the DRIVER, to cause the proper motion on the stepper
motor. Such a system would very often be used in indexing a 4th axis
(usualy rotary axis) where the main system is only capable of
handling 3 axes.

> Index signal -> Controller & Driver -> Vexta

Jeff
www.xylotex.com


--- In CAD_CAM_EDM_DRO@yahoogroups.com, "volitan712003
<volitan@o...>" <volitan@o...> wrote:

> 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.
>
> For example, if one of you experienced people were to buy something
> like this cool looking thing:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?
> ViewItem&category=25286&item=1923982111&rd=1
>
> You'd notice that it clearly states: "Pack Driver - Stepping Motor
> Driver"
>
> Would you then expect to hook a controller up to this? Or would you
> expect to make a cable from your PC right to the Pack Driver unit?
>
> PC -> Controller -> Driver -> Stepper
>
> or
>
> PC -> Driver -> Stepper
>
> I don't know why I can't get my head around this, is sounds fairly
> straightforward.
>
> Also, would the Xylotex units be considered a controller and a

driver

> in one?
>
> Thanks
> David