[Timbob]

Yes. I'll get my settings for you so you can compare, but it might be later.

I used the canned cycle now. When I first started threading, I used the "expanded" code to see specifically what each increment was. That got old real fast!!

Interesting tidbit that I discovered: if you set the cut per pass too small, and the number of passes, start to completion, exceeds 200, on pass #200, Mach just cuts whatever is left over. It is actually possible to do this since the per pass cut can be calculated as volume based on the first pass. The things you learn when you do stupid things!!

[Shrimp]

Yes. I'll get my settings for you so you can compare, but it might be later.

I used the canned cycle now. When I first started threading, I used the "expanded" code to see specifically what each increment was. That got old real fast!!

Interesting tidbit that I discovered: if you set the cut per pass too small, and the number of passes, start to completion, exceeds 200, on pass #200, Mach just cuts whatever is left over. It is actually possible to do this since the per pass cut can be calculated as volume based on the first pass. The things you learn when you do stupid things!!

Awesome, that would be a huge help. If you can just use Alt + Print Screen and post those screenshots. I have a feeling maybe I don't have some type of input enabled and that's why my program stops when it gets to the canned cycle. It's waiting for some type of index signal on the spindle.