Searching \ for 'Orcad part files for 16F877' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=16F
Search entire site for: 'Orcad part files for 16F877'.

Truncated match.
PICList Thread
'Orcad part files for 16F877'
1999\09\08@172531 by Erik Reikes

flavicon
face
Does anyone know where I can get the part database for the new 16F877 parts?

Thanks.

-Erik Reikes
Xsilogy, Inc.

1999\09\08@175121 by Andy Kunz

flavicon
face
At 02:27 PM 9/7/99 -0700, you wrote:
>Does anyone know where I can get the part database for the new 16F877 parts?

Use a PIC16C74 or '77

Andy

==================================================================
Eternity is only a heartbeat away - are you ready?  Ask me how!
------------------------------------------------------------------
spam_OUTandyTakeThisOuTspamrc-hydros.com      http://www.rc-hydros.com     - Race Boats
.....andyKILLspamspam@spam@montanadesign.com  http://www.montanadesign.com - Electronics
==================================================================

1999\09\08@193000 by Dave VanHorn

flavicon
face
> At 02:27 PM 9/7/99 -0700, you wrote:
> >Does anyone know where I can get the part database for the new 16F877
parts?
>
> Use a PIC16C74 or '77


Did they "fix" this in the new orcad too? (and make it dramatically more
difficult?)
It only takes me a few minutes to make any part, and I make most parts
custom to the job, so that the schematic makes sense, rather than using one
pinout and making spaghetti out of the schematic.

1999\09\08@201230 by Dennis Plunkett

flavicon
face
At 18:28 8/09/99 -0500, you wrote:
>> At 02:27 PM 9/7/99 -0700, you wrote:
>> >Does anyone know where I can get the part database for the new 16F877
>parts?
>>
>> Use a PIC16C74 or '77
>
>
>Did they "fix" this in the new orcad too? (and make it dramatically more
>difficult?)
>It only takes me a few minutes to make any part, and I make most parts
>custom to the job, so that the schematic makes sense, rather than using one
>pinout and making spaghetti out of the schematic.
>
>


So do you save the library for each schematic? This can become a
maintenance nightmare. What hapens if you lose the library for that
schematic (Re-incarntaion?)
To stop spaghetti, why not use buses and hierarchial representation of the
CCT?

Dennis

1999\09\08@203317 by Dave VanHorn

flavicon
face
>
>
> So do you save the library for each schematic? This can become a
> maintenance nightmare. What hapens if you lose the library for that
> schematic (Re-incarntaion?)
> To stop spaghetti, why not use buses and hierarchial representation of the
> CCT?
>
> Dennis

Of course. Each project is archived with all the tools necessary to
reproduce it.
I start with the generic libraries, and if I have a new part that isn't in
the libraries, then I add it to "custom.lib".

When I start neatening things up though, I archive all the parts into a
project library ("thing.lib"), and any further work on the parts is now
unique to this project. When I finalize, I turn off all other generic
libraries, and work only in the project's library.

Same with PCB modules, except the board file IS the project library (an
irritating inconsistency)

I archive delivered or dead projects in a separate directory. Delivereds go
with their gerbers and drill files in the exact zip file I sent to the board
house, along with the schematic and it's part's library. I copy the design
to a new rev level for any modifications that I might make.  Anything I make
a board of is frozen at that level, and any mods happen to the new rev. This
way I can always get the schematic of the original board, regardless of any
"surgery" I've done.  I also hardfile a blank board for each project.

I use buses, and hierarchies, but still, I like ins on the left, and outs on
the right, and signals that logically go together should be located near
each other on the schematic, regardless of the physical pinout.  /RD, /WR,
and /CE are a functional group, even if intel decided to interleave them
with address lines on eproms. Address lines are a group (buss) and so is
data (another buss, located near address)  The control signals are the third
group.

More... (looser matching)
- Last day of these posts
- In 1999 , 2000 only
- Today
- New search...