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

Expose property for master clock range #44

Closed
CodaCarlson opened this issue Sep 7, 2015 · 2 comments
Closed

Expose property for master clock range #44

CodaCarlson opened this issue Sep 7, 2015 · 2 comments

Comments

@CodaCarlson
Copy link

I would like for the master clock range to be exposed in the property tree. I see auto_tick_rate and tick_rate as well as the dsp rate range, however, at least for the b210 max out at 16Msps without a master_clock_rate arg. I would like to be able to dynamically tell what the possible clock range. I look in the b200_io_impl and it looks like it's just a define. I could just include that define, however, I would rather something be exposed in either multi_usrp or the property tree since I am working with different USRP types.

@mbr0wn
Copy link
Contributor

mbr0wn commented Sep 29, 2015

This is a reasonable request, and I like the idea. There's a couple of issues that need resolving; for example, the X-Series allows certain discrete master clock rates (albeit not at runtime). The B200- and E310-series already have different ranges, so this would be quite useful there.

@mbr0wn
Copy link
Contributor

mbr0wn commented Mar 28, 2018

@CodaCarlson We have an actual fix in the pipeline. It's going through review and CI and will probably go live in a few days.

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

2 participants