SDS100/SDS200: SDS100 Keypad Enter Button not always registering button presses

[ccsprague]

Anyone else have issues where occasionally their enter button on the SDS100 will click but the scanner won’t respond with a beep?

 

[ccsprague]

Video of issue

 

[Ubbe]

Try to click on the rotary encoder, it should work the same as the enter key. If that works then your enter key are probably worn out. But if the rotary have the same problem then it could be a cold solder joint issue or the scanner are stuck doing other things. The keypad are scanned in a background process and when it detects a button being pushed it sets a flag and waits for the main program to pick up that information. If the main program have problems, maybe struggling to handle a lot of data or have issues reading the SD card, then the whole scanner gets unresponsive.

/Ubbe

 

[ccsprague]

Try to click on the rotary encoder, it should work the same as the enter key. If that works then your enter key are probably worn out. But if the rotary have the same problem then it could be a cold solder joint issue or the scanner are stuck doing other things. The keypad are scanned in a background process and when it detects a button being pushed it sets a flag and waits for the main program to pick up that information. If the main program have problems, maybe struggling to handle a lot of data or have issues reading the SD card, then the whole scanner gets unresponsive.

/Ubbe

Yeah the rotary switch works half the time as well. So guessing it’s a SD card issue. Any way to test the issue to see if it’s a cold solder joint before sending it to Uniden?
This is the MicroSD card currently in it: Amazon: SanDisk 32GB High Endurance Video MicroSDHC Card with Adapter for Dash Cam and Home Monitoring Systems - C10, U3, V30, 4K UHD, Micro SD Card - SDSQQNR-032G-GN6IA

 

[Ubbe]

Any way to test the issue to see if it’s a cold solder joint before sending it to Uniden?

It usually shows in debug file. There's some instructions here at the forum and probably in some of the Uniden Wiki. Record 30 sec while pushing buttons. The debug log are a text file and it will say that it repeats the commands and finally errors out. If no repeated lines can be seen and no error then it's probably something else.

But I can says that I often find myself pushing on the rotary button several times until it finally gets it. So it can be something Uniden have done to balance more CPU power to another function like decoding data from the DSP and the keypad scan then takes the back seat. They have already lower the sampling rate for the debug data collection to half speed and scan rate have also gone down to half speed.

/Ubbe

 

[ccsprague]

It usually shows in debug file. There's some instructions here at the forum and probably in some of the Uniden Wiki. Record 30 sec while pushing buttons. The debug log are a text file and it will say that it repeats the commands and finally errors out. If no repeated lines can be seen and no error then it's probably something else.

But I can says that I often find myself pushing on the rotary button several times until it finally gets it. So it can be something Uniden have done to balance more CPU power to another function like decoding data from the DSP and the keypad scan then takes the back seat. They have already lower the sampling rate for the debug data collection to half speed and scan rate have also gone down to half speed.

/Ubbe

So I found the instructions on this page that showed how to create a debug file. I see it can be read from a text editor but I cannot make heads or tails of it. It's a foreign language to me.

 

[Ubbe]

I cannot make heads or tails of it.

Do a text search for "err" and also "TIME OUT"
If none are found then the data communication thru the connector are fine without any interruptions.

/Ubbe