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

Urukul - initial routing #321

Closed
gkasprow opened this issue Sep 21, 2017 · 26 comments
Closed

Urukul - initial routing #321

gkasprow opened this issue Sep 21, 2017 · 26 comments

Comments

@gkasprow
Copy link
Member

@jordens The routing is done. It is still preliminary. Once you accept it, I will finish cosmetics, pour polygons and start PI & SI & Thermal analysis. The bottom side of the PCB below DDS chips is free so one can use it to glue a heatsink.

@hartytp
Copy link
Collaborator

hartytp commented Sep 21, 2017

Maybe too late to do anything about this, but it would be nice to standardise FP layout a little bit between the EEMs. In particular, it would be nice if both Clocker and Urukul had their clock input SMAs in similar locations.

@jordens
Copy link
Member

jordens commented Sep 21, 2017

@gkasprow excellent! will do.

@jordens jordens added this to the 0.1 design milestone Sep 21, 2017
@hartytp
Copy link
Collaborator

hartytp commented Sep 21, 2017

I'm out of the lab atm with no access to Altium, and it's hard to follow this kind of thing on the PDFs. I'll have a quick look, but can @cjbe or @klickverbot have a more careful look using Altium and sign off on this, please?

@jordens
Copy link
Member

jordens commented Sep 21, 2017

Yes @gkasprow could you add Gerbers?

@gkasprow
Copy link
Member Author

@jordens I added Gerbers. I also updated pdfs.

@gkasprow
Copy link
Member Author

@hartytp It's easier to change the clock input on clocker module than on DDS.

@hartytp
Copy link
Collaborator

hartytp commented Sep 22, 2017

@gkasprow Had a quick look over the PDFs, and it generally looks like a good layout.

To do a better check, I'd really need Altium to follow what the traces are connected to etc.

@hartytp
Copy link
Collaborator

hartytp commented Sep 22, 2017

Closing, as this seems to have been superseded by #322

@hartytp hartytp closed this as completed Sep 22, 2017
@jordens
Copy link
Member

jordens commented Sep 22, 2017

This is the issue for doing the review. It should be closed when done with the review. The other issue(s) are those arriving from the review. Note the different assignees.

@jordens jordens reopened this Sep 22, 2017
@jordens
Copy link
Member

jordens commented Sep 22, 2017

@hartytp I am done at the rough level @gkasprow requested. I'll leave this open for you or others who want to review.

@jordens jordens modified the milestones: 0.1 design, Urukul 0.1 design Sep 22, 2017
@gkasprow
Copy link
Member Author

Here is how the voltage drop looks like for 1.8V rail. This is not optimised PCB.
So with existing layout the board would probably not work or work in not reliable way. Instead of 1.8V the DDS chips would get 1.5V in the worst case, under assumption that with lower voltage they still consume same current.
I post this example to show how important design verification is :)
obraz

More critical is current density. Without optimisation we exceed the limit 10 times. It means that sooner or later the copper will overheat and may burn.
obraz

@gkasprow
Copy link
Member Author

gkasprow commented Sep 24, 2017

And after optimisation we get 39mV of drop
obraz
Current density does not exceed 36A/mm2 so it is well below the limit.
obraz

@gkasprow
Copy link
Member Author

gkasprow commented Sep 24, 2017

I did simple thermal simulation. The conditions are below:
obraz
And the results:
obraz

@gkasprow
Copy link
Member Author

gkasprow commented Sep 24, 2017

The same conditions but flow rate reduced to 10cm/s:
The board will switch off the power supply at 80deg.

obraz

Fow rate 200cm/s
obraz

@gkasprow
Copy link
Member Author

gkasprow commented Sep 24, 2017

The 24572-407 cooling unit which Joe ordered, generates 36m3/h of flow. After translation assuming that we have rectangular duct of 160x480mm, we get 130cm/s of air speed. So we should be fine providing that we block unused slots. Of course the unit conversion works under assumption there are no obstacles in the duct which is not true in our case.
For MTCA there are special dummy modules that provide such function, there should be similar for 3U.
Another issue is supply of the fans (12V, 0.7A), maybe it should be connected to the same power source as the Kasli/VHDCI to avoid operation of EEMs without cooling.

