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

Sayma clock mezzanine interface #23

Closed
10 tasks done
jbqubit opened this issue Oct 10, 2016 · 10 comments
Closed
10 tasks done

Sayma clock mezzanine interface #23

jbqubit opened this issue Oct 10, 2016 · 10 comments

Comments

@jbqubit
Copy link
Collaborator

jbqubit commented Oct 10, 2016

Interface between Sayma clock mezzanine and Sayma RTM motherboard. Same interface will be used for passive clock distribution board by WUT and on-mezzanine clock distribution by Oxford.

@cjbe @weidazh please forward to Harty

geometry and mechanical

  • what is minimum clock mezzanine geometry? WUT is presently assuming 43 x 80 x 4.2 mm
  • what IC sets/constrains this geometry
  • use same mounting to RTM motherboard as analog mezzanine interface analog mezzanine physical/interface specification #8?
  • if space is tight on RTM motherboard, mezzanine could be moved to AMC motherboard or RF-backplane clock distribution slot -> not needed

RF shield

  • minimum interior height under shield lid

PCB material/layers

  • 4-layer PCB, top layer .020" Rogers 4350B
  • single ground for analog and digital

connector choices

power/IO header routing

ADCs

  • are inputs on 24-bit calibration ADC desired ?
@hartytp
Copy link
Collaborator

hartytp commented Oct 11, 2016

@jbqubit the biggest factor in the geometry is the number of PLLs we'll need: if the 100MHz reference clock reaching the mezzanine meets the phase noise spec up to ~100kHz then we can lock the microwave VCO directly to it. If not, then we'll need to add an extra 100MHz clean-up oscillator, which makes the board bigger.

For the PLL board:
RF Input: 3V3 PECL square-wave, please (2 x SMP?)
RF Output: as input
Power: we need a clean +3V3 analog rail. +5V would be good too.

Is the "passive board" a mezzanine, which takes the front-panel SMA DAC clock input and connects it to the RTM? If so, can we give it a TCM2-43X+, ADCLK905 (or your favourite equivalent IC) & AC coupling caps to perform sine-square conversion. That way, the RTM only needs to be designed to take in a LVPECL square wave.

@dhslichter
Copy link
Member

Can the mezzanine host LDOs to make its own clean 3.3V and 5V rails from a low noise +6VDC rail? This would allow sharing of power supplies with the analog mezzanines, which would be nice. One could use the same power/IO connector with a pin-compatible wiring.

@hartytp
Copy link
Collaborator

hartytp commented Oct 14, 2016

@dhslichter I'd be happy with putting LDOs on the clock mezzanine.

@gkasprow
Copy link
Member

gkasprow commented Oct 14, 2016 via email

@sbouhabib
Copy link
Collaborator

I agree with greg the last LDO step should be on the mezzanine, and there shoul be a possiblity to get the hight possible voltage for future use (12V mains) even if it is not used at the moment, a lot of VCOs use 10V, 12 V even more, lacking this and even stepping up from 6V could be problematic in the future

@jbqubit
Copy link
Collaborator Author

jbqubit commented Oct 31, 2016

@hartytp Do you want access to one of the 24-bit calibration ADCs?

@hartytp
Copy link
Collaborator

hartytp commented Oct 31, 2016

@jbqubit If there is a spare one, I think it would be a good idea.

@jbqubit
Copy link
Collaborator Author

jbqubit commented Nov 2, 2016

@gkasprow Is this possible? I don't know if all the calibration ADCs are allocated.

@gkasprow
Copy link
Member

gkasprow commented Nov 2, 2016

At the moment we have all 16 ADC inputs connected to ADC/DAC mezzanines.
Shall I add another calibration ADC? Why would you need it?

@hartytp
Copy link
Collaborator

hartytp commented Nov 8, 2016

Shall I add another calibration ADC? Why would you need it?

Don't bother. I have no immediate plans to use an ADC on the clock mezzanine. My comment was just that if there had been a spare ADC channel, then it might come in use later.

@jordens jordens modified the milestone: 0.1.1 (prototype 1 first review) Nov 9, 2016
@jbqubit jbqubit closed this as completed Dec 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants