Maybe I was a bit too dumb about how this works? Since I can’t get anything out of the interactive tuner. All the guidance I have is the syntax help in the editor which doesn’t seem to help at all.
DRC (obviously the rule is violated, the track is not long enough for 58~62mm constraint. Either the rule is incorrect or the topology detection is broken but it is never meant to fail silently):
Also X-Net in a more general meaning also includes this “signal goes across coupling capacitor” thingy, which is common on high speed differential signals. These are real world scenarios that needs to work (and me as a bugfix contributor can’t even figure out). If this is a production-ready feature it needs more documentation as this feature is SUCH a quality of life feature for layout.
Fix to get auto front + back annotation with no force for user to be very careful and click click click click to not easy destroy designs like now. If need to check good function see old cadsoft eagle.
I have hacked my way into creating net ties on internal layers, and there seems to be some interest from others on the forum in a proper way to do this. One example case for it is for tying two ground zones together. A ground zone is likely to be on internal L1 in a 4 layer stackup.
Net ties are symbols corresponding to footprints (at least in 8.08) and footprints produced by the footprint editor can only be on front or back layers. I can see that there is a challenge for the footprint editor to be able to do as I am suggesting, unless it is also capable of putting other footprints on internal layers.
Perhaps net ties need to be separated from other footprints somehow; created with a different tool. Or perhaps just a (NOT DEFAULT!) check box indicating that the footprint is a net tie which is on an internal layer.
Will it be possible to get internal layer net ties in version 10?
It should be no room for mismatch between schema and printed circuit board. Check the old cadsoft eagle if you wonder – very easy to add + delete schematic sheets, nothing can go wrong. Also very simple to save project to new project. Etc. Pls do not get angry if I say “eagle” here. it is just an example.
The title is misleading, it seems to suggest that wishes posted here will become reality. This topic is just a long talkfest. At least some wishes got written up as issues, and some got pointed out as already works.
I think that’s OK. It is often useful to discuss ideas before making them an official feature request. It helps to refine them. Or it might be that a requested feature already exists. Or maybe a suggestion would have unwanted side effects. There’s nothing wrong with discussing these things.
Exactly,
Sometimes people come up with an idea but it’s the incorrect request BUT a collective discussing can change what is requested.
For example… what I would like to see is the ability to cut back copper from the edge of the board when it is defined by the footprint, IE the pads.
Take the classic M4 PTH mounting pad, if this overhangs the board edge or is too close to the edge w.r…t copper to edge what do you do?
Move the pad inboard
Custom pad to draw a chord
Ask the fabricator to cut it back
4…
I am facing this right now in XPEDITION where there is a SLIGHT chord created and mechanically it is ok and XPEDITION cannot cut back so we need to negotiate with the fab as part of their process to cut that back. It would be great if Kicad could perform this activity
One thing out of many things that I would like in KiCAD is that when I load an old schematic/circuitboard it does not load the parts from the current library but keeps what is in the schematic.
I do not use the KiCAD provided libraries and draw my own but overtime these might/will get updated so components change because of an error or just a better way of placing the pins for instance.
But when I do load an old schematic it unfortunally loads the updated part(s).
I know I can export components and such to a local library but that should not be necessary.
Ooh man, would it be nice to have CAD like boolean operators in the footprint (and PCB?)!
We do already have boolean addition in pads (say I want a Mickey Mouse pad, I can make pad1, add circles, and use ctrl-E to combine):
straight to:
But boolean cuts for example still lacks, let’s say I want a pacman pad, I make a circle pad, define a triangle… how do I cut this part off without making a full zone myself?
to this (edited in paint, because KiCad doesn’t have it yet afaik):
@PimvH : It’s very sad, but you will not get this boolean operation as a new feature in kicad v10.
But to give you some hope: maybe the existing already implemented feature is enough for you: select two polygones–>RMB-click–>context menu–>Shape modification–>merge/subtract/intersect shapes.
Regarding the original topic of this thread: variants. The last really missed thing: natively implemented variants.
Caveat - I am pretty new to KiCad so some of these may already be included, or massively too complex.
I use another program for PLC programming and they have implemented a Library which is populated with known configuration, this is user and company supported, things like templates for Modbus devices or RS232/485 commands etc.
In KiCad how about a library for reference designs for typical or less so schematics?
ERC exists but how about overall design review in place, ERC, EMC, optimal layout, likely errors we might have made etc - Maybe KiCad 20
Easy roll back or re-save to the last version - I know, I need to be better at saving a copy between versions but I did not find my 9.0 issues until I had gone several hours
in.
Going back to the PLC software, If I Program in 12.6 and I am currently running 16.9 I cant work on 12.6. There is an expected norm that I will have multiple installs of the software, currently running around 12 versions there and I have a launcher to pick which version I need for a given site. works well, updating buildings in the real world to the latest FW has rarely proved a good idea - unless the new features are suddenly mandatory!
Double “heart” to this. Thanks for the tip for boolean shape intersections.
And I agree to the native variant support, we currently use it quite heavyly in the company with Altium and I would love to have it directly supported by KiCad as well.
Also I would love to have true support for polar coordinates. While you CAN do basically anything with cartesian coordiantes even on circular boards, it would make even distribution so much more user friendly. It would avoid the manual conversion and frickling around.
The title is misleading, it seems to suggest that wishes posted here will become reality. This topic is just a long talkfest. At least some wishes got written up as issues, and some got pointed out as already works.
