-
Notifications
You must be signed in to change notification settings - Fork 91
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
Clarification on intended behaviour of AveragerProgram.trigger()
#153
Comments
prog.trigger()
AveragerProgram.trigger()
Your understanding is correct, and it is strange that you're seeing a pulse even though your example never executes the program, or even uploads it to the FPGA - as you say, that would be done by Maybe the pulse you're seeing is nothing to do with your program, it is happening when you initialize |
Hi All, |
I think you're misunderstanding what You can set the QICK to wait for an incoming pulse on a PMOD pin before starting a program: https://qick-docs.readthedocs.io/en/latest/_autosummary/qick.qick_asm.html#qick.qick_asm.AcquireMixin.acquire, also #137 But that may not do everything you want. |
Hi, this is also what I need, but is there an updated link to the page? The link above doesn't work for me. |
Sorry, we reconfigured our docs site, just remove the |
Hi,
I am trying to understand the API, and I have encountered something that seems to be either a bug or unintended behaviour. (ZCU216, latest distribution)
Pin PMOD_0 is activated briefly (long enough to see on a multimeter) when
trigger
is called. From my understanding the expected behaviour is thatprog.trigger()
adds thetrigger
command to anasm
program, which is only actually read by the device when calling anacquire
or similar method. Here it appears that the trigger happens immediately; or, at some point in this script, the PMOD pin is activated unintentionally. Can you clarify if that is the case?Thanks!
The text was updated successfully, but these errors were encountered: