Hi, any config file here for ET5420A+?
Hi HKJ,
I wrote a configuration file for the HP / Agilent 3458A 8,5 digit multimeter.
Quote from: HKJ on 12 December 2022, 10:56:09
I generally do not decode secondary displays on multimeters, there are a couple of reasons for that.
Not very useful information (This is mostly about the frequency in AC).
Logging rate goes down (Depends on multimeter).
TC will automatic track range changes for devices with one value, not for devices with multiple values. This is not about the main pages, but on the popups (A lot of TC's functionality are in the popups).
Here is a device configuration file for Fluke 863, 865 and 867B Graphical Multimeters.
Just for fun, and for your Multimeter frequency response page, here is the frequency response of the 867B:
The "USBTMC" Protocol has come up in the past. I've an OWON SDS1192 which uses the "PC" setting to log to its own propreiety software. However, it does support "USBTMC" mode as well.
Any chance of this being updated? I know very little about it at the moment, but it appears it would allow Test Controller to nearly immediately add a bunch of equipment to its list of supported devices.
The problem is that USBTMC requires native code and cannot be done in Java and native code requires separate code for each OS and cpu architecture.
OK, back to my question.
Wouldn't python-usbtmc make all this happen?
https://github.com/python-ivi/python-usbtmc
At least I could connect to a Siglent DSG1025 AWG on the command line using pyvisa after installing python-usbtmc
I'm trying for a device to convert in NR3 a number. For example 0.123 -> 123E-03 (and not 123m as si). Is there a trick to do it ?
Hi HKJ,
Thank you for the explanation. I tried it immediately.
When I click right on the log window and select "Generate scripts" and then "Chart/Hist/Range script", indeed something is running in the log & program editor window. I save the script.
When I stop, and restart the logging, I click "load and run", open the script, and click "run". Indeed the right traces are now selected, but unfortunately NOT in the right order....
So I must be missing something....
Anyway, this work-around seems like more work then just manually click the traces in the right order....
I think I see the problem, I have not really seen the selection sequence as a important parameter, just that the right tracks are selected.
The script do more than just select the traces as you can see on the script commands.
If you email me a datafile and screen shoots of your selection, the restored selection and the generated script. I will take a look and if I agree you are right about selection is important and it is not too hard to fix it I will.
When doing this it might be best to generate a menu entry, it makes future selection very easy.
V2.35 is up
Added: Block driver will support socket interface.
Added: Poll delay setting in Block driver (#pollPause)
Fixed: A charset issue with #rxStart in Block driver
2. I also confirm that #pollPause does its job well, provided value should be in milliseconds.
Unfortunately I do not see it mentioned in documentation for the driver https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html#Binary_with_fixed_communication_blocks_(Block)
3. I wonder where to read about "socket interface" ?
Is this about possibility to communicate over a TCP socket in network instead of a serial interface?
Yes, socket is using TCP. There is no special documentation about it, but see here: https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html#The_device_identification_and_connection_parametes. It will be selected if you write a socket port number after the #port tag.
I did not test it when adding the code and somebody says it do not work, it will be tested (and fixed) before next version.
...
Monitoring the lines with a terminal window I can see the responses to Test Controller's commands.
When using socket, the response does not appear to be read into Test Controller so it keeps sending the same command.
I made a minor change to the definition file for the Siglent SDL10xxXxx to do with how the instrument changes modes to CC on connection and locks its front panel, it now won't do that.
V3.26 is up.
Changed: #ChartCurves will select curves in the sequence listed in the command
"V3.26 is up."
I guess this should be - V2.36 is up.
At least the is what the About box says.
There is something changed?
I have used this program before, but today when I try to save the log, buttons "Save" or "Export" does nothing. They are supposed to show a dialog where I can choose to save the log, as I remember ...
There is something changed?
I have used this program before, but today when I try to save the log, buttons "Save" or "Export" does nothing. They are supposed to show a dialog where I can choose to save the log, as I remember ...
Strange, I just tried here and it works as it is supposed to.
Note: Save and Export only works when there are data in the table. They will also be disabled if you are active logging to disk, but will be enabled when you stop logging.
There is something changed?
I have used this program before, but today when I try to save the log, buttons "Save" or "Export" does nothing. They are supposed to show a dialog where I can choose to save the log, as I remember ...
Strange, I just tried here and it works as it is supposed to.
Note: Save and Export only works when there are data in the table. They will also be disabled if you are active logging to disk, but will be enabled when you stop logging.
I know, I have used it many times before. It has data, just wasted 4 hours of logging. After stopping can't save ... I have downloaded last version do a test log, same problem. If you say that should work, maybe is something from Java ...
There is something changed?
I have used this program before, but today when I try to save the log, buttons "Save" or "Export" does nothing. They are supposed to show a dialog where I can choose to save the log, as I remember ...
Strange, I just tried here and it works as it is supposed to.
Note: Save and Export only works when there are data in the table. They will also be disabled if you are active logging to disk, but will be enabled when you stop logging.
I know, I have used it many times before. It has data, just wasted 4 hours of logging. After stopping can't save ... I have downloaded last version do a test log, same problem. If you say that should work, maybe is something from Java ...
The Java I tested with is:
C:\Users\hkj>java -version
java version "1.8.0_231"
Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)
Try running TC from a DOS prompt, it will output error messages to the DOS window. Error messages are always output, debug messages only in debug mode and both to DOS window and to TC log window.
The output at export command is in file attached.