• 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. 17.2 Padstack Editor -- Opening scripts for 16.6 in 17.2...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 166
  • Views 5062
  • 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

17.2 Padstack Editor -- Opening scripts for 16.6 in 17.2?

JFuoco
JFuoco over 6 years ago

Is there a simple way to open padstack scripts written for v16.6 in padstack editor v17.2? It seems like a complete scripting language overhaul. 

The root of this problem is that I exported a design from TI's WEBENCH tool. However the padstack scripts don't seem to work at all in v17.2. The first issue that occurs is "Can't find window; Form.padedit"

Here's a sample part of the script:

######################## New PadStack #########################
pse_new
fillin "R10180550000000A.pad"

FORM padedit units Mils
FORM padedit decimal_places 4

FORM padedit layers
FORM padedit grid row 1
FORM padedit geometry Rectangle
FORM padedit width 17.7165
FORM padedit height 55.1181
FORM padedit x_offset 0
FORM padedit y_offset 0
FORM padedit geometry_th Null
FORM padedit grid row 4
FORM padedit geometry Rectangle
FORM padedit width 17.7165
FORM padedit height 55.1181
FORM padedit x_offset 0
FORM padedit y_offset 0
FORM padedit grid row 6
FORM padedit geometry Rectangle
FORM padedit width 17.7165
FORM padedit height 55.1181
FORM padedit x_offset 0
FORM padedit y_offset 0
FORM padedit parameters
FORM padedit single YES
FORM padedit plating Non-Plated
pse_save_as
fillin "R10180550000000A.pad"

Here's a snippet from a script I started recording in v17.2:

# Pad Editor script
# file: 123.scr
# start time: Wed Dec 19 2018 16:35:30
# Version: 17.2 S033 (3691042) Windows SPB 64-bit Edition

QtSignal GuidedTabsParent PadstackTypes currentRowChanged 1
QtSignal GuidedTabsParent PadstackTypes itemSelectionChanged "SMD Pin"
QtSignal GuidedTabsParent PadstackTypes itemClicked "SMD Pin"
QtSignal GuidedTabsParent GuidedStartTab keyPressEvent 16777249 67108864 false 1
QtSignal MainWindow Units CurrentIndexChanged Millimeter
QtFillin Yes
QtSignal MainWindow Units CurrentIndexChanged Mils
QtFillin Yes

  • Cancel
Parents
  • steve
    steve over 6 years ago

    The biggest issue is probably the name of the exe that is first called up. 17.2 uses padstack_editor.exe and 16.6 used pad_designer.exe. Look at the script file and see if that helps

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JFuoco
    JFuoco over 6 years ago in reply to steve

    Hi Steve thanks a lot. Confirmed, the original .exe calls pad_designer.exe:

    Beginning of original script:

    ==============================

    cd %~dp0
    allegro -s CustomShapes.scr
    pad_designer -s 2018-12-18_14-22-36_pads.scr

    ==============================

    My edits, to work for 17.2:

    ==============================

    cd %~dp0
    C:\Cadence\Cadence_SPB_17.2-2016\tools\bin\allegro.exe -s CustomShapes.scr
    C:\Cadence\Cadence_SPB_17.2-2016\tools\bin\padstack_editor.exe -s 2018-12-18_14-22-36_pads.scr

    ==============================

    I also tried opening the 2018-12-18_14-22-36_pads.scr script inside padstack editor directly to see if it runs, but thats where i get the error above:

    "Can't find window; Form.padedit"

    Any thoughts? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JFuoco
    JFuoco over 6 years ago in reply to steve

    That'd be great Steve. Here's the zip I had downloaded from TI: 2018-12-18_14-22-36.zip

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • steve
    steve over 6 years ago in reply to JFuoco

    Here you go data.zip

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JFuoco
    JFuoco over 6 years ago in reply to steve

    Thanks a lot Steve. This works and I can see the symbols and pads. Appreciated. But now, the _brd script itself is having issues. It seems to go through correctly... It does a bunch of things, including what looks like re-drawing the symbols. But when all is said and done, the blank_Board.brd is unchanged, and that is the only board file in the directory. 

    Any way you could run the script in 16.6 and include the updated .brd file here?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • steve
    steve over 6 years ago in reply to JFuoco

    Hi - OK This does run as part of the bat file but I have also run the script internally and the _brd script just creates more footprint files. It doesn't place any parts. The updated board (included this time) is empty). You might need to go back to UltraLibrarian who wrote this to find out if something is missing. data1.zip

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JFuoco
    JFuoco over 6 years ago in reply to steve

    Well, I feel better knowing that. Thanks a lot for the help Steve, truly appreciated as always.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • JFuoco
    JFuoco over 6 years ago in reply to steve

    Well, I feel better knowing that. Thanks a lot for the help Steve, truly appreciated as always.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data
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