First, DRC issues a warning saying that you can’t assign two names to a single net (makes sense, I suppose). Then I get an error because Bar is undriven (which is clearly and obviously not true).
I’m not certain, but I think this might even be why the DRC check on the associated PCB keeps complaining about an “unconnected track” which is clearly and obviously connected.
What do I have to do to make KiCAD stop complaining about this? Surely wanting to use two names to refer to the same signal isn’t exactly unusual.
I think the situation is still that you will have to use a net-tie between Foo and Bar. Search for “tie” in the symbol library. Its function is to connect two different nets.
First, you could learn to read, or failing that, just post the exact message.
I’m not trying to be rude here. Maybe English is not your native language, you were tired at the moment, a brain fart of any of another plausible reasons.
So I made a similar screenshot below.
In the ERC box, KiCad is not complaining you can’t connect labels, but it just informs you that you did connect different labels together.
If you don’t like these “warnings”, then you can simply right click on the warning in the ERC window and select the: “Ignore all [of this type]” messages.
In ERC you can simply right click on any ERC message,
I also get an: Error, Input pin not driven, but this message is about a completely different pin. In my case it’s about pin 1, which is indeed open, and input’s should not left open like that, so KiCad is right to complain. KiCad has the “No Connection Flags” to explicitly tell KiCad you left pins open by choice and have not forgotten about them, and this is a useful feature.
It was quite tricky to get this screenshot, because this problem also appears to make the KiCAD crash during the check. I have to repeatedly reopen the app and rerun the check until it randomly runs without crashing.
It seems putting a “NetTie_2” component between the labels makes the check pass without errors (and without crashing KiCAD!) But now it’s complaining the component doesn’t have a footprint. Is there a way to say “just put a wire here”?
The error-message in your picture (observe: no error, only warning!) is only a information. It’s very well allowed to connect labels together, but Kicad informs you about this (as was already written by @paulvdh). You decide if this was intential (ignore or accept the warning) or a drawing mistake (than correct the mistake).
Regarding the crash: If you have really a reliable crashing project than we would be interested in the archived project. Only with such examples bugfixing is possible.
It warns about duplicate net names, which is fair enough I guess. But it also claims that one net is undriven, which is false.
Regarding the crash: I had assumed it was upset about the duplicate names (since fixing that seems to make the crash go away). However, I tried to build a minimal example to reproduce, and it doesn’t crash. Not sure exactly what’s triggering it; if I do find a reproducible example I’ll let you konw. (I thought I saw something in the release notes about this bug being fixed, but it appears I’m mistaken.) Note that I’m using KiCAD V6, which isn’t even the latest release.
