Lathe Rigid tapping G33.1 with tailstock as W axis

More
6 years 9 months ago - 6 years 9 months ago #154422 by andypugh

alkabal wrote: I not fully understand what you think is the best :
1-change all the needed source code for allow to use G33.1
2-change all the needed source code for adding something like G33.2 (i think need the other change like for G33.1 but surely better to separate)
3-do something with remap


It depends if you want to fix it for everyone and change LinuxCNC or just make your machine work.

To fix it for yourself only, the simplest thing is to use the Y axis for the tailstock.

To fix it for yourself only and to keep the preview looking good, making a remapped G33.n is the way to go (you can't remap G33.1)
linuxcnc.org/docs/2.7/html/remap/remap.html
Amongst a lot of other info, this shows that G33.2 is available.
You could remap this in G-code to something like:
In the INI
Code:
[RS274NGC] REMAP=G33.2 argspec=uvw ngc=myridgidtap


then create a file "myrigidtap.ngc"
Code:
O<myrigidtap> SUB (store starting UVW) (note that at this point #<w> is the W-word from the G33.2 command, and #<_w> is the current W position) #1 = #<_u> #2 = #<_v> #3 = #<_w> G33 U#<u> V#<v> W#<w> (reverse the spindle) M4 G33 U#1 V#2 W#3 {spindle back to forwards) O<myrigidtap> ENDSUB M2

But if you want to fix it for everyone, then that involves changes to the LinuxCNC source code. And spindle-synched motion is one of the more complicated parts.
Last edit: 6 years 9 months ago by andypugh.

Please Log in or Create an account to join the conversation.

More
6 years 9 months ago - 6 years 9 months ago #154428 by alkabal
Top, i check this remap soon, a lot of thanks

Really i like to change source for everyone i(f this something possible to merge and keep logic) but for now i can't compile correctly, and you think in all way add a G33.2 is better vs only update the G33.1 source code ?

Br
Last edit: 6 years 9 months ago by alkabal.

Please Log in or Create an account to join the conversation.

More
6 years 9 months ago #154431 by andypugh
The best solution would be to extend G33.1 to all axes. (you can imagine using a rotary axis to cut a partial worm sector.....)
But it looks like that would be a significant undertaking.

Please Log in or Create an account to join the conversation.

More
6 years 9 months ago #154440 by alkabal
For now remapping does not work fine :
W is 0
Ask G33.2 W-5 K1 S50 (spindle speed for M3 M4 inside remap)
The initial move is ok, stopping after 5 full spindle revolution (by hand)
the retract wait 5 backwards spindle revolution before start the synchronised move.
I’m afraid about overrun after the initial move if the spindle does not reverse instantly. (I have see something about over range or something like this in the source code)

Br

Please Log in or Create an account to join the conversation.

More
6 years 9 months ago #154444 by andypugh

alkabal wrote: For now remapping does not work fine :
The initial move is ok, stopping after 5 full spindle revolution (by hand)
the retract wait 5 backwards spindle revolution before start the synchronised move.


Ah, that is definitely no good. I might have led you down a blind alley here.
Sorry.

Please Log in or Create an account to join the conversation.

More
6 years 9 months ago - 6 years 9 months ago #154449 by alkabal
Lol do not worried this is a great attempt.

I will try to continu patching the G33.1

If no success maybee keep the config with Y axis the easy way.

Thanks you
Last edit: 6 years 9 months ago by alkabal.

Please Log in or Create an account to join the conversation.

Time to create page: 0.340 seconds
Powered by Kunena Forum