How can a component or trace be marked (given an attribute?) that can be accessed in layout for special handling?
1 Like
Symbols/footprints have fields which you can use. Symbol fields are propagated to the corresponding footprints and you can use them in footprint texts.
Other items don’t have such attributes.
I think that is a really great idea.
In same way that in a component we define footprint (size, pads, etc) can be good a good definition for the future tracks.
Netclass: QuadSpi
Width: 0.169
Cleareance: 0.350
tolerances: 5mm (distance when the width/cleareance can be override.
impedance: 90ohms
Not only color and dot.
I like your idea, too. But, I actually want to mark a net to be a wider trace that won’t be in a plane.
Track widths are normally handled via net classes. This is a standard feature of any decent PCB design program.
Dear Paul,
Yes, net classes do part of the job. Still is missing a “tolerance” or transitional net classes to be used on some part of the tracks, for example when the tack go into the qfn chip. (Altium has this functionality)
For example the first 3 mm from chip the net classes attributes are XX, after that the attributes are YY, or max length allowed for net violations etc etc.
Many times very small footprint has greater currents (more track width), or special tracks (with high cleareance) and Kc need tollerate a ZZ rules violation (between margins)
In KiCad you can override the net class settings when a track is routed for example inside a courtyard with custom rules. That would give you pretty comparable results compared to that other program.
I know, but inside courtyard is another thing. On a Qfn or Lqfp the tracks leave the courtyard very close to be separated.
For this, i insist in create a ZZ lenght of fail tolerance
2 Likes