On Sunday 27 July 2014 06:55:04 andy pugh did opine And Gene did reply: > On 27 July 2014 05:58, Gene Heskett <[email protected]> wrote: > >> Does the code depend on a parameter that isn't set at program load > >> time? > > > > Well, for the G76 code, you do need quite a few parameters, but the > > only ones set at program load time are the Zstart, Zend, TPI or TPmm > > and the OD of the thread. > > It isn't that, then. The values are right there in the code. > > I have had strange behaviour when values are pulled in from the G-code > "analogue inputs" which may not have any value at the time that the > G-code it loaded. > (In 2.6 this gets much neater, my thread cutting macro now uses lines > like this: #4 = #<_hal[gladevcp.thread.pitch-f]> (Feed / Pitch) > To pull values into G-code direct from HAL.
Neat! > I will comment that metric threads are not specified by threads-per-mm > so I think you have a bogus pitch calculation going on. I've cut several metric threads using that line of code, seemed to have worked as the 8mm purchased nuts fit well. But you raise a point I may have missed, so in the interests of doing it right, how are metric threads specified? 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 ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
