Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Reverse frequency sweeping on Rohde&Schwarz ZNB40 via QCoDeS

Open
#7,100 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the ZNB driver entry point in qcodes.instrument_drivers.rohde_schwarz.ZNB and read the linked Rohde & Schwarz reverse-sweep FAQ. Inspect how frequency_start and frequency_stop are validated for measurement channels; done means the driver can represent a reverse sweep for a channel without rejecting a lower stop frequency.

Written by the indexing model from the issue text.

Description

Hi,

This is mainly a feature request but it would be nice if the user has the option to define a frequency sweep in the opposite direction for a measurement channel. Currently for instance, if measuring S21 for a DUT, we set

from qcodes.instrument_drivers.rohde_schwarz.ZNB import ZNB
station.add_component(
    ZNB(
        name="VNA",
        address="<ip_address>",
        init_s_params=True,
    )
)     
station.VNA.S21.frequency_start(500e6)
station.VNA.S21.frequency_stop(1000e6)

to perform the measurement. However, QCoDeS gives out an error when setting the attribute frequency_stop to be lesser than frequency_start.

Looking up the manual for the ZNB40 VNA in particular, we find a section on independently defining the port configuration via the K4 option (see this FAQ from R&S). Interestingly enough, atleast on the VNA we have at hand I was unable to find this option via the in-built local GUI of the VNA.

It would be nice if the driver could include this feature.

Dominant language
Python
Stars
459
Forks
359
Avg merge
2d 10h
Merged PRs (30d)
79

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/Qcodes

All issues in microsoft/Qcodes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.