-
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
Slaving DAC board #320
Comments
What do you need this to do? If you need accurate timing, I think this is The daisy chain pinout is on page 7 of this document: I believe you want daisy0in+ and daisy0in-, which are pins 4 and 5 on the The signaling is LVDS. This means that you have to drive 3.5 milliamp into All of this is fine. The problem I think you will have is that the LVDS I believe, but do not know for sure, that daisy inputs are ignored while If you can live with 4 ns start jitter, you can probably make it work. Can you do the trigger the other way? Use one of the ECL outputs on the On Thu, Feb 18, 2016 at 5:26 PM, Ryan Barnes [email protected]
|
I think we can live with a 4 ns jitter in the start time of the DAC waveform. We can try putting the pulse generator on the same clock as the DAC to maybe circumvent this jitter. We tried doing this the other way, setting the DAC as master, but the pulse generator that runs the rest of the spectrometer has very limited functionality when slaved and cannot run the spectrometer. Also switching to run the spectrometer off of the DAC is problematic because there aren’t enough independent trigger channels. We’re interested in trying to slave the DAC because it’s currently the simplest option however if this proves troublesome we may rethink our approach. I will keep you updated with my progress. Thanks for your reply,
|
I need to slave the DAC board to an external pulse generator. Which pin on the 'daisy up' ethernet plug do I need to raise? Is the logic level 5 V? and what are the constraints on trigger length?
Thanks for the help!
~Ryan
The text was updated successfully, but these errors were encountered: