# Carvey Probe Gcode

**URL:** <https://community.inventables.com/t/carvey-probe-gcode/73963>\
**Category:** Carvey\
**Created:** [June 7, 2019, 3:06pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963 "2019-06-07T15:06:12Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel9](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/daniel9/32/76824_2.png) [@Daniel9](https://community.inventables.com/u/Daniel9)\
**Post date:** [June 7, 2019, 3:06pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/1 "2019-06-07T15:06:12Z")

</div>

Hello,

I configured UGS (universal gcode sender) to work with the Carvey.  
Is there a way to get the GCODE PROBING SEQUENCE that Easel would automatically generate for any given job?  
I’m milling out some PCBs and need to have a z-offset reference each time I run the job (turn on/off the machine).

Thanks!

---

<div class="post-metadata">

**Author:** ![NeilFerreri1](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/neilferreri1/32/84403_2.png) [@NeilFerreri1](https://community.inventables.com/u/NeilFerreri1)\
**Post date:** [June 7, 2019, 5:19pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/2 "2019-06-07T17:19:55Z")

</div>

Not at a PC, but if you export gcode from easel for the Carvey, it’ll include the start up probing sequence (at least it used to).  
That said, if you’re milling pcbs, I’d probe off of the PCB. The “smart” clamp won’t be accurate enough. The Z offset will persist across power cycles if you use G10 L20.

---

<div class="post-metadata">

**Author:** ![Daniel9](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/daniel9/32/76824_2.png) [@Daniel9](https://community.inventables.com/u/Daniel9)\
**Post date:** [June 7, 2019, 5:47pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/3 "2019-06-07T17:47:51Z")

</div>

Thanks for the reply.  
Yeah, that’s the problem is that I want to probe using UGS (universal Gcode sender) instead of using Easel, so I was looking for the actual Gcode that Easel would generate.

Probing off the PCB would be good. Would I just need to reroute the wires from the “smart clamp” to the PCB so there would be continuity between the PCB and the bit?

---

<div class="post-metadata">

**Author:** ![NeilFerreri1](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/neilferreri1/32/84403_2.png) [@NeilFerreri1](https://community.inventables.com/u/NeilFerreri1)\
**Post date:** [June 7, 2019, 11:29pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/4 "2019-06-07T23:29:37Z")

</div>

> [@Daniel9](#):
>
> Would I just need to reroute the wires from the “smart clamp” to the PCB so there would be continuity between the PCB and the bit?

Yup.

---

<div class="post-metadata">

**Author:** ![gaz99](https://avatars.discourse-cdn.com/v4/letter/g/49beb7/32.png) [@gaz99](https://community.inventables.com/u/gaz99)\
**Post date:** [June 10, 2019, 3:01am UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/5 "2019-06-10T03:01:59Z")

</div>

Hi Daniel,

What did you have to do to the Carvey firmware to get it to work with UGS ??

Gaz

---

<div class="post-metadata">

**Author:** ![Daniel9](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/daniel9/32/76824_2.png) [@Daniel9](https://community.inventables.com/u/Daniel9)\
**Post date:** [June 10, 2019, 1:46pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/6 "2019-06-10T13:46:20Z")

</div>

I had to add a few lines of Java code to UGS and recompile it in order for it to recognize Carvey’s firmware. I can send you the modified UGS if you want?

---

<div class="post-metadata">

**Author:** ![gaz99](https://avatars.discourse-cdn.com/v4/letter/g/49beb7/32.png) [@gaz99](https://community.inventables.com/u/gaz99)\
**Post date:** [June 10, 2019, 11:07pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/7 "2019-06-10T23:07:46Z")

</div>

That would be great, the re-compile stuff is a bit out of my area of expertise.

I have sent you a PM.

Gary

---

<div class="post-metadata">

**Author:** ![HaldorLonningdal](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/haldorlonningdal/32/72377_2.png) [@HaldorLonningdal](https://community.inventables.com/u/HaldorLonningdal)\
**Post date:** [June 11, 2019, 12:10pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/8 "2019-06-11T12:10:07Z")

</div>

Might be better off with a CNC-sender that support surface mapping (probing a grid over the entire area to be carved)

---

<div class="post-metadata">

**Author:** ![Daniel9](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/daniel9/32/76824_2.png) [@Daniel9](https://community.inventables.com/u/Daniel9)\
**Post date:** [June 11, 2019, 12:44pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/9 "2019-06-11T12:44:09Z")

</div>

Hi Haldor. For this specific operation, the tolerance is extremely tight. I’m milling out a trace on a multi-layered PCB, and can only go down about 0.040", so probing off of the PCB, as close to where I’ll be milling, is critical. If I go too far, then the board turns to scrap.

---

<div class="post-metadata">

**Author:** ![NeilFerreri1](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/neilferreri1/32/84403_2.png) [@NeilFerreri1](https://community.inventables.com/u/NeilFerreri1)\
**Post date:** [June 11, 2019, 1:05pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/10 "2019-06-11T13:05:06Z")

</div>

@Daniel9 What @HaldorLonningdal is suggesting is that you use bCNC or similar for the auto probing and mesh leveling. Any inconsistencies in your PCB thickness or wasteboard will be adjusted for.

---

<div class="post-metadata">

**Author:** ![Daniel9](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/daniel9/32/76824_2.png) [@Daniel9](https://community.inventables.com/u/Daniel9)\
**Post date:** [June 11, 2019, 7:49pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/11 "2019-06-11T19:49:56Z")

</div>

I understand now, but why bCNC and not UGS? Is bCNC better?  
I simply use the 38.2 command in UGS and it works fine.

---

<div class="post-metadata">

**Author:** ![HaldorLonningdal](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/haldorlonningdal/32/72377_2.png) [@HaldorLonningdal](https://community.inventables.com/u/HaldorLonningdal)\
**Post date:** [June 11, 2019, 8:07pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/12 "2019-06-11T20:07:51Z")

</div>

UGS dont support surface mapping.

---

<div class="post-metadata">

**Author:** ![HaroldBourne](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@HaroldBourne](https://community.inventables.com/u/HaroldBourne)\
**Post date:** [October 25, 2023, 11:44pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/13 "2023-10-25T23:44:26Z")

</div>

Hi Daniel9  
Just got myself a 2nd hand Carvey. I would be interested in the modified UGS to allow me to use that instead of Easel as I intend to generate the Gcode from Fusion360 first. Please could you post a copy of send me one?  
Thanks.

---

<div class="post-metadata">

**Author:** ![NeilFerreri1](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/neilferreri1/32/84403_2.png) [@NeilFerreri1](https://community.inventables.com/u/NeilFerreri1)\
**Post date:** [October 26, 2023, 12:54am UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/14 "2023-10-26T00:54:11Z")

</div>

@HaroldBourne Use gSender. It’s a much more polished sender. I started using cncjs with the Carvey almost as soon as I got it. gSender has picked up from there.  
By the way, if you want an extra Carvey, let me know, I have one for sale.

---

<div class="post-metadata">

**Author:** ![HaroldBourne](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@HaroldBourne](https://community.inventables.com/u/HaroldBourne)\
**Post date:** [October 26, 2023, 7:46am UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/15 "2023-10-26T07:46:32Z")

</div>

@NeilFerreri1 Thanks for the prompt reply, especially as my query was 4 years after the post! Glad to see this forum still has users. I will check out gSender. Can I just copy the first part of the gCode into a new Fusion generated GCode to do the auto probe bit? i.e. the code from the intro file is  
G90  
G21  
G28  
G21 G38.2 Z-71 F80  
G10 L20 P1 X17 Y-12.25 Z12.7  
G54  
G0 Z20  
G0 X20 Y20  
M3 S12000  
G4 P1  
G20

---

<div class="post-metadata">

**Author:** ![NeilFerreri1](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/neilferreri1/32/84403_2.png) [@NeilFerreri1](https://community.inventables.com/u/NeilFerreri1)\
**Post date:** [October 26, 2023, 4:56pm UTC](https://community.inventables.com/t/carvey-probe-gcode/73963/16 "2023-10-26T16:56:32Z")

</div>

So you still want to use the smart clamp? (You don’t have to)

Yes, you can use that, but be careful about units and such. Do you want that part of the code to start your spindle? Fusion should be doing that.

I’d just use the probing gadget in gSender or cncjs.
