Button Press Strength

Status
Not open for further replies.

Triangulum

Member
Joined
Feb 24, 2015
Messages
122
Reaction score
0
This is more of a curiosity than an actual concern. If some 536 owners could experiment with this then it would be appreciated. Keep in mind this device was just opened, out the box this past week.

The 5 buttons under the screen are:
Avoid | Replay | System | Dept | Channel

The Avoid button seems to need a more sturdy press to push it a little deeper than the others in order to register. If I lightly press any of the other buttons there, as long as goes in then it immediately registers. I can push the Avoid button in softly and have it not register. It needs that extra bit of pressure to register. It doesn't consistently do this, but I notice it every now and then

Is this normal and more of a safety design or a programming code issue since Avoid is triggering the scanner to continue scanning? Is it a breaking-in issue that will self-correct itself? Does it has more to do with the button being towards the left edge of the device and needing a more direct push since its not at the device's center of gravity? Or is it just a slightly faulty button?
 
Last edited:

troymail

Silent Key
Joined
Dec 19, 2002
Messages
9,981
Reaction score
32
Location
Supply (Lockwood Inlet area), NC
Not sure if it's the same thing or not but under certain conditions, pressing harder/holding longer and/or waiting for digital decode to stop seems to be required to get response to button pushes. This is worse apparently as the SD card gets filled (with recordings, etc.). This is very annoying to me and I'm hoping it will be addressed in a firmware update. I suspect others are hoping the same.

On the other hand, you may just be seeing a defect for that one button.
 

Triangulum

Member
Joined
Feb 24, 2015
Messages
122
Reaction score
0
As mentioned above, its more of a curiosity than a concern. Its something I've noticed on rare occasion.

I am hedging my belief that its a combination of it being towards the left-end edge with less center of gravity and that it will wear-in with usage. Its hard to replicate. Right now I had some success pressing the far right corner and getting it to press/click without registration. But anywhere else its registering. I think its just a matter of the button not being fully pushed and not even a valid curiosity (it was never a concern).

If I have to try this hard to replicate it then I doubt its a real issue. But if anyone wants to experiment then go for it. Try the right edge of the Avoid button.

In other words, I think I may have made a disservice with this thread. I am really enjoying my time with this scanner and would recommend it to anyone observing this who is on the fence.
 
Last edited:

BenScan

Member
Premium Subscriber
Joined
May 12, 2001
Messages
1,054
Reaction score
368
Location
D/FW
I don't believe the buttons work well, both in the physical pressure required and the responsiveness for both the BCD436HP and the BCD536HP. Some of the responsive issue may relate to audio recording and the extra processor power needed to do so much. Basically, the scanner is not designed and built well.

This is more of a curiosity than an actual concern. If some 536 owners could experiment with this then it would be appreciated. Keep in mind this device was just opened, out the box this past week.

The 5 buttons under the screen are:
Avoid | Replay | System | Dept | Channel

The Avoid button seems to need a more sturdy press to push it a little deeper than the others in order to register. If I lightly press any of the other buttons there, as long as goes in then it immediately registers. I can push the Avoid button in softly and have it not register. It needs that extra bit of pressure to register. It doesn't consistently do this, but I notice it every now and then

Is this normal and more of a safety design or a programming code issue since Avoid is triggering the scanner to continue scanning? Is it a breaking-in issue that will self-correct itself? Does it has more to do with the button being towards the left edge of the device and needing a more direct push since its not at the device's center of gravity? Or is it just a slightly faulty button?
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
Some of the responsive issue may relate to audio recording and the extra processor power needed to do so much.

To test that, press them 'normally' and see if they respond after a few seconds.
 

rcool101

Member
Feed Provider
Joined
May 31, 2002
Messages
1,032
Reaction score
230
Location
Eastern Ohio
This is more of a curiosity than an actual concern. If some 536 owners could experiment with this then it would be appreciated. Keep in mind this device was just opened, out the box this past week.

The 5 buttons under the screen are:
Avoid | Replay | System | Dept | Channel

The Avoid button seems to need a more sturdy press to push it a little deeper than the others in order to register. If I lightly press any of the other buttons there, as long as goes in then it immediately registers. I can push the Avoid button in softly and have it not register. It needs that extra bit of pressure to register. It doesn't consistently do this, but I notice it every now and then

Is this normal and more of a safety design or a programming code issue since Avoid is triggering the scanner to continue scanning? Is it a breaking-in issue that will self-correct itself? Does it has more to do with the button being towards the left edge of the device and needing a more direct push since its not at the device's center of gravity? Or is it just a slightly faulty button?
All my buttons work the same
 

AC2OY

Member
Joined
Mar 29, 2011
Messages
2,397
Reaction score
-12
Location
Belleville,New Jersey
On my 536 there is a sweet spot for my avoid button and yes sometimes I miss or don't press it correctly. I would agree with my esteemed colleagues on this one!!!
 

Triangulum

Member
Joined
Feb 24, 2015
Messages
122
Reaction score
0
And just so observers understand, this thread was more of a curiosity than a concern. If I was concerned then I would have just exchanged the unit for another one as its in the return-window. I am not. Its not a problem.
 
Status
Not open for further replies.
Top