On Tuesday 18 November 2014 08:10:26 Mark Wendt did opine And Gene did reply: > On Tue, Nov 18, 2014 at 7:42 AM, andy pugh <[email protected]> wrote: > > On 18 November 2014 12:26, Mark Wendt <[email protected]> wrote: > > > Ah, then, I guess it may or may not work for me. My table is 55" > > > long, > > > > and > > > > > my G Code is written for a Z station for every inch of X station. > > > Back > > > > to > > > > > the probekins I guess. > > > > I think lincurve will probably work better in your case. Probekins is > > likely to be confused by your lack of Y. > > 16 points lets you define quite a complicated shape. > > > > -- > > atp > > If you can't fix it, you don't own it. > > http://www.ifixit.com/Manifesto > > Andy, > > I'm still trying to figure out how, on my machine without a moveable Y > axis (in other words, since I have no real Y axis movement - the > gantry just moves along the X axis and the Z axis goes up or down), do > I still need to have a Y coordinate on the setp line? > > Also based on your example (i've probably got this incorrect): > > setp X1 V1 > setp Y1 V1 > > Is the V number the Z offset? How does that get passed to the Z axis?
With the offset function also linked to in one of the replies here. "man 9 offset" should get you that page. Motion will output a new x position value every millisecond in most setups. Fed to lincurve, it will then output a + or - that you would apply by feeding motions z position into a sum2 module, with the other input to the sum2 coming from this Y(output) value from the lincurve module. The end result being that your z value passed to the stepgen is tickled enough to get what you want, following the curves you setp it to. The offset module would essentially be doing what I just suggested using a sum2 for, but offset may have some other features that are desirable too. OTOH a sum2 module is quite versatile too. Need a fp invertor? setp the gain of that input to -1.000. Done. Its confusing that the modules setp syntax uses x and y, they are just arbitrary names for the in value (x) where this output (y) corresponds to. It actually has only 1 input, and only 1 output. And it traces it literally on a thousandth or less of travel per correction value output. Your machine doesn't have a y, and thats confusing. Blocking the visualization of what is going on as it were. Nothing should prevent you from using arbitrary x location values to change the curvature of the cut to get precisely what you want, where you want it. I believe you could probably trace this to see it with halscope, probably with motor power off so you can simulate machine motion fast enough to be able to see the whole resultant curve in halscope. Halscope does have its limits when looking at slow speed stuffs. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
