East Tester ET4410&ET4510 Desktop LCR Meter

[james38]

When you press "SET" on your device and then the right arrow (down would be more intuitive imho) often enough to reach the second screen, you can set the baud-rate there. Mine is set to 9600 baud and I don't think that I've ever changed it.

Ah ok, yes you are right you can set it in the device.
Hard to find ;-)

But the baud rate was never touched before.
So it was by default on 9600.

But i checked also the original data.ini and there is also an entry for the baudrate.
My be the flash process initiate itself the correct baudrate or checked
the common rates until he gots a response.

The only one that was changed were the Path to the firmware and the comport. Everyting else has not changed.

Regarding the boot loader.
I don't know how it works here but 0xc0 could be enought to tell that the loader is ready.


data.ini
------------------
[Program parameters]
Serial port = COM16
Baud rate = 19200
File directory = C:\Users\PC\Desktop\boot upgrade tool\Program upgrade tool\ET44_V6.00.2405.039.hex
Delay = 1
Delay time = 100

Another observation:
If you check the strings from "data.ini" you find the following:

Code: [Select]

=COM16
=19200
=C:\Users\PC\Desktop\boot
\ET44_V6.00.2405.039.hex
=100
I assume that this configures the update-program to 19200 baud. This may have an influence on the boot-loader-byte in my previous message.

Yes i got the same results as you mentioned.

[JohanH]

I was successful flashing the device in Linux and wine.

I think the issue before was permissions with the serial port.

Before I used an intercepting program (interceptty) to show the communication and forward it to a virtual port, so I didn't really know exactly what worked and not. E.g. the remote control software did work fine on the virtual port while logging the communication.

In the end it worked when I used the native port (/dev/ttyS0) (my motherboard has a serial port). It was assigned as COM1 in wine. But I had to make it read and writeable for all (sudo chmod a+rw /dev/ttyS0), it didn't help that I had group read/write access to the port.

So the tool started working and when resetting the device this time, screen remained black and flashing process started.

Btw, I run the program with the command:

  LC_ALL=zh_CN wine setup.exe

(I had renamed it to setup.exe for simplicity)


End result was:

程序下载完成！
程序下载用时：347秒

(Program download complete!
Program download time: 347 seconds)

There were some errors from the program after this (exception in exe file at address something, but I think it was a wine issue).

After that the device came online with firmware version V6.00.2405.039.

Unfortunately this way I didn't get a log of the serial communication.

I could maybe try to flash it again if nobody else manages to get a log, but I wouldn't want to risk it.

[JohanH]

Btw, I didn't configure the serial port, it has default speeds etc:

$ setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
   Baud_base: 115200, close_delay: 50, divisor: 0
   closing_wait: 3000
   Flags: spd_normal skip_test

Edit.

Looks like the tool was able to change the port speed (?), because the content of the data.ini file is:

[程序参数]
串口=COM1
波特率=19200
文件目录=C:\Firmware\update\ET44_V6.00.2409.049.hex
是否延时=1
延时时间=100

(translated)
[Program parameters]
Serial port = COM1
Baud rate = 19200
File directory = C:\Firmware\update\ET44_V6.00.2409.049.hex
Delay = 1
Delay time = 100


This might have been the issue before, too, that it didn't have permissions to change the speed (speculating now...).

[james38]

I was successful flashing the device in Linux and wine.
After that the device came online with firmware version V6.00.2405.039.

Congrats Johan. 
Yes, I believe that it is not easy under Wine, but you have managed it successfully now. ;-)

Btw, I didn't configure the serial port, it has default speeds etc:

$ setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
   Baud_base: 115200, close_delay: 50, divisor: 0
   closing_wait: 3000
   Flags: spd_normal skip_test

Edit.

Looks like the tool was able to change the port speed, because the content of the data.ini file is:

[程序参数]
串口=COM1
波特率=19200
文件目录=C:\Firmware\update\ET44_V6.00.2409.049.hex
是否延时=1
延时时间=100

(translated)
[Program parameters]
Serial port = COM1
Baud rate = 19200
File directory = C:\Firmware\update\ET44_V6.00.2409.049.hex
Delay = 1
Delay time = 100


This might have been the issue before, too, that it didn't have permissions to change the speed (speculating now...).

Yes, that's what I suspect too, that the program itself sets up the things it needs for the process.

We didn't have to set anything up beforehand.

It was really easy. Set the COM port, select the firmware,
press the button, switch it on/off a bit and you're done.

[Martin72]

I think I actually have a serial problem.
The LCR software works with the USB connection, when I made the RS232 connection it just looked like it was working.
I think I fell for the oldest trick in the book, the serial cable....
What I have is 1:1, I think pin 2 and pin 3 need to be flipped.
I'll do it tomorrow.

[w.v.s.]

This might have been the issue before, too, that it didn't have permissions to change the speed (speculating now...).

Congratulations! As far as I understand, if you have the rights to read and write to a com-port under linux, you can also change the communication settings.

[JohanH]

Congratulations! As far as I understand, if you have the rights to read and write to a com-port under linux, you can also change the communication settings.

Thanks. Yes, I thought that too. My user belongs to the "dialup" group that has read/write access to the com-port. But not until I changed it to world-wide read/write access this program worked under wine.

Now I see that there is the following entry in the SELinux audit log on my Fedora system:

 "avc:  denied  { execheap } for  pid=5456 comm="wine-preloader"

This is probably the reason. It could also explain the other memory errors I saw at the end. A temporary "sudo setenforce 0" would work to enable these security violations in SELinux. And SELinux can permit this with a rule change "selinuxuser_execheap boolean on". However, this means allowing system wide heap memory being executable, which is generally frowned upon and is avoided for security reasons. These old windows programs are doing nasty stuff.

Edit. I think Windows Data Execution Prevention could cause similar problems (in Windows OS) with programs that try to execute heap memory, at least theoretically. DEP is enabled by default, but can be turned off.

[Martin72]

The consistently variable frequency is something that still makes the ET4510 interesting.

Ah,
Saw the ET4510 on Aliexpress earlier, at a very good price.
What can I say, I bought it.
We'll soon find out whether the inner workings of the ET4410 and ET451o differ.

[w.v.s.]

Ah,
Saw the ET4510 on Aliexpress earlier, at a very good price.
What can I say, I bought it.
We'll soon find out whether the inner workings of the ET4410 and ET451o differ.

That are good news for the weekend. I'm looking forward to your posts.

[james38]

I have found a TearDown for the ET4501 on YT (5 Years old)



As far as i can see the PCB from ET4501 differs completely from the ET44xx models.
I suspect that the PCB of the Et4510 will look similar.
The keys are sometimes assigned differently.
Interestingly, the board is called ET44.M.v1.01

I have made some snapshots from the video as good as i can.

Her some pictures.

[w.v.s.]

Interesting, thank you! It might also be possible that early versions of the 4410 were based on the same board. His firmware V1.00.1912.002 made me think if the next to last number in the version was a date code, which might also be plausible with my V6.00.2232.019 (happy new year edition  ) and the new V6.00.2409.039.

Unfortunately, that guy does not seem to be very into digital electronics, so he did not put much attention to the MCU. So now I am even more interested in Martins observations. I would guess that his board looks quite different from the 2019 version.

[pope]

I got a 4510 a few months ago. If (and that's a big if) I find some spare time I will try to take some photos.

But... please remind me if I don't do it within the next couple of weeks or so...

Also, what exactly should I focus on? Once I take the photos and put it back on the self, that'll be it so I should better get it right the first time 

[w.v.s.]

I got a 4510 a few months ago. If (and that's a big if) I find some spare time I will try to take some photos.

But... please remind me if I don't do it within the next couple of weeks or so...

Also, what exactly should I focus on? Once I take the photos and put it back on the self, that'll be it so I should better get it right the first time 

Hello and thank you for that offer! Could you tell us what firmware Version is displayed, when you hit the SET-button? It would also be interesting to know, if your device also shows the list-bug, which was mentioned above.

Regarding the photos: My first focus were the MCU and its direct surroundings and the PCB-Version name, that it printed on the board. Martin had a closer look at his board, so I hope he can add further points here.

[pope]

I got a 4510 a few months ago. If (and that's a big if) I find some spare time I will try to take some photos.

But... please remind me if I don't do it within the next couple of weeks or so...

Also, what exactly should I focus on? Once I take the photos and put it back on the self, that'll be it so I should better get it right the first time 

Hello and thank you for that offer! Could you tell us what firmware Version is displayed, when you hit the SET-button? It would also be interesting to know, if your device also shows the list-bug, which was mentioned above.

Regarding the photos: My first focus were the MCU and its direct surroundings and the PCB-Version name, that it printed on the board. Martin had a closer look at his board, so I hope he can add further points here.

Version is: V6.00.2136.018

Everything else will have to wait a bit 

[Martin72]

When my 4510 arrives, I will take it apart and take pictures of it.
However, I don't think the hardware will be any different.
We'll see soon.

[james38]

If you enter the *IDN? command via SCPI, you will get the SN and FW as well as a hardware version.
It would certainly be interesting to observe that.

I checked this with the "Test Controller" software.

Results with software "Test Controller":
*IDN?
;; ZC,ET4410 ,1072240xxxx ,V6.00.2405.039 V1.12.2103.008

In this case, the version V1.12.2103.008 must be the HW version of the device.

It seems, that "Test Controller" changes the Sequence.

When I use the Software "Messinstrumente" by Peter Dreiseibner
the order of the values ​​was correct as in the SCPI document.

The query returns <Manufacturer>,<Model>,<Firmware>,<Hardware>,<SN>

Results with software "Messinstrumente"
Length of data: 66 bytes
ZC,ET4410         ,V6.00.2405.039,V1.12.2103.008,1072240xxxx 

[pope]

Can someone please explain me how can I use the List scanning function? Say for a capacitor.
I never had the need to use it and the manual is utterly useless.

EDIT: Never mind, I figured it. The values seem to be all over the place...

That's a 10nF film cap

[w.v.s.]

In this case your firmware shows the same bug like the ET4410, for which the fix was provided recently. You could ask your seller for a fix and then we would see if the same firmware is provided for the 45XX. I would guess the answer will be yes.

[james38]

If anyone has ever wondered what this one button with the Chinese character and the question mark means.
This switches you to ECap mode for electrolytic capacitor measurements.

Unfortunately, the character set seems to be wrong here.
I have corrected it. If anyone is interested, they can replace the attached exe file with the existing one.

It was adapted using the Resource Hacker program in the latest version (5.2.7).
You can also make other adjustments to a certain extent if you are familiar with it.

Link:https://www.angusj.com/resourcehacker/

Original:


Adapted :


LCR Programm with the adapted button:
 LCR4X_ENG.zip (347.23 kB - downloaded 10 times.)

[Martin72]

Firmware update:

Somehow I can't get any communication to the device.
Which adapter did you use?
I had been using a TTL to USB...

[JohanH]

I used a regular RS232 female to male cable as my current desktop computer motherboard has a native serial port. The pinout for the ET4410 is in the manual. In the past I've heard about issues with USB-serial adapters. The ones I've used in the past have worked for my purposes, though (Arduino stuff etc).

[james38]

Hi Martin,
my friend who flashed the device used this
USB to TTL adapter (UT-8801) with an FTDI chip.

It works well and without any problems.
All others work too, but in my experience the real FTDI doesn't give any problems.

CP2102 or CH340 may have their peculiarities.
And never use an adapter with PL2303.

[w.v.s.]

Hello,

I've tried a "NULL-modem" connection with 2 com ports, with wine as well with windows 8. I expected the firmware upgrade software to send some command, when i pressed the "\?\?\?" button below the 100ms. But it was silent on the other side of the NULL-modem line. Transmissions from other programs were visible. I wonder, if the software does some additional checks before sending out a command.

[Martin72]

I bought a crossover cable and connected it to the notebook and the ET4410 using a Digitus adapter.
I get a perfect connection between the RS232 port of the ET4410 and the LCR software.
But the firmware program still doesn't work, I don't know what's wrong.
In addition:
I had installed the Chinese language pack, but it still only displays gibberish instead of Chinese characters.

[w.v.s.]

That fits to my observation. My main boards com-port is working fine with wine. ET4410 only connects pins 2,3,5 (verified by resistance measurements). Did only connect my scope to be sure that the handshake lines do not tell that something with more than TXD and RXD is connected. Pushed to button below 100ms and nothing happens on the TXD line. Same port and setup and terminal software instead of firmware upgrade software shows the messages, which I send out, on the scopes screen. Would be nice to be able to read the messages. Maybe it already complains about the firmware file and I don't understand what it says.