Test Equipment ET4410

[Haidry82]

Hi,
I have purchased ET4410 and want to connect it with my computer so the measurement can be recorded. Please let me know the link to download its software. Or, let me know if someone has its software and can share. Thanks in advance!
Ali

[SHTechnics]

As far as I know there's no specific software for the ET44xx. Maybe your version could work with Test controller, but I haven't tested it myself on my ET44 : https://lygte-info.dk/project/TestControllerIntro%20UK.html

[Martin72]

Thanks for the hint, I´ve download it and did a first play.
Will be found, you can control it via PC, must play al little bit more with it, for example read out of values.

Martin

[HKJ]

Will be found, you can control it via PC, must play al little bit more with it, for example read out of values.

TC can do a couple of different readouts:
1) Current value tab
2) Popups readout (Only one value)
3) Popups GridPanel, you can select a couple of different readouts here, use the "Device (tracking) readout, Dual device readout"
4) Adjust scale. Not really a readout, but can be used to check how close a component is to specified value.

[Martin72]

Played against a while, don´t get it to readout.
Remote controling is no problem (although the display of the ET4410 still shows "Local").

[HKJ]

Played against a while, don´t get it to readout.
Remote controling is no problem (although the display of the ET4410 still shows "Local").

That makes me suspect that the protocol changes with software version or model in the ET4410. The definition is based on a ET4401

This can be fixed/added to the definition file, it is a text file, but it requires some work.
The definition use the :FETC? command to get values and units. It then splits it into values and units and uses the units to select columns to show.

[Martin72]

Hi,

Ah ok, makes sense.

but it requires some work.

Indeed, didn´t such things so far, but it´s a good reason to start for.
Below the txt. file of the ET44XX.

[HKJ]

Indeed, didn´t such things so far, but it´s a good reason to start for.
Belwo the txt. file of the ET44XX.

You can try using the :FETC? command from the TC command line.
I believe it is supposed to return: unit value unit value
The units are the ones listed last on the #value lines definitions in the file.

Using =getMode("ET4410") on the TC command line will show what mode TC believes the device is in.

If you just want to see values from the device and do not care about mode/units you can add these two lines to the definition:
#value Value1 _ SI
#value Value2 _ SI
They will make TC ignore mode and show the two first values it decodes from the device, with the current definition it is the 2. and 4. item on the answer line that is decoded as a value.

[Martin72]

Hi,

You can try using the :FETC? command from the TC command line.

This I´ve done it a few moments ago and that works.  (3.9mh coil as DUT)
Interesting things, I´ll examinate this further in the next days.

Martin

[HKJ]

Hi,

You can try using the :FETC? command from the TC command line.

This I´ve done it a few moments ago and that works.  (3.9mh coil as DUT)
Interesting things, I´ll examinate this further in the next days.

You can get this working by removing the #askValuesReadFormat xsxs line and using the two #value lines above.

But it would be much better if you can find a command the returns the unit/mode of the meter. It will have to be used together with the :FETC? command (With a ; between) and the #askModeMathFormat and #modeFromValue will have to be adjusted.

I have no idea if it is different software versions or different models that is the reason for the difference in response, as you can in the file it was not me that made it, I do not have this meter.

[Martin72]

I´ll test and "investigate" it in the next days/weeks, post the results here.
The ET44XX file came from the user DefPom:

https://www.eevblog.com/forum/testgear/east-tester-et4410-desktop-lcr-meter/msg4003669/#msg4003669

[Martin72]

Hi all,

I've simply asked East Tester, if there is a software avaible and/or a list of the used scpi commands.
And got now both..
Software is in chinese, nevertheless I'll try it in the evening.
Martin

[Martin72]

Hi,

Hm-hm....

The software is a kind of mystery for me, it won´t be displayed proper, also it seems it couldn´t find my LCR...
Would upload the zip. file, but it got to much memory (9.1MB).
But what I can upload are the list of the scpi commands...

[sage]

First of all, thanks so much for this software! I have been using the NI-VISA based PyVisa before for controlling instruments, but this National Instruments stuff is crashing and freezing randomly since years, which is very frustrating.

I bought one of those ET4410 LCR Meters as well and find it quite nice actually. I downloaded TC and could gain control to the instrument. However, I am running into similar issues like Martin72. I can send the :FETC? command and it nicely returns the values of what I have set. Perfect. But now, how can I log these values and create a chart?

[HKJ]

I bought one of those ET4410 LCR Meters as well and find it quite nice actually. I downloaded TC and could gain control to the instrument. However, I am running into similar issues like Martin72. I can send the :FETC? command and it nicely returns the values of what I have set. Perfect. But now, how can I log these values and create a chart?

In the new versions of TestController you can use ParamSweeper to sweep frequency and if you checkmark "log" it will also log the sweep frequencies.

[w.v.s.]

Mine is from "MUSTOOL" with a "FREG" button, but seems to have and updated, not fully compatible firmware. It identifies with:  ELEC,ET4410         ,V6.00.2232.019,V1.12.2103.008,...

[HKJ]

Mine is from "MUSTOOL" with a "FREG" button, but seems to have and updated, not fully compatible firmware. It identifies with:  ELEC,ET4410         ,V6.00.2232.019,V1.12.2103.008,...

You can probably still use it with TestController, you just need to edit the #idstring line

[w.v.s.]

You can probably still use it with TestController, you just need to edit the #idstring line

Thank you! I actually did that before the post above. It was then recognized, but I got some error messages, because it returned measurement data, while TC expected a mode. This seems a bit surprising, because the relevant behavior is consistent with most of the SCPI-command list provided by Martin72. The VERSION? command throws an error with my unit.