[Coco] CoCo Keys2USB - Problem

[edward jaquay]

The latest version of Vcc has a keyboard map editor.  You may be able to
fix the mapping using the editor.

On Fri, Aug 13, 2021, 4:47 PM <coco at jechar.ca> wrote:

>
> I found the documentation and with a by cutting a piece of a used google
> play card to size I replaced the lost nylon and I got the keyboard
> working.
>
> However there are issues.
>
> 1. The documentation says "You can tell which key map is selected as a
> ‘V’, ‘X’, or ‘M’ will display on the screen – indicating ‘VCC’, ‘XRoar’,
> and ‘MAME’ respectively." however this does not happen.
>
> I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and
> the alphabet and numbers but much of the top row works incorrectly for
> example
>
>     [SHIFT2] gets @ and should get a "
>     by the way the notation here
>     [SHIFT2] means hold down the shift key and the 2 key at the same
> time.
>     [SHIFT6] gets ^ and should get  &
>     [SHIFT7] gets & and should get '
>     [SHIFT8] gets * and should get (
>     [SHIFT9] gets ( and should get )
>     [SHIFT0] gets ) and should not
>     [:] by which I mean pressing the : key which is in the top row on a
> COCO.
>     [:] gets a - but should get a :
>     [SHIFT:] gets an underscore but should get a *
>     [-] gets a = should get a - "minus"
>     [SHIFT-] should get an = but gets a +
>     [CTRL-] should get an underscore but gets an =
>
>      And finally BREAK and ESCAPE do not seem to work.
>
>      Is there a way to fix this. Will there be a software update to fix
>      these and is there a way to update I did not notice if there is a
>      PROGRAM button like on a pi pico and in the documentation included
>      no Info about flashing in new keyboard maps.
>
>      Charlie
>
>
> On 2021-08-12 22:49, Paul F wrote:
> > Charlie -
> >
> > The CoCo Keys2USB is my project. There are two links on the Tindie site
> > -
> > one for the source code and one for the .pdf version of the
> > documentation.
> > It sounds like you clicked the first link which brings you to the
> > GitHub
> > repository, and the readme.md file that you mentioned in your post is
> > an
> > industry standard markdown document which accompanies most git
> > repositories. It can be viewed with a standard text viewer or is
> > rendered
> > through any HTML viewer/browser.
> >
> > I believe the document you need though is the second link, which can be
> > accessed here -
> >
> https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf
> >
> > The thin piece of plastic you referred to in your original post is just
> > a
> > clear piece of nylon cut from a milk jug. It's only purpose is to
> > provide a
> > non-conductive wedge between the flat-flex mylar keyboard cable and the
> > 2x16 card edge connector on the Keys2USB kit. As the documentation
> > mentions, you want to have that under (on the non-conductive) side of
> > the
> > mylar cable to ensure the conductive (upper) side of the cable makes a
> > firm
> > and solid contact with the card edge connector.
> >
> > Also, the kit is designed so that the card edge connector could be used
> > in
> > both orientations (with the micro USB connector either on the left or
> > the
> > right). The important thing is that in either orientation, the nylon
> > wedge
> > is on the underside of the flat-flex mylar cable.
> >
> > Paul
> >
> > On Thu, Aug 12, 2021 at 9:53 PM <coco at jechar.ca> wrote:
> >
> >> Ok I found some documentation at
> >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it
> >> was
> >> .md format I do not have a program to
> >> read that why did they not stick to a standard like .docx or .pdf
> >>
> >> Do you know someone who can convert it to .pdf if I email it to them.
> >>
> >> Charlie.
> >>
> >> On 2021-08-12 20:29, Christopher R. Hawks wrote:
> >> > On Thu, 12 Aug 2021 20:16:44 -0400
> >> > coco at jechar.ca wrote:
> >> >
> >> >>
> >> >> Hi I have a CoCo Keys2USB which I have used in the past however the
> >> >> piece of plastic holds in the keyboard ribbon cable must have fallen
> >> >> out and when I moved the keyboard and realized that the connection
> >> >> had come loose and I am not sure which is the correct way to plug it
> >> >> in nor do I know if I plug it in the wrong way If I will destroy it
> >> >> can't find the documentation I had nor does there seem to be a PDF
> >> >> online can anyone help.
> >> >>
> >> >> Charlie
> >> >>
> >> >
> >> >     A quick search with DuckDuckGo shows the kit web page is here:
> >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/
> >> >
> >> >     It includes links to the documentation and source code.
> >> >
> >> >
> >> > Christopher R. Hawks
> >> > HAWKSoft
> >> > --
> >> > Piglet noticed that even though he had a very small heart,
> >> > it could hold a rather large amount of gratitude.
> >> >                      ---Winnie Ther Pooh
> >> > ----------------------------------------
> >> >        \   ^__^
> >> >         \  (oo)\_______
> >> >            (__)\       )\/\
> >> >                ||----w |
> >> >                ||     ||
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> https://pairlist5.pair.net/mailman/listinfo/coco
> >>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>