Showing 1 of 2440 conversations about:
zoopthorton
2
Feb 20, 2017
bookmark_border
Anyone tried flashing a new layout? Ever since I did, the 'slave' board's LCD doesn't update to show the current layer.
Feb 20, 2017
domesdkg
9
Feb 20, 2017
bookmark_border
Did you flash both halves? You need to.
Feb 20, 2017
zoopthorton
2
Feb 20, 2017
bookmark_border
Yes. Both halves were connected separately to the computer and flashed with the left and right bin created by the input club configurator tool.
The issue doesn't affect just one hand, either hand as the 'slave' keyboard has the same issue. The LCD will dim when changing layer on the master and changing the layer with a button on the slave isn't always registered. Individually (not daisy chained) the boards work correctly, and the config is applied, it's only an issue when daisy chaining them.
Feb 20, 2017
mershaqdiesel
1
Feb 20, 2017
bookmark_border
I have the same issue. It also seems like the function keys lock on the slave board, and there is a massive delay in recognizing the function press between boards.
Feb 20, 2017
shultzy
2
Feb 20, 2017
bookmark_border
Same issue here when I daisy chain both halves.
Feb 20, 2017
rcmosher
3
Feb 20, 2017
bookmark_border
Zoop, already sent you this on input club, but for everyone else...
Here's my <a href="https://spideroak.com/storage/OVPXG4DJMRSXE33BNNPWC5LUN5PTCOBRGQZDE/shared/1293635-3-116909/02122017MDErgo1-Default-809090f631efafa017c6daa0ce46b6ab.zip?f6ead8579137bdba9409eaf37d3daa76">current image</a>. I'll try to find one closer to the default when I'm home. Let me know if this is still buggy as I may have grabbed the wrong image off my phone.
You can use "import map" in the configurator and copy in the .json file to see what it looks like, but the general philosophy is: Main Layer: normal keyboard modified for Ergodox layout. Also Capslock is replaced with Esc cause I use vim. Layer 1: Right half is arrow keys and other movements. Left half is media keys, and other misc. Used the f1 key as a shift key instead of locking. Layer 2: Right half is number keys. Layer 3: Halves are swapped so you can reach (most) any key from one half. Layer 4: Flash keys in upper-outer corners. And has NKRO and LED keys which I don't really use.
Also, since I'm guessing this is your first Ergodox Infinity, here's a tip. The quickest way to flash both halves of your keyboard is to plug both halves directly into your computer, not one chained through the other. Flash each side, one at a time, with the correct file for the half. Then disconnect one half and chain it to the other when you're done. Though this isn't great for detecting bugs like we're seeing with current files.
Also, use "sleep" on linux ("timeout" on widows, I think) to delay when the flash happens so you can switch into flash mode after hitting enter at the command prompt if your only keyboard is your Ergodox. Though, now that I think about it, the windows tool isn't command line.
And you should always flash both halves once you've confirmed it works on one half. I had some earlier issues that resolved (perhaps coincidentally) after I put the image on both halves.
Feb 20, 2017
rcmosher
3
Feb 20, 2017
bookmark_border
I should say for everyone here, the image above is a current working image I have that I created before this bug showed up. Though it's very different from the Ergodox default
Feb 20, 2017
zoopthorton
2
Feb 20, 2017
bookmark_border
Was this image one you created through the online configurator, or did you create it some other way?
It solved the issue to me, so I'm thinking the tool may have a bug, instead of it being a hardware (i.e. cable) issue
Feb 20, 2017
zoopthorton
2
Feb 21, 2017
bookmark_border
@shultzy @mershaqdiesel
The configurator has been updated, and I can confirm it's been fixed.
Feb 21, 2017
rcmosher
3
Feb 21, 2017
bookmark_border
I used the configurator. And it appears to issue has been fixed for files created with the configurator (and I assume using the git repository files directly).
Feb 21, 2017
View Full Discussion