@gkasprow
Copy link
Member Author

at 130cm/s the temperature distribution is here:
obraz

@jordens
Copy link
Member

jordens commented Sep 24, 2017

Power (assuming the other rails are similar) and thermal look ok to me.
Is this board/part/copper temperature or air boundary layer?
And all the coupling via exposed pads and copper planes is included?
We could consider rotating the four channels by 90 degrees together. That seems to give about 5-10 degC more headroom. But likely not worth the trouble.

  • We should move IC12 as high up as possible so that it sees more of the relevant peak temperature.

@jordens
Copy link
Member

jordens commented Sep 24, 2017

@gkasprow Also could you review the component choices from the perspective of the testing that you would like to do with the AD9912 prototype boards before you send them to us (testing with ADI software+LVDS driver, etc)?

@hartytp
Copy link
Collaborator

hartytp commented Sep 24, 2017

@gkasprow Also could you review the component choices from the perspective of the testing that you would like to do with the AD9912 prototype boards before you send them to us (testing with ADI software+LVDS driver, etc)?

@jordens @gkasprow What is the plan for testing the AD9910 variant? @gkasprow Can you verify the performance using one of the prototype boards we've paid for (this will need to be done for the NU-servo project).

@hartytp
Copy link
Collaborator

hartytp commented Sep 24, 2017

Another issue is supply of the fans (12V, 0.7A), maybe it should be connected to the same power source as the Kasli/VHDCI to avoid operation of EEMs without cooling.

That's quite a lot of current, given that our PSU is only 5A.

Since these boards have over temperature shutdown, it might be better to leave the fans independent of Kasli.

@gkasprow
Copy link
Member Author

@jordens This is very rough thermal simulation. It takes into account copper distribution but IC models are very simplified.
For testing I will use 9910 and 9912 devkits together with TTL to LVDS board. Not all features could be tested (i.e. synchronisation) so to make tests complete I'd need ARTIQ driver.
I will need to produce both variants to do the tests. Which means additional tooling cost because component population is quite different - too many of them to do it manually.

@jordens
Copy link
Member

jordens commented Oct 10, 2017

The testing of the AD9910 synchronization only needs setting of the registers. If the ADI tool gives you access to those that should be fine.

The new routing looks good! Really nice and well thought through.

  • A few stray wires around still.
  • I guess the SYNC distribution if matched yet.
  • And there is no space for clips to shield IC19? (It's OK if there isn't, just making sure we understood each other).
  • Is it OK to power the SYNC distribution IC4, IC9, IC16 from P3V3A and not from P3V3? They are not noise sensitive and more of an aggressor on P3V3A IMHO. (IC19 and OSC1 should definitely stay on P3V3A).
  • It is slightly irritating that the EEM sub-circuits have their suffixes mixed (J1A is EEMB etc).

@gkasprow
Copy link
Member Author

@jordens I didn't finish routing yet.

@jordens
Copy link
Member

jordens commented Oct 10, 2017

I know. ;) Just providing some early feedback.

@gkasprow
Copy link
Member Author

@jordens I didn't shield IC19 because there is not much to shield. Most tracks go on bottom or on mid layers. Frankly speaking, I believe that we won't need any shields at all.
I replaced names of J1A and J1B.
The IC4,9,16 are separated by ferrite beads, but it's true, they can be supplied from 3V3. It simplifies routing and makes 3.3VA rail less loaded.

gkasprow added a commit that referenced this issue Oct 17, 2017
@jordens
Copy link
Member

jordens commented Oct 17, 2017

@gkasprow Thanks! Do you want to have us take another look at it (we'd need a git tag and the complete data package uploaded to the release)? Or can we slot it into the production now?

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

3 participants