deskthority

If you have a US ANSI model M, I can trade with you a German ISO model M...

For typing : If noise doesnt matter - Any IBM model F keyboard. If you are lucky, you can get one for as low as 20 euros. You'll have to search on local classifieds though. A Model F is several times better than a model M (at least in my opinion) If you want a quiter keyboard - Cherry MX brown or bl...

I want to trade one of my Blue ALPS board. - Focus 727/747. Send offers via PM. I am based in Germany, prefer to ship to EU. Since this is a fairly rare board, please send fair trade offers... Condition doesn't matter as long as it works. I am particularly interested in Model Fs (No XTs - I have sev...

I recently acquired a Focus 727/747. The condition is fairly good. What's peculiar however is that the date label reads 19.3.1976!!! Is that even possible? IMG_20190909_113426.jpg IMG_20190909_200045.jpg I was under impression that the earliest blue Alps were not even made until the early 80s. There...

Bump

If your rivets are intact (and you aren’t missing more than 5/6 of them), I would not recommend bolt modding. If your keys register fine, skip the bolt modding....

In Europe, generally we get an invoice to pay from the customs. I am a bit surprised that you are buying a keyboard from Europe and having it shipped over to the US. I would expect it to be the other way round, there’s tons of retro stuff that I’d rather buy from the US....which are impossible to ge...

Both the 3178 (blueswitch) and 3101 (commonsense) have been converted with commonsense ...

Here's my entire IBM family:

From top to bottom:
IBM 3101 Beamspring (1983)
IBM F XT 1985
IBM F 3178 BlueSwitch 1984
IBM Model M 1990
IBM Model M122 1990

Missing members:

IBM SSK (Anybody generous enough for a donation ?)
IBM F107

Just to add: this is a *hobby*, something we all do in our own time and when we have spare energy. It's not a trade, nor barter or any other exchange, but a *gift*, and should be accepted as such. Y'know, gift horse and mouth and all that? Also I can't get my layer mods settings to persist beyond l...

karlmartin95 wrote: ↑

27 Aug 2019, 19:40

... and do you know why the back of the blueswitch has some space? it's very rare this keyboard.

The back of the keyboard has space for the manual...

Its not as rare as you think. They are quite common and not that expensive either...

Here you go https://github.com/dmaone/CommonSense For the pintout, here's the one I went with. However, take note that this pinout is based on a previous version of commonsense than whats on Github. The new version has a different default pin assignment. So use my diagram ONLY for reference. 3178.png

Soarers will not work on the 3178. I converted the 3178 using DMA's commonsense.
Enjoy your blueswitch. this is my favourite model F and I use this as my daily driver....

bump

For layers, in “layout”, click layer 1 then click switch. Define your layout for each layer. Keep the Fn keys consistent in each layers. Once you define layers, click apply. It’s a good idea to export and save the layout should you want to do a quick import later. Go to layers in FC and then assign ...

@PancakeMSTR
Lets do a screen share session later today.

Second problem: While everything else works nicely in flight controller, I can't seem to get any output from the "good" keys outside of it. I.e.., I can't get the keyboard to type anything in a normal window outside of FC, even though I've mapped keys in the FC layout editor. steps to correct this:...

Both the PCB ground traces MUST be connected to GND on cypress. Additionally, the two PCB ground traces MUST also be connected to the chassis. One of the cypress GNDs must also be connected to chassis. Without this, I couldn’t get it to work either.

The 8x24 project still has the old pin assignment in PSOC. We realised this when all three of us (PancakeMSTR, Darcruix and I) all had three dead columns. A closer inspection revealed that the PSOC PIN settings hadn’t been updated to reflect the new pin out proposed by DMA on github. Changing the pi...

I am trying to get the 8x24 project to work on a beamspring. I built the bootloader and the 8x24 project first without any changes - the build worked all fine. I then changed Config.h on the 8x24 project to reflect 24 Columns and 4 Rows and changed switch type to Beamspring. When building the firmwa...

Also your matrix seems wrong, you should see 24x8 or 24 x4. I see only 16x8, which means you didn't change the config.h correctly. Once your set the correct matrix in config.h, you must recompile the firmware and flash the firmware once again.

What about GND? The two GND traces on the beamspring PCB must be connected to GND on cypress AND also to the keyboard metal chassis.

In keymonitor, the values are obtained automatically. You do not need to press anything. Just click reset, choose "Max", let the values stabilize for a few seconds and then click "Set Thresholds". Go to Thresholds, for beamsprings, reduce the values by say 25%. So 4 becomes 3 and so on. Click Apply....

Click "Scan" in Flight controller. It's grayed out, you can see it next to "Unsafe". "Scan" must be in green before you can set thresholds. Click on it multiple times until it turns green.

Once green, click on "Threshold" and then follow DMA's guide on "Configuring Keyboard"

There are 23 columns on a beamspring. I counted 23 on your PCB as well. So you don't need to remove any resistor on the cypress board.

2. By base pins - I mean the following D0: 0.2. Must be connected to the nearest GND. Guard: 0.3. Must be connected to the nearest GND BY A SEPARATE WIRE ADC Vref: 0.4. Must be connected to the nearest VDD. This is different than what’s on my cypress board. I have what you described in the previous ...

A few open questions though: 1. If I want to reuse an existing cypress board (say for a future project), can I just reflash a new firmware on it? For example your new default hex file for the 24x8 matrix? 2. If yes to the above, I will have to change the base pins per the new layout you have describ...

Sometimes exiting setup mode doesn't work when you close FC - so either click yellow status bar area and then close FC, or just pull out the keyboard and plug back in. THAT was IT. All solved now! I am typing on it now... I learned a lot. Including how to compile hex files and what not.... A big ap...

What are you talking about ! I have asked a question and hence the post...

So here's a quick update: After wiring by the Cypress board (i used the prior default config), flashing the firmware (i used CommonSense.cywrk to compile the firmware) and wiring up the keyboard and after successfully connecting to the keyboard via Flight controller; I did the following: 1. Set the ...