Program that can log from many multimeters.

[Gulftown]

Hi,

i tried to integrate my Tek TDS460A with a GPIB Adapter using an ESP32 Port of the AR488 Project.
When i try to add an AR488Lan Interface from the GPIB Menu, Test Controller adds a normal AR488 interface where i can not set the ip adress and just the serial port.

I think this is a bug.

I was able to add the Scope with a litte bit of hacking in the normal Tek MDO MSO etc. device definition using a normal tcp socket and the auto mode in AR488, but it would be nice to use the correct method for this.

Thank you.

[HKJ]

When i try to add an AR488Lan Interface from the GPIB Menu, Test Controller adds a normal AR488 interface where i can not set the ip adress and just the serial port.

I think this is a bug.

It is a bug, it is fixed (It was very simple to fix) and will be included in the next release.

[adso85swe]

TC do not have that function, but it can easily be done with scripting in TC, including naming the files with a sequence number or a date.
This example will save every 10 seconds and then restart the log:

#while 1
#log 1
#delay 10
#log 0
#savetable ("c:\\data\\log"+date())
#endwhile

Place it in the "log" window and press "Run", it will log from all connected devices

In this scripting example above to start a log from the command prompt, is it possible to add a line to set the logging frequency as well? I.e. can I define that I want data to be logged e.g. every third second by script?

[HKJ]

In this scripting example above to start a log from the command prompt, is it possible to add a line to set the logging frequency as well? I.e. can I define that I want data to be logged e.g. every third second by script?
[/quote]

Easily, the number after the #log command is the logging interval in seconds. You need to use #log 3 for every third second, values like #log 0.1 is also possible (10 times a second).

[HKJ]

Somebody posted some questions and deleted them again, but they where good questions:

If I will use this script, then by automatically saving partial logs and restarting the table each time, TC will not use a lot of RAM on the PC, when logging very long time?

That is correct, but using the "Direct to disk" option is easier and will put all data in one file. Neither is needed for a few hours of logging.

And please explain me one thing, when I import CSV to Open Office spreadsheet, "minutes" and "date" are presented in strange way. Can not figure out how to convert it in to actual minutes and date:

Instead of using the save button, use the export button and select another format for "dateTime" in the format column.

[Gediminas]

In this scripting example above to start a log from the command prompt, is it possible to add a line to set the logging frequency as well? I.e. can I define that I want data to be logged e.g. every third second by script?


Easily, the number after the #log command is the logging interval in seconds. You need to use #log 3 for every third second, values like #log 0.1 is also possible (10 times a second).

If I understood correctly, then if I will use this script, which saves partial logs and restarts table each time, then TC will need much less RAM, when logging very long time, right?

Also, can someone explain to me what "DATE TIME" format TC are using, when saving table as CSV file. I imported table in Open Office, and can not figure it out.

[HKJ]

I answered most of it above, the actual format of dateTime is Unix, i.e. seconds since Jan 01 1970.

[Gediminas]

I answered most of it above, the actual format of dateTime is Unix, i.e. seconds since Jan 01 1970.

Thanks!

[Oleksii]

Is there any way to have a dedicated button, which starts logging by single click with predefined interval?

I find it complicated and annoying that I need to do extra steps than just a single click:
- one click on Log button;
- move mouse down to X seconds option;
- click one more time on desired interval.

[Oleksii]

Also, one more feature request - clean up current collected values by a singe button.
This would allow to avoid stop/start again steps, which I should perform each time for such cleanup.

I'd love to see such button everywhere where we have buttons Save/Export. First of all its on Chart and Historgram tabs.

[HKJ]

Is there any way to have a dedicated button, which starts logging by single click with predefined interval?

I find it complicated and annoying that I need to do extra steps than just a single click:
- one click on Log button;
- move mouse down to X seconds option;
- click one more time on desired interval.

There is, it is called Grid Panel. You can also assign script commands to a function key.

Try executing this command:
#SinglePanel 302 37 212 118 Script "Logging" "script:#;1sec\n#log 1" "script:#;Stop\n#log 0"

This command can also be assigned to a function key.

[HKJ]

Also, one more feature request - clean up current collected values by a singe button.
This would allow to avoid stop/start again steps, which I should perform each time for such cleanup.

I'd love to see such button everywhere where we have buttons Save/Export. First of all its on Chart and Historgram tabs.

What do you mean bu clean up?

[Oleksii]

What do you mean bu clean up?

Imagine when I had Log running and want to start it as a new logging, to forget min/max/avg values and have a new/fresh only values on Graph, Table, Chart tabs

And I want to perform it easily, preferably by single click on a dedicated button on those tabs in TC.

[HKJ]

What do you mean bu clean up?

Imagine when I had Log running and want to start it as a new logging, to forget min/max/avg values and have a new/fresh only values on Graph, Table, Chart tabs

And I want to perform it easily, preferably by single click on a dedicated button on those tabs in TC.

