You could for example double check the newly generated silkscreen text with the recovered lineart. Do DRC for finding conversion errors, etc. Place the Footprints on the right places on top of the from Gerbview imported copper tracks. (You could even park notes on a unused copper layer if you deemed it usefull). Use GerbView to export the silk screen to a user drawing, fabrication or other auxilary layer. Use GerbView to export the board outline and copper traces to a KiCad project. With the current state of KiCad (V5.0.2) the most sensible path seems to be: - Redraw the schematic (Which is a nuisance, but redrawing a schematic is not that much work from even a paper printout.) - From the schematic you can generate a normal netlist & footprint association. Pad locations are recovered (but SMD pads seem to be converted to holes) Silkscreen gets recoverd, but all silkscreen text is converted to individual line segments. So I did the export in Gerbview, and imported it again in Pcbnew. It does not know the difference between copper and silkscreen. In GerbView you first get a popup with how to export layers, and where to. Imported all the layers in GerbView, and then I saw in the File menu an option for: "Export to PCBnew" so I tried that immediately. As preparation I first made some Gerber files with KiCad of a very simple design I had liing around (2 diodes connected in parralell). My curiousity was what you can do with GerbView (Gerber viewer part in KiCad). Weird combination, but it's probably on the roadmap to improve that. File import/export is a very immature funcionality at the moment in KiCad, but I know that Pcbnew (PCB part of KiCad) can export layers (Copper, silkscreen, or any other) as an SVG file, and it can import layers from a. I was curious about that so I had a look.
0 Comments
Leave a Reply. |