Gerber: The Format that Just Won’t Die

I’m a big believer in standards but I’m not so sure why IPC is pushing a Gerber Coupon Generator when it has spent so many years developing IPC-2581, a much more comprehensive electronic data format.

Now in its B revision, IPC-2581 has been implemented in trial and production, and represents the most comprehensive set of industry requirements for printed circuit board fabrication, assembly, and test in a data-centric, open, license-free, industry driven standard format. Moreover, the consortium supporting its adoption boasts more than 90 members, including all the major PCB software vendors, plus a host of major OEMs, equipment suppliers, manufacturers, and service suppliers.

It’s time the emphasis be placed on moving the industry out of the buggy era. (Pun intended.)

Full disclosure: I’ve been a member of the IPC-2581 task group since its inception, and spent several years at IPC working on the predecessors to IPC-2581.

ODB++ Plus, Plus, Plus

I wrote a bit about ODB++ back in October. Nothing has really changed much since then. I’m just clarifying a few things.

First, I want to put more emphasis on the use of ODB++. In addition to being beneficial to the manufacturing process, it can make your job a little easier. If you send ODB++, you do not need to send either the centroid or Gerber files. The ODB++ replaces both.

Eagle CAD does not have an ODB++ export. However, the Eagle .brd file will work too. You can send the .brd instead of the centroid and Gerber files.

If you can’t send either of those formats, we as an EMS still need the centroid and Gerbers (top copper, bottom copper, solder paste stencil, silkscreen and solder mask layers).

Duane Benson

Number Six
I am not a number, I am a free man!

http://blog.screamingcircuits.com/

IPC-2581 ‘Chat’ Recap

We had nearly 1,000 visitors to today’s PCB Chat on IPC-2581. The moderators, led including Gary Carter of Fujitsu, answered more than 20 questions in a chat that lasted almost twice as long as planned. (The moderators plan to respond to some of the other questions they received that they couldn’t get to during the chat, so be sure to check back in a few days and see the updated transcript.) You may also contact them directly with questions at www.ipc2581.com/index.php/about.

The results show that data transfer is an area of high interest to the industry. The committee will be presenting a poster next week at IPC Apex Expo and will also have a booth there, where members can answer your questions about the new standard.

Speaking of Apex, on March 2 I will moderate a chat on the show. As always, we’ll open the chat to questions a few days early.

Upcoming Chats

SMT process consultant Phil Zarrow’s moderated chat is today at 2pm Eastern.

You don’t need to make the live session in order to ask a question: questions may be submitted in advance.

Future chats will cover data transfer, PCB cleaning, environmental regulations and MSDS tracking, and on March 2 yours truly will take questions on this year’s Apex trade show.

IPC-2581 Update

It’s been a while since I updated readers on the IPC-2581 Consortium. Here’s a few tidbits:

  • The group of supporters continues to grow, and a couple large IT and test equipment OEMs are now considering joining. At least one announcement could be coming shortly.
  • The verification team, led by Ed Acheson at Cadence, is making progress. They are looking at some designs to use for test runs. At least 10 designs are expected to be validated using the members’ CAD and CAM tools.
  • Wise Solutions expects to have an IPC-2581 viewer by January. It will likely be made available through multiple websites.
  • The Consortium will have a booth at the IPC Apex show in late February and PCB West in September. Members will also have a poster at Apex and will make a presentation at PCB West.

Here’s a question: Should Mentor or Frontline (which Mentor owns a 50% stake in) join the IPC-2581 Consortium? Feel free to reply here or directly to me if you wish.

Talking Data Transfer at ZDAC

I had the great pleasure of attending Zuken’s ZDAC users group meeting earlier this month in San Antonio at the invitation of Steve Chidester, head of product marketing, and Amy Clements, marketing/sales manager.

Steve and Amy had asked me to present on electronics data transfer, a subject many readers know has long held my interest.

