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.
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 CatramboneUTStarcom, Inc.