Hi, sorry for the confusion. I will ask internally for the most up-to-date information and change the article accordingly. I maintain most of our documentation, and sometimes things are missed when updating it simply due to the fact of how many articles there are.
What I can say already is that our final/processed thickness has a variance of ±10% which is a typical value in the industry.
rgd docs: yeah, I totally understand, lots of work. I also have some to maintain;)
fwiw, because of the “outdated / incorrect” issue, nowerdays I usually generate docs from code. and then maintain and CI test the code. this removes a couple of traps and work.
in an ideal world, I’d git clone an Aisler GitHub repo with OSS Python code for both the stacks and materials definitions …
would be interesting to hear your thoughts, what are people/pros in the hardware community usually do? I mean with all this PCB stuff. I am a SW eng. and HW is a complete new world for me. so pls excuse my maybe silly questions;)
I, personally, like to document things using Markdown. The forum format has been chosen before I started my job here at AISLER, mainly because it is easier to engage with people and get feedback directly.
Markdown is great! Standard flavor or GitHub flavored. The latter is even better. And yeah, engaging people is super important I absolutely agree. I am using it a lot as well. On GitHub and for doc centric stuff, including for generating other formats (PDF…, RFCs, …), but I probably use Sphinx even more, I am just a Python guy;) But I’m using it even for non-Python, or even business oriented docs as well. Love being able to just use/embed Godot and the kitchen sink;)
fwiw, here is a glimpse of the Aisler stack stuff as I am using it
One more Q: does Aisler offer impedance testing - in general (for production runs) and/or for prototype runs (“Beautiful Boards”)?
I could add a microstrip transmission line isolated/separated from the actual stuff onto my PCB, and then verify and know for sure if my assumptions add up based on values measured by Aisler for a “known target” (the microstrip line designed for 50 ohm or 100 ohm).
“Continuous Testing” fully automated, always and end-to-end is a standard best practice in SW development these days. I’d love to do that with HW as well …
here is another discrepancy: the KiCad PCB template at
has yet different values than the PCB stackup docs here - for both Dk of core, and for Dk of solder mask, and it seems to use the raw/unprocessed copper thickness, not the processed thickness
Hi, I will notify you when I hear back from the manufacturing people. We do offer impedance testing on production runs, but not when using the prototype pools. Single design panels can be controlled much tighter than the multi design prototype panels.
I believe the best software analogy would be that some tests cannot be implemented in a software container, and only be tested on the actual embedded device.