2 steppers on one axis 5i25 - 7i76

any idea what I am doing wrong?

Todd Zuercher wrote:

rodw wrote: Other idiots build from source.....

I don't know if I'd call them idiots, masochists maybe but not idiots.

Ahh one of the real gurus reports in....
I only compiled from source because after compiling the linux kernel to get my mesa ethernet hardware working, it was so trivial by comparison. It's been a great learning experience.

Do you have any ideas on making both joints respond to the Y button in unhomed mode, or is that not possible?

I don't remember ever seeing them try to move other than in unison. I mostly use Gmoccappy but I do have some axis configs. I just hit home all as I power up becasue usually an unhomed axis won't jog to where I want it to ss it thinks its in a different place. I just had a play then and Both joints move in unison when jogging Y when unhomed from the Axis GUI and my Mesa MPG.

rodw wrote: I just had a play then and Both joints move in unison when jogging Y when unhomed from the Axis GUI and my Mesa MPG.

Its possible that a new version of master has fixed this behaviour as I found a few bugs in homing on Gmoccappy that Norbert fixed and there was a bit of a flurry on some of the other GUIs after the problems I raised were noted.

chadrat6458 wrote: any idea what I am doing wrong?

Try from the Synaptics GUI. Check the deb settings there first. So long ago since I did it. (I just type make)

chadrat6458 wrote: I still can't get one of the steppers to move. I have attached the hal and ini file.

I definately see an error.

look for this line in the Y axis:

net y-pos-cmd => hm2_5i25.0.stepgen.01.position-cmd

change it to:

net y-output <= hm2_5i25.0.stepgen.01.velocity-cmd

i bet you see movement then (hopefully good movement)

Chris M

Now, I am confused. Do I make the change mentioned above or do the joints?