There is no automatic hatched fill. If you want something which looks like a hatched fill you will need to manually place cutouts in your fill outline.
That will work, but every time you make a modification to the wiring you have to remember to create the hatched fill zones again. Unfortunately a hatched zone is not high on the agenda either so there’s no telling when (if) it will be implemented. It’s not something which is trivial to implement either.
Hi! My first post here! I’m one of the “victims” of the videos Chris released some time ago. Got into KiCad and i guess i’ll stick with it, as it’s getting better and better in time. In my last board design i also wanted to use a few capsense buttons and encountered the problem of generating hatched zones. I used the free version of Diptrace to generate them. Apparently, despite the pin number limit in the free version you can still import a gerber layout and use an automatic pad detection, even if it has more than 300 pads. The board i was working on had over 500 of them.
Anyway, here is a photo tutorial on how i did this. Hope it will help some of you. I’m using windows, but as far as i know there is a Diptrace version for linux and os x, so it should work on these platform too.
I created a simple cap sense buttons project in KiCad:
Now, you could import the gerbers directly into KiCad, however, since there is no way of grouping objects, they will appear as separate tracks, not really handy if you plan to do some changes to the rest of the board or even to precisely position the zones on the board. Preferably the zones should appear as separate objects. The next steps are similar to the previously posted tutorial. Load the gerber file into the Gerbv viewer and export them as an SVG file:
8.Use the KiCads bitmap converter to import the zones as a silkscreen objects and use any text editor to move the objects into the copper layers (leaving out the reference/value):
Since there are no pads in the component,it can’t be assigned to any net. I ended up adding a large rectangle smd pad at the border of the zone to connect it with the rest of the solid gnd plane:
This is just an example board i do for the purpose of the tutorial. Unfortunately, in my main design, much more complex one, i found out that the imported zones were causing KiCad to crash every time i refilled the native zones. I ended up moving hatched zones away from the board for any editing. When the rest of the board was finished, zones filled up, i moved hatches back where they belong using the previously written down coordinates.
Here is the end result:
Hi,
Thanks for all this great guidance. I used a combination of these methods to create top and bottom hatch planes for my project. Everything seems to look good except one thing I noticed. In the Properties sheet for my bottom hatch, under Board Side, Front is selected (although I set the layer to B.Cu using a text editor on the .mod file, and it does appear as a green object and hides when I hide the Bottom layer, as you would expect). Selecting Back on the Properties sheet inverts it, turns it Red making it part of the Front layer. So clearly I don’t want to do that, but should I be worried about this attribute being backwards? I did scan through the .mod file for the hatch, but see no clues there.
Thank you to Gerd V. Egldy (via @VinayDand) and @PzP for the diligent documentation on your methods. I don’t know how I overlooked this missing feature for so long. Now that I’ve had reason to apply hatched fills (yes, one of those picky CapSense sensors), this thread has been crucial.
That all said, I abandoned both the documented solutions! Trying to maintain control over edges and dimensions between vector export, rasterisation and re-vectorisation through 4 separate software tools just became too much. And the result is too difficult to tweak, due to the prolonged edit-preview cycle.
In the end I drew it by hand, all in KiCad. KiCad’s trace drawing behaviour is definitely not ideal for this, but actually helped surprisingly well. Being able to set a grid, copy and paste, still get track snapping, and work directly on the PCB allowed consistent, albeit arduous, progress.
See attached for the result. Like with painting, all the hard work is in the cutting in. Doing so with straight edges was probably the biggest limitation, but if you’re willing to have a bit of arbitrary aliasing in your “curves”, it’s fine. Zoom in to see the details.
The development branch is currently at what is known as a “feature freeze”, meaning that (except for a couple well documented (for the developers, of whom I’m not a member) exceptions) there are no new features being developed for the targeted 6.0 release. So all (most) of the current development work on 6.0 is crushing bugs. The hope is that they will start releasing Release Candidates for 6.0 early next year.
It would be great to be able to set the fill hatch pattern right here in the properties so I can have solid grounds on all the board but hatched ground areas under the capsense buttons.
It could be handled like like style formats in a word processor. I can predefine and name my hatch styles somewhere and then select it’s name here in the fill property.
Only zones can be hatched. It’s of course complicated if you need a circle, but I doubt it’s really the case. A four corner polygon would be fine enough.
You might ask your fabricator if he can crosshatch your copper pour. It might well be that he prefers to receive the simple solid fill and crosshatch on his CAM system rather than receive the large and complicated crosshatched Gerbers. Or he might not.