Attached is block diagram showing a spindle orient example. I also attached the hal netlist.PID, limit2, offset, … etc parameters values are not complete, you will need to figure them out as you experiment.
@Benb -
Thank you for the comments.
I already have orient working on my subspindle, and
generally understand how it works and fits with other LCNC functions.
The problem with trying to combine orient with caxis.comp (attached in the first post) is that the caxis.comp functions are 'in charge' of the spindle motor at all times, except when a spindle-on command is issued. When the spindle is stopped, C-axis takes over and the PID ferror returns the spindle position to the last position prior to the M3/M4.
I don't know this for a fact, but I think what would happen is a race condition where once the spindle-off signal is triggered, but before orient.comp is engaged, caxis.comp will 'take over' the spindle and return it to the original position.
Meaning orient.comp wouldn't be useful to get the spindle close enough after freewheeling and before re-engaging the c-axis.
If Aciera's unhoming python comp doesn't work, and PCW's doesn't either, I will likely revisit orient.comp.
