Conversation

Notices

1. Foone🏳️‍⚧️ (foone@digipres.club)'s status on Monday, 19-Feb-2024 12:33:25 JST Foone🏳️‍⚧️

   The board is looking corroded under the capacitor, and it's got gunk coming out the top and button, but... it tests perfectly fine.
   huh.

   (I'm still replacing it, sure, but I was expecting this cap to read as FUCKT on the little LCD)

   • martin_fff (martin_fff@mastodon.social)'s status on Monday, 19-Feb-2024 12:53:13 JST martin_fff

     in reply to

     @foone Did you check it for ESR?

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Monday, 19-Feb-2024 12:53:13 JST Foone🏳️‍⚧️

     in reply to

     • martin_fff

     @martin_fff no, I don't have a tester handy. so I'm just gonna replace it

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 12:31:36 JST Foone🏳️‍⚧️

     in reply to

     I think I figured out why it's broken: I was measuring the size of the caps so I can order appropriate replacements, and according to my calipers, the leads of this cap are exactly 6.66mm apart.

     Clearly it failed to the influence of THE SATAN

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 12:42:56 JST Foone🏳️‍⚧️

     in reply to

     ahh, this service manual is of the Old School where when they say "MF" they mean µF.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 13:45:20 JST Foone🏳️‍⚧️

     in reply to

     okay caps ordered. and I finally looked into the keyboard, and it turns out the 4-wire interface is... interesting.

     So the way it works is that it has +5V, GND, CLK, and DATA. CLK is a lie: it's not a clock.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 13:46:39 JST Foone🏳️‍⚧️

     in reply to

     the IC in the keyboard works by constantly sending the state of a given key to the connected terminal.

     if you set clock to low for a short period (less than 6 microseconds) it advances to the next key.

     if you set clock to low for a long period (>30 microseconds), it resets to the first key.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 13:47:54 JST Foone🏳️‍⚧️

     in reply to

     so to scan the keyboard, you just need to hold "CLK" low for >30 microseconds, then you watch the data line while pulsing CLK using pulses less than 6 microseconds long

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 13:49:09 JST Foone🏳️‍⚧️

     in reply to

     the fun thing about this is that wyse produces very similar keyboards for different terminals, with things like added function keys or numeric keypads

     they have completely different layouts in terms of key ordering, so... you can't swap keyboards between terminals, even if they use the same connector

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 13:50:18 JST Foone🏳️‍⚧️

     in reply to

     so like the Wyse-30 keyboard tells you the state of the numeric keypad 1 key after a reset, I believe.

     the wyse-60 keyboard? it tells you the state of the SETUP key

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Tuesday, 27-Feb-2024 13:58:14 JST Foone🏳️‍⚧️

     in reply to

     WYSE: it is a good and normal thing to have two visually identical keyboards that need to match their similar terminals and will fuck up completely if you accidentally swap them

   • vxo (vxo@digipres.club)'s status on Tuesday, 27-Feb-2024 21:58:54 JST vxo

     in reply to

     @foone that is the most gloriously primitive protocol I've ever heard of. Thing straight up reminds me of AMX192, a 1970s stage lighting control protocol

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 08:55:57 JST Foone🏳️‍⚧️

     in reply to

     okay I wired up a teensy microcontroller to the +5/GND/DATA pins.

     so now I can determine... if the 1 key on the numpad is down. that's all.

     progress, technically?

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 09:04:42 JST Foone🏳️‍⚧️

     in reply to

     okay I can manually advance through the matrix by sending my teensy an "n" character. So I can confirm I can send pulses of the correct length (or close enough)

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 09:14:49 JST Foone🏳️‍⚧️

     in reply to

     I have it scanning but I accidentally made it only update the keys the first time they're pressed.

     So every key works, but... only once.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 09:19:23 JST Foone🏳️‍⚧️

     in reply to

     I'm currently pulling a reverse CSI:

     I'm using two keyboards at once

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 09:36:15 JST Foone🏳️‍⚧️

     in reply to

     Okay I've tested all the keys. They work just fine... except for the "C" key.

     Fortunately these are off the shelf Cherry Blacks, so I can just buy a brand new one, a mere 32 years later

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 09:41:40 JST Foone🏳️‍⚧️

     in reply to

     I can't easily make an Actual Keyboard out of this with the parts I have on hand: I'm using a Teensy 2.0 because I need 5v support, but I can't make that into a keyboard because I've run out of RAM in my program.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 29-Feb-2024 09:43:14 JST Foone🏳️‍⚧️

     in reply to

     but at least this lets me confirm my keyboard works, and gives me the beginning for my potential future project of a Wyse Keyboard Protocol Translator