Re: IIe Keyboard On A II Plus

["Bill Garber" <willy46pa@comcast.net>]

"Bill Garber" <willy46pa@comcast.net> wrote in message I5udnanzFbR2pf3VnZ2dnUVZ_umdnZ2d@comcast.com">news:I5udnanzFbR2pf3VnZ2dnUVZ_umdnZ2d@comcast.com...
> 
> "Bill Garber" <willy46pa@comcast.net> wrote in message 2aKdnQkD6ID-TsLVnZ2dnUVZ_gSdnZ2d@comcast.com">news:2aKdnQkD6ID-TsLVnZ2dnUVZ_gSdnZ2d@comcast.com...
> > 
> > <a2aviator@gmail.com> wrote in message ce1de9e0-d31d-48b8-88d4-ebf90528985f@w5g2000prd.googlegroups.com">news:ce1de9e0-d31d-48b8-88d4-ebf90528985f@w5g2000prd.googlegroups.com...
> > > /me hit me with a clue-by-four.
> > > 
> > > I never even bothered to think about those encoders as micro
> > > controllers. Hell, and I have documentation not very many others have
> > > even seen.. apparently I've not looked at all of it either.
> > > 
> > > ...and if it's emulating a 16 pin keyboard it should work anywhere,
> > > Franklins, clones, whatever.
> > 
> > That's something I need to do. Test it in my Franklin, who also has 
> > a keyboard that doesn't want to work. Need to dig out an extended 
> > keyboard for that though. 
> 
> Ok, I got out the Franklin, added 6 more socket extensions to clear 
> all of the lower case stuff, and whatever else is on that big riser board. 
> 
> Anyway, it works, although there doesn't seem to be lower case, and 
> I think I know why, but due to the many uses for this device, I'm not 
> going to add it. The upper board may not be necessary in the Franklin, 
> but I'm not sure how easy it is to remove it. I'll have a look at it, and, 
> if anyone already knows (Michael or Tony or David, or anyone else), 
> please speak up before I wreck this thing.  :o) 


Apparently, this has lots of stuff attached to it, because, nothing works 
with it off. There are lots of empty sockets under it. Now that's a hack. 
Anyway, put about 6-7 riser sockets on the Encoder and, it works ok 
with the Franklin Ace 1000 v. 2.2. 

Bill Garber from GS-Electronics
http://www.garberstreet.com