Jump to content

ODB++

Edit links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Vanished user ty12kl89jq10 (talk | contribs) at 12:19, 20 December 2011 (new sections per GA reviewer). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Distinguish2

File:ODB 100x98.jpg
Logo of ODB++ from Mentor Graphics

ODB++ is a proprietary CAD-to-CAM data exchange format[1] used in the design and manufacture of electronic devices. Its purpose is to exchange printed circuit board design information between design and manufacturing and between design tools from different EDA/ECAD vendors.[2] It was originally developed by Valor Computerized Systems, Ltd. (acquired in 2010 by Mentor Graphics[3]) as the job description format for their CAM system.[2]

ODB stands for open database,[4] but its openness is disputed,[5] as discussed below. The ++ postfix, evocative of C++, was added in 1997 with the addition of component descriptions.[6] There are two versions of ODB++: the original (now controlled by Mentor) and an XML version that Valor developed and donated to the IPC organization in an attempt to merge GenCAM (IPC-2511) and ODB++ into Offspring (IPC-2581).[7][8][1] The XML version was called ODB++(X).[9]

Introduction

Almost all printed circuits boards are designed virtually in a computer aided design (CAD) system.[10] To physically realize the design, the computerized design information must be transferred to a photolithographic computer aided manufacturing (CAM) system.[11] After the bare board is manufactured, the electronic components are placed and soldered, for example by SMT placement equipment and wave soldering. Since the CAD and CAM systems are generally produced by different companies, they have to agree on a CAD-to-CAM data exchange format to transfer the data. ODB++ is one such format.[12] Other formats are compared and contrasted below.

File structure

When in use, ODB++ data is stored in a hierarchy of files and file folders.[13] However, for transmission it is convenient to use common operating system commands that create a single, compressed file that preserves the hierarchy information. For example, on Unix tar and gzip commands can be used.[2] In ODB++(X), the database is contained in a single XML file by default.[9]

ODB++ covers the specification of not only conductor layer artwork and drill data, but also material stack up, netlist with test points, component bill of materials, component placement, fabrication data, and dimension data. This is in contrast to the competing Gerber/drill approach where such data must be delivered separately.[14]

History

Valor was founded in 1992[15] and it released ODB in 1995. It added the ++ postfix when component names were added in 1997. The XML version was developed beginning 2000,[6] and ended in 2008 with the donation to IPC.[16] Valor was acquired by Mentor in 2010.[3]

Adoption

In the late 1990's it became clear to industry participants that a second-generation data transfer format would be more efficient than the prevalent, first-generation Gerber format.[8] However, it was very difficult to reach a consensus over which of two candidates should be selected:

  1. ODB++: proven but proprietary
  2. IPC-2511 GenCAM: not widely used but open

The nominal result was a compromise, ODB++(X),[1] but in fact this proved to be a dead end.[16] As detailed in the next two subsections, the industry is presently divided into two camps over a second generation format in general, and ODB++ in particular:

Advocacy

Companies that have adopted the ODB++ format are advocates for its use. Streamline Circuits reports that it provides much greater efficiency than the competing Gerber format, stating that "an 8-layer printed circuit board can take up to 5 hours to plan and tool using Gerber and only 1 hour when using ODB++."[17] According to Streamline, manufacturers are adopting it to overcome the limitations of the simpler Gerber format.[17] DownStream Technologies calls ODB++ "the defacto standard for intelligent data exchange in EDA"[18] In 2002, Dana Korf of Sanmina/SCI called ODB++ "the prevalent non-Gerber format."[1]

In 2002, the format was recommended by National Electronics Manufacturing Initiative (NEMI; an industry body, subsequently renamed International Electronics Manufacturing Initiative, iNEMI) after a two-year mediation effort between the GenCAM and ODB++ camps.[1] Companies that supported the recommendation for ODB++ included Cadence, Hewlett-Packard, Lucent, Mentor (which acquired Valor some eight years later), Nokia and Xerox.[1]

Lists of EDA tools that support import and/or export of ODB++ have been compiled by Artwork Conversion Software,[19] Mentor itself,[20] and on the Comparison of EDA packages table.

Opposition

Concerns

ODB++ is a proprietary format controlled by Valor and now Mentor, and so, like all proprietary standards, it comes with the risk of vendor lock-in. Although Mentor claims that it "...openly supports inclusion of ODB++ and updates for other EDA tool vendors,"[21] it restricts access to the specification[22] and requires a non-disclosure agreement.[2] The application form includes a requirement to: "...Demonstrate a customer need for this integration through references from mutual customers. Provide a recommendation from a Mentor Graphics product division or demonstrate the incremental value of this integration to both Mentor Graphics and the partner company.", which implies direct competitors to Mentor will not be granted access. This is a source of frustration not only for competitors but also for the Mentor user community.[23]

Potential resolution

Critics of the proprietary nature of ODB++ point to several more open formats as models for a future consensus format:

  • Gerber format (RS-274X from Ucamco): Although it is nominally a proprietary standard, the specification can be freely downloaded from the Ucamco website[24] making it de facto an open standard.
  • IPC-2511 ("GenCAM")[25] which resulted from a donation of certain technologies by Teradyne/GenRAD to IPC.[1]
  • IPC-2581 ("Offspring")[7][26] an attempt to merge GenCAM with ODB++(X).[27] The specification can be downloaded freely.[28] Recently an industry consortium was created to support it, motivated in part by frustration with the proprietary nature of ODB++.[26] Cadence Design Systems, Zuken,[29] Artwork Conversion Software[30] and and the owners of Gerber format, Ucamco, joined it,[31][32] but not Mentor.[16]
  • OpenAccess which resulted from a transfer of certain technologies by Cadence to the Si2 organization.[33] Although it was originally designed for integrated circuits, it's now finding application for IC package and PCB design also.[34]
  • Fujiko: JPCA-EB02,[35] based on work by Prof. Tomokage of Fukuoka University.[36]
  • EDIF - Electronic Design Interchange Format

