{"id":22379,"date":"2019-06-12T22:21:15","date_gmt":"2019-06-12T14:21:15","guid":{"rendered":"\/blog\/?p=22379"},"modified":"2021-07-02T11:32:13","modified_gmt":"2021-07-02T03:32:13","slug":"how-to-generate-assembly-files-and-why-they-are-important","status":"publish","type":"post","link":"https:\/\/www.seeedstudio.com\/blog\/2019\/06\/12\/how-to-generate-assembly-files-and-why-they-are-important\/","title":{"rendered":"How to Generate Assembly Files and Why They are Important"},"content":{"rendered":"\n
\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n

In an ideal world, you can just give the bill of materials to an assembly house and they will have enough information to populate your PCBs correctly. In reality, it\u2019s rarely that simple. <\/p>\n\n\n\n

From our experience, even the most standard of standards, whether as interpreted by customers or provided directly by manufacturers can be flawed. Datasheets missing data or being unnecessarily cryptic, manufacturers deciding to go against widely accepted standards, designers failing to indicate orientations and polarity markings or just plain silly mistakes, there are a plethora of potential pitfalls designers can fall victim to. These issues usually rear their ugly head at the last minute, at which point they can be a production nightmare to both designer and assembler. The amount of time and resources that could be lost should not be underestimated.<\/p>\n\n\n\n

The other day, someone rather bluntly asked one of our\nengineers, \u201cWell, what can we do about this?\u201d. For the here and now, there\nisn\u2019t really an easy solution, except just to be vigilant. Check, check again\nand check some more. There is ample talk of idealistic ways of tackling the\nissues from utilizing smart software to panning together to make standard footprint\nlibraries, but none can ever guarantee flawless assembly. <\/p>\n\n\n\n

Some examples of the problems we commonly face as an\nassembler:<\/p>\n\n\n\n