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

[gby]

HKJ,

Attached is a debug session doing the 4 steps that I listed.  There are no errors in the log.

I often turn devices off, turn another device on, and then hit the Reconnect button.  I have never seen this issue before.

FWIW I was last running V3.53 and just switched to V3.57 today.

Josh,

My step statement "Log some data" means hit the log button, wait a moment, hit the stop log button.  So, I was only logging data while the devices connected were stably connected.

[flash2b]

HKJ,

numberDual sends its two values separated by a space, for example:

:write: COMP:SLIM
Tx: COMP:SLIM 2.0 5.0

Many SCPI devices expect a comma, like COMP:SLIM 2.0,5.0, and take only the first value otherwise. Right now this needs a #scpiCmd wrapper:

#scpiCmd compSlim tx COMP:SLIM (replace(value," ",","))

Would it be possible to add an optional delimiter to numberDual, like the set control has? For example a :delimiter: tag:

:delimiter: ,

[HKJ]

HKJ,

numberDual sends its two values separated by a space, for example:

:write: COMP:SLIM
Tx: COMP:SLIM 2.0 5.0

Many SCPI devices expect a comma, like COMP:SLIM 2.0,5.0, and take only the first value otherwise. Right now this needs a #scpiCmd wrapper:

#scpiCmd compSlim tx COMP:SLIM (replace(value," ",","))

Would it be possible to add an optional delimiter to numberDual, like the set control has? For example a :delimiter: tag:

:delimiter: ,

Try:
:write: COMP:SLIM #,#

It can also be written as:
:write: COMP:SLIM (value+","+value2)

[flash2b]

Thx, that works !

12669.42ms LCR2020: Tx <COMP:SLIM 2.0,4.0>
12671.70ms COM7: Tx: <COMP:SLIM 2.0,4.0.> 43 4F 4D 50 3A 53 4C 49 4D 20 32 2E 30 2C 34 2E 30 0A
12987.44ms LCR2020: Tx <COMP:SLIM?>
12990.42ms COM7: Tx: <COMP:SLIM?.> 43 4F 4D 50 3A 53 4C 49 4D 3F 0A
12995.12ms COM7: Rx: <+2.00000e+00,+4.00000e+00> 2B 32 2E 30 30 30 30 30 65 2B 30 30 2C 2B 34 2E 30 30 30 30 30 65 2B 30 30
12995.67ms LCR2020: Rx <+2.00000e+00,+4.00000e+00>
12996.28ms LCR2020: Rx as numbers <2.0 4.0>

[HKJ]

TC has 3 ways you can add parameters to commands.
1) Do nothing, i.e. only write the command and TC will put the parameter(s) at the end of the line.
2) Using #, this allows parameters to placed in the middle of a command line.
3) Using expressions, i.e. (value), this makes it possible to calculate on parameters, before they are transmitted.

Controls with multiple parameters (numberDual and multi) works nearly the same way, with the following modification:
2) Each # used will take the next parameter
3) More values are declared, they are value,value2,value3,etc... This makes it possible to calculate on values and to swap sequence.

[flash2b]

I have update by Owon LCR2000 series (and Anbai/Applent variants) with 3 new tabs

Release notes:
Added: Comparator tab: state, mode (Δ, Δ%, SEQ), nominal value, number of bins, secondary limits, AUX bin, beep and open check
Added: Bins tab: editor for the 9 comparator bins, with Send, Retrieve, Save and Load; the bins are retrieved automatically at connect
Added: #interface readFrequency, set/getFrequency, set/getVoltage, set/getCurrent and set/getBiasVoltage
Modified: Monitor 1 and 2 modes split over two lines, setup window is narrower
Modified: Trigger and Correction now use toggleButton controls, List tab got a separator below List Parameter
Modified: metadef token MaxFreq renamed to MAXFREQVAL, matching the TICKVAL naming
Modified: Configuration line uses MAXFREQVAL, shows DCR and Bias for all models except the AT810A
Fixed: typo in Automatic Level Control
Added: List tab: editor for the 10-point list sweep, with Send, Retrieve, Save and Load; the list is retrieved automatically at connect adapted from the Yokogawa 755x 756x v1.13 Program feature
Added: Device info control - model, ID string, interface type and address, read with the new deviceInfo? command
Modified: File Load, Save and Delete combined into one File Action row
Fixed: File load, save and delete always used file 0; the selected file number is now sent with each command
Fixed: Removed unneeded page names from :update: lines

