Products > Test Equipment

New Hantek DSO2X1X models?

<< < (315/388) > >>

dirtmover:

--- Quote from: laserdyne.rd on August 22, 2023, 11:10:11 pm ---
--- Quote from: DavidAlfa on August 18, 2023, 03:13:54 am ---Yes, it's damn annoying!

--- End quote ---
Is there a pathway to report this and get it fixed? It is literally a blocker for us using this scope. It's great otherwise.

--- End quote ---

You can try reporting at https://www.eediscuss.com but don't expect action any time soon, if at all!

aleph0:
ty dirtmover. I notified them here https://www.eediscuss.com/forum.php?mod=viewthread&tid=17977 but nothing yet. Not holding my breath...

morgan_flint:
Hi DavidAlfa and all,

Today I connected the scope after a long time without using it. To my surprise, I found none of the rotary encoders give any response!

Entered in UTILITY/FrontPanelSelfTest and checked that all the buttons work OK, but none of the rotary encoders.

I tried a factory reset (both Keysight application and serial console), but still the same.

Looking at the schematics, I see the signals for the buttons and encoders share the same path in the ribbon cable, so I don't think the problem is there. I suspect then it could be SW or FW corruption. Probably, FPGA's FW, as the FPGA is controlling the user interface, if I remember well.

I have backups done with David's Backup Builder. Do you think restoring with dso3kb_CN2149029XXXXX_FPGA.upk could be the solution? Or is better to take the opportunity to update everything to the lastest versions? (I never updated SW or FW)

PD: I tried to restore with dso3kb_CN2149029XXXXX_FPGA.upk but can't do it as without the rotary encoder it's not possible to select the update from the directory... I'm afraid I'll have to restore in FEL mode

DavidAlfa:
Having a backup, try platform-tools.
Or reseating the ribbon cable just in case, doesn't take much work.

morgan_flint:
Ok, thanks.

Now I'm waiting for another backup with DSOFlash to end, just to be sure before starting anything.

I'll take a new look at the ribbon cable, but I don't think that is the case, as the pushbutton signals travel through the same path as those of the encoders (see attachments).

The yellow signals go to the ribbon cable, the green ones correspond to pushbuttons (including those in the encoders, at Scan_Data_5), and the red ones to the rotary part of the encoders. If there's a bad connection, it should be between the encoders' diodes and U2, and to see that I have to take apart the display, a bit more complicated than accessing the main board, but I'll do it when the backup ends.

BTW, I've had problems with the FEL driver in this PC, followed all the instructions but DSOFlash gave an error. I've done the same on another PC and it's going OK.

EDIT: Backup finisher, took apart the display and reseated the ribbon cable. Also, checked with the multimeter continuity from all the diodes' anodes to pins 1 and 2 of U2. All correct. I also took the opportunity to clean the board, which had a lot of flux residues (I thought it could have been the culprit, if these residues had become conductive with humidity, for example). But no luck. I'll try platform tools

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod