• 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 PCB Editor Report like Condensed BOM report

Stats

  • Locked Locked
  • Replies 40
  • Subscribers 167
  • Views 45060
  • 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 PCB Editor Report like Condensed BOM report

ahmetozsoy
ahmetozsoy over 16 years ago

Hi,

Allegro Editor ( 16.2)  generates Bill of Material Report(Condensed). The report columns are SYM_NAME,COMP_DEVICE_TYPE,COMP_VALUE,COMP_TOL,COMP_CLASS, QUANTITY and REFDES.

This simplified report gives the quantities and used component REFDES in same line.

For ex.

SYM_NAME   COMP_DEVICE_TYPE                                                                                        COMP_VALUE .... REFDES

0402               CAP_SMD-GRM155R71C103KA88D-0402,10NF_50V,GRM155R71C103KA88D        10NF_50V    .....   C3,C5.....

What I want to do is to genarate a report like this simplified one but with PART_NUMBER not COMP_DEVICE_TYPE. Because COMP_DEVICE_TYPE is always long and does inculde extra information other than PART_NUMBER, I wish to use only the PART_NUMBER intsead of COMP_DEVICE_TYPE.

I have checked every option and could not find a simplified report like this one. QUANTITY doesn't exist in generating reports. I want to see the quantity in one line only. So my report can be like this

SYM_NAME   PART_NUMBER                    COMP_VALUE .... REFDES

0402               GRM155R71C103KA88D        10NF_50V    .....   C3,C5.....

Thank you for your helps.

Ahmet OZSOY

  • Cancel
  • oldmouldy
    oldmouldy over 11 years ago
    There is something amiss with the RefDes text formatting, it could be "just blank", in any case, do you have an example BRD file that you can attach so that I can test the code?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • chads108
    chads108 over 11 years ago

    Can you give me an address to send you a file, or contact me privately at csaathoff@iphase.com.  The file is too big to attach.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • chads108
    chads108 over 11 years ago

    Oldmouldy,

    I spent a little time trying to figure out why this wouldn't work for me.  I decided to try it on another board file and it ran perfectly, so i narrowed it down to something board specific.  I noticed that on the board file that it wouldn't run, there was a reference designator that was in the format of: P6A  That is what proved to be the problem with the script running.  Once I removed that, it ran as expected.  Now the question is, can the SKILL script take that in to account, or does it overly complicate the entire request.  I suspect this is a rare occurrence so maybe not worth the effort.

    Thanks for your input and help.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 11 years ago
    Hi Chad, OK I suspected something like that might be the case. To sort the RefDes list, the assumed format is (bunch of letters) then (bunch of numbers), like C54, TR629 and so on, the code "chucks up" when the trailing letter gets encountered and the resulting value is then empty, hence the message about "requires 'something' is nil". I will modify some RefDes's on a test board and see if I can get the code to be more tolerant of the RefDes format.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 11 years ago

    2867.cond_bom.zip

    It looks like a standard axl function will help out with the sort.

    Also includes Value, comment out the lines that output the value, where indicated and un comment the lines that don't output the value.

    sample test report output in archive

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

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

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