On Wednesday 08 October 2014 08:19:52 andy pugh did opine And Gene did reply: > Looking through the source, emcannon.hh > > 423 extern void STRAIGHT_PROBE(int lineno, > 424 double x, double y, double z, > 425 double a, double b, double c, > 426 double u, double v, double w, unsigned > char probe_type); > 427 > 428 /* Perform a probing operation. This is a temporary addition to the > 429 canonical machining functions and its semantics are not defined. > 430 When the operation is finished, all axes should be back where they > 431 started. */ > > Is there a chance that probing will disappear?
I sure hope not, I've found it as handy as bottled beer. But the comment about winding back up at the starting co-ordinates obviously does not apply. Or am I confused about the context of this? My thinking, when probing is mentioned, is the G38.n family of canned moves. I do things with the direct from #5xxx memory results that are very handy when needed. 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 ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
