Program that can log from many multimeters.

[HKJ]

Attached is a updated version of the Siglent SDL10xxXxx definition to fix the mAh vs Ah display and logging table, and incorrect label of the CR mode resistance setting.

Thanks, the update will be included in the next release.

[RichardM]

I don't suppose there is a chance of getting an old Fluke 8502a with AR488 working with this excellent software ?

Regards

Richard

[HKJ]

I don't suppose there is a chance of getting an old Fluke 8502a with AR488 working with this excellent software ?

There is, but you may have to do the work.
The program depends on user contributions for equipment support (I try to help as much as I can).

Definitions for different devices are made with ascii files and you can view all included definitions in the "devices" directory.

[PushUp]

Hi,
I recently purchased a Gossen Metrahit Energy with the USB IR interface cable and was excited to run across this software. Unfortunately, the cable doesn't seem to work with my MacBook running 10.15 Catalina or MacMini running Monterey. Normally, a device shows up in the /dev folder with the names cu.usbserial-xxxxx and tty.usbserial-xxxxx. I assume that is the address that the Test Controller program wants. At first I thought it was a FTDI driver problem but other FTDI devices I have do work. I did install the FTDI beta VCP driver 1.4.7 for MacOS 10.15 from their website but no luck.

Has anyone got the Metrahit USB X-Tra cable working with their Mac? I'm looking forward to trying out Test Controller. It looks pretty impressive. Thank you.

Edit:
I am beginning to think that the Gossen cable only works with the supplied driver in Windows. That would be a shame. I have asked Gossen about this and will let you know what they say.

Michael

You can save the money for the Gossen Metrawatt "Z216C USB X-TRA" and do 10 selfmade for one IR-USB-Interface by Gossen Metrawatt; you only need their software to read out the internal data logging, which is clearly the best of all handheld DMMs!

As I had the same issues with their "Z216C USB X-TRA" under linux, I am quite sure, that you will also have success in solving the problem:

"The USB-IR-thingie is probably old and anyone knows it, but just to sum it up for later use:"

https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg4015216/?PHPSESSID=e8ja7i0ragru6auspt39agp3m1#msg4015216

The selfmade - and only this - works without a problem from the beginning under linux:

https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg4096519/#msg4096519

Cheers! 

[Totoro]

Hey, thank you PushUp!
That self-made interface looks like my next project. I even already have a couple of FTDI to USB boards. Bummer that the Gossen cable seems to only work with their Windows driver. Haven't yet heard back from them BTW.
Thanks again!
Michael

[oz2cpu]

Tonghui TH2830 LRC meter was mentionened before in this thread,
did anyone solve a driver ?

is it connected to a pc by USB ? or by the DB9 Serial connector ?

what i want to achieve is to perform frequency versus the two measured values, it displays in any selected mode combination

[gby]

Hi HKJ,

Attached is a driver file supporting the GW Instek AC supply for you to include in the next release.  It is fully tested with ASR-2100 over LAN but supports ASR-2000 and ASR-3000 families.

Couple of issues supporting this supply:
1. It has a RANGE setting the is either base voltage/twice voltage and correspondingly base current/half current.  How would you suggest handling that in the Setup popup #cmdSetup entries for legal numeric range?  Right now this file is fixed at twice voltage range values for the #metadef #replaceText values.
2.  This device outputs either ac to simulate ac line, or dc with a symmetric negative to positive range, or the sum of both.  It also includes a rudimentary arbitrary function generator.  So, I don't think it really fits in the
   #interfaceType PS
dc power supply instrument category.  What do you think of using "ACPS" as the category/instrument type when/if I get around to adding #interface commands to this instrument driver file?

[oz2cpu]

test controller is mentioned in my latest video:
https://youtu.be/UpAvgAQBId4

here it is used to reveal temperature regulation loop, by creating a curve of power usage via a power supply

Super smart and easy to use, this test controller sw.

[HKJ]

Tonghui TH2830 LRC meter was mentionened before in this thread,
did anyone solve a driver ?

None is included or scheduled to be included at the current time.

what i want to achieve is to perform frequency versus the two measured values, it displays in any selected mode combination

This can be done with TestController, but because frequency is not defined as output parameter for a typical LCR meter, it can be a bit tricky to setup.

[oz2cpu]

>This can be done with TestController, but because frequency is not defined as output parameter for a typical LCR meter, it can be a bit tricky to setup.

oh.. did not know it was so special :-)
yes the TH2830 do support user input of test frequency, even to the last Hz
so this means if this can be used for a sweep, we can make very sexy curves with this instrument

[HKJ]

Attached is a driver file supporting the GW Instek AC supply for you to include in the next release.  It is fully tested with ASR-2100 over LAN but supports ASR-2000 and ASR-3000 families.

Thanks, it will be included.

1. It has a RANGE setting the is either base voltage/twice voltage and correspondingly base current/half current.  How would you suggest handling that in the Setup popup #cmdSetup entries for legal numeric range?  Right now this file is fixed at twice voltage range values for the #metadef #replaceText values.

The easiest way is to use the high values, but another solution is to double up on the settings and select with "#cmdSetup selector"

2.  This device outputs either ac to simulate ac line, or dc with a symmetric negative to positive range, or the sum of both.  It also includes a rudimentary arbitrary function generator.  So, I don't think it really fits in the
   #interfaceType PS
dc power supply instrument category.  What do you think of using "ACPS" as the category/instrument type when/if I get around to adding #interface commands to this instrument driver file?

You can use #interfaceType ACPS PS
But it might be best to only rate it as ACPS
It is probably best to use the set/get/read voltage to handle the AC values and add another set with voltageDC for the DC values.

[HKJ]

>This can be done with TestController, but because frequency is not defined as output parameter for a typical LCR meter, it can be a bit tricky to setup.

oh.. did not know it was so special :-)
yes the TH2830 do support user input of test frequency, even to the last Hz
so this means if this can be used for a sweep, we can make very sexy curves with this instrument

For now it can be done two ways:
1) Modify definition of LCR meter to include frequency
2) Use a generator that can sweep (External AVG or Soundcard output) and a script to sync the LCR meter to it.

[HKJ]

test controller is mentioned in my latest video:
https://youtu.be/UpAvgAQBId4

here it is used to reveal temperature regulation loop, by creating a curve of power usage via a power supply

Super smart and easy to use, this test controller sw.

I will add that video to my list of videos on the intro page.

[RichardM]

I am having difficulty getting TC working with my Fluke 8502a and AR488.

At a serial terminal (baud 115200) all I need to do is type the following with a linefeed to get the voltage returned
++addr 5
++auto 1
V?

and I get the voltage returned

-009.4110E-3

I have setup a GPIB controller in TC with baud 115200, port 7, Id A, and I add ++auto 1 into the Settings box.

I then try the following device file, my attempt anyway

----------------------------------------------
#idString FLUKE8502A
#name Fluke-8502a
#handle FLUKE8502A
#port GPIB
;#port comfixedbaud
#baudrate 115200N82
; using a AR488 so the DTR has to be set correctly:
#driver ascii
#eol \n

; A list of possible column name with unit and formatter (SI, Time, Int, D0..D6)
#value VoltageDC V D6 VDC

; How to poll for data, this is used for table and #values?
; a #askMode, #cmdMode and #prepareSample is used before this is string is used.
; This is a single line command
#askValues V?

;++read_tmo_ms is controlled with #readingDelay
#readingDelay 1

;++read eoi is controlled with #gpibReadEol
#gpibReadEol 10

; Switch meter to this mode during start, leave empty to avoid any switching
#initialMode

; Strings to configure device in different modes
; First parameter must match a #value (4 parameter) and second parameter must match what #askMode returns
; First parameter is also used in shortcut menu
;#cmdMode VDC V?
;#cmdMode VAC VA?

; Initial commands to meter when establishing connection
; syst:rwl locks keypad during remote operation
#initCmd

; Final command to meter before breaking connection
#finalCmd
---------------------------------------------------

and the debug window shows

Starting
;; jSerialComm version: 2.9.1
;; COM7: Set params: 115200
;; Start thread for: AR488 A:5 - Fluke-8502a
;; Start thread for: COM4
;; Start thread for: COM9
;; COM7: Tx: <++default.> 2B 2B 64 65 66 61 75 6C 74 0A
;; COM7: Tx: <++auto 1.> 2B 2B 61 75 74 6F 20 31 0A
;; COM9: Set params: 9600
;; COM4: Set params: 9600
;; Found Fluke-8502a on AR488 A:5
;; COM4: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM9: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM4: Rx: timeout
;; COM9: Rx: timeout
;; COM4: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM9: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM4: Rx: timeout
;; COM9: Rx: timeout
;; Stopping thread for: COM9
;; Stopping thread for: COM4
;; COM4: Close
;; COM9: Close


If I then try to enter a command line input like V? I get

;; FLUKE8502A: Tx <V?>
;; FLUKE8502A: Rx Timeout

Any help appreciated. I am just trying to get a minimal device setup file going at the moment or even get the device responding to the command line. I am not sure I am even entering the commands into the command line correctly. I would benefit from a similar GPIB device that accepts simple commands like V?, I? etc

Cheers Richard

[HKJ]

I am having difficulty getting TC working with my Fluke 8502a and AR488

You are not supposed to use ++auto, TC will use the ++read command
When using a ascii device there is no free answer, you have to use txrx? or similar commands to get an answer.

And remove the checkmark in "Scan serial ports", this will remove the scan of all the serial ports from the log (This function is only useful if you have a couple of serial devices that responds to the *idn? command, I typically uses it with my homemade Arduino devices).

You have to load the 8502 into the device list and specify it uses port A:5

The "#port GPIB" do not use a baudrate setting, but you can use: "#port GPIB com" and then it will be possible to select serial port.

A fairly similar device would probably be the "HP3478A.txt"

[RichardM]

I am having difficulty getting TC working with my Fluke 8502a and AR488

You are not supposed to use ++auto, TC will use the ++read command
When using a ascii device there is no free answer, you have to use txrx? or similar commands to get an answer.

