Products > Test Equipment

New Hantek DSO2X1X models?

<< < (316/388) > >>

DavidAlfa:
You're right. Then there're few options left.
- Corrupted fpga FW file? I don't think so, the buttons wouldn't work either.
- Corrupted filesystem? Maybe... still, rare that only the buttons work.
 (Both would be fixed with platform-tools)

- Defective chips? Still rare, maybe a bad soldering joint.

The encoders common wires are Scan_Data_4 &  Scan_Data_6.
Maybe one of these are bad, or any of the diodes is shorted.

The Scan_Lines are also used for the buttons, so they would also fail if bad.

morgan_flint:
Just read your post, that came up while I was editing mine  :'(

I had checked for continuity between diodes and U2, but I didn't check for shorts on the diodes. Will dismount it again and check.

EDIT: Done, all the diodes are OK. Also checked the connections between U2 and U1, also OK. Tried also some more cleaning and heating around U1 and U2 with hot air. No luck. Time for platform tools

EDIT2: Updated to SW 1.0.2.0.0 (221028.00) FW 3205 with Platform Tools (it was 1.0.1.1.0 (20210726.00) 3202). No luck. Must be a hardware failure (probably U2 or, maybe, U1). I will retouch all solders before trying anything else.

Any other ideas?

DavidAlfa:
Is R109 OK? It's the only thing powering the keypad matrix.

morgan_flint:
Yes, I also checked R109. Although it is common with the rest of the keys, I suspected it could be also the problem because of the forward drop in the diodes (supposing there was a weaker pullup also in the FPGA). But no, it's OK.

Although I had already checked them with the multimeter, I also resoldered relevant pins of U2 (1, 2, 9, 10, 11) and U1 (3, 4, 5), but no luck.

If it's not a SW or FW problem, I can only suspect bad U2, more remotely, bad U1, or, even more strange, a failure in the FPGA section in charge of reading the keyboard.

If I had a longer ribbon cable, I could also try some "live" measurements in the user interface board, but I don't have it.

Unfortunately, without the encoders, the scope is practically useless, but maybe I can still use it with the Keysight application

DavidAlfa:
Do you have access to the serial port? It would be interesting to see the kernel messages.
But you need flash the oldest platform-tools version, the keypad kmod (/dso/etc/fpga_i2c_kb.ko) debugging output was silenced in newer versions.
On rotation you should see a lot of messages like:

--- Code: ---[   22.793724] Get irq key
[   22.818725] Get irq key

--- End code ---

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