Probing Cycle Failed- Snapping Bits

CNC Machines Shapeoko
1

So I’ve got a shapeoko 3xl with the touch probe. I have an intermittent problem with zeroing using my probe. Sometimes it works just perfect, then I can go and reset after a bit change and when i initiate it drives down on the z, goes red when contact is made and then continues to force the router down still. I’ve included a video with the Z set higher prior to probing to minimize impact on the probe. Unfortunately this has already cost me a few bits as it will force it down and snap them off. After it fails I have to reinitialize and try again. Any help is appreciate, I haven’t seen any other posts with the same issue.

  • Mike
2

can’t put the video on as it won’t allow .movs.

3

I have developed a habit of lifting the bitzero up to the router bit after attaching the croc clip and checking the LED goes RED, it’s part of my “remember to probe Z properly” muscle memory.

Might be worth you checking the LED colour change manually like that before probing just to check the basic connectivity?

1 Like
4

If I tap the clip to the probe it goes red. Sometimes it will go perfectly through the z,x,y zeroing and sometimes it just slams down through the touch probe during z zeroing. It’s random, but the light always goes red with the bit or testing prior.

5

Oh, so the LED goes red during the probing cycle and the machine just carries on “probing” anyway?

6

Any chance you’re using another program that’s sending GRBL settings to your Shapeoko? Something like laser software? I’ve found that some of these programs send settings that screw up the probe cycle.

7

Exactly what it’s doing

8

No other programs being used

9

Well that’s really not good.

I think this might be a good point to email the video into support and see what they’ve got to say, @WillAdams ?

1 Like
10

@DookDesigns Can you make the probe connection (close the circuit) and paste the log output here?

11

But you can post it online (e.g. YouTube) and past a like here for viewing…right?

12

Here is the link to the video. Like I stated this was starting at a higher z value, otherwise it clicks into the probe a few times before failing.

1 Like
13

Here’s the log from a failed attempt.

(9244): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0>
(9243): <- ok
(9242): <- $132=80.000
(9241): <- $131=850.000
(9240): <- $130=845.000
(9239): <- $122=400.000
(9238): <- $121=400.000
(9237): <- $120=400.000
(9236): <- $112=5000.000
(9235): <- $111=5000.000
(9234): <- $110=5000.000
(9233): <- $102=40.000
(9232): <- $101=40.000
(9231): <- $100=40.000
(9230): <- $32=0
(9229): <- $31=0
(9228): <- $30=1000
(9227): <- $27=5.000
(9226): <- $26=25
(9225): <- $25=2000.000
(9224): <- $24=100.000
(9223): <- $23=0
(9222): <- $22=1
(9221): <- $21=0
(9220): <- $20=0
(9219): <- $13=0
(9218): <- $12=0.010
(9217): <- $11=0.020
(9216): <- $10=255
(9215): <- $6=0
(9214): <- $5=0
(9213): <- $4=0
(9212): <- $3=6
(9211): <- $2=0
(9210): <- $1=255
(9209): <- $0=10
(9208): -> $$
(9207): -> gc_get_settings
(9206): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0>
(9205): -> gc_sync
(9204): <- ok
(9203): -> M56P1
(9202): -> gc_enable_parking
(9201): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0|WCO:0.000,0.000,0.000>
(9200): -> gc_sync
(9199): <- ok
(9198): -> N0 G4P0.005
(9197): -> gc_wait_for_idle
(9196): <- ok
(9195): <- [PRB:0.000,0.000,0.000:0]
(9194): <- [TLO:0.000]
(9193): <- [G92:0.000,0.000,0.000]
(9192): <- [G30:0.000,0.000,0.000]
(9191): <- [G28:0.000,0.000,0.000]
(9190): <- [G59:0.000,0.000,0.000]
(9189): <- [G58:0.000,0.000,0.000]
(9188): <- [G57:0.000,0.000,0.000]
(9187): <- [G56:0.000,0.000,0.000]
(9186): <- [G55:0.000,0.000,0.000]
(9185): <- [G54:0.000,0.000,0.000]
(9184): -> $#
(9183): -> gc_get_offsets
(9182): <- ok
(9181): <- [GC:G0 G54 G17 G21 G90 G94 M5 M9 M56 T0 F0 S0]
(9180): -> $G
(9179): -> gc_parser_state
(9178): <- ok
(9177): -> G90
(9176): -> gc_not_motion
(9175): <- ok
(9174): -> G49
(9173): -> gc_not_motion
(9172): <- ok
(9171): -> G21
(9170): -> gc_not_motion
(9169): <- ok
(9168): -> G10L2P1X0Y0Z0
(9167): -> gc_not_motion
(9166): <- ok
(9165): -> G54
(9164): -> gc_not_motion
(9163): <- ok
(9162): -> G92.1
(9161): -> gc_not_motion
(9160): <- ok
(9159): -> N0 M5
(9158): -> gc_spindle
(9157): <- ok
(9156): -> N0 G4P0.005
(9155): -> gc_wait_for_idle
(9154): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0>
(9153): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0|WCO:0.000,0.000,0.000>
(9152): -> gc_wait_for_status_updates
(9151): <- ok
(9150): <- [PRB:0.000,0.000,0.000:0]
(9149): <- [TLO:0.000]
(9148): <- [G92:0.000,0.000,0.000]
(9147): <- [G30:0.000,0.000,0.000]
(9146): <- [G28:0.000,0.000,0.000]
(9145): <- [G59:0.000,0.000,0.000]
(9144): <- [G58:0.000,0.000,0.000]
(9143): <- [G57:0.000,0.000,0.000]
(9142): <- [G56:0.000,0.000,0.000]
(9141): <- [G55:0.000,0.000,0.000]
(9140): <- [G54:0.000,0.000,0.000]
(9139): -> $#
(9138): -> gc_get_offsets
(9137): <- ok
(9136): <- [GC:G0 G54 G17 G21 G90 G94 M5 M9 M56 T0 F0 S0]
(9135): -> $G
(9134): -> gc_parser_state
(9133): <- ok
(9132): -> G90
(9131): -> gc_not_motion
(9130): <- ok
(9129): -> G49
(9128): -> gc_not_motion
(9127): <- ok
(9126): -> G21
(9125): -> gc_not_motion
(9124): <- ok
(9123): -> G10L2P1X0Y0Z0
(9122): -> gc_not_motion
(9121): <- ok
(9120): -> G54
(9119): -> gc_not_motion
(9118): <- ok
(9117): -> G92.1
(9116): -> gc_not_motion
(9115): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0>
(9114): -> gc_sync
(9113): <- ok
(9112): -> N0 G4P0.005
(9111): -> gc_wait_for_idle
(9110): <- <Idle|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0|Ov:100,100,100>
(9109): <- ok
(9108): <- [MSG:Caution: Unlocked]
(9107): <- <Alarm|MPos:-804.750,-711.425,-34.775|Bf:14,128|FS:0,0|WCO:0.000,0.000,0.000>
(9106): -> $X
(9105): <- [MSG:’$H’|’$X’ to unlock]
(9104): <- Grbl 1.1f [’$’ for help]
(9103): <- ok
(9102): <- [PRB:0.000,0.000,0.000:0]
(9101): STATE: SET MACHINE STATE: INIT
(9100): -> GRBL_RESET
(9099): STATE: SET MACHINE STATE: MACHINE_ALARM
(9098): <- ALARM:5

1 Like
14

Thanks for posting the video…looks like a bad probe.

Don’t laugh, but have you tries tapping it on the board, and then trying to see if it works?

15

I’ll give it a shot, only thing that makes sense to me as it’s intermittent

16

tapped it, got no result, tapped harder and it managed to pass a simple z zero, moved it to the corner and failed to x zero. shifted wires and tried to get an z,x,y multiple times and fails. Ugh, I just wanna finish my project

17

Maybe a bad cable or loose connection? If you can, check the solder on your PROBE connections on the controller.

1 Like
18

With regards to finishing your current project, you could manually set your zeros. Use a piece of paper, a feeler gauge, or simply rotate the collet while projecting it down into the work piece. Look and feel for a little drag.

1 Like
19

I found that a V bit was a really good way to hit an X Y zero by eye. As above for Z

1 Like
20

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.