And remove the checkmark in "Scan serial ports", this will remove the scan of all the serial ports from the log (This function is only useful if you have a couple of serial devices that responds to the *idn? command, I typically uses it with my homemade Arduino devices).

You have to load the 8502 into the device list and specify it uses port A:5

The "#port GPIB" do not use a baudrate setting, but you can use: "#port GPIB com" and then it will be possible to select serial port.

A fairly similar device would probably be the "HP3478A.txt"

Thanks but unfortunately none of those suggestions seem to make a difference. I only used ++auto 1 as one other user indicated that is what he needed to to to get his device working. Seem to always get no data timeout?

Regards

Richard

[HKJ]

Thanks but unfortunately none of those suggestions seem to make a difference. I only used ++auto 1 as one other user indicated that is what he needed to to to get his device working. Seem to always get no data timeout?

In debug mode using:

txrx? V?

on the command line (You can test commands from the command line), ought to show both the command going out and the "++read" command in the log.

[rachdatu]

Did you try the commands for my Philips counter?
It works for me but your device may not have the same commands.
For example ++auto 1 is a command described in my Philips Manual. I looked quickly at yours and don't see that command.

Don't try *IDN? It's probably not  going to work. This device is too old and at that time, the GPIB standard did not exist!

Anyway, follow HKJ instructions. He knows what he is talking about 

[RichardM]

Thank for the replies.

I went and made a cup of tea and came back with a clear head. I trimmed the device file to a minimum and have it working in a basic sense. Now I just need to understand all the rest of the commands etc. Iassume I define all the device commands using #scpiCmd ? If I uncomment the #initCmd below I get the timeout error ?

#idString Fluke,Fluke 8502a
#name Fluke 8502a
#handle myFluke8502a
#driver Ascii
#port GPIB com
#eol \n\r

; There must be a line for each of the original device commands that will be used, converting it to a similar SCPI command
;#scpiCmd init tx command to init
#scpiCmd values? txrx? ?

; A list of possible column name with unit and formatter (SI, Time, Int, D0..D6)
#value Voltage V SI
 
; This is a single line command
#askValues txrx? ?

;Accept this delay when reading values (seconds)
#readingDelay 5

; Prepare the meter to response to #askValues
;#prepareSample

; Initial commands to meter when establishing connection
;#initCmd tx V?

Thanks for developing this software

[HKJ]

#scpiCmd values? txrx? ?

#askValues txrx? ?

This is not the way to do it, when you have defined a command with #scpiCmd you use it for the other definitions:

#askValues values?

; Initial commands to meter when establishing connection
;#initCmd tx V?

I cannot see this command can give a timeout, because "tx" do not expect any answer. But it may affect the next command because you will get a answer to the V? and that answer may affect the next command.

It is very important to handle answer/no answer correctly. Any command with a ? is supposed to give an answer, this is valid for defined #scpiCmd and for the txrx type commands, but not for the command listed after the txrx command.

I.e.
#scpiCmd mycmd? txrx? xxxxx  is valid if xxxxx returns an answer
#scpiCmd mycmd txrx? xxxxx  is invalid
#scpiCmd mycmd? txrx xxxxx  is invalid and will give a timeout
#scpiCmd mycmd txrx xxxxx  is valid if xxxxx returns an answer that must be ignored
#scpiCmd mycmd tx xxxxx  is valid if xxxxx do not return an answer

[HKJ]

>This can be done with TestController, but because frequency is not defined as output parameter for a typical LCR meter, it can be a bit tricky to setup.

oh.. did not know it was so special :-)
yes the TH2830 do support user input of test frequency, even to the last Hz
so this means if this can be used for a sweep, we can make very sexy curves with this instrument

For now it can be done two ways:
1) Modify definition of LCR meter to include frequency
2) Use a generator that can sweep (External AVG or Soundcard output) and a script to sync the LCR meter to it.

I did not like my answer here and have been modifying TestController. From next version the ParamSweeper popup can include the parameters it sweeps by using a check mark. This makes it easy to do the above curves/tables.

[oz2cpu]

wow thanks a lot :-) now i just need to get that darn serial connection working
still no use full hints from china support, not even pinout, signals that needs to be this or that,,
it is all a dark secret

[SpottedDick]

Recently discovered Test Controller (name needs changed so it's easier to Google!) and love it.
Really made my Atorch capacity tester actually useful.

I unfortunately discovered that the external temperature sensor data is not sent out by the device, so there's no way to log it on the computer along with all the other data. I use it for battery temperature monitoring so I'd love to be able to get this into Test Controller along with the rest of the logs.

Actual question: Is there a cheap temperature sensor that works over USB that Test controller can read so I can add it to the logs with the rest of the data from the Atorch?

Thanks!

[HKJ]

Actual question: Is there a cheap temperature sensor that works over USB that Test controller can read so I can all it to the logs?

You can use many DMM's to measure temperature, but there you will usually have issues with batteries (i.e. they need to be replaced often).

A better solution is a DIY temperature sensor, it is easy and cheap:
https://lygte-info.dk/project/TestControllerArduino2%20UK.html#DS1820_temperature_device

[SpottedDick]

Oh you actually have a solution on your site, and I have all those parts here beside me, excellent