Search found 17 matches
- Sat Apr 16, 2016 4:27 pm
- Forum: AutoLeveller Software
- Topic: Etching Problems
- Replies: 9
- Views: 10234
Re: Etching Problems
Apologies again for the long delay - was waiting for an isolation bit that took a bit longer than it should. APCDlg.jpg I did make the compare WPF app - and have added statistics for the individual files as suggested. Although trivial, the program has really helped me get a decent result now:-). Oft...
- Thu Mar 24, 2016 10:56 am
- Forum: AutoLeveller Software
- Topic: Etching Problems
- Replies: 9
- Views: 10234
Re: Etching Problems
Actually the comparison was done between matching coordinates on two distinct probe files, rather than min/max values on the same probe file. Am assuming min to max is what you used given the large variations (0.26mm). The idea was to keep comparing probe files until the differences were 'negligible...
- Sun Mar 20, 2016 5:46 pm
- Forum: AutoLeveller Software
- Topic: Etching Problems
- Replies: 9
- Views: 10234
Re: Etching Problems
Sorry about the delay in replying. Thanks for that, I clearly should've looked at the FlatCam code first. I cannot explain how the Z0.0000's got there, and even worse can't replicate it. But if this is something that can happen (weird race condition in FC?), maybe it could be useful if AL could log ...
- Mon Mar 07, 2016 4:47 pm
- Forum: AutoLeveller Software
- Topic: Etching Problems
- Replies: 9
- Views: 10234
Re: Etching Problems
Ok, sure. GTestEtchTopLayer_0.25mmdepth.nc -is the original GCode Mach3ALProbeGTestEtchTopLayer_0.nc - is the RPF created by Mach3 Zeroed_Mach3ALProbeGTestEtchTopLayer_0.nc - is the RPF created by Mach3 with probe values zeroed. The original GCode was created by FlatCam v8.4.
- Fri Mar 04, 2016 6:40 pm
- Forum: AutoLeveller Software
- Topic: v0.8.7 Output appears to use Incorrect Mach3 Probe Var
- Replies: 4
- Views: 5136
Re: v0.8.7 Output appears to use Incorrect Mach3 Probe Var
At the start, #502 should be set the the first Z in the probe table in the gcode file which should be close to 0 anyway. Oh good grief - I missed that. Sorry. The retraction should be the probe clearance value you set in AL. By default this is 2mm. No, I meant the retraction that is carried out via...
- Fri Mar 04, 2016 6:39 pm
- Forum: AutoLeveller Software
- Topic: Etching Problems
- Replies: 9
- Views: 10234
Etching Problems
I've been trying to etch the same small circuit many times. The pcb etching is not level, with air cuts in some places. It is a cheap cnc machine, but have made a sacrificial pocket and used double sided tape, as many have recommended. But the amount of depth difference for such a small board did se...
- Wed Mar 02, 2016 12:45 pm
- Forum: AutoLeveller Software
- Topic: v0.8.7 Output appears to use Incorrect Mach3 Probe Var
- Replies: 4
- Views: 5136
Re: v0.8.7 Output appears to use Incorrect Mach3 Probe Var
Well I am using the RPF. Where I got confused, is that o100 is called when starting the RPF modified code. I can only assume that in that case #502 should be zero. However the G31 moves the probe down until contact occurs, then retracts the probe slightly. How is that retraction taken into considera...
- Sat Feb 27, 2016 11:26 am
- Forum: AutoLeveller Software
- Topic: v0.8.7 Output appears to use Incorrect Mach3 Probe Var
- Replies: 4
- Views: 5136
v0.8.7 Output appears to use Incorrect Mach3 Probe Var
I've been having a (way) too deep etch on v0.8.7. The o100 sub procedure is using var #502 as the return from the probe operation - according to the Mach3 documentation #2002 is filled with the Z value. Altering to #2002 has anyway solved my basic problem, and the etch depth is much more as expected...
- Fri Feb 26, 2016 2:16 pm
- Forum: AutoLeveller Software
- Topic: AL 0.8.7 - X,Y Length Zero
- Replies: 2
- Views: 3632
Re: AL 0.8.7 - X,Y Length Zero
Thanks Country_Bubba! That fixed it.
- Fri Feb 26, 2016 11:36 am
- Forum: AutoLeveller Software
- Topic: AL 0.8.7 - X,Y Length Zero
- Replies: 2
- Views: 3632
AL 0.8.7 - X,Y Length Zero
I'm having problems setting the etch depth correctly, it seems to be cutting too deep. Anyway made a small test circuit (approx 20x20mm) using FlatCam - after loading in AL something is going wrong. The GCode (attached) loads fine in Mach3.