I was used to Eagle. Where you create a net and add wires to it. But Kicad just goes a bit differently. Does the same thing. I
The simple reason is that, architecturally speaking, each pin must be in a net. Attaching labels to a pin does not “create” a net, it just renames it. The net list is a list of all the pins in a design, whether or not those pins are connected to other pins. There are valid reasons to want single-pin nets (for example, antennas, capacitive sensors, etc)
1 Like
Without seeing the project files before and after the edits and a detailed explanation of what happened vs. what was expected to happen, I can only guess.
My guess is you had some nets with automatically generated net names assigned to specific netclasses and/or zones. Then after making changes to the schematic new automatically generated names were given to the nets and PCBNew got lost. If you need to assign a specific netclass or zone to a net, best practices are to manually name the net using a label.
@Andy_P and @eelik - Can we kindly stop the nitpicking arguing about nets vs. wires if we agree that “wires” are a subset of the “net” superset? Getting down into those weeds does nothing but further confuse @jimmi who is trying to get a grasp on the basic concepts.
3 Likes
Are you using KiCad 6.0.3? There was a nasty bug in 6.0.3 that could be causing your type of problem. If so, update to 6.0.4 and see if that resolves your issues.
1 Like
I got sucked into Kicad 6 too and got grief
Connections in schematic aren’t all transferred to PCB ratsnest. Pads that are connected in Schematic aren’t connected in PCB and show as no net.
Deleting and replacing a symbol sometimes fixes the net in PCB
If there is a junction on a net in Schematic there is no hope of a net in PCB
Global labels don’t connect in PCB as well
Net labels aren’t reliable either. Connect in PCB sometimes and sometimes not. Think it is related to the junction problem
All seems to be related to some tie up between symbols footprints pins pads and nets
Updating Schematic from PCB does not work
Kicad 6 is basically unreliable currently
The work around is to export nets in Schematic and import nets in PCB Seems to work on a small sample of instances
The net function seems to be depreciated in Kicad 6 for reasons unfathomable
PCB DRC is pretty scrappy too. Doesn’t catch all errors
Copying symbols in Schematic isn’t so good now too. Changed to ctrl c and ctrl v. Not a convent as previous where just pressing c copied a symbol ready to place.
Probably not a good idea to use 6 for anything that matters in it current form.
Which exact version do you have / had when you had those problems?
Could you show us the version info from:
Help → About KiCad → Copy version information
It sounds like you may have the broken 6.0.3 which was recalled
OK Thanks Yes it is very broke
I gave Kicad 6.0.3 a go on a process machine running under Ubuntu 18.04
Didn’t play nice at all
Actually thought I downloaded 6.0.2 Must have caught it on the change over
I’ll have a look in due course for a version that isn’t broke and maybe give it another trial.
Thanks
6.0.4 was released quickly to replace 6.0.3, it does not have the bugs that happened in 6.0.3
If recall correctly, v6.0.3 windows installer was not added to the download page at all (or sit there for several hours only, so I didn’t spot it). This serious bug was reported at early release of kicad version for linux (and maybe mac) only. Linux installer of v6.0.3 was available for day or two, but sadly, ubuntu autoupdater got that for many linux users.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.