Probe question

What would the starting commands be for a zprobe / touchplate using the jackpot / FluidNC?
The equivalent of this block of code from the Marlin days:

G92 X0 Y0 ; Set Current position to 0 on the X and Y axes.
M0 Attach probe ; Pause to connect touchplate
G38.2 Z0 ; Probe down to touchplate
G92 Z0.5 ; Set new Z position to thickness of touchplate
G1 Z2 F900 ; Lift off touchplate
M0 Remove probe ; Pause and wait for touchplate removal
M106 ; This will turn on an IOT relay to start a router or vacuum

EDIT: Here’s what I came up with for the starting text:

G21
G90
G94
$h
G10 L2 P0 X0 Y0 ; Set Current position to 0 on the X and Y axes.
M0
G38.2 Z-60 F400 ; Probe down to touchplate
G92 Z0.5 ; Set new Z position to thickness of touchplate
G1 Z2 F900 ; Lift off touchplate
M0 ; Pause and wait for touchplate removal
M106 ; This will turn on an IOT relay to start a router or vacuum
G00 X0.0000 Y0.0000 Z0.0000
G00 Z10.1600

It didn’t like the G92 and the fluidnc wiki seems to prefer G10 so I changed it to that.

Does this seem right? It works but I wouldn’t mind one of the pros looking over it and letting me know if there’s a better way to start a cut.

Thanks for your help!

Ryan’s start code with the probe looks like this:

G21
G90
G94
G92 X0 Y0
M0 (MSG Attach probe)
G38.2 Z-80 F200 P0.5 ( probe down set thickness )
G1 Z10 F900
M0 (MSG Remove probe)
M62 P0 ( start spindle pin26 )

This was taken from the FluidNC.pp file in the docs

1 Like

Does this mean I can take this and create a Macro button for the dashboard?

Is there code to reset all coordinates? So I can place the cutter on my zero?

I’m all wired up, stop switches tested and passed. Next things to sort out on the dashboard is the probe and resetting the coordinates to set the start point. Oh, and ensure Estlcam codes for Grbl!

You should be able to place that in a macro, or you can set that as Program Start GCode in your CAM program.

I just imported Ryan’s settings file as a starting point and went from there. It has Program Start and end, as well as Tool change GCode already set up.

That snippet will set the current X and Y as your home, Pause and wait for you to attach the probe. you press Resume and the probe will drop. It will then pause for you to remove the probe and start your spindle. Press Resume and it will go.

Tool change also has probe integrated as part of it.

1 Like

If you use this file to configure your estlcam, Jackpot CNC Controller - V1 Engineering Documentation, it will add starting ending and tool change commands. You can edit or copy them from there.

I guess I need to break them out to the basics page soon. I thought I was still testing but things are working fine.

The end code might be problematic for the MPCNC:
Program end text=
[>>>]

M63 P0 ( stop spindle pin26 )
$HZ
M30
[<<<]

For whatever reason my controller threw an error with the G92 X0 Y0 command. I’ll play around with it again tonight if I can find the time as I can’t remember the exact error it gave me off the top of my head. For some reason it was ok with G10 L2 P0 X0 Y0 ;

This is what I have been using as a macro:
G0 Z5 F400
$HX
$HY
G92 X0 Y0
G0 X50 Y50 F2100 ( move for room for touchplate)
M0 (MSG change tool, probe)
G38.2 Z-80 F200 P0.95 ( Probe set thickness)
G00 Z10.0000 F500 ( Clearance )
M0 (MSG remove probe)
G0 X0 Y0

I did it as a macro to try out doing a tool change. It worked fine.

1 Like

Risking exposure as a full newb, do I assume to take out the characters in parenthesis? Or can I leave them in?

1 Like

Leave them in.

( ) are comments in GCode

In FluidNC, those MSG comments will show in the terminal so you know why it paused for M0.

1 Like

Can’t get this to work. I’m about to give up.

The fluid.pp file downloaded from the jackpot page works for me. This is a settings file for EstlCam. It adds the proper Gcode to your estlcam files to do the z-probing at the beginning of a cut.
Is that where you’re stuck?

This is what I get back in the controller command after reworking the settings from Estlcam:

$G [GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0] ok $Report/Interval=1500 <Idle|MPos:0.000,0.000,0.000,0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000,0.000,0.000,0.000> [MSG:INFO: Channel auto report interval set to 1500 ms] ok <Idle|MPos:0.000,0.000,0.000,0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000,0.000,0.000,0.000> [GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0] $SD/Run=/1-CNCFinals/M&DUrn2.gcode [MSG:WARN: Low memory: 14376 bytes] [MSG:WARN: Low memory: 14256 bytes] [MSG:WARN: Low memory: 14064 bytes] [MSG:WARN: Low memory: 13864 bytes] [MSG:WARN: Low memory: 13736 bytes] [MSG:WARN: Low memory: 12328 bytes] [MSG:WARN: Low memory: 12128 bytes] [MSG:WARN: Low memory: 12004 bytes] <Idle|MPos:0.000,0.000,0.000,0.000,0.000,0.000|FS:0,0|Ov:100,100,100> ERROR:66 error:66 Error : undefined :undefined

I gave up on the probe idea and decided to just manually zero through the command. then attempted to load a design and that code above was returned.

Can you show a screen shot of your starting, ending and tool change sections of estlcam?

I use these settings so I know they work something must be missing from the import.

What reworking are you doing?

9_16_jackpot.zip (1.0 KB)
The exact settings I am using on a cut right now. No reworking should be needed.

I also haven’t had any problems after importing that file in EstlCAM 11 either.

Error 66 is “Failed to open file”, so that sounds like a pre-gcode problem

The reworking was the change from Marlin to GRBL. After getting the jackpot board plugged in and working by the wifi FluidNC controller, I hadn’t yet updated the Estlcam from my Rambo/Marlin settings. So I had to reset them to the GRBL.

The pp I just uploaded and is in the instructions should change all the settings for you and inject my starting and ending stuff. Just unzip and import my config file to estlcam.

After that if there are any issues show us the screenshots.