Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

RE: [lpc2000] OrCAD library for LPC2000

2006-01-05 by Greg Deuerling

> -----Original Message-----
> From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com] On Behalf
> Of Sean
> Sent: Thursday, January 05, 2006 10:21 AM
> To: lpc2000@yahoogroups.com
> Subject: RE: [lpc2000] OrCAD library for LPC2000
> 
> 
> It's not that I (or others) don't know how to use these things, it's just
> that everyone is always under very tight time constraints.  If you need to
> take a day to create the physical parts in your CAD software then that's
> one more day until you're complete.  When you're working on tight
> deadlines
> and 10 hour days to meet unrealistic deadlines then that starts to make a
> big difference.  Add in the fact that (typically in my experience) every
> extra hour spent in the original design phase planning and thinking is
> worth 4 hours of debugging time.  Rush the design, spend a lot more time
> debugging.  So saving a day by using libraries already made, which are
> already tested and known to work, can save several days down the
> line.  Waste not, want not.
> 
> And it doesn't take a day to read a few responses :)

And when that 1000 pin FPGA symbol you got from somewhere has several errors
in it, those 60 minutes you saved your self turns into a nightmare when you
get your PCB's back :)  How do you know that symbol you just got from Joe
Schmo in an email attachment has ever been used or tested before?

I see this all of the time and after being burnt by it several times I now
make EVERY symbol and footprint that goes on my PCB's.  I've not used an
OrCad supplied symbol in years.

Sorry if it seems like I'm dumping on you, but I've been doing schematic's
and PCB's for 20+ years and I'm just trying to help you out in the long
run...

Greg Deuerling
Fermi National Accelerator Laboratory

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.