deskthority

If soldering MCU pins fixed the problem for a while then it is likely you have badly soldered MCU to PCB or the MCU is broken. The thermal stress may have temporarily (dis)connect something in the MCU package. The chance that it is somewhere else around the broken row traces on the PCB is lower now....

LOL, nice one!

Try to measure the resistance between the row and the ground when the keyboard is not connected (powered off). Make sure you place the negative probe of the ohm-meter on the ground (notice that many ohm-meters have negative pole on the red probe). You should measure values in the range of 10 MΩ or b...

Red_October wrote: ↑

11 Feb 2019, 21:32

Model F 122-key. N-key rollover, infinite programmability through Soarer's Converter

How much latency does Soarer's Converter add?

Cherry MX Brown switches in my Kinesis Advantage started to misbehave after about 11 years of daily use. All other keyboards/switches I used did not fail but I never used them for more than about 1-2 years. A friend had a bad luck with Gateron white (linear). Two switches failed after about 2-3 year...

Interesting. He adds key travel time to the latency and the key travel time is in the range of 16 - 32 ms. Cherry MX registers in the middle of the travel so that would make it 8 - 16 ms latency because of the the travel time. Well, gamers should use microswitch keyboards with about 0.5 - 1 mm trave...

Kinesis Advantage 1 USB polling rate is 8 ms. This is Cherry MX Brown.
My custom K84CS keyboard polling rate is 2 ms. This one is Gateron Blue.
I have only PS/2 rubber dome now -> no rubber dome data from me.

No ghosting and jamming is requirement for any keyboard regardless whetter is is a generic rubber dome or an expensive gaming keyboard. I doubt that rubber domes do jam or ghost more often. I never had this problem with the few rubber domes I had. I had some ghosting problems with a Cherry MX switch...

Ok, that is true for the actions which can be anticipated. But if it can be anticipated about 200-300 ms in advance then it is probable it can be anticipated 5 - 10 ms more to compensate for keyboard delay. And that means that keyboard does not matter at all. Objectively. Of course, there is your ar...

I measured myself few years ago when I was playing games more and my response was around 220 ms (image change detected by eye to finger movement). This web site claims: "The average (median) reaction time is 215 milliseconds, according to the data collected so far." But when one looks at the data th...

Menuhin wrote: ↑

05 Feb 2019, 16:02

I thought, how I can apply this?

Glue it on the top of the keyboard. There is no point putting it on the bottom. Nobody will see it there.

Allegedly, if a trademark is not defended than it is lost. So if the guy does not get cease and desist letter for long enough and his logos are known enough then the logo becomes free. Make the logos through a small LLC and if the logo gets defended then the LLC will go under :) ... or talk to a law...

If the key registration on a network server (instead of registration on the local computer) is important then the internet latency is the biggest problem because it can vary a lot between players. Here are some estimates of common latencies: internet: typically from 20 to 60 ms roundtrip keyboard wi...

I'm really not sure that a 3D printer would be able to recreate the level of precision that injection moulding would It would not. FDM/FFF and SLA are ruled out. The vertical wall will not be smooth enough. Maybe SLS printers can get enough resolution and detail but I did not hear about an SLS prin...

Don't go for tiny soldering iron tips. E.g. for a 1 mm wide SMD part it is still good to have about Ø 2 mm bevel or chisel tip. A bigger tip is good to transfer heat quickly to the part.

I would put it in a vise with padding: wooden plate (about 1 cm thick) polystyrene (about 1.5 cm thick) keyboard polystyrene wooden plate Then bent it back by pressing on it through another wooden plate and polystyrene layers ... and pray for best. If it would not work afterwards then it is time for...

Thanks for pointing out the low power consumption of sharp memory LCD.
e-ink has better viewing angles. That may be a reason to prefer it. Isn't e-ink also cheaper?

Edit: Yes, eink seems to be slightly cheaper.

andrewjoy wrote: ↑

10 Jan 2019, 11:10

But would they not be better with sharp memory LCDs ?

USB2 gives you only 2.5 W. That would not be enough for LCDs.
They would be limited to USB3 with Power Delivery.

Huh? What kind of firmware stops scanning mid-scan? If there is a conditional command checking whether something is pressed after scanning started and before the whole matrix is scanned then that is enough. My firmware (and the firmware I branched from) has such a command there after scanning a col...

Sounds like my users are just as well off trusting the manufacturer of the keyboard. If it is so then your clients need to review the keyboard firmware. Even the smallest keyboard firmware will have at least few kilo bytes. And you need a custom firmware. The reason is explained below: You do not w...

What’s a controller to do when the switches can’t do their job? The only thing a controller can do is increase the debounce time (easy) or improve the debounce method. The most simple debounce method just requests that N sequential reads of the switch return the same value. E.g. when reading the ma...

Files from a faulty Gateron linear switch. When pressing the switch quickly then it is almost stabilized in about 20 ms. Although some disturbance to the signal is still there after 55 ms. bad-5ms.png bad-2ms.png When pressing it slowly then the situation is much worse. There are still major errors ...

You may want to save one key press and release if you actually intended to press the key outside of a layer which you already pressed in the layer. It just looks like you did not optimize your layouts for this scenario. It is similar to you wanting to save one key press/release in the case of your p...

I do not use xwhatisit controller but I think it is the intended behavior. My firmware behaves the same way as for as point 1 and differently as for as point 2 (no need to release Fn before pressing another macro triggering key). But the original firmware I branched from had the behaviour the same a...

I think a way of addressing the problem with current switches might be to make the board with user adjustable anti-bounce. Have a small potentiometer (possibly screwdriver headed) hidden under the board where you can choose how much anti-bounce (would this come at the expense of response time?) you...

You're not the first with this idea. Have a look at HaaTa's KLL Spec. It is an obvious use case of an analog switch. It would be depressing if I would have been the first one :D Is an analog switch only in a spec or is there some prototype and user feedback how well it works as well? E.g. another a...

vvp, why not look at the date of the response, that was back in 2013, the keyboard was only a year old (+a couple months). THAT'S unreasonable? No, that's very much rude and telling the customer that they know their product only lasts a couple years before people buy replacements. Good point. I did...

Expecting some kind of warranty on a keyboard from 2012 is unreasonably optimistic :shock: I'm surprised the support team did respond at all. Edit: Actually their response is reasonable and to be expected from a good sales guy. They are trying to sell you a new keyboard; hoping to placated you with ...

I’d like to see someone take an oscilloscope to some badly chattering Matias switches. What I expect to see is a lot of white noise at the individual switch level. I do not have any broken switches at hand :) I have only Cherry MX and Gateron switches and all of them are good. Here are some scope f...

Yes, agreed. But the consequence is the same. A delay for the user. And how the user will perceptive is the only thing which matters. That said, it is good you are trying analog switches. You should definitely achieve smaller delay times. And for some things analog switches would be great. E.g. they...