my first pcb (opinions needed)

Go To Last Post
25 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Guys,

 

I have just "finished" my first PCB. Prior to that I read a few documents, especially the ones you guys suggested here.

I am not saying that I could follow every "rule" but I tried my best.

 

Please not that I have never used eagle before nor any other tool like that....

 

So keep in mind the above and please let me know a few opinions, the biggest issues with it.

 

I will try to consider them if possible.

 

Notes:

- I know that I have so many drill sizes unfortunately and as I know it is not possible to change it in the PCB (at least I could not find it). Next time I will take care of this as well...

- I am a beginner and I know you guys will find 100+ errors but please let me know only the "big ones" first...

- I did not use the autorouter.

- I have not "optimized" it yet. I might find a better routes but firstly I wanted to know your opinions, because it is possible that I need to throw it to the trash :)

 

 

Thanks in advance,

Mitya

 

Update1: the files are Eagle files ...

 

Update2: I added pics as well of the BCP itself... (don't know how to generate good GERBER files yet)

 

 

Attachment(s): 

Last Edited: Wed. Mar 28, 2018 - 10:37 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Over the last few years KiCad is gaining a lot of popularity.

KiCad is becoming a pretty profesional and easy to use Schematics / PCB program.

KiCad is also Open Source and released under the GPL licence. It will therefore always stay Free (3x).

KiCad has no artificial limits on board size, pin count, layers etc.

 

Some time ago Autodesk bought Eagle and they changed the "free" version to a subsribtion based model.

That was a good reason for a lot of people to change from Eagle to KiCad.

 

I do not have Eagle, nor any interest in using it.

There is a converter for KiCad to import Eagle projects, but that is not perfect yet.

 

If you want some simple comments, you are much more likely to get answers if you post your project in a common format.

Instead of the "Eagle" project, can you post it as an PDF, SVG, or maybe even the gerber files?

 

Edit:

I am somewhat curious of the quality of converting Eagle -> KiCad so I'll give it a try.

I'll probably be back in an hour or so.

https://duckduckgo.com/html?q=Eagle+KiCad+Converter

 

Edit 2:

KiCad users are anxiously waiting for the official release of Version 5, which has the Eagle importer integrated.

If I want to convert an Eagle Project to KiCad I would have to run it through some (outdated?) Python scripts by hand.

This is likely going to be of not much use to anyone but (maybe) you.

I can not update to 5.0 yet myself because I need the official 4.0.7 for an important project right now.

 

If you are interested in KiCad there are 2 places I can highly recomend. The official KiCad site and the KiCad forum (Linked from the KiCad site).

http://kicad-pcb.org/made-with-kicad/

https://forum.kicad.info/

Doing magic with a USD 7 Logic Analyser: https://www.avrfreaks.net/comment/2421756#comment-2421756

Bunch of old projects with AVR's: http://www.hoevendesign.com

Last Edited: Wed. Mar 28, 2018 - 12:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

I'm not sure how much of this is important, and how much is just my personal preferences:

You have a bunch of places where traces are very close together, or run very close to pads, and they don't really need to be.  Even though you have a relatively generous "clearance" DRC parameter set, and the separations meet them, I would normally space things out conservatively, with larger gaps.  (this repeats all over the board, but here's one example:)

 

Current:

 

 

 

My style:

 

Your signal traces are very wide (25mil) for any sort of professional manufacturing process, but the clearance (10mil) is "small" for homebrew processes.  I'd normally set both to about 15mil (for a slightly smaller total width for a track+spacing)  Maybe 0.5mm for homebrew (somewhat depending on how the specific homebrew process tends to fail...)

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You might want to show a gif of the pcb so others can look at it. Unfortunately Eagle doesn’t work on an iphone.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Here's an animation of @westfw's changes so you can better see:

 

"Experience is what enables you to recognise a mistake the second time you make it."

"Good judgement comes from experience.  Experience comes from bad judgement."

"Wisdom is always wont to arrive late, and to be a little approximate on first possession."

"When you hear hoofbeats, think horses, not unicorns."

"Fast.  Cheap.  Good.  Pick two."

"We see a lot of arses on handlebars around here." - [J Ekdahl]

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My thought @westfw's idea:

Make sure that the desing rules are compatible with what your board house can manufacture.

PCB fab's often charge extra if the traces / clearances get too small.

 

In KiCad such handwork does not stay long on the PCB.

In KiCad there is an extremely handy function that if you are routing a trace it can push 4 or 5 other traces aside (All within the design rules) to make room for an extra trace.

In this way if you add a via to a trace you are drawing it automatically and in real time pushes the traces on both sides of the board away to make room for the via.

This feature alone has not only saved me hours of work on a densely populated board, but I probably could not have routed that board (on 2 layers) without that function.

Doing magic with a USD 7 Logic Analyser: https://www.avrfreaks.net/comment/2421756#comment-2421756

Bunch of old projects with AVR's: http://www.hoevendesign.com

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

PCB fab's often charge extra if the traces / clearances get too small.

Most of the low-cost board houses do 6/6 or at least 8/8mil width/clearance, so the trace width/separation he has (25/10) is numerically/theoretically just fine.  I just like to be very conservative (especially if I'm making the boards myself, or dealing with a very low-cost manufacturer); it makes for "wiggle room" in fab AND assembly.

 

I think the latest EAGLE (v8.x) has "push and shove" features as well (but I bought a copy back in the 7.x days, and I'm not crazy about "upgrading" to the new license model.)

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

westfw wrote:
I think the latest EAGLE (v8.x) has "push and shove" features as well (but I bought a copy back in the 7.x days, and I'm not crazy about "upgrading" to the new license model.)

Agree with you "Westfw" I hope if all customer not update they will change policy. 

Thierry

Thierry Pottier

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Kartman wrote:
You might want to show a gif of the pcb so others can look at it. Unfortunately Eagle doesn’t work on an iphone.

 

I see your points guys, sorry for that.

I have just added pics to the original post.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Paulvdh wrote:

In KiCad there is an extremely handy function that if you are routing a trace it can push 4 or 5 other traces aside (All within the design rules) to make room for an extra trace.

 

This feature sounds very interesting. I will try KiCAD 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0