Program that can log from many multimeters.

[gby]

HKJ thanks for the update.  I can confirm:

    Fixed: #eol can be used on Ascii devices.

now works with the ascii driver.  The device I am trying to talk to just never responded to communications before and is now replying with the #eol \r\n setting and the ascii driver.

Now I just need to work through all the details before sharing a device setup file...except now is time for my day job.

Thanks for all your work.

[enut11]

Hi @HKJ, I have a HP 34401A connected to my PC via CH340 RS232 to USB adapter. I tried to connect to TestController with no success.
I have used this setup with Agilent DMM Utility so I know it works.
Any advice?
enut11

[HKJ]

Hi @HKJ, I have a HP 34401A connected to my PC via CH340 RS232 to USB adapter. I tried to connect to TestController with no success.
I have used this setup with Agilent DMM Utility so I know it works.
Any advice?

The first thing to try is starting in debug mode, you can post the output here or send me a mail.

[enut11]

Not sure what you mean by debug mode.
When I enter the 34401A meter info in the Load Devices screen I see this:

[enut11]

then, when I click Reconnect I hear a beep from the 34401A and 'Rmt' and 'Error' appear on the 34401A display but I do not see my meter in the Commands screen.

[HKJ]

Not sure what you mean by debug mode.

There is a "testControllerDebug.bat" file that can be used to start testController.
If you are running on a non-windows system you need to start it with a command line something like this: "java -jar TestController.jar debug"

Then it will list all steps it do to connect.

When using debug mode it is best only to enable the device being debugged, to keep the debug output as simple as possible.


Can it be that the baudrate setting is wrong?

[enut11]

Thanks, I will try now. Baud rate is always 9600. Also looking at the AgilentHP34401A.txt file

[enut11]

is this what you need?

[HKJ]

is this what you need?

Yes, you only need to copy the text, not the full picture.

It looks like baudrate or parity/bits. You can specify something like "9600O71" instead of just 9600, if that is required.
Note: I do not have a 34401A meter, the definition was made by "maukka".

[enut11]

This is what my PC reports
How do I get in touch with "maukka"

[HKJ]

This is what my PC reports
How do I get in touch with "maukka"

If that is the correct setting, just try using it in the baudrate field on the "load devices" page:
9600E72

I found the manual for the 34401A, the baudrate and parity is a setting in the meter, factory default is 9600E72

maukka is a name here on EEVBlog.

[enut11]

No, it did not work for me.

[maukka]

Here's how my settings looks like.



Please check that the connection is working with a terminal program such as Coolterm.

[HKJ]

It may be a good idea to check the actual settings in the 34401A.

[maukka]

My 34401A settings under I/O menu:

Interface: RS-232
Baud rate: 9600 baud
Parity: none 8 bits
Language: SCPI

[enut11]

Hi @maukka
Thanks for responding.

I can talk to my 34401A using Keysight connection expert  and log using Agilent dmm utility so the r3232/usb interface works.

When I start TestController I get an 'ERROR' on the 34401A.

My Com port setting is the same on my PC and TestController but I note that you use different com port in TestController (Com8) compared to your PC (Com3).

[HKJ]

I can talk to my 34401A using Keysight connection expert  and log using Agilent dmm utility so the r3232/usb interface works.

Are you sure the Agilent tool uses the PC parameters and not its own?
The best way is to check the baud settings directly on the meter.

[maukka]

My Com port setting is the same on my PC and TestController but I note that you use different com port in TestController (Com8) compared to your PC (Com3).

Looks like the program finds the meter just fine automatically even when the com port settings are wrong.

[HKJ]

Looks like the program finds the meter just fine automatically even when the com port settings are wrong.

Only happens when you have checked "Scan serial ports" and you devices answers a *idn? on 9600 baud.

[enut11]

I can talk to my 34401A using Keysight connection expert  and log using Agilent dmm utility so the r3232/usb interface works.

Are you sure the Agilent tool uses the PC parameters and not its own?
The best way is to check the baud settings directly on the meter.

@HKJ, yes my 34401A reports 9600 baud when queried through its front panel menu.

[enut11]

Given that @maukka can use his 34401A with TestController program and I cannot, there must be a difference in the way my CH340 RS232/USB interface works compared to the Keyspan USB Serial interface.

[HKJ]

@HKJ, yes my 34401A reports 9600 baud when queried through its front panel menu.

What about parity and bits?

[HKJ]

Given that @maukka can use his 34401A with TestController program and I cannot, there must be a difference in the way my CH340 RS232/USB interface works compared to the Keyspan USB Serial interface.

That may be, but TestController can probably handle it. The only other options I can think of is handshake signals and you can also specify them in the baud rate setting.
At the end of the baud rate string you can add:
D to force DTR high or d to force DTR low.
R to force RTS high or r to force RTS low.

But as long as you receive data from the meter it is not the handshake signals.

[enut11]

OK, I can now connect my 34401A to TestController

I copied the Agilent file and made some changes to the TXT file. I think a mistake on my part in not correctly specifying the #idstring line for the meter.

Currently logging and it seems to work. I will test it further.

Meanwhile, how do I re-scale the Y-axis on the Chart window?

BTW, fantastic program @HKJ. Thank you for making it available to Forum members. Much appreciated  

[enut11]

@HKJ, yes my 34401A reports 9600 baud when queried through its front panel menu.

What about parity and bits?

I have set my meter and PC to 9600 Baud, 8 Data, 1 Stop, No Parity

BTW, I found how to re-scale the chart thanks.