Finally, I tested whether it was due to my device - it's not, Testcontroller finds it without any problems.
Hm,
You also have a com port displayed, but the program can't find anything for me...
Which OS do you have? I am running Win10.
When starting the program, I can select any COM port.
Windows 7 x64 v.6.1.7601
Windows 7 x64 v.6.1.7601
Aha...

@All:
If I use the compatibility mode for win7, then it works!The colors in the illustration are somewhat unfortunate, perhaps this can be changed.
But it works perfectly and the ET4410 is recognized and displayed without any problems.
Got the program working in wine after "winetricks allfonts". Set a COM1 port in the registry.
Still can't access the device. I can select COM1 in the program.
I can't find any specs if it requires a specific port speed. Tried also swapping RX and TX on the cable but no go.
This is how my program looks like (at least mine shows more contast

):
Left plot is time series for primary measured value, next to it a histogram of that value.
First line: Time, last measured primary value, average and standard deviation.
Second line: Selection of primary unit, measured secondary value, real part of impedance, imaginary part of impedance.
Third line: Selection of secondary unit, frequency.
Not the best C++ coding style. Currently running with 22.04.1-Ubuntu. Also talks with GPIB, LXI, and some USB devices.
but man i hate all the black thingy / fashion / trend, way too hard to see, use light gray instead, if your room get too dark or darker in a sense, you loose the contrast effect and almost see nothing ??
black is not for me loll even on instruments front panels ...
kudos
Aha... 
@All:
If I use the compatibility mode for win7, then it works!
The colors in the illustration are somewhat unfortunate, perhaps this can be changed.
But it works perfectly and the ET4410 is recognized and displayed without any problems.

Why does your interface look prettier than mine?
I have a question mark after the value "ROUT".
All the selection fields are curved, the colors are also different.
And I can't change the value of the "ROUT" value, there are 100 and 30 ohms, I can choose but they don't change on the device, it always shows 100 ohms.
Hi,
Why does your interface look prettier than mine?
No idea, I´ve changed nothing.
I have a question mark after the value "ROUT".
And me a "0" instead of

, makes ist not better.
And I can't change the value of the "ROUT" value, there are 100 and 30 ohms, I can choose but they don't change on the device, it always shows 100 ohms.
Now you´ve mentioned, same here...

I have examined the exe file with
Uni-Extract, the LCR programme itself is written in Delphi, perhaps something can be changed/corrected there.
This software looks pretty hopeless to me
So as they are built right now, what's capping the max frequency at 100kHz ? Say you wanted to extend it to 1 or 10MHz, would much have to be added or changed ? Someone would have to hack the MCU or whatever's in itm to add the extra range.
I'm interested in trying that with my LCR meter, but I'm over my head with the MCU.
So as they are built right now, what's capping the max frequency at 100kHz ? Say you wanted to extend it to 1 or 10MHz, would much have to be added or changed ?
It won't work that easily.
I had drawn a part of my ET4410 as a circuit diagram and if I remember correctly, the circuit corresponds exactly to the one on the left side(lower corner) of this picture:

For frequencies above 100kHz it becomes much more complex, simply increasing the frequency is not enough, the whole circuit has to be adapted/replaced.
It's not worth it.
On the contrary, I started with the circuit diagram to find out how to optimize the existing circuit so that it works up to 100kHz, because I have my doubts that it does.
Edit: Pic taken from the Impedance Measurement Handbook (Agilent):https://wiki.epfl.ch/carplat/documents/rcl_agilent.pdf
Did a small face lift on my ET4410. Might appear boring, but I did not like the look of that orange

Proper red would also be acceptable but was not on stock.
Received the ET4410
Internals are basically the same as the ones Martin posted other than the micro. Instead of STM32F103 we have a more powerful N32G455. Though the meter is probably running the same code for the most part. The UI front panel uses N32G457.
Parts seen:
-
N32G455 144MHz 32-bit 5MSPS ADC, 1MSPS DAC
-
SGM3003 analog switch
-
MS8052M high speed 5V 250MHz op-amp
The factory CAL routine mentioned above (hold SET when powering on) requires: 1.4k, 4.64k, 15k, 47.5k, 174, 25.5, 6.81, 2.05, and "standard impedance" whatever that is.
To disassemble:
- Remove two large philips head screws at the back of the case
- Remove the tilting bale by rotating it, then pop out
- Sheet metal case will slide off
edit: jlink can connect to the N32G455RE, but of course the flash is locked so no easy way to read it out.
Received the ET4410
Internals are basically the same as the ones Martin posted other than the micro. Instead of STM32F103 we have a more powerful N32G455. Though the meter is probably running the same code for the most part. The UI front panel uses N32G457.
If your device is still open: Did you look if there is any activity on the through-holes for the front-usb, where no connector is mounted?
If your device is still open: Did you look if there is any activity on the through-holes for the front-usb, where no connector is mounted?
There is an unpopulated connector JP2 + U10 at the top, presumably goes to the GPIB connector on the back. JP3 is SWD port. Then JP5 which is right above the USB hole, has 5V, Gnd, then two other pins that presumably go to the 32G457 OTG port. But there is no activity or voltage on the two middle pins, so I don't think any connection is implemented in the software its running.
For whatever reason HPOT output has some distortion on it whereas HCUR signal does not. I guess when they are connected its normal so it doesn't matter?
Output is:
- 2V at 10kHz and 1.8V at 100kHz with no load.
- 0.67V and 0.57V with 50R load.
If your device is still open: Did you look if there is any activity on the through-holes for the front-usb, where no connector is mounted?
There is an unpopulated connector JP2 + U10 at the top, presumably goes to the GPIB connector on the back. JP3 is SWD port. Then JP5 which is right above the USB hole, has 5V, Gnd, then two other pins that presumably go to the 32G457 OTG port. But there is no activity or voltage on the two middle pins, so I don't think any connection is implemented in the software its running.
Thank you for checking this!
For whatever reason HPOT output has some distortion on it whereas HCUR signal does not. I guess when they are connected its normal so it doesn't matter?
Output is:
- 2V at 10kHz and 1.8V at 100kHz with no load.
- 0.67V and 0.57V with 50R load.
HPOT and LPOT are LCR Meter Signal High Z Sensing Inputs, HCUR is the Drive Signal Output Source and LCUR is the Drive Signal Sink, usually at virtual ground as forced by a Transimpedance amplifier.
Best,
Hi,
i have found an interesting Blog where some tells about an Issue in the Scan-List with the ET4410
and that he got an FW Upgrade.
It is in chinese so you must translate it via Google.
https://blog.zeruns.tech/archives/774.htmlThe Url for the Upgrade is pan baidu but there ist also
an alternate URL on the page where you can download it without pan baidu.
https://www.123pan.com/s/2Y9Djv-ZCcvH.htmlI have not tested it but maybe its interesting for someone.
I've tried to decode the hex-file, assuming that the :10 lines contain 16 bytes of data each and
have a 211392 bytes binary file now. It may not be correct, yet. But it does not seem to be encrypted, because I see familiar strings:
ET4510"X
,A/x
PARAMETER)
MODEi
STAT))
P<LIS
list
LEVEL
VOLTAGz)
OURC
VERSIONx
REMOTP
LOCA
FAI'
9(?b
IMMEDI,
BEEPER)
TNSYSTECy
4(x
COMVALU
AUTO
RANGu1)
EQUI
IMPEDANC
DEVi
FUNCTION
I was also glad to the "ET4510" string in the ET4410 firmware. I am guessing, that the target location for that data might be 0x8004000. The :02 seems to give the coarse location of a block and the characters 4 to 7 of the :10 the fine address within that block.
In the meantime, I've learned that this is a intel format for hex-files and well documented. So not much need for guessing here.
SYSTEM
4401
4402
4410
4501
4502
4510
these are used for some switch/case:
;-- switch:
│ 0x08015584 dfe800f0 tbb [0x0801558c] ; switch table (6 cases) at 0x8015588
0x08015588 .char 3
0x08015589 .char 8
0x0801558a .char 13
0x0801558b .char 18
0x0801558c .char 23
0x0801558d .char 28
│ ;-- case 0: ; from 0x08015584
│ ; CODE XREF from fcn.0801556c @ 0x8015584(x)
│ 0x0801558e 19a1 adr r1, 0x64 ; "4401"
│ ; 0x80155f4
│ 0x08015590 01a8 add r0, var_4h
│ 0x08015592 eff73ef8 bl fcn.08004612
│ ┌─< 0x08015596 18e0 b 0x80155ca
│ │ ;-- case 1: ; from 0x08015584
│ │ ; CODE XREF from fcn.0801556c @ 0x8015584(x)
│ │ 0x08015598 18a1 adr r1, 0x60 ; "4402"
│ │ ; 0x80155fc
│ │ 0x0801559a 01a8 add r0, var_4h
│ │ 0x0801559c eff739f8 bl fcn.08004612
│ ┌──< 0x080155a0 13e0 b 0x80155ca
│ ││ ;-- case 2: ; from 0x08015584
│ ││ ; CODE XREF from fcn.0801556c @ 0x8015584(x)
│ ││ 0x080155a2 18a1 adr r1, 0x60 ; "4410"
│ ││ ; 0x8015604
│ ││ 0x080155a4 01a8 add r0, var_4h
│ ││ 0x080155a6 eff734f8 bl fcn.08004612
│ ┌───< 0x080155aa 0ee0 b 0x80155ca
│ │││ ;-- case 3: ; from 0x08015584
│ │││ ; CODE XREF from fcn.0801556c @ 0x8015584(x)
│ │││ 0x080155ac 17a1 adr r1, 0x5c ; "4501"
│ │││ ; 0x801560c
│ │││ 0x080155ae 01a8 add r0, var_4h
│ │││ 0x080155b0 eff72ff8 bl fcn.08004612
│ ┌────< 0x080155b4 09e0 b 0x80155ca
│ ││││ ;-- case 4: ; from 0x08015584
│ ││││ ; CODE XREF from fcn.0801556c @ 0x8015584(x)
│ ││││ 0x080155b6 17a1 adr r1, 0x5c ; "4502"
│ ││││ ; 0x8015614
│ ││││ 0x080155b8 01a8 add r0, var_4h
│ ││││ 0x080155ba eff72af8 bl fcn.08004612
│ ┌─────< 0x080155be 04e0 b 0x80155ca
│ │││││ ;-- case 5: ; from 0x08015584
│ │││││ ; CODE XREF from fcn.0801556c @ 0x8015584(x)
│ │││││ 0x080155c0 16a1 adr r1, 0x58 ; "4510"
│ │││││ ; 0x801561c
│ │││││ 0x080155c2 01a8 add r0, var_4h
│ │││││ 0x080155c4 eff725f8 bl fcn.08004612
│ │││││ 0x080155c8 00bf nop
ELEC
V6.00.2405.039
%s,%s,%s,%s,%s
)FhF
)FhF
0Hz
10Hz
30Hz
100Hz
120Hz
200Hz
400Hz
800Hz
1kHz
2kHz
4kHz
8kHz
10kHz
15kHz
20kHz
30kHz
40kHz
50kHz
80kHz
100kHz