Does that mean I cannot have two signal layers next to each other, such as [plane - signal a - signla b - plane][? I think this is reasonable because when two signal layers are directly next to each other, there will be inductance between them, which could cause serious interference. Is that what you what is "severe restrictions" about?
It is unusual that all traces on a board are impedance controlled. Usually only extremely fast digital signals or analog signals have this requirement. For example, on an 1152 pin Xilinx Virtex 4, (hundreds and hundreds of i/o), a common design would only require the Rocket IO or LVDS pins to be impedance controlled. In that case, only one or two layers out of a potential 12 layer board would be impedance controlled (and need accompanying plane layers). Alternatively, you can always insert an extra plane layer to get the number of layers to an even number.But if all signal layers needs to be "sandwiched" by internal planes, then a consequence is that the layer stack must be arranged like:
layer 1 (top)
___plane 1
signal 2
___plane 2
signal..
___plane..
..
___plane k
layer k+1 (bottom)
and there will be a total of 2k+1, odd number layers. This is of course not the fact since all boards made from double-sided copper pads which after fabrication would always result in even number of layers. What is the mistake I have made here in the reasoning?
2. As far as I know the most common substrate material should be FR-4, which has Er typically between 4 and 4.5 So do you mean to use different substrate made from different material? Or, to vary h in the formula, which means to vary core/prepreg thickness. Is it possible?
3. Polygon pour
We have a classified transmission lines to two types here 1)microstrip, which is on top and bottom layers 2)stripline.
But when polygon pour (connecting to GND) is used on the external layers, can we still regard it as microstrip which has an immediate plane layer below it? Do we need to take the poured polygon, which is of considerable area, into consideration?
And if polygon pour is used for internal signal layers, does the “stripline” formula still valid?
What about DDR2 interface? These lines spans four layers on the board I am referencing, so I think all these four layers needs to be impedance controlled?Usually only extremely fast digital signals or analog signals have this requirement. For example, on an 1152 pin Xilinx Virtex 4, (hundreds and hundreds of i/o), a common design would only require the Rocket IO or LVDS pins to be impedance controlled. In that case, only one or two layers out of a potential 12 layer board would be impedance controlled (and need accompanying plane layers).
I didn't quite get what "second layer" "layer three" here refer to. There seems to be some ambiguity when referring to these layers. Does "second" layer mean the second signal layer, or the second physical layer? The same question applies to "layer three".Even if you have no traces on the second layer (the plane being on layer three), potential dielectric discontinuities between layers 2 and three could affect the desired impedance.
Do you mean "split plane" by "broken planes"? I am using Altium Designer and it allows to cut internal planes to several regions, which they call "split plane"s. For example, GND plane could be cut to GND, GND_DAC, GND_ENC and so on, and power plane could be cut into VCC_3V3, 3V3_DAC and so on. And of course, these regions are separated by lines on which copper are removed. Do you mean that if transmission lines on adjacent signal planes cross (have their projection) these separations lines between different regions on a power plane, there might be nondesirable effects?It is best to use unbroken planes in areas where transmission lines live. Discontinuities at plane boundaries result in nondesirable effects.
+1 on this. normally you adjust the line width so that it will match your impedance requirement.It is unusual to say, "I want a 5 mil trace to be 50 ohms."
Yes this is really common. I usually use this material.As far as I know the most common substrate material should be FR-4
It is common that you use necking on the BGA and neglect its impedance requirement until it reaches the outside of the BGA.I am fanning out from a tight BGA, exactly the case.
According to your experience, does PCB designers usually put impedance control information in Gerber file as textual information, or specifies them when they are routing in the PCB editor?
According to your experience, does PCB designers usually put impedance control information in Gerber file as textual information, or specifies them when they are routing in the PCB editor? Which is more common?
So when we opened a PCB file, we might not need to take the track height, core/prepreg thickness, dielectric constant information seriously. They might actually be nothing but only the default values assigned by the particular EDA software (Altium, Allegro, etc.), having being ignored by its original designer in favor of specification in Gerber files, and are only typical values filled in by EDA software for most common tasks such as two-layer low-speed design.
Therefore, the only authentic information about material and impedance of a particular board, if that is obtainable, is the Gerber file. So if this reasoning and conclusion is true, then it solved my question in the first post of this thread that why I got different \[{Z}_{0 } \] from PCB and Gerber information: the PCB data are software's default information and are irrelevant.
When you use necking, can you still ensure that the tracks' characteristic impedance be the same everywhere within its length? It seems to me that necking is suitable only for non-critical low-speed signals. When the speed is high and if you use necking, how can you eliminate reflection?It is common that you use necking on the BGA and neglect its impedance requirement until it reaches the outside of the BGA.
Isn't the copper foil glued to the layer next to it? Where does the gap come from? Does it has anything to do with the thickness of the glue when it has cured?a big effect on the line width is the gap between the copper foil & the plane layer next to it.
If you have high speed tools such as a router and Signal Integrity tools you also require the stack information for these to work correctly, and if you are doing high speed design that requires controlled impedance it wont be long before you require these tools to take the guess work out of design.
Isn't the copper foil glued to the layer next to it? Where does the gap come from? Does it has anything to do with the thickness of the glue when it has cured?
hobbss:
Is .dxf an AutoCAD format? Did you use AutoCAD to draw it or other software?
hobbss said:Furthermore, unless you want to greatly complicate your math, the dielectric thickness must be the same on either side of the layer in question.
KAK said:after choosing your board thickness you can use a stack up manager like POLAR and choose the desired thickness of every material in the stack up. Copper foil, core & pre-preg.
Iit's the dielectric not the glue, just what hobbss said.Isn't the copper foil glued to the layer next to it? Where does the gap come from? Does it has anything to do with the thickness of the glue when it has cured?
There are times that necking is inevitable. this is due to the pitch of the bga. that's why you need to limit the length of the thinner line width.When you use necking, can you still ensure that the tracks' characteristic impedance be the same everywhere within its length? It seems to me that necking is suitable only for non-critical low-speed signals. When the speed is high and if you use necking, how can you eliminate reflection?
I use gerber file. I'm using PCAD to generate the file.What is your file format? Which software did you use to generate the file?
symmetry is better. I never used assymmetrical in any of my designs. but POLAR can handle assymetric but I never tried that.hobbss suggest using symmetric plane thickness to not involve complicated math, but from KAK's description it seems that POLAR handles asymmetric case? Is POLAR's calculation accurate with asymmetric configuration?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?