Hi all,
I've been betting frustrated by a problem with KiCad(ver 7.01) when I try to generate Gerbers it says "Zone fills out-of-date. Refill?" What does that mean? I can't find any answer that makes sense.
I've been betting frustrated by a problem with KiCad(ver 7.01) when I try to generate Gerbers it says "Zone fills out-of-date. Refill?" What does that mean? I can't find any answer that makes sense.
Perhaps it means, "Timestamp of zone fill operation(s) is earlier than timestamp of the most recent edit to tracks and/or footprints" ??
In other words, zones may no longer be synchronized to tracks and/or footprints.
My version of KiCad automatically re-generates all zone fills every time I run the design rule checker, so in my setup, running the D.R.C. (and discovering zero problems!!) would probably make that error go away. I've never seen that error myself so I've never had to "fix" it, however.
In other words, zones may no longer be synchronized to tracks and/or footprints.
My version of KiCad automatically re-generates all zone fills every time I run the design rule checker, so in my setup, running the D.R.C. (and discovering zero problems!!) would probably make that error go away. I've never seen that error myself so I've never had to "fix" it, however.
Mark's answer makes sense. I'd try refilling the zones and see what happens. Make a backup copy of the KiCAD project beforehand. 🙂
There were some file format changes from previous versions. The biggest change was from 5.x to 6.0, but I was presented with a warning about format changes when I installed version 7.0 as well. My project file was saved in ver. 6.x. It could be something related to the file format change that triggers that error. That should go away if you refill the zones and save the file.
Tom
There were some file format changes from previous versions. The biggest change was from 5.x to 6.0, but I was presented with a warning about format changes when I installed version 7.0 as well. My project file was saved in ver. 6.x. It could be something related to the file format change that triggers that error. That should go away if you refill the zones and save the file.
Tom
When I choose refill zones, it wipes out the existing ones that are nested within a larger zone. The weird thing is I successfully designed and had JLCPCB fabricate them for me but the wrong side of the board was black. In attempting to get the correct side of it black, something went wrong and when I submitted them for fabrication they said there was no copper on the board, even though they looked OK on my end. So after many frustrating attempts to fix the original design I decided to start all over. Now I can't even reproduce my original success, I keep getting the zones out of date message, and when I have it fill the zones, it erases them! ARGH! Can anyone tell me what that message actually means? What is it that is "out of date" I don't get it.
Mike
Mike
At one point 7.0.0 automatically refilled zones after any edit. This behaviour was changed so that a fill had to be called (DRC does this)
It is very important that nested zones have correct and unique priorities.
There was also a bug fix recently for zone knock outs, which on Windows you can try with a recent "Testing"
https://gitlab.com/kicad/code/kicad/-/commit/51dc2b109eccd0a279717e0613eebe060c805494
It is very important that nested zones have correct and unique priorities.
There was also a bug fix recently for zone knock outs, which on Windows you can try with a recent "Testing"
https://gitlab.com/kicad/code/kicad/-/commit/51dc2b109eccd0a279717e0613eebe060c805494
Well, as I stated, I was already able to design and have the original version fabricated with no problems except that it ended up black on the wrong side, I had assumed the entire board would be black. So in trying to fix it I managed to muck it up to where it was just a mess, so I started over from scratch with a completely new design, and now I can't even reproduce what I originally created.
The board I am trying to make will be a mount for input/output jacks on the back plane of a stereo preamp, with RF/EMI blocking surface mount components on the inside. So I wanted it black on the non-component side, with PCB text labeling the jacks for the user. The jacks are grouped for each input and output left/right pair, with a separate isolated ground for each input pair as an island inside of a larger overall ground pour. I'm sure it is something I messed up, but I can't figure out what.
Mike
The board I am trying to make will be a mount for input/output jacks on the back plane of a stereo preamp, with RF/EMI blocking surface mount components on the inside. So I wanted it black on the non-component side, with PCB text labeling the jacks for the user. The jacks are grouped for each input and output left/right pair, with a separate isolated ground for each input pair as an island inside of a larger overall ground pour. I'm sure it is something I messed up, but I can't figure out what.
Mike
Last edited:
Well...Just as I suspected, my problems were self inflicted. And in the interest of full disclosure, I am a total noob when dealing with CAD programs in general and haven't been messing with KiCad much until recently...as if that weren't readily discernable.
So, where I went wrong was not paying enough attention to the details...the reason I was having so much trouble was due to 1)Not fully understanding how zones worked, and 2)Failing to set the proper attributes for each zone; specifically, I didn't have "priority" defined.
Learning KiCad is like learning a different language when one has teethed on Windows functionality one's whole "computer lifetime"...it's been, how do I say it...Fun!
Thanks to those who replied, your input didn't directly solve my problem, but got me thinking in the right direction. I appreciate it.
Mike
So, where I went wrong was not paying enough attention to the details...the reason I was having so much trouble was due to 1)Not fully understanding how zones worked, and 2)Failing to set the proper attributes for each zone; specifically, I didn't have "priority" defined.
Learning KiCad is like learning a different language when one has teethed on Windows functionality one's whole "computer lifetime"...it's been, how do I say it...Fun!
Thanks to those who replied, your input didn't directly solve my problem, but got me thinking in the right direction. I appreciate it.
Mike
You're not the first one to be tripped up by the zone priority thing. We have a wishlist item for a zone priority editor (that would show all zones and their priorities at once), but it hasn't been built yet.
FWIW, the zone-out-of-date thing doesn't check a time-stamp, it actually does a fill in the background and then compares the results with what currently exists.
There's a checkbox at the top of the DRC dialog that says "Fill all zones before running DRC" (or something to that effect). So if you always run DRC before plotting (and you have that checkbox set) you'll never see the out-of-date warning.
FWIW, the zone-out-of-date thing doesn't check a time-stamp, it actually does a fill in the background and then compares the results with what currently exists.
There's a checkbox at the top of the DRC dialog that says "Fill all zones before running DRC" (or something to that effect). So if you always run DRC before plotting (and you have that checkbox set) you'll never see the out-of-date warning.
Yeah...I figured that out after shooting myself in the foot...then the other foot! But it's all good, I've actually gotten somewhat adept at getting things done, it just required paying better attention to the details...being somewhat lazy by nature I sometimes try shortcuts that turn out to be the long (wrong) way through it. "Some people" never learn. 😀
Mike
Mike
Circling back to the manufacturing issues: I've made it a habit to check the Gerber output with a Gerber viewer before I send the files out for manufacturing. Here's an online Gerber viewer: https://www.gerber-viewer.com/
I do this for a number of reasons. First off, it catches errors such as the "no copper" that you describe. I don't think I've ever had that happen, but I have had an error in a file name extension result in odd results with OSH Park for example. Secondly, I find it handy to look at each layer individually. I often do that in the layout tool anyway but I catch a few more non-idealities when I review the layers in the Gerber viewer. Using a Gerber viewer can be handy for verifying the solder paste mask as well. Just view the copper and solder paste masks together.
That said, I've had dozens of boards manufactured correctly before I started reviewing the boards with a Gerber viewer, so it's by no means mandatory. I just find it helpful. It won't catch "wrong colour solder mask" errors, though. 🙂 I'm surprised the board house didn't flag that.
Tom
I do this for a number of reasons. First off, it catches errors such as the "no copper" that you describe. I don't think I've ever had that happen, but I have had an error in a file name extension result in odd results with OSH Park for example. Secondly, I find it handy to look at each layer individually. I often do that in the layout tool anyway but I catch a few more non-idealities when I review the layers in the Gerber viewer. Using a Gerber viewer can be handy for verifying the solder paste mask as well. Just view the copper and solder paste masks together.
That said, I've had dozens of boards manufactured correctly before I started reviewing the boards with a Gerber viewer, so it's by no means mandatory. I just find it helpful. It won't catch "wrong colour solder mask" errors, though. 🙂 I'm surprised the board house didn't flag that.
Tom
Or just imagine you are a lone engineer working for Maxim/Analog_Devices and any errors you let through, are going to cost the company 1E+7 dollars (chip mask sets ain't cheap) and you will be fired.
Yeah... I take that approach too. 🙂 Even if a screwup only costs 2.5E+2 dollars it's still a waste of time and money. There are few things I actually hate but waste is one of them.
Tom
Tom
KiCad has a fairly good built in Gerber viewer. I actually use it to check gerbers generated in other CAD tools. I have found the transition to KiCad 7.0 a bit more challenging than expected. V7.01 fixed some of the issues. I have been using KiCad since V4 or so. Great improvement in usability.
Just to be clear, all of the issues I had were my own damned fault, and to their credit JLCPCB has been helpful in sorting things out. I have submitted two more boards for fabrication and don't expect any more issues. In addition to the Gerber viewer, I also like to view the board as I build it with the 3D viewer.
Mike
Mike