• 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. modules

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 164
  • Views 13394
  • 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

modules

archive
archive over 19 years ago

is anyone doing modules using viewlogic front end and allegro back end?
creating modules is fairly easy but we have problems when we start making changes such as
deleting and adding parts. parts seemed to get confused as to whether they belong to a module or the none module part of the brd.


Originally posted in cdnusers.org by jdkelly3
  • Cancel
  • archive
    archive over 19 years ago

    The short answer, It is difficult to use the module functionality with Viewlogic on the front end. It is not impossible but very hard to manage. I have used modules to reuse sections of circuitry from board to board as long as the Viewlogic schematic is done carefully to maintain the module Prefix for the reference designators it should work.

    If you add or delete parts they would need to be done inside of the module file (*.mdd) and the Viewlogic schematic manually. You could also maintain a small schematic for the module only so if components are added or deleted you could simply load a netlist into the module to make the changes. Of course you would need to do a refresh of the module on your board file (.brd) prior to importing the full schematic netlist.

    Maybe someone else has a more automated way to manage reuse modules with Viewlogic on the front end but whenever Cadence changes the way modules are stored in the Allegro database you will also have to change the way they are stored on the Viewlogic side. This is why I use the semi-manually way of using reuse modules.

    Hope this helps or at least gets you thinking on ways to handle modules.
    Michael Catrambone
    UTStarcom, Inc.


    Originally posted in cdnusers.org by mcatramb91
    • 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