Pic's come in all sizes and packages. 8, 18 24 both skinny 0.3 width and
normal 0.6 and so on. As do AVR's
I've not done any AVR programming, but there are lots of tools available,
you don't need to use C. Look at Bascom which is a basic-like programming
system for the AVR
I use plain old machine code for the PIC, however there are C and basic
systems for these as well, esp the higher end 18 series.
Using 0.3 and 0.6; No, not side by side just have enough width and holes
available so that the wider chip straddles the 0.3 location.
x=hole, 3=0.3 6=0.6 .=no track
xxxxx6x3.36xxxxx
xxxxx6x3.36xxxxx
xxxxx6x3.36xxxxx
xxxxx6x3.36xxxxx
....
and so on
Andy
On Tue, 24 Nov 2009 11:42:05 -0800
rocko <[email protected]> wrote:
> Funny I was thinking the same thing after I was finished.
> Changing to a 18 pin wouldn't increase the board size,
> so my cost wouldn't go up.
> Pretty sure I could fit a 20 pin, I'll have to give it a try.
> As for a 28 pin that's good idea also, but I don't use
> anything larger than 20 pin atm, thats more of a AVR/PIC thing.
>
> I always wanted to try AVR programming, but I dont know any C/C++.
> I do have an Arduino and it's fairly easy to program, but it's not
> really C. More simplified version.
>
> Any way I just might make a 28 pin proto board for the heck of it,
> I'm sure someone would find a use for it.
>
>
> "If you extend the size up to 20+ pins I would also
> make that area able to take both 0.3 and 0.6 spacing chips."
>
> I'm not sure on how to do that?
> Do you mean put 2 dip modules side by side?
>
>
>
> On Tue, 2009-11-24 at 11:31 +0000, Andy Eskelson wrote:
> >
> > A couple of suggestions:
> >
> > You are limiting yourself a little by using a DIP16
> > There are many chips such as microcontrollers in larger packages. e.g.
> > the Microchip PIC which is available in 8, 18, 20 28 pin packages and
> > so
> > on.
> >
> > Obviously a 40 pin package is rather large, and I doubt if you are
> > thinking along those lines, however you would increase the range of
> > your
> > board if you made the chip area able to take larger chips.
> > I would certainly increase it to 18pin dip, and if the size is not
> > such a
> > problem up to 28pin. If you extend the size up to 20+ pins I would
> > also
> > make that area able to take both 0.3 and 0.6 spacing chips.
> >
> > Andy
> >
> > On Mon, 23 Nov 2009 19:23:49 -0800
> > rocko <[email protected]> wrote:
> >
> > > wow, that first pic is kinda small, can't really see it too well.
> > > Iv'e attached a larger pic this time.
> > >
> > > On Mon, 2009-11-23 at 19:06 -0800, rocko wrote:
> > > >
> > > > [Attachment(s) from rocko included below]
> > > > I know the name is kinda lame, but I was up all night
> > > > finishing my little proto board and decided to give
> > > > it that name, you know lack of sleep and all.
> > > >
> > > > I'm always making little projects with the 4000 series cmos
> > > > chips, mostly oscillators for mini synth/noise boxes, and needed
> > > > something a little better than vero/strip board after
> > breadboarding.
> > > >
> > > > the board is only 7.38 sq inches, BatchPCB wanst $18 for one
> > board.
> > > > But if I order from Golden Phoenix it's only about $7. which aint
> > > > too bad.
> > > > Advanced Circuits charges less than $4 per board, but I gotta
> > order
> > > > like 150 of them.
> > > > Don't really need that many, I suppose i could sell what I don't
> > > > use, but this isn't that useful of a board, not sure if anyone
> > else
> > > > would be interested.
> > > >
> > > > Any way I've attached a .png from the 3d viewer.
> > > > I know it's not much, but it fulfills a need, at least for me.
> > > > Suggestions as always.
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Please read the Kicad FAQ in the group files section before posting
> > your question.
> > > Please post your bug reports here. They will be picked up by the
> > creator of Kicad.
> > > Please visit http://www.kicadlib.org for details of how to
> > contribute your symbols/modules to the kicad library.
> > > For building Kicad from source and other development questions visit
> > the kicad-devel group at
> > http://groups.yahoo.com/group/kicad-develYahoo! Groups Links
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
> ------------------------------------
>
> Please read the Kicad FAQ in the group files section before posting your
> question.
> Please post your bug reports here. They will be picked up by the creator of
> Kicad.
> Please visit http://www.kicadlib.org for details of how to contribute your
> symbols/modules to the kicad library.
> For building Kicad from source and other development questions visit the
> kicad-devel group at http://groups.yahoo.com/group/kicad-develYahoo! Groups
> Links
>
>
>
