IS there any way ODB++ files can be generated from eagle?
I tried by exporting to pulsonix first but with complex designs this gets messy.
IS there any way ODB++ files can be generated from eagle?
I tried by exporting to pulsonix first but with complex designs this gets messy.
Ok thanks for the fast reply,
We have had several issues with assembly partners because they want to run valor checks on the boards and they cant run Valor checks on gerber files. When we use gencad sometimes the pads get rotated and then the optical instpection systems cant check the board because the pads are rotated in the files.
All together we are verry happy using eagle but the incompatability with other industry standards makes it difficult to use eagle from time to time. Ill hope you guys take this into account for future developments.
Ill hope you guys take this into account for future developments.
I will forward your request to our development people, let's see what the say......
Hi Richard,
Any news on this topic?
best regards,
Pepijn Herman
Hi Pepijn,
no sorry no news yet....
Regards,
Richard
Please add my name to the requests for ODB++ support in Eagle.
Hi Joe,
noted your request and will forward it to our development team.....
Regards,
Richard
Hi Richard,
Please add my name to the request for ODB++ support in Eagle. Thanks.
Hi,
there are still no changes concerning ODB++ in EAGLE. Basically it is possible to write an ULP that allows exporting this data format. You only have to have a good description of the data format and a bit of skills in programming ULPs. But the User Language is fully documented in the EAGLE help.
By the way:
Recently I talked to a well-known board manufacturer and he told me that there are only very very few clients that are sending ODB++ data format. Gerber is considered simply as the better format.
Regards,
Richard
Hi Richard,
Most of the EMS needs intelligent data like ODB++ for process analysis and preparation. With only Gerber driven data one must reverse engineer as far as needed with all possible problems that process (which can be avoided) might introduce.
Bareboard manufacturers may only need artwork (gerber) and some technology information’s. Assembly houses may additionally need centroid information, netlist, BOM`s, etc... in order to be able to prepare the data for assembly, test or whatever.
We(EMS company) personally advise our customers who are using eagle to send us a .brd file or to generate a FATF file as we are able to use those. With gerber driven data, our “time to market” is because of the QA around it just longer. After all we are trying to reduce human error and deliver quality.
We prefer unlike the board manufacturer you spoke with to receive an ODB++ data for a various well thought reasons.
I think that Eagle should seriously consider the possibilities to adapt ODB++ within the business goals of course. I must agree, those NDA`s are sometimes nasty.
Mentor (valor division) is promoting ODB++ as never before, they even launched http://www.odb-sa.com/ for such cases.
Billo