Stats

  • State Not Answered
  • Replies 14
  • Subscribers 43
  • Views 8577
  • Members are here 0
More Content

Back Annotate from Allegro to bring in component location and board side using "pickdata" broken on 17.4

JERATSSI

We generate our bill of materials from the schematic and one of the things we need is the component board side.  A long time ago Ole Ejlersen wrote a script called symboldata that creates a swap file I could back annotate into the schematic to bring in that information so I can export a report with all the components and their placement info.  It worked fine on 17.2 but now that I've gotten to 17.4 it appears to be broken.  

This is the example of the output

;**************************************************
;Backannotation file with pick and place data
;from Cadence Allegro to Capture and Capture CIS
;**************************************************
.Section3 UpdateProperties Parts
"{Reference}" "COMPX" "COMPY" "COMPROT" "COMPSIDE"
"C11" "-142" "-764" "180.000000" "BOT"
"C12" "-266" "-879" "180.000000" "BOT"
"C13" "-206" "-627" "90.000000" "TOP"

When I try back annotating with or without the generate board feedback box selected I get:

"Encountered an improper argument."

I'm guessing by this message and another thread about compatibility being lost with PADS that back annotate has changed significantly and my script will no longer work.  Is there a new way to get this information into my schematic component properties so I can do my standard BOM reports again?

  • JERATSSI
    0 in reply to JERATSSI

    Okay, so here's my work around so far:

    1) Export properties from capture

    2) Run the skill file to generate the swap file

    3) Open both in excel and use a index/match to find the ref des in the swap file and put the component board side information into the compside column (create first if it doesn't exist), then reimport back into capture

    Hopefully I can either adjust the skill used in step 2 to generate an importable file but I don't see information on part instances on the Allegro side of things when I do show element so I don't know if that will work.  Otherwise a script to do step 3 without excel would be sufficient, import the properties and swap file and export a new importable properties file

  • redwire
    0 in reply to JERATSSI

    Ok, this makes total sense.   We used to use ref des below 500 = TOP, 500 & above = BOTTOM and filter the data once we had the single component per line BOM.  However, if my SKILL knowledge was a bit less rusty, I would be able to add this property to each symbol and then it would import directly during back anno..

    What I would do is reach out to Dave Elder on here who is a SKILL guru and ask for some help in this area.  The SKILL file you are using uses a shelled command to post-process an extracta output.  That's really not what you need.  Dave is usually on here and answers a bunch of SKILL questions on the SKILL forum.  Go see the master.

    In the meanwhile I'm going to de-rust my SKILL and see if I can figure this out.


  • AvengerThanos
    0 in reply to excellon1

    Irrespective of version still .swp file in generated in project directory. With layout being removed user lost scope and mode options.

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.