IBM Model F 5291 Terminal (bigfoot) Keyboard

[xavierblak]

I fear this may be a bit of a lost cause but it's worth a shot. I recently acquired a handful of vintage keyboards. They're a little dirty and all the cords have been removed by someone looking for some scrap copper.

One of those keyboards was what I assumed to just be a Model F XT/AT board. But while cleaning it I opened it up and noticed it had too many wires to just be connected to a din connector. After a little searching it looks like I have a IBM 5291 Keyboard.

Anyone ever seen an adapter for one of these keyboards? Anyone have info on the pinout/protocol used to connect this to whatever terminal it was originally connected too?

Edit:
Just adding a link to some nice pics of the this model keyboard. Still googling for a protocol or pin out.

Controller firmware is now up, and handles this keyboard

[berserkfan]

Soarer told me his converter can't be used to convert this kind of Model F, but I'm really hoping someone on geekhack manages to do it in a reasonably easy fashion and posts his results. I really love the legs on this keyboard.

[Soarer]

It has no CPU! The 'protocol' as such is driving the mux and capacitive sense chips directly. I've got proof-of-concept code working pretty well, but it needs more work.

In essence, to read a key...

• set the key code onto the D lines
• set strobe low
• delay for a microsecond or two
• read the output
• set strobe high

On the plus side, it uses the older 4-channel capsense chip which seems to be far easier to drive than the 8-channel version with its variable sensitivty setting. I've been scanning the matrix at 1000Hz

[0100010]

Got any pics of the controller board - if it has one?

Wondering if it is like the 104 key Unsaver F's, where swapping in a 122 key F control board works to make it compatible.

[xavierblak]

Show Image

It has no CPU! The 'protocol' as such is driving the mux and capacitive sense chips directly. I've got proof-of-concept code working pretty well, but it needs more work.

In essence, to read a key...

• set the key code onto the D lines
• set strobe low
• read the output
• set strobe high

On the plus side, it uses the older 4-channel capsense chip which seems to be far easier to drive than the 8-channel version with its variable sensitivty setting. I've been scanning the matrix at 1000Hz :D

Hmm I think I follow. So I'm picking the key I want to know the status of with the D lines and then setting strobe low to get the state on the out pin? Cool, thanks for the info. Any chance you have the pinout from the pcb? I don't have the 15 pin connector anymore since my cable was removed before I bought it.

Got any pics of the controller board - if it has one?

I didn't but I just took some.

It's hard to say for sure unless I take the keyboard section apart but the pcb seems to continue down below the keys and is actually what registers the key contacts in place of the typical flexible membrane.

[Soarer]

From 5291_MaintenanceLibrary.pdf p38:





In a useful format, that's:

Code: [Select]

           D1  1      20  Ground
(missing pin)             -Strobe
           D2             Ground
           D3             D0
     (unused)             (unused)
     (unused)             (unused)
     (unused)             Frame Ground
           D4             +5V
           D5             Ground
           D6  10     11  Output

Only one Ground pin needs to be connected, I used pin 12.

[poxeclipse]

They look and feel better without the casing. Soarer, will try your controller  when is ready.

[xavierblak]

In a useful format, that's:

Code: [Select]

           D1  1      20  Ground
(missing pin)             -Strobe
           D2             Ground
           D3             D0
     (unused)             (unused)
     (unused)             (unused)
     (unused)             Frame Ground
           D4             +5V
           D5             Ground
           D6  10     11  Output


Awesome! Is the code you mentioned earlier available to look at?

Thanks so much for you knowledge on this stuff. I didn't think I'd get so much good info, glad you could prove me wrong. 

[Soarer]

Source code isn't available. I'm actually using my generic controller code, which I keep saying will be available 'soon', but I've had some interesting Real Work recently taking my time! It takes a config file to set it up, for this 'board it looks like:

Code: [Select]

matrix
scanrate 1
debounce 1
blocking 0
muxstrobe_port PB6:0
sense_delay 1
muxstrobe_gate -PD1
sense_polarity 1

sense PD0

muxstrobe 0 UNASSIGNED
muxstrobe 1 UNASSIGNED
muxstrobe 2 UNASSIGNED
# ...
muxstrobe 94 UNASSIGNED
muxstrobe 95 UNASSIGNED
end

[xavierblak]

Status update. I've got a proof of concept up and running. Thanks so much Soarer!

Next step map the key layout.

[berserkfan]

erm, I'm not really following this, but can I ask if there is a very high chance of this keyboard being adapted to work on a soarer converter?

I have gotten me some colored dupont line connectors and a teensy with legs and breadboard. Once xavierblak gets his F terminal up and running, I had better buy one before ebay prices soar through the roof.

[poxeclipse]

I have two of these keyboards. Willing to test a new controller, when it is ready.

[Soarer]

These jumper wires are great for quickly hacking a Teensy inside most IBMs...

[xavierblak]

erm, I'm not really following this, but can I ask if there is a very high chance of this keyboard being adapted to work on a soarer converter?

That would be up to soarer as I don't believe he's released the source for this controller. Either way I'm just using a teensy connected to the circuit board. I'll have to look at some of the avaiable teensy firmwares to see if any of them make sense to be converted to work with this keyboard. Once I have something working I'll post it here.

I have two of these keyboards. Willing to test a new controller, when it is ready.

I'll post to this thread once I have something. Do you have a Teensy and the ability to connect it to your keyboards?

These jumper wires are great for quickly hacking a Teensy inside most IBMs...

(Attachment Link)

I probably should have though of this but I still had a small pigtail of the wire left inside the case. So I just solder this to a perfboard with a dip socket for the teensy.

[poxeclipse]

I have two of these keyboards. Willing to test a new controller, when it is ready.

I'll post to this thread once I have something. Do you have a Teensy and the ability to connect it to your keyboards?

Yes, I do. 

[berserkfan]

Soarer, I know every post I make demonstrates my ignorance, but how did you connect the jumper cables directly to the PCB? Unless there are already connectors there which happen to be hidden by the dupont connectors' heads?

These jumper wires are great for quickly hacking a Teensy inside most IBMs...

(Attachment Link)

[Soarer]

There's a connector there that looks like two rows of Teensy pins side-by-side. It's where the cable would normally plug in to the PCB.

[berserkfan]

Um soarer, so are you able to make that keyboard work like a normal keyboard? Or are we at the physical-connection stage still? I am following this with great interest.

There's a connector there that looks like two rows of Teensy pins side-by-side. It's where the cable would normally plug in to the PCB.

[Soarer]

I guess you could call this 'working like a normal keyboard' - I just put a basic keymap onto it and typed this

Code: [Select]

matrix
scanrate 1
debounce 1
blocking 0
muxstrobe_port PB6:0
sense_delay 1
muxstrobe_gate -PD1
sense_polarity 1

sense PD0

