I then created several dummy traces and exported everything as ASCII. The traces were created by importing DXF polylines as "Top" - lines only (no arcs) but make sure you have points in your DXF that will define the arc (extra point, anywhere on each arc). The file was then imported and contents copied into my actual design document. ) from the shapes to the pours, and then delete the shapes. In the ASCII file it was easy enough to make multiple copies of the pour, move points (pt. I then created a dummy copper pour (with desired parameters) and exported everything as ASCII. The pours were created by importing DXF shapes as "Board Outline" into a new empty document. There are two things imported here - traces and pours. Working with the ASCII files is annoying, but will speed things up a lot compared to manually punching in hundreds of coordinates. (No, these are not friendly enough to publish - but if you are comfortable working with C code you can have it) * Global shape scaling - useful when that multi-part/-layer logo you've tediously imported is the wrong size for your next design * Copy a single component to multiple locations defined in a CSV file - useful for LED signage * Converting board outlines to shapes or pours - because importing DXF as board outline actually works I've had to resort to write a DipTrace ASCII parser and writer in C, so that I can do some of these things programatically.įor instance, I've constructed programs to: However, DipTrace ASCII files are typically the way to go for advanced maneuvers not inherently supported. DipTrace has terrible shape import support, which is sad since I love almost everything else about it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |