Program that can log from many multimeters.

[Dwaine]

I just tried this program to watch a charging of a car battery.  Great application it worked well.  I was using a Keysight U1272A to log the voltage during the charge.  Remote x11 session from my linux server to my Windows 10 laptop. 

Quick question.  How do you set the baud rate from 9600 to 19200?  I tried to change the config file but it always tries 9600 baud.   Also, the only option for measurement is DC Voltage.  How do you pick other measurements?

[HKJ]

Quick question.  How do you set the baud rate from 9600 to 19200?  I tried to change the config file but it always tries 9600 baud.   Also, the only option for measurement is DC Voltage.  How do you pick other measurements?

Baudrate is part of the driver definition and I forgot there is a baudrate setting on the meter.
To select range you have to turn the range switch on the meter, then use the mode button in TestController and press "Check mode" on the popup.

[HKJ]

V0.64 is up

It is with a working selector control and I have modified the Keysight344xx to use it:



Now the setup window will track the selected mode and it updates much faster, because only the visible controls are updated.

I also fixed some bugs with current input selection.
The temperature selection only has thermocouplers and are missing RTD, I did not fix that.

The selector is the last control in the file, if it is removed it will revert to the old layout.

I hope there are baudrate selection on the Keysight handheld now (I did not test).

[MikeLud]

HKJ,

I made some changes to the Keysight344xxA device file. I need to work on the temperature selection, I am not sure how I am going to set it up maybe I will use the new selector control

Change 1: removed all of the not needed :update: & :updatedelayed: tags since you added #;init at the end of the :write: tags
Change 2: Changed all radio controls that have more then 3 items to a comboboxHot control
Change 3: added Ratio setup



 Keysight344xxA.txt (18.44 kB - downloaded 62 times.)

[gby]

I am working on a device file for Sorenson/Ametek XG series power supply and have run into an issue.  On a device popup I am trying to have on/off button with "indicator light".  Unfortunately the power supply SCPI code for turning output on/off and for reading the state of the output is not symmetric.  Setting the state you must use "on" or "off" as the value sent.  The same command as a query returns "0" or "1".  If you send "0" or "1" as the value the supply ignores the command/does nothing.  The code I am using is:

#cmdSetup buttonsOn Main_Output
:read: OUTP:POW:STAT?
:write: OUTP:POW:STAT
:color: (0,255,0)
:tip: Turn output on or off
:updatealloff:
Off off
On on

With the above code the buttons successfully turn the output on or off.  However, the indicator light is always off.  If I change the last two lines to Off 0, On 1 the on/off buttons do not work but with manually sending the on/off command the indicator light works.

Any idea to have the buttons and the indicator light work?

[HKJ]

I am working on a device file for Sorenson/Ametek XG series power supply and have run into an issue.  On a device popup I am trying to have on/off button with "indicator light".  Unfortunately the power supply SCPI code for turning output on/off and for reading the state of the output is not symmetric.  Setting the state you must use "on" or "off" as the value sent.  The same command as a query returns "0" or "1".  If you send "0" or "1" as the value the supply ignores the command/does nothing.  The code I am using is:

You need to use something called :readmath: something like:

:readmath: getElement("off on",value);

will probably fix it. It will return "off" when value is 0 and "on" when value is 1

[MikeLud]

HKJ,

I am working on finishing the Temperature setup. I am using the new new selector control, can you check if I am on the right track.

Thanks
MikeLud

 Keysight344xxA.txt (20.35 kB - downloaded 39 times.)

[HKJ]

I am working on finishing the Temperature setup. I am using the new new selector control, can you check if I am on the right track.

Sorry, but there are a few issues with that.
1) A control can only be used in one selector and when you(me) use "Temperature." all controls on the Temperature page are used once, but you also try to use some of them in a second selector.
2) Only top levels selectors can handle more than one control. I can fix that, but not today.
3) The current version to not support multilevel selectors, but that was an easy fix and you can download a new jar file with it from the usual link.

4) To preview a selector page place it as the first line.
 

I also got a timeout:
;; 20:22:59.656 K34465: Rx as number <100.0>
;; 20:22:59.656 K34465: Tx <TEMP:TRANS:FRTD:OCOM?>
;; 20:23:09.657 K34465: Rx Timeout
;; 20:23:09.662 K34465: Rx as number <NaN>

[gby]

HKJ, thanks for the :readmath: getElement("off on",value); tip.  Ufortunately either I am using this idea wrong or something is not working about this idea.  I updated the buttonsOn code to:

Code: [Select]

#cmdSetup buttonsOn Main_Output
:read: OUTP:POW:STAT?
:readmath: getElement("Off On",value);
:write: OUTP:POW:STAT
:color: (0,255,0)
:tip: Turn Main output on or off
:updatealloff:
Off Off
On On
Testing the above the indicator is always on.  Using debug mode I see the readmath is clearly taking the returned 0 or 1 value and changing it to On or Off.  See cut and paste from debug showing all the lines from when I turned the popup on until it populated/was done.  At the end Rx is set to Off but the indicator stays on/lit.  The last line says Rx NaN which is true, but does that indicate a problem?  Suggestions to clean this up/make it work?  In case it helps I have attached the full work in progress device file.  I tested with Ver 0.64.

Code: [Select]

;; A600V1_4A: Tx <SOUR:VOLT:LEV:IMM:AMPL?>
;; A600V1_4A: Rx <625.00000>
;; A600V1_4A: Rx as number <625.0>
;; A600V1_4A: Tx <SOUR:CURR:LEV:IMM:AMPL?>
;; A600V1_4A: Rx <1.46600>
;; A600V1_4A: Rx as number <1.466>
;; A600V1_4A: Tx <SOUR:VOLT:PROT?>
;; A600V1_4A: Rx <660.00000>
;; A600V1_4A: Rx as number <660.0>
;; A600V1_4A: Tx <SOUR:CURR:PROT?>
;; A600V1_4A: Rx <1.54000>
;; A600V1_4A: Rx as number <1.54>
;; A600V1_4A: Tx <OUTP:POW:STAT?>
;; A600V1_4A: Rx <0>
;; A600V1_4A: Rx after :readmath: getElement("Off On",value); <Off>
;; A600V1_4A: Rx as number <NaN>


[HKJ]

Testing the above the indicator is always on.  Using debug mode I see the readmath is clearly taking the returned 0 or 1 value and changing it to On or Off.  See cut and paste from debug showing all the lines from when I turned the popup on until it populated/was done.  At the end Rx is set to Off but the indicator stays on/lit.  The last line says Rx NaN which is true, but does that indicate a problem?  Suggestions to clean this up/make it work?  In case it helps I have attached the full work in progress device file.  I tested with Ver 0.64.

As default buttonson is expecting a numeric result, place a :string: on the next line and it will expect a string result.

[gby]

HKJ, adding :string: got it to work fine.  Thanks for your patience to help me.  Have a great evening.

[MikeLud]

I also got a timeout:
;; 20:22:59.656 K34465: Rx as number <100.0>
;; 20:22:59.656 K34465: Tx <TEMP:TRANS:FRTD:OCOM?>
;; 20:23:09.657 K34465: Rx Timeout
;; 20:23:09.662 K34465: Rx as number <NaN>

HKJ,

I fixed the timeout and added all of the controls on the temperature setup.  Please check out.

Thanks
MikeLud

 Keysight344xxA.txt (20.35 kB - downloaded 47 times.)

[HKJ]

V0.66 is up

The Keysight 344xx is updated, I fixed a few bugs with temperature, but not everything:

Do not work:
;; 08:40:18.852 K34465: Tx <abort>
;; 08:40:18.852 K34465: Tx <*cls>
;; 08:40:18.852 K34465: Tx <TEMP:TRANS:RTD:OCOM 1>  <- Meter report error
;; 08:40:18.852 K34465: Tx <init>
;; 08:40:18.852 K34465: Tx <TEMP:TRAN:RTD:OCOM?>
;; 08:40:19.084 K34465: Rx <0>   <- value is not changed
;; 08:40:19.084 K34465: Rx as number <0.0>

Meter has a Auto zero setting in 2W and Tcouple mode


This version includes a new driver called "ascii", it is very similar to the Modbus driver with command definition, but this time it is plain ascii commands that is defined. This will hopefully make it possible to connect to a lot of non-scpi equipment.
I have updated the manual here: https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html

[MikeLud]

The Keysight 344xx is updated, I fixed a few bugs with temperature, but not everything:

Do not work:
;; 08:40:18.852 K34465: Tx <abort>
;; 08:40:18.852 K34465: Tx <*cls>
;; 08:40:18.852 K34465: Tx <TEMP:TRANS:RTD:OCOM 1>  <- Meter report error
;; 08:40:18.852 K34465: Tx <init>
;; 08:40:18.852 K34465: Tx <TEMP:TRAN:RTD:OCOM?>
;; 08:40:19.084 K34465: Rx <0>   <- value is not changed
;; 08:40:19.084 K34465: Rx as number <0.0>

Meter has a Auto zero setting in 2W and Tcouple mode

HKJ,

Hopefully I have everything now. I am still going to do a complete proof of the device file, let me know if you see anything.

Fix 1: Corrected all of the TRANS errors they should have been TRAN. This was cause by cutting and pasting an error in the manual.
Fix 2: Added Auto zero setting in 2W and Tcouple mode



 Keysight344xxA.txt (22.39 kB - downloaded 44 times.)

[HKJ]

Thermistor 2.25kohm do not work on 34465 (That is the one I am using for testing), the other two values works fine:
;; 14:45:26.353 K34465: Tx <abort>
;; 14:45:26.354 K34465: Tx <*cls>
;; 14:45:26.354 K34465: Tx <TEMP:TRAN:THER:TYPE +2500>
;; 14:45:26.354 K34465: Tx <init>
;; 14:45:26.556 K34465: Tx <TEMP:TRAN:THER:TYPE?>
;; 14:45:26.675 K34465: Rx <+10000>

Looks like a missing :string: tag
;; 14:47:57.940 K34465: Tx <abort>
;; 14:47:57.940 K34465: Tx <*cls>
;; 14:47:57.940 K34465: Tx <TEMP:TRAN:TC:RJUN:TYPE FIX>
;; 14:47:57.941 K34465: Tx <init>
;; 14:47:58.141 K34465: Tx <TEMP:TRAN:TC:RJUN:TYPE?>
;; 14:47:58.283 K34465: Rx <FIX>
;; 14:47:58.283 K34465: Rx as number <NaN>
;; 14:47:58.284 K34465: Tx <TEMP:NULL:VALUE?>
;; 14:47:58.286 K34465: Rx <+0.00000000E+00>


I also get an error from the meter when enabling "Null" in RTD 2W, RTD 4W, thermis2W, but not in thermis4W & Tcouple. There are no errors when disabling it.
The low looks fine enough, here is one fro RTD 2W:
;; 14:58:26.262 K34465: Tx <abort>
;; 14:58:26.262 K34465: Tx <*cls>
;; 14:58:26.262 K34465: Tx <TEMP:NULL:STAT 1>
;; 14:58:26.262 K34465: Tx <init>
;; 14:58:26.463 K34465: Tx <TEMP:NULL:STAT?>
;; 14:58:26.543 K34465: Rx <1>
;; 14:58:26.543 K34465: Rx as number <1.0>
;; 14:58:26.543 K34465: Tx <TEMP:NULL:VALUE?>
;; 14:58:26.546 K34465: Rx <-5.83932611E-01>
;; 14:58:26.546 K34465: Rx as number <-0.583932611>

[MikeLud]

Thermistor 2.25kohm do not work on 34465 (That is the one I am using for testing), the other two values works fine:

Looks like a missing :string: tag

I also get an error from the meter when enabling "Null" in RTD 2W, RTD 4W, thermis2W, but not in thermis4W & Tcouple. There are no errors when disabling it.
The low looks fine enough, here is one fro RTD 2W:

HKJ,

Attached is an updated device file. I am not sure why enabling "Null" in RTD 2W, RTD 4W, thermis2W does not work, do you have any ideas.

Fix 1:  Thermistor 2.25kohm had wrong value +2500 changed to +2250
Fix 2:  Added :string: tag to #cmdSetup radio Offset Temperature2

 Keysight344xxA.txt (22.4 kB - downloaded 36 times.)

[HKJ]

Attached is an updated device file. I am not sure why enabling "Null" in RTD 2W, RTD 4W, thermis2W does not work, do you have any ideas.
Fix 1:  Thermistor 2.25kohm had wrong value +2500 changed to +2250
Fix 2:  Added :string: tag to #cmdSetup radio Offset Temperature2

The string tag fixed that problem, the 2.25k thermistor do not work, do the meter even support it? Maybe I have an old software version?

The beep when enabling "null" is strange, because the command works, even when I get the error message on the meter.

[MikeLud]

Attached is an updated device file. I am not sure why enabling "Null" in RTD 2W, RTD 4W, thermis2W does not work, do you have any ideas.
Fix 1:  Thermistor 2.25kohm had wrong value +2500 changed to +2250
Fix 2:  Added :string: tag to #cmdSetup radio Offset Temperature2

