Re: Using DRO data for feedback

[Allen <allenf-at-choice.net>]

Weyland wrote:
> 
> That worked~!
> Thanks Allen~!!
> Man, it scrolled line after line for like 25 minutes, maybe 35 minutes.
> (I finally walked away)
> 
> Okay, so now I've done my first compile?
> Well, here's what I got -
> Went back and checked the dro.c file, and
> sure enough, that line you told me take out was back,
> so I edited it out again.
> 
> Now, the problems -
> emc-sim runs, but I still get no encoder feedback.
> emc-generic runs, but no feedback.
> emc-mini won't even run after clicking it.
> emc-run gives the popimage, but never comes up after that.
> 
> What'd I do wrong?

Well I don't know what went wrong, but I'll
outline the steps and then some.

1. Remove the line that reads "#define extern" from
the dro.c file located in /usr/local/emc/src/emcmot

2. Next run the BDI_build script to recompile.

3. edit the Tkemc file located in
/usr/local/emc/plat/linux_2_2_18/bin.
Change all references of linux_2_2_17 to linux_2_2_18.
Emc-run will not work until this is done.
I can't speak about the other icons as I only use emc-run.

4. Edit your emc.ini file.
Type in if needed "EMCMOT=smdromod.o" and make it the
active motion program in the EMCMOT section.
In each axis section, set the input and output scale. 
Input scale = encoder counts per 1 inch
Outputs scale = stepper motor counts per 1 inch

You are close Weyland.

Before I ran smdromod I ran freqmod and got my
motors tuned first. smdromod uses freqmod in
its code. That eliminates most tuning issues
if you have problems when switching over to
smdromod. Pretty much you can figure it's an
encoder problem or input scale setting.

Regards,
Allen