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

Review V1.1 #72

Closed
10 tasks done
pathfinder49 opened this issue Mar 30, 2020 · 17 comments
Closed
10 tasks done

Review V1.1 #72

pathfinder49 opened this issue Mar 30, 2020 · 17 comments

Comments

@pathfinder49
Copy link
Collaborator

pathfinder49 commented Mar 30, 2020

Review chasnges for V1.1 from this PR.

Specific changes requiring attention:

  • DAC-SPI signal integrity
  • DAC-SPI series termination
  • DAC-SPI parallel termination (DNP)
  • P3V3_MP
  • En_AFE_PWR pull down
  • i2c dependencies
  • IC3 grounding
  • P/N12V0A capacitors
  • DAC channel layout
  • component clearances
@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • I would connect pin 8 of IC3 to GND instead of pin 9. It's a subtle difference.
  • I wouldn't pour the GND on the top and bottom layers. There is a subtle difference - it's easier to control how circuits are connected to GND. With copper pour, one can easily create parasitic GND connections between neighboring circuits. This also makes the crosstalk lower. Take into account that vias have inductances and resistances.
  • termination for 2cm traces do not make much sense but let's treat it as a lowpass filter and we want to have identical circuits for all channels
  • C106_x should have a dedicated via to GND. Now it shares with power supply caps which will affect the PSRR
  • use tented vias. The only exception is vias in the pad where it must be left open on both sides to not create acid pockets.

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • I would supply the IC6 and JP1 from P3V3. The IC17 is used to disconnect the I2C bridge from the P3V3 power domain. When P3V3 is absent, the FPGA will pull all SPI lines to 0.7V.

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • the supply of the DAC is not optimal.
    obraz
    The trace should follow the route: source -> inductor/resistor -> bulk cap -> ceramic cap -> pin
    The critical is low impedance of the ceramic cap to GND. In this case the path from this capacitor goes to the neighboring channel. Now the caps are far away from the IC. The original design did not have such problem
    obraz
    This can be improved, for example
    obraz

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • reference decoupling is critical. Now the decoupling capacitor is connected between the REF pin and GND of neighboring channels. I placed the decoupling cap between REF and GND on purpose
  • reference bulk capacitor shares ground with a decoupling cap.

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

Here are a few images from my teaching materials that explain what I meant. They come from random app notes
obraz
obraz
obraz
obraz
obraz
obraz

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • the ceramic caps are too far away from +/-12V pins of the opamps. It is not that important as in case of the DACs.
  • LDAC is too close to high impedance opamp input
    obraz
    this can be fixed in such way
    obraz

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • we can get rid of R153 ane make space for correct VREF decoupling

@gkasprow
Copy link
Member

gkasprow commented Apr 1, 2020

  • increase the clearance between the traces and copper pour because of massive antennas/resonators that cause additional coupling between tracks
    obraz

@pathfinder49
Copy link
Collaborator Author

I would connect pin 8 of IC3 to GND instead of pin 9. It's a subtle difference.

I went with pin 9 as I tested that configuration. Is there a strong reason to go with pin 8 instead?

reference decoupling is critical. Now the decoupling capacitor is connected between the REF pin and GND of neighboring channels. I placed the decoupling cap between REF and GND on purpose

Are you refering to the top and bottom GND polygon here?

pathfinder49 added a commit to pathfinder49/Fastino that referenced this issue Apr 6, 2020
@pathfinder49
Copy link
Collaborator Author

pathfinder49 commented Apr 6, 2020

@gkasprow I've pushed updates addressing your points except the IC3 pin. Could you please take another look?

@pathfinder49
Copy link
Collaborator Author

@gkasprow Do you know when you'll have a chance to look at this?

@gkasprow
Copy link
Member

@pathfinder49 next time pls write an email directly to me.

@gkasprow
Copy link
Member

@pathfinder49 where is the PCB? I cloned your repo and there is the old version..

@pathfinder49
Copy link
Collaborator Author

It's on the branch "fixes" (apologies for the poor naming). https://github.com/pathfinder49/Fastino/tree/fixes

@gkasprow
Copy link
Member

I think it is good enough. Every project can be done better, but here the main goal is high channel isolation. Let's produce it;

@gkasprow
Copy link
Member

I changed the rev_ID from 1 to 2

@pathfinder49
Copy link
Collaborator Author

@gkasprow If you merge PRs through the webinterface, the linked issues can be closed automatically 😉

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