Author Topic: OrCAD / Allegro to KiCad?  (Read 8956 times)

0 Members and 1 Guest are viewing this topic.

Offline timofonic

  • Frequent Contributor
  • **
  • Posts: 904
  • Country: es
  • Eternal Wannabe Geek
 
The following users thanked this post: Wrydog

Offline Wrydog

  • Contributor
  • Posts: 27
  • Country: us
Re: OrCAD / Allegro to KiCad?
« Reply #1 on: November 17, 2016, 12:16:56 pm »
Bump.

I'm looking too.
 

Offline richardlawson1489

  • Regular Contributor
  • *
  • Posts: 125
  • Country: us
    • PCB Assembly
Re: OrCAD / Allegro to KiCad?
« Reply #2 on: December 30, 2016, 05:48:03 pm »
Thanks for the information. This is really helpful to all.
 

Offline technotronix

  • Regular Contributor
  • *
  • Posts: 211
  • Country: us
    • PCB Assembly
Re: OrCAD / Allegro to KiCad?
« Reply #3 on: January 02, 2017, 11:19:54 pm »
 

Offline PCB.Wiz

  • Frequent Contributor
  • **
  • Posts: 319
  • Country: au
Re: OrCAD / Allegro to KiCad?
« Reply #4 on: January 11, 2017, 01:59:16 pm »
Are there more projects or ways to translate Cadence OrCAD/Allegro to KiCad?
I just found this...

https://github.com/fjullien/rnif2ki
Orcad to KiCAD netlist converter
Mar 13, 2015

Netlists should not be too hard, but you will need to correlate the library-convention-names.

In parallel with NetLists, which pass connectivity,  I've tried the GerbView to KiCad and that has promise.
The appeal of Gerber, is you can import almost any CAD format, at least to the view it and copy stage.

Right now, it works - but makes some bad default decisions, so any flashed pad passes as a Via (even SMD ones) and it does not preserve the PAD copper but instead replaces with a Via of Max size.
ie this can work, on a 100% thru hole PCB, with all round pads to the point you can edit and create a new PCB.
BOM side, is not so great, as the footprints are exploded.

Smarter would be some simple rules like
* Always export copper that forms PAD (so KiCad can plot a PCB the same )
* Add via, only if Drill info says to. Via can be PAD smallest width & use Drill info.

IIRC KiCad can post-merge netlist info, you can can add footprints, delete the vias, then import NET and the traces 'connect'.

I see Netlist in Gerber is close too..., which would improve Gerber paths further.

https://en.wikipedia.org/wiki/Gerber_format
"In July 2016 Karel Tavernier from Ucamco published a draft specification to include netlist information in Gerber for public review. After a number of revisions of the draft triggered by input from users the draft was finalized on October 2, 2016."
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf