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

[flash2b]

Can #ChartCurves reference a math column? I create math entries from an Other menu with #Math and they show up correctly in the Math window with data, but listing the name in #ChartCurves does not select them. Clicking the same curve by hand in the chart works.

Example:
#Math AVG_CH1_30 °C Average 30 XEXX0600.TempCH1 then #ChartCurves AVG_CH1_30

If math columns need a different name form there, what is it? If they are not supported, could they be?

[HKJ]

Can #ChartCurves reference a math column? I create math entries from an Other menu with #Math and they show up correctly in the Math window with data, but listing the name in #ChartCurves does not select them. Clicking the same curve by hand in the chart works.

Example:
#Math AVG_CH1_30 °C Average 30 XEXX0600.TempCH1 then #ChartCurves AVG_CH1_30

If math columns need a different name form there, what is it? If they are not supported, could they be?

They are supported, battery test uses them (It do some stuff by running a script).
But there can be timing involved, they can first be selected when they exist in the table. Do you have a #waitui after changing the math columns?

[flash2b]

I had a \x23delay 5

but that doesn't work as planned. I see the curves disable but the AVG curve not enable

[flash2b]

No luck. What I have tried in the Other menu of a definition:

  \x23Math AVG_CH1_30 °C Average 30 XEXX0600.TempCH1     (x6, one per channel)
  \x23waitui
  \x23ChartCurves AVG_CH1_30 AVG_CH2_30 ... AVG_CH6_30

The math entries are created, they show in the Math window with the checkbox on and they have data. #ChartCurves does not select them. Raw device columns in the same #ChartCurves line do get selected, so the command itself is working.

Also tried: #delay 5 instead of #waitui, both together, and runScript instead of runScriptAsync. Same result each time. Clicking the same curve by hand in the chart works immediately.

Does the battery test run its script from the ScriptLibrary rather than from an Other menu, and would that make a difference? Or is there something else that has to happen between creating a math entry and selecting it as a curve?

[HKJ]

I had a \x23delay 5

but that doesn't work as planned. I see the curves disable but the AVG curve not enable

You know you can first select curve when first entry is logged?

#log 1
#haslogged

Will start logging and wait for first entry.


I checked my code:

Code: [Select]

sb.append("#chartcurves " + getVoltmeterScale(charge) + " " + getCurrentScale(charge)+ " Math.Capacity Math.Energy\n");
CommandProcessor.runScript(sb.toString());

Nothing special in that, but I do first run it about 2 second after starting logging.

[flash2b]

My reference need to start with: Math.

Two findings I got: math columns are named bare in #Math but addressed as Math.<name> everywhere else, and #waitui after creating them.

This is not in the documentation.

I got it working after trying numerous times.

[HKJ]

My reference need to start with: Math.

Two findings I got: math columns are named bare in #Math but addressed as Math.<name> everywhere else, and #waitui after creating them.

This is not in the documentation.

I got it working after trying numerous times.

In TC Math. is used everywhere a math channel is referenced, but I may need to update the documentation for the Math page to make it clear. It would probably also be a good idea to mention #waitui in the #math commands.

[Cyclotron]

Another PSU family to the list:
This driver covers the E3640A, E3641A, E3642A, E3643A, E3644A, and the E3645A. 
This was created and validated against an E3641A

https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/HP_Agilent_E364xA

[HKJ]

Another PSU family to the list:
This driver covers the E3640A, E3641A, E3642A, E3643A, E3644A, and the E3645A. 
This was created and validated against an E3641A

https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/HP_Agilent_E364xA

I have added them, thanks.

[PushUp]

We have a forum member "Maria", who bought the new "Rohde & Schwarz UDS600".

As this is the successor of the "Rohde & Schwarz HMC8012", maybe HKJ is able to give a hint to him or her?

Is it better to add the new ID to the old script or is it better to make a new one for the UDS500 and UDS600 series, as there are probably some new features like:

UDS 500-G/UDS 500:    200.000 counts, 5½ digits
UDS 600-G/UDS 600: 2.000.000 counts, 6½ digits

Unfortunately, I am not that good at doing new definitions, so that it would be nice to help him or her more or better than I could:

https://www.eevblog.com/forum/chat/what-did-you-buy-today-post-your-latest-purchase!/msg6346238/

[KungFuJosh]

We have a forum member "Maria", who bought the new "Rohde & Schwarz UDS600".

As this is the successor of the "Rohde & Schwarz HMC8012", maybe HKJ is able to give a hint to him or her?

Is it better to add the new ID to the old script or is it better to make a new one for the UDS500 and UDS600 series, as there are probably some new features like:

UDS 500-G/UDS 500:    200.000 counts, 5½ digits
UDS 600-G/UDS 600: 2.000.000 counts, 6½ digits

Unfortunately, I am not that good at doing new definitions, so that it would be nice to help him or her more or better than I could:

https://www.eevblog.com/forum/chat/what-did-you-buy-today-post-your-latest-purchase!/msg6346238/#msg6346238

Resolution doesn't matter. That can be adjusted for each meta variant. Assuming they use all the same language/features, then adding it should be simple.

[HKJ]

We have a forum member "Maria", who bought the new "Rohde & Schwarz UDS600".

As this is the successor of the "Rohde & Schwarz HMC8012", maybe HKJ is able to give a hint to him or her?

Is it better to add the new ID to the old script or is it better to make a new one for the UDS500 and UDS600 series, as there are probably some new features like:

UDS 500-G/UDS 500:    200.000 counts, 5½ digits
UDS 600-G/UDS 600: 2.000.000 counts, 6½ digits

To decide if a new definition file is needed, compare the SCPI commands and how they work, if that is basically the same, add it to the old definition.
If not, make a new definition, maybe copy the old one as a starting point.

For TC a new file is not a big deal, many definitions in a file is to make it easier to make and maintain a couple of very similar devices.

[KungFuJosh]

A new file shouldn't be necessary. R&S claims compatibility between the models, and the definition uses si without a digit count. All they need to add to the HMC8012 is:

Code: [Select]

#metadef
#idString Rohde&Schwarz,UDS600,
#name     R&S UDS600
#handle   UDS600
...and it should work.

[Cyclotron]

HP Electronic Load 6060B created and validated.

More info and screen shots here:
https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/HP_Agilent_6060B

[HKJ]

HP Electronic Load 6060B created and validated.

More info and screen shots here:
https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/HP_Agilent_6060B

Added, thanks.

[KungFuJosh]

Here's a maintenance release for the Batronix Magnova.

I'm debating adding FFT or Bode plot. Would anybody use those remotely?

Thanks,
Josh

[HKJ]

Here's a maintenance release for the Batronix Magnova.

I'm debating adding FFT or Bode plot. Would anybody use those remotely?

Added, thanks.

[flash2b]

I have added support for the Yokogawa 7555 (both versions) in  Type 0 : 7552 compatibility mode

Furthermore I have done some extending functions of the meter and bug fixing of my Yokogawa 755x and 756x definition, so changelog is long:

Added: Math tab with dB Reference (dBV, dBµV, dBmV, 600, 75 and 50 Ohm), dB Multiplier for KC, Logic Family (TTL/HCT, LVTTL 3V3, CMOS, RS232) with CMOS Vdd, and Scaling Mode (Nominal, Deviation, Shunt) with Nominal Value;
Added: Computation tab holding the constants, Math status and function, split off the Math tab;
Added: IC Card status, Definition version and IC Card support level on the System tab;
Added: Support for the Yokogawa 7555 (RS232/GPIB) in Type 0 : 7552 compatibility mode
Fixed: Reset all Constant values did not reset KA, the scpiCmd was missing none so the first :setvar: was consumed as the action;
Fixed: dataHeadVal decoding read only 3 positions;
Fixed: daOutputVal not assigned the decoded value;
Fixed: IC Card and Front/Rear detection now ignore status bit 4, which is CARD BUSY on the 7563;
Fixed: OSLINESVAL set to 12 for 7563 and addional temperature constants are skipped/ignored, Decibel functions gated due to Not Supported
Modified: renamed to Yokogawa 755x 756x.txt to cover the whole series;
Modified: unit suffix for Ohm_2W, Ohm_4W, freqACV and freqACA on radio range buttons;
Modified: IC Card status now reads Inserted / Not Inserted;
Modified: constMax renamed CONSTMAXVAL and the OS line count moved to OSLINESVAL;
Modified: Constant KD no longer forced into the meter's native format, which the dBµV and dBmV references need;

The new math screen has functions that the meter does not offer, but can be supported in a user friendly manner. TestController can be use to extend functionality of a meter and I use this method often not stopping of just making functions available 1:1.


The 7563 should now also work better since I got the details from a Japanese manual

HKJ
- please delete Yokogawa 7551-7552.txt from your release
- please add Yokogawa 755x 756x.txt to the next release

[ Specified attachment is not available ]

Part of TC

[flash2b]

Notepad++ syntax highlighting for TestController definition files - v1.04

Bugfix (folding) and some missing commands added.

 TestController-Notepad++ UDL pack.zip (8.61 kB - downloaded 19 times.)

[HKJ]

I have added support for the Yokogawa 7555 (both versions) in  Type 0 : 7552 compatibility mode

Furthermore I have done some extending functions of the meter and bug fixing of my Yokogawa 755x and 756x definition, so changelog is long:

Updated and old file deleted, thanks.

[Cyclotron]

A driver for the Guildline 6560 resistance standard/calibrator.

  https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/Guildline_6560

[KungFuJosh]

Here's an updated driver for the Siglent SDM4000A series. Autozero stuff works now.

Thanks,
Josh

[HKJ]

A driver for the Guildline 6560 resistance standard/calibrator.

Added, thanks.
Interesting device and a advanced box for only 19 high precision resistors.

[HKJ]

Here's an updated driver for the Siglent SDM4000A series. Autozero stuff works now.

Updated, thanks.

[flash2b]

Other menu — write a variable to a file and read it back

Is there a way from the Other menu to write the content of a script variable to a text file, and to read that file back into a variable?