As shown in the image below, the kicad exported file(hyp) in the hyperlynx software is messed up.
Similar to the topic below, but I have version 9.0.3 with the same problem. Is there a solution for it?
1 Like
It is possible to check in 9.0.4 ? Or create a small example?
The following version does not have this problem, but it has been Y-Mirrored!
Version: 9.99.0-unknown-5e6ef67fce~182~ubuntu24.04.1, release build
KiCAD version 9.0.3 was on Windows
Night versions are not stable, check in 9.0.4 if the error persists, you can create a request to gitlab
This problem exists in version 9.0.4
I also updated to version 9.99 and it also has the same problem!
Version: 9.99.0-unknown-fb558eee3c~186~ubuntu24.04.1, release
1 Like
This looks very similar to a bug in the “fab 3000” (CAM 350?) software that was mentioned here years ago. There was a thread where even a PCB manufacturer joined in (I think it was JLC) and wrote something about using custom scripts to work around / fix bugs.
I wonder if these are all related in some way.
Apparently there is some ambiguity in the direction in which arc’s are defined.
I encountered a similar problem when exporting to IPC-2581 bottom pads are (sometimes) mirrored and rotated incorrectly vs. Valor/CST/Cadence/circuithub.com (#19703) · Issues · KiCad / KiCad Source Code / kicad · GitLab
1 Like
I have noticed the same problems. We have a circuit board that was developed in KiCad 7. We opened the circuit board with KiCad 9.0.5 (release build) and exported it to Hyperlynx. We imported the export into CST PCBs & Packages ( a programm for simulation signal integrity problems). During this process, we noticed that curves in the conductor tracks are displayed incorrectly in CST.
When I open the layout in KiCad 7 (7.05, Release Build) and then perform the Hyperlynx export, the arcs are displayed correctly in CST, but the entire layout appears mirrored on the x-axis.
1 Like
Unfortunately, it is not possible to open a PCB created with KiCad 9 in KiCad 7. So this is not a possible workaround 
.
One of the first things to figure out is whether this is an export problem of KiCad, or an import problem of Hyperlinx. But if it worked with KiCad V7 and not with KiCad V9, then it seems likely the problem is indeed on KiCad’s side.
Has any of you made a bug report for this on gitlab? (If so, then please also add crosslinks to keep the subjects together.
One option would be to create Gerbers from KiCad V9, then create a PCB from that in KiCad V7 and then export to Hyperlinx. It’s not a very elegant workflow, but for example comparing the files generated by KiCad V9 and V7 with each other can be a useful analysis tool.
Is it possible for you to create a trivial board with this issue in V7 that can be shared, and export from both V7 and V9 and then capture what CST shows?
The developers probably don’t have CST, so samples are very helpful
1 Like
Hello everyone,
I have created a simple example. KiCad7Test2.zip is the KiCad project created with KiCad 7.0.10 and KiCad7Test2.hyp is the exported Hyperlynx file. When I import these into CST, it looks like KiCad7ExportToCST_1.png and KiCad7ExportToCST_2.png.
KiCad9Test2.zip is the same project, which was opened with KiCad 9.0.5 and then saved.
KiCad9Test2.hyp is the Hyperlynx file exported from KiCad 9. When I import this into CST, it looks like KiCad9ExportToCST_1.png and KiCad9ExportToCST_2.png.
By comparing the export files, I found out where the error in the KiCad 9 export lies:
In Hyperlynx, an arc is specified as follows:
(ARC X1=….. Y1=….. X2=…. Y2=….. XC=….. YC=…. R=…. W=…. L=…)
X1 and Y1 specify the starting point of the arc, and X2 and Y2 specify the end point. If I swap the starting and end points, the arcs are displayed correctly in CST.
This is shown again in KiCad9ExportToCST_changed_1.png and KiCad9ExportToCST_changed_2.png.
I have corrected this in KiCad9Test2_changed.hyp.
I hope that this information will help to fix the error in the Hyperlynx export from KiCad 9.
Unfortunately, I do not currently have permission to upload files to this forum. Therefore, I have uploaded all of these files to the following GitHub repository so that everyone can view them:
1 Like
You can now.
Thanks for the samples, but it is best to raise an issue, as not all the developers are here and issues get tracked. It looks like you have found a bug.
I have just created an issue report.
You can find it here:
2 Likes