On 03/22/2018 05:08 PM, andy pugh wrote:
On 22 March 2018 at 19:36, Mark <wendt.m...@gmail.com> wrote:
Since the X axis hasn't moved, and the lincurve values for the X axis at
zero are this:
setp lincurve.0.x-val-00 0
setp lincurve.0.y-val-00 0.000
It should have a 0.000 output.
It should have, yes. But I think you should check with halmeter to be sure.
Okey dokey.
I think something is missing here. That would be the either the
axis.0.motor-pos-cmd or axis.1.motor-pos-cmd feeding lincurve.0.in the
actual X axis position. This might be a little tricky since I have the two
drives slaved as the X axis like this:
net ypos-cmd axis.1.motor-pos-cmd => axis.1.motor-pos-fb
net xpos-cmd axis.0.motor-pos-cmd => stepgen.0.position-cmd
stepgen.1.position-cmd
Would I net lincurve.9.in to xpos-cmd or ypos-cmd? Or would I net to
something else?
xpos-cmd, I think.
does ypos-cmd actually go to a stepgen? It seems rather redundant.
ypos-cmd is for the slaved driver. I think the axis.1.motor-pos-fb is
fed back in on a different net. I'll give the xpos-cmd a whirl and see
if it makes it work.
Mark
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
