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.

Sign up for GitHub

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

Jump to bottom

DecaDAC ramp parametrization, interruption, set_dac, trigger results in uncontrolled ramp #109

Closed
paulsurrey opened this issue Nov 4, 2024 · 1 comment
Closed

DecaDAC ramp parametrization, interruption, set_dac, trigger results in uncontrolled ramp #109

paulsurrey opened this issue Nov 4, 2024 · 1 comment
Assignees
@paulsurrey @THuckemann
Labels
bug Something isn't working question Further information is requested

Comments

@paulsurrey
Copy link

When starting a DecaDAC ramp but a trigger is not send to the DecaDAC, then the ramp is still armed.
A voltage set command also changes the ramp range. It is changed to the full output range (

QuMADA/src/qumada/instrument/custom_drivers/Harvard/Decadac.py

Line 433 in c49b60d

self.ask_raw(f"U65535;L0;D{code};")
). And the ramps slope is not set to 0.
Thus, if then a trigger is given, the DecaDAC starts to ramp to one of the bounds of its output range.
paulsurrey pushed a commit to paulsurrey/QuMADA that referenced this issue Nov 4, 2024
@paulsurrey
Limited sweep range for voltage set commands, such that uncompleted r…
6c5a9b8 
…amps don't ramp. Also triggers are reset.qutech#109
@THuckemann THuckemann added bug Something isn't working question Further information is requested labels Jan 3, 2025
@THuckemann THuckemann mentioned this issue Jan 28, 2025
Merged
@THuckemann
Copy link
Collaborator

Used Paul's fix. Seems to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paulsurrey paulsurrey

@THuckemann THuckemann

Labels
bug Something isn't working question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paulsurrey @THuckemann