CNC PCB milling

[andrew]

@neverdie for er11 fastening you should use two wrenches.

if you loose steps during the milling, then with the given feed rate / depth / spindle speed combination the cnc / spindle / steppers are not powerful enough.

if you wood milling depth is not constant then:

• the wood is not flat
• the cnc bad is not flat
• the cnc x axis is not horizontal

my availability for the next couple of days will be quite limited, so I wish you good luck for experiencing the router and for the first PCBs!

[ben999]

@neverdie said in CNC PCB milling:

Also, what is the preferred way to tighten the ER11 chuck? So far, I did it just by hand, which seems to have been good enough. However, maybe a better way is to give it a 1/4 turn further tightening using wrenches after that? How are others here approaching that?

+1 for the wrench, mostly because of vibrations that could unscrew it. No need to pull a muscle on it as it is tapered and has big contact surface

[zboblamont]

@neverdie If it is anyway similar to a Router, it should have a locking pin to hold the spindle, or a second nut against which you tighten the collet. Do not overtighten, just enough to bite the shaft, otherwise you either damage the shaft or more seriously shatter the collet, it should be just enough to be a firm clamp to ensure grip, the collet will do the rest.
Not a user of these CNCs but I would guess the same principles apply... Just my 2c...

[NeverDie]

@andrew

Have a Merry Christmas!

Also, I'm not going to dwell on etching wood . It was just my first attempt at etching anything, and I thought wood might be a little softer.

I suppose the next step is to have a go at auto-leveling on a PCB rather than perfect the machine's etching of plywood. Indeed, PCB's may turn out to be easier, as the resistance to downward motion (especially after auto-levelling) should be more uniform.

[NeverDie]

Meh, I think I know what happened now. If the z-axis ever skips a step in downward motion--for whatever reason--then the rest of the etching is screwed from that point forward, because the higher height then becomes the new "zero" for the entire remainder of the etching since the depth control is completely open loop. So, the first spot in the sequence that isn't at proper depth would be where the error occurred, creating a persistence of the error from that point forward in the etching sequence.

[zboblamont]

@neverdie If the material is parallel to the cutting plane, the cut depth should be constant. Might I suggest doing same experiment using auto-level.... Wood is easier on the bits, plywood less so but still less abrasive than FR4...

[NeverDie]

@zboblamont said in CNC PCB milling:

Might I suggest doing same experiment using auto-level....

Is there an auto-level that works on wood? I thought it assumed a conductive surface, like on a blank copper PCB, to facilitate the auto-leveling mapping process, so that it knows when contact is made and therefore the height at each touch point.

[zboblamont]

@neverdie Tinfoil?

[zboblamont]

@neverdie I should explain my thinking... I do not think your wood experiment made sense. You assume your sensors and the wood are parallel, this need not be true. Plywood is generally less than 0.3mm out of true, even if you could zero the 4 corners with foil or similar it would give you a plane on which to see if the original trial was misleading.

[NeverDie]

@zboblamont said in CNC PCB milling:

@neverdie Tinfoil?

You get an A+ for creative thinking. I suppose extra wide foil tape might work.

[zboblamont]

@neverdie I was thinking kitchen foil pressed flat as possible to the block surface, whatever works...

[NeverDie]

This is a good video for how to auto level in ChiliPeppr:
Auto-Level a PCB in ChiliPeppr – 21:33
— John Lauer

So, with that as inspiration, I plan to connect the probe to A5 on the woodpecker, and the PCB surface to GND. He soldered his ground wire to the PCB, so I guess I'll do the same, at least for now.

I'll use tape to secure the PCB to the sacrificial board underneath.

[NeverDie]

I've confirmed that A5 and GND work correctly for the auto-leveling.

However, Chillipeppr strangely defaults to probe a much larger area than is needed for auto-leveling, so I need to figure out how to reduce the upper and right-hand boundaries of the probing area:

Otherwise, it runs the risk of not even hitting the PCB if it gets too far out.

[NeverDie]

Nailed it!

Well, further progress will have to wait until I can move the CNC to the garage or outdoors, so that I don't fill the house with toxic fiberglass particles (Thank you @executivul for pointing that out, and sorry I butchered your name earlier. I didn't mean to.)

[executivul]

@neverdie no problem, I got used to it since I'm using such a weird nickname, the good part is it's always free to register on any forum so all I have to remember is the pass.

I'm really excited about wet milling, it's freezing down here and not having to have windows open for the modded vacuum cleaner it's a treat. The trick is to use a solution with higher surface tension then water, but not too thick or it will gather around the mill as a small tornado and start splashing everywhere. You can use soap, shampoo, dishwash, carwash, etc. Start at 1:1 water mix and add more water if it tends to gather around the spinning bit. It's better to pour it slowly on the board and spread with your finger (use a syringe) than to spray it as not to make foam. Also try using a clear shampoo to better see what's milling below the liquid. A piece of flat plastic, acrylic, lexan, plexiglas, whatever, doublesided taped to the wood spoilboard is a must unless you leave a large margin between the actual milling and pcb edge liquid will spill and will swell the wood. Have a roll of paper sheets nearby and a garbage bag open. Always use glasses when operating the machine. I made a "fence" out of some polycarbonate sheet to contain any eventual splashes which occur mostly when drilling through the board, normal engraving behaves and doesn't splash at all.

[NeverDie]

Given that the goal is to get 6mil isolatioin routing, what cutting depth should I set in flatcam? 0.05mm?

[dbemowsk]

@neverdie I have been kind of following this topic, but don't have a CNC mill, but wouldn't the thickness of the copper clad on the board be your depth?

[NeverDie]

@dbemowsk said in CNC PCB milling:

@neverdie I have been kind of following this topic, but don't have a CNC mill, but wouldn't the thickness of the copper clad on the board be your depth?

Makes sense to me. Well, doing that it would be 0.01mm. But since this isn't a perfect process, it likely needs some added depth to guarantee it's removed. The effective tool width gets wider the deeper you cut, so in some sense I suppose there's that as an added constraint on how deep you can cut before it becomes more than 6 mil isolation. We could try to arrive at an answer analytically from first principles only, but I thought it might be easier to just ask what depth others who are doing this successfully are using.

[dbemowsk]

@neverdie See what depth you need to go with that bit to get 6 mil routing, and that will be your max. I would think that would be more than 0.01mm, but I haven't seen your bit, so I don't know.

[andrew]

@neverdie you should use one depth, regardless of the trace width. for me 0.05mm worked, see my shared settings above. you should decide the isolation width, this is the main property for the given config, but you should stick for one milling depth only. if the requires isolation width is bigger than the tool width at a given depth, then it will use multiple rounds to reach the given width, but still, with one milling depth.

[NeverDie]

I'm stuck. I converted my gerber to gcode using flatcam, and imported it into Chilipeppr:

On the one hand, it seems to have gotten the dimensioning right, as indicated by the Y1.48in and X1.43in. However, the grid that it's showing is out of sync with that. Each square on the grid is 5mm. It's as though Chilipeppr thinks the entire design fits easily inside a 5mm square, and so when I attempt to do the autoleveling, it comes out completely wrong.

[andrew]

@neverdie said in CNC PCB milling:

I'm stuck. I converted my gerber to gcode using flatcam, and imported it into Chilipeppr:

On the one hand, it seems to have gotten the dimensioning right, as indicated by the Y1.48in and X1.43in. However, the grid that it's showing is out of sync with that. Each square on the grid is 5mm. It's as though Chilipeppr thinks the entire design fits easily inside a 5mm square, and so when I attempt to do the autoleveling, it comes out completely wrong.

you can mark the zero point in the pcb designer tool before you export the gergbel, or in flatcam, during the post processing. if you do not define it, then maybe the given zero point could have some "offset" to the effective design. it is not problem, but it could make your life easier if your zero is e.g. at the pcb's corner.
if you don't want to update the files, then in chilipeppr you can update the probe area to not start from 0,0 but from a given offset.

[NeverDie]

Thanks! I don't know why, but somehow that fixed the problem:

[NeverDie]

I found these copper clad boards that seem to be made out of bakelite (?) rather than fiberglass. So, hopefully not the same level of toxic dust concern as with FR4's.

I double sided taped the non-copper side:

and soldered a ground wire on the copper clad side:

Now I'm ready for autoleveling and then my first PCB etch.

[NeverDie]

Here are the results of the autoleveling:

For some reason it's hard to read some of the numbers.

[dbemowsk]

@neverdie It looks like everything in the top right corner is above the level bed surface. which puts it above the grid that is shown. Looks like the bed is tilted.

[NeverDie]

@dbemowsk Fortunately the auto-leveling should render it a moot issue.

[NeverDie]

LOL, except that unfortunately it did not:

OK, my bad. I hadn't sent the auto-leveled g-code to the workspace (I had thought this would be done automatically, but no), so this picture shows what would happen without auto-leveling.

I've made the change and am now re-running the job with the auto-leveled g-code.

[dbemowsk]

@neverdie Looks about on par with your final matrix, only it is following the grid and not the auto leveling values.

[NeverDie]

So, I re-ran the job over the same area with the g-code modified by auto-leveling, and this time I got a better result:

So, now I'll try it on a fresh area of the PCB, after doing a new auto-leveling.

[NeverDie]

Judging from the looks of the photo directly above though, it looks like quite a bit of copper wasn't removed where it needed to be. I'm guessing I will need to:

1. etch to a deeper depth; and/or,
2. use a finer mesh for auto-leveling; and/or
3. ???

[executivul]

Etch 0.1mm. The groove between tracks also helps with soldering. I currently use 0.1mm and even 0.15 when in a hurry.

[rmtucker]

@neverdie
The last photo looks like the tip is missing from the cutter?

[NeverDie]

@rmtucker Good catch! Here it is in contrast to a new one:

I'll replace it with the new one.

[rmtucker]

@neverdie
Just for future reference i would use a duff cutter for autolevelling then change to a good cutter to cut the job after resetting the z0.
It is so easy to smash the front of an engraving cutter when using this method for autolevelling as the machine takes a little time to stop after touching the pcb.
Just my advice anyway

[NeverDie]

@rmtucker said in CNC PCB milling:

Just for future reference i would use a duff cutter for autolevelling then change to a good cutter to cut the job after resetting the z0.

What's a "duff cutter"? Did you mean "dull cutter"?

[rmtucker]

@neverdie
Yes sorry a used one

[NeverDie]

@rmtucker Thanks! Makes sense to me. I'll do it that way.

[NeverDie]

Argh. I ran the job, and the first cut went great. All subsequent cuts though didn't penetrate the surface:

Afterward, when I checked the zero on z, I found that it was off by 0.049. That explains it, since the cut-depth was 0.05.

I'll re-zero and try running the same job again.

[NeverDie]

That made a much better result:

It corresponds to this as the actual PCB:

[NeverDie]

However, what's telling is that it obliterated the traces on either side of a 6 mil separation:

This is how it should look instead:

So, what happened?

My current hypothesis: the first cutting sheared 0.049mm off the tip of the blade, making it wider than it should be. Then, after re-zeroing, the wider blade cut too wide as it cut the traces for the solder jumper.

Is that reasonable, or is there a better hypothesis?

If it's true, then what do I do about it? Perhaps use a higher quality bit than the freebie that came with the kit?

Actually, I'm not even sure what the dimensions were on the freebie. It wasn't labeled. Perhaps it was too wide to begin with.

[NeverDie]

Well, to explore this more, I think I'll create a test board consisting purely of a few solder jumpers. That way I can put the focus directly on the 6 mil issue and won't be wasting time on etching that's unrelated to that.

[NeverDie]

Doing just a single solder jumper, with the same bit, and autoleveling every 1mm, the result is:

which is pretty close, actually. Looks like maybe the bit is a little too wide, or else there's runout which is making it appear wider than it actually is.

I'll try it with a fresh bit next and see if it improves.

[NeverDie]

Well, that went horribly:

and I have no idea why:

[NeverDie]

I tried again with the same bit, after removing and re-inserting it. Got a better result this time:

Unless someone has suggestions on how to tweak this, I think that may represent approximately the best this CNC can do.

[NeverDie]

In truth, though, I think it may be a flawed gcode algorithm:

Instead of two separate cutting passes through the center section, one would do, and would produce a better result.

How to tweak flatcam to do that? I probably haven't configured flatcam correctly. i.e. user error.

[rmtucker]

@neverdie said in CNC PCB milling:

Actually, I'm not even sure what the dimensions were on the freebie. It wasn't labeled. Perhaps it was too wide to begin with.

Maybe this is where your problem lies.
How did you write the g-code without knowing?
Too many variables here wich could give you these results.
The bigger tracks,Are they measuring the correct width with a vernier after you have cut them?

[NeverDie]

I assumed the width on the freebies was 0.1mm, because that's what was advertised on Jack's posting for the machine. However, I don't know how to verify that, so the uncertainty comes in whether Jack actually delivered what was advertised or slipped in something else. I chose to give Jack the benefit of the doubt.

[NeverDie]

If I were to enter a wider tool diameter of 0.155mm (instead of 0.1mm) into flatcam, I think I can coax flatcam into generating better g-code for this situation. I'll do that and then post the results.

[mfalkvidd]

@neverdie have you verified isolation between the parts? The cut is good?

[NeverDie]

No improvement really:

I think this means that the effective cutting width is actually greater than that, either from the bit itself or from runout or from who knows what else.

Probably nothing I can do about runout, except buy a different/better motor.

I'll have to wait for the etching bits from Aliexpress to try what is maybe (?) a proper 0.1mm etching bit. Like I say, I have no way of judging whether the freebies that came with the kit really are that or not, as I have nothing to compare.

By the way, my reason for picking the 0.155mm tool width in flat cam is that it produces this g-code path, which should have preserved more of the copper pad where it was being obliterated:

[executivul]

Yes you can. Get the gcode I've posted above, adjust for your feedrate, autolevel it in cp and give it a go. Really curious about the results.

[NeverDie]

@mfalkvidd said in CNC PCB milling:

@neverdie have you verified isolation between the parts? The cut is good?

Good question. I have doubts about how well I could measure it using calipers. However, maybe if I put the board onto a flatbed optical scanner, which would have a known DPI, I could measure the actual cut width with reasonable accuracy. I haven't done that yet, though.

[executivul]

@NeverDie Using traces one next to other at known distance you can determine the exact width of the engraving for a wanted depth of cut. I know you don't want to mess with gcode, but it's simpler than you think. Please look at the code: you have init (g92 for setting zero, g21 for mm, etc) you set the feedrate in mm/sec, you have a few movements (g0) a "dwell" to pierce the copper for 0.5seconds (g4) then some cutting moves (g1) all have absolute cartesian coordinates. Eg you're at (0,0) then g1 x0y10 means travel at (0,10) move only the y axis 10mm to the back of the machine, g1 x0.1y10 means move 0.1mm to the right, etc.
You have the whole script posted above, set your feedrate the same as you set in flatcam, and set the depth in the first z-0.1mm line, maybe you want 0.05mm for eg. After editing the file run it in cp with autoleveling and post the results.

[NeverDie]

@neverdie said in CNC PCB milling:

@mfalkvidd

Oh, sorry, I realize now you were asking something else. No, I haven't verified that yet. This is all just early attempts. Good question though.

[NeverDie]

@executivul said in CNC PCB milling:

Using traces one next to other at known distance you can determine the exact width of the engraving for a wanted depth of cut.

OK, I think I see what you mean. In other words, when the two cuts just barely bleed into one another, then one can deduce the width of the cut as being the absolute width between the absolute coordinates of the lines it's trying to cut. Makes sense. I'll give it a try. Thanks for the suggestion.

[NeverDie]

Good news. I just received my model 2 bits from Aliexpress. Model 2 is 20 degrees with a 0.1mm tip. I compare it here to the freebie bits from Jack:

Model 2 is on the right, and Jack is on the left. Looks like the angle is wider on Jack, which I presume (?) means that the tip is wider than 0.1mm.

[NeverDie]

Well, I thought the model 20 would do better, but it actually did worse:

It does seem to cut smoother lines though.

[NeverDie]

I also received model 6, which is the variety pack that includes a 10 degree bit with a 0.1mm angle. Should I give it a try? I've read that they're prone to create flying shrapnel. Anyone here have experience with them? If it doesn't blow up, it might be just the ticket for doing this cut.

[NeverDie]

I just now tried the Model 10:

Rougher edges, but it didn't decimate the pads as badly as the model 20.

[mfalkvidd]

@neverdie sorry for being unclear. I was thinking of just using a multimeter in continuity mode to verify that there is no connection between parts that should have no connection.

[NeverDie]

Merry Christmas, @executivul
Here is the output of your script using a Model 20 bit:

[executivul]

@neverdie Marry Christmas!
What feedrate did you use? (F parameter) and what engraving depth? (G01 Z-0.1?)
The jagged edges make me believe your feedrate is a bit high for the used rpm. You can run the first gcode to determine the best feedrate, or just use something low like 200mm/min and maybe a little deeper engraving.
It seems that your engraving is about 0.25mm wide, the 0.1mm is clear, 0.2mm is clear, 0.3mm is partially clear, from 0.4mm onwards you see the spacing between passes.

[NeverDie]

@executivul said in CNC PCB milling:

G01 Z-0.1

I did it again with F200 this time:

Doesn't look like the autoleveling is working so well, even though I had it probe every 2mm.

I think I may try covering 100% of the back of the pcb with tape. Maybe spacing it out has created this kind of artifact.

Not that it matters, but here's how it looks in ChiliPeppr:

[NeverDie]

@neverdie Oops. It was F1400.00, which is what your script had. It must have overridden the F200 I had entered manually before running it.

[NeverDie]

Here it is again, after I modified @executivul script to be F200:

[NeverDie]

Here's something I've noticed. Before running the auto-leveling, I run a test probe and then zero everything out when it makes contact. After running auto-leveling, if I run the test probe again, it generally reads about 0.05 higher than where I zeroed it out after the first test probe before the auto-leveling. Meaning?

[NeverDie]

Wow! Here's Jack's bit at a cutting depth of 0.05 and a feedrate of 200:

Seems to blow away the Aliexpress Model 20.

[NeverDie]

Anyhow, I'm not sure what all this means, but 6mil isolation milling seems like a stretch, unless there's more that I can do to get there.

What's a conservative number for mill isolation that I can count on getting without having to fuss over it? @executivul was getting 8mil. @andrew was getting 6 mill. So, maybe I can bank on getting 12 mill for sure without much effort such that it "just works"?

[executivul]

@NeverDie
The last bit tested is under 0.1mm wide. WOW!
Remember to:
-pre run: set the autolevel probe limits and a speed of 25mm/s
-run the probing: and DON'T redo Z probing after autolevel, it messes things up, use the same bit for probing and engraving.
-post run: "send autoleveled gcode to workspace"
Go slower, 100-150mm/min, afterall you don't need 6mil traces for a huge board so time is not an issue here.

PS. try some water/shampoo mix, it kinda' helps with engraving, cooling, lube, I don't know.

PPS. I've moved to opencncpilot lately (last 2 boards), free on github, a short tut on the tube, it has a great feature that is to break long moves in 5mm segments, works better for bowed/wavy boards.

[NeverDie]

@executivul Do you cut everything in one pass, or do you use multiple passes (each pass at a deeper depth)? Flatcam supports multiple passes, though I have been using only 1 pass.

[NeverDie]

@executivul
Thanks for the tips. Here is Jack's bit again, this time at F100. Even better!

[NeverDie]

Here are Jack's etching bits: https://www.aliexpress.com/store/product/Freeshipping-10pcs-3-175mm-Flat-Bottom-CNC-wood-Router-machine-Tools-Cutting-Bits-Carving-V-Shape/424291_32718430291.html?spm=2114.12010612.0.0.6cc36820P3WAXu
It says 30 degree angle and 0.1mm tip.

[NeverDie]

Time to see whether this machine can cut the mustard or not. I just did a 5mm autoleveling on the following:

and now I'll try cutting it using Jack's bit.

[NeverDie]

Here's the result:

The above was cut at a depth of z=-0.1, and still not all the paths cut completely through. Yet, In the middle one of the traces got obliterated.

I'm afraid I'm unlikely to make it work at the resolution that I'm able get from the fab. It's close, but no cigar. So I think it's better suited for earlier prototyping work that's not so optimized for space. For that it might be very handy. Then I can both cut deeper and also not worry about trace obliteration.

[NeverDie]

By the way, do any of the programs have built-in verification after the cutting, where it can probe to verify that the trace is throughly cut (i.e. no continuity with ground)? Seems like it should be easy to do, at least in theory, by using a method similar to the probing for auto-leveling, except probing each track instead.

[executivul]

@neverdie Congrats for your result, I use a "copper pour" all over the board, that makes it pass at least 2 times, once for the track and once for the pour isolation. I never mess with flatcam's multiple passes, but I believe you can get the same results. What you see in the middle are copper "silvers" that is copper left behind between traces.
From the last picture of the width test is seems your bit is engraving 0.1mm wide.
Try to use OpenCNCPilot instead of Chillipeppr and set the lines to be split at 1-2mm lengths and probing each 2-3mm. That should make the engraving depth more uniform.
I see a couple copper flakes, maybe go even slower than 100? And give it a light sandpaper with 1000 grit or a scotchbrite sponge and some abrasive detergent for dishes?

[NeverDie]

@executivul Thanks!

For the convenience of others reading this thread, here's a quick youtube:
OpenCNCPilot relased - new Autolevelling GCode Sender for GRBL – 03:28
— martin2250

I'm surprised to learn that not all auto levelers do it that way, because it seems like the only right way to do it. I'll give it a try.

[NeverDie]

Well, for some reason when I connect using OpoenCNCPilot, it turns the spindle on at maximum speed. I tried turning it off with the command 'S0', but it had no effect. So, I manually disconnected the wire that powers the spindle. Surely, there's a better way?

Anyhow, after doing that, I notice that the motors are making a really loud shrill sound, even though they're not moving. So, something is definitely FUBAR the moment I connect.

I had to disconnect and then connect using chilipeppr to have it all return to normal.

Maybe @andrew can try it? Perhaps there's a workaround that's not self-evident to me, but perhaps would be to someone else.

[executivul]

@neverdie OpenCNCPilot needs latest grbl 1.1f

[NeverDie]

OK, I'll resume the search for my dragon....

