Joebus
February 21, 2024, 2:12pm
1
I’m looking for a little hand holding
It’s been almost 2 years since I’ve run my LR2 and have just finished the LR3. I’m very rusty. I have drawn the crown test and passed.
I’ve uploaded my gcode to the LR3. My 0,0 of my spoil board is 80mm from home on my X.
*I want to be able to hit “start job” > Press button to probe > Probe > remove probe > turn on router > Press button to start cutting and motion.
In Fusion PP I have “Probe on Start” turned on. EDIT: Having this turned on is giving me an error when starting the job.
I know there is some Start and End gcode that is provided( saw in jackpot docs) . Where do these go and how do I use them?
DougJoseph
February 21, 2024, 2:50pm
2
So you can definitely use Fusion 360 to produce Gcode. Most of us use ESTLcam instead for most jobs. I use ESTLCam for my LowRider that has a router, but I use Fusion 360 for my LowRider that has a plasma cutter.
Getting setup in ESTLcam is pretty straightforward and pretty easy. In its options/preferences/setup area it has boxes where you paste in your Start Gcode and End GCode. It has some basic settings, such as choosing GRBL (for Jackpot) as opposed to choosing Marlin (for SKR boards). ESTLcam basically builds its own Post Processor for you on the fly based on the settings you choose.
Things are a little different with Fusion 360. I think it needs you to choose or provide a Post Processor, and you also will need to walk though some setup steps per job. I was able to locate a Post Processor for my plasma related work, but I don’t know about one for what you are doing.
One workaround option (perhaps temporary) is to put your starting GCode and ending GCode in files (.gcode files) on your SD card and run them like jobs. Or to put them in .g files and upload them to the Jackpot and assign macro buttons to point to them.
In the FluidNC WebUI for the Jackpot, there is a setting that turns on a Probe panel (not enabled by default). It adds a probe interface to the WebUI.
Joebus
February 21, 2024, 2:56pm
3
Hi Doug, thanks for the speedy reply!
I’ve already got the PP for fusion in and that is actually working(except for the probe at start line, this used to work on my LR2 but doesn’t now). I also have probe menu enabled and have been probing successfully from the webui and from the M5 dial. I think what I’m still struggling on is order of operations/workflow.
So I think for now I need to : Jog to my start location on XY > Zero Location > Probe > Zero Location > Jog up Z away from workpiece > Remove Probe > Start Router > Start Job > Wait and Pray > Profit??
DougJoseph
February 21, 2024, 3:02pm
4
Basically, yes. A couple thoughts come to mind here.
One is do an “air cut” first as a test. To do this, when you probe, manually tap your electrode wire end against your touch plate, well before the machine actually moves all the way down. This falsely and intentionally tells the machine the material is higher than it is. You can then run the job, without the router on, in a nondestructive test.
The other is that, depending on your GCode settings, the script for probing may or may not automatically set an XY 0,0 offset. The probe feature built into the FluidDial pendant does not. The probe scripts offered by some V1E docs do. By contrast, however, in practically all cases where you specify a plate thickness in probe settings, or probe script, the probe action will automatically set the Z height at zero offset at the time of probing.
Does this help?
1 Like
Joebus
February 21, 2024, 3:34pm
5
Yes thank you. This helps. I like your tip for setting the probe higher for testing.
1 Like
Joebus
February 21, 2024, 5:56pm
6
Ok so I’ve been able to get things to start and run. The motions are matching what I’m telling it to do. All except it runs 600 mm up the Y axis then starts. X is spot on and Y is spot on. Any ideas?
DougJoseph
February 21, 2024, 6:21pm
7
Maybe you could wrap your GCode file as a Zip compressed file and upload it here. ?
Joebus
February 21, 2024, 6:22pm
8
Yes, Sorry I just realized I should share gcode and some pics. one min
All they Y axis movements look normal to me.
Summary
%
Joebus
February 21, 2024, 6:56pm
9
I think it has to do with the M5 Dial pendant. I’m doing my jogging, probing and job start via the dial. Referring back to the coordinate readout glitch in the dial; When I jog X over to where I need to be. Then switch to Y, Y displays a -600 and something readout. If I wait 1 sec it clears and goes to zero. When I started the job I posted above I jogged X over and did probe but never switched the dial to Y so I think it was stuck at -600 on Y. So then it traveled to “0” which in actuality is +600 up the Y. I’m testing now by doing everything the same but displaying Y on the dial for a second so it zeros out.
EDIT: Yes. This was the issue. It works as expected now.
DougJoseph
February 21, 2024, 7:05pm
10
OK, glad you got that sorted. Wow.
I need a refresher/walkthrough of starting a job on my LR3 with a jackpot and probe. I use F360 to create my gcode.
