cho45 / kicad-utils Goto Github PK

I wanted to try out your tool and ran into this error message:

[vivien@vivien-nb ~]$ npx -p github:cho45/kicad-utils kicad-utils sch2svg /path/to/file.sch

/home/vivien/.npm/_npx/36935/lib/node_modules/kicad-utils/dist/src/kicad_sch.js:61
            throw "schematic format version is greater than supported version: " +
            ^
schematic format version is greater than supported version: 4>2
(Use `node --trace-uncaught ...` to show where the exception was thrown)

Some Information, that may help:

• Eeschema header: EESchema Schematic File Version 4
• KiCad version: 5.1.8
• npx version: 6.14.9
• node version: 15.4.0
• Linux kernel: 5.10.2-2-MANJARO

Hi!

First off, thanks you so much for this project!

I've been using a python script to panelize some KiCad boards, but started to write my own parser in node because of limitations of the Python script. I want to automate a lot more and do mousebits and edgecuts in my panelization scripts.

And then I found this project just the other day which really seems to be solving a lot of my problems. I myself started out with an intermediate s-expr parser that I found, but I see the tokenization is done already here.

I just started out trying to use this project as a lib but I wanted to just ask - does it parse "everything" and keep all the data or is it just parsing what's needed for the functions exposed here - I mean making those graphics? If not, do you think it is a lot of work to extend your parser to handle everything, because I think I'm going to need almost everything.

My idea is to load up a bunch of boards, do some transforms and output them all to the same file. Just like that python script I've been using does: http://projects.borg.ch/electronics/kicad/panelize.html, but with a bit more extensibility as a node lib.

Thanks!

Fails to parse this target

(target plus (at 200.877792 146.347713) (size 5) (width 0.15) (layer Edge.Cuts) (tstamp 59AE70DB))

unknown token layer at line 3601

Trying to debug why this happens, I see that layer is definitely there…