I still don't understand, all min/max/avg is based on actual table data and when you start on a new log the table start over, i.e. they are cleaned out.
Another point is that you can control just about anything in TC from script, i.e. you can add more than just "#log 1" to a button, you can also add script commands to set specific values/states in TC or anything else.
To find the commands type # on the command line and the help window will show a list of all commands. Typing the full name of a command will show a description of the parameters in the help window.

[KungFuJosh]

Can you add a note on your website about the release date so we know if it's been updated recently?

Thanks!

[HKJ]

Can you add a note on your website about the release date so we know if it's been updated recently?

I do not really see a reason for that, TC itself tells you when a new version is available:

 
You can also subscribe to this thread and you will get notified when a new release is available and a lot of other stuff about TC.

[Gediminas]

In case somebody is interested,

Finally found Serial to USB adapter which works out of the box on Windows 10 (Windows installs driver automatically).
Chip FT232RL
Supports 3.3V and 5V systems
Has integrated stabilizer for 3.3V power delivery



Bought it in Europe for about 5 Euro here: https://ardustore.dk/produkt/ft232rl-ftdi-usb-2-0-to-ttl-serial-adapter-module?gad_source=1&gclid=Cj0KCQiA6vaqBhCbARIsACF9M6mFt5dqH5Lfv7ZKHjJnqkt39621htmWl7eMl2ZpxOtOSiz2XIU-Nc8aAnowEALw_wcB

[Messtechniker]

Simply search for
FT232RL FTDI USB
for many hits.

[C18669]

Hi Everyone
I am trying to add the HP 6033 power supply... I have got to the point where I get
;; Start thread for: PrologixUSB A:7 - HP6033a
;; COM6: Tx: <++auto 0.> 2B 2B 61 75 74 6F 20 30 0A
;; COM6: Tx: <++mode 1.> 2B 2B 6D 6F 64 65 20 31 0A
;; : Tx <txrx? ID?>
;; COM6: Tx: <++addr 7.> 2B 2B 61 64 64 72 20 37 0A
;; COM6: Tx: <ID?.> 49 44 3F 0A
;; COM6: Tx: <++read_tmo_ms 900.> 2B 2B 72 65 61 64 5F 74 6D 6F 5F 6D 73 20 39 30 30 0A
;; COM6: Tx: <++read eoi.> 2B 2B 72 65 61 64 20 65 6F 69 0A
;; COM6: Rx: <ID HP6033A> 49 44 20 48 50 36 30 33 33 41
;; PrologixUSB A:7 Device HP6033a do not match: ID HP6033A
;; COM6: Close
;; Stopping thread for: PrologixUSB A:7 - HP6033a
;; COM6: Close

the device file has...
#idString HP6033a
#name HP6033a
#handle HP6033A
#port GPIB
#baudrate 9600
#driver SCPIx

[C18669]

Hi Everyone
managed to "fix" my issue...  not nice, but it works....

#idString ID HP6033A
#name HP6033A
#handle ID,HP6033A
#port GPIB
#baudrate 9600
#driver SCPIx

[HKJ]

Hi Everyone
managed to "fix" my issue...  not nice, but it works....

#idString ID HP6033A

Not nice, but it is the answer, you can improve it by using a #scpiCmd override to edit it.

[Messtechniker]

Been busy doing a device file for my new UNI-T UT622 LCR meter.
Works quite well with Test Controller. Except for the fact that it will log only ESR and not Capacitance. But the values are being logged in Table. Strange.

Also the supplied software apparently uses some commands not detailed in the manual.
Like "Clear", "Parallel", "Serial" and "REC", for example. Will probably have to sniff these.

Now some piccies:

[HKJ]

Been busy doing a device file for my new UNI-T UT622 LCR meter.
Works quite well with Test Controller. Except for the fact that it will log only ESR and not Capacitance. But the values are being logged in Table. Strange.

Looking forward to getting the definition.
What do you mean by "being logged in the table"?

Also the supplied software apparently uses some commands not detailed in the manual.
Like "Clear", "Parallel", "Serial" and "REC", for example. Will probably have to sniff these.

That is probably a issue with many devices. They have a few extra commands for their software, but they are not documented anywhere.

My guess is that (in some cases) the design team decides what is needed of commands, but the team doing the software find out that they need more commands. These commands are then not documented because they are not defined by the design team.
I will agree that it is very bad praxis to do this, but my opinion do not affect anything for the manufacturer.

[Messtechniker]

The values from the UT622 are to be found for both Capacitance and ESR in the Table. But only the values for ESR are to be found in the graph. Strange. Will look into this tomorrow.

[HKJ]

The values from the UT622 are to be found for both Capacitance and ESR in the Table. But only the values for ESR are to be found in the graph. Strange. Will look into this tomorrow.

??
That makes no sense, table and chart uses the same variables. You might have found a special character that TC has issues with.
Basically value names are variables in TC, that put some restriction on them, but I have put in some code to (try to) fix it.


Variables names may not contain anything like control chars or operators used in expressions. That is simplified, but mostly covers it.

For more knowledge: The variable tables in TC do not have any restriction on names, but the parser have. This means that you can get around restrictions, but I will rate that as a bad idea.