• 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. Allegro X PCB Editor
  3. Pad's Translator 17.4, Not valid allegro subcts

Stats

  • Replies 5
  • Subscribers 160
  • Views 2497
  • Members are here 0
More Content

Pad's Translator 17.4, Not valid allegro subcts

MPollock
MPollock over 3 years ago

Hello Forum,

I am trying to translate a old Pad's project to Allegro 17.4, looks like it is creating the netlist fine, but it stops with an error in the pads_in.log there is a message at the end,

ERROR: Subclass name SOLDERMASK_TOP not valid Allegro subcls for class ROUTE KEEPOUT. Quitting.
ERROR: Failed while writing the Allegro database.
Information: Object is empty, so CSet 1_16_17 renamed to DEFAULT

Warning: Default electrical CSets are not supported in Allegro PCB Editor.
Manually assign the ¡®DEFAULT¡¯ electrical cset to the objects.

Looking at the project.asc in Notepad++ but can't see what the issue is, any idea's would be greatly appreciated ! 

Thanks Much,

Mike Pollock.

  • Sign in to reply
  • Cancel
  • RFinley
    RFinley over 3 years ago

    I use PADS vx2.5 and Allegro 16.6, 17.2, and 17.4 because I go back and forth a lot.   

    What is in your options file for the PADS translation import (text editor)?

    Do you have entries for SOLDERMASK_TOP or ROUTE_KEEPOUT that you can delete?

    Have to figure out where Route Keepout comes from.

    This is a report of a successful xlation into Allegro 16.6 (17.2 and onward won't xlate back to MGC until they update the translator to use current Allegro padstacks.)

    PADS layer usage summary:
      Layers 1 to 4 are route layers.
      LINES:
         1           ETCH - TOP
         4           ETCH - BOTTOM
        21 BOARD GEOMETRY - SOLDERMASK_TOP
        24  * Not mapped!
        26 BOARD GEOMETRY - SILKSCREEN_TOP
        28 BOARD GEOMETRY - SOLDERMASK_BOTTOM
      COPPER:
         1           ETCH - TOP
         2           ETCH - INT2
         3           ETCH - INT3
         4           ETCH - BOTTOM
      TEXT:
         1           ETCH - TOP
         2           ETCH - INT2
         3           ETCH - INT3
         4           ETCH - BOTTOM
        19  * Not mapped!
        21 BOARD GEOMETRY - SOLDERMASK_TOP
        22  * Not mapped!
        23  * Not mapped!
        24  * Not mapped!
        26 BOARD GEOMETRY - SILKSCREEN_TOP
        28 BOARD GEOMETRY - SOLDERMASK_BOTTOM
        29 BOARD GEOMETRY - SILKSCREEN_BOTTOM
      DECALS:
         0 PACKAGE GEOMETRY - SILKSCREEN_TOP
         1 PACKAGE GEOMETRY - SILKSCREEN_TOP
        14  * Not mapped!
        15  * Not mapped!
        20  * Not mapped!
        21 PACKAGE GEOMETRY - SOLDERMASK_TOP
        23 PACKAGE GEOMETRY - PASTEMASK_TOP
        25  * Not mapped!
        26 PACKAGE GEOMETRY - SILKSCREEN_TOP
        27 PACKAGE GEOMETRY - ASSEMBLY_TOP
      PADS:
         0           ETCH - internal_pad_def
         1           ETCH - TOP
         2           ETCH - INT2
         3           ETCH - INT3
         4           ETCH - BOTTOM
        21            PIN - SOLDERMASK_TOP
        23            PIN - PASTEMASK_TOP
        28            PIN - SOLDERMASK_BOTTOM
      VIAS:
         0      VIA CLASS - internal_pad_def
         1      VIA CLASS - TOP
         2      VIA CLASS - INT2
         3      VIA CLASS - INT3
         4      VIA CLASS - BOTTOM
    
     WARNING: 3237 data objects mapped to the UNUSED class were ignored.
    
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • MPollock
    MPollock over 3 years ago in reply to RFinley

    Hello RFinley,  Right now I'm using the default pads_in.ini file, first time trying to do this, very complex PCB and was done with a 2007 version of Pads.  I can see the entry's for SODERMASK_TOP, not sure what is the problem tried to change the name from underscore to dash with no luck.  Thanks,   Mike P.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • RFinley
    RFinley over 3 years ago in reply to MPollock

    send me an email rfinley91729 at gmail.com if you want me to try up-reving the ascii file.   

    The Allegro xlator definitely falls over past PADS 9.5.  Have to downrev.  

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • MPollock
    MPollock over 3 years ago in reply to RFinley

    Hey thanks much for the offer, but really good to know, we were thinking it might have had something to do with the age of pads.  This is part of a microwave Ablation system, we are looking at contracting this out, but this company is very concerned about confidentially, requires signing NDA forms. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • RFinley
    RFinley over 3 years ago in reply to MPollock

    Oof!  NVM...   Good luck.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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.

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

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