muxstrobe  0 Z # 00
muxstrobe  1 S # 01
muxstrobe  2 W # 02
muxstrobe  3 3 # 03
muxstrobe  4 X # 04
muxstrobe  5 D # 05
muxstrobe  6 E # 06
muxstrobe  7 4 # 07
muxstrobe  8 C # 08
muxstrobe  9 F # 09
muxstrobe 10 R # 0A
muxstrobe 11 5 # 0B
muxstrobe 12 V # 0C
muxstrobe 13 G # 0D
muxstrobe 14 T # 0E
muxstrobe 15 6 # 0F
muxstrobe 16 B # 10
muxstrobe 17 H # 11
muxstrobe 18 Y # 12
muxstrobe 19 7 # 13
muxstrobe 20 N # 14
muxstrobe 21 J # 15
muxstrobe 22 U # 16
muxstrobe 23 8 # 17
muxstrobe 24 PAD_2 # 18
muxstrobe 25 PAD_5 # 19
muxstrobe 26 PAD_8 # 1A
muxstrobe 27 NUM_LOCK # 1B
muxstrobe 28 M # 1C
muxstrobe 29 K # 1D
muxstrobe 30 I # 1E
muxstrobe 31 9 # 1F
muxstrobe 32 COMMA # 20
muxstrobe 33 L # 21
muxstrobe 34 O # 22
muxstrobe 35 0 # 23
muxstrobe 36 PERIOD # 24
muxstrobe 37 SEMICOLON # 25
muxstrobe 38 P # 26
muxstrobe 39 MINUS # 27
muxstrobe 40 SLASH # 28
muxstrobe 41 QUOTE # 29
muxstrobe 42 LEFT_BRACE # 2A
muxstrobe 43 EQUAL # 2B
muxstrobe 44 SPACE # 2C
muxstrobe 45 RSHIFT # 2D
muxstrobe 46 BACKSLASH # 2E              # ~ (ISO)
muxstrobe 47 RIGHT_BRACE # 2F
muxstrobe 48 CAPS_LOCK # 30
muxstrobe 49 PAD_ASTERIX # 31
muxstrobe 50 ENTER # 32
muxstrobe 51 BACKSPACE # 33
muxstrobe 52 PAD_0 # 34
muxstrobe 53 PAD_1 # 35
muxstrobe 54 PAD_4 # 36
muxstrobe 55 PAD_7 # 37
muxstrobe 56 PAD_PLUS # 38
muxstrobe 57 UNASSIGNED # 39
muxstrobe 58 PAD_MINUS # 3A
muxstrobe 59 SCROLL_LOCK # 3B
muxstrobe 60 PAD_PERIOD # 3C
muxstrobe 61 PAD_3 # 3D
muxstrobe 62 PAD_6 # 3E
muxstrobe 63 PAD_9 # 3F
muxstrobe 64 EUROPE_2 # 40             \ | (ISO)
muxstrobe 65 A # 41
muxstrobe 66 Q # 42
muxstrobe 67 2 # 43
muxstrobe 68 LALT # 44
muxstrobe 69 UNASSIGNED # 45
muxstrobe 70 UNASSIGNED # 46
muxstrobe 71 1 # 47
muxstrobe 72 F7 # 48
muxstrobe 73 F5 # 49
muxstrobe 74 F3 # 4A
muxstrobe 75 F1 # 4B
muxstrobe 76 F8 # 4C
muxstrobe 77 F6 # 4D
muxstrobe 78 F4 # 4E
muxstrobe 79 F2 # 4F
muxstrobe 80 F10 # 50
muxstrobe 81 UNASSIGNED # 51
muxstrobe 82 UNASSIGNED # 52
muxstrobe 83 UNASSIGNED # 53
muxstrobe 84 F9 # 54
muxstrobe 85 UNASSIGNED # 55
muxstrobe 86 UNASSIGNED # 56
muxstrobe 87 UNASSIGNED # 57
muxstrobe 88 LSHIFT # 58
muxstrobe 89 LCTRL # 59
muxstrobe 90 TAB # 5A
muxstrobe 91 ESC # 5B
muxstrobe 92 UNASSIGNED # 5C
muxstrobe 93 UNASSIGNED # 5D
muxstrobe 94 UNASSIGNED # 5E
muxstrobe 95 UNASSIGNED # 5F
end


[berserkfan]

Hey Soarer,

That's awesome, but where did you type the stuff? Is the following text be put into an .sc file like your standard remapblock? I notice you have 13 unassigned keys. Does that mean the PCB has 13 spare contacts lurking inside the casing, or are they merely the additional f13-24 that I notice this keyboard has sharing keycaps with f1-12?

Well if you've managed to make it work, I guess the next question is whether it is practical and usable for normal purposes.

Are there any power requirements that make the keyboard impractical to use on a standard USB connection to a desktop?

Looking on ebay, these guys arent cheap. Considering how much more troublesome they are than an F XT and still share the same infuriating layout, it's ridiculous.

I guess you could call this 'working like a normal keyboard' - I just put a basic keymap onto it and typed this

Code: [Select]

matrix
scanrate 1
debounce 1
blocking 0
muxstrobe_port PB6:0
sense_delay 1
muxstrobe_gate -PD1
sense_polarity 1

