Replies: 17 comments
-
|
Interesting! I've been using keymaps from the jellytitan folder - but i vaguely remember something like that happening, and switching the keys. I'll recheck the keymap matrix today and let you know what i find. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I found and fixed a switched matrix config: I just pushed up the fix to my QMK sofle_pico. I haven't updated the Uf2 files in this repo though - so the drag and drop config is still outdated. If you want to try that method of flashing - i'll update them now. Since your OLED's are soldered - do you still have access to the |
Beta Was this translation helpful? Give feedback.
-
|
That was it! I have my own config going already at https://github.com/uberrice/qmk_firmware . Just updated it to all the last week's changes. Still learning how to handle QMK config as I go, but it's going well!
My current setup. One thing I noticed - the new QMK logo you added, at least on my screen, seems like it has lines that are too long. it seems like it's overflowing, making 'jaggies'. Is that something in-progress? |
Beta Was this translation helpful? Give feedback.
-
|
By the way, I properly socketed the OLEDs now - if you try to solder them in directly, the pins are awfully short anyways. |
Beta Was this translation helpful? Give feedback.
-
|
Your setups looking great so far! I'm having intermittent issues with |
Beta Was this translation helpful? Give feedback.
-
|
The OLED issue was simply me not understanding you actually need to add it to your config ;) the 'noise screen' is the startup sequence, the screen being updated chunk by chunk. I noticed that if right is the usb-connected keyboard, the menu is upside down. Also, the qmk logo periodically appears on my right screen - is that on purpose? |
Beta Was this translation helpful? Give feedback.
-
|
As for intermittent issues - I also had that problem with other keys, in my case simply touching up the soldering somewhat fixed it (those solder joints were ugly!) |
Beta Was this translation helpful? Give feedback.
-
|
Oh. Also - no need to set a max RGB value - I changed it back to 255 and my board is not even getting warm with all of them on full blast for hours. |
Beta Was this translation helpful? Give feedback.
-
|
For the intermittent QMK logo - the root cause it the startup/sleep behavior. I haven't quite figured out how to resolve that. Thanks for checking on the max brightness of the LED's - I"ll crank that setting to max in the config, but leave it in there. (I expect it may be needed if the level shifter is bypassed). |
Beta Was this translation helpful? Give feedback.
-
|
Took a look at the config - seems like what is causing the 'startup behaviour repeating itself' is a fairly simple bug that you have introduced. bool oled_task_user(void) {
static bool finished_logo = false;
if ((timer_elapsed(startup_timer) < OLED_LOGO_TIMEOUT) && !finished_logo) {
// Display the logo for 5 seconds on boot.
if (is_keyboard_master()) {
render_logo();
} else {
render_qmk_logo();
}
} else {
// Display the current keyboard state.
if (!finished_logo) {
// Clears the OLED.
oled_clear();
} else {
finished_logo = true;
}
if (is_keyboard_master()) {
render_status(); // Renders the current keyboard state (layer, lock, caps, scroll, etc)
} else {
render_logo();
}
return false;
}
return true;
}The whole 'finished logo = true' thing needs to be in in the 'if(!finished_logo)' part. Also I don't get why you have the return true at the bottom - if you want to show errors, you would also need a return false in your if statement - but it is always going to be if or true, so you can just remove the return false above and change the return true at the bottom to false. The screen then go to sleep as wanted. |
Beta Was this translation helpful? Give feedback.
-
|
I have nothing to contribute but just read through the three issues you 2 have been discussing this on and it's great to see the collaboration. I'm a relative newbie to custom keyboards having only built a macropad so far but I hope to build this Sofle-Pico keyboard soon. Would it be mostly OK for me to order the current PCBs in their current state or should I continue waiting for more testing/revisions? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @LoopControl. I ordered my own revision (that got merged in at some point I think) - that definitely worked for me without any hw patches - the voltage shifter components are not needed, so you need to bridge the solder jumper on the board. I'd recommend using 6/7mm spacers or something. I used 8mm I think, which causes the board itself to be 'suspended' between the 3d printed plates. Other option would be to make the bottom plate thicker, with slots for the spacers to fit into down to the 'original height'. Once the switches are installed, it's no real issue anymore, however. I don't know what @JellyTitan changed since then other than the LED cutouts, he'll have to comment on that. |
Beta Was this translation helpful? Give feedback.
-
|
@LoopControl I'm delighted that you're interested! While the v3.5 release is working - I'd recommend waiting another week. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the responses. I'll wait for the newer revision before ordering the PCB. I've been looking at keycaps/switches and am thinking of these "low-profile" keys from Nuphy. Would these be compatible with this PCB? |
Beta Was this translation helpful? Give feedback.
-
|
@LoopControl
If you feel strongly about the gateron low profile footprint, I'd recommend waiting until the Sofle Pico is released and then forking the branch and adding the footprints yourself, or opening an issue with a feature request label so that it can be worked on someday. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not attached that much to the low-profile version and will pay more attention to make sure I get the non-LP keycaps/switches, thanks! |
Beta Was this translation helpful? Give feedback.
-
It seems like there is something not quite right with the config.
I am writing from the Sofle Pico right now, so, working it is!
However, at least for my board, it looks like two keys are swapped. Specifically the two keys on the right thumbcluster, left side - the big one and the one next to it. SW26 and 27. Whatever button press is configured for SW26 happens on SW27 and vice versa. Only happens on the right side. Any idea why? Do you have the same behaviour?
Beta Was this translation helpful? Give feedback.
All reactions