VMC related HAL questions.

It complains that "spindle-pos-cmd" is float and or2 wants bit.

thewho wrote: It complains that "spindle-pos-cmd" is float and or2 wants bit.

Sorry, yes.
I should have used the orient-mode and position-mode signals.

I just stood by the machine doing G33.1 over and over with my mouth wide open :woohoo:
I can't thank you enough Andy!
The spindle encoder was apparently not connected correct, but with a little hal-scoping i figured out that index and A was inverted. Quick fix and then it worked! :laugh:

A question though, when I write M19 in MDI mode nothing happens. Do i need to specify the R,Q,P parameters or is there something else?

thewho wrote: A question though, when I write M19 in MDI mode nothing happens. Do i need to specify the R,Q,P parameters or is there something else?

It should work.

Time to check things out with the HAL tools. Try opening "show hal config" and selecting the watch tab, then adding the motion.spindle-orient, the orient component pins, the angle, hm2_5i25.0.7i77.0.1.spinena, the PID inputs and outputs and enable, etc

I can't get pid.1 (position) to react.
"Motion.spindle-is-oriented" is always lit, that can't be right?

thewho wrote: I can't get pid.1 (position) to react.
"Motion.spindle-is-oriented" is always lit, that can't be right?

No, that is likely to be the problem.

The issue here is one of calculation order. The near.0 calculation is happening before the orient component can calculate a new position, so the motion system gets the signal that orient is over before it even begins.

The best solution is to use a different version of "orient" that I have written which outputs a pin to drive motion.spindle-is-oriented.

For testing just comment-out the line
But the best solution is to comp --install the modified orient component, remove all references to near.0 and have