References

  1. ^ a b c d e f g Mike Santarini (1/22/2002 2:33 PM EST). "ODB++ spec tapped for CAD-to-CAM data exchange". EE Times. Retrieved 29 September 2011. {{cite web}}: Check date values in: |date= (help)
  2. ^ a b c d "ODB++ Overview". Artwork.com. Artwork Conversion Software Inc. Retrieved 25 September 2011.
  3. ^ a b "Mentor Graphics Acquires Valor Computerized Systems, Ltd". Mentor.com. Mentor Graphics. 18 March 2010. Retrieved 25 September 2011.
  4. ^ Andy Shaughnessy (10/20/2000 3:25 PM EDT). "Which Data Transfer Format is Best for the Industry?". EE Times. Retrieved 28 September 2011. {{cite web}}: Check date values in: |date= (help)
  5. ^ IPC-2581 Panel: A Spirited Discussion on PCB Data Transfer Formats, Richard Goering, Cadence Design Systems blog, October 2, 2011 on the panel session "Data Transfer in the 21st Century," PCB West conference, Santa Clara, California, September 29, 2011
  6. ^ a b "ODB++ / GenCAM Convergence Project". PCB Standards: Forum. 06-19-2002. Retrieved 3 October 2011. {{cite web}}: Check date values in: |date= (help)
  7. ^ a b "IPC Subcommittee 2-16 Product Data Description (Laminar View)". ipc.org. IPC. Retrieved 25 September 2011.
  8. ^ a b Mike Santarini (10/20/2000 2:51 PM EDT). "Camps eye CAD-CAM unity". EE Times. Retrieved 2 October 2011. {{cite web}}: Check date values in: |date= (help)
  9. ^ a b "Translators and preprocessors for ODB++". Artwork.com. Artwork Conversion Software Inc. Retrieved 25 September 2011.
  10. ^ "EDA: Where Electronics Begins". edac.org. Electronic Design Automation Consortium. Retrieved December 18, 2011.
  11. ^ "PCBexpress Printed Circuit Board Tutorial". PCBexpress.com. Retrieved December 18, 2011.
  12. ^ Mike Buetow (28 June 2011). "A Short History of Electronic Data Formats". Retrieved December 18, 2011. {{cite journal}}: Cite journal requires |journal= (help); Unknown parameter |publication= ignored (help)
  13. ^ "ODB++ File Hierarchy Tree". artwork.com. Retrieved 2 October 2011.
  14. ^ Karel Tavernier, Ucamco (2011/2Q). "Improving CAD to CAM Data Transfer: A Practical Approach" (PDF). Journal of the HKPCA, Issue No.40. Retrieved 2 October 2011. {{cite web}}: Check date values in: |date= (help)
  15. ^ "Valor Computerized Systems Incorporated". businessweek.com. Retrieved 4 October 2011.
  16. ^ a b c Mike Buetow interview with Julian Coates of Mentor Graphics (29 June 2011). "Mentor's Coates: 'Our Strategy is Based Around ODB++'". Printed Circuit Design and Fab magazine. Retrieved 3 October 2011. The XML [version of ODB++] went end-of-life a few years ago in the days of Valor, after being handed over to the IPC to be used as the basis for IPC-2581.
  17. ^ a b "ODB++" (PDF). Mentor.com. Streamline Circuits. August 2011. Retrieved 25 September 2011. Why Stay Stuck in the Past With Low Intelligence Gerber Files?
  18. ^ "ODB++ Interface". Downstreamtech.com. DownStream Technologies. Retrieved 25 September 2011.
  19. ^ "PCB tools supporting ODB++". Artwork.com. Artwork Conversion Software Inc. Retrieved 25 September 2011.
  20. ^ "ODB++ Data Exchange". Mentor.com. Mentor Graphics. Retrieved 25 September 2011.
  21. ^ "ODB++ Intelligent data exchange between design and manufacturing" (PDF). Mentor.com. Mentor Graphics. August 2011. Retrieved 25 September 2011.
  22. ^ "Online application form for OpenDoor Program to obtain access to specifications". Mentor Graphics. Retrieved 30 September 2011.
  23. ^ Yu Yanfeng (Jan 15, 2011). "Why Mentor(Valor) doesn't publish ODB++ spec in public?". communities.mentor.com. Retrieved 2011 November 04. {{cite web}}: Check date values in: |accessdate= (help)
  24. ^ "The RS-274X Format" (PDF). Ucamco. 2010. Retrieved 31 March 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  25. ^ "Product Data Description (Hierarchical View) Subcommittee". ipc.org. IPC. Retrieved 2 October 2011.
  26. ^ a b "IPC-2581 Consortium". ipc2581.com. Retrieved 1 October 2011. ...but it does not transfer stackup data, materials, design intent or netlist.
  27. ^ Richard Kubin and Barbara Goldstein (November–December 2003). "The Key to the Electronics Lifecycle: Open industry standards will go a long way toward increasing quality and lowering cost". APICS Magazine. Retrieved 2 October 2011.{{cite web}}: CS1 maint: date format (link)
  28. ^ "IPC-2581 with Amendment 1 Generic Requirements for Printed Board Assembly Products Manufacturing Description Data and Transfer Methodology" (PDF). ipc.org. May 2007. Retrieved 8 October 2011.
  29. ^ Keith Felton and Hemant Shah, Cadence Design Systems (28 July 2011). "Equipping the PCB Design and Supply Chain with 21st Century Data". Printed Circuit Design and Fab magazine. Retrieved 3 October 2011.
  30. ^ "Artwork Conversion Software Joins IPC2581 Consortium". Artwork Conversion Software. October 1, 2011.
  31. ^ IPC-2581 Consortium press office (09/27/2011). "Newly Created Industrywide IPC-2581 Consortium Adds Key New Members; Consortium Is Focused on Driving IPC-2581 Adoption Across PCB Design & Supply Chain". Investors Business Daily. Retrieved 10 October 2011. {{cite web}}: Check date values in: |date= (help)CS1 maint: numeric names: authors list (link)
  32. ^ Mike Buetow (28 September 2011). "IPC-2581 Consortium Adds Ucamco, Aegis". Printed Circuit Design and Fab magazine. Retrieved 3 October 2011.
  33. ^ "FAQ 7: What is the history of OpenAccess?". Si2.org. Retrieved 2 October 2011.
  34. ^ "Si2 OA Coalition Members". Si2.org. Retrieved 2 October 2011.
  35. ^ "JPCA Standards".
  36. ^ "FUJIKO for board design". zuken.co.jp (in Japanese).
Retrieved from "https://en.wikipedia.org/w/index.php?title=ODB%2B%2B&oldid=466850878"