sense PD0

muxstrobe  0 Z # 00
muxstrobe  1 S # 01
muxstrobe  2 W # 02
muxstrobe  3 3 # 03
muxstrobe  4 X # 04
muxstrobe  5 D # 05
muxstrobe  6 E # 06
muxstrobe  7 4 # 07
muxstrobe  8 C # 08
muxstrobe  9 F # 09
muxstrobe 10 R # 0A
muxstrobe 11 5 # 0B
muxstrobe 12 V # 0C
muxstrobe 13 G # 0D
muxstrobe 14 T # 0E
muxstrobe 15 6 # 0F
muxstrobe 16 B # 10
muxstrobe 17 H # 11
muxstrobe 18 Y # 12
muxstrobe 19 7 # 13
muxstrobe 20 N # 14
muxstrobe 21 J # 15
muxstrobe 22 U # 16
muxstrobe 23 8 # 17
muxstrobe 24 PAD_2 # 18
muxstrobe 25 PAD_5 # 19
muxstrobe 26 PAD_8 # 1A
muxstrobe 27 NUM_LOCK # 1B
muxstrobe 28 M # 1C
muxstrobe 29 K # 1D
muxstrobe 30 I # 1E
muxstrobe 31 9 # 1F
muxstrobe 32 COMMA # 20
muxstrobe 33 L # 21
muxstrobe 34 O # 22
muxstrobe 35 0 # 23
muxstrobe 36 PERIOD # 24
muxstrobe 37 SEMICOLON # 25
muxstrobe 38 P # 26
muxstrobe 39 MINUS # 27
muxstrobe 40 SLASH # 28
muxstrobe 41 QUOTE # 29
muxstrobe 42 LEFT_BRACE # 2A
muxstrobe 43 EQUAL # 2B
muxstrobe 44 SPACE # 2C
muxstrobe 45 RSHIFT # 2D
muxstrobe 46 BACKSLASH # 2E              # ~ (ISO)
muxstrobe 47 RIGHT_BRACE # 2F
muxstrobe 48 CAPS_LOCK # 30
muxstrobe 49 PAD_ASTERIX # 31
muxstrobe 50 ENTER # 32
muxstrobe 51 BACKSPACE # 33
muxstrobe 52 PAD_0 # 34
muxstrobe 53 PAD_1 # 35
muxstrobe 54 PAD_4 # 36
muxstrobe 55 PAD_7 # 37
muxstrobe 56 PAD_PLUS # 38
muxstrobe 57 UNASSIGNED # 39
muxstrobe 58 PAD_MINUS # 3A
muxstrobe 59 SCROLL_LOCK # 3B
muxstrobe 60 PAD_PERIOD # 3C
muxstrobe 61 PAD_3 # 3D
muxstrobe 62 PAD_6 # 3E
muxstrobe 63 PAD_9 # 3F
muxstrobe 64 EUROPE_2 # 40             \ | (ISO)
muxstrobe 65 A # 41
muxstrobe 66 Q # 42
muxstrobe 67 2 # 43
muxstrobe 68 LALT # 44
muxstrobe 69 UNASSIGNED # 45
muxstrobe 70 UNASSIGNED # 46
muxstrobe 71 1 # 47
muxstrobe 72 F7 # 48
muxstrobe 73 F5 # 49
muxstrobe 74 F3 # 4A
muxstrobe 75 F1 # 4B
muxstrobe 76 F8 # 4C
muxstrobe 77 F6 # 4D
muxstrobe 78 F4 # 4E
muxstrobe 79 F2 # 4F
muxstrobe 80 F10 # 50
muxstrobe 81 UNASSIGNED # 51
muxstrobe 82 UNASSIGNED # 52
muxstrobe 83 UNASSIGNED # 53
muxstrobe 84 F9 # 54
muxstrobe 85 UNASSIGNED # 55
muxstrobe 86 UNASSIGNED # 56
muxstrobe 87 UNASSIGNED # 57
muxstrobe 88 LSHIFT # 58
muxstrobe 89 LCTRL # 59
muxstrobe 90 TAB # 5A
muxstrobe 91 ESC # 5B
muxstrobe 92 UNASSIGNED # 5C
muxstrobe 93 UNASSIGNED # 5D
muxstrobe 94 UNASSIGNED # 5E
muxstrobe 95 UNASSIGNED # 5F
end


[Soarer]

Yeah, my controller code takes a config file, like my converter. I think I'm about ready to release a second beta test of it - but be warned, it will come with _very_ scant documentation!

I haven't used for long stretches, but I haven't seen any glitches like missing or doubled key-presses, even with an armful of keys pressed. It takes less power than a PC/XT keyboard, since it has no CPU.

I haven't taken it apart to look (I'm sure there's a pic out there somewhere) but I don't think there are any other usable pads. 5 of the gaps are used to read the jumper settings. Anything to do with the key markings would've been handled by the terminal, so I've no idea what the 1-12 / 13-24 markings are or how they functioned. I just put PC/XT codes on, as a familiar base for adding remaps and layers to later.

I guess there's no particular reason for anyone to get one of these unless the faster scanning is important to them.

[berserkfan]

I await the good news! (And in the meantime, I still have Model F on my ebay radar screen...) 

[Soarer]

Controller firmware is now up, and handles this keyboard

[poxeclipse]

Controller firmware is now up, and handles this keyboard

Did somebody try it on 3178 display terminal keyboards ?

[xavierblak]

I probably won't be able to get any photos up for a while. But I got it all cleaned up and am typing on it right now. Thanks to Soarer for posting his firmware.

With it's legs fully extended this thing is a monster!!!!

[Soarer]

Controller firmware is now up, and handles this keyboard

Did somebody try it on 3178 display terminal keyboards ?

I doubt it, yet!

edit: moved full reply to my controller thread 

[poxeclipse]

Controller firmware is now up, and handles this keyboard

Did somebody try it on 3178 display terminal keyboards ?

I doubt it, yet!

edit: moved full reply to my controller thread 

They do have a chip, it's not the same as 5291, right ?

[poxeclipse]

I probably won't be able to get any photos up for a while. But I got it all cleaned up and am typing on it right now. Thanks to Soarer for posting his firmware.

With it's legs fully extended this thing is a monster!!!!

Try without the case. It's much easier to type.

[Soarer]

Controller firmware is now up, and handles this keyboard

Did somebody try it on 3178 display terminal keyboards ?

I doubt it, yet!

edit: moved full reply to my controller thread 

They do have a chip, it's not the same as 5291, right ?

Not the same. I think they have an 8048 CPU (40-pin chip), but I don't know which capsense chip they have.

[SneakyRobb]

Hi,

I have 4176191 for 5291.

I used the controller from soarer on teensy 2.0.
Soarer_controller_v1.20_beta4_atmega32u4.hex.

I used scaswr to upload and hid listen to listen.

The teensy is wired directly to the pcb pins like is shown in a picture earlier in this thread.

My question is, that after all of this is done, the output I see on hid_listen is bizarre.
it consists of masses of data.
I tried with the config 'bigfoot' but when I pressed a key, it would type something like "-.36QE258O.P/"
Or close all my windows, open a window and type randomly, which was seen earlier in thread.

I made simple alterations to soarer config with everything unassigned.
On hid_listen the out put was about 500 characters of the form

"/03 \5E /12" etc. whenever I press a random key.

When nothing is presed on the keyboard nothing seems to happen.
I feel this is likely electrical/wiring.
I have provided a picture of my wiring.

The ground wire is something that might be a concern as I thought it might be necessary.
I do not know about it though and have a novice understanding of all of this.

Regardless, what is my course of action?
Is this a wiring issue or is it a mistake I made in setup

edit: also putting my hand near it seems to be picked up on hid listen?

[Soarer]

Try replacing the bolt that holds the PCB to the backplate - that makes an important ground connection!

[SneakyRobb]

Try replacing the bolt that holds the PCB to the backplate - that makes an important ground connection!

This has worked!

Thanks for the quick reply, and writing all of this firmware.

[Soarer]

This has worked!

Excellent!

[SneakyRobb]

From 5291_MaintenanceLibrary.pdf p38:

(Attachment Link)

(Attachment Link)

In a useful format, that's:

Code: [Select]

           D1  1      20  Ground
(missing pin)             -Strobe
           D2             Ground
           D3             D0
     (unused)             (unused)
     (unused)             (unused)
     (unused)             Frame Ground
           D4             +5V
           D5             Ground
           D6  10     11  Output

Only one Ground pin needs to be connected, I used pin 12.

Hi,

How does the frame ground work? Is that included in the only need one pin? My keyboard works, I am just having a hard time finding information about grounding.

[SneakyRobb]

It seems that it shorts out when the steel backplate is in contact with the metal pan. Are not these components supposed to be touching at all times though?

[SneakyRobb]

I think what is happening is that the lack of tabs and bolt issues. It seems to work if I support it on little feet. There are two nuts on the back that I installed that were coming into contact with the pan. I see now fohat's recommendation about keeping tabs intact.

 I think my issue is not electrical. I think there is not enough stable physical connection between the two plates, meaning that they can move ever so slightly so that if the back one is pressed it actually strains away from the front, giving spurious readings. I do not know if this is conclusive, but given that it was working and I changed nothing except how it was supported that I must be pointed in this direction.
I had rather enthusiastically removed most of the tabs, and the current arrangement allows for the plates to slide apart vertically slightly, I will perhaps need to install more bolts in order to achieve stability as well as proper spacing.

[Soarer]

Frame ground is intended as a safety precaution - a separate connection from the keyboard case to the host's frame ground. Using USB power provides plenty of protection, so we don't really need more. You could connect it to ground on the Teensy. It being disconnected is highly unlikely to affect the functioning of the keyboard, and nor is the lower frame or bolts touching the case.

So yeah, it sounds more like a mechanical issue. I can't remember how much space there is for making holes in the PCB, but one idea might be to have a couple of bolts tight, using washers in the middle of the sandwich to get the height right. Perhaps there's room at the front edge of the keyboard. That should reduce wobble, but I don't know if it would solve the issue. Disclaimer: I've never bolt modded any BS, so I'm just guessing!

[input]

Big thanks to soarer and xavierblack, I have had this 5291 for a couple of years and only just stumbled upon this thread.

I never thought I would see the day when I could actually see output from this keyboard, absolutely amazing.

Definitely a strange typing experience, spacebar is so large, feels so much nicer than an model M.

Still going strong after 27 years,

[dorkvader]

Big thanks to soarer and xavierblack, I have had this 5291 for a couple of years and only just stumbled upon this thread.

I never thought I would see the day when I could actually see output from this keyboard, absolutely amazing.

Definitely a strange typing experience, spacebar is so large, feels so much nicer than an model M.

Still going strong after 27 years,

you may want to consider lightening up the spacebar a bit if you plan to use it for a while, though. I'm glad you got it working, and it's a great KB to type on.

[cohomology]

From 5291_MaintenanceLibrary.pdf p38:

(Attachment Link)

(Attachment Link)

In a useful format, that's:

Code: [Select]

           D1  1      20  Ground
(missing pin)             -Strobe
           D2             Ground
           D3             D0
     (unused)             (unused)
     (unused)             (unused)
     (unused)             Frame Ground
           D4             +5V
           D5             Ground
           D6  10     11  Output

Only one Ground pin needs to be connected, I used pin 12.

Forgive my newbie question, I am guessing D0, D1, D2, D3 , D4, D5, D6 etc. are the pins on the teensy, but what about Strobe, Frame GND and Output? Not able to locate these pins on teensy 2.0 board I just picked up. Thanks!

[jacethesaltsculptor]

A How To Do this Guide:

Apologies for the thread Necromancy, but I had a rare opportunity to do four of these boards, and in the process was able to create a proper writeup on it, being that this is one of the biggest google hit results for this keyboard,

I want to help others who are able to get ahold of these boards convert them so they are still useful, and avoid the landfill.

I've attached a PDF I've written with some straightforward instructions on what one needs to do this.

If any mods/admins aren't okay with this, please tell me and I'll make a new post instead, the PDF does have a mega link in it that contains Soarer's Controller from one of his last posts, as well as the Teensy.exe program.

Best of luck with your conversions!

And if Soarer ever gets to see this: Thank you! You've made me and my family very happy with our keyboards, and it's thanks to you.

Here is the PDF in images, but the PDF is still included if you want to have a personal copy: The Files needed are attached at the end of the post as well.

The folder from the PDF is also available here:
https://mega.nz/#!vmBmzA6Z!Ha7clArUowNf7gmoi4D19-zwjgbNHc2d8_wQn4y0VJI

and in the attachments section of this post.

Happy convertin!

[xavierblak]

A How To Do this Guide:

Thanks for posting this. Very well done and clear.

[Jaki1122]

Hello everyone from Spain. Why I'm telling were I am? Because that will tell you that my IBM Model F "Big Foot" is NOT a 5291 but a 8521. Not that they are much different, the caps have different legends (Spanish text) on them and the pinout may be different (yet I doubt it, but I want to be sure). The missing pin on the connector that goes to the terminal is in the other side and VCC is also misplaced! Despite the pin heather in the board apparently having the same pinout, I want to be sure its is the same. Does anyone have the pinout for this one, so I can build a converter? Thanks!
Also, the jumpers 1,2 and 4 came shorted in my keyboard, but I don't see that being the case on your keyboards, you only seem to have the number 0 shorted. Why is that?

[Inoue]

Hello, not sure how active this is anymore...  acquired 4 bigfoots as of about a week ago and went to do this and followed directions to a T.  Somehow I'm just getting lots of keypresses on all of the bigfoots. I thought the board was bad so I went ahead and converted another with another teensy 2.0 just rule both out and had the same outcome keypresses would look like (see below). My converted model f xt looked normal and used that as an reference of what "normal" should look like.

(bigfoot output)
\17 +25 \1F +26 d25 d26
/17 -25 /1F -26 u25 u26
\17 +25 \1F +26 d25 d26
/17 -25 /1F -26 u25 u26
\13 +24 \1B +53 d24 d53
/13 -24 /1B -53 u24 u53
\13 +24 \1B +53 d24 d53
/13 -24 /1B -53 u24 u53
\13 +24 \1B +53 d24 d53
/13 -24 /1B -53 u24 u53
\50 +43 \58 +E1 d43 dE1 \40 +64 \48 +40 d64 d40
\24 +37 \2C +2C d37 d2C
/24 -37 /2C -2C u37 u2C /40 -64 /48 -40 u64 u40 /50 -43 /58 -E1 u43 uE1
\50 +43 \58 +E1 d43 dE1 \40 +64 \48 +40 d64 d40 \2C +2C d2C \24 +37 d37

[AngryC]

Hi, I have the same problem with 3 bigfoots.
I connected the teensy 2.0 like described in the guide above and flashed the bigfoot.sc on the teensy with the 1.20 beta4 version.

I mostly get 2 or 0 characters per key press.

I played around with the soarer settings like scanrate a bit but no change.

Any suggestions?

[AngryC]

I discovered something:
When I press M it outputs "nm". But when I hold the M key, it only outputs "m".
So the "n" comes in on the upstroke it seems. Same with other keys.

[AngryC]

Ok, I found the issue:
The guide above is wrong: Wire 2 and Wire 3 need to be each one pin above!

Here is how you connect the keyboard to the Teensy:
https://deskthority.net/viewtopic.php?p=519579#p519579

[jhoney12]

It's impressive to see the progress on adapting the IBM Model F 5291 terminal keyboard! The detailed protocol and pinout information provided is invaluable for anyone looking to work with these vintage keyboards. Given the complexity of the conversion and the detailed efforts being made, it might be worth exploring custom firmware options or seeking out community support for further refinements. Keep up the great work, and thanks for sharing these insights!