Electronics > Repair
Siglent Oscilloscope SDS2104X repair help
<< < (5/6) > >>
marq12345:
Sorry to revive an old thread, but I recently damaged channel 2 on my 1104X-E and a google search brought me to this thread while I was trying to identify components. The trace for this channel was off-screen no matter what I did with gain, vertical offset, or AC coupling. The front-end also has a SOT-23 package marked K52G, which was shorted. Turns out it is actually the input JFET to the discrete amplifier, 2SK508G, but I couldn't easily find it from Digikey etc... so I ordered it from LCSC (Which I think the is parent company of JLCPCB):
https://www.lcsc.com/product-detail/Bipolar-Transistors-BJT_UTC-Unisonic-Tech-2SK508G-K52-AE3-R_C258268.html

After replacing it, the scope seems to work normally again, so this JFET is at least a good enough match. Also, while it was still broken, I attempted a self-cal (which didn't help), and after replacing the JFET, I had to self-cal again for the trace to appear back where it should. Surprisingly, in my case, the two protection steering diodes to 5V and 0V at the input of the JFET are still ok. Hopefully this helps someone in the future.
FringIdeas:
@marq12345, and everyone else with the pics, links, etc, thank you!

I had the same scope, 1104X-E, with the same problem, the trace would not stay on the screen. I found nothing while internet searching the first few times. Then accidentally found this thread. I went and ordered a few 2SK508G-K52-AE3-R from the link. Took about a month to get to me, but I got them. I opened the scope and the K52G did seem to check out bad. So I replaced it with the new part, fired up the scope, did a self calibration, and I got my trace back!! So happy.. so happy..

Thank you for sharing the information!
Deso:

--- Quote from: FringIdeas on September 24, 2024, 08:58:16 am ---@marq12345, and everyone else with the pics, links, etc, thank you!

I had the same scope, 1104X-E, with the same problem, the trace would not stay on the screen. I found nothing while internet searching the first few times. Then accidentally found this thread. I went and ordered a few 2SK508G-K52-AE3-R from the link. Took about a month to get to me, but I got them. I opened the scope and the K52G did seem to check out bad. So I replaced it with the new part, fired up the scope, did a self calibration, and I got my trace back!! So happy.. so happy..

Thank you for sharing the information!

--- End quote ---

Very interesting. Can you share more details?

I have such a problem with my sds1104x-e, but I have no idea how this happens to me (I'm not a novice and this is the first scope in my hands that broke).
One day I was measuring some things and a few days later I came back to update to the latest firmware - V6.1.37R17. After the update I get the very same problem - no waveform on the screen at all. All channels act like that. I have been in communication with the seller and Siglent support, although it is under warranty, it seems that this issue will not be covered. Siglent support provided me with a recovery firmware that downgraded the firmware and I started seeing something on the screen. They don't seem completely dead, as they can measure the calibration signal with erroneous measurements on the screen, but they can't detect lower signals. I use only 2 channels almost all the time, but last time I ended up using only channel 1. I can't explain how all 4 channels stop working at once.

If anyone has any idea what could be causing or fixing this, it would be helpful to me. Thanks!
tautech:

--- Quote from: Deso on November 29, 2024, 10:40:29 pm ---
--- Quote from: FringIdeas on September 24, 2024, 08:58:16 am ---@marq12345, and everyone else with the pics, links, etc, thank you!

I had the same scope, 1104X-E, with the same problem, the trace would not stay on the screen. I found nothing while internet searching the first few times. Then accidentally found this thread. I went and ordered a few 2SK508G-K52-AE3-R from the link. Took about a month to get to me, but I got them. I opened the scope and the K52G did seem to check out bad. So I replaced it with the new part, fired up the scope, did a self calibration, and I got my trace back!! So happy.. so happy..

Thank you for sharing the information!

--- End quote ---

Very interesting. Can you share more details?

I have such a problem with my sds1104x-e, but I have no idea how this happens to me (I'm not a novice and this is the first scope in my hands that broke).
One day I was measuring some things and a few days later I came back to update to the latest firmware - V6.1.37R17. After the update I get the very same problem - no waveform on the screen at all. All channels act like that. I have been in communication with the seller and Siglent support, although it is under warranty, it seems that this issue will not be covered. Siglent support provided me with a recovery firmware that downgraded the firmware and I started seeing something on the screen. They don't seem completely dead, as they can measure the calibration signal with erroneous measurements on the screen, but they can't detect lower signals. I use only 2 channels almost all the time, but last time I ended up using only channel 1. I can't explain how all 4 channels stop working at once.

If anyone has any idea what could be causing or fixing this, it would be helpful to me. Thanks!

--- End quote ---
From what previous version ?

In the install instruction they recommend immediate running of the Self Cal after the FW update.
Did you do this at any time ?
Even after running the recovery package ?

Make contact via PM with your email address and we'll work through getting you all fixed up.
Deso:

--- Quote from: tautech on November 30, 2024, 12:16:20 am ---....
From what previous version ?

In the install instruction they recommend immediate running of the Self Cal after the FW update.
Did you do this at any time ?
Even after running the recovery package ?
...

--- End quote ---

Thank you Tautech.

It was with SW 6.1.37R10 and I upgraded to 6.1.37R17. Of course, I performed a calibration and after not seeing any waveforms, I started "default", "security erase" and all that kind of stuff. I reverted back to SW 6.1.37R10 and followed the same steps, but there were no waveforms at all. Finally, I flashed the recovery firmware and performed a calibration. It started showing waves that were wrong.


--- Quote from: tautech on November 30, 2024, 12:16:20 am ---....
Make contact via PM with your email address and we'll work through getting you all fixed up.

--- End quote ---

Done.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod