G33.1 right hand tapping weird behavior H E L P !

Hi,
i am almost finished with my bridgeport retrofit now at training stage i found out that G33.1 (because i normally don't use it ) doesn't behave as it should.

i have also prepared an python drill script generator which i donate when we solve that -

So i go to lets say g0 x0 y0 z0.5
S200 M3
G33.1 Z-3 K1.5

i would expect that it does go down to Z-3 in the needed speed to achieve 1.5 per revolution
so far so good (i looks that i have a glitch from motor to spindle it is a 1:2 ratio but ,.. )
so i use a bigger number in K to achieve the ratio )

but when the system reaches Z-3 it reverses the spindle also ok
but then it proceeds i stopped it then at Z-30

so has anyone seen that behavior and how can i check what i probably have done wrong ?

or if someone has an Working G84 script which i can remap would also help a lot

i use now the latest live cd and do updates
so any hint welcome
thx
thomas kamsker

tkamsker wrote: but when the system reaches Z-3 it reverses the spindle also ok
but then it proceeds i stopped it then at Z-30 /quote]

Does your spindle encoder definitely count both up and down? It sounds to me like you might be in counter-mode and the system thinks that the spindle is still moving in the same direction.

Hi andy,
Thank you for the fast answer
i think the encoder can not count backwards because i only have Z and A signal on the same pin
i thought because of the reverse spindle it should "know" that it is backwards.

Is there any known configuration which makes this possible or do i have to mount an B signal 90° from the A signal ?

this is something we could manage would that help ?
i then would have A and Index on one signal and B on an 2nd 90° apart

thomas

tkamsker wrote: i thought because of the reverse spindle it should "know" that it is backwards.
Is there any known configuration which makes this possible or do i have to mount an B signal 90° from the A signal ?

Just because a spindle reversal has been requested does not mean that the spindle has actually changed direction.
I am afraid that there probably is no alternative to adding a second sensor.
It doesn't have to be at 90 degrees, 360+90 or 720+90 etc all work too.

Hi andy
i now build an 2nd Probe to my config and can get some better insights
My question which values does the 33 command take in consideration ?


This is an example where i have 201 as RPM and 3,35 as Rev/Sek

And when i turn the direction i is negative
Is that correct ?
Is there an example to work from ?
thx
thomas

tkamsker wrote: My question which values does the 33 command take in consideration ?

G33 uses the value of motion.spindle-revs (revolutions, not rpm)

You need to set up the encoder scale so that one rotation clockwise of the spindle gives an increase of exactly 1.0 in motion.spindle-revs and one rotation anticlockwise makes it _reduce_ by exactly 1.0.