I also defined a #interface for #interfaceType LCR since that is missing on the documentation.

Well this major update can now be added to the next release of TC.

 Owon LCR2000.zip (11.97 kB - downloaded 14 times.)
 

[HKJ]

I have update by Owon LCR2000 series (and Anbai/Applent variants) with 3 new tabs

Updated, thanks.

That was a serious update!

[gby]

I have created a definition for the Owon OWH9811, OWH9811B and OWH9822 1-phase Power Meters

flash2b,

I note in the device file that the interface definition line is:
   #interfaceType Power Power:2 Power:3 Power:4 Power:5

Please note that previous Power Analyzers like
   Yokogawa WT3000
   Yokogawa WT5000
   Vitrek PA9000
   Hioki PW6001
all use
   #interfaceType PA

So, at the moment we have two different category names for power meters:  "PA" (Power Analyzer) and "Power".  It would be better if we only had one.  From my selfish perspective I vote for "PA" because I have been using that for years and have scripts using that.  Could it make sense to change this Owon power meter definition to match the others and use "PA"?

[HKJ]

I have created a definition for the Owon OWH9811, OWH9811B and OWH9822 1-phase Power Meters

flash2b,

I note in the device file that the interface definition line is:
   #interfaceType Power Power:2 Power:3 Power:4 Power:5

Please note that previous Power Analyzers like
   Yokogawa WT3000
   Yokogawa WT5000
   Vitrek PA9000
   Hioki PW6001
all use
   #interfaceType PA

So, at the moment we have two different category names for power meters:  "PA" (Power Analyzer) and "Power".  It would be better if we only had one.  From my selfish perspective I vote for "PA" because I have been using that for years and have scripts using that.  Could it make sense to change this Owon power meter definition to match the others and use "PA"?

The official list:

    PS: Power supply
    ACPS: AC Power supply, usually a generator that can deliver 120/230VAC
    DMM: Digital multimeter
    BMM: Bench multimeter, this is guaranteed to have electronic control of ranges with setMode(). A BMM will usually also list a DMM type.
    ARB: Arbitrary waveform generator
    LCR: LCR meter
    Load: Electronic load
    Power: Power meter
    Osc: Oscilloscope
    Counter: A Counter or timer/counter device.
    SA: Spectrum Analyzer
    Relay: A controlled switch
    Input:  Digital input, detects on/off for one or more signals, either voltage or current
    Output: Digital output with voltage or current, output will typical be 0 or 3.3V/5V/12V
    AInput: Analog input voltage or current, will often be for sensors with 0-10V, 0-20mA, 4-20mA but can be other values.
    AOutput: Analog output voltage or current. will often be for sensors with 0-10V, 0-20mA, 4-20mA but can be other values.
    Calibrator: Precision output of voltage, current or resistance, similar to AOutput, but much more precise.
    Servo: Servo driver controlling a motor/servo, can be moved to different angles.
    Stepper: Driver controlling a stepper or similar, can be moved to different positions.
    Charger: Battery charger device
    Thermometer: Temperature measuring device
    Humidity: Humidity measurement, analog value that is 0-100%, this device will probably also have a Thermometer device.
    Lux: Lux meter for measuring light intensity.
    Readout: A small display that can echo a value from TestController (i.e. from any connected device).
    Virtual: All the test devices build into TC
    PC: PC based hardware, this is the sound input/output devices and nothing else.

And no definition uses PA

[Gertjan]

The official list:

    ...........
    ...........

There is no category for RF generators. (Signal Generators in British English)
RF generators are all similar in output capabilities. Which are vey different from ARB.

regards, Gertjan.

[HKJ]

There is no category for RF generators. (Signal Generators in British English)
RF generators are all similar in output capabilities. Which are vey different from ARB.

I usually add new categories when needed.
I.e. submit a RF generator and specify what category name you are using, I will change it if I do not like it.

In my supported list I do have a RF generator entry https://lygte-info.dk/project/TestControllerSupportedEquipment%20UK.html#RF_Generators, but nobody has asked my to add it to the category list.

My first idea would be something like RFGen.

[Gertjan]

My first idea would be something like RFGen.

RFGen sounds good to me.

I will ad #interfaceType RFGen to my Marconi 2018/2019 and Hameg HM8135 definitions.

regards, Gertjan.

[HKJ]

My first idea would be something like RFGen.

RFGen sounds good to me.

I will ad #interfaceType RFGen to my Marconi 2018/2019 and Hameg HM8135 definitions.

regards, Gertjan.

Ok, I have added RFGen to the list (Case will first be controlled correctly from next version).

[gby]

HKJ,

Ah, I guess you changed the category name in the driver files at some point.  In May 2023 when I submitted the drivers for
      Yokogawa WT3000 Power Analyzer.txt
      Yokogawa WT5000 Power Analyzer.txt
      Vitrek PA900.txt
      Hioki PW6001.txt
the definitions used "PA".  As does my local copies of these driver files.  Checking an old TestController V2.35 from June 2023 these drivers used "PA".

However, I see that in my current install directory for TestController that these drivers have all been changed by you to use "POWER".

Thanks for clarifying.  I will update my local copies and the scripts I have to "POWER".

gby

[HKJ]

HKJ,

Ah, I guess you changed the category name in the driver files at some point.  In May 2023 when I submitted the drivers for
      Yokogawa WT3000 Power Analyzer.txt
      Yokogawa WT5000 Power Analyzer.txt
      Vitrek PA900.txt
      Hioki PW6001.txt
the definitions used "PA".  As does my local copies of these driver files.  Checking an old TestController V2.35 from June 2023 these drivers used "PA".

However, I see that in my current install directory for TestController that these drivers have all been changed by you to use "POWER".

Thanks for clarifying.  I will update my local copies and the scripts I have to "POWER".

When I added the filter for category, I also changed some names.

[flash2b]

There is a typo in LC Tech ADC16F103R.txt on the #interfaceType line.

It should be AInput:11 (the A is missing).

[flash2b]

I have updated my def for the Analogic DP100 (and R&S labeled one)

Please add it to the next release of TC.

[ Attachment Invalid Or Does Not Exist ]

Part of TC v3.60

[HKJ]

There is a typo in LC Tech ADC16F103R.txt on the #interfaceType line.

It should be AInput:11 (the A is missing).

Fixed 11 & 15

[HKJ]

I have updated my def for the Analogic DP100 (and R&S labeled one)

Please add it to the next release of TC.

Updated, thanks.

[Gertjan]

RFGen sounds good to me.
I will ad #interfaceType RFGen to my Marconi 2018/2019 and Hameg HM8135 definitions.

Ok, I have added RFGen to the list (Case will first be controlled correctly from next version).

Hi HKJ,

I added #interfaceType RFGen to my RF generator definitions.

Now I felt obliged to also add a #interface for scripting.
Frequency and amplitude settings are most useful for use in TestContoller. (Generally to create sweeps)

As these  are the first RF generator definitions with #interface commands, I would like you to check if you are happy with them before submitting the definitions:

Code: [Select]

; ------------------  Programming Interface commands  -------------

; For RF generators, default amplitude unit is dBm

#interface setFrequency FREQ:CW (value)
#interface getFrequency FREQ:CW?
#interface readFrequency 0

#interface setAmplitude POW:LEV (value)
#interface getAmplitude POW:LEV?
#interface readAmplitude 1

; #interface setOn, set the device on or off, this must be with 1 for one and 0 for off
#interface setOn OUTP:STAT (value)
#interface getOn OUTP:STAT?

I used your documentation as guide, and looked at what is used for ARB.
Using the interface test popup, all commands test OK.

regards, Gertjan.

[HKJ]

Now I felt obliged to also add a #interface for scripting.
Frequency and amplitude settings are most useful for use in TestContoller. (Generally to create sweeps)

As these  are the first RF generator definitions with #interface commands, I would like you to check if you are happy with them before submitting the definitions:

I will adopt them, but I have a few question:
Is frequency in Hz, I hope it is, else please add a conversion.
Is output level in V or dB? and what unit?

[Gertjan]

As these  are the first RF generator definitions with #interface commands, I would like you to check if you are happy with them before submitting the definitions:

I will adopt them, but I have a few question:
Is frequency in Hz, I hope it is, else please add a conversion.
Is output level in V or dB? and what unit?

Yes, Frequency is in Hz.

Output level is in dBm.  It is the default standard unit for RF generators.
To avoid confusion, I added the comment above the #interface commands

However, Volts is also possible (mostly in mV or uV). Not all generators support it, and they do it in different ways.
And it would need new commands, like #interface getAmplitudeUnit
So for now I decided to avoid this can of worms.
regards, Gertjan.

[HKJ]

Yes, Frequency is in Hz.

Output level is in dBm.  It is the default standard unit for RF generators.
To avoid confusion, I added the comment above the #interface commands

However, Volts is also possible (mostly in mV or uV). Not all generators support it, and they do it in different ways.
And it would need new commands, like #interface getAmplitudeUnit
So for now I decided to avoid this can of worms.
regards, Gertjan.

I have added it here: https://lygte-info.dk/project/TestControllerInterfaceDefinitions%20UK.html

I added a getAmplitudeV as a secondary function, one way to do it is to do the conversion in TC.

[Gertjan]

Yes, Frequency is in Hz.

Output level is in dBm.  It is the default standard unit for RF generators.
To avoid confusion, I added the comment above the #interface commands

However, Volts is also possible (mostly in mV or uV). Not all generators support it, and they do it in different ways.
And it would need new commands, like #interface getAmplitudeUnit
So for now I decided to avoid this can of worms.
regards, Gertjan.

I have added it here: https://lygte-info.dk/project/TestControllerInterfaceDefinitions%20UK.html

Yes, that will work.
Please define Volts as "Volts into 50 ", as Volts with open output are also sometimes used.
RF generators live in a 50R world, so Volts into 50R is more common.

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

Code: [Select]

; for amplitude in dBm
#interface setAmplitude POW:UNIT DB;POW:LEV (value)
#interface getAmplitude POW:UNIT DB;POW:LEV?

; for amplitude in Volt into 50R
#interface setAmplitudeV POW:UNIT VL;POW:LEV (value)
#interface getAmplitudeV POW:UNIT VL;POW:LEV?

And we forget about readAmplitude? It is used in ARB definitions, but is gives the same result as getAmplitude anyway.

I added a getAmplitudeV as a secondary function, one way to do it is to do the conversion in TC.

Yes, that is what I do with my Marconi 2018 definition.
One can set the amplitude on the front panel in dBm or Volts. But it sends only dBm over the GPIB.
So i spent some time to create dBm to Volt and Volt to dBm calculations

regards, Gertjan.

[HKJ]

Please define Volts as "Volts into 50 ", as Volts with open output are also sometimes used.
RF generators live in a 50R world, so Volts into 50R is more common.

Added to document.

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, that is what I do with my Marconi 2018 definition.
One can set the amplitude on the front panel in dBm or Volts. But it sends only dBm over the GPIB.
So i spent some time to create dBm to Volt and Volt to dBm calculations

TC has a function for dB, or rather a couple: https://lygte-info.dk/project/TestControllerFunctions%20UK.html#Decibel_dB