• 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. PCB Design
  3. Allegro / Expedition

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 168
  • Views 16836
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Allegro / Expedition

Andre L
Andre L over 13 years ago

 Hello All, For those who had the chance to work on Allegro and Expedition, Why Allegro is better? What Allegro have that Expedition don't? Can I have and Idea of forces and weaknesses of both tools?

 Many Thanks

Andre

  • Cancel
  • 22ladd
    22ladd over 13 years ago
    Expedition is much easier to use. A better product .
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Goblin60
    Goblin60 over 13 years ago
    What do you base this conclusion on?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • azrick
    azrick over 13 years ago

    How bout this for starters. ....

    Let me start by saying Mentor DXDesigner is a pretty good tool, but....

    Allegro is much more flexible tool -> Expedition (iCDB flow) is much more rigid (can pull parts from only one library - building and using quick-turn pre-released parts is a pain because everything has to flow through one library)

    Allegro's toolset is simpler/more refined

    Allegro has 1 environment for doing pcb design, documentation and generation of mfg output.

    Expedition has three design environments (Expedition/Drawing Editor/Fab Link)

    Each Expedition environment spins off a multitude of additional files and folders which are linked to its own unique format of the Expedition database.

    Each Mentor environment must be kept in sync with the main Expedition database. (its a pain to keep in sync - has bugs).

    Operation in each Mentor environment is slightly different compared to the others - causes confusion and hard to learn 

    Most of Allegro functionality and command options are accessible from mouse clicks via context menus and getting information about an object is as simple as hovering cursor over an object -> Expedition seems to require many more mouse clicks to get the same results....Example: Many Expedition options for interactive editing require supplemental keyboard strokes (alt key/cntrl key) while in a command to get the full array of options. In Allegro, they're all right their by click of a mouse button.

    Allegro's file structure is simpler and more efficient -> Expedition much more structured and rigid.

    Allegro's has one design file (.brd) -> can be moved anywhere independent of where schematic is -> and is completely self contained (libraries can be recreated from the one file)

    The Mentor Expedition database is so closely tied to the schematic (via the iCDB) it cant be moved independently unless you go though another process (undocking).

    Mentor iCDB (the link between schematic and layout) can present sync problems between schematic and layout. In general Mentor is much more complex to manage.

    Once Mentor DX/EX design container loses links with the ONE LIBRARY you cant forward annotate until you link it back up.

    Typical size of our Allegro/Concept design container < 100 GB - Mentor design containers can grow upwards of 400 GB (related to the spin off of multiple files associated with different design environments.

    Wish I had someone to point these things out before....I could go on but you get the idea.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • azrick
    azrick over 13 years ago

    Correction on those design container sizes   .....Allegro/Concept < 100 MB    DX/EX 400 MB and greater.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • girish
    girish over 13 years ago

    Good Comparision & usefull.

    Thanks ,

    Regards,

    Girish Kumar 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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