So it’s a bit of a dilemma - maintaining translators sucks and they're never accurate, but forcing people to use a script forces them to have at least a copy of the SW sitting around. The major issue is that to execute scripts, you need a license of OrCAD / Allegro. This makes a LOT more sense as it is much harder to abandon an API than to change a file format (which is done often to throw the competition off and to support new features). I’d like to also consider building a script to run in OrCAD that way we don’t “translate” files but rather, use the OrCAD API to ‘generate’ EAGLE files. A lot of energy is being put into this at the moment and we’re taking suggestions! Curious, what version of OrCAD / Allegro are you using? 16? 17? Next step, schematics and finally board files (hopefully, barring any ugly issues). The first step will be Orcad & Altium libraries. Thanks for your post! We’re working on it (it’s on the “wish list” for the coming year).
0 Comments
Leave a Reply. |