Re: [Emc-users] G code problem with G95

2012-10-24 Thread Matt Shaver
On Sun, 21 Oct 2012 11:40:15 -0500 Chris Radek ch...@timeguy.com wrote: G76 uses spindle position (spindle-revs). G95/G96 use spindle velocity (spindle-speed-in). Are you sure you've hooked up both? See the motion.spindle* section of http://linuxcnc.org/docs/html/man/man9/motion.9.html

Re: [Emc-users] G code problem with G95

2012-10-21 Thread Matt Shaver
On Sat, 20 Oct 2012 20:44:02 -0500 ed ate...@mwt.net wrote: Finally got my Hardinge CHNC lathe up and mostly running and am having a problem. Do you simply put G95 on a line then on the next G1 make sure there is a F feedrate per rev? What ever I try the prog stops with the spindle running

Re: [Emc-users] G code problem with G95

2012-10-21 Thread ed
Matt Shaver wrote: On Sat, 20 Oct 2012 20:44:02 -0500 ed ate...@mwt.net wrote: Finally got my Hardinge CHNC lathe up and mostly running and am having a problem. Do you simply put G95 on a line then on the next G1 make sure there is a F feedrate per rev? What ever I try the prog stops

Re: [Emc-users] G code problem with G95

2012-10-21 Thread jeremy youngs
I don't think the spindle encoder is relevant unless you have closed loop spindle control. My guess is it only looks at the S word rpm's to calculate feed rate. then how would it know where to index the cut at? -- jeremy youngs

Re: [Emc-users] G code problem with G95

2012-10-21 Thread Chris Radek
On Sun, Oct 21, 2012 at 11:12:12AM -0400, Matt Shaver wrote: Thanks for confirming what I have been thinking - That G95 is broken somehow. I consult for Smithy who sells CNC lathes with Linuxcnc control, and our lathe customers report this same behavior. Interestingly G76 threading works OK,

Re: [Emc-users] G code problem with G95

2012-10-21 Thread Chris Radek
On Sun, Oct 21, 2012 at 11:26:52AM -0500, ed wrote: I don't think the spindle encoder is relevant unless you have closed loop spindle control. My guess is it only looks at the S word rpm's to calculate feed rate. Your guess is incorrect - thanks for labeling it as a guess, so as not to

Re: [Emc-users] G code problem with G95

2012-10-21 Thread Chris Radek
On Sun, Oct 21, 2012 at 12:31:26PM -0400, jeremy youngs wrote: I don't think the spindle encoder is relevant unless you have closed loop spindle control. My guess is it only looks at the S word rpm's to calculate feed rate. then how would it know where to index the cut at? G95 is not used

Re: [Emc-users] G code problem with G95

2012-10-21 Thread andy pugh
On 21 October 2012 16:12, Matt Shaver m...@mattshaver.com wrote: Thanks for confirming what I have been thinking - That G95 is broken somehow. My lathe was running 2.5, and G95 worked as expected. Deleting the link to motion.spindle-speed-in stopped it working, however. I then upgraded to

Re: [Emc-users] G code problem with G95

2012-10-21 Thread ed
andy pugh wrote: On 21 October 2012 16:12, Matt Shaver m...@mattshaver.com wrote: Thanks for confirming what I have been thinking - That G95 is broken somehow. My lathe was running 2.5, and G95 worked as expected. Deleting the link to motion.spindle-speed-in stopped it working,

Re: [Emc-users] G code problem with G95

2012-10-21 Thread andy pugh
On 21 October 2012 19:43, ed ate...@mwt.net wrote: I am running 2.51 at this time. Could you tell what the links are? http://www.linuxcnc.org/docs/2.4/html/examples_spindle.html#sec:Spindle-Synchronized-Motion You need to link motion.spindle-speed-in to something (possibly

[Emc-users] G code problem with G95

2012-10-20 Thread ed
Finally got my Hardinge CHNC lathe up and mostly running and am having a problem. Do you simply put G95 on a line then on the next G1 make sure there is a F feedrate per rev? What ever I try the prog stops with the spindle running on the first G1 line. Baffling. Maybe someone has a small