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

Fast waveform upload on Keysight awg819x #3

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

timoML
Copy link
Contributor

@timoML timoML commented Nov 12, 2021

Using the IVI-COM driver from Keysight, waveform upload speeds can be massively boosted (>200 MB/s via PCIe).

Description

Caveats:

  • due to comtypes usage, only works on Windows
  • the limiting factor in total upload time seems now often the binary sample compilation needed after getting floats from the sequence generator

How Has This Been Tested?

  • 3 setups with both awg8190, 95.

Types of changes

  • Bug fix
  • New feature
  • Breaking change (Causes existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • I have documented my changes in /docs/changelog.md.
  • My change requires additional/updated documentation.
  • I have updated the documentation accordingly.
  • I have added/updated the config example for any module docstrings as necessary.
  • I have checked that the change does not contain obvious errors
    (syntax, indentation, mutable default values, etc.).
  • I have tested my changes using 'Load all modules' on the default dummy configuration.
  • All changed Jupyter notebooks have been stripped of their output cells.

@timoML timoML changed the title Fasst waveform upload on Keysight awg819x Fast waveform upload on Keysight awg819x Nov 12, 2021
@timoML
Copy link
Contributor Author

timoML commented Oct 9, 2023

Please note that there is a confirmed memory leak occuring somewhere between the Keysight driver and comtypes (1.2.0). Uploading multiple waves will cause memory usage rise without proper clearing. Thanks @PJVetter for investigating.

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

Successfully merging this pull request may close these issues.

1 participant