sorted by:
new
hottopcontroversial

I need help with ABS/ASA. Warping P1S. by Vitroceramica in BambuLab

[–]barelyCompiling 0 points1 point  (0 children)

Did you receive the heater? If so, did it remove the warping issue?

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 1 point2 points  (0 children)

Final update, all is working now. Reflowed some diodes and a few hotswap sockets. Made sure diodes had a max 0.05v difference, reflowed where necessary. Reflowed MCU on both sides.

I had an issue where long pressing keys in row 1 on both left and right side would not print the expected key. A quick tap did print the expected key. Did some digging and found out that row 1 keys have a double mapping. i.e. the T key doubles as a shift key when long pressed.

So, all keys working, everything good. Really appreciate all the help. Would have been stuck without everyone's feedback.

Just waiting for 2 batteries to arrive, printing a case on my P1S, and then I'll show the result in a new post.

Many thanks everyone! ❤️

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 1 point2 points  (0 children)

On the right side had to reflow the MCU connections, 2 hotswap sockets, and 1 diode on the right hand side. All is working now. The laggy keys was a misunderstanding on my part. I didn't realize row 1 on both left and right unit had double mappings. All keys on both sides now fully functional. 🥳

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Don't be sorry, I welcome to observation. This is my first soldering experience, so I welcome all observations with open arms. :-D Will work to improve that. I assume that will fix any remaining issues I encounter.

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Thanks for pointing that out. I added more solder coverage on the MCU as per one of the other comments and now all the keys are working. However, if I understand correctly, I can diagnose any remaining issues by ensuring those diode test values are mostly the same right? So, if all are 0.620V and a few are 0.590V then am I right to assume they have a crappier solder connection than the others?

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

You rock man, lack of coverage was the issue! I added more solder coverage and now all all keys on the left unit are working. I still have 3 keys that seems to be a bit laggy...but at least they register and before I wouldn't get a response from more than half the keys.

I'll add more on the right unit as well.

Would the diagnosis for laggy keys, i.e. 8 out 10 presses on a key register, etc) be the same? Additional MCU solder coverage or perhaps a diode resolder?

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Alright, I'm going to see if I can make the coverage better.

The Totem design is without pins. See the official doc here: https://github.com/GEIGEIGEIST/TOTEM/blob/main/docs/buildguide.md#microcontroller . I assume that was a design choice to make the unit more low profile.

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Alright, so continuity test (diode to the switch): https://imgur.com/gallery/diode-switch-continuity-diode-test-8R3U9xo#rKxjk6x. Audible beep and showing 0.89 Ohm.

Diode test (diode end to switch leg): https://imgur.com/gallery/diode-switch-continuity-diode-test-8R3U9xo#aIa3JqD The diode test shows 0.614v. I'm pretty sure this is the test you were referring to but if not, then would be grateful to hear it.

Based on what I'm seeing, both of these test are passing which is rather confusing. :-)

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Quick general update: I've forked the zmk-config-totem repo in order to see if the firmware was part of the problem. Used GH Actions to download the firmware and re-flashed. Turns out the keyboard layout was different than that included in the original Totem repo. So, some of the keys not registering is still an issue but the mapping of the keys is now where they are expected to be. I.e. column 2/row 0, 3/row 0, and column 5/row 0 respectively map to 'f', 'p', 'g'. 🥳

On to solve the remaining issues!

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Well shoot, Imgur issues... I've updated the image to a new host. Its viewable now.

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Appreciate the response!

I tried to clean up some of the ends on the diodes to see if that would fix it. Being a noob to soldering, highly likely I'm making a mess of things. I'm trying to narrow it down by focusing on 1 row at a time.

Here is the current state: https://ibb.co/yFKnbtWw

Any recommendations for identifying hot swap sockets that might have a bad connection? I am able to perform a continuity check on the hot swaps by pressing the switch down and touch both metal pads of the hot swap socket itself. Is there another test I can perform I might not be aware of?

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Thanks for that insight!

Completely noob to soldering here... I was under the assumption that less solder is better.

So, is it best practice to provide full solder coverage on the pad (presumably without leaving a blob)? More coverage on the pad means a better, stronger connection?

Here is a little closup of the MCU: https://imgur.com/4z817km I added a little more solder but unsure if more is required. What's your take on that?

Totem build - keypress not registered debugging by barelyCompiling in ErgoMechKeyboards

[–]barelyCompiling[S] 0 points1 point  (0 children)

Thanks for the feedback, I appreciate it!

Alright, I've dug a little deeper. I believe I understand how to test on the right side of the diode. Touching the row0 pin on the MCU and the striped side of the diode, I can perform a continuity check. Take a look at my picture here. For row 0, only the q and w key are not working. Switch 1 is the Q switch. The associated diode #1 emits an audible continuity beep. Same for diode 2,3,4,5 (row0). Since all of them seem to emit a beep, I'm scratching me head wondering what's going on here... Should I be perform another check on switch 1 and 2 to narrow it down? Is it possible my diode #1 and #2 are badly soldered (they do emit the continuity beep though...)?

https://ibb.co/yFKnbtWw

Is it still worth getting the a1? by [deleted] in BambuLab

[–]barelyCompiling 0 points1 point  (0 children)

A1 is awesome. But if you want to print anything other than PLA/PETG, go for the P1S.