Hello,
I was wondering how much designers rely on scripts while doing
schematics or boards in eagle. Do you use scripts for some routine tasks
which would simpify the schematic capture or board layout? Which ones are
those?
- Sujay
Hello,
I was wondering how much designers rely on scripts while doing
schematics or boards in eagle. Do you use scripts for some routine tasks
which would simpify the schematic capture or board layout? Which ones are
those?
- Sujay
Sujay Phadke wrote:
Hello,
I was wondering how much designers rely on scripts while doing
schematics or boards in eagle. Do you use scripts for some routine tasks
which would simpify the schematic capture or board layout? Which ones
are those?
- Sujay
With ULP's and scripts you can do almost anything. Rather then bloating
the user interface with every conceivable feature with the building
blocks provided they can be assembled by the user to do unique and
common tasks. If you can type it in on the command line you can put it
in a script to save it for later.
I will use a spread sheet to generate the x,y locations when building a
part from the data sheet. Use that data and make a script then run it,
check the output, modify the script and repeat until it is what I want.
Paul R.
I was wondering how much designers rely on scripts
I will use a spread sheet to generate the x,y locations when building a
part from the data sheet. Use that data and make a script then run it,
check the output, modify the script and repeat until it is what I want.
They are essential for me. The user community has provided many ULPs in
the download area that make me more efficient.
I use ULPs and scripts to do renumbering, export layouts to Protel, and
add some frequently used AutoCad-like functions such as Offset and
Fillet. I use scripts to automate sequences of commands and settings
(such as exporting images of layouts using particular colour settings).
I also use Excel to calculate and visualise data then create Eagle
scripts. I've used it to create scripts to draw sine waves to add info
to schematics, and to make a "veroboard" like layout.
Cheers
Neil
On Mon, 22 Jun 2009, Paul Romanyszyn wrote to us saying :
I will use a spread sheet to generate the x,y locations when building a
part from the data sheet. Use that data and make a script then run it,
check the output, modify the script and repeat until it is what I want.
I habitually do something very similar, though rather than a spreadsheet
I tend to use a python script to generate the Eagle script. I'm
gradually getting more proficient with Eagle ULP, too, which is dead
handy for custom tasks such as generating a pin-out list for all the
connectors on the board. The semi-automated generation of sticky labels
for the components being sent to the board house uses a hairy mix of
ULP, Python, a bit of hand fiddling, and OpenOffice Writer.
--
Rob Pearce http://www.bdt-home.demon.co.uk
The contents of this | Windows NT crashed.
message are purely | I am the Blue Screen of Death.
my opinion. Don't | No one hears your screams.
believe a word. |
thanks everyone for your inputs! I did use the genpkg script to make a SSOT
package. I wish we could use python or perl to directly interface with eagle
instead of the custom ULP. Maybe the eagle designers could look into adding
perl/python hooks in eagle which would make it more user friendly IMO.
"Sujay Phadke" <sphadke@umich.edu> wrote in message
news:h1ojai$nf3$1@cheetah.cadsoft.de...
Hello,
I was wondering how much designers rely on scripts while doing
schematics or boards in eagle. Do you use scripts for some routine tasks
which would simpify the schematic capture or board layout? Which ones are
those?
- Sujay