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

question: should we compensate for latency of FUD to DAC output of DDS (pipeline delay)? #36

Closed
ghost opened this issue Jun 20, 2015 · 4 comments

Comments

@ghost
Copy link

ghost commented Jun 20, 2015

No description provided.

@ghost
Copy link
Author

ghost commented Jun 20, 2015

We should do this. The AD9858 specification says this is 83 cycles of SYS_CLK (1 GHz). This is a fixed delay and can be trivially compensated for by Artiq. It's one less thing a user has to worry about.

@jordens
Copy link
Member

jordens commented Jun 21, 2015

Rationale?
Doing that in gateware does not gain anything. My idea was always to define it in the ddb and then handle it in software. But that needs spec'ing.

@jordens jordens closed this as completed Jun 21, 2015
@ghost
Copy link
Author

ghost commented Jun 21, 2015

A straightforward way of achieving pipeline delay compensation is using the gateware. If you prefer to implement this in software please do so. I'd like to be able to report at the group meeting on Monday that the AD9858 implementation in Artiq passes the test suite. Without pipeline delay compensation it does not.

@jordens
Copy link
Member

jordens commented Jun 21, 2015

Could you point me to a test in the testsuite that needs this to pass? It seems naive to compensate w.r.t. DAC output as the reference plane if there are (frequency dependent even!) delays in the trafos, amplifiers, cables after the DAC output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant