Tagged: repeating of various keys
TafrynParticipantDecember 15, 2016 at 11:51Post count: 2
Recent firmware binaries downloaded from the configurator seem to be really buggy. Modifier keys will get stuck, or simply stop working, keys will get stuck repeating while the rest of the keyboard fails to send key-presses, individual LEDs will stop working, etc. Most of these issues can be addressed by disconnecting and reconnecting the keyboard. However, that is only a temporary fix; the issues always return. Has there been a change to the firmware generated by the configurator in the last few months that may have caused this?gbarnParticipantDecember 19, 2016 at 12:48Post count: 6
I am getting a similar result with fast typing it either locks up and I have to unplug and replug to clear or I get an infinite repeating key. All keys worrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
The above happened as I typed this. Got it on last Massdrop, in service only a month, I recently updated the key mapping via the online configurator. Help, it is somewhat unusable. It is getting worse the more I get use to it and the faster I type.Jeremy BondesonModeratorDecember 19, 2016 at 13:14Post count: 48
Try to go to the alpha version of the configurator and import your previous .json file (should be in the zip you downloaded), then in the “kll defines” section add an entry for “MinDebouceTime” and set the value above 5 (maybe start at 7 and see if you need to go up/down from there). That configures the debounce settings for the keyboard. They are normally set at Cherry’s standard of 5ms, but you may be running into an issue with your switches.
Could you also both just let me know which switches you have installed?gbarnParticipantDecember 19, 2016 at 20:30Post count: 6
Ok, I did as instructed and am typing on it with this reply. I have the MinDedbouceTime set to 7 as suggested. I will give it a try and see if the issue goes away. I’ll report back in a few days. Thanks for the quick reply to the issue.
Oh, I installed Cherry Browns for the switches.gbarnParticipantDecember 30, 2016 at 18:22Post count: 6
It seemed to be working great for a week or so and it started happening again today. Keys getting stuck on repeat. It happens when I start to type really fast. This is very worrisome as I have a lot of money invested in it.
Any other ideas or settings I should try? Is it possible that the changes I made to “fix” it have somehow been lost?gbarnParticipantDecember 30, 2016 at 18:38Post count: 6
Ok I just flashed again using a 9 for the MinDebouceTime setting. I’ll try to uy
I was typing the above message and had a typo and hit the backspace key very quickly to get rid of the y and the keyboard seemed to hang. I couldn’t get anything to type. I tried hitting the L1 and it seemed to enter that page, at least the LCD changed color but other keys didn’t work. Getting very frustrated at this point.gbarnParticipantJanuary 3, 2017 at 08:42Post count: 6
Keyboard is still locking up after a short time of use. What is the process I need to start to get it either resolved or sent back for a refund?PCallathanParticipantFebruary 13, 2017 at 09:05Post count: 3
I am having the same issues with the most recent ergodox. I also have an Infinity Ergodox from the second drop and it is running the same firmware and working flawlessly.
– It is more likely the slave side that has the repeating key, but I have seen it on the master as well.
– Multiple keys have issues (so far M, B, R, _, Backspace) which sort of rules out the switch hardware.
– Interconnect between the master and slave can be removed during repeating and the slave key will continue to repeat.
– Issue persists regardless which hand is the master (same firmware on both hands).
– I have also seen when both halves will not send any keys to the PC but I can still change layers etc, so the keyboard is still functioning.
I am compiling my own firmware and I have just grabbed the latest and changed the MinDebounceTime from 5 to 7. I will see if there is any improvement with that.gbarnParticipantFebruary 13, 2017 at 09:14Post count: 6
For the record I was able to return the keyboard and get my money back. I had spent a lot of time working the issue and came to the conclusion that it was never going to get resolved. I am and was a very good customer, and have spent plenty of dollars so the return was granted. @PCallathan good luck.parakModeratorFebruary 13, 2017 at 22:18Post count: 32
Hey folks, sorry for the delayed response. This sounds like a known issue that will soon be fixed in the alpha configurator – I’ll post again as soon as it’s live there for you to try.parakModeratorFebruary 15, 2017 at 09:25Post count: 32
Please update your firmware via the configurator – it’s currently running the latest fixes, some of which are relevant to a intermittent lockup of the keyboard.RobParticipantFebruary 19, 2017 at 09:06Post count: 13
This issue sounds a little different, but I tried customizing my layer images from the controller git repository. Flashing one half was fine, but when I flashed the 2nd half, the slave couldn’t change layers consistently. The layer change keys were unreliable, either doing nothing or locking when they should have shifted. The left side display also only flashes, but doesn’t change color or show the layer icons.
I tried fixing it by loading a new image downloaded from the configurator on February 17. It did clear my custom images, but the layer issue persisted. Today I flashed using a older image from February 12, and it resolved my issue. I’m wondering if the update referred to on February 13th or 15th has some bugs.Jeremy BondesonModeratorFebruary 20, 2017 at 17:17Post count: 48
Just a note here as well, the issue with the Ergodox Infinity slave is fixed and updated, so people would be encouraged to try the new version again.daantjieParticipantJuly 18, 2017 at 11:42Post count: 1
I have exactly the same problem as the OP. I hadn’t updated the fiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
firmware for a while now, but it started happening after I’ve been moving the keyboard around and plugging it into another (Windows) machine – I’m running Arch Linux. I’ve tried loading the firmware with the alpha version of the I:C configurator, and that hasn’t happened.
master, but I can’t get that to build. I’ve also tried the advice at the bottom of issue #204, doing selective
checkouts. This is the error I get:
[ 96%] Linking C executable kiibohd.elf
CMakeFiles/kiibohd.elf.dir/Scan/ISSILed/led_scan.c.obj: In function `I2C_Send’:
/home/daniel/hotfix/controller/Scan/ISSILed/led_scan.c:591: undefined reference to `I2C_BufferCopy’
CMakeFiles/kiibohd.elf.dir/Scan/ISSILed/led_scan.c.obj: In function `LED_setup’:
/home/daniel/hotfix/controller/Scan/ISSILed/led_scan.c:392: undefined reference to `I2C_setup’
CMakeFiles/kiibohd.elf.dir/Scan/STLcd/lcd_scan.c.obj: In function `LCD_clear’:
/home/daniel/hotfix/controller/Scan/STLcd/lcd_scan.c:241: undefined reference to `LCD_clearPage’
CMakeFiles/kiibohd.elf.dir/Scan/STLcd/lcd_scan.c.obj: In function `LCD_setup’:
/home/daniel/hotfix/controller/Scan/STLcd/lcd_scan.c:298: undefined reference to `SPI_setup’
CMakeFiles/kiibohd.elf.dir/Macro/PartialMap/trigger.c.obj: In function `Macro_evalTriggerMacro’:
/home/daniel/hotfix/controller/Macro/PartialMap/trigger.c:293: undefined reference to `Macro_evalLongTriggerMacroVote’
/home/daniel/hotfix/controller/Macro/PartialMap/trigger.c:294: undefined reference to `Macro_evalShortTriggerMacroVote’
/home/daniel/hotfix/controller/Macro/PartialMap/trigger.c:350: undefined reference to `Macro_isLongResultMacro’
CMakeFiles/kiibohd.elf.dir/Macro/PartialMap/trigger.c.obj: In function `Trigger_process’:
/home/daniel/hotfix/controller/Macro/PartialMap/trigger.c:474: undefined reference to `Macro_updateTriggerMacroPendingList’
CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj: In function `CLI_init’:
/home/daniel/hotfix/controller/Debug/cli/cli.c:79: undefined reference to `prompt’
CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj: In function `CLI_tabCompletion’:
/home/daniel/hotfix/controller/Debug/cli/cli.c:393: undefined reference to `prompt’
CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj: In function `CLI_retreiveHistory’:
/home/daniel/hotfix/controller/Debug/cli/cli.c:446: undefined reference to `prompt’
CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj: In function `CLI_process’:
/home/daniel/hotfix/controller/Debug/cli/cli.c:188: undefined reference to `prompt’
collect2: error: ld returned 1 exit status
make: *** [CMakeFiles/kiibohd.elf.dir/build.make:688: kiibohd.elf] Error 1
make: *** [CMakeFiles/Makefile2:137: CMakeFiles/kiibohd.elf.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
Error in make. Exiting…
This is all quite distressing[[FROZEN]]
to me, as it’s always worked absolutely fine before, and, frankly, I paid a lot of money. What’s going on? Is there any movement to getting this fixed?
You must be logged in to reply to this topic.