-
Notifications
You must be signed in to change notification settings - Fork 21
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
ADC LED Questions #355
Comments
This isn't super surprising. Check the current limit on your power supply, On Jun 30, 2016 3:23 PM, "amopremcak" [email protected] wrote: Two of our ADCs are displaying some strange behavior. One ADC is build #1 Build # 7 ADC without reference clock: Once we plug the 1.5 V peak-to-peak 10 MHz reference into clock in, the LED Build # 7 ADC with reference clock: Build # 1 ADC with reference clock: Our connections were to the screw terminals were replaced with the parts Why would plugging in the 10 MHz reference clock signal effect the LEDs on — |
Whenever anything weird happens with these boards it's a power issue.
|
Yea I haven't bothered you guys about them for a while. I took your words to heart and fixed up the insides of our power supplies and our cabling from the power supplies to the boards. I am finally confident in our setup but this was a new failure mode. The supply isn't hitting the current limit as it is not beeping/blinking. I will try cranking up the voltage corresponding to this LED once I observe the effect you are talking about. The strange thing is that this isn't happening on either of the two DACs we have on this rack. Thanks for the feedback @DanielSank |
Your suggestion did the trick @DanielSank . When hooked up to the 10 MHz reference clock, the pin tied to the 1.5 V supply dropped by roughly 300 mV. Any idea of why that ought to occur? |
Higher current draw plus nonzero resistance of cables etc.
|
Word. |
We are having a hard timing getting the LEDs labeled Dt1 A - Dt4 -A on the ADCs to go off after running the DAC bring up script. The number of times we have to run the ghz_dac_bringup.py script seems to vary with the power level at the CLK IN port on the boards. Our cables are equal lengths from the same 10 MHz reference clock. We have varied the power from 1.5 V peak-to-peak to 0.7 V peak-to-peak. What power level do you typically go with? Also, do you guys use any higher level servers/scripts to interface with your DACs/ADCs above and beyond the ghz_fpga_server? I guess I am just really confused at how to proceed. Robert has us trying to bring up randomized bench marking using these boards but we don't even have full control over the hardware yet. I suspect that some of the custom code that we are using to control these boards is the source of our problems. |
Any feedback on the getting the Dt1A-Dt4A lights to go off would greatly appreciated. |
Two of our ADCs are displaying some strange behavior. One ADC is build #1, the other is build #7. Before plugging in the 10 MHz reference clock, all 6 LEDs on our ADCs are illuminated. Below are photos:
Build # 7 ADC without reference clock:
Build #1 ADC without reference clock:
Once we plug the 1.5 V peak-to-peak 10 MHz reference into clock in, on of the LEDs goes off as well as one of the other LEDs (the group of four) which are related to the PLL I believe. Below are photos:
Build # 7 ADC with reference clock:
Build # 1 ADC with reference clock:
Our connections to the screw terminals were replaced with the parts you recommended:
Why would plugging in the 10 MHz reference clock signal effect the LEDs on the other side of the board? Have you guys ever seen this type of behavior before?
The text was updated successfully, but these errors were encountered: