Thanks, I hadn't seen it -- that's pretty much what I had in mind for probing.
What I'd like is the ability to save data after probing and to recall it as needed. To do that, I need to be able to save the coordinates of a point when it is probed. So, I probe the center of a circle and the probe routine saves the point. Now I want to create a five hole pattern where a second point defines where the first hole is. OK, I probe that point. Now, how do I tell the pattern routine to use the first point as the center and the second as the first hole? What I would do is keep track of the last N points that were probed. (Or calculated from other probed points, or jogged to points, or whatever.) It would store them in a stack. Then my library of routines would use some of the items on the stack. So, My hole pattern routine would use the top of the stack as the center and the next item on the stack as the origin. If I probed them in the wrong order, I would just run a command (by pushing a button) that executed a MDI routine that swapped the top two items on the stack. I can do all of this stuff. The question though is how do I display the contents of the probe stack. There doesn't seem to be a path for gcode to send parameter values to PYVCP (or alternatively, for PYVCP to request them from the interpreter.) My most recent idea is to have the gcode log (using the "LOG" comment form) relevant parameters to a named pipe (It's not clear whether the interpreter will permit the output file to be a named pipe.) The some python code (in a glade environment) could read the same pipe. I'm looking for a way to do this with minimal effort. Ken On Fri, Jun 12, 2015 at 9:05 AM, Marius Liebenberg <[email protected]> wrote: > Dont know why but the link does not show. Here it is again > > https://github.com/verser-git/probe_screen > > > > >Hi Ken > >Did you have a look at this already? > > > > Probe screen for linuxcnc > > > > > > > >------ Original Message ------ > >From: "Kenneth Lerman" <[email protected]> > >To: [email protected] > >Sent: 2015-06-12 13:10:59 > >Subject: [Emc-developers] Can I Display Gcode Parameters in PYVCP? > > > >> > >>I think the answer is no. But perhaps someone can suggest a work > >>around > >>for what I want to do. > >> > >>I'd like to write some subroutines to be used interactively. For > >>example: > >> > >>Jog to position one. Hit a button in pyvcp labeled "enter". That will > >>run an mdi program that will save the current X in #<_pX0> and the > >>current Y in #<_pY0>. > >> > >>Jog to the the center of a circle. Hit a button in pyvcp labeled probe > >>circle. That will save the _pX0 and _pY0 variables in _PX1 and _PY1 (I > >>like RPN) and save the probed center of the circle in _pX0 and _pY0. > >> > >>Now hit a button labeled "circular pocket". The will use _pX0, _pY0 as > >>the center of a circle and _pX1, _PY1 as a point of the circle and > >>create a pocket. (let's not worry about depth right now -- we could > >>use > >>a slider for that.) > >> > >>All of this could work really nicely. The one fly in the ointment is > >>that I have to remember the contents of my stack -- the doesn't seem > >>to > >>be a way to display it. > >> > >>I'd like to add a bunch of routines for probing -- probe left, probe > >>right, probe lower left corner, probe upper right corner, ... Having > >>to > >>remember what is stored in which parameter is painful. > >> > >>In case anyone is wondering, I use my milling machine to build > >>prototypes; not for production. I just bought a probe and would like > >>to > >>build the infrastructure to work interactively. > >> > >>Any thoughts? > >> > >>Thanks, > >> > >>Ken > >> > >>-- > >>Kenneth Lerman > >>55 Main Street > >>Newtown, CT 06470 > >> > >> > > >>------------------------------------------------------------------------------ > >>_______________________________________________ > >>Emc-developers mailing list > >>[email protected] > >>https://lists.sourceforge.net/lists/listinfo/emc-developers > > >------------------------------------------------------------------------------ > >_______________________________________________ > >Emc-developers mailing list > >[email protected] > >https://lists.sourceforge.net/lists/listinfo/emc-developers > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > -- Kenneth Lerman 55 Main Street Newtown, CT 06470 ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
