Hi all, I made my first attempt at using spindle synchronized motion for a rigid tapping operation on my Bridgeport BOSS mill today and it didn’t go as planned. It has a spindle encoder and a Pico USC board. I can use the spindle to read encoder counts and spindle position (I already use PYVCP to show me spindle speed). However, G33.1 produces unusual results and doesn’t seem to work properly. It appears that the down feed works properly, but the spindle either never reverses or reverses very slowly and the synchronized motion on retract doesn’t appear to reliably track the spindle motion. In several tests, it either retracts while still turning clockwise, appears to retract faster than the counter-clockwise speed would allow, or just doesn’t retract at all. According to the g code reference page, motion.spindle-at-speed and encoder.n.phase-Z must be connected in HAL. I don’t have spindle-at-speed hooked up, but am using rigid tapping sample HAL from Pico Systems, with the encoder connected to motion.spindle-revs.
I attempted to troubleshoot using this references: https://forum.linuxcnc.org/27-driver-boards/26275-spindle-encoder-on-pico-usc <https://forum.linuxcnc.org/27-driver-boards/26275-spindle-encoder-on-pico-usc> I ran a halcmd sets on the spindle index enable and it reset counts to zero immediately. spindle index enable remained false and fiddling with halscope wasn’t ever successful in showing a change from false to true while playing with G33 commands, etc. I’m not sure what to try next. Thanks! Matt _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
