deskthority

Old Logo Dell branded Model M

Let's assume with replacement keycaps. I'm just not quite sure how sought after that logo is on a model M.

Controller Replacement This is the approach I took. You can see some details in the thread I started earlier this year. https://github.com/kiibohd/controller/blob/master/Scan/Deprecated/EpsonQX-10/scan_loop.c It's actually pretty straight-forward to do. Just a little bit tedious. However, this appr...

Long story short - I think it's kind of hard. I'm also interested in this, though, as I just picked up an Epson something-or-other, I'll post the model number this evening. I believe @snacksthecat has experience with converting Fujitsu leaf springs and could offer some advice/suggestions. He also co...

I have tried, desperately, to be very polite throughout all my exchanges here. All I care about is getting my beamspring working, not getting into petty arguments, but DMA is constantly antagonizing and insulting, and seems to assume everyone is an idiot because they can't look at his code for five...

@PancakeMSTR Have you tried different usb cable(s)? Are you using a usb hub? These are a few things that have tripped me up in the past with stuff like this. No clue if these will actually help but wanted to share my experience. I will try to think of other things as well. I've been using the same ...

go stare at matrix output. All you'll ever need to fixing the scans is there. If you're not able to deduce from that info what's wrong - there's nobody in the world to help you. Yeah, EXCEPT FOR YOU . That's why I'm asking - nay - PLEADING for your help! WHAT AM I LOOKING FOR??? And, since you're n...

Hey, let's just relax. This is a frustrating problem for both of us. I understand that "unsafe" means the keys are spamming, what I don't understand is how to fix that problem. My grounds are setup to spec, and the I'm using settings on FC that were with the previous source not giving me "unsafe" bu...

Okay so this is sort of interesting. I go through all the steps I outlined in my previous comment. I'm at the point where I've uploaded the config to EEPROM. I close flight controller and (usually, not always) can get output from the keyboard at this point. Spamming keys, as usual. Now, I unplug the...

Also, now when I start up FC the "UNSAFE" indicator is lit up red and I can't get "Scan" or "Output" to stay green (I get the "Scan module has gone insane and had to be shot!" error). That's noise/grounding issue. Docs tell what to check in that case. Also it's good that it trips - it will bring do...

DMA - Just wanted to let you know, tried the new source since your last commit, no change in behavior. Still can't get output outside of FC no matter what I do. Also, now when I start up FC the "UNSAFE" indicator is lit up red and I can't get "Scan" or "Output" to stay green (I get the "Scan module ...

Found a thing commented out that should not have been commented out. Would manifest as keyboard not turning "Output" green and not emitting anything if just plugged in, with FC not being connected. PancakeMSTR - that likely fixes your problem. I'll try it when I get home and get back to you with th...

PMed

darkcruix wrote: ↑

13 Aug 2019, 18:18

Apart from committing to EPROM, did you uodate prior (CTRL+U)?

I've tried it both ways, updating and not updating. Makes no difference as far as I can tell.

So, "setup" being yellow, controller outputs keypresses via debug channel. That's normal. To get it to send data as keyboard, you either click "setup" so it's grey, or exit FC. The spam means your readings are unstable. Go to hardware settings, reset charge/discharge to what's recommended. If it's ...

Computer is not a part of the problem, that's one thing I can guarantee (FC is much fussier than HID driver, if it works - the USB device part definitely works). Delete the CommonSense directory, download from github, change config.h and pins to match your physical layout, recompile, reflash. Okay ...

Okay I'm gonna start fresh on a different computer. It's the only thing I can think to try, other than trying a new Cypress. Btw I've quadruple checked the pins, and I'm using the source from since you most recently updated the pins. I'll try from scratch anyway though, can't think of anything else ...

Ah. go to globals.h and change NOT_A_KEYBOARD back to zero. Well, I was certain that would do it, but unfortunately no dice. For reference, I rebuilt both the bootloader and the 8x24 project in PSoC after I made this change, then reflashed the Cypress. Didn't make any difference, setup mode still o...

As for "can't see keypresses" - check that you have layout correct and it has letters on _base_ layer. Setup mode gives you matrix coordinates. They are transformed by layout to actual USB scancodes. Right, and I can only get Flight Controller to see keypresses as matrix coordinates, not characters...

Couple other notes. Rebooting the host is NOT needed. Closing FC is the most drastic action you will ever need to take. "Upload" uploads your changes to the firmware, BUT NOT TO EEPROM (must I say that's in readme?). "Commit" writes to EEPROM. "Revert" reboots the controller - same thing as pulling...

I bet you previously have it written to the eprom, I always did a upload (Ctrl+U) before I wrote it to the EPROM, but that probably doesn't matter. What happens, if you click on the yellow "Setup" at the bottom of the main FC window? After that, keys shouldn't register in the application anymore bu...

Here are some pictures of Flight Controller with my Beamspring. Let me know if you would like any more.

Notice that when I commit to EEPROM it says "wrote zero bytes." What is that about?

yes, should be safe to remove that, and recompile. I've also re-written a good portion of that code as well, as the macros IMHO don't allow for a more maintainable code-base, but that's just a personal code-smell kind of thing. let me know if it still doesn't work right, i might have accidentally m...

Okay update. Counting from Col 0, wired (the dead columns) Col8, Col9, and Col10 to pins 15.[2,3,4] respectively and removed C41,C42, and R5 from the cypress. This has fixed the dead columns issue. I sat around playing with thresholds for a while and managed to get almost every key working properly ...

@PancakMSTR: My problems with unrecognized columns vanished, after: I did get 3 GNDs attached to the metal part of the case. I had to attache both top and bottom ground of the PCB and one ground from the Cypress. Once I did that, I got good readings The connections from the Cypress to the PCB have ...

So I'm using the updated github source, with the pinouts set appropriately, and I'm running into two problems. One is major, and one is probably minor. The major problem is that three of my columns aren't registering, specifically 9,10, and 11. Here is a screenshot of my matrix monitor. Second probl...

The README describes how to do it without any defaults. From the [readme] There are config files in misc/ directory which should be a good starting point. The README describes how to do it without any defaults. Just do it in steps. Planning => Soldering => Thresholds (+hardware settings if you can'...

Also in the same boat with darkcruix and kmnov on the 8x24 project.

yes, should be safe to remove that, and recompile. I've also re-written a good portion of that code as well, as the macros IMHO don't allow for a more maintainable code-base, but that's just a personal code-smell kind of thing. let me know if it still doesn't work right, i might have accidentally m...

Okay I just simply don't understand why this is not working for me. I've gone through the steps multiple times and can't get any decent behavior. If I mash the keyboard with my hands I get a bunch of output in flight controller but pressing single keys simply doesn't do anything, ever. Steps: - Load...

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...