East Tester ET4410&ET4510 Desktop LCR Meter

[w.v.s.]

If someone tries to update his device, it would be great if he could log the serial communication with the device during the update process!

[james38]

Hi,

here an update.

A friend of mine contaced Bangood directly via email for an official Update for the ET4410.
They reacts immediately and sent him the update and a video with an howto (chinese).
It was the identical as from the other blog site.

He flashed two ET4410 successfully.
One is a Musttool and one was an East-tester (mine one).
By the way the East-tester has kept its logo in contrast to Musttool where there was none anyway.

@w.v.s
Sri he has no capability to trace the Update via RS232.

Use at your own risk!

You only need the Flash-tool itself and you must not register the MSCOM.
Copy the folder with the Flash program (6 files) in a separate folder with no chinese signs in foldername.
This makes trouble. Check if you can start and close the program!
If this works everything is ok.

The screenshots below are from the video that was sent.

Hint: The device must on before you start the program.

1. Update only works via RS-232 so you have to use your USB<->RS232.
    Do not use the Handler Port.


2. The tool must be started with admin rights.
    It is the only exe in the folder. (程序升级工具.exe)


3. Then select Com port


4. Then select firmware file.



5. Then press the first button below the number with the 100ms.


6. The program now waits for the et4410 to be switched off and on again.
    After switching it back on, the screen remains black.


You now see something about Flash in the update program and a few strange characters.
But the upload counter in % at the bottom is important.
Here you can see when the flash process has finished.



When the flashing process is complete, the ET4410 will restart automatically.
This takes a few minutes.


If everything goes well you will see the screen.

Use at your own risk!

Added:
Hint: The device must on before you start the program.

Contrary to the version in the file name, the correct version that is inside is: V6.00.2405.039

[james38]

To get readable colors under Win10 for the program LCR4X_eng.exe only delete the LCR4X_ENG.exe.manifest and you will get better colors.
For me it works.

[Martin72]

Do you know what will be changed with the firmware update?

[james38]

Hi Martin,

yes of cause. There was a Bug in the List Scan mode.
When you measured in this mode you get incorrect values which make no sense.

After the Update everything works fine.
More is not known.

[pope]

Will this also work for the 4510?

[james38]

Well,
the user w.v.s has examined a little the Firmware and found the following strings in there:
4401
4402
4410
4501
4502
4510

It seems to be that this FW is also for the 44x and 45x models but there is no official statement about it that it is also for other Models like Et4410.
We asked only for the ET4410.
So I can only say that it works for the et4410.

The firmware filename is named ET44_V6.00.2409.049.hex
The prefix ET44 suggests that it probably only applies to the et44xx models.

By the way do you have the ET4510?
We are interested in Hires Pictures from the Board to compare them with the ET4410. Is it possible, that you can provide some pictures?

[james38]

I was a little suprise as i wrote the above message.
The firmware file is called : ET44_V6.00.2409.049.hex

I then looked at the FW in the Device and see: V6.00.2405.039
Thats the identical value which w.v.s has found.
It seems they have misspelled the file name.

Code: [Select]

ELEC
 V6.00.2405.039
 %s,%s,%s,%s,%s
)FhF
)FhF
Contrary to the version in the file name, the correct version that is inside is: V6.00.2405.039

[w.v.s.]

It would be also interesting to see what firmware was provided, when someone (best would be a 45xx owner) asked the manufacturer or distributor for an update for the 45xx series. I would expect that frequency selection is a matter of software only, but levels/offset might involve a hardware variation. Right now, I would guess the 44xx and 45xx might have identical main pcbs. But that might be a bit too optimistic, because the print on Martins pictures says "ET.44.M.V1.31".

[Martin72]

The consistently variable frequency is something that still makes the ET4510 interesting.
The list function would be a great addition, if only it didn't have so few lines.

[Martin72]

5. Then press the first button below the number with the 100ms.

This produces a message that I cannot interpret.

[w.v.s.]

Is your computer prepared to display Chinese text? And would you mind logging its serial communication during the update?

[JohanH]

I got a new serial cable and now the software for remote control worked also in Linux.

I used interceptty to monitor the serial traffic. Remote control seems to work.


I tried the firmware update also. I had to install some Chinese fonts to make letters show.

I also had to install and register MSCOMM32.ocx.

It seems to work half ways, it detects the ET4410 and requests me to reset it:

请复位设备...  (Google translate: Please reset your device...)

And the serial communication repeats these characters:

<  7a 1b 42 54 39 36 05 7a 1b 42 | z BT96 z B
<  54 39 36 05 7a 1b 42 54 39 36 | T96 z BT96
<  05 7a 1b 42 54 39 36 05 7a 1b |  z BT96 z
<  42 54 39 36 05 7a 1b 42 54 39 | BT96 z BT9
<  36 05 7a 1b 42 54 39 36 05 7a | 6 z BT96 z
<  1b 42 54 39 36 05 7a 1b 42 54 |  BT96 z BT
<  39 36 05 7a 1b 42 54 39 36 05 | 96 z BT96


During resetting, I see different characters in the communication that repeat also:

