Yes.
freaking word limit fluff
Streamline hardware test
Advanced T&M remote control and analysis suite
Yes.
freaking word limit fluff
Unfortunately, I’ve only started to use it myself, so I’m still bumbling around too. But everything I’ve done so far has worked well…once I figured out how this piece of software thinks. Mostly parametric modelling of some large woodworking projects, then getting dimensions from it.
I have not tried to integrate it with anything outside of its ecosystem, so it’s entirely possible for that to be a deal-breaker. It does import a bunch of standard formats though, so maybe that could be an option…
Just thought I’d mention a possibility, is all.
I’d like the ability of saving/loading presets for plotting/fabrication output.
Without that, the risk of using the wrong options is too high. Unless you absolutely never change options. But if you use plotting frequently for different use cases, that IS going to happen.
I’d like the ability of saving/loading presets for plotting/fabrication output.
I’m astonished about how many of the wishes in these lists are already there, sometimes even in older versions. This one is in 9.0rc.
People, please at least read the development news thread(s) first.
I’d like to have a clear separation between “Design Relevant” settings and settings like window position, last open files, etc.
This would it make much easier to have the different config json files under source control.
The settings relevant to the actual design on the one hand and the settings for each user (UI etc.) are already mostly separated. The .kicad_prl file has the UI stuff and should be left out from version control, backups etc. If you find something which is in a wrong file, you can start a discussion about it in the forum or file it as an issue.
As eelik says, that’s been true for a while. See the file types documentation here for which ones you don’t need under version control.
Hi gkeeth and eelik
Thanks for your response. I know the different file types cause I am using KiCad since V4. As an embedded HW and FW developer I also now what files normally go into GIT. Maybe may wish above was not clear enough so I will try in other words.
In our small HW Team I would like to have a setting that all KiCad user have the same “Design Relevant” setup and that this cam out of GIT. Modification after a review go back to GIT.
The Idea is to symlink the local git repo to the KiCad setting location (as ex: ln -s ~/Desktop/eb-kicad/kicad ~/Library/Preferences/ on OSX).
This setup works beside the following things…
For me “Design Relevant” settings are: (jsut some to show the problem)
“Fancy Settings” are:
Now the problem is that “Design Relevant” and “Fancy Settings” are stored in the same files and therefore it is not possible to have them in GIT or it makes it at least very difficult to track/merge only the important things.
So it would be nice to split the different json files in static and dynamic files. The static files could then go easy to GIT.
I know the big discussion would be then to decide what settings go in which files.
Hope that helps to understand my idea.
Hi,
The possibility to have git integrated in the kicad UI for librarian, with a dedicated GUI related to the footprint generator that will help to filled all files linked and create footprint, 3d models, populates the merges request.
This to simplify the whole process and to recruit more librarian.
V9 will have support for exporting to XAO formats to SALOME:
Solid 3D model export improvements: Option to fuse copper geometry together Option to export copper on inner layers Options to exclude board body or components Net filter (can be used to export a single net) Zone geometry approximation with arcs for faster processing and smaller file sizes Export in BREP or XAO formats XAO defines pad surfaces as face groups and can be imported into SALOME or newer versions of Gmsh for FEM simulations: [image]
I agree, FEM simulation integration is definitely a direction we should be heading.
FYI, not sure if you noticed, there is support for export to SALOME coming in v9:
Solid 3D model export improvements: Option to fuse copper geometry together Option to export copper on inner layers Options to exclude board body or components Net filter (can be used to export a single net) Zone geometry approximation with arcs for faster processing and smaller file sizes Export in BREP or XAO formats XAO defines pad surfaces as face groups and can be imported into SALOME or newer versions of Gmsh for FEM simulations: [image]
Would be great if Kicad integrated simulation with ngscopeclient:
Advanced T&M remote control and analysis suite
This would improve visualization of simulations and workflow. For instance, after producing real product any custom signal processing you might want to do would already be setup. It also just generally seems like a smoother workflow, and you could directly compare your simulation to reality.
agree, FEM simulation integration is definitely a direction we should be heading.
May be a plugin approach similar to
Has anyone noticed this FEM plugin? [image] It seems very interesting…
could cover this…
@Drinausaur is there any chance to convert your code to a plugin?
However Kicad does not need this feature completely, may be rarely, because in Kicad you can select what ever you want objects.
Please, select all capacitors of 100nf with MPN 100nF/25 on a schematic of 9 pages and 625 components.
Altium also allow select multiple components too, is not the focus. There a lot of instances when you need a specific selection. If you use a snapeda footprint, with a lot of garbage fields (providers, alternatives, copyright… etc) maybe you want select all components with a field called “providers”.
The selection tool requested, is not mandatory of usage, is only a tool that can be usefull for the user.
If you want to select using “garbage fields”, wouldn’t you be better off using a Data Base?
I understand. Sadly many times you have to work with inherited projects. Or sometimes the work is to homogenize projects done by different people at different times.
As THT and SMD footprints are often radically different in size, I don’t see the value of an “alternate footprint”. Perhaps you want to have an SMD board and another THT board, with a common schematic. That is also a painful process as the underlying database of components would have to be duplicated and edited separately.
(little) Alignment aids:
Ever used a mac with Pages or Keynote? It draws crosshairs when moving a picture and snaps to the center relative to another object. It also snaps to the center of a page. You even feel a click in the trackpad.
In KiCad, if I want to make a board visual nice, I can do that with align in the context menu. Personally, I would like some more simple aids to easily align symbols or footprints.
When tracing multiple tracks along side, I have to manually try to evenly space them. Would like some automation with that. (Edit: I saw you can drag multiple tracks in v9 )
Trace a track between to pins and centering it between it takes more effort than I would like from a tool. It has to do with the grid of course, but it would be much more appealing if a trace runs through the middle.
To be clear, posts and hearts on the forum are at most a vibe check.
If you want to show support for a given feature, find it on Gitlab. Most features requested in these threads are already near the top of the popularity list here: Open issues by popularity. Then give it a thumbs up. Do not add a “+1” comment unless you have more information (“I want/need this too” and “any update on this?” is just noise).
Quick list of the big items in this thread I can see issues for:
Also see: Closed issues by popularity for completed big-ticket items. A lot of those were closed within in the last year (meaning they’re v9 additions). There are some things in this thread already done in v9:
There are more, and when there aren’t, do feel free to raise specific (emphasis on the specific) requests at Gitlab.
The good news is, many of these indeed are on the (informal!) v10 hitlist!
Thank you johnbeard for taking the time to summarize all in this post,
there are indeed some features requests for stuff i didn’t know i disparately need till now