Altium import with hierarchic schematic

Hello !
I am not an Altium user but I wanted to have a look at an existing Altium project.
KiCad Import went well enough for my purposes (KiCad 9.0.3)

But when I try to save the schematic the resulting KiCad project includes only the first sheet.
It works when I save all sheets seperately as copies in the new KiCad directory and then reassign the sheet symbols on page 1 to the new locations.

Is this the intended workflow to rebuild the schematics structure ?

I think this question has been raised before but I found no answers/confirmation and I would like to know if my proceedings are correct…

Greetings from Chris

Hmm you seem to be correct. I can import the Altium project and the hierarchical schematic appears correct and navigable, but saving only persists the top-level.

Same thing happened to me. To fix it I had to go to the top level Kicad schematic sheet that was created by the import, and set the properties for each sub-sheet entity to point to the new schematic sub-sheet in the new directory that has the imported schematic sub-sheets. Then the proper sub-sheets showed up.

I have yet to try this that may work:
Make a copy of the Altium files: project file, schematic file, pcb file, etc., and put them into a new directory. Then use that directory for both the import input and import export directories during the import process. Maybe then the top level schematic file will have the correct file location pointer values. If that does not work, then I guess the above work-around will have to be used for now.

Just a note to the Kicad creation team: Thanks all the well-done work.

-Tim

OK, so that seems to be the current situation for importing Altium.

I also found Altium Schematics (possibly older ones ?) that can´t be opened at all.
KiCads error message is: “Header already parsed” and the sheet remains empty while PCB import looks good ?

Modern Altium schematics can definitely be imported.

If you don’t open GitLab issues for these things, including a copy of the offending file, plus as much other context as you can give, there is approximately 0% chance anyone can or will fix it.

If the file is somehow sensitive, you can mark issues on GitLab confidential and then only KiCad devs can see it. But ideally it would be a stripped-down minimal example that you can make public where possible.

2 Likes

Of course you are right !

I just thought someone might have already experienced this.
I am not authorized to give away any of the project files no matter how confidential.
And as I don´t have Altium I can not add useful information about versions etc.

I use KiCad “as it is” and I am generally impressed by the available functions !

1 Like

It’s probably quite easy to find a hierarchical design made in altium on github or elsewhere. If you can reproduce the fault in such a project, you can upload such a project too, or just a reference to the git repository. Just putting in a bit of effort this way to find a case that exposes a bug is valuable to the KiCad project as a whole.

This is already a reported bug: Incorrect hierarchical import from Altium project (#21173) · Issues · KiCad / KiCad Source Code / kicad · GitLab

2 Likes