Hi all,
I’m currently working on trace length matching in KiCad and ran into an issue. When I use the Tune Track Length tool, it only selects individual segments of the trace instead of the entire routed path. This makes it difficult to tune the full length accurately.
Is there a way to make the tool consider the entire trace for length tuning?
Thanks in advance!
I don’t have a direct answer, but there is another active thread about this topic:
Make sure the routing path is clean - there’s no stubs or overlapping segments. Also it’s best to attach an example project so others can look at it.
The issue is that when using the length matching tool, the trace is split at via transitions, and the entire net isn’t selected as a single continuous path
Check that there are no extra track segment stubs connected to the vias.
Also make sure they aren’t locked.
Is this related to removing stubs? The issue, as I understand it, is that the vias are assigned to a net, but they aren’t being selected as expected.
some via are not getting selected with trace selection.I retraced two of them, which allowed the entire trace to be selected. However, for the rest, repeated retracing isn’t making that possible
Also, in V7, When placing a Via into a Track, the Track gets Split into segments and cannot be tuned as a Whole Track. (Does not matter if the Tracks/Via is assigned to a NET.)
Widening the Track does not help. Deleting the Via, thus leaving segments can be Tuned.
V7 experience is not very relevant here.
It’s hard to tell what’s going on here, I recommend posting an example project if possible.
That is a very narrow-minded opinion.
The OP did not specify what version OP is using.
The ‘problem’ existed before v8,v9.
The ‘problem’ (if wanting to consider it a ‘problem’), like many other ‘issues’ in Kicad, gets carried over to the next version and not addressed. Thus, as a User, ‘I do’ consider it Relevant and is a ‘typical’ reason for my Not updating Kicad beyond v7 (which, does everything I need it to do).
And, I’m also a ‘Programmer’ and if I wanted to fix a Bug, it would be helpful to know at what version the Bug started thus, helping to identify the cause.
Lastly, you (@dsa-t ) could have spent 30 seconds making a Track, placing a Via and seeing what happens with Tuning. If it works correctly for you, then you could Post why it works and what ‘we’ could do to get it working, too…
Thus, you underscore my point about knowing at what version the ‘problem’ started and it’s being helpful info.
Sure, it’s helpful if the problem is a regression.
@BlackCoffee I doubt this is a problem in the OP’s case. Plus, what you show on the video breaks the proper connection between the via and the tracks.
This looks like this known issue in v9:
It might but, that depends upon what ‘the proper connection’ is supposed to be.
My opinion is, if the Via contacts the desired Track(s), then it’s a propper connection…
The track end/start points should match exactly with the via center point, otherwise various algorithms will not work correctly.
Ignoring the centered endpoint issue that @dsa-t has highlighted, the tuning tool won’t work through vias. The length calculation should (see bug I highlighted above, which is the issue which started this thread), but the tuning tool can only work on a single segment. That includes segments on the samle layer that are connected with stub vias, as in this example.
Yes, and there are other factors to consider, too ( and many are unstated in this (any) topic). It should be obvious that if a User is Tuning a Track, then the User must realize Resistance changes with removed copper for the Via and Hole… a list can grow… But, that does Not mean a User can’t know this, and thus, do tweaks to add Back missing Copper and do other tweaks…
Engineering is Not an iPhone where you can push a Button and blindly accept the Outcome
