deskthority

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

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" K I've gone through the...

Just finished wiring everything up and tried to test. I'm getting absolutely nothing in flight controller, but I can't tell what I've done wrong. The only thing I can point to is some error in Flight controller saying something like "Scan module has gone insane and had to be shot." Does anyone have ...

I'm starting to try and convert my beamspring using common sense because I've given up on the xwhatsit (can't do the SMD soldering). I have a question, because I'm getting conflicting results from the (available) documentation and the project page, which is do I still have to modify the controller (...

Huh I'll have to play around with that. You mean the else statement with the print right?

Hey sorry I have one.

ah, so glad to hear you got this working! i was gonna pipe in and say that there's a big ol bug in the form of a debug statement in the middle of an interrupt routine that causes the QMK converter to bug out. if you remove that statement it works just fine. no idea why its there, or why someone tho...

I might have missed but did you try hasu's xt_usb - https://github.com/tmk/tmk_keyboard/tree/master/converter/xt_usb as this one is reported to be working. Well I tried this, and it seems to be working perfectly. I'm typing this message out on the Zenith. I'll use the keyboard for a bit and update ...

I think you're probably right. I can't remember about the slits, but they definitely have the simplified contact mechanism without the white part.

Nice diverse sale thread! If I hadn't just purchased and received a set of EC9009 caps I would buy yours - I wanted the JP sublegends too but settled on the normal base set =/ My B key is even crooked >_< Anyway, GLWS! Oof.... And I've been meaning to post this stuff for literal weeks. Thanks thoug...

If that's okay, I'm starting my own sell thread. This is the first round, and it's distinctly possible I'll add more down the road. If mods have an objection to this, let me know. For all items, I only want paypal and buyer pays shipping. I'm working on packing all of these items up and will update ...

kokokoy wrote: ↑

25 Jul 2019, 07:55

I might have missed but did you try hasu's xt_usb - https://github.com/tmk/tmk_keyboard/tre ... ter/xt_usb as this one is reported to be working.

No I haven't I'll try that tonight.