• 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. Failed to export partial ODB !!!

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 165
  • Views 17831
  • 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

Failed to export partial ODB !!!

Ineedhelp
Ineedhelp over 16 years ago

 Hello!

I'm working with Cadence Allegro 16.01 and want to export ODB++ File. (ODB++ inside Version 8.2.0).

I choose:

- Gzip

- Partial ODB++

 

>> Begin Translation... >> Translation finished successfully

 

Then the Export Setting Popup appears.

I choose:

- Assy

>> Failed to export partial ODB !!!

 

Does anyone know which problems are there?

Thanks

 

 

  • Cancel
Parents
  • Rik Lee
    Rik Lee over 16 years ago
    The solution on Sourcelink alludes to a package boundary height that exceeds what would be 'normal' e.g. 2000 MM.

    If you already have the line:

    attr_value_correct=yes

    and you have closed and then re-invoked the Valor GUI re-run your job and then look at the log file, it will point to the problem component in most cases.

    Job=odbjob, Step=pcb, Layer=comp_+_top, Component=TP41  :  illegal value 78.740158 for attribute .comp_height was changed to default 0.000000

    Additionally, you could create a report using the extract view file below to scan and see if any of the information isn't 'typical'.


    GEOMETRY
      REFDES!=""
      CLASS="PACKAGE GEOMETRY"
      SUBCLASS="PLACE_BOUND_TOP"
      OR
      SUBCLASS="PLACE_BOUND_BOTTOM"
        REFDES
        SUBCLASS
        GEO_PACKAGE_HEIGHT_MIN
        GEO_PACKAGE_HEIGHT_MAX
    END
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Rik Lee
    Rik Lee over 16 years ago
    The solution on Sourcelink alludes to a package boundary height that exceeds what would be 'normal' e.g. 2000 MM.

    If you already have the line:

    attr_value_correct=yes

    and you have closed and then re-invoked the Valor GUI re-run your job and then look at the log file, it will point to the problem component in most cases.

    Job=odbjob, Step=pcb, Layer=comp_+_top, Component=TP41  :  illegal value 78.740158 for attribute .comp_height was changed to default 0.000000

    Additionally, you could create a report using the extract view file below to scan and see if any of the information isn't 'typical'.


    GEOMETRY
      REFDES!=""
      CLASS="PACKAGE GEOMETRY"
      SUBCLASS="PLACE_BOUND_TOP"
      OR
      SUBCLASS="PLACE_BOUND_BOTTOM"
        REFDES
        SUBCLASS
        GEO_PACKAGE_HEIGHT_MIN
        GEO_PACKAGE_HEIGHT_MAX
    END
    • 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