I ran the HS320561K part through FritzingCheckPart. That got a lot of complaints. Looking at the svg files, I found there were multiple layers of group in group in group … wrapped around whole file content, and blocks of graphics within files.
“copper1” groups exist in breadboard and icon images, as well as pcb. The pcb image has a copper0 group inside of copper1, implying through hole, but the copper0 group is empty. The copper elements all exist on only the one side (bottom) of the board. The fzp file information indicates that the connectors should be on both sides.
Loading the part into Frtizing, and examining the results, pin 6 connector is missing in all views. In pcb view, the expanded ellipse pad exists, but not the connector. I see a “connector0pad-4-4” ellipse, which is probably supposed to be that missing connector5 = pin6. If that is a “no connect” pin, it should exist, and be tagged as such, in at least breadboard and pcb views. The schematic view of the part is rather over sized. It should be more of symbolic view, instead of those drawn shapes for each segment. In breadboard view, the connector pins are bigger than they should be. I schematic view, the pins (lines) are not aligned to the standard 0.1 in spacing.
The fzp title element should be a description of the part, not the part number. The label should be prefix used to tag instances of the part (along with a sequential number). Something like “disp”, so multiple instances would become disp1, disp2, … Duplicating the part number in the variant is not needed. For this, variant does not need to exist. It would be used to identify variations that would otherwise have identical attributes.
The definition information says 300mil spacing. Breadboard looks like 400mil spacing (possibly from those px units). pcb view looks like 600mil spacing.
With both your original, and my modified version, exporting the pcb view looks good for jpg, png, pdf, but I see your glitch on the svg export. Examining the source and created path elements, I do not see anything specific that Fritzing should choke on, but the different structure says it dropped some segments of the path. Which would be a bug.
I used inkscape to ungroup those groups multiple times, deleted the empty copper group, then regrouped the pcb elements to get the non-silkscreen elements inside a copper0 group, which is inside of a copper1 group. After that, I ran FritzingCheckPart on the result. The full report after that is below, with the file paths truncated to shorten the lines. Here is a summary of what it says.
- the fzp file is supposed to have an attribute recording the Fritzing version number.
- the breadboard file is dimensioned in “px” units, which is not safe
- the fzp file has definitions for connector 0 through 4, 6 and 7, 9 through 12. 5 and 8 do not exist, and they should (do not HAVE to) be sequentially numbered
- that extra/bogus copper group in the breadboard svg shows up first, so this complains about expecting to find the breadboard id first
- there are connect«n»terminal id attributes specified for breadboard view connectors in the fzp file, but they do not exist in the svg
- the connector«n»pin elements in the pcb svg are ellipses, but Fritzing, especially gerber output, expects circles. Holes will be drilled only for circles.
% FritzingCheckPart …/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp
Processing "…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp"
File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
This is a through hole part as both copper0 and copper1 views are present.
If you wanted a smd part remove the copper0 definition from line 49
Warning 7: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
At line 2
No Fritzing version in fzp file
Warning 19: File
'…/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak'
At line 17
Height 47.262985 is defined in px
in or mm is a better option (px can cause scaling problems!)
Warning 19: File
'…/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak'
At line 17
Width 107.63095 is defined in px
in or mm is a better option (px can cause scaling problems!)
Error 64: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector5 doesn't exist when it must to stay in sequence
Error 69: File
'…/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak'
At line 78
Found a drawing element before a layerId (or no layerId)
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector0terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector1terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector2terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector3terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector4terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector6terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 18: File
'…/part.HS320561K_740433510e6913850aacb34dc1d42eaf_12.fzp.bak'
Connector connector7terminal is in the fzp file but not the svg file. (typo?)
svg …/svg.breadboard.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_breadboard.svg.bak
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 133
Connector connector6pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 133
Connector connector6pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 154
Connector connector9pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 154
Connector connector9pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 175
Connector connector11pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 175
Connector connector11pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 196
Connector connector7pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 196
Connector connector7pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 217
Connector connector10pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 217
Connector connector10pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 238
Connector connector0pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 238
Connector connector0pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 280
Connector connector3pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 280
Connector connector3pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 301
Connector connector1pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 301
Connector connector1pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 322
Connector connector4pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 322
Connector connector4pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 343
Connector connector2pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 343
Connector connector2pin has no radius no hole will be generated
Error 65: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 364
Connector connector12pin is an ellipse not a circle, (gerber generation will break.)
Error 74: File
'…/svg.pcb.HS320561K_c4b652af30a5f0e3ceaa988c37267ec3_2_pcb.svg.bak'
At line 364
Connector connector12pin has no radius no hole will be generated
Here is the part with the described adjustments. It is not correct yet. It only has the nested group and pcb copper 0 stuff cleaned up.
HS320561K-2.fzpz (18.1 KB)
I said the glitch is a bug. However similar structures work elsewhere, even the second row of pins in this part. So it should be possible to build those paths differently to avoid whatever is triggering the glitch.