• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. Need Help Exporting ODB++ from OrCAD 16.2 Layout – GW2ODB...

Stats

  • Replies 12
  • Subscribers 163
  • Views 4770
  • Members are here 0
More Content

Need Help Exporting ODB++ from OrCAD 16.2 Layout – GW2ODB Executable or Alternatives?

Davide98
Davide98 8 months ago

Hi everyone,

I'm reaching out to see if anyone might be able to help with a few legacy tool challenges we’re facing.

We’re currently working with several old PCB designs created in OrCAD Layout 16.2, and we need to export them in ODB++ format. In the past, this was done using the GW2ODB executable that Valor used to provide (specifically: gw2odb_setup_v730.exe). Unfortunately, the original executable seems to be lost and no longer available online or from the original contacts.

We’re looking for help on a few points:

  1. Does anyone still have a copy of the GW2ODB executable? If yes, would you be willing to share it or point us to a safe download location?

  2. What is currently the best way to generate ODB++ output from OrCAD Layout 16.2? The export option is visible in the tool, but the functionality depends on the missing executable.

  3. Is there a reliable workflow or tool for converting .MAX files (Layout) to .BRD (Allegro/PCB Editor) without losing data or design integrity? We'd like to consider migrating the designs to a more modern toolchain if feasible.

Any insights, tools, or shared experiences would be greatly appreciated!

Thanks in advance!

  • Cancel
  • Sign in to reply
Parents
  • Robert Finley
    Robert Finley 7 months ago

    What is the latest release you're license entitles you to?   

    I use the current ODB exporter between Allegro 16.6  to 24.1.

    We are over the hump abandoning PADS but still need to translate so...   16.6.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Davide98
    Davide98 7 months ago in reply to Robert Finley

    Hi Robert,

    The latest legacy version we're entitled to use is 16.2.
    However, we also have licenses from 17.4 up to 24.1.

    One of the first ideas I had was to try converting to a newer version, and I did try using the "Translator" tool in both 17.4 and 22.1 under "OrCAD Layout...".
    But since we work in millimeters and use precision up to four decimal places, the resulting design had many nets that weren’t properly connected — not to mention severe issues with shapes. You just can't expect to convert a .MAX file and get a clean .BRD file.

    There are also netlist issues due to formatting differences: characters like . and / aren’t allowed, which adds even more complications.

    At this point, I haven’t found an effective way to generate ODB++ files that include both trace and netlist information.
    Given all these limitations, I decided to abandon that conversion path.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Robert Finley
    Robert Finley 7 months ago in reply to Davide98

    I strongly suspect any license that runs 17.4 and above also runs 16. 6 and below.  16.6 needs windows 10.  16.3 doesn’t run on windows 10(a requirement to get translator help from MGC.)

    I have 16.2 squirreled away somewhere just in case.  Just think 16.2 to 16.6 should be easy.  Currently using the same odb plugin from 16.6 to current release.

    to read 16.x after 22.1 we have to use DBdoctor.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Davide98
    Davide98 7 months ago in reply to Robert Finley

    Thanks for the insights.

    The main issue on my side is that the starting file is a .MAX file. Do you happen to know if .MAX files are still supported in version 16.6? I also keep version 16.2 always ready and operational on an XP VM, just in case.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Robert Finley
    Robert Finley 7 months ago in reply to Davide98

     I can confirm that Allegro 16.6 sp 115  >File >import >Orcad Layout Max file.

    And, it shares the ODB exporter with 24.1

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • excellon1
    excellon1 6 months ago in reply to Davide98

    Hi,

    That translator does work well, however there are some things not so obvious. Ideally you would need to have an allegro parameter file from an allegro design that contains both Text and colors. This is useful because when you pull in the translated design you will have an easy method to set the colors of your design and text sizes for things like ref-dez etc. Otherwise your going to have to set all of this up within allegro.

    On your design if it was done in imperial inches - Mil -  then keep the design in its native units. Be aware that 4 decimal precision in MM is actually less than 2 decimal precision in imperial mil. Mil is more accurate in this regard than MM units.

    On the disconnected nets usually this is due to the shapes. In allegro there are both static and dynamic shapes. Dynamic shapes typically flow around etch. You would most certainly need to merge shapes so as to get the shape parts to connect. It is fairly simple to do this in allegro, just a few clicks.

    Generally speaking the translator does a very good job. I had used it to convert multi-layer boards done in Layout for a client with very good success.

    There is not really a quick path for translated files in any cad system, some massaging would be needed. The translators can save some time as opposed to a complete re-do. As indicated before it is usually alot easier to keep your design withing the native cad system.

    The only thing on this is one would have to know Allegro or be used to using it, I guess somewhat similar to any new cad system.

    Best regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • excellon1
    excellon1 6 months ago in reply to Davide98

    Hi,

    That translator does work well, however there are some things not so obvious. Ideally you would need to have an allegro parameter file from an allegro design that contains both Text and colors. This is useful because when you pull in the translated design you will have an easy method to set the colors of your design and text sizes for things like ref-dez etc. Otherwise your going to have to set all of this up within allegro.

    On your design if it was done in imperial inches - Mil -  then keep the design in its native units. Be aware that 4 decimal precision in MM is actually less than 2 decimal precision in imperial mil. Mil is more accurate in this regard than MM units.

    On the disconnected nets usually this is due to the shapes. In allegro there are both static and dynamic shapes. Dynamic shapes typically flow around etch. You would most certainly need to merge shapes so as to get the shape parts to connect. It is fairly simple to do this in allegro, just a few clicks.

    Generally speaking the translator does a very good job. I had used it to convert multi-layer boards done in Layout for a client with very good success.

    There is not really a quick path for translated files in any cad system, some massaging would be needed. The translators can save some time as opposed to a complete re-do. As indicated before it is usually alot easier to keep your design withing the native cad system.

    The only thing on this is one would have to know Allegro or be used to using it, I guess somewhat similar to any new cad system.

    Best regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information