Rigid Taping - DAC closed loop Spindle

[Mateusz]

Hi Tom,

I've got new issue regarding Gigid Tapping, kflop version 4.35f

I discovered that my Homing code Inhibits Rigid Tapping routine.

After INI machine, without homing, Rigid Tapping works, all the time for whole day...
After INI machine and making homing procedure, Rigid Tapping is invoked by M119, turns On Spindle Bits - but is not spinning and finishes cycle without any action. Jumps to another hole and again without any action...

To "get back" Rigid Tapping functionality I have to restart just Kflop Board.

Please see attached files

file RigidTapMultiPassJogM119_v2_Jim.c is called in Thread 6

Thanks
Mateusz

[TomKerekes]

Where is the Z axis coordinate before the Tap?

What GCode are you running?

What is printed on the when it works and what is printed when it doesn't?

[Mateusz]

Where is the Z axis coordinate before the Tap?

Z coordinate goes to Z2 over the hole and moves from hole to hole on the same high and finishes program on Z2 as well.

What GCode are you running?

(Call a Rigid Tap Sequence)
G21

F1000
S200
G1 X40 Y40
M7
G1 Z5
G99 G84 Z-6 R2 Q4 F1.5
X0 Y0
X60 Y70
G80
G0 X100 Y50
M9
M30

What is printed on the when it works and what is printed when it doesn't?

- When it doesn't tap:
Bottom = -6.000000
Retract = 2.000000
Peck = 4.000000
Pitch = 1.500000
RPM = 200.000000
Units = mm
Axis = 2
AxisRes = 254000.000000
Bottom = -0.236220 Inches
Retract = 0.078740 Inches
Peck = 0.157480 Inches
Pitch = 0.059055 Inches
Z0 = -1080000.000785 counts
Z0 = -4.251968 inches
Z_Dist = -4.015748 inches
Bottom = -6.000000
Retract = 2.000000
Peck = 4.000000
Pitch = 1.500000
RPM = 200.000000
Units = mm
Axis = 2
AxisRes = 254000.000000
Bottom = -0.236220 Inches
Retract = 0.078740 Inches
Peck = 0.157480 Inches
Pitch = 0.059055 Inches
Z0 = -1080000.000000 counts
Z0 = -4.251968 inches
Z_Dist = -4.015748 inches
Bottom = -6.000000
Retract = 2.000000
Peck = 4.000000
Pitch = 1.500000
RPM = 200.000000
Units = mm
Axis = 2
AxisRes = 254000.000000
Bottom = -0.236220 Inches
Retract = 0.078740 Inches
Peck = 0.157480 Inches
Pitch = 0.059055 Inches
Z0 = -1080000.000000 counts
Z0 = -4.251968 inches
Z_Dist = -4.015748 inches
Jogging Spindle Stop

- When it does tap:

Bottom = -6.000000
Retract = 2.000000
Peck = 4.000000
Pitch = 1.500000
RPM = 200.000000
Units = mm
Axis = 2
AxisRes = 254000.000000
Bottom = -0.236220 Inches
Retract = 0.078740 Inches
Peck = 0.157480 Inches
Pitch = 0.059055 Inches
Z0 = 19999.999215 counts
Z0 = 0.078740 inches
Z_Dist = 0.314961 inches
TotalCut = 0.000000 inches
TotalCut = 0.157480 inches
Bottom = -6.000000
Retract = 2.000000
Peck = 4.000000
Pitch = 1.500000
RPM = 200.000000
Units = mm
Axis = 2
AxisRes = 254000.000000
Bottom = -0.236220 Inches
Retract = 0.078740 Inches
Peck = 0.157480 Inches
Pitch = 0.059055 Inches
Z0 = 20000.000000 counts
Z0 = 0.078740 inches
Z_Dist = 0.314961 inches
TotalCut = 0.000000 inches
TotalCut = 0.157480 inches
Bottom = -6.000000
Retract = 2.000000
Peck = 4.000000
Pitch = 1.500000
RPM = 200.000000
Units = mm
Axis = 2
AxisRes = 254000.000000
Bottom = -0.236220 Inches
Retract = 0.078740 Inches
Peck = 0.157480 Inches
Pitch = 0.059055 Inches
Z0 = 20000.000000 counts
Z0 = 0.078740 inches
Z_Dist = 0.314961 inches
TotalCut = 0.000000 inches
TotalCut = 0.157480 inches
Jogging Spindle Stop

[Mateusz]

Hello Tom,

I think I know what is going on, but I'm not able to fix this bug,
I'm working on RawMAchineCoordinates OFF, XYZ are set to Gcode value, everything is positioning to proper distance a part of Z parameter in G84. For example:
- having code G84 Z-6 R2 Q4 F1.5 machine will go to Z-6mm but in RawMachineCoordinates not to GCode coordinates displayed on the screen. In that case, when I'm below negative value = -6 with RawMachineCoordinates limit, command G84 is refusing to go deeper. I hope this is clear.


Regards
Mateusz

[TomKerekes]

Hi Mateusz,

Thanks for pointing that out. I see a mixed use of GCode and Machine Coordinates. Please try the attached program.

[Mateusz]

Hi Tom,

Still not good,
This time program starts tapping but virtual thread over the material. It's mean starts cycle from CCW Spindle rotation and Z axis going in positive direction. Also Console buffer loops up gathering lot of data even after killing threads and Reboot! command. To get out from this state I have to restart KMotion and KMotionCNC.

Thanks
Mateusz

[TomKerekes]

Hi Mateusz,

Oops, No peck case wasn't handled properly. Please try this.

[Mateusz]

Hi Tom,

Good one, it does work now I think now it is tested fully
Appreciate your help. You are first Company I know which is able support within hours ...on Sunday

Regards
Mateusz