BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lou Kolb <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Sat, 15 Jun 2013 19:04:23 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (47 lines)
Mine did it too, Debee.  Not reliably, though so I imagine it's a problem of 
pad key wear.  Great rig, though.
----- Original Message ----- 
From: "Deborah Armstrong" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Saturday, June 15, 2013 6:44 PM
Subject: Kenwood TS-440 question


> Kelvin asked me to do an accessibility review of the TS-440.
>
> I've used mine on and off for several years, and am using mine a lot this
> week.
>
> But, I purchased the thing used, and it has a problem that I'm not sure is
> common to them all or specific to my unit. Don't want to mention it in my
> review if it's just a problem with my rig.
>
> When I enter a frequency or a memory location, using the mode keys which
> double for this function, the keys "bounce". Bouncing is a firmware
> programmer's term for the problem but I'm not sure what the layperson's 
> term
> is. Typematic, perhaps.
>
> Basically, if you touch a key, it sometimes repeats, so touching five 
> enters
> three fives instead of a single five.
>
> I have to be very careful to not hold a key down even for the tiniest
> fraction or it will repeat.
>
> Because this rig was one of the first with a Microprocessor -- I believe 
> it
> was a Z80, they probably didn't do much in its firmware to avoid key 
> bounce.
> But then again, it could be a hardware problem -- sticky keys. I don't 
> have
> the famous Dot problem, but I've been careful to keep it in dry locations.
>
> Anyway, if this bounce annoyance is common to the TS-440 I'd like to 
> mention
> it as an access issue, but maybe my swap meet special is the only rig with
> this glitch.
>
> --Debee [KF6BKR]
> 

ATOM RSS1 RSS2