- Python 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| plugins | ||
| resources | ||
| manual.webm | ||
| messup.png | ||
| metadata.json | ||
| README.md | ||
| start.png | ||
| target.png | ||
Kyperspace
KiCad routing in hyperspace. Because it creates traces that won't appear on your board.
TL;DR
Route your nets using 0Ω resistors, without having to place them on the schematic.
This plugin simplifies the clickfest you'd have to do manually to prevent KiCad from overzealously removing your components or traces.
Description
With this plugin, you don't have to modify the schematic to place 0Ω resistors.
Also, you will no longer accidentally clean up your bridge resistors or traces when using board tools. And the DRC won't complain!
The catch: due to fake vias (and lack of customization), this only works well for 1-layer boards.
To connect two traces of the same net with a bridge resistor:
- Place both traces. Make sure the ends are unconnected, like this: |— —|
- Place a 0806 or 1206 SMD resistor on the open ends of the traces. DO NOT change its value.
It should look like this:
- Finally, press the plugin icon.
The plugin will:
- Find all 0806 and 1206 reistors with default values
- Mark them as not on schematic
- For all such resistors, find pads which overlap ends of existing traces.
- Assign the pads the same net as the trace it's overlapping.
- Place a hyperspace trace joining the pads
- Place a wormhole to hyperspace on the pads. Just kidding. It's a regular via you can't get rid of.
Which is a lot of clicking if you look at the video:
FAQ
What's wrong with putting your 0Ω resistors on the schematic?
A 0Ω resistor is not a component, it's a track that you route. And routing decisions should not influence the schematic. Imagine to declare all your vias and traces. Just no.
Isn't this fighting KiCAD?
Perhaps. Suggestions for a better tool welcome.
What KiCad meltdowns does this prevent?
When you place your 0Ω resistor manually and then clean up tracks, the tracks will be gone up to who knows where. Unless pads have the correct nets.
What you want:
What you get:
When you update the board from schematic, the bridge will get removed. Unless you mark it "not in schematic".
When you check connectivity, KiCad will shout. Unless you route a redundant track parallel to your bridge – in hyperspace of an extra Cu layer. With corresponding vias.
I want 0Ω resistors as bridges on my own 2-layer board!
Great! You need to change the Cu layer used for hyperspace. That's easy.
What's worse is that fake vias will still cross all layers, fucking up your routing on the back layer. I don't know of any way to avoid this in KiCad.
This sucks, who's going to use it?
Works for me.
If you find this useful, feel free to send patches.
License
AGPL 3.0.
This project is part of the DFSIODHANR effort (Dorota Finishes Stuff Instead Of Doing Half And Never Returning)