Meanwhile, I should be receiving my CNC drill bits and routing bits (to cut the board outline) fairly soon. Will I be using Chillipeppr to do those tasks (I'm guessing so) or something else?

[executivul]

@neverdie I have an idea, why don't you open the gcode in Opencncpilot, simplify it, split long moves, save it and then open in chillipeppr and do the probong and actual milling?

[NeverDie]

@executivul Brilliant idea! Simplifying, the line count went from 3609 to 3608. Converting arcs to line segments had no effect. Then, splitting every 1mm, it went to 4114. I copied it into a new file, and now I'll see how it runs using chilipeppr.

[NeverDie]

Results look much better this time:

Using Chilipeppr, I probed every 3mm and then let it rip. As before, it was cutting at z=-0.1 and a feedrate of 76.2 (the feedrate wasn't a conscience choice but rather just what flatcam gave me, for whatever reason).

The good news is that it doesn't have the blatantly obvious trace obliteration that it had the first time. All in all, it looks like a definite improvement.

[executivul]

@neverdie Seems like it's getting better, still some traces in the middle are hairthin, maybe increasing tool size in flatcam a tad? like 0.12mm so it lets the tracks be wider. Bare in mind this is a prototyping machine, I use mine for low batch home automation boards, under 20 boards of the same kind, at the price of a blank pcb I can buy 10 for the price of one fab made 100x150mm, not to speak of wait time.

After you are satisfied with the board is time to get some plumber's paste for soldering copper pipes, that is used for tinning, or maybe you can find some liquid tinning solution, but that's more expensive here, I use the paste.

Then some soldermask and some uv led strips to make an exposure unit and there you have your own pcb fab at home

[NeverDie]

@executivul How much overlap in flatcam are you using? I've been using zero. Would changing it to something non-zero help, or is it irrelevant?

[executivul]

@neverdie I never do multiple passes, so overlap is irrelevant to me...

[NeverDie]

When I probe at 2mm, it often randomly fails with messages like this:

Moving to {x:12,y:28}
probe failed, clear controller alarm before resuming
Paused
Working on probe for {x:12,y:26} Found lowest Z:0.17499999999999996
Paused

What is causing these "probe failed" to happen? And how exactly am I supposed to "clear controller alarm"? It always seems that I need to disconnect from the serial port and then reconnect to get any further movement. But if I do that, it clears the x,y,z positions, effectively preventing any kind of sensible resumption.

[NeverDie]

Argh, it just happened again. This time when doing 3mm probing.

Moving to {x:12,y:27}
probe failed, clear controller alarm before resuming
Paused
Working on probe for {x:12,y:24} Found lowest Z:0.23000000000000004
Paused

How does it even decide that a probe error has happened?

[executivul]

@neverdie timing racing condition is f*king spjs, ugly hack is to try to increase probing starting height from 0.5mm to 1.0mm

[NeverDie]

It's hard to photograph these etchings. They actually look better by eye. I tested out the last one with a continuity meter, and it seems that it would be functional (in the sense that the traces were isolated from what they should be and they connected the pads that they should.

However, without the solder mask, I'm doubtful those closely packed micro-usb pads on the middle left near the edge would be solderable without bridging.

I really hadn't considered I would ever need to do solder mask, I guess because the demo boards I've seen other people make don't seem to have it.

So, maybe a better question is: what is the minimum isolation width so that I won't need solder mask? Perhaps that becomes the limit for prototyping.

Anyhow, I'll look into it, but I really hadn't planned on taking that extra step.

[mfalkvidd]

neverdie said in CNC PCB milling:

It's hard to photograph these etchings.

Do you have a flatbed scanner? Not sure if the copper reflects too much light, but the focus should be good.

[NeverDie]

They keep getting better!

I used a fresh Jack bit to get this one. The tip on the bit used in the previous etching was a bit worn down, which I think explains the undesirable width of its cuts. I also dropped the feedrate to 50mm/minute, which may have helped also. Anyhow, most of the cuts seem very crisp compared to earlier attempts. As before, I split the line segments into 1mm lengths using the OpenCNCPilot. I think that is probably helping a lot.

I did this one is two passes. The first pass was z=-0.05, and it didn't cut through enough of the copper. The second pass was z=-0.1, which is what you see above. Yet, some of the traces on the micro-usb on the middle left still don't seem fully isolated, so I'm about to try a third pass at z=-0.15

Also, this was the first job I ran with autoleveling set at 2mm. Perhaps that helped also.

[NeverDie]

I received my end-mill bits for cutting the PCB loose from the rest of the copper clad blank. Which got me thinking: since I have doubled sided tape on the back of the PCB blank, I presumably don't need mouse bites or similar, right? I should be able to just cut the board outline by cutting through to the sacrificial board underneath, right? Is that what others here are doing? Or are you milling tiny little supports that you break away at the end?

Regardless, what diameter end mill bit should I use for the task? What cutting depth? I'll look back to see if it's in @andrew 's list of magic numbers, but anyone else feel free to post what you like to use and do.

https://www.aliexpress.com/item/10Pcs-Set-1-8-0-8-3-175mm-Drill-Bits-Engraving-Cutter-Rotary-PCB-CNC-End/32774556522.html?spm=a2g0s.9042311.0.0.BShrFG

[NeverDie]

Here's what @andrew had to say:

edge cut or hole milling with the 0.8mm endmill:

feed rate: 170
z cut: -1.7mm
multi depth, depth/pass: 0.2mm

So, I guess by "z cut: -1.7mm", he likely meant that as a Z that's -1.7mm below the depth of the PCB? I'm not sure how else to interpret that. Hmmm.. I think he assumed the board thickness of 1.5mm, so he gave is 0.2mm more than that. Mine (being single sided) is 1.35mm, so I'll set cutting depth to 1.6mm, just to be sure.

Aside from that, 0.8mm end mill and multiple passes at a feed rate of 170. So, I guess I use flatcam to produce the gcode that conforms to this and then run it in Chilipeppr.

And, it looks like flatcam adds the cut-out supports automatically. Nice.

[NeverDie]

Argh. Another probe failure:

Moving to {x:4.430000007152557,y:19.430000007152557}
probe failed, clear controller alarm before resuming
Paused
Working on probe for {x:4.430000007152557,y:24.430000007152557} Found lowest Z:0.051000000000000156
Paused

even though I have it set to start probing at z=1.0mm. This really needs to be fixed.

[NeverDie]

Unfortunately, I botched the third etching pass. My fault. But I decided to try the board cutout anyway:

I didn't see a way for flatcam to do a circular cut-out, so I just went with the rectangular cut-out. Anyhow, it worked.

I receive my CNC drill bits on Friday, so after that I should be able to do a complete PCB of some kind.

[NeverDie]

@neverdie said in CNC PCB milling:

This really needs to be fixed.

I wonder whether increasing the priority of the tasks using the Windows task manager might help at all? Perhaps some background tasks are interfering and slowing things down to the point where cp can't keep up with real-time?

[executivul]

@neverdie there is a tutorial for custom board cutout in flatcam, "google it baby", it involves manually using open_gerber and follow commands. I'm on the phone and can't find it right now.
Regarding cutout I sugest you use 0.5mm depth and 100-150mm/min with 0.8mm endmill. Your spindle is pretty low rpm. I use 1mm depth and 300-400mm/min, 2 passes, 1.6mm thick pcb, about 40k rpm.

[NeverDie]

For those who are interested, this is the best solder mask tutorial I was able to find:
Green Solder Mask / Dynamask / Solder Resist on PCB's by Rembrandt Electronics – 08:53
— Rembrandt Lights

It doesn't look too bad, but I'd still rather not go there if I can avoid it.

However, this process doesn't seem optimized for people who are doing, say, .1mm etchings around their pads. I mean, couldn't one squeegee in the solder mask, uv cure it, and then remove what trace amounts might remain on the pads themselves by burnishing it off with a scotchbrite pad or something? I mean, for quick and dirty results that work well enough for prototyping, that's what I'd have in mind. Anyone try something like that?

The techniques on youtube for using solder mask goop aren't optimized for people who have veritable canals around their solder pads. Why not take advantage of that?