The string tag fixed that problem, the 2.25k thermistor do not work, do the meter even support it? Maybe I have an old software version?

The beep when enabling "null" is strange, because the command works, even when I get the error message on the meter.

HKJ,

2.25k thermistor was added in Firmware Revision 3.00 Enhancements and Fixes. The current firmware is Revision 3.02, link below. Maybe I need to add a #notes Requires Firmware Revision 3.00 or higher.

For the null issue maybe it needs a delay so I adjusted the below line, try the attached
:write: abort;*cls;[100];TEMP:NULL:STAT #;init

https://www.keysight.com/main/software.jspx?ckey=2367633&lc=eng&cc=US&nid=-32051.1242960&id=2367633

 Keysight344xxA.txt (22.41 kB - downloaded 55 times.)

[HKJ]

2.25k thermistor was added in Firmware Revision 3.00 Enhancements and Fixes. The current firmware is Revision 3.02, link below. Maybe I need to add a #notes Requires Firmware Revision 3.00 or higher.

Thanks for the link, now some of meters are up to date:
;; Keysight Technologies,34461A,MY53214390,A.03.02-02.40-03.02-00.52-01-01 
;; Keysight Technologies,34465A,MY57502236,A.03.02-02.40-03.02-00.52-03-01 
;; Keysight Technologies,34470A,MY54700281,A.03.02-02.40-03.02-00.52-02-01 

But none of them will handle the 2.25kohm thermistor. I found out what the problem was with the null: The meter must have a valid reading when I activate it. Why it reports error in command, instead of something more like invalid input, it not something that can guess.

The 34461 has a couple of problems with temperature, it has much less support for different thermo sensors than the bigger model.
Here is one of the problems:
;; 17:23:28.006 K34461: Tx <TEMP:TRAN:RTD:OCOM?>
;; 17:23:38.006 K34461: Rx Timeout
;; 17:23:38.006 K34461: Rx as number <NaN>
;; 17:23:38.006 K34461: Tx <TEMP:TRAN:THER:POW:LIM:STAT?>
;; 17:23:48.006 K34461: Rx Timeout

[tubularnut]

My 34465A has the option of a 2.252 kohm thermistor, not 2.25 kohm

[HKJ]

My 34465A has the option of a 2.252 kohm thermistor, not 2.25 kohm

That was the issue, now it is working.

[Messtechniker]

Thanks for the massive amount of work you put into this.
RTD 2W now works on my 34465A which is great news. 
But a small bug remains here:
RTD 2W LP does not work. LP is not displayed and the temperature value does not change slightly as it should.

[HKJ]

Thanks for the massive amount of work you put into this.
RTD 2W now works on my 34465A which is great news. 
But a small bug remains here:
RTD 2W LP does not work. LP is not displayed and the temperature value does not change slightly as it should.

There is a typo in the settings, the correct is:
#cmdSetup radio RTD_2w_Low-Power Temperature2
:write: abort;*cls;TEMP:TRAN:RTD:POW:LIM:STAT #;init
:read: TEMP:TRAN:RTD:POW:LIM:STAT?
:update: Null_Value

[MikeLud]

My 34465A has the option of a 2.252 kohm thermistor, not 2.25 kohm

There is a typo in the settings, the correct is:
#cmdSetup radio RTD_2w_Low-Power Temperature2
:write: abort;*cls;TEMP:TRAN:RTD:POW:LIM:STAT #;init
:read: TEMP:TRAN:RTD:POW:LIM:STAT?
:update: Null_Value

HKJ,

I did a good hard look at the device file, hopefully I did not miss anything. Remove all features that the 34461A does not have.

I was thinking of changing all of the Mode conf: (resets all settings to default) commands to  func (keeps last settings) and add on the top of each setup a reset to default button using the conf: command. What are your thoughts, good idea?

 Keysight344xxA.txt (24.4 kB - downloaded 49 times.)

Fix1: Corrected 2.252 kohm thermistor
Fix2: Corrected #cmdSetup radio RTD_2w_Low-Power Temperature2 typo.

[HKJ]

I was thinking of changing all of the Mode conf: (resets all settings to default) commands to  func (keeps last settings) and add on the top of each setup a reset to default button using the conf: command. What are your thoughts, good idea?

I do have that much of an opinion on it, with the current menus it is very fast to setup the meter either way around.
Maybe change you note to say "3.00 to support all functions" or something similar, because it mostly work on older versions.