Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-28 Thread David Bagby
On 7/28/2018 8:58 AM, Sebastian Kuzminsky wrote: On 07/27/2018 02:39 PM, Kurt Jacobson wrote: So the question is, why did LCNC choose to use relative positions for the probe parameters? There must be a good reason to not follow what seems to be a standard among other controllers, but the only

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-28 Thread andy pugh
On 28 July 2018 at 16:58, Sebastian Kuzminsky wrote: > I would prefer adding nine new Interpreter parameters containing the > *absolute* probe location, and adding a new field to the Status buffer > (and the 'stat' variable in the linuxcnc python module) containing the > probed position in *work

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-28 Thread Sebastian Kuzminsky
On 07/27/2018 02:39 PM, Kurt Jacobson wrote: > So the question is, why did LCNC choose to use relative positions for the > probe parameters? There must be a good reason to not follow what seems to > be a standard among other controllers, but the only advantage I can see is > when probing to

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Gene Heskett
On Friday 27 July 2018 21:15:03 Kurt Jacobson wrote: > On Fri, Jul 27, 2018 at 8:46 PM, andy pugh wrote: > > Good point. How about... > > > > G21 G91 > > G38.2 z-20 F80 > > G0 X#5061 Y#5062 Z#5063 > > G10 L20 P1 Z0 > > That would probably crash the probe, but a variant of that would work. > >

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Kurt Jacobson
On Fri, Jul 27, 2018 at 9:29 PM, andy pugh wrote: > On 28 July 2018 at 02:15, Kurt Jacobson wrote: > > >> Good point. How about... > >> > >> G21 G91 > >> G38.2 z-20 F80 > >> G0 X#5061 Y#5062 Z#5063 > >> G10 L20 P1 Z0 > >> > > > > That would probably crash the probe, > > Unless I am missing

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Jon Elson
Here's a routine I use that probes the "lower left" corner of a part. So, the probe is on the -X -Y corner. It backs away a little in -X and then quickly probes in the +X direction, then backs off and repeats at a much slower speed, and then sets #1001 to the offset between the probed position

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread andy pugh
On 28 July 2018 at 02:15, Kurt Jacobson wrote: >> Good point. How about... >> >> G21 G91 >> G38.2 z-20 F80 >> G0 X#5061 Y#5062 Z#5063 >> G10 L20 P1 Z0 >> > > That would probably crash the probe, Unless I am missing something, it should be a move back to the exact point where the probe tripped?

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Kurt Jacobson
On Fri, Jul 27, 2018 at 8:46 PM, andy pugh wrote: > Good point. How about... > > G21 G91 > G38.2 z-20 F80 > G0 X#5061 Y#5062 Z#5063 > G10 L20 P1 Z0 > That would probably crash the probe, but a variant of that would work. G21 G91 G38.2 z-20 F80 G0 Z[#5063 + .100] (move up a know amount from

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread andy pugh
On 28 July 2018 at 01:32, Kurt Jacobson wrote: > I have noticed several people using G10 L20 in their probing routines > (presumably because it is easy), but it is not at all correct. > > Here is a snippet taking from a probing routine: > ... > G21 G91 > G38.2 z-20 F80 > G10 L20 P1 Z0 > ... > >

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Kurt Jacobson
On Fri, Jul 27, 2018 at 6:02 PM, andy pugh wrote: > On 27 July 2018 at 21:39, Kurt Jacobson wrote: > > > There are significant advantages to having the probed pos be in ABS > > coordinates, mainly because it makes it easy to set a WCS to the probed > pos: > > > > G38.2 Z-.5 > > G10 L2 P0

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Gene Heskett
On Friday 27 July 2018 20:10:36 Kurt Jacobson wrote: > On Fri, Jul 27, 2018 at 5:12 PM, Gene Heskett wrote: > > Somewhere in the gcode is a pair of commands that switch it > > incremental<->absolute. Yes g90 for absolute, and g91 for > > incremental. Its also I think, switchable in the view

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Kurt Jacobson
On Fri, Jul 27, 2018 at 5:12 PM, Gene Heskett wrote: > Somewhere in the gcode is a pair of commands that switch it > incremental<->absolute. Yes g90 for absolute, and g91 for incremental. > Its also I think, switchable in the view pulldown. > > Does this not fix the g38.2 results too? > Gene,

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread andy pugh
On 27 July 2018 at 21:39, Kurt Jacobson wrote: > There are significant advantages to having the probed pos be in ABS > coordinates, mainly because it makes it easy to set a WCS to the probed pos: > > G38.2 Z-.5 > G10 L2 P0 Z[#5063] Is G10 L20 any help here? -- atp "A motorcycle is a bicycle

Re: [Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Gene Heskett
On Friday 27 July 2018 16:39:56 Kurt Jacobson wrote: > I asked this on IRC yesterday, but realize that was a bad format, so > here goes! > > I have been helping Lcvette with a very simple probing GUI and some > probing routines. The routines probes the top and then corner of the > part and set

[Emc-developers] Probe result parameters (5061-5069)

2018-07-27 Thread Kurt Jacobson
I asked this on IRC yesterday, but realize that was a bad format, so here goes! I have been helping Lcvette with a very simple probing GUI and some probing routines. The routines probes the top and then corner of the part and set the specified (not necessarily current) WCOs to the value of probed