[yugami]

Doing any sort of tap op royally screws the machine. G84 or G88 and the machine sticks at that line.


Heres the control display for the G84 N12 and N13 are from the program. The rest are the canned cycle stuff I'm assuming.



Just cycles at 500RPM and sits there until you cancel it.

Is it the M29? That says its some sort of Aux output, maybe the wiring is off? The machine did threading when I examined it a year ago before moving it.

[Brian L]

I use Tension and compression holders and don't do it using a canned cycle... but first thing I see is you have 0 for the feed rate, so yeah, it's going to sit there and do nothing until you cancel it.

[yugami]

Feed rate in the program is 0.0312 (feed rate should be in pitch according to the manual) and this is confirmed working on Cent 7

[Brian L]

I see F0. in your picture, and my Centurion V manual says feed rate is pitch x rpm. For example 20 pitch would be .050" x say 500 rpm would be a feed rate of 25.0 ipm

[Superman]

I see F0. in your picture, and my Centurion V manual says feed rate is pitch x rpm. For example 20 pitch would be .050" x say 500 rpm would be a feed rate of 25.0 ipm

+1... but I'll add that this is quite correct if G94 (feed per minute) is previously stated.... If G95 is stated instead of G94.... then feed is the pitch of the tap... remember to switch back to G94 for normal milling.

....Also cannot see the M3 on the G29 line... some controls require it, even if the cycle does start the spindle.

Check your program in single block.... the problem may be in the following lines, not on the G84 line at all.

[yugami]

Hopefully I'll have some time to play around with this some more, must have been a change in the control between Cent 5 and Cent 6.

[Brian L]

Like Superman says, depends upon if you are running G94 (IPM) or G95 (IPR) and your programming doesn't show enough to determine that. Is that code you are showing on the screen from the conversational side? Doesn't look like standard g-code to me. I never really bothered with the conversational portion as I have been doing g-code since the late 70's and it comes second nature.

[yugami]

Like Superman says, depends upon if you are running G94 (IPM) or G95 (IPR) and your programming doesn't show enough to determine that. Is that code you are showing on the screen from the conversational side? Doesn't look like standard g-code to me. I never really bothered with the conversational portion as I have been doing g-code since the late 70's and it comes second nature.

Most of what's showing is the type of stuff that shows on my screen when it's executing canned cycles. This is in cycle when it got stuck

The two lines N12 and N13 are the only program gcode showing

[Brian L]

Oh, then it would help to see the code for that tool.... easier to decipher what it might not be working.

[Superman]

Oh, then it would help to see the code for that tool.... easier to decipher what it might not be working.

you are right.... create a program for just that operation, then prove it off in your machine, then you won't have other op's settings(G/M codes) coming into play

[wfr8577]

This works for my Partner 1. It was a 5 hole test. 4-40 Tap.
https://youtu.be/p0m8xPVP5l4

O1005 (DRILL AND RIGID TAP TEST)
(T21 D=0.115 CR=0 - ZMIN=-0.225 - RIGHT HAND TAP)
N1 G90 G94 G17
N2 G20
N3 G32
(RIGID TAP)
N4 M9
N5 T21 M6
(4-40 TAP)
N6 S500 M3
N7 G56
N8 M7
N10 G0 X-0.25 Y0.3625
N11 G43 Z0.6 H21
N13 G0 Z0.2
N14 G98 G88 X-0.25 Y0.3625 Z-0.225 R0.1 P0 F0.025
N15 X-0.5
N16 X-0.75
N17 X-1
N18 X-1.25
N19 G80
N20 Z0.6
N22 M9
N23 G32
N24 G53 Y0
N25 M30

[yugami]

Thanks for the sample.

Looks like its probably the M29 that the post is outputting. Its a pulsed output and reading the manual a little closer, everything locks up until the corresponding input gets a signal. Not sure why this is being output by default, but it appears to not cause an issue on newer controls (having had good feedback from a Cent 7 guy).

Going to play a little bit after lunch.

[yugami]

It was the M29 - I just deleted that line and the test sailed though perfectly.

[wfr8577]

It was the M29 - I just deleted that line and the test sailed though perfectly.

Sweet! I'm glad you were able to get it working.