Program that can log/control many multimeters and other devices.

[Gertjan]

I can support #interface setAmplitudeV by adding an extra SCPI command to make sure the generator is in the correct mode (dBm or V):

As long as logging output do not change!

Yes, logging will also change from dBm to V or vice versa.. (On both generators it is a mode change)
But I don't think this a a problem. One will work either with dBm or in Volt. (just what is appropriate for the current measurement)
So the generator stays in the current used amplitude unit.

TC has a function for dB, or rather a couple

Yes, I found those. But could not figure out how to use them for converting dBm to V and vice versa....

regards, Gertjan.

[HKJ]

Yes, logging will also change from dBm to V or vice versa.. (On both generators it is a mode change)
But I don't think this a a problem. One will work either with dBm or in Volt. (just what is appropriate for the current measurement)
So the generator stays in the current used amplitude unit.

The issue is if the user uses the function and the column change unit, that means it will list values with two different units in the same column at the same time.

TC has a function for dB, or rather a couple

Yes, I found those. But could not figure out how to use them for converting dBm to V and vice versa....

They are only from volt to db, maybe I ought to add the reverse also.

They one you need is:
dBm(voltage,resistance)

With resistance==50

[Gertjan]

Yes, logging will also change from dBm to V or vice versa.. (On both generators it is a mode change)
But I don't think this a a problem. One will work either with dBm or in Volt. (just what is appropriate for the current measurement)
So the generator stays in the current used amplitude unit.

The issue is if the user uses the function and the column change unit, that means it will list values with two different units in the same column at the same time.

My thinking is that if one, for example, is working in Volt, logging will be done in Volts.
Using the #interface commands to set/get Volts will keep the mode in Volt. So no problem.
Only when using the dBm #interface commands, the mode will change. But who will use/need the dBm commands when working in Volts?

But maybe I am missing something?
If you are not happy with it, I will leave it out.

Regards, Gertjan.

[HKJ]

Yes, logging will also change from dBm to V or vice versa.. (On both generators it is a mode change)
But I don't think this a a problem. One will work either with dBm or in Volt. (just what is appropriate for the current measurement)
So the generator stays in the current used amplitude unit.

The issue is if the user uses the function and the column change unit, that means it will list values with two different units in the same column at the same time.

My thinking is that if one, for example, is working in Volt, logging will be done in Volts.
Using the #interface commands to set/get Volts will keep the mode in Volt. So no problem.
Only when using the dBm #interface commands, the mode will change. But who will use/need the dBm commands when working in Volts?

But maybe I am missing something?
If you are not happy with it, I will leave it out.

Anything that changes the columns belong in the "Mode" popup, there a checkmark (#cmdModeCheck) to select between dBm and V would be fine.