I’m checking the point of @sschaak … yes it seems diodes are changed.
I checked into the Schematics and I discovered: THT!
but I never ever edited the schematics since the export to JLC I’m trying to revert all and I will check all the other projects as well. Sine I go tthe same. I can’t figure out how it’s happened.
D4 was: Diode_SMD:D_SOD-123
But I got: Diode_THT:D_DO-35_SOD27_P7.62mm_Horizontal
However; things is not changing even substituting the footprint.
Check now D4 … ratentest everywhere
Come-on … the issue ok can be some footprint is changing (for no reason I have not clue) but not all the components.
package replacement: kicad normally(*1) don’t changes the packages in the schematic automagically, so I believe the false footprints were already present in the v6-versions of your files. Obviously this theorie can only be proved/disproved with the v6-files.
As issue-author you could set your gitlab-issue to confidential.
Or maybe its possible to strip-down the v6-project to a unsuspicious example and attach that?
Did you run the “update all symbols from library” command and had the “update footprint”-checkbox checked?
*1 not seen such effect in 2 years working with kicad
It would probably be more constructive and useful if you report a bug and attach the original project. If you don’t want to share the original design with the wider world, there is a possibility to mark the issue as confidential.
First of all, do you have a Back-up of your project before migration to 7.0.x?
If you do, I recommend checking the Footprint assignment for these affected parts, when opened in 6.0.x
The KiCad developers can not do very much if they can not reproduce the problem, but they also do not need your whole design. Consider this option:
You make a copy of the old V6 project.
You delete the “company secret” parts. If you leave just a few diodes and resistors that demonstrate the problem, it is enough for the KiCad developers. You can also replace some custom and identifyable PCB outline with a simple square, etc.
You port that “crippled” project to V7, and verify the error still exists.
Create a gitlab issue with those two projects.
A lot of other PCB design programs cost a lot of money, I consider putting some extra of my own time into making test cases, answering forum questions and such as my way of “paying back to KiCad”.
Indeed, whoever have been involved in Software development knows how valuable is good quality bug report with proper bug reproduction scenario.
Whenever I can, I try to provide exact steps and prepared test cases to my reports (often it’s stripped down work project that is still releavant to display the issue)
