Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schematic Cleanup, PCB stackup, Trace Rerouting #219

Open
fabianmuehlberger opened this issue Mar 21, 2024 · 7 comments
Open

Schematic Cleanup, PCB stackup, Trace Rerouting #219

fabianmuehlberger opened this issue Mar 21, 2024 · 7 comments

Comments

@fabianmuehlberger
Copy link

fabianmuehlberger commented Mar 21, 2024

Hi,

[EDIT] 18.11.2024

The schematic should follow general guidelines like:

  • Symbol naming/numbering from left top to right bottom,
  • Upper left Power, IO
  • right side MCU, peripherals (flash, crystal)
  • do not cross lines if possible
  • PWR labels always Up, GND labels always down
  • labels on symbols should sit on the line

I found this guide with basic recommendations for the schematic.

Elegant schematics
schematic checklist

A best practices regarding ground can be found here

I have not checked if the left and right side have significant functional differences, if so, making hierarchical sheets for duplicates would be suggested too, e.g. keys, LEDs, MCU on separate sheets and references to them for left and right side if the components are the same.

Regarding the PCB, I would suggest switching to a 4 layer PCB. Since ground pour is only on the top side with a high number of traces on the top and bottom, as well as layer changes of signal lines, current return paths are VERY restricted. A 4 layer PCB with 2 ground inner layers would make routing easier and improve the board overall.

I made some example changes in the corne chocolate schematic on my fork
Please let me know if you are interested in a redesign, if there is interest, I am happy to contribute.

Best Fabian

@foostan
Copy link
Owner

foostan commented Mar 21, 2024

Thank you for your suggestion. Please provide evidence to evaluate the validity of your proposal. thank you.

@fabianmuehlberger
Copy link
Author

fabianmuehlberger commented Mar 21, 2024

Deleted

@foostan
Copy link
Owner

foostan commented Mar 21, 2024

Thank you for sharing. I'll confirm the guide and fix them.

About 4 layer, could you tell me your opinion more. Could you share Pros/Cons?

@fabianmuehlberger
Copy link
Author

fabianmuehlberger commented Mar 22, 2024

Hey, It's not about the guide, these enhancements can be separately applied.

  1. Schematic rearrangement/refactor is to make it more concise. The goal is to make it easier to read and debug if there are problems. Following basic guidelines will help adapt and improve the design in the future and make it more portable.

  2. PCB stackup is a big topic itself, and I am not an expert. But 4 layer PCBs are the norm nowadays and have gotten cheap to produce; therefore we can get the advantages over a 2 layer board with basically no downsides. I see no reason for not using a 4 layer board
    These are:

  • Inner ground layers: generally speaking, you want all traces separated by a ground layer. This helps with crosstalk and provides a solid current return path. With 2 layers, this is only possible when using one side for traces and the other for ground. Obviously, this can only be done on low density boards (low component count; space for routing).
  • Easier Routing: With a 4 layer board, it is much simpler since you can use the 2 inner layers for GND and the PWR bus and use the outer layers for the signal traces. This makes routing easier, since you simply have more space to do so.
  • EMI: For commercial products in the EU an EMI/EMC test is mandatory. So far, I have not produced a PCB for the market, but it's a big topic. Following the industry norm wherever you can helps comply with those standards.
    https://www.protoexpress.com/blog/7-pcb-design-tips-solve-emi-emc-issues/

Best

@foostan
Copy link
Owner

foostan commented Mar 28, 2024

Thank you for sharing. I'll read the docs you shared.

@fabianmuehlberger
Copy link
Author

From your answer, I assume that you are not interested in me contributing to the project.
I close this issue then.

@fabianmuehlberger
Copy link
Author

Since there is an ongoing discussion regarding EMI problems, #265 I decided to reopen this issue.
It seems that the concerns in this issue are directly related with the current issues of the hardware.

@fabianmuehlberger fabianmuehlberger changed the title Schematic Cleanup + PCB stackup considerations Schematic Cleanup, PCB stackup Nov 18, 2024
@fabianmuehlberger fabianmuehlberger changed the title Schematic Cleanup, PCB stackup Schematic Cleanup, PCB stackup, Trace Rerouting Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants