• 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. brd2odb Error translating input.

Stats

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

brd2odb Error translating input.

abcdef123
abcdef123 over 13 years ago
I looked for this error and everyone seems to address the issue by changing the artwork type to RS274Xand decimal places to 5.I also run dbdoctor and have 0 errors but when I try to translate I get:    

*********** ERROR  12Nov2012.141047.467  5924  91.1 Update 1(38) Windows XPCadence Interface - File geoms_28381155.out has wrong header*********** ERROR INTERNAL 12Nov2012.141047.467  5924  91.1 Update 1(38) Windows XP(ind_list != ((void *)0) && ind_list->magic == 12121212) at D:\vSureSRC\s911\gen\gen_sort.c 1236

Why is trying to read something from my D drive? Could this be the cause of it? I´m running the translator from within Allegro menu (file>export>odb++ inside)I´m on Allegro PCB Editor 15.5
  • Cancel
  • clarkage
    clarkage over 12 years ago

    I'm having a similar problem when attempting to export ODB++ from .brd file.  It seems to break at some point and starts spitting out the error messages referring to D:\vSureSRC\ like the OP.  The last few lines of the log_brd2odb_x.txt are included below.  The fifth line is where this log diverges from other successful gererations of ODB++ files for our other boards.

    Done - 0 seconds

    Create step profile ...

    Complete step ...

    write file - G:/XXxxxxx/XXXxxxx/hw/XXXXxxxxx/hw/rXvX/allegro/odbjob/steps/pcb/eda/data.Z

    *********** ERROR INTERNAL 26Feb2013.093354.892  4676  9.1(1) Windows Vista

    (hIn != ((HANDLE)(LONG_PTR)-1)) at D:\vSureSRC\s91\gen\gen_fs.c 1930

    *********** ERROR INTERNAL 26Feb2013.093355.766  4676  9.1(1) Windows Vista

    System open call error : No such file or directory at D:\vSureSRC\s91\gen\gen_fs.c 1930

    *********** ERROR INTERNAL 26Feb2013.093355.766  4676  9.1(1) Windows Vista

    file/dir causing error : C:/MentorGraphics/Allegro Export ODB++/tmp/brd_2/comps-genesis186ad.XXxxxx-Xxxx.4676

    *********** ERROR  26Feb2013.093355.766  4676  9.1(1) Windows Vista

    Object id = 1151, type = 3

    *********** ERROR  26Feb2013.093409.846  4676  9.1(1) Windows Vista

    colors file does not exist - C:/MentorGraphics/Allegro Export ODB++/.genesis/colors

    ***********  COMMAND 26Feb2013.093409.906  4676  9.1(1) Windows Vista

    units,type=inch (0)

    ***********  COMMAND 26Feb2013.093409.906  4676  9.1(1) Windows Vista

    display_comp_outline_mode,mode=Body (0) 

     

    Something happened to my board file when my computer crashed due to a graphics card failure.  After DB doctoring after the crash everything appeared to work fine; constraint manager was fine, all components imported worked fine, and gerber generation went off without a problem.  However, now that I try to export an ODB++ file(s) the symbols folder within the ODB++ archive is empty and this is something our contract manufacturer needs.  I tried the suggestion of changing the artwork to RS274X and decimal places but to no avail ( we use this format so I actually moved it away and back to the RS274X settings)

     

    Did anyone ever get resolution on this?  Right now I'm attempting to place-replicate an entire board design from the newer failing brd file to an older file that still generates ODB++ correctly but it's not fast or perfect and we've already lost some time due to this.

     

    Thanks for any help

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

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

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