There were about 100 people who attended the event this year, slightly up over last year. All the usual Zuken folks were there: Gerhard Lipski, GM of Zuken Europe; Dave Gullickson, GM of Zuken USA; apps engineer Griff Derryberry; Humair Mandavia; Sandy Jones; and so on. I also was fortunate to meet with Zuken COO Jinya Katsube and CTO Kazuhiro Kariya.

As we’ve reported over at PCDanfF.com, just before ZDAC, Zuken rolled out two new tools: DesignForce, which accelerates prototyping by enabling chip-package-interconnect substrate optimization in a single, native 3D format. The CAD company also released CR-8000, its primary CAD flow. (DesignForce is embedded in CR-8000.) They spent a considerable amount of time discussing those two new tools and their ongoing product roadmap, including CR-5000 Lighting v. 14 next March, which will include a netless router. Zuken says it sees a need to move more information to upstream design, such as system and architecture. The main takeaway was that design makes up 4% of the cost of the process, but it determines 60% of the product cost.

I had about 45 people in my session. There was great interest in the topic, in part because some of the people there have been pushing their companies (RIM, Rockwell Collins, Northrop Grumman, to name but a few) to standardize on IPC-2581. All in all, it was well worth the time.

Also, Zuken is doing a lot in wiring harness design. This is a big market for many EMS companies (especially for military and aerospace work), and there are probably 12 to 15 companies that supply design software for wiring harness. (Some big ones are Mentor, Zuken, Eplan, Autodesk, and IGE-XAO). I didn’t attend the wiring harness design sessions, but it seems the audience was fairly split between the two.

Next year’s event will be held in Newport, CA, around the same time frame (early November).

Major Major and Standard Standard

We ask for your bill of materials, Gerber and centroid files to assemble your PCBs. All those pieces of information are necessary to properly program our machines to place your parts. That’s pretty standard stuff, but did you know that when the Gerber format reference book was first published, Jimmy Carter was President of the United States, Russia was the “Soviet Union” and Voyager 1 was well inside the Solar System?

Use of the format has been going on even longer. Yeah. It’s been around a while. For some reason, it has been very difficult to get everyone to agree to and use a standard file format. Gerbers really don’t have enough information in them to do the job properly, but it is the standard. Hopefully not for too much longer. How many of you reading this were even born when Gerber was new?

There are a number of formats around that are better than gerber and Screaming Circuits will accept many of them. First, your CAD software probably will export an “ASCII CAD file”. This is a good format. Some export ODB++, which is one of the newer formats, again a good choice. One of the newest standards is the IPC-2581. It’s been around a few years and is now getting a lot of attention. If you happen to use Eagle CAD, you can also send us the Eagle “.brd” file.

IPC-2581 includes the best of ODB++ and GenCAM. It has all of the fab data, assembly data, netlist and BOM. Everything needed in one convenient file. My understanding of the format is that you can exclude portions of the data set that you consider proprietary. You can learn more about the format here. There’s more background information on the subject at PCD&F magazine.

Duane Benson
Where’s Henry?
I need an inductor.

http://blog.screamingcircuits.com/

Data Transfer in the News

A couple new articles are out on the IPC-2581 and ODB++ data transfer formats.

On Oct. 2, longtime EDA journalist Richard Goering provided a well-written writeup on the “lively panel discussion” (“Data Transfer in the 21st Century”) we held during PCB West on Sept. 29. Richard does a nice job capturing the frustration of the designers present and historical give-and-take that has led us to the current situation.

And yesterday, EDN weighed in with interviews of participants from the data transfer panel held at PCB West and other key spokespersons.

Given the new support for IPC-2581 by Cadence and Zuken, among others, this issue isn’t going away.

Talk Isn’t Cheap

Communicating is hard. It took thousands of years just for man to develop a common language. I don’t suppose, then, even in our “enlightened” state, we should expect it to be easy to develop a common, complete method for describing all the myriad features of a printed circuit board.
This week at PCB West, the Silicon Valley annual trade show, a special panel will convene to address just that decades-old issue. (Disclosure: I’m the moderator.) I don’t expect the group to solve all the industry’s data problems in just 90 minutes, but I do think a few key aspects will be noted.

