Thanks Nick,

Adjusting the range makes no difference. I moved it in small increments from 60 to just about the limit on either side. 


Mike

-------- Original message --------
From: Nick England <[email protected]>
Date: 10/2/21 12:21 PM (GMT-07:00)
To: Mike McAuley <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [GreenKeys] Model 28 with a new problem

What happens when you adjust the RANGE control?

On Sat, Oct 2, 2021 at 3:16 PM Mike McAuley <[email protected]> wrote:
Hmmm, okay I see your point Wayne. Thanks!


Mike

-------- Original message --------
Date: 10/2/21 12:04 PM (GMT-07:00)
Subject: Re: [GreenKeys] Model 28 with a new problem

>what could be causing a MARK to be sent on bit 5 in cases where it should be a SPACE?

Might be asking the wrong question, it might be "what could be causing those bit 5 characters to be decoded & printed incorrectly?"  IOW, the code may be getting sent correctly but decoded incorrectly.  That the characters have a common denominator in the type box sounds suspicious.

Wayne
WB4OGM

-----Original Message-----
From: Mike McAuley <[email protected]>
To: Green Keys <[email protected]>; John <[email protected]>; [email protected]
Sent: Sat, Oct 2, 2021 11:54 am
Subject: [GreenKeys] Model 28 with a new problem

So I got the code bar 3 issue fixed as far as I can tell.  I can see all five code bars shifting back & forth.

But now there is a new issue...

A types as W
E types as Z
I types as P
S types as Y
U types as Q

3 types as quotation mark
7 types as 1
8 types as 0
Dash types as 2
STOP types as hashtag
Spacebar types as H
Line feed types as L

Now I was sleuthing the bit codes for all those keys and from what I see, the common denominator is bit 5.

On those keys, a bit 5 SPACE is being turned into a MARK.  On other characters where bit 5 is *supposed* to be a Mark, they are typing fine.

AND... it's not doing it on ALL the keys where switching bit5 from S to M would change the character.  For example, typing C does not change to V.

I can also see that these affected characters happen to lie in the center four columns on each side of the typebox (middle four for the FIGS section, & middle four for the LTRS section.)

The bit 5 code bar is NOT stuck. I can see it freely running back & forth between M & S.

So the question is: what could be causing a MARK to be sent on bit 5 in cases where it should be a SPACE?

Any thoughts, ideas or suggestions appreciated 


73s

Mike
KD7VRG
______________________________________________________________
GreenKeys mailing list
Home: http://mailman.qth.net/mailman/listinfo/greenkeys
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

>>> Jordan Spencer Cunningham's GreenKeys Search Tool: https://teletype.net/gksearch
>>> 2002-to-present greenkeys archive: http://mailman.qth.net/pipermail/greenkeys/
>>> 1998-to-2001 greenkeys archive: http://mailman.qth.net/archive/greenkeys/greenkeys.html
>>> Randy Guttery's 2001-to-2009 GreenKeys Search Tool: http://comcents.com/tty/greenkeyssearch.html

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
______________________________________________________________
GreenKeys mailing list
Home: http://mailman.qth.net/mailman/listinfo/greenkeys
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

>>> Jordan Spencer Cunningham's GreenKeys Search Tool: https://teletype.net/gksearch
>>> 2002-to-present greenkeys archive: http://mailman.qth.net/pipermail/greenkeys/
>>> 1998-to-2001 greenkeys archive: http://mailman.qth.net/archive/greenkeys/greenkeys.html
>>> Randy Guttery's 2001-to-2009 GreenKeys Search Tool: http://comcents.com/tty/greenkeyssearch.html

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
--
Nick England K4NYW
www.navy-radio.com