-
Notifications
You must be signed in to change notification settings - Fork 4
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
Shuttler analog bandwidth #36
Comments
@dhslichter @adbr8389 @gkasprow How do you find current bandwidth? Do we need to fix AFE to follow statement in Wiki (~15 MHz)? |
@kaolpr what is the gain in the AFE currently? What is the bandwidth for signals measured before the AFE? There are several places that could be causing this issue with the bandwidth. |
AFAIK this was measured before AFE. Tomorrow I'll ask @jmatyas to provide more details. |
the simulations in #28 appear to be with an ADA4896? |
@kaolpr looks like this is just an effect of C40/C41 giving a lowpass rolloff. We should change those capacitance values to 33 pF from 100 pF and will get back the ~15 MHz bandwidth. @gkasprow was there a reason these capacitors needed to be 100 pF? For our purposes we would rather have the output bandwidth of the system limited by user-implemented passive filters placed after the remote AFE outputs, and have the FMC and remote AFE boards keep as much of the available bandwidth as possible. The FMC DAC AFEs should have a 3dB bandwidth of ~30 MHz or higher per ADA4896 datasheet, with no filter capacitor in the feedback loop (confirmed with simulations). Cutting this down to ~15 MHz with a small filter capacitor (22 or 33 pF) in C40/C41 is acceptable, but let's not go to stronger filtering than this on the FMC card. |
What is the IC used for the differential amp after the ADA4896's? If it has some smallish capacitive input, it could explain the discrepancy between Daniel's estimation of a 33 pF cap for a 15 MHz bandwidth. |
The 33 pF = 15 MHz was only a coarse estimate, I think the measured data seem reasonable. Glad to see that this increased the bandwidth @kaolpr. Next question is whether we should increase further (e.g. 10 pF, or just DNP these capacitors). I would be in favor of testing with capacitors removed and ensuring the op amp outputs are stable (they should be, since we are at G=5). This gives maximum bandwidth out of the FMC card. One can always use following components to reduce the bandwidth as desired for applications, but this would make the FMC card maximally useful for different tasks. |
Issues fixed: - [x] TEMP_ALARM does not turn off N3V0A PS #41 - [x] [FMC_DAC_PSU] Wrong PN in R130 #37 - [x] FMC VIO_B_M2C not connected #32 - [x] HW issues #30 (remove R12/R13) - [x] Schematics details #27 - [ ] AFE AUX PSU connection crossed #35 -> (AUX PSU will be changed accordingly) - [x] mechanical issues #31 - [x] Shuttler analog bandwidth #36 -> 33pF caps -> ~12MHz BW. Other fixes: - [x] Shuttler FMC stackup adjusted - [x] Added missed templates - [x] P_version project parameter added - [x] Shuttler AFE stackup table added - [x] Shuttler AFE - FTG added - [x] Shuttler AFE - keepout for NPTH added
Issues fixed: - [x] TEMP_ALARM does not turn off N3V0A PS #41 - [x] [FMC_DAC_PSU] Wrong PN in R130 #37 - [x] FMC VIO_B_M2C not connected #32 - [x] HW issues #30 (remove R12/R13) - [x] Schematics details #27 - [ ] AFE AUX PSU connection crossed #35 -> (AUX PSU will be changed accordingly) - [x] mechanical issues #31 - [x] Shuttler analog bandwidth #36 -> 33pF caps -> ~12MHz BW. Other fixes: - [x] Shuttler FMC stackup adjusted - [x] Added missed templates - [x] P_version project parameter added - [x] Shuttler AFE stackup table added - [x] Shuttler AFE - FTG added - [x] Shuttler AFE - keepout for NPTH added - [x] R12 marked as DNP
According to wiki, Shuttler's analog bandwidth is supposed to be around ~15 MHz, however after some testing on Shuttler v1.0 it seems to be closer to 6 MHz :
To achieve those results:
The text was updated successfully, but these errors were encountered: