Re: Adding a DAC, DRO wrapping


Hi Chris

I for one would love to see such code added.  I have seen offers to drill
and etch pc boards for $50 or so, and don't think the chips are that much:
dac's or pwm & encoders + a fpga for glue.  The Dallas Personal Robotics
group(dprg- http://www.dprg.org) has a project page that describes 2
H-bridges that don't look that hard to build.

My personal dream would be a chip like ADMC401(see attach.).  This motor
control chip has a encoder and pwm and dac plus can run almost any motor
made even ac.

So yes include code.  If noone else wants it, I sure do.  

charly

  
>
>I guess my basic questions are - am I duplicating work others have
>already done?  Or is this code worth trying to clean up and eventually
>figuring out how to contribute to the cvs tree?  
>
>Also, would it make sense to have a generic 'model' driver for a DAC
>that people could easily modify for various boards?  Part of the
>complicaton of adding a new driver is putting it in the half dozen
>places in the emcmot/Makefile, and making sure the resulting module is
>mentioned in emc.run so it can get loaded and unloaded.  It would be
>nice to have either instructions or a script for doing this, or simply
>a prototype driver (something like myservo.o) that had all the
>necessary files and was mentioned in the right places, so that people
>could simply edit their particular outb's and inb's into the source
>file, rebuild, and run.  (This is essentially what I did at first
>time, hacking up the stg driver, but that didn't seem very clean, so I
>built a new module).
>
>Oh, one more question: what are the units for the MAX_VELOCITY in the
>.ini file?  Is this the velocity for G0 rapids?
>
>Chris
>
>-- 
>Christopher C. Stratton, stratton-at-mdc.net
>Instrument Maker, Horn Player & Engineer
>22 Adrian Street, Somerville, MA 02143
>http://www.mdc.net/~stratton
>NEW PHONE NUMBER: (617) 628-1062 home, 253-2606 MIT
>
>
>
>
>
>

ADMC401_b.gif




Date Index | Thread Index | Back to archive index | Back to Mailing List Page

Problems or questions? Contact