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

[HKJ]

Both HKJ and Gertjan... that fixes it... but now the limit is 8.... ?

Is that the max?

Yep, the limit is 8, except for digital traces.

[flash2b]

What is a digital trace in TC?

I see the number of histograms is limited to 3. 

[HKJ]

What is a digital trace in TC?

It is a trace with two states, they can be declare in device definitions and on the Math page (Type Digital).

I see the number of histograms is limited to 3. 

Any more would be way to small.

[Richard W.]

Hi, I'm new here. I apologize in advance for my bad English.
I have a problem with communication between a PC with W10prof 64b and HP34401A. The connection between the PC and the HP is an RS232-USB cable and a null modem connected as shown in the picture.
https://cdn.shopify.com/s/files/1/0267/5366/3039/files/dd577314b803a2ebc27b2307185a01ac_480x480.jpg?v=1607953427
TC shows that the connection is established, but when clicking on any button in TC reports HP error -410 (return communication error)
I loaded SW TC about a week ago on a PC with W7Prof64b and it behaves the same.
Could I ask for some advice?

Hi

i've got a similar problem, trying to use TC with an HP 34401 via USB to RS232 on UBUNTU

If i start the Software via Terminal as Superuser (sudo java -jar /..../.../TestController.jar) i can connect to the Instrument, Display says "Rmt", i can query "*idn?" and the Multimeter answers correctly. Scaling of the Fonts / Graphics look a bit strange so..

As soon as i click "log" or any other button in TC, the Multimeter says Error -410
Funny thing: it was already working briefly, i was able to see actual values.

Since IDN works, i assume the Hardware should be fine?

If i start TC without Superuser, the Fonts and Graphics of TC look fine, but the connection doesn't work.

Unfortunately i'm new to Linux, so please consider stupid errors made by me 

Maybe some timing-issues?
Maybe Linux is not up for these highly complex tasks? 

The PC itself is an i3 second generation, 4GB RAM, Notebook.
Quite old, but i assumed it should be fine for this task? 

Any help is appreciated 

[HKJ]

As soon as i click "log" or any other button in TC, the Multimeter says Error -410
Funny thing: it was already working briefly, i was able to see actual values.

Since IDN works, i assume the Hardware should be fine?

There is a issue with handshake on Linux (It is not fully supported), it may be the problem here.

[flash2b]

What chipset do you use for the USB to RS232 ? (Prolific, FTDI, WCH, SiliconLabs, etc....)

Also sometimes the connection to Carrier Detect (CD) in the null modem adapter can be the problem. On ether DTE or DCE side.

[TizianoHV]

If i start the Software via Terminal as Superuser (sudo java -jar /..../.../TestController.jar) i can connect to the Instrument, Display says "Rmt", i can query "*idn?" and the Multimeter answers correctly.

I'm on linux mint and it just works, have you enabled your user for serial ports? "sudo usermod -a -G dialout $USER"

As soon as i click "log" or any other button in TC, the Multimeter says Error -410
Since IDN works, i assume the Hardware should be fine?

Sometimes it happens also on windows for me. Usually, when it gets stuck, I send manually some query commands and it purges. I use "cutecom" and send "*IDN?" a few times. If you send manually "READ?" does it works?

[HKJ]

V2.95 is up
It contains a few new devices and some updated devices, but it is mostly some minor changes/addition to TC by me.
   Update: UNI-T UTL8511+, UNI-T UTL8512+ and UNI-T UTL8513+ Electronic load (Thanks homico)
   Added: A HiRes (i.e. ms) time option for the time column in table view.
   Added: Configuration to adjust dateTime format.
   Added: Keithley 2700, Keithley 2701, Keithley 2750 DMM (Thanks KungFuJosh)
   Updated: Keithley DMM6500, Keithley DAQ6510 and Keithley DMM7510 DMM (Thanks KungFuJosh)
   Added: R&S RTB2004 Oscilliscope (Thanks 2X)
   Added: Build in function to view/edit AutoRun/AutoInit files (Edit uses a OS supplied editor).
   Added: AutoInit file, this is a script file that will be executed each time devices are loaded.
   Added: getHandle("deviceName") function to return actual handle for a loaded device, based on its name.
   Added: isLoaded("handle/deviceName") function to check if a specific device is loaded.

I believe the autoRun facility of TC is mostly ignored, I have made it more easy accessible and also added a AutoInit that is much more useful.
The documentation is here: https://lygte-info.dk/project/TestControllerAuto%20UK.html it is accessible when pressing F1 in the view window and from the website.

It can be used to make TC automatic do stuff like opening a window when loading devices:


I do not really agree with the HiRes time option, but now it is possible to force more decimal in the tables time column (Right click and select Time or TimeHiRes).
Anybody that dislike my date format (Probably all Americans, they want month first) can now make their own, the full range of Javas time format is available, to get back to my format simply clear the field.

If somebody makes some useful scripts for the Auto files, please post them, I may add a example page at a later date if there are many good ideas.

[flash2b]

The UNI-T UTL8511+, UNI-T UTL8512+ and UNI-T UTL8513+ definition produces an error:

Code: [Select]

dk.hkj.devices.SetupFormats$NumberField - Amp_Fall - Line do not contain 3 parameters: :-------------------------------------------
dk.hkj.devices.SetupFormats$NumberField - Amp_Fall - Line do not contain 3 parameters: :-------------------------------------------
dk.hkj.devices.SetupFormats$NumberField - Amp_Fall - Line do not contain 3 parameters: :-------------------------------------------


[HKJ]

The UNI-T UTL8511+, UNI-T UTL8512+ and UNI-T UTL8513+ definition produces an error:

I hope homico sees this and get it fixed.

[KungFuJosh]

I'm adding Filter options to the DAQ/DMM definition, and I ran into a sort of weird maybe bug (using latest version - haven't tested others).

I've added the Filter function to the bottom of each function's setup controls. However, I was forced to add it to the top of the Temperature function, probably because of the paging...but that's weird.

Here's what works:

Code: [Select]

; ******** TEMPERATURE ********
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup separator - Temperature
:labelformat: bold (0,40,115)
1 100 Empty
center Filter_Settings
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup buttonsOn Temp_Filter Temperature
:read: TEMP:AVER?
:write: TEMP:AVER (value)
:string:
:nogrid:
:color: blue
Off 0
On 1
:tip: Enable or disable filter.
#cmdSetup number Temp_Filter_Count Temperature
:read: TEMP:AVER:COUN?
:write: TEMP:AVER:COUN #
_ 1 100
:updatemodechange:
:tip: Filter average count. Higher value results in less noise.
#cmdSetup comboboxHot Temp_Filter_Avg_Type Temperature
:read: TEMP:AVER:TCON?
:write: TEMP:AVER:TCON #
:updatedelayed: 0.5
:update: Temp_Filter_Avg_Type
Repeating REP
Moving MOV
Hybrid HYB
:tip: The hybrid average filter is only available when the buffer style is set to Full.
:updatemodechange:
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup separator - Temperature
:labelformat: bold (0,40,115)
1 100 Empty
center Sensor_Settings
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup comboboxHot Transducer_Type Temperature
:read: :TEMP:TRAN?
:write: :TEMP:TRAN (value)
:update: Temperature_Settings
:string:
Thermocouple TC
Thermistor THER
2W_RTD RTD
3W_RTD TRTD
4W_RTD FRTD
:updatemodechange:
#cmdSetup toggleButton Temperature_Unit Temperature
:read: :TEMP:UNIT?
:write: :TEMP:UNIT (value)
:nogrid:
:string:
:color: red green blue
:updatedelayed: 1
Celsius CELS
Fahrenheit FAHR
Kelvin KELV
:updatemodechange:
#cmdSetup selector Temperature_Settings Temperature
:read: :TEMP:TRAN?
:update: Transducer_Type
:updatedelayed: 0.2
:updatemodechange:
RTD Temperature2.Transducer_Type Temperature2.2W_RTD_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
TRTD Temperature2.Transducer_Type Temperature2.3W_RTD_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
FRTD Temperature2.Transducer_Type Temperature2.4W_RTD_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
THER Temperature2.Transducer_Type Temperature2.Thermistor_Type Temperature2.NPLCycles  Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
TC Temperature2.Transducer_Type Temperature2.Thermocouple_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync

#cmdSetup buttonsOn Line_Sync Temperature2
:read: :TEMP:LINE:SYNC?
:write: :TEMP:LINE:SYNC (value)
:string:
:nogrid:
:color: blue
Off 0
On 1
:tip: Enable or disable line sync.
#cmdSetup radio Auto_Zero Temperature2
:read: :TEMP:AZERO?
:write: :TEMP:AZERO #
Off 0
On 1
:updatemodechange:
#cmdSetup button Auto_Zero_Once Temperature2
:write: :AZERo:ONCE
:update: Auto_Zero
:updatemodechange:
:tip: Perform Auto Zero one time.
#cmdSetup number NPLCycles Temperature2
:read: TEMP:NPLC?
:write: TEMP:NPLC #
_ 0.0005 15
:updatemodechange:
:tip: Max is 12 for 50Hz, or 15 for 60Hz
#cmdSetup comboboxHot Thermocouple_Type Temperature2
:read: :TEMP:TC:TYPE?
:write: :TEMP:TC:TYPE #
:update: Active_Type
B B
E E
J J
K K
N N
R R
S S
T T
:updatemodechange:
#cmdSetup toggleButton Thermistor_Type Temperature2
:read: :TEMP:THER?
:write: :TEMP:THER (value)
:update: Thermistor_Type
:nogrid:
:string:
:color: red green blue
2.2kOhm 2252
5kOhm 5000
10kOhm 10000
:updatemodechange:
#cmdSetup comboboxHot 2W_RTD_Type Temperature2
:read: :TEMP:RTD:TWO?
:write: :TEMP:RTD:TWO (value)
:string:
PT100 PT100
PT385 PT385
PT3916 PT3916
D100 D100
F100 F100
User USER
:updatemodechange:
#cmdSetup comboboxHot 3W_RTD_Type Temperature2
:read: :TEMP:RTD:THR?
:write: :TEMP:RTD:THR (value)
:string:
PT100 PT100
PT385 PT385
PT3916 PT3916
D100 D100
F100 F100
User USER
:updatemodechange:
#cmdSetup comboboxHot 4W_RTD_Type Temperature2
:read: :TEMP:RTD:FOUR?
:write: :TEMP:RTD:FOUR (value)
:string:
PT100 PT100
PT385 PT385
PT3916 PT3916
D100 D100
F100 F100
User USER
:updatemodechange:
This does not work:

Code: [Select]

; ******** TEMPERATURE ********
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup separator - Temperature
:labelformat: bold (0,40,115)
1 100 Empty
center Sensor_Settings
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup comboboxHot Transducer_Type Temperature
:read: :TEMP:TRAN?
:write: :TEMP:TRAN (value)
:update: Temperature_Settings
:string:
Thermocouple TC
Thermistor THER
2W_RTD RTD
3W_RTD TRTD
4W_RTD FRTD
:updatemodechange:
#cmdSetup toggleButton Temperature_Unit Temperature
:read: :TEMP:UNIT?
:write: :TEMP:UNIT (value)
:nogrid:
:string:
:color: red green blue
:updatedelayed: 1
Celsius CELS
Fahrenheit FAHR
Kelvin KELV
:updatemodechange:
#cmdSetup selector Temperature_Settings Temperature
:read: :TEMP:TRAN?
:update: Transducer_Type
:updatedelayed: 0.2
:updatemodechange:
RTD Temperature2.Transducer_Type Temperature2.2W_RTD_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
TRTD Temperature2.Transducer_Type Temperature2.3W_RTD_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
FRTD Temperature2.Transducer_Type Temperature2.4W_RTD_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
THER Temperature2.Transducer_Type Temperature2.Thermistor_Type Temperature2.NPLCycles  Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync
TC Temperature2.Transducer_Type Temperature2.Thermocouple_Type Temperature2.NPLCycles Temperature2.Auto_Zero Temperature2.Auto_Zero_Once Temperature2.Line_Sync

#cmdSetup buttonsOn Line_Sync Temperature2
:read: :TEMP:LINE:SYNC?
:write: :TEMP:LINE:SYNC (value)
:string:
:nogrid:
:color: blue
Off 0
On 1
:tip: Enable or disable line sync.
#cmdSetup radio Auto_Zero Temperature2
:read: :TEMP:AZERO?
:write: :TEMP:AZERO #
Off 0
On 1
:updatemodechange:
#cmdSetup button Auto_Zero_Once Temperature2
:write: :AZERo:ONCE
:update: Auto_Zero
:updatemodechange:
:tip: Perform Auto Zero one time.
#cmdSetup number NPLCycles Temperature2
:read: TEMP:NPLC?
:write: TEMP:NPLC #
_ 0.0005 15
:updatemodechange:
:tip: Max is 12 for 50Hz, or 15 for 60Hz
#cmdSetup comboboxHot Thermocouple_Type Temperature2
:read: :TEMP:TC:TYPE?
:write: :TEMP:TC:TYPE #
:update: Active_Type
B B
E E
J J
K K
N N
R R
S S
T T
:updatemodechange:
#cmdSetup toggleButton Thermistor_Type Temperature2
:read: :TEMP:THER?
:write: :TEMP:THER (value)
:update: Thermistor_Type
:nogrid:
:string:
:color: red green blue
2.2kOhm 2252
5kOhm 5000
10kOhm 10000
:updatemodechange:
#cmdSetup comboboxHot 2W_RTD_Type Temperature2
:read: :TEMP:RTD:TWO?
:write: :TEMP:RTD:TWO (value)
:string:
PT100 PT100
PT385 PT385
PT3916 PT3916
D100 D100
F100 F100
User USER
:updatemodechange:
#cmdSetup comboboxHot 3W_RTD_Type Temperature2
:read: :TEMP:RTD:THR?
:write: :TEMP:RTD:THR (value)
:string:
PT100 PT100
PT385 PT385
PT3916 PT3916
D100 D100
F100 F100
User USER
:updatemodechange:
#cmdSetup comboboxHot 4W_RTD_Type Temperature2
:read: :TEMP:RTD:FOUR?
:write: :TEMP:RTD:FOUR (value)
:string:
PT100 PT100
PT385 PT385
PT3916 PT3916
D100 D100
F100 F100
User USER
:updatemodechange:

#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup separator - Temperature
:labelformat: bold (0,40,115)
1 100 Empty
center Filter_Settings
#cmdSetup separator - Temperature
1 100 Sunken
#cmdSetup buttonsOn Temp_Filter Temperature
:read: TEMP:AVER?
:write: TEMP:AVER (value)
:string:
:nogrid:
:color: blue
Off 0
On 1
:tip: Enable or disable filter.
#cmdSetup number Temp_Filter_Count Temperature
:read: TEMP:AVER:COUN?
:write: TEMP:AVER:COUN #
_ 1 100
:updatemodechange:
:tip: Filter average count. Higher value results in less noise.
#cmdSetup comboboxHot Temp_Filter_Avg_Type Temperature
:read: TEMP:AVER:TCON?
:write: TEMP:AVER:TCON #
:updatedelayed: 0.5
:update: Temp_Filter_Avg_Type
Repeating REP
Moving MOV
Hybrid HYB
:tip: The hybrid average filter is only available when the buffer style is set to Full.
:updatemodechange:

The only difference between the two is the placement of the filter code. I assumed it would be fine at the end since it specifies Temperature, and not Temperature2. When it is set at the bottom, there are also visual bugs present as seen in the screenshots. For the Mode buttons, mousing over the screwed up buttons fixes them. Moving the Filter stuff to the top fixed both problems. 🤷

Thanks,
Josh

[Richard W.]

As soon as i click "log" or any other button in TC, the Multimeter says Error -410
Funny thing: it was already working briefly, i was able to see actual values.

Since IDN works, i assume the Hardware should be fine?

There is a issue with handshake on Linux (It is not fully supported), it may be the problem here.

Thanks for the infomation, maybe i have to get a Windows-Machine for this task...

Or does Linux Mint behave different from Ubuntu?

[...]

I'm on linux mint and it just works, have you enabled your user for serial ports? "sudo usermod -a -G dialout $USER"

[...]
Since IDN works, i assume the Hardware should be fine?

Sometimes it happens also on windows for me. Usually, when it gets stuck, I send manually some query commands and it purges. I use "cutecom" and send "*IDN?" a few times. If you send manually "READ?" does it works?

I enabled the user to use the serial port. Otherwise nothing works. Took me some time to figure out...
If the HP goes into error, i can't get it out again. I need to power cycle. The error gets logged several times.

What chipset do you use for the USB to RS232 ? (Prolific, FTDI, WCH, SiliconLabs, etc....)

Also sometimes the connection to Carrier Detect (CD) in the null modem adapter can be the problem. On ether DTE or DCE side.

It's a FTDI-Adapter. The null modem adapter is hand soldered according to the HP's user manual, using all 9 lines.
The used Adapters and Cables have worked before (under Windows, playing around with HTERM)

[KungFuJosh]

Here's the updated definition for the DAQ6510/DMM6500/DMM7510. Cleaned up the initcmd and added filter support.

Thanks,
Josh

[HKJ]

I'm adding Filter options to the DAQ/DMM definition, and I ran into a sort of weird maybe bug (using latest version - haven't tested others).

I've added the Filter function to the bottom of each function's setup controls. However, I was forced to add it to the top of the Temperature function, probably because of the paging...but that's weird.

I have no idea where to start to figure this one out.
The paging is done by sorting the controls, before initializing and rendering them on different pages.

[HKJ]

There is a issue with handshake on Linux (It is not fully supported), it may be the problem here.

Thanks for the infomation, maybe i have to get a Windows-Machine for this task...

I do not have the equipment and have not tested it, the issue I mention is described in the JSerialComm library I uses for communication (It is a Linux issue, not Windows).
I remember that some early HP equipment had a issues with handshake, it basically accepted one command and then needed a sort pause before the next, it used handshake to signal that. I have no idea how big a issues it is in praxis.

[HKJ]

Here's the updated definition for the DAQ6510/DMM6500/DMM7510. Cleaned up the initcmd and added filter support.

I have updated it, thanks.

[KungFuJosh]

I've made some updates to the Keysight 344xxA definition. Main changes include: added filter functions for 34465A and 34470A; added support for 34460A (needs to be tested but should work); changed value lines to default SI7 instead of D6; changed handles to include the trailing A.

Thanks,
Josh

[HKJ]

I've made some updates to the Keysight 344xxA definition. Main changes include: added filter functions for 34465A and 34470A; added support for 34460A (needs to be tested but should work); changed value lines to default SI7 instead of D6; changed handles to include the trailing A.

I have added it, but I got rid of the A. I do not like changing handles and I see no reason for the change.

[KungFuJosh]

I have added it, but I got rid of the A. I do not like changing handles and I see no reason for the change.

It bugs me because the model number includes an A and the file doesn't for no reason. But I'll keep my version. It only takes a second to update your scripts tho.

[HKJ]

I have added it, but I got rid of the A. I do not like changing handles and I see no reason for the change.

It bugs me because the model number includes an A and the file doesn't for no reason. But I'll keep my version. It only takes a second to update your scripts tho.

There is no version of the meters without the A, that makes the letter superfluous and I prefer the slightly shorter handle.

[KungFuJosh]

There is no version of the meters without the A, that makes the letter superfluous and I prefer the slightly shorter handle.

I heard a rumor there will be a 34465B.

[flash2b]

I can't get the #metaSection and #sections to work.

I have, for two different devices/handles:
#idString Flash2b, NXH16,
#name Flash2b NXH16
#handle NXH16
#sections CH8

#idString Flash2b, NXH32,
#name Flash2b NXH32
#handle NXH32
#sections CH20

I have made splitted-up my commands with

#metaSection CH20
...
...
#metaSection

But only the handle CH8 works, excluding the commands between #metaSection CH20... so OK

But....

If I switch to the handle where CH20 is active, it will also exclude... so non of the #metaSection CH20 commands are executed while #sections CH20 is part of the device handle.

Why is that ?


I got it a bit further with this now, since #metaDebug does not seem to work,  so I removed the #idString, #name and #handle after the meta section introducing some errors. Now #metaDebug shows the include and exclude, so the debug only shows details in case of an error. See below.

Code: [Select]

Starting
Definition is not valid: null
#metaDebug on Flash2b NXH32
#metaSection CH20  --Include--
#metaSection  --Include--
#metaSection CH20  --Include--
#metaSection  --Include--
#metaSection CH20  --Include--
#metaSection  --Include--
#metaSection CH20  --Include--
#metaSection CH20  --Include--
#metaSection CH8  --Exclude--
#metaSection  --Include--
#metaSection CH20  --Include--
#metaSection  --Include--
#metaSection CH20  --Include--
#metaSection  --Include--
Definition is not valid: null
Definition is not valid: null
;; jSerialComm version: 2.11.2
How can I see what is correct and what is wrong from this debug ?

Investigating the #metaDebug problem shows:

- For the ascii driver, when #metaDebug is there, I see debug messages ! like #replaceText
- For the modbus driver, when #metaDebug is there, I DO NOT see debug messages ! (there are #replaceText in the definition)

So bottom line, there is a problem with #metaDebug for sure, and it seems that #sections are not handled correctly for Modbus driver.

[flash2b]

@homico

Can you fix you defintion please ?

The UNI-T UTL8511+, UNI-T UTL8512+ and UNI-T UTL8513+ definition produces an error:

Code: [Select]

dk.hkj.devices.SetupFormats$NumberField - Amp_Fall - Line do not contain 3 parameters: :-------------------------------------------
dk.hkj.devices.SetupFormats$NumberField - Amp_Fall - Line do not contain 3 parameters: :-------------------------------------------
dk.hkj.devices.SetupFormats$NumberField - Amp_Fall - Line do not contain 3 parameters: :-------------------------------------------


[homico]

Can you fix you defintion please ?

The UNI-T UTL8511+,

OK,,, I'll try....
...if I understand what it is

[flash2b]

I have update my Yokogawa defintion.

Added: embededed dummyInit; #interface commands, modeRanges? to read from cached modeVal, DA Output Option support, Cleanup for 7551/7552, function and range commands, Changed dB to 5 decimals.

HKJ please add it to TC.

 Yokogawa 7551-7552 v1.07 Final.zip (7.29 kB - downloaded 22 times.)