Here’s a question I plan to raise: Would the problem of unintelligent data files be essentially resolved if the initial cost to upgrade were lower?

Upstream, Intel, for example, sends an army of engineers to its suppliers to help them implement new processes. Few companies have the resources of Intel, of course. No fabricator does. And this leaves the fabs in a bind: They know that Gerber is insufficient, and spend countless hours massaging (often without their customer’s knowledge) the bad or incomplete data received from design. But with tooling jobs stacking up on their desks, and margins cut to the bone, they claim no resources to spend on implementing one of the richer data transfer formats like ODB++ or IPC-2581.

So who pays?

Neither IPC nor Valor make any money directly from their respective data transfer formats, so it’s unlikely either would see the value in extending themselves further by underwriting the onsite development and implementation work. (Whether they should anyway is a column for another day.) Designers tend to be risk-averse: They are unlikely to risk their jobs on something upper management is not mandating. Thus, it may be that the fabricators need to start assigning a CAM engineer to its key customers — perhaps one at a time, to keep costs down — to help them get up and running — no matter which rich format they choose.

The argument for switching to a superior format(s) is that manufacturers will save money down the road. I understand, however, that quantifying the cost savings is exceedingly difficult. Moreover, as one CAD developer told me, there’s an unwritten incentive for the status quo (read: Gerber) because manufacturers don’t want to appear inflexible.

I would argue that the industry’s margins can’t afford to keep sending bad data downstream and hoping for a miracle in return. Fabricators over the past decade have lost most of their influence over the printed circuit board development. This is an area where they can truly coach their customers — and add value in the process. They should grab it.

Talk Isn’t Cheap

Communicating is hard. It took thousands of years just for man to develop a common language. I don’t suppose, then, even in our “enlightened” state, we should expect it to be easy to develop a common, complete method for describing all the myriad features of a printed circuit board.

This week at PCB West, the Silicon Valley annual trade show, a special panel will convene to address just that decades-old issue. (Disclosure: I’m the moderator.) I don’t expect the group to solve all the industry’s data problems in just 90 minutes, but I do think a few key aspects will be noted.

Here’s a question I plan to raise: Would the problem of unintelligent data files be essentially resolved if the initial cost to upgrade were lower?

Upstream, Intel, for example, sends an army of engineers to its suppliers to help them implement new processes. Few companies have the resources of Intel, of course. No fabricator does. And this leaves the fabs in a bind: They know that Gerber is insufficient, and spend countless hours massaging (often without their customer’s knowledge) the bad or incomplete data received from design. But with tooling jobs stacking up on their desks, and margins cut to the bone, they claim no resources to spend on implementing one of the richer data transfer formats like ODB++ or IPC-2581.

So who pays?

Neither IPC nor Valor make any money directly from their respective data transfer formats, so it’s unlikely either would see the value in extending themselves further by underwriting the onsite development and implementation work. (Whether they should anyway is a column for another day.) Designers tend to be risk-averse: They are unlikely to risk their jobs on something upper management is not mandating. Thus, it may be that the fabricators need to start assigning a CAM engineer to its key customers — perhaps one at a time, to keep costs down — to help them get up and running — no matter which rich format they choose.

The argument for switching to a superior format(s) is that manufacturers will save money down the road. I understand, however, that quantifying the cost savings is exceedingly difficult. Moreover, as one CAD developer told me, there’s an unwritten incentive for the status quo (read: Gerber) because manufacturers don’t want to appear inflexible.

I would argue that the industry’s margins can’t afford to keep sending bad data downstream and hoping for a miracle in return. Fabricators over the past decade have lost most of their influence over the printed circuit board development. This is an area where they can truly coach their customers — and add value in the process. They should grab it.