Don’t make assumptions. Also if one runs a debian version that does not supply the current stable version, there is also no nightly version for it.
Rene, please look at my screenshot … clearly the netlist created a BOGUS entry for pin 22 connected to pins that is not even connected in the schematic ! Its right there in the screenshot. I cannot make this up !
Oh Lordy, so the compiler crashed with an “internal error” roundabout at 43%
Seems to have afound a rat in the Ratsnest LOL.
"
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
common/CMakeFiles/pcbcommon.dir/build.make:765: recipe for target 'common/CMakeFiles/pcbcommon.dir//pcbnew/ratsnest_data.cpp.o’ failed
make[2]: *** [common/CMakeFiles/pcbcommon.dir//pcbnew/ratsnest_data.cpp.o] Error 4
CMakeFiles/Makefile2:595: recipe for target ‘common/CMakeFiles/pcbcommon.dir/all’ failed
make[1]: *** [common/CMakeFiles/pcbcommon.dir/all] Error 2
Makefile:137: recipe for target ‘all’ failed
make: *** [all] Error 2
The only screenshot I see does not show enough of the schematic to be able to determine how you managed to make those connections. But instead of blaming Kicad you should be looking for your mistakes. The screenshot does show many of them. As @bobc has already pointed out your 6P4T switch symbol is poorly drawn, as are the wires that connect to the switch pins. Fix your symbol and redraw the connections a little more carefully.
Complain about the grid all you want but in the end set it to 50 mils and forget about it. This of course does not apply when laying out the board in PCBnew.
3 Likes
One other thing which should be obvious, and probably is, but still may not be, is this: have you remembered to update the netlist after changing the schematic? It’s not updated automatically.
1 Like
If compiling uses only 1 core and it’s a problem it should be changeable with make: make -j 24. (In general; I don’t know how well it works with KiCad source.) With such amount of cores it’s probable that the speed of one core is slower than in a 4 core processor.
1.21 Gigawatts You obviously did not read the previous messages and introduce a mismatch to the data presented. I had to try to place junctions to force connections. Thats why it looks messy. Sometimes it helped. I had to add lines between passive pads and pins before they connect etc. etc. All this and your primary concerns are irrelevant because That the netlist containing completely bogus connections thats not in the schematic is truly laughable. Before that is not resolved why even continue. ? Clearly it is a bug as the netlist routine (is that the ratsnest that crashed in the source code ?) Im not blaming anyone. I am, just giving it as it is.! That is just not right and it is blaringly obvious to anyone caring to look. You seem to carefully pussyfut around the bogus connection regarding pin 22. Its missing from the net it is connected to in the schematic but it pops up later in a completely bogus net at the bottom. Just read the netlist and see for yourself.What you say about that ? This is not right…blame the user as much as you want. I can just show you what happens. Maybe you should fix your editor too so these things cannot happen.
Best is all cool down until I get a newer version of the software installed.
If you are using the latest Debian stable, follow the link above and learn how to install backports. That will give you 4.0.7 the current Kicad stable release.
Hermit: thanks, Im using Jesse so it should work without backports. I have no problem installing backports, but in this case not necessary afaik.
“That old broken version has to be Debian. One of the reasons I jumped to nightly.”
you are right I am using Debian, what is the problem you refered to with debian in the past ?
Andy
“Why the hell are you compiling the program suite when you can download binaries from the link I provided?”
Because if you read the post you would see that I am required to use apt to install the binaries, that requires me to use the repository provided for kicad. The repository cannot handle debian as it is seemingly configured ubuntu only. It branches to ubuntu/jesse which obviously creates a 404 as such a thing doesnt exist. It seems to read the /etc/distro for version rather than to just do what is asked.
So All that remains is “to hell” install from sources because as you know it is really the right way to do it in the first place.
Bobc
“The symbol “6P4T_ROTARY_SWITCH_INV” appears to be badly wrong,”
Even if true it is irrelevant as the netlist created a BOGUS entry for pin 22 connected to pins that is not even connected in the schematic. why even continue with such a blatant violation ?
Rene
“If it would really do that, all of our pcbs would be defect. I don’t even think there is such a bug in any kicad version. (Such terrible bugs are found during the development cycle. Very early on)”
But I show you exactly that this is happening. See the netlist I provided. It is a rediculous bug.
Either I lie and make this up as you suggest or you have a serious problem. I have no reason to make this up.
This is what happened.
I have read the entire topic, the part that is obvious is that you refuse to listen to anyone replying to you and attempting to assist you.
While it is entirely possible for Kicad to generate an erroneous netlist, it is unlikely. You have been told numerous times your switch symbol is incorrect. There is no point continuing until you resolve that issue. And we can’t see the rest of the schematic to be able to comment on it.
We are all users here just like you, many of us have years of experience and many successful boards using Kicad.
2 Likes
[quote=“retnev, post:33, topic:8940”]
Hermit: thanks, Im using Jesse so it should work without backports. I have no problem installing backports, but in this case not necessary afaik.
[/quote]NO, NO, NO. Please read my post above. You MUST use backports to get the latest version into Jessie. When Debian freezes a release it is extreamly difficult for software maintainers to get anything other than bug fixes into that branch. That is why the version you posted has all of those letters appended to it. That is the way the package maintainer tracks these ‘sub versions’. From the link above:
Jessie Backport Version: 4.0.7 (KiCad actual version)
or
Jessie Release Version: bzr4027 (KiCad stable release 2014)
I first learned about this using Sage Math. Their live distribution was actually done on stable Debian but they gave up trying to keep their latest version in the stable branch. It was just too painful.
Let me try one more time … you see, we have all “cared to look” and it seems to be “blaringly obvious” to everyone but you. We cannot see S1, S2, S3, or S4 but from what we can see there is nothing “bogus” in the netlist. We are all aware that Kicad has generated a netlist that you did not expect but from what we can see it is a perfectly valid netlist. You complain about S5 pin 22 missing but then say it shows up later in a “bogus” net. Let me ask you this, which pin 22 are you referring to? Are you even aware that you have two pin 22 in the S5 symbol? In fact all the pins from pin 19 to pin 24 are duplicated. So of course one of the pin 22 will be missing, since there can only be one. The net that does have a pin 22 is valid, it’s just not the pin 22 you were expecting. It is not a bogus netlist due to some “ridiculous” bug, it is just a bad schematic.
1 Like
Hermit,
Thanks I installed kicad-common_4.0.5+dfsg1-4~bpo8+1_amd64.deb with backports. Unfortunately after installation of the new kicad, it completely erased my home directory proj and schematic files ! Weird, usually software update or reinstall doesnt destroy the user files. No problem really as those were tests to see if the software works. I will just have to recreate it and will try again with the new version. The only reason I stick with Kicad is that it is very much like PCad and is very intuitive and well designed. It is just the underlying programming that I had an issue with, not the way it works. Great easy intuitive editor just like PCad. I sure hope that the netlist trouble was solved in this version. Will let you know.
Nope, I checked it and its the netlist. The pins in the bogus net referred to is not even connected to anyhing ! No way out of that one. Anyway it is an old version which I thought was the newest. I will try the new version now.
Please look again at your symbol. Does it still have multiple copies of the same pin number? If so, fix it first before we search further.
By the way i slowly get the feeling you are a troll.
1 Like
Oh god please lets just keep the name calling out of this.
See my last response to Hermit where I clearly describe that the new installation of Kicad destroyed my home directory kicad project file. It might even be that there was a permissions issue and that it did not really save the project which seems more likely as I never closed Kicad until reinstall. As it was only a test I was not concerned anyway. I am repeating it now with the new kicad that was installed and which he correctly pointed out that I forgot about the fct that the new Kicad would be in backports which solved the instllation of the new version. I doubt the library survived during the new install, but I will check.
Did the same with the newer version of the software. There are no Bogus nets this time so that is good news !
Must have been something with the old version.
This time I have trouble connecting which I did not have before. Last time the traces and pins connected…
The square from the wire and circle from the pins vanish when a trace is connected, but the netlist says there is absolutely no connection.
I also did G-drag and only the traces drag with, definitely not connected to pins.
Anyway, I will go read the manual again.
This must be something I do wrong, but I would expect if a circle and square vanishes, that a connection is actually made as someone mentioned.
So the Bogus net problem was solved with the upgrade to the new version.
As I was preparing to do this it occurred to me I never did a FAQ entry for “Getting to Blinky”! Doh…
https://contextualelectronics.com/courses/getting-to-blinky/
You only seem to cover creating footprints not schematic components. Your question there in one of the videos about why dimensions are done that way comes from isometric paper cad drawing pre PC (pre 1980). It is the Min-max principle by which you are required in your technical drawings always to give the minimum set of dimensions from which all the other dimensions can be derived. It prevents clutter and obviously if you studied Technical Drawing (what it was called back then) you must be able to do simple arithmetic immediately in your head.Anyway I could not find any video about creating schematic components from the component editor as I may learn something there about the problem I now have. Very well presented videos.