No working connectors in new part

Hi I have tried to modify this existing part to the Part I want to use. The connectors are the same, only the dimensions of the part are different. I have changed the dimensions and connector positions in Inkscape, however when I use the new drawing the connectors are in the correct position but I cannot connect them. What did I do wrong?

Name of the part
HLK-10M05

Previous work, similar parts
HiLink HLK-5M05

Top view
![image|144x87](upload://a6NoQADF0JIVeR49he6d61sDzGh.png

Datasheet
The official documentation of the part manufacture is linked here:

Please add a link to PDF of the manufacturers datasheet

Type
I did not read this
Breakout board, sub assembly, plug in module (A)
Antenna (AE)
Battery (BT)
Capacitor (C)
Diode (D)
Display (DS)
Fuse (F)
Hardware , mounting screws, etc. (H)
Jack, fixed part of a connector pair, header (J)
Relay (K)
Inductor, Coil, Ferrite bead (L)
Loudspeaker, Buzzer (LS)
Motor (M)
Microphone (MK)
Plug, moveable part of a connector pair (P)
Transistor (Q)
Resistor (R)
Thermistor (RT)
Varistor (RV)
Switch (S)
Transformer (T)
Integrated Circuit (IC)
Crystal, Oscillator (Y)
Zender diode (Z)
Other (please specifiy)
Transformer

Footprint
Custom

@Jaapio1969 What do you mean by “No working connections”

Sorry, I posted to soon. I edited the post in the meantime.

Do let me know if you’ve edited as the forum won’t notify me

Hi Raptor, Have edited the post. I hope all is clear to you.

@Jaapio1969 Can you attatch that .fzpz file?

Yes, please find it attached. I experimented a bit further. Now there is a square in the middle which connects. But the connectors do not work…
HLK-PM12.fzpz (11.9 KB)

Please use variant 3, that is the part I have drawn.

@Jaapio1969 Many problems here

Breadboard


Scale is wrong

Has to change to

Ungroup everything

The connectors are in a mess, and typically we want to number them like this

Fill for connectors usually #9a916c so in XML editor change to

Renumber and reorder the connectors (delete connector1terminal too)

Then run the svg with @vanepp’s FritzingCheckPart.py which flags the following:

Modified 4: File
‘bb.svg’
At line 40

ReferenceFile

‘HLK-PM01-Breadboard.svg’

doesn’t match input file

‘bb.svg’

Corrected

Modified 1: File
‘bb.svg’
At line 180

Removed px from font-size leaving 77.626

Modified 1: File
‘bb.svg’
At line 184

Removed px from font-size leaving 74.9261

Modified 1: File
‘bb.svg’
At line 189

Removed px from font-size leaving 74.9261

Modified 1: File
‘bb.svg’
At line 194

Removed px from font-size leaving 74.9261

Modified 1: File
‘bb.svg’
At line 199

Removed px from font-size leaving 74.9261

Modified 1: File
‘bb.svg’
At line 204

Removed px from font-size leaving 74.9261

Modified 1: File
‘bb.svg’
At line 210

Removed px from font-size leaving 77.626

Modified 1: File
‘bb.svg’
At line 276

Removed px from font-size leaving 77.626

Modified 1: File
‘bb.svg’
At line 282

Removed px from font-size leaving 77.626

Warning 23: File
‘bb.svg’
At line 276

Key -inkscape-font-specification
value ‘Droid Sans’ is invalid and has been deleted

Warning 26: File
‘bb.svg’
At line 282

Apparant nested tspan which fritzing doesn’t support
If your text doesn’t appear in Fritzing this is probably why

Error 69: File
‘bb.svg’
At line 174

Found a drawing element before a layerId (or no layerId)

Then open the SVG and edit → select all → ctrl/cmd + g → XML editor → change id to breadboard

Then edit your old part with the new part editor and load this SVG

bb

in there. The connectors have changed, so we have to change from

to

Schematic


The easiest is to redo the whole schematic with the schematic extension

image

which will result in this SVG

sch

PCB


Disclaimer: I assume the hole sizes are correct

So, the groups are wrongly configured

First, ungroup everything

Then delete the unused circles and the texts

Group everything, then adjust the scale

and ungroup everything.

Group the rectangle, the connectors twice, and reorder/rename them, like this. Same thing, rename the connectors as necessary

You also have to change the stroke to #f7bd13 too.

svg.pcb.HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb

HLK-PM12-fixed.fzpz (10.5 KB)

Wauw, thank you for your efforts and explanation. I am using two different transformers. I will generate the other with your instructions!

I have worked my way trough until

I am using a MacBook with OSX 15.3 installed. I managed to install Python, I opened the Phyton terminal screen. When I enter the following syntax:

FritzingCheckPart.py HLK-part.fzpz.bak

Python returns “SyntaxError: invalid syntax”

I assume some paths are not correctly set? Is there a OSX manual on using this tool?

There is no manual for any version, it is mostly used by people familiar with python (and there are only a handful of users.) That command won’t work and should return a usage message as it is expecting a .fzpz file (not a .fzpz.bak file.) You also need to load the lxml library in to python before it will run (although the this error message isn’t from no lxml either.)

Peter

Hi Peter,

Thank you for your reply. I have altered the filename and the command to:

FritzingCheckPart.py HLK-part.fzpz

I still get the same return: “SyntaxError: invalid syntax”

Do I understand correctly that if I am not familiar with Python it is not possible to work with? Do you have a online method to use your script perhaps? Or can I go through the drawing step by step to do it manually?

There isn’t an online version that I am aware of, it usually runs without much problem (the lack of lxml is usually the problem and that can be cured with pip) but it normally gives more error information than just “SyntaxError: invalid syntax” (but I am on Windows not a Mac, so things may be different there.) One thing to try is run it as FritzingCheckPart.py -d3 part.HLK-part.fzp (the file name should be .fzp not the .fzpz file which is compressed.) The directory with the part should look like this with the .fzp file and all the svgs present.

part.24V_SMD2835_LED_Strip_1.fzp
svg.breadboard.prefix0000_6fbdb41430491ba080df8d6e0bc872e1_11_breadboard.svg
svg.icon.prefix0000_6fbdb41430491ba080df8d6e0bc872e1_11_icon.svg
svg.pcb.prefix0000_6fbdb41430491ba080df8d6e0bc872e1_11_pcb.svg
svg.schematic.prefix0000_6fbdb41430491ba080df8d6e0bc872e1_11_schematic.svg

The -d3 activates debug mode which should produce a bunch of debug information on the console and may tell me something. Alternately and maybe easiest if you upload your .fzpz file (upload is 7th icon from the left in the reply menu.) I can download it, decompress it and run it through FritzingCheckPart.py to both check it and show you what kind of output you should be expecting and what to do about any errors.

edit:

I just downloaded your part above and ran it with this result

$ FritzingCheckPartw.py part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp

**** Starting to process file Startup, no file yet

**** Starting to process file part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp

**** Starting to process file svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak

**** Starting to process file svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak

**** Starting to process file svg.pcb.HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb.svg.bak

File
‘part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.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 47

Modified 4: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 4

ReferenceFile

‘HLK-PM01-Breadboard.svg’

doesn’t match input file

‘HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg’

Corrected

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 28

Removed px from font-size leaving 5.56692982

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 45

Removed px from font-size leaving 6

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 48

Removed px from font-size leaving 6

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 49

Removed px from font-size leaving 6

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 50

Removed px from font-size leaving 6

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 51

Removed px from font-size leaving 6

Modified 1: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 68

Removed px from font-size leaving 5.56692982

Modified 4: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 4

ReferenceFile

‘HLK-PM01-Schematic.svg’

doesn’t match input file

‘HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg’

Corrected

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 38

Removed px from font-size leaving 5.94430017

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 42

Removed px from font-size leaving 5.94430017

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 46

Removed px from font-size leaving 9.0708704

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 47

Removed px from font-size leaving 5.45108986

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 48

Removed px from font-size leaving 5.45108986

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 49

Removed px from font-size leaving 3

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 50

Removed px from font-size leaving 3

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 51

Removed px from font-size leaving 3

Modified 1: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 52

Removed px from font-size leaving 3

Modified 4: File
‘svg.pcb.HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb.svg.bak’
At line 5

ReferenceFile

‘5 volt voeding new.svg’

doesn’t match input file

‘HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb.svg’

Corrected

Warning 6: File
‘part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp.bak’
At line 2

ReferenceFile name

‘generic_ic_dip_4_300mil.fzp’

Doesn’t match fzp filename

‘HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp’

Warning 32: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 2

Scale is not the desirable 1/1000 ratio from width/height to
viewBox width/height.

Warning 23: File
‘svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak’
At line 97

Key -inkscape-font-specification
value Droid Sans is invalid and has been deleted

Warning 32: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 2

Scale is not the desirable 1/1000 ratio from width/height to
viewBox width/height.

Warning 32: File
‘svg.pcb.HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb.svg.bak’
At line 3

Scale is not the desirable 1/1000 ratio from width/height to
viewBox width/height.

Warning 25: File
‘svg.pcb.HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb.svg.bak’
At line 30

Silkscreen layer should be above the copper layers for easier selection
in pcb view

Warning 23: File
‘svg.pcb.HLK-10M05_7db924165e20438e5ba65929091a3343_2_pcb.svg.bak’
At line 33

Key -inkscape-font-specification
value OCRA is invalid and has been deleted

Error 18: File
‘part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp.bak’

Connector connector0terminal is in the fzp file but not the svg file. (typo?)

svg svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak

Error 18: File
‘part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp.bak’

Connector connector2terminal is in the fzp file but not the svg file. (typo?)

svg svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak

Error 18: File
‘part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp.bak’

Connector connector3terminal is in the fzp file but not the svg file. (typo?)

svg svg.breadboard.HLK-10M05_7db924165e20438e5ba65929091a3343_2_breadboard.svg.bak

Error 69: File
‘svg.schematic.HLK-10M05_7db924165e20438e5ba65929091a3343_2_schematic.svg.bak’
At line 28

Found a drawing element before a layerId (or no layerId)

another thought are you running python3? I’m not sure FritzingCheckPart.py will run on python2.x although it may.

edit2:

I modified a test script to have a syntax error then ran it. For me here is the output it produces:

$ FritzingCheckPartt.py part.HLK-10M05_7db924165e20438e5ba65929091a3343_2.fzp






           FritzingCheckPart.py: Starting to process file

Startup, no file yet






INFO: FritzingToolst.py line 152
Entering ProcessArgs

INFO: FritzingToolst.py line 339
Exiting ProcessArgs

Traceback (most recent call last):
File “/usr/local/bin/FritzingCheckPartt.py”, line 352, in
Fritzing.OutputSplashScreent(InFile, Debug)
AttributeError: module ‘FritzingToolst’ has no attribute ‘OutputSplashScreent’

I would expect to see more information than just a syntax error with no context, python normally provides detailed error messages as it did here.

Peter

In the fritzing-parts repositort, I am maintaing a script to check parts during our CI, which is also intended to be run manually.
For some problems, there are automatic fixes that can be enabled. It also takes care to apply minimal changes during these auto-fixes, so that changes still can be reviewed manually line by line.
Unless of course you reformat the whole file with scour or similar.

Hi KjellM, This sounds great. Where can I find this script?

Hi Raptor7762,

I did what I could do with the instructions you posted above. I need two transformers to be designed on a new PCB, the HLK-30M12 and the HLK10M05.

For both parts I have altered all .SVG files to a level I think it must be OK now. Can you please check them with your script. As it is not a daily thing for me, I should be fine if one of you can check the files for me. Afterwards I can share them with the rest of the world! :wink:
Many thanks in advance for your efforts!!
HLK-30M12C.fzpz (13.9 KB)
HLK-10M05.fzpz (14.4 KB)

HLK-10M05 datasheet
HLK-30M12 datasheet

@Jaapio1969 I’m busy trying to sort out some major error core parts in Fritzing, so I’m busy. @vanepp Can you help me

In the fritzing-parts repo:

A correct version of the HLK-10M05 is available here:

(before making new parts always do a google search of the form “fritzing part HLK-10M05”)

I’ll look over your HLK-30M12C part and correct it as needed.

edit:

OK a number of corrections starting with breadboard
The output pin numbers are backwards connector2 wants to be on the bottom and connector3 on the top (the same format as an IC) so the two right pins need to swap pin numbers.

you are missing a layerId which will cause the part to not export as an image (and get questions as to why that is!)

from the data sheet

the breadboard image is the wrong size and the pins are in the wrong position (both are supposed to reflect real life)

from the data sheet I set construction lines (after resizing the rectangle to the correct size) to mark the position of the pins then moved them to where they should be.

Then I did an Edit->select all an Edit->Resize page to selection and Object->group and named the group breadboard (which is what it is called in the .fzp file) then saved the corrected svg.

schematic has a number of problems

It doesn’t have the correct scale nor the correct colors or font sizes. Rather than try and fix it I chose to make a new schematic using Randy’s Inkscape fritzing schematic extension

then set the pin names for the first 2 pins

then the last 2 pins

and hit finished and it creates the new svg at the correct scale with the correct layerId

however the pins are slightly offset so ungroup the svg and then move the pins in to a better position and then regroup the svg and set the layerId again

then save the svg and move on to pcb there are a couple of problems here, the pin numbers need to be corrected to reflect the numbers used in breadboard and schematic, and the pins need to be circles (not ellipses as they are now, ellipses will not generate a hole in the gerber output!)

the easiest way to correct the radius is set both 4x and ry in xml editor to the same value (I used a radius of 29 which will give a 0.038 hole suitable for a 0.1in header)

then move the pad on space left then one space right to put it back in the same position it was. Inkscape recognizes that the ellipse has changed to a circle and replaces rx and ry with r=29 which along with a stroke-width of 20 will produce the correct hole size like this

next we need to change the stroke-width of the silkscreen rectangle to 10 (to make it 10thou inches which is the standard silkscreen line size.)

That changes the size of the rectangle slightly so we need to first correct that

then change the width and height to match the data sheet then set up the construction lines to correctly move the pads in the correct position (they were already in the correct position before I changed the rectangle size, so the entire group only needed to be moved to the correct new position.)

re doing the groups creates the completed pcb svg which can now be saved.

On to the .fzp file

<module fritzingVersion="1.0.5" moduleId="HLK-30M12C_c18aaf9a40156747a68f55b2d8d3cadb_1" referenceFile="generic_ic_dip_4_300mil.fzp">

I updated the fritzing version to the version I tested the part on (1.0.5) and then

  <author>Iyad Nahas (modified by vanepp May 2025)</author>
  <title>HLK-30M12C</title>
  <label>A</label>

updated the author field to say I modified your part, corrected the title to reflect the correct part number and set the label to A (for assumbly) then I updated the label property to reflect the correct part number

    <property name="label">HLK-30M12C</property>

corrected the description field to match the voltage output of the new part

  <description>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"&gt;
&lt;html&gt;&lt;head&gt;&lt;meta name="qrichtext" content="1" /&gt;&lt;style type="text/css"&gt;
p, li { white-space: pre-wrap; }
&lt;/style&gt;&lt;/head&gt;&lt;body style=" font-family:'.SF NS Text'; font-size:13pt; font-weight:400; font-style:normal;"&gt;
&lt;p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"&gt;AC-DC 220V to 12V Step-Down Power Supply Module&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</description>

reused the breadboard svg as the icon svg (to save file space)

    <iconView>
      <layers image="breadboard/HLK-30M12C_c18aaf9a40156747a68f55b2d8d3cadb_2_breadboard.svg">
        <layer layerId="icon"/>
      </layers>
    </iconView>

then changed the description and name fields in connectors2 and connector3 to reflect the new order of the two pins by reversing connectors 2 and 3.

    <connector id="connector2" name="+Vo" type="male">
      <description>+V Out</description>
      <views>
        <breadboardView>
          <p layer="breadboard" svgId="connector2pin"/>
        </breadboardView>
        <schematicView>
          <p layer="schematic" svgId="connector2pin" terminalId="connector2terminal"/>
        </schematicView>
        <pcbView>
          <p layer="copper0" svgId="connector2pin"/>
          <p layer="copper1" svgId="connector2pin"/>
        </pcbView>
      </views>
    </connector>
    <connector id="connector3" name="-Vo" type="male">
      <description>-V Out</description>
      <views>
        <breadboardView>
          <p layer="breadboard" svgId="connector3pin"/>
        </breadboardView>
        <schematicView>
          <p layer="schematic" svgId="connector3pin" terminalId="connector3terminal"/>
        </schematicView>
        <pcbView>
          <p layer="copper0" svgId="connector3pin"/>
          <p layer="copper1" svgId="connector3pin"/>
        </pcbView>
      </views>
    </connector>

then corrected the url field to point to the datasheet for this part

  <url>https://www.lcsc.com/datasheet/lcsc_datasheet_2409141607_HI-LINK-HLK-30M12_C2761166.pdf</url>

which creates this corrected part.

HLK-30M12C-fixed.fzpz (7.1 KB)

which should do what you want.

Peter

I think we may need some more information to actually use this. I tried to run it after downloading all the py files that seemed to be needed by fzp_checker_runner.py and I assume I got them all because it so far hasn’t complained after I added the python3 definition. By default I think cygwin runs python 2.something and it looks like the import command has changed between python2 and python3

$ fzp_checker_runner.py
/usr/local/bin/fzp_checker_runner.py: line 1: from: command not found
/usr/local/bin/fzp_checker_runner.py: line 2: from: command not found
/usr/local/bin/fzp_checker_runner.py: line 3: from: command not found
/usr/local/bin/fzp_checker_runner.py: line 4: from: command not found
/usr/local/bin/fzp_checker_runner.py: line 5: import: command not found
/usr/local/bin/fzp_checker_runner.py: line 7: class: command not found
/usr/local/bin/fzp_checker_runner.py: line 8: syntax error near unexpected token (' /usr/local/bin/fzp_checker_runner.py: line 8: def init(self, path, verbose=False):’

Assuming it defaulted to python 2.x I added

#!/usr/bin/env python3

to fzp_checker_runner.py

with that in place it appears to run

$ fzp_checker_runner.py
usage: usage: fzp_checker_runner.py
[-c [{all,missing_tags,connector_terminal,connector_visibility,pcb_connector_stroke,font_size,viewbox,ids} …]]
[-s SVG] [-f FILE] [-v] [-h]
path

Scan FZP files for various checks

positional arguments:
path Path to FZP file or directory to scan

optional arguments:
-c [{all,missing_tags,connector_terminal,connector_visibility,pcb_connector_stroke,font_size,viewbox,ids} …], --checks [{all,missing_tags,connector_terminal,connector_visibility,pcb_connector_stroke,font_size,viewbox,ids} …]
Type(s) of check to run (default: all)
-s SVG, --svg SVG Path to an SVG file to search for in FZP files
-f FILE, --file FILE Path to a file containing a list of SVG and FZP files
to check
-v, --verbose Enable verbose output
-h, --help Show this help message and exit
fzp_checker_runner.py: error: the following arguments are required: path

I may just be missing an option that I should be including so I will continue poking at it (with the intent of switching to this from FritzingCheckPart.py)

when run with an fzp file as an argument it does this:

$ fzp_checker_runner.py part.prefix0000_2831a6f19938d01c8f6d8eccfc7a7e54_1.fzp
Traceback (most recent call last):
File “/usr/local/bin/fzp_checker_runner.py”, line 219, in
checker_runner.check(selected_fzp_checks, selected_svg_checks)
File “/usr/local/bin/fzp_checker_runner.py”, line 32, in check
errors = checker.check()
File “/usr/local/bin/fzp_checkers.py”, line 65, in check
if not self.svg_has_element_with_id(terminal_id, view.tag):
File “/usr/local/bin/fzp_checkers.py”, line 75, in svg_has_element_with_id
svg_doc = etree.parse(svg_path)
File “src/lxml/etree.pyx”, line 3536, in lxml.etree.parse
File “src/lxml/parser.pxi”, line 1875, in lxml.etree._parseDocument
File “src/lxml/parser.pxi”, line 1901, in lxml.etree._parseDocumentFromURL
File “src/lxml/parser.pxi”, line 1805, in lxml.etree._parseDocFromFile
File “src/lxml/parser.pxi”, line 1177, in lxml.etree._BaseParser._parseDocFromFile
File “src/lxml/parser.pxi”, line 615, in lxml.etree._ParserContext._handleParseResultDoc
File “src/lxml/parser.pxi”, line 725, in lxml.etree._handleParseResult
File “src/lxml/parser.pxi”, line 652, in lxml.etree._raiseParseError
OSError: Error reading file ‘svg/core/schematic/prefix0000_2831a6f19938d01c8f6d8eccfc7a7e54_1_schematic.svg’: failed to load external entity “svg/core/schematic/prefix0000_2831a6f19938d01c8f6d8eccfc7a7e54_1_schematic.svg”

which as noted may be due to operator error since I don’t know what I am doing yet. It may just need a copy of the the parts directory in the same directory I am running from I expect since it looks to be looking for something in core parts. Doesn’t look like the parts directory will help. The referenced file isn’t in core parts for 1.0.5 only prefix0000_1.svg and prefix0000_SFE-10467-v10_2.svg neither of which are what it is looking for. I guess it may not support fzpz type file format and needs repository format.

Peter