I am a KiCad user, should I switch to Horizon and why?
From the docs it seems like your main selling point is a better library, why not just make a better library for KiCad?
I only got to know about LibrePCB at the end of 2016 after several months of development on Horizon EDA. While there are some similarities such as the use of UUIDs and strong link between schematic and netlist, there are major architectural differences such as Horizon EDA using raw OpenGL vs QTSceneGraph(?) and Gtkmm vs QT.
As far as I can tell, the development models also differ significantly: The LibrePCB devs seem to be focused on doing things the right way the first time such as having a proper operation-based undo/redo stack whereas horizon just stores a copy of the whole schematic/board for undo/redo. They also seem to focus more on simplicity for beginners rather than more advanced features such as length tuning and advanced design rules.
Putting development effort where I like enabled me do to the board for my master thesis https://github.com/carrotIndustries/x-band-tx/ (4 Layers, differential pairs, length-matched traces) in Horizon EDA only after about 2 years after the initial beginning of development.
1. Yes it does, has even a Annotation mode to add sheet increments for part numbers (e.g. R101, R102, etc for the first sheet, R201, R202, etc for the second sheet). Pasting between sheets works, having multiple gatesn (e.g. of a hex inverter) spread out over multiple sheets works as well.
2. yes, including global or per-net rules for thermal relief, spacing etc. It warns you if nets have not been recalculated on Fabrication output. Adding them is simply: draw a polygon, right-click and "Add Plane", there you have to select any names net.
3. there is length tuning built in, but quite frankly I never had to use it, so I don't know if that is what you're looking for
1. Does Horizon support an equivalent to the 'Variant Manager?' This is something that will allow variance of build outputs (different component populations, different schematic text, etc).
2. In the docs it seems to mention submitting parts to the default pool. If people submit parts to the pool are there style guides somewhere? (line widths, US vs EU resistor symbols, etc)
3. Looking at a random SMD footprint (SOT-363) it looks like the paste window is equal to the pads. Is there a way to set paste mask expansion like is done in Altium? (Automatically offset paste window from pad by some amount)
1. Opening up your first project is not straightforward. Instead of just opening with a blank project and letting you add a resistor, the app asks a lot of rather irritating and irrelevant questions (who cares who the "author" is at creation time, and couldn't it guess anyways?) that could be better decided later. Worst offense: the "create" button is grayed. As in: nope, you won't be able to use me until you answer all the useless trivia.
2. Horizon seems to cling to the "main window launches sub-apps" paradigm (much like kicad). This is a rather confusing UX workflow. At the very least, it clutters up your desktop. Why can't all sub-app live under one roof ? I mean even gimp has finally given up on the broken multiple top window idea ages ago.
3. Couldn't find any standard old-timey thru-hole parts in the default "pool": 2N2222, 2N3904 standard, LEDs. Not fashionable these days for serious work, but still very much in demand by the hobby crowd.
4. To place a part, it looks like you have to select the *exact* component you need right away. Why? . Why can't I just place a generic NPN in the diagram and then refine what part it'll actually be later on ?
5. The part browser : why so many search boxes ? I want a Google-style single search box that's smart enough to match what I'm saying to a given part. Finding a part shouldn't be like entering an SQL statement. Fuzzy matcher please.
6. Right-click on a component: a mile long menu, no "part properties" entry. When I finally locate the "change symbol" entry (in a sub-menu), it sends you to a subtly different UI than the part browser.
7. No navigation buttons in sight. Where's "Frame All", "Frame component"
8. Components are hard (near impossible) to just grab-and-move
I'll have to play with it more, but the initial interaction with the UX is kinda icky.
[edit]: forgot to mention installation. On ubuntu, this was not exactly straightforward. Choice between installing a binary through flatpak (non-standard thing I don't have) or building from scratch (there went 30mn of my day). Almost made me open the windows laptop that's specifically reserved for running win-only crapware.
- on 1: Starting projects: for me it is only entering a project title and selecting a path, which is reasonable unless you are the type who wants to decide things like these in the end on saving.
- on 2: While I also like single window concepts better (with panes like Blender), I think having schematic, board and pool/library editors in seperate windows is kinda reasonable.
- on 4: You actually can. You are not forced to use existing parts if you use "Place component"
- on 6: Given how the whole thing works, such a thing like "Part properties" doesn't really make sense. In Horizon everything you place on the schematic is either a generic unit (E.g. "Two-terminal resistor") where you can enter a value or a existing part mapped to this generic unit (e.g. a "ERJ-6ENF2003"). This is (on purpose) different from how other EDA-tools do it, but in practise it works quite well. The point on the different assign window is something I'd like to have changed as well : )
- on 8: if you want to move something you have to use the move tool which you invoke by pressing the m key. You can also move things with the arrow keys.
Generally the UX paradigm of horizon is very much built around single key shortcuts or key sequences. And if you don't know the keys just press the spacebar and search for the command and it will tell you right there.
As for now the experience for power users is very fluid, but when it comes to installation, onboarding etc. the whole thing could use a lot of improvement (and are gladly beeing worked on).
Gtk's and horizon's OpenGL requirements (3.3 core profile + extensions) likely aren't met by whatever graphics adapter your VM implementation provides.
Nice work! The world badly needs a FOSS EDA program that isn't insane.
Any plans for Mac downloads? And also, does its component model separate out schematic symbols and pin assignment (like DesignSpark PCB and I assume others) or are they inseparable (like KicadPCB)?
When producing a placement file for a PCB, can component part numbers be exported ? Neither Cadence, nor KiCAD stores components in their PCB files, only footprints, so part numbers cannot be easily accessed.
osamagirl69|5 years ago
karotte|5 years ago
Starting from scratch also allowed me to trivially implement features that KiCad is missing, such as proper panelisation: https://blog.horizon-eda.org/progress/2020/04/05/progress-20...
popped|5 years ago
Differential pair routing
Pin swapping... ie a differential pair where the pins can be reversed
Pin agnostic routing, ie a MCU or FPGA where it doesn't matter which pin is used
Incremental part placement, unlike kicad where all the footprints get dumped on the board in a big mess at the start
These are things that bother me most in kicad (it does have diff pair routing)
Thanks - looking forward to taking it for a spin
karotte|5 years ago
Yes, uses KiCad's push&shove router
> Pin swapping... ie a differential pair where the pins can be reversed
Not really, but swapping P/N in a diffpair is as easy as selecting nets in the schematic and using the "swap nets" tools.
> Pin agnostic routing, ie a MCU or FPGA where it doesn't matter which pin is used
Not really, but you can draw the connections in the board editor and backannotate them into the schematic: https://horizon-eda.readthedocs.io/en/latest/backannotation....
> Incremental part placement, unlike kicad where all the footprints get dumped on the board in a big mess at the start
Yes, there's list showing all currently unplaced packages: https://imgur.com/ZrvRw46
stickac|5 years ago
karotte|5 years ago
As far as I can tell, the development models also differ significantly: The LibrePCB devs seem to be focused on doing things the right way the first time such as having a proper operation-based undo/redo stack whereas horizon just stores a copy of the whole schematic/board for undo/redo. They also seem to focus more on simplicity for beginners rather than more advanced features such as length tuning and advanced design rules.
Putting development effort where I like enabled me do to the board for my master thesis https://github.com/carrotIndustries/x-band-tx/ (4 Layers, differential pairs, length-matched traces) in Horizon EDA only after about 2 years after the initial beginning of development.
nrclark|5 years ago
1. Does the schematic editor support multi-page schematics? Kicad's hierarchical-block approach always feels needlessly clunky to me.
2. Does the PCB editor support planes and copper pours?
3. Does the PCB editor have anything to help estimate a line/diffpair's characteristic impedance?
atoav|5 years ago
2. yes, including global or per-net rules for thermal relief, spacing etc. It warns you if nets have not been recalculated on Fabrication output. Adding them is simply: draw a polygon, right-click and "Add Plane", there you have to select any names net.
3. there is length tuning built in, but quite frankly I never had to use it, so I don't know if that is what you're looking for
rta5|5 years ago
1. Does Horizon support an equivalent to the 'Variant Manager?' This is something that will allow variance of build outputs (different component populations, different schematic text, etc).
2. In the docs it seems to mention submitting parts to the default pool. If people submit parts to the pool are there style guides somewhere? (line widths, US vs EU resistor symbols, etc)
3. Looking at a random SMD footprint (SOT-363) it looks like the paste window is equal to the pads. Is there a way to set paste mask expansion like is done in Altium? (Automatically offset paste window from pad by some amount)
karotte|5 years ago
No, but there's been some discussion on it: https://github.com/horizon-eda/horizon/pull/347#issuecomment...
> 2. In the docs it seems to mention submitting parts to the default pool. If people submit parts to the pool are there style guides somewhere?
There's https://github.com/horizon-eda/horizon-pool-convention, but that's still work in progress.
> 3. Is there a way to set paste mask expansion like is done in Altium?
Yes, you can set it globally in the board.
ur-whale|5 years ago
[edit]: forgot to mention installation. On ubuntu, this was not exactly straightforward. Choice between installing a binary through flatpak (non-standard thing I don't have) or building from scratch (there went 30mn of my day). Almost made me open the windows laptop that's specifically reserved for running win-only crapware.
atoav|5 years ago
- Navigation Buttons: I proposed a solution here: https://github.com/horizon-eda/horizon/issues/119#issuecomme... This is part of the effort to add icons and toolbars to things that right now are reachable behind the spacebar menu
- Many TH (as well as audio/synthesizer-related) parts can be found in the work branch of my fork of the offical pool: https://github.com/atoav/horizon-pool/tree/work The offical library/pool only includes parts that have been checked by four eyes, so many parts are still open as Pull requests: https://github.com/horizon-eda/horizon-pool/pulls
As for the other points:
- on 1: Starting projects: for me it is only entering a project title and selecting a path, which is reasonable unless you are the type who wants to decide things like these in the end on saving.
- on 2: While I also like single window concepts better (with panes like Blender), I think having schematic, board and pool/library editors in seperate windows is kinda reasonable.
- on 4: You actually can. You are not forced to use existing parts if you use "Place component"
- on 6: Given how the whole thing works, such a thing like "Part properties" doesn't really make sense. In Horizon everything you place on the schematic is either a generic unit (E.g. "Two-terminal resistor") where you can enter a value or a existing part mapped to this generic unit (e.g. a "ERJ-6ENF2003"). This is (on purpose) different from how other EDA-tools do it, but in practise it works quite well. The point on the different assign window is something I'd like to have changed as well : )
- on 8: if you want to move something you have to use the move tool which you invoke by pressing the m key. You can also move things with the arrow keys.
Generally the UX paradigm of horizon is very much built around single key shortcuts or key sequences. And if you don't know the keys just press the spacebar and search for the command and it will tell you right there.
As for now the experience for power users is very fluid, but when it comes to installation, onboarding etc. the whole thing could use a lot of improvement (and are gladly beeing worked on).
luckydata|5 years ago
Glib::Error: No GL implementation is available.
Couldn't find much to help me out figure out how to fix that issue, I assume it's some missing dependency but... where do I go from here?
karotte|5 years ago
atoav|5 years ago
IshKebab|5 years ago
Any plans for Mac downloads? And also, does its component model separate out schematic symbols and pin assignment (like DesignSpark PCB and I assume others) or are they inseparable (like KicadPCB)?
atoav|5 years ago
This is a good summery (with a nice graphic of the structure of an example part): https://horizon-eda.readthedocs.io/en/latest/pool-why.html
ruslan|5 years ago
When producing a placement file for a PCB, can component part numbers be exported ? Neither Cadence, nor KiCAD stores components in their PCB files, only footprints, so part numbers cannot be easily accessed.
karotte|5 years ago
StavrosK|5 years ago
mkj|5 years ago
mbrumlow|5 years ago
Why should I learn Horizon vs Kicad first, or vise versa?
karotte|5 years ago
- library management that makes sense (though is a bit more complex than KiCad's)
- clean and modern UI
- fast-paced development (if there's a suggestion, that makes sense to me, I'll implement it)
pro KiCad:
- large library of parts
- has been around for a long time, so for every problem you may encounter, there's likely a forum post or so that describes a solution/workaround
- larger community