# Probe routine runs twice at start of every job **URL:** \ **Category:** 💡 Suggestion\ **Created:** [October 19, 2024, 10:28pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228 "2024-10-19T22:28:21Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![Ternary](https://forum.sienci.com/user_avatar/forum.sienci.com/ternary/32/9071_2.png) [@Ternary](https://forum.sienci.com/u/Ternary)\ **Post date:** [October 19, 2024, 10:28pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/1 "2024-10-19T22:28:21Z")
Hi all, I just switched over to gSender from Carbide Motion on my Shapeoko Pro. Everything about it runs great so far, I’m successfully running my test jobs and getting results. I’m exporting gcode from VCarve using the Shapeoko Post Processor. My issue is that ever time I start a job (including rerunning the same job twice), it runs the probe routine for the initial tool (there is a T1 in the gcode near the start). Then it immediately runs the probe routine again because I’m using tool T(not 1), which runs M6 tool-change command, which runs the probe. Is there a simple step or setting I’m missing? This is a bit of a pain since I’m still at the stage where most of my work is on \< 2minute cuts, since I’m running tests, proof of concepts, etc. With such short jobs, the double probe routine is adding a significant chunk of time to these that I’m trying to run in quick succession. Do I need to change something in the post-processor? (I haven’t done this before but can do it with the proper links/info). Is there a setting in gSender I’m overlooking? Thanks in advance! ---
**Author:** ![NeilFerreri](https://forum.sienci.com/user_avatar/forum.sienci.com/neilferreri/32/1959_2.png) [@NeilFerreri](https://forum.sienci.com/u/NeilFerreri)\ **Post date:** [October 20, 2024, 11:28pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/2 "2024-10-20T23:28:28Z")
Can you share a gcode file where this happens? ---
**Author:** ![Ternary](https://forum.sienci.com/user_avatar/forum.sienci.com/ternary/32/9071_2.png) [@Ternary](https://forum.sienci.com/u/Ternary)\ **Post date:** [October 21, 2024, 4:31am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/3 "2024-10-21T04:31:12Z")
Hmm, as a new user I can’t upload files apparently. Here are the first few lines including the M6 tool change command. The probe routine gets triggered on the very first line (T1), and then again on M6: ```auto (VECTRIC POST REVISION) (AC06FA06858F6820297A912D3D187A70) T1 G17 G21 G90 M6 T201 G0Z6.350 G0X0.000Y0.000 S20000M3 G0X19.052Y9.640 G0Z6.350 G0Z3.810 G1Z0.000F3048.0 ``` ---
**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\ **Post date:** [October 21, 2024, 10:34am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/4 "2024-10-21T10:34:12Z")
@Ternary Welcome to the group. I’ve moved your post. You posted in the UGS category and since you are using gSender, I’ve moved it the gSender question category. ---
**Author:** ![Ternary](https://forum.sienci.com/user_avatar/forum.sienci.com/ternary/32/9071_2.png) [@Ternary](https://forum.sienci.com/u/Ternary)\ **Post date:** [October 24, 2024, 4:17pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/5 "2024-10-24T16:17:40Z")
> You posted in the UGS category and since you are using gSender, I’ve moved it the gSender question category. Whoops, sorry about that! ---
**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\ **Post date:** [October 24, 2024, 4:55pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/6 "2024-10-24T16:55:29Z")
@Ternary No worries. I believe that it will get more traction here. 😀 ---
**Author:** ![Ternary](https://forum.sienci.com/user_avatar/forum.sienci.com/ternary/32/9071_2.png) [@Ternary](https://forum.sienci.com/u/Ternary)\ **Post date:** [October 28, 2024, 4:23pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/7 "2024-10-28T16:23:07Z")
I made a hacky attempt here to avoid the double probe by changing the initial `T1` to whatever the first tool is that actually gets used in the file (`T201` in this case). This unfortunately does not work. Further info: I’m using the Auto Z Plate method using the carbide bitsetter. ---
**Author:** ![Kerryh2012](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/7ba0ec/32.png) [@Kerryh2012](https://forum.sienci.com/u/Kerryh2012)\ **Post date:** [July 18, 2025, 4:40pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/8 "2025-07-18T16:40:47Z")
The Fusion grbl post processor inserts an M6 command on every tool including the initial tool path. I know there are other grbl posts that have the option to not insert an M6 on the first tool path but I would prefer to stick with the stock one. It would be nice if there was an option under the TLS settings to ignore the first M6 command to reduce the time not cutting in a job. I would rather not have to edit every multi-tool gcode file I generate. ---
**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\ **Post date:** [September 24, 2025, 11:56pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/9 "2025-09-24T23:56:33Z")
@Kerryh2012, funny you bring this up. As of 1.5.5 we implemented an ignore for this first tool change due to the confusion it was causing others. If you can try it out and let us know if it’s worked out for you, that’d be great ---
**Author:** ![Kerryh2012](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/7ba0ec/32.png) [@Kerryh2012](https://forum.sienci.com/u/Kerryh2012)\ **Post date:** [September 25, 2025, 12:04am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/10 "2025-09-25T00:04:58Z")
Thanx Chris, I’ve just been removing the first tool change manually. I’d almost forgotten about it. I saw that my other issue with the AZTP with a set bit diameter is on the fix list the other day too. I called it a missing divide by 2 issue, the devs called it a double compensating issue. I found that funny. It looks like this release fixes 3 of my issues, 2 I have brought up on the forums. 1 I privately wondered why I had to probe the initial tool on the first tool change since it was the one I zeroed with. I’m looking forward to giving it a run though. ---
**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\ **Post date:** [September 25, 2025, 12:14am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/11 "2025-09-25T00:14:07Z")
Yeah it a sense it was both since if you double compensate radius then you get diameter, and if you don’t divide diameter by two to get radius, you get diameter XD Either way, it was all a part of a specific focus on probing for 1.5.5 so the issue should now also be fixed as of the testing I did with the team over the last couple days. Fingers crossed! ---
**Author:** ![Kerryh2012](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/7ba0ec/32.png) [@Kerryh2012](https://forum.sienci.com/u/Kerryh2012)\ **Post date:** [September 25, 2025, 12:39am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/12 "2025-09-25T00:39:01Z")
This works too but won’t not having it as a selectable option cause problems for things like the ATC? ---
**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\ **Post date:** [September 25, 2025, 12:40am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/13 "2025-09-25T00:40:53Z")
Yes it will cause problems. For ATC application we’ll be working on a better long-term solution alongside all the other work we’re putting in to support ATC systems ---
**Author:** ![Kerryh2012](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/7ba0ec/32.png) [@Kerryh2012](https://forum.sienci.com/u/Kerryh2012)\ **Post date:** [September 25, 2025, 1:34am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/14 "2025-09-25T01:34:11Z")
Can always pad the beginning of the gcode file with G21’s as a hack. Just tested this. ---
**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\ **Post date:** [March 20, 2026, 6:27pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/15 "2026-03-20T18:27:33Z")
This is still an aspect we haven’t fully solved yet for Carbide Create and Fusion 360 except a recent update to highlight when it’s the first cycle through so that you can just ignore it the second time around. We initially made gSender skip the first command entirely, but that created other knock-on issues so we had to revert it unfortunately ---
**Author:** ![Kerryh2012](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/7ba0ec/32.png) [@Kerryh2012](https://forum.sienci.com/u/Kerryh2012)\ **Post date:** [March 20, 2026, 8:11pm UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/16 "2026-03-20T20:11:25Z")
For Fusion, the first tool can be set to manual tool change (no M6) in the tool settings. ---
**Author:** ![KGN](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/c77e96/32.png) [@KGN](https://forum.sienci.com/u/KGN)\ **Post date:** [September 1, 2026, 11:53am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/17 "2026-09-01T11:53:22Z")
There is now (as of 1.6.0) a selectable option to skip this for tool changes, so I’ll be marking this as complete. ---
**Author:** ![KGN](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/c77e96/32.png) [@KGN](https://forum.sienci.com/u/KGN)\ **Post date:** [September 1, 2026, 11:53am UTC](https://forum.sienci.com/t/probe-routine-runs-twice-at-start-of-every-job/14228/18 "2026-09-01T11:53:24Z")