Startup Rigol 1052E

[GGMM]

Hello,

I put aside the broken switch problem.
The oscilloscope starts but seems to "crash" afterwards after 4/5 s of boot (see pictures) .
An idea before I show it all.
Memory? Pb update or failed upgrade attempt  --->100mhz?


Some useful information:
http://rigol.codenaschen.de/index.php/Schematics
https://www.pascalchour.fr/mesures/rigol_ds_1052e.htm

cdt

[GGMM]

You can see this link. Part of the schematic has been rewritten. Thank you

https://www.eevblog.com/forum/repair/rigol-ds1052ds1102-schematic-diagrams/msg4095688/#msg4095688

[GGMM]

For information, I could still access the MENU during the 4/5 seconds of operation. After that, it crashes.
So all is not so bad. LOL

I think pb of memory at 90%
your opinions

I have a 2nd digital oscilloscope that works well now. I will be able to look a little deeper if it is accessible.
cdt

[GGMM]

Hello,

Before I showed up this afternoon, I did some more research
an interesting post
https://www.jackenhack.com/rigol-ds1054z-oscilloscope-hangs-boot/
Well, I have to find the button in question for the 1052nd
If someone has the solution before I dive into the documentation
It costs nothing to test

Also this link, but more connectors pbs


I will also disassemble the power switch and find a transitional solution

to be continued.....

[GGMM]

also another track to see
Chemical capacitor leak (on power supply or motherboard)?

soon the rest of the show LOL

[GGMM]

re,

I checked the power supply, apart from the switch which is broken, the voltages are good in charge.
On the motherboard, we see that there was an attempt to repair or control. A circuit seems to have been cut a little.
I will check this. Its origin is flawed, but there is a video on youtube that gives an indication.



see 2mn 09s

cdt

[GGMM]

re,
I completely disassembled the oscilloscope.
It is easier to see the components and possibly test flat.
Well, I don’t know why, there was a beautiful short circuit on the USB port welds, but the pb should not come from there.
We see on the underside, the other 2 converters, which the video confirms, but I do not think that the crash comes from there.

I do not know if tests exist that could be charged by the USB port to test the motherboard or via the serial port.
If you have that I’m taking it.

cdt

[GGMM]

Re,
I would like to anticipate a procedure for complete reinstallation of the firmware, often it is an update and so we proceed on an oscilloscope that "Run"

1.Copy .RGL file to the root of USB flash
2.Power on DS1000E/D/U, insert USB into DS1000E/D/U, there will be a note that find a new firmware whether to update. Press update button
3. After finish update ,reboot and check the version
Note: Do not power off the instrument or move the USB flash during the updating.

But as mine crashes after 5s , I would like to know if there is a procedure to reinstall the firmware of zero. As if we had a new, blank motherboard.  (there may have been an attempt gone wrong, it’s just a suposition)
Help!
Thank you

[GGMM]

re,

I did some more tests this afternoon
I prepared a USB key to reinstall the firmware
When I install the key and I turn on with the save key pressed, the oscilloscope recognizes the USB key and proposes the installation.
But as it crashes after 5 s, we can not go further.
This proves once again that the functions work, but a malfunction of a component makes that one does not go far.
I looked at the memory, it seems that this one is an H57V2562 GTR 75C
Il have to confirm, because since there was a sticker, it is difficult to see and if you put too much cleaner it may erase.
So in case anyone could confirm.
I’ll look tonight under a microscope

cdt

[GGMM]

hello,

ay you give me a little help on my subject to see more clearly.


So, I better identified the memory. This is an H57 1262GTR 75C.

I also read on the forum and started reading also this post
https://www.eevblog.com/forum/blog/the-dark-side-of-the-rigol-hack-bricked-scope-how-to-fix-it/msg18086/#msg18086

On the Rigol I’m trying to troubleshoot, the firmware is 00.02.01 SP1

First may you tell me what is this version (Old official or other)

2nd) If there was an attempt to upgrade or switch to 100MHZ that failed, does my failure symptom match? (see beginning of the post)
From what I’ve read, there are more calibration pbs.


So, me for now I guess the RAM out. (?)

Thank you for your answers (NB: I had none since the beginning of the post)
cdt

[iMo]

I would re-solder that pins on the chip above. Looks like the chip has been replaced and the pins were shorted during their soldering attempts, thus they tried to remove the shorts between the pins/pads with a sharp something. Do use a lot of flux and no additional solder.

[GGMM]

iMo,

The chip which would appear to be tinkered, is a chip that acquires AD9288 (one of the 3 on the upper side of the board)
 Of course, I re-checked the welds and removed the short circuits.
This should not prevent it from working.
I don’t have the history of what was done on this scope.

That’s why my two questions are important and need an answer.
For me, the crash does not come from there, it's other.
cdt

[GGMM]

I read that  Drieg was an expert on this subjet.
Do he still answer that,

cdt

[GGMM]

I will still do a test with Hyperterminal
on the USB port. Simply to see if the link is broken or not when the oscilloscope seems to crash.


Ex: See the version, model...

*IDN? ---> never do enter, but touch Alt 010 after the command!
Command Format:
*IDN?
Function Explanation:
The command queries the ID character string of the instrument, including a field
separated by 4 commas: manufactory, model, serial number and the version
number composed of numbers and separated by “.” .
Returned Format:
RIGOL TECHNOLOGIES,<model>, <serial number>, <software version
number>.
Example:
RIGOL TECHNOLOGIES,DS1102E,DS1EB104702974,00.02.01.01.00

[GGMM]

re,

Apparently during the 5 seconds where the oscilloscope starts before crashing, I have the hand with a hyper terminal

The *IDN? command seems to work and sends me some information. (The serial number has been erased)

So it’s always the same story, as long as it works, all commands are OK

Any ideas for you? Are there no more Rigol specialists here?

I ordered the RAM in case.

cdt

[GGMM]

Well, I take everything back to zero
We will start from the beginning and identify the equitete that was stuck (Fortunately I had made a picture, I wanted to see the reference of the components)

For you this corresponds to what?
Hardware version?
Firmware version?
Model?
Which firmware is the most recent i can use?

As I said before, I don’t have the history of what was done. So you can imagine, even a motherboard change.

thank you for your answers