M19 spindle orient

Todd Wrote:-
Why not set the encoder scale for the hardware encoder counter for your 360 degrees, then use a scale component on the position output by encoder counter to get your per rev number?

I thought it would be easier to leave the hardware encoder alone for speed measurement, then use separate software encoders for the orient part. I found it very difficult to understand the orient process. Finding the correct float to connect to the orient pins took ages.
I can see a scale component would be better for getting the rev number.
Would using a software encoder cause any problems?. The orient process would be very slow compared to spindle speed counting, so the software encoder should be fast enough.

There is absolutely no reason (or advantage) to using multiple software encoder counters to read a single encoder. The hardware encoder has both position and velocity outputs, and those outputs values can be sent to multiple inputs and the hardware encoder can reliably count pulses many, many, many times faster and more reliably than can the software encoder (which would have to read pulses in the servo-thread.)

Thanks for the explanation. I've re drawn the schematic for a hardware encoder only, it looks much tidier. The only complication I can see is I will need to turn off the encoder reset when not using orient, but I've found a way to do that.

Here is the orient schematic with hardware encoder only. Seems to work ok.

raglanlittlejohn thanks !
Does this circuit work on a real machine ?
I'll try

I've got all the electronics connected up and working,ready to fit to a lathe. This orient part works as it should. The PID varies the commanded speed to the motor as expected. The closer the motor gets to its final position, the slower it's commanded to go.
I've only got an older style VFD, and it wont respond as quickly as I'd like for accurate orient positioning. I'm trying to find out if a new vector type VFD would be better.
Good luck with your project.