<  05                            |           
>  7b 02 00 00 00 00 80          | {         
<  7a                            | z         
>  7a                            | z         
<  1b 42 54 39 36 05             |  BT96     
>  1b 00 00 00 00 00 00          |           
<  7a                            | z         
>  00                            |           
<  1b 42 54 39 36 05             |  BT96     


But after reset, the device boots up normally and it starts showing the same communication and still asks me to reset:

请复位设备... (Google translate: Please reset your device...)

I'm not sure what the second button in the firmware update tool is supposed to do. Says something like "resume download" possibly?

[Martin72]

Is your computer prepared to display Chinese text? And would you mind logging its serial communication during the update?

I had downloaded and installed simplified chinese language (windwos10), but that doesn't help, it stays like this.
I have a connection to the ET4410 via 232-USB, which also works.
But the update tool, I don't know how to proceed.

[james38]

I'll summarize the update process here again.

Hint: The device must on before you start the program.

1. The tool must be started with admin rights.
2. Then select Com port
3. Then select firmware file.
4. Then press the first button below the number with the 100ms.

6. The program now waits for the et4410 to be switched off and on again.

    After switching it back on, the screen remains black.
    You now see something about Flash in the update program and a few strange characters.
    But the upload counter in % at the bottom is important.
   Here you can see when the flash process has finished.

When the flashing process is complete, the ET4410 will restart automatically.
This takes a few minutes.


If everything goes well you will see the screen.

##################################################

@martin72
When you have presses the Button under 100ms

You must Turn the Device off and on to start the Flashprocess.
Then have a look at the Bar Graph on the Bottom which rises from 0% to 100%
The device restarts automaticaly when ist was finishied.

It is important that the communication works via the selected Com port.

Added:
Hint: The device must on before you start the program.
Contrary to the version in the file name, the correct version that is inside is: V6.00.2405.039

[Martin72]

Hi,

1. The tool must be started with admin rights.
2. Then select Com port
3. Then select firmware file.
4. Then press the first button below the number with the 100ms.

And then the message appears and then nothing more.
After this message, I switched the device off and on again, but it starts normally.
Serial communication is OK, as mentioned earlier.

[james38]

Hi Martin,

yes you are right you have mentioned it.
sri, I overlooked that. ;-)

Is this the only connection which is connected or do you have USB also plugged in?
Which RS232 Port du you have taken?
The bottom one is the right one don't use the handler port.

The blog says that the update only works via RS232, not via USB.
My best friend who flashed the device used also the RS232 with an USB to RS232 Adapter.

[Martin72]

Hi,
The connection to the PC is made via the RS232 socket on the ET4410, then via the RS232 to USB adapter on the PC.
The correct port is active, I have tested the connection using the LCR software and it works.
Then I called up the firmware utility, loaded the firmware, then pressed the button - and then this message appears.
And as long as I don't know what it says, I can't react accordingly.

[james38]

Hi,

I just set the locale to traditional Chinese in a virtual machine so that I could identify the message. (see pictures)

As I expected, there seems to be a problem with the serial connection.
That is exactly what the pop-up says.

[w.v.s.]

I get the same message when I start the tool with wine. It is independent on the com-port and firmware file selection. So the error seems rather basic. In parallel, wine prompts something like

Code: [Select]

0024:err:ole:com_get_class_object no class object {648a5600-2c6e-101b-82b6-000000000014} could be created for context 0x5
Did you run it on the same windows-version? Maybe in some cases you also need to install the other stuff, which was provided in the zip-archive? Did you execute it with admin-rights? You could also test if
a) something is sent out on the selected com-port when you push the button and
b) the device sends something on the com-port when it is turned on.
You could also check if your device was configured with the same baud-rate.

[james38]

@martin72
There are two possibilities that come to mind as to what the problem could be.
As I can see from your picture, you have it running directly on the desktop.

Please use a separate folder on drive D: or something like that. This can be problematic, especially when it comes to Windows rights.

The other thing is that the device has to be on before starting the software.

I think the software is asking for something briefly here.

[james38]

Did you run it on the same windows-version? Maybe in some cases you also need to install the other stuff, which was provided in the zip-archive? Did you execute it with admin-rights? You could also test if
a) something is sent out on the selected com-port when you push the button and
b) the device sends something on the com-port when it is turned on.
You could also check if your device was configured with the same baud-rate.

The MSCOMM32 is not needed here.
As far as i know it is already part of Windows and if it were not installed, you would not be able to select a COM port in the program.
I think it is only included for the sake of form for very rare cases.

to a)
And yes, when the button is pressed, the program asks once
via the COM port  if any device is reachable.
Therefore, the device must also be on when the software is started.

to b)
Yes, when the device is restarted, a bootloader seems to be active for a short time that is responsible for the firmware upload.
The program already listens, recognizes the signature and then starts to upload the firmware.

The baud rate is determined by the program, there is nothing you can adjust.

[w.v.s.]

The baud rate is determined by the program, there is nothing you can adjust.

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.

[w.v.s.]

to b)
Yes, when the device is restarted, a bootloader seems to be active for a short time that is responsible for the firmware upload.
The program already listens, recognizes the signature and then starts to upload the firmware.

Did the test. Boot-loader doesn't talk much. Seems to send a single byte (0xC0) when the device is turned on.

[w.v.s.]

The baud rate is determined by the program, there is nothing you can adjust.

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.