u/Roppano

Image 1 — Bragging about my first complex soldering job
Image 2 — Bragging about my first complex soldering job
Image 3 — Bragging about my first complex soldering job
Image 4 — Bragging about my first complex soldering job
Image 5 — Bragging about my first complex soldering job
🔥 Hot ▲ 94 r/ElectricalEngineering

Bragging about my first complex soldering job

I have a project I made a PCB design for, and today I finally had the chance to assemble it. Can't test it properly yet, the built-in SMPS is the only sign of life it can give (I'm waiting for the cable I'll use to debug/flash the board), and it does show SOME sign of life (I'm measuring 0.89V instead of 1.1V).

This is a VERY amateur result, probably. I can see many places where I used too much solder, there's also flux everywhere, and some smaller components don't seem to align perfectly, but it's a start, and it isn't completely dead.

I made some design/part ordering mistakes, too. The buck converter at the narrow part of the board has a 10 uH coil soldered to it, but it's supposed to be 3.9 uH. So when I power this thing from the intended 9V battery, I get 3.8-4V instead of 3.3V, which is problematic for the reset pin, for example. The 3 connectors are placed so close together that the middle one is almost impossible to solder without burning both its neighbours. The 2 connectors at the top are too close to the edge, which means that I needed to use sandpaper on the opposite side for the board to fit into the enclosure I bought.

I loved using the test points I made. This is the first time I used them, and they're useful, even without actual logic running on the board, let alone when I finally get the debugging cable.

Overall, the job is messy, my desk is even worse, and everything is sticky. But I'm proud, nonetheless. Curious what you think, give me your best....or worst.

u/Roppano — 3 days ago
▲ 29 r/KiCad

KiCad 10 regressing for wayland?

I'm perfectly aware of the KiCad devs' stance on Wayland. At the same time, Wayland is encroaching on the ecosystem more and more, with GNOME 50 removing all X11 dependencies and many major distros following suit, abandoning X11 completely. I think it's time to reevaluate this attitude. I can see GitLab having a bunch of Wayland-related tickets, and I think it's about time the devs started prioritising them more.

I have 2 Ubuntu systems, one is 24.04 LTS with an AMD iGPU, the other is more on the edge with 25.10 with a discrete nvidia GPU. KiCad 9 was...usable on both systems, with slightly different, but not necessarily breaking behaviour.

But ever since KiCad 10 came out, I see regressions that make it borderline impossible to use. The biggest of which is that many windows are refusing to update. For example, in the BOM window, when I click on a checkbox to include a specific field, I need to scroll the field list before the change is actually visible. But scrolling isn't working well either, because when I click a checkbox after scrolling, the wrong checkbox is selected. It looks like the window is one step behind at all times.

Did you experience something similar? What's your opinion on KiCad supporting Wayland in general?

I have some programming prowess, and I'd be happy to help out with this, though I'm feeling really insecure at the moment :D

reddit.com
u/Roppano — 4 days ago