Wrong attenuation range on QCoDeS parameter
Description
What is the current behavior?
The total range of the attenuation QCoDeS parameters gets set with hardcoded numbers:
vals=vals.Multiples(2, min_value=0, max_value=60),
which has been fine up to a certain point. With a new hardware revision, an attenuation chip has been taken out. That means, the actual range is 0 to 30 dB for some boards. Because of that, when the users sets a value such as 50 on a board with the new revision and then query the attenuation, they get 30 dB back. None of this is dangerous for the hardware but it is misleading for the user.
What is the expected behavior?
To get an accurrate attenuation range.
Possible fixes
A SCPI command can be written to query the attenuation range, called from some init function and used to populated the QCoDeS parameter range.
Steps to reproduce
Set output attenuation to 50 on a module with only one attenuator on the output path. Read the attenuation out. See that it's only 30.