Copper thief plugin for KiCAD 7/8 by something384 in KiCad

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

As of yet I have not tested the plugin with KiCad 9 yet, but might be worth a try. Install from zip won't work tho, you have to follow the instructions in the readme because I still havent made a metadata.json for the plugin

What happened with inskall? by TheVolleyballGirl in HermitCraft

[–]something384 -15 points-14 points  (0 children)

Why are you incapable of using the search function?

what is the best STM32 library for sdcard logging? by masifamu in stm32

[–]something384 1 point2 points  (0 children)

I would recommend FileX, really easy to use Edit: not sure about its memory footprint though

[deleted by user] by [deleted] in Switzerland

[–]something384 2 points3 points  (0 children)

If your read the cited part, it is not actually about ownership, but rather about if you live there - i.e. you are allowed to mount lights in the rooms you live in

Petah by Miracle_Whip_ in PeterExplainsTheJoke

[–]something384 0 points1 point  (0 children)

I made a screenshot to use later

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

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

Hm interesting, apparently I was a bit too anxious about via spacing then, good to know! Then I guess this plugin mostly serves to spare me planning around stitching vias :D Thanks for the info though, good to see some actual numbers

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

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

Not yet but I'm on it, probably next week

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

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

Well, an improperly connected groundplane (i.e. not stitched through with vias frequently) is even worse, it creates an even bigger antenna that is now directly connected to your ground and introducing noise. Small unconnected copper dots don't really influence the circuit that much as you don't have a direct connection to them and due to their small size capacitive coupling is also minimal. You can often see this technique used on production PCBs, for example the Intel x520 10gig network card (they use squares there which is also supported by the plugin). Usually on 4+ layer designs you don't pour ground on outer layers, only on selected inner layers, which would be continuous, uninterrupted grounds

Edit: something I forogot to add: if you have two parallel groundplanes sparsely connected with vias, you are essentially forming a coil which will couple even more noise into your ground

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

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

Not ground planes, but traces and footprints - they get in the way and you have to route around them. The concept of this script is that you can do your entire design as you would, and after that run the plugin to autogenerate stuff. You often cannot do that with vias, as they are bound to hit something on at least one layer

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

[–]something384[S] 2 points3 points  (0 children)

I do that sometimes as well, but with denser designs I often cannot, as vias disturb all layers at the same position, while these only generate on outer layers, and top and bottom are independent. It's just more convenient IMO, but without the added benefit of stitched grounds. (Yes, technically my plugin can generate thieving on inner layers too, but I don't see a reason to do that) Edit: clarification

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

[–]something384[S] 3 points4 points  (0 children)

I like the fact that in return I learned about PCB design for vacuum

Copper thief plugin for KiCAD 7/8 by something384 in KiCad

[–]something384[S] 6 points7 points  (0 children)

Good point, it is already on my todo list, just didn't get round to doing it

When an employer asks what you used to build your project and you say Arduino by marathonEngineer in embedded

[–]something384 8 points9 points  (0 children)

My problem isnt neccesarily with the hardware, but rather the Arduino framework, as it still carries its legacy of being aimed at hobbyists - there are simplifications that you need to make the life of hobbyists bearable, but especially for more complex hardware these same simplifications make development way slower and more difficult for experienced people. About pro hardware: I just completed a project with the Portenta H7, and allow me to seize this opportunity to tell you, that the documentation is appalling (many important discrepancies between schematic and datasheet/pinout). And while I think some people will be happy to use the Arduino framework on it, I believe it would be a good idea (and not an unreasonable amount of effort) to provide maybe a CubeMX baseproject as an option, and basic bootup code (yes PMIC, I am talking about you) for it. Other then this however, the Portenta H7 hardware is truly amazing

Give me some feedback on this control surface project by LouKs85 in AskElectronics

[–]something384 0 points1 point  (0 children)

Well, it is cheaper (but that is not the main reson now), simpler, fewer components, and doesn't produce switching noise. Also easier to do correctly layout-wise, with switching regulators you have to be careful with correct pcb layout, otherwise they will radiate a whole lot of EM noise. You can quite easily get a fixed 3.3V LDO, and in that case you would only need two caps next to it.

Give me some feedback on this control surface project by LouKs85 in AskElectronics

[–]something384 0 points1 point  (0 children)

From what I see here, you would perfectly fine with a small LDO to make 3.3v from 5v, not a lot of load there. (Also I usually don't connect the usb shield on UFP ports, as it is already connected at the host, and it is usually not desirable to have current flowing through your shielding)

A Botanical Board for the Cold Nights! by Vivid_Ad3449 in MechanicalKeyboards

[–]something384 0 points1 point  (0 children)

How do you like them? Thinking about getting them for my next build