First of all, major thank you to all the contributors around here. Would never have gotten half this far without you and I’m still in total awe of the machine that’s setting in my garage right now.
After your guys’ help on switching the DC power wires, my LR3 is now running great. Was extremely (and pleasantly) surprised to find that everything is perfectly square. The crown test went wonderfully and I’ve been studying Estlcam to create my strut file. I decided to do an air test on the file before cutting to make sure it was going to run the way I programed it. Unfortunately, after touching the probe, the x-axis wouldn’t stop raising up. It pinned itself against the kill switches (which do work when homing) and started grinding until I killed the program.
The start code I used for Program Start in Estlcam is copy and pasted from the guide:
The Z-110 should just mean that it will go down a max of 110mm before it errors out if it hasn’t triggered the probe yet.
I don’t see anything apparent in the gcode itself.
What about the config?
Is it 100% exact as Ryan’s config? Is it possible the mpos_mm is set incorrectly, which could be causing it to go up very far when it executes G1 Z10 F900? Maybe scratch that…I’m not sure that setting affects probing, just homing.
You can download and paste your config file here if you want to have it checked.
I’m assuming that
means that it
Showed you an “Attach Probe” message in the console
You attached the probe
Hit resume
The router moved down towards the workpiece/probe and stopped when the bit hit the probe
Then moved all the way back up into the endstops
Is that correct? Or is it moving straight up when you hit resume after “Attach Probe”, without ever heading towards the workpiece?
After the probe is contacted, the router just goes all the way up without stopping. We don’t even get the opportunity to hit resume. I did look at the file in notepad and noticed my first number is G20 instead of G21. Not sure why it saved that way, but could that be causing the issue?
