Fusion 360 post issues (maybe?) on 2 axis lathe conversion

andypugh wrote:

You do need a spindle-speed-in for G95 to work.

You probably don't need a simulated encoder to achieve this. You can just connect spindle.0.speed-out to spindle.0.speed in in the HAL.

But, it would be much better to have an actual spindle encoder. There are many ways to get one set up, including using a gear in the head and a gear tooth sensor.



Thanks will try that hal code. Planning on adding an encoder soon just wanted to see movement and cut a few parts to test out the steppers.  

That worked great thanks! Was able to run the part I needed for another project.


Few more questions
Any issues with a single encoder, thinking of using an induction sensor to read the three chuck holes. I could read a gear if needed but not sure what would be a good sensor for doing so.

What is the recommended interface these days? I used gmoccapy for plasma a few years ago and it's OK for lathe but not great. The new qtplasmac interface is great for plasma but don't see a lathe version yet.

Does anyone use touch probes for setting tools? If so any recommendations?


Thanks for the help!

Ideally you need pulse and index. You can do it with a single sensor and a missing tooth, but then you probably don't want to remove a tooth from the gears in your lathe headstock. (When cars use a "missing tooth" it is actually a slightly shorter tooth, which still drives)

For sensing gear teeth the ATS667 sensor has been used by a number of LinuxCNC folks. Though there are many other options out there, including housed versions for e-bikes.
Some car parts are very cheap, but I don't know if they need a magnetised wheel to work:
www.autodoc.co.uk/dakatec/15730222
But those are also quite cheap:
www.autodoc.co.uk/corteco/13842295

ATS667 onto a gear for pulse and one more on a bolt or keyway for index is more tried-and-tested though.