Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow typing is OK… but faster typing gets corrupted #7

Closed
jrw35 opened this issue Jan 4, 2025 · 8 comments
Closed

Slow typing is OK… but faster typing gets corrupted #7

jrw35 opened this issue Jan 4, 2025 · 8 comments
Assignees

Comments

@jrw35
Copy link

jrw35 commented Jan 4, 2025

Hi. This project is great — thank you.

It works for me, but only if I type slowly. ‘One finger’ speed is OK.

When I type at normal speed, it starts generating control codes instead of letters. I think it registers more than one key and they get mixed up.

Do you have any suggestions, please?

Thanks in advance.

@No0ne
Copy link
Owner

No0ne commented Jan 5, 2025

Which motherboard and OS are you using?

@jrw35
Copy link
Author

jrw35 commented Jan 5, 2025

Thanks. It’s an old (2000) HP laptop running Windows XP.

@No0ne No0ne self-assigned this Jan 5, 2025
@No0ne
Copy link
Owner

No0ne commented Jan 5, 2025

Dusted off my old Toshiba laptop and I can reproduce the problem. I'll come back to you when I have a fix for that.

@jrw35
Copy link
Author

jrw35 commented Jan 5, 2025

Amazing. Thanks. Let me know if I can help.

I will also find a newer computer with PS/2 to check if my circuit behaves differently with that.

@jrw35
Copy link
Author

jrw35 commented Jan 11, 2025

Hi again. Following up to say that I’ve tested this on a slightly newer desktop PC with a different keyboard and I had the same results. Just like before, it works perfectly at slow speeds but not if you type faster.

I’ve also rebuilt the circuit from scratch (the only parts that I reused are the Pico and the OTG adapter) but that hasn’t made any difference.

@No0ne
Copy link
Owner

No0ne commented Jan 29, 2025

Should be fixed in the latest 2.2 release!

@No0ne No0ne closed this as completed Jan 29, 2025
@jrw35
Copy link
Author

jrw35 commented Jan 29, 2025

That's great -- well done and thank you very much for fixing. Looking forward to trying it out!

@jrw35
Copy link
Author

jrw35 commented Feb 13, 2025

Working perfectly. Thanks again!

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants