# Ask Me Anything with IPC-2581

**URL:** <https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850>\
**Category:** Ask Me Anything\
**Tags:** ipc, ipc-2581\
**Created:** [January 10, 2024, 8:26pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850 "2024-01-10T20:26:45Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucy.sierracircuits](https://sea2.discourse-cdn.com/sierraconnect/user_avatar/sierraconnect.protoexpress.com/lucy.sierracircuits/32/8_2.png) [@lucy.sierracircuits](https://sierraconnect.protoexpress.com/u/lucy.sierracircuits)\
**Post date:** [January 10, 2024, 8:26pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/1 "2024-01-10T20:26:45Z")

</div>

> **Ask Me Anything with IPC-2581**
>
> **Starts:** February 7, 2024, 1:00pm (America/Los\_Angeles)\
> **Ends:** February 7, 2024, 2:00pm (America/Los\_Angeles)

Have a question about **IPC-2581**? **Hemant Shah** and key IPC-2581 Consortium members will answer on Feb 7th!

---

<div class="post-metadata">

**Author:** ![lucy.sierracircuits](https://sea2.discourse-cdn.com/sierraconnect/user_avatar/sierraconnect.protoexpress.com/lucy.sierracircuits/32/8_2.png) [@lucy.sierracircuits](https://sierraconnect.protoexpress.com/u/lucy.sierracircuits)\
**Post date:** [February 3, 2024, 1:06am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/2 "2024-02-03T01:06:06Z")

</div>

What are the key features and objectives of IPC-2581, and how does it differ from other PCB file formats?

---

<div class="post-metadata">

**Author:** ![steve.carney](https://sea2.discourse-cdn.com/sierraconnect/user_avatar/sierraconnect.protoexpress.com/steve.carney/32/50_2.png) [@steve.carney](https://sierraconnect.protoexpress.com/u/steve.carney)\
**Post date:** [February 3, 2024, 1:12am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/3 "2024-02-03T01:12:04Z")

</div>

I think it would be interesting to answer how IPC-2581 facilitates collaboration and communication between the different stakeholders, ie. the designers, manufacturers, and assemblers.

---

<div class="post-metadata">

**Author:** ![mark](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@mark](https://sierraconnect.protoexpress.com/u/mark)\
**Post date:** [February 5, 2024, 4:07am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/4 "2024-02-05T04:07:58Z")

</div>

I have Rev B on Allegro. Is Rev C coming soon? What new features will it offer?

---

<div class="post-metadata">

**Author:** ![Jane](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@Jane](https://sierraconnect.protoexpress.com/u/Jane)\
**Post date:** [February 5, 2024, 4:34am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/5 "2024-02-05T04:34:08Z")

</div>

What are the advantages of using IPC-2581? How does it help with design and/or manufacturing?

---

<div class="post-metadata">

**Author:** ![George](https://avatars.discourse-cdn.com/v4/letter/g/71e660/32.png) [@George](https://sierraconnect.protoexpress.com/u/George)\
**Post date:** [February 5, 2024, 4:37am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/6 "2024-02-05T04:37:56Z")

</div>

I saw you’re doing a webinar on data handoff with 2581. Will you explain how you maintain data integrity and accuracy during the design-to-manufacturing process?

---

<div class="post-metadata">

**Author:** ![Charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@Charles](https://sierraconnect.protoexpress.com/u/Charles)\
**Post date:** [February 5, 2024, 4:46am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/8 "2024-02-05T04:46:14Z")

</div>

How well is IPC-2581 supported by EDA tools? Is it supported by all tools?

---

<div class="post-metadata">

**Author:** ![Rilley](https://avatars.discourse-cdn.com/v4/letter/r/7ea924/32.png) [@Rilley](https://sierraconnect.protoexpress.com/u/Rilley)\
**Post date:** [February 5, 2024, 4:50am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/9 "2024-02-05T04:50:22Z")

</div>

Does Sierra Circuits accept IPC2581 files? How do we send you such files?

---

<div class="post-metadata">

**Author:** ![dale.wager](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@dale.wager](https://sierraconnect.protoexpress.com/u/dale.wager)\
**Post date:** [February 5, 2024, 6:27pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/10 "2024-02-05T18:27:33Z")

</div>

Is the IPC-2581 a complete manufacturing file for both PCB manufacturing and PCB assembly?  
Are there any additional supporting files required when submitting a design in the IPC-2581 format?  
How does it differ from ODB++  
How readily is IPC-2581 accepted by the Contract Manufactures? The Chinese CMs we use prefer ODB++. They say they have problematic issues with IPC-2581

---

<div class="post-metadata">

**Author:** ![j.p](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@j.p](https://sierraconnect.protoexpress.com/u/j.p)\
**Post date:** [February 5, 2024, 7:00pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/11 "2024-02-05T19:00:37Z")

</div>

What does this output include? Do I still need to to include the IPC-D-351, NC-Drill Files? What about testpoints? Does it also include the stackup?

---

<div class="post-metadata">

**Author:** ![bbegel](https://sea2.discourse-cdn.com/sierraconnect/user_avatar/sierraconnect.protoexpress.com/bbegel/32/247_2.png) [@bbegel](https://sierraconnect.protoexpress.com/u/bbegel)\
**Post date:** [February 5, 2024, 7:34pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/12 "2024-02-05T19:34:01Z")

</div>

I am not very familiar with IPC-2581, majority of times I used Gerber RS-274X format for most of the PCB design I was involved with.  
My general question is, what con and pro to use IPC-2581 vs. Gerber?

---

<div class="post-metadata">

**Author:** ![joe.bak](https://avatars.discourse-cdn.com/v4/letter/j/43a26b/32.png) [@joe.bak](https://sierraconnect.protoexpress.com/u/joe.bak)\
**Post date:** [February 5, 2024, 9:10pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/13 "2024-02-05T21:10:47Z")

</div>

IPC-2581 seems to have solid, multi-vendor support from CAD tools, but I have seen **extremely poor** uptake from PCB fabricators. I can only think of two fabricators that will let me upload a project in IPC-2581 for an automated quote (Sierra is one of them).

What is being done to coax fabricators to adopt this standard? Does The Consortium need to offer them free CAD format conversion tools until they are weaned off of legacy formats? Do they just need to lose business before they will upgrade?

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 4:56am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/14 "2024-02-06T04:56:45Z")

</div>

IPC-2581 Revision C was released in 2020, the software vendors started supporting it in 2021 onwards. Manufacturing vendors then started supporting it based on their customers needs/demands

To read about what’s new in revision C you can read  
a) this article by Ed Acheson, who was the technical chair for the IPC-2581 at the time - [Design007 Magazine - Design007-Mar2021 (uberflip.com)](https://iconnect007.uberflip.com/i/1348195-design007-mar2021/67?)

and / or  
b) listen to this interview Sierra Circuits did at PCB West a few years ago - [IPC-2581 Revision C for PCB Data Management by Hemant Shah | Sierra Circuits (protoexpress.com)](https://www.protoexpress.com/blog/ipc-2581-revision-c-facilitates-pcb-data-management-by-hemant-shah/)

I also suggest you start following the consortium LinkedIn page - [IPC-2581 Consortium | LinkedIn](https://www.linkedin.com/company/ipc-2581-consortium/) - to get periodic updates from us

You can also subscribe to our emails, which are very few in the year - 5 to 6 times - where we annnounce our presence at a show or talk about a blog you should be aware of. - go to [ipc2581.com](http://ipc2581.com) and subscribe to emails.

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 5:14am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/15 "2024-02-06T05:14:25Z")

</div>

IPC-2581 is an intelligent, open format developed by the industry through IPC. It provides function modes to protect IP by providing intelligent subset of the design for fabrication only, assembly only or for stencil creation etc. All of the data that is needed to build your board is included in the file and through function mode you can limit the amount of data shared with your manufacturing partners.

It is the only open bi-directional standard. It provides two ways to exchange data with your manufacturer. First, it allows the designer and manufacturing house to exchange the stack up BEFORE the design is started. This is important for high speed signals on your design. It eliminates manual entry of stack up by teh designer based on data from the manufacturer.

Second, it supports exchange of Design for Manufacturing (DFx) including questions, exceptions and any changes your manufacturer asks for in the design before manufacturing your board. This data is exchanged electronically in 2581 format, so all your approvals can be archived with the design data itself. Plus the DFx exchange is much more smoother and contextual than through emails, powerpoint, excel etc etc

information about IPC2581 adoption and support can be found on [ipc2581.com](http://ipc2581.com).

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 5:20am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/16 "2024-02-06T05:20:02Z")

</div>

All major EDA tools have been supporting IPC2581 for several years now. Just this year, KiCAD started supporting IPC-2581 revisionB.

IPC2581 Consortium provides a support matrix on [ipc2581.com](http://ipc2581.com) that shows all the software that supports IPC2581 - [Support | IPC- 2581 Consortium (ipc2581.com)](https://www.ipc2581.com/support/)

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 11:49am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/17 "2024-02-06T11:49:17Z")

</div>

Yes, Sierra Circuits does accept IPC-2581. Its easy to generate IPC-2581 from your PCB design tool. You can contact your PCB design tool company to guide you on what you need to do to generate IPC-2581.

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 11:55am UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/18 "2024-02-06T11:55:27Z")

</div>

IPC-2581 is an intelligent format. Gerber packages include a ton of files and they all must be in sync. Often one or two of the files are not in sync in the package.

Advantages of IPC-2581 are  
a) intelligent format - it includes all the data that is needed to fabricate, assemble and test your PCB. In addition you can just send the subset of data that is needed for a specific manufacturing task. For example, you can send just the fabrication data, but not the assembly data.  
b) it is bi-directional. Two things can go back and forth. First is stack up data and second is DFx data, eliminating ePaper based communications using Excel, PowerPoints and emails.  
c) Secure design data exchange with function modes. THere are several built in function modes and several tools allow users to customize and create their own by choosing what to include and what not to include

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 12:03pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/19 "2024-02-06T12:03:40Z")

</div>

IPC-2581 is a complete data set for fabricating and assembling and testing your PCB.  
There are no additional files required. The 2581 file with revision C also includes things like intentional shorts, embedded components, complete impedance specifications and much more. You can read about what’s new in revision C in this article - [Design007 Magazine - Design007-Mar2021 (uberflip.com)](https://iconnect007.uberflip.com/i/1348195-design007-mar2021/67?)

ODB++ is also an intelligent format, but it is a proprietary format. in 2004, ODB++ format was donated to IPC and a merger of IPC’s GENCAM and ODB++ created IPC-2581.

IPC-2581 is adopted by many design houses, CMs, Fabricators and other manufacturing companies. The key has always been a customers requiring/requesting their suppliers to support 2581. If a CM is having trouble using 2581, ask them to reach out to ioc2581 consortium. Consortium members are ready to assist them overcome their issues, Often the issue is lack of information or lack of right connections. Consortium is made up of companies in the entire PCB design and supply chain.

contact the consortium through the contact us page on [ipc2581.com](http://ipc2581.com)

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 12:10pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/20 "2024-02-06T12:10:44Z")

</div>

IPC2581 is an intelligent design data exchange format. All others are data “hand-off” formats. The data integrity is built in with all the data that is needed being included in the 2581 file. Security is maintained through function modes that allows designers to only send the subset of data that is needed for a particular manufacturing step.

Included below is a slide that shows you the power of function modes.

 ![FunctionModeSlide](https://global.discourse-cdn.com/sierraconnect/original/1X/f2b9e77a22ca749e5a9e1ea31fe194c5a56d3190.png)

---

<div class="post-metadata">

**Author:** ![hemant.shah](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@hemant.shah](https://sierraconnect.protoexpress.com/u/hemant.shah)\
**Post date:** [February 6, 2024, 12:20pm UTC](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850/21 "2024-02-06T12:20:51Z")

</div>

Everything you need to build the board is included in the file. You don’t need any additional files or data. It includes stackup also. included below is a slide that tells you what all is included

 ![WhatDoesItContain2](https://global.discourse-cdn.com/sierraconnect/original/1X/c966b06df4f4da871d9e7bc5fe5846221d937ff7.png)

[Next page](https://sierraconnect.protoexpress.com/t/ask-me-anything-with-ipc-2581/850.md?page=2)
