Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Greetings,I'm investigating various methods for creating assembly drawings and I'm curious what you may be using.We currently create an IPF file and import it into a new .brd file. This, of course, creates a non-intelligent version of the graphics that must be updated manually (or via scripts) every time the board changes.We've given some thought to producing drawings from within the main .brd file by importing the page border, but this seems to create more questions and what-ifs.Another idea on the table is to export DXF to a "friendlier" drawing tool, such as Visio or AutoCAD.What are your experiences and what tools or methods do you currently use?Thanks in advance,Scott
Scott,We have been an Allegro user for more than 15 years and initially we used to export our data to AutoCad to do the drawings. We concluded long ago that it was much more practical to maintain the drawings in the .brd file. It allows us maintain a much higher degree of continuity between the actual data and the drawing. There have always been sychronization issues when you have the data in two places, so we have tried to avoid this wherever possible. We use color files to maintain the views/layer mapping to each of the drawings (Fab and Assembly) and their respective sheets.So as an example, if you have a 2 sheet Fab drawing and the drawing number is 12345, we would have a color file called 12345-1 for sheet 1 and 12345-2 for sheet 2. If you had a 3 sheet assembly drawing numbered 12346, we would have a color file for each of those sheets 12346-1...12346-3. We also have the revision embedded in the names to allow for different revs of the same drawings.The color files allow each user to do the drawings with whatever subclass(es) they choose (we do have recommended standard layers), but other users can quickly pickup the design and navigate to the appropiate drawing using the visibility form.Hope this helps.
We generate our assembly drawings inside the Allegro database. We do not create a separate board file by importing IPF files or export DXF from the board into AutoCAD or Visio. As you said, doing things the Export/Import way you take the risk of the assembly drawing data becoming out of date. I have Allegro symbols of different size formats that can be placed in the Allegro database and quick update to the title block then you are in business.I have been doing this way for a very long time and the only issue that seems to come up is the ability to scale up the assembly view (2 to 1, 4 to 1) so it can be read on a printout. This has become less of an issue as when we started to store these drawings electronically in PDF format instead of killing trees.As far as importing the assembly data into a 3rd party drafting tool, I have done this as well but it is much easier keeping things in one database then maintaining two.Mike CatramboneUTStarcom, Inc.
FWIW, on the scaling issue, we have created 1/4 and 1/2 scale formats that, when plotted at full scale, will produce 4/1 and 2/1 drawings.
Another way to get around the scaling issue is to create Details of the features/classes that you want to be on your drawings. You can scale up/down the details as neccesary as well as mirror for the bottom side. In our case we have automated most of the drawing creation/display process entirely within Allegro. Our Allegro library contains custom format drawings for the border and title blocks. When there is a need to show a more complex 3d assemby view, we import DXF from ProE and add it to it's own assembly sheet within Allegro. Our final drawing export from Allegro to manufactuing is a single PDF that contains all the sheets. I definitely recommend keeping the assembly & lamination drawing creation process within Allegro.Randy
Creating a Detail of the features/sub-classes will work but that information can get out of date but with a script like you have it may not matter because it is automatically updated. We used the multiple scaled format symbol options, as Charlie outlined, a while back but the format seemed to take more space then the actually assembly view. It is more important to have a assembly view that can be read vs. having it on a pretty format.We went to the simple title block, that we used for our artwork layers , for the Assembly and Fabrication drawings to get the largest view possible. We still generate 3D Pro-E Assembly drawings for the higher level assembly of the mechanical components which includes some of the major components but a basic 2D Assembly drawing out of Allegro showing the parts placement works just fine for visual inspection. Using PDF files of these drawings is definitely the way to go.
It is true that the detail drawings could easily get out of date if the automation/process was not place to allow for easy recreation/modification of the details with every new CAD data release. If you choose to use details it is critical to have a process and/or automation in place to ensure yourdrawings are current with artwork/drill. In our case using details for PCA/PCB drawings was originally recommended and implemented for us by Cadence's Methodology Services group. Since the original implemenation in the 13.5 era, we have internally maintained and enhanced the process/code as necessary.