Program that can log from many multimeters.

[Baruke]

Thank you for your response. Trying to figure this out has taken way too much of my time.

Do you know of a "not too expensive" multimeter or load tester (400w) that works with Mac OS and LoadTester without hassle?

[HKJ]

Do you know of a "not too expensive" multimeter or load tester (400w) that works with Mac OS and LoadTester without hassle?

Look for serial or network connections, they are the same on all platforms.
This list is a good starting point: https://lygte-info.dk/project/TestControllerSupportedEquipment%20UK.html
Just be aware that I have not tested everything on the list, some of it is added because it is part of a series that works the same way and some of it is added because it is supposed to be a copy of a working device.

I have tested the KEL103 load and Brymen multimeters (Note HID interface is not supported on Mac).

[dmenezes]

Thanks

I have been thinking about this a couple of times, but I sort of like that TC do not ask about the save data all the time.

I agree. I wouldn't want extra prompts. However, if you added it as an optional thing, that would be cool. People could then choose if they want those prompts or not.

I'm with @KungFuJosh in this regard, an option to control that behavior would be great.

And just to complement @HKJ's response above: even without the option suggested by @KungFuJosh, TC would not ask it "all the time", it would ask only when the data in the buffer hasn't been saved (and therefore would be lost if the operation proceeded without warning the user first).

[dmenezes]

Thank you @HKJ for your prompt response.

If you really want it you can assign #CLEARTABLE to a F key.
https://lygte-info.dk/project/TestControllerScriptCommands%20UK.html##CLEARTABLE

Thank you for that. i did not know about the `#CLEARTABLE` command, and also didn't know commands could be assigned to keys. This will be really helpful in my use case (I do need to clear the buffer without stopping/starting the log or loading another file).

I have been thinking about this a couple of times, but I sort of like that TC do not ask about the save data all the time.
If you log important data, you can log directly to disk, that way you will not loose data, even if the computer crashes.

Thanks for your response. I avoid logging directly to disk because this machine has plenty of memory, but its disks are not that fast (old spinning rust), but will try logging to disk and see how it works. Will the chart/table windows still work the same, or to be able to see the data being captured in them, would I have to stop capturing and then load the data from disk?

[HKJ]

Thank you for that. i did not know about the `#CLEARTABLE` command, and also didn't know commands could be assigned to keys. This will be really helpful in my use case (I do need to clear the buffer without stopping/starting the log or loading another file).

You can assign a script to 10 of the 12 F keys:
Type the script in the log window
Mark it with the mouse
Right click and select the F key

These F keys only works while on the Commands page.

Thanks for your response. I avoid logging directly to disk because this machine has plenty of memory, but its disks are not that fast (old spinning rust), but will try logging to disk and see how it works. Will the chart/table windows still work the same, or to be able to see the data being captured in them, would I have to stop capturing and then load the data from disk?

TC uses multi threading to handle logging to the disk in background, i.e. even slow disk will usually not interfere with the sampling.
The chart nearly works the same way, but if you log for a log time a data reduction algorithm will kick in and reduce the table to every 3 data point (Disk log will contain all data points), this data reduction can be applied multiple times. The data reduction is done to keep memory consumption limited, as far as I remember the sample count is kept between 10k and 30k. I.e. the first time it kicks in is at 30k samples (And just to be clear: This only applies when logging direct to disk, not when logging to memory only).

[jmurray]

I made some minor corrections to the Agilent/HP 34401A definition file. The math function for interpreting mode had been placed in the wrong section and there were underscores missing from string values, so there were instances where upon connecting to the 34401A, TC could not determine the existing mode setting of the 34401A.

[bdunham7]

I made some minor corrections to the Agilent/HP 34401A definition file. The math function for interpreting mode had been placed in the wrong section and there were underscores missing from string values, so there were instances where upon connecting to the 34401A, TC could not determine the existing mode setting of the 34401A.

Is that why I get an error when I connected to the 34401A when it was in anything other than the default configuration?  For example I had it set to power up with slow 6-digit and high impedance but had to take that out to not get an error  with TC.  If you've fixed that, then thank you!

[jmurray]

I made some minor corrections to the Agilent/HP 34401A definition file. The math function for interpreting mode had been placed in the wrong section and there were underscores missing from string values, so there were instances where upon connecting to the 34401A, TC could not determine the existing mode setting of the 34401A.

Is that why I get an error when I connected to the 34401A when it was in anything other than the default configuration?  For example I had it set to power up with slow 6-digit and high impedance but had to take that out to not get an error  with TC.  If you've fixed that, then thank you!

I may have spoken too soon. Testing again and now it's back to inconsistent, even after making a few more corrections that I missed.
Will have to spend some more time on it.

[KungFuJosh]

I dunno if this is a bug, or a glitch in the matrix, or whatever... but I added a KS 34465A to my bench today, and things got a little weird.

Previously, all my meters were setup as Type=Socket in the Load devices tab. After adding the Keysight, the Siglent no longer was discovered on start, so I switched it to LXI, and it started working. Leaving the Keysight and Keithley both as Socket, gave the attached glitches.

The grid panel showing two of the same readouts only has one readout loaded.

Anyway, I switched the Keysight to LXI, and the glitches went away. Now the Keysight and Siglent are both LXI, and the Keithley seems to like being set to Socket better. 🤷

Thanks,
Josh

ETA: Might just be a display driver glitch. I updated my drivers; I'll update if the issue reoccurs.

[KungFuJosh]

Is it possible to save the state of TC and run that state again on TC startup?

For example, I want 3 or 4 meters with parameters set (including Current Values - Format), and the grid panel including selected channels and custom colors for those channels. Running those defaults would get me the attached screenshot setup.

[The Soulman]

Attached is the working a tested definition for the Voltcraft VC7200BT bench multimeter.
It is a modified version of the Owon XDM3051 definition, same as the Owon meter the dual measurement functions are not supported.

In this definition the port number is set to 5025, set dmm accordingly.

[KungFuJosh]

One more feature request:

Ability to have the Grid panel "always on top" so it doesn't get lost behind other windows.

Thanks,
Josh

[HKJ]

I dunno if this is a bug, or a glitch in the matrix, or whatever... but I added a KS 34465A to my bench today, and things got a little weird.

I have no idea about this, I mostly use socket connections to my devices.

[HKJ]

Is it possible to save the state of TC and run that state again on TC startup?

For example, I want 3 or 4 meters with parameters set (including Current Values - Format), and the grid panel including selected channels and custom colors for those channels. Running those defaults would get me the attached screenshot setup.

Sort of.
Right click in log window, select "Generate scripts, Layouts, In log window", then save the generated script in:
...\Documents\TestController\Settings\autorun.txt

I prefer to save layouts as menus, then I can select the one I want each time.

[HKJ]

Attached is the working a tested definition for the Voltcraft VC7200BT bench multimeter.
It is a modified version of the Owon XDM3051 definition, same as the Owon meter the dual measurement functions are not supported.

In this definition the port number is set to 5025, set dmm accordingly.

Thanks, I have added a #notes to the file about the port setting.

[HKJ]

One more feature request:

Ability to have the Grid panel "always on top" so it doesn't get lost behind other windows.

With you layout example I can see why you might want it, I will think about it.
I have made Grid panel a full window and you can select it in the bar at the bottom, i.e. it is always fairly easy to get on top.

[KungFuJosh]

One more feature request:

Ability to have the Grid panel "always on top" so it doesn't get lost behind other windows.

With you layout example I can see why you might want it, I will think about it.
I have made Grid panel a full window and you can select it in the bar at the bottom, i.e. it is always fairly easy to get on top.

A toggle for that option shouldn't be too bad. This is what google generated 😉:

Code: [Select]

import javax.swing.JFrame;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import javax.swing.JButton;

public class AlwaysOnTopToggle {

    private static boolean alwaysOnTop = false;

    public static void main(String[] args) {
        JFrame frame = new JFrame("Always On Top Toggle Example");
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setSize(300, 200);

        JButton toggleButton = new JButton("Toggle Always On Top");
        toggleButton.addActionListener(new ActionListener() {
            @Override
            public void actionPerformed(ActionEvent e) {
                alwaysOnTop = !alwaysOnTop;
                frame.setAlwaysOnTop(alwaysOnTop);
                if (alwaysOnTop) {
                    toggleButton.setText("Disable Always On Top");
                } else {
                    toggleButton.setText("Enable Always On Top");
                }
            }
        });

        frame.getContentPane().add(toggleButton);
        frame.setVisible(true);
    }
}
I assume/hope something like that should work?

I like to keep the grid panel on top, but I also reset my chart a bunch of times. So, I have to keep finding and clicking the grid panel each time.

Thanks,
Josh

[HKJ]

I like to keep the grid panel on top, but I also reset my chart a bunch of times. So, I have to keep finding and clicking the grid panel each time.

Some windows in TC is on top and it can be selected for other.
Coding is not a problem, adding a menu point in a logical place is.

[KungFuJosh]

I like to keep the grid panel on top, but I also reset my chart a bunch of times. So, I have to keep finding and clicking the grid panel each time.

Some windows in TC is on top and it can be selected for other.
Coding is not a problem, adding a menu point in a logical place is.

Easy! The Grid panel menu is all right-clicked, so add always on top to the right-click menu. I would add it at the bottom of the menu (top level, not sub menu).

[HKJ]

Easy! The Grid panel menu is all right-clicked, so add always on top to the right-click menu. I would add it at the bottom of the menu (top level, not sub menu).

Not really, the Grid panel has two menus: "Grid layout" and "Add panel"
It could be used on the Single panel, because it do not have its own menu.

[KungFuJosh]

Easy! The Grid panel menu is all right-clicked, so add always on top to the right-click menu. I would add it at the bottom of the menu (top level, not sub menu).

Not really, the Grid panel has two menus: "Grid layout" and "Add panel"
It could be used on the Single panel, because it do not have its own menu.

It wouldn't make sense to add it to the Grid Layout. I'd add it directly below system on the "Add panel" top level menu. From a UI perspective, it's just the Grid panel's general menu, since we don't see (what I assume is) the menu name in the code.

[HKJ]

It wouldn't make sense to add it to the Grid Layout. I'd add it directly below system on the "Add panel" top level menu. From a UI perspective, it's just the Grid panel's general menu, since we don't see (what I assume is) the menu name in the code.

Ok, Ok, try this:
http://lygte-info.dk/pic/Projects/TestController/TestController.jar

[KungFuJosh]

Ok, Ok, try this:
http://lygte-info.dk/pic/Projects/TestController/TestController.jar

THANK YOU!

Thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you

[KungFuJosh]

Right click in log window, select "Generate scripts, Layouts, In log window", then save the generated script in:
...\Documents\TestController\Settings\autorun.txt

I prefer to save layouts as menus, then I can select the one I want each time.

I just tried it out as a menu, and I like it. Thanks!

I have no idea about this, I mostly use socket connections to my devices.

When you have some time, could you please test with 3 or 4 devices connected via LXI? TC gets laggy when they're all LXI, and I don't know if that's a TC thing, or something about my system setup that slows it down.

I don't have the option of using socket anymore. I've tried different ways, but if the Siglent and Keysight are both powered on, they both need to be LXI for things to work right. I have all my meters connected as LXI now, and that seems more stable than 2 or 3 as LXI and the rest as Socket.

Thanks,
Josh

[dmenezes]

Hi,

Per the subject: left TC running for a few hours, logging data from my S8000 battery charger. When I came back to it a few hours later, TC was initially responsive, and I managed to send a couple of commands to the charger and get its responses, but when I clicked on the "Chart" tab, it suddenly stopped responding and all I see is a blank window:

The OS seems OK, memory is not an issue (over 1.3GB of RAM free and no swap activity -- so the system is not thrashing or anything) and everything else but TC seems to be working fine. CPU is fine too, utilization is under 10%.

I've been using TC extensively in this same setup (Linux Debian Bookworm with openjdk-17-jre-headless), and this is the first time it shows anything like this.

I would really like not to lose the data I was capturing. Any hints? 

EDIT: forgot to mention, but this is with TestController v.2.53 downloaded exactly 26 days ago from https://lygte-info.dk/pic/Projects/TestController/TestController.zip