FAB3000 definitely outputs components in the ODB++ (provided there is component data), and this can be verified by importing your combined ODB++ file back into FAB3000 or any ODB++ Viewer (the component layers and information should definitely be visible).
However I believe the "vendor's issue" may be they're using a specific 3rd party tool to import the ODB++ files (for simulation, assembly machine, etc.), and that 3rd party tool expects the ODB++ component data to be arranged in a certain fashion (or containing specific attributes/properties).
All we need is any sample ODB++ file that does work for your vendor (it can even be a sample demo file), and we can quickly determine exactly what your vendor requires. Usually within a few days we can have an update of FAB3000 available, that does works perfectly for your vendor.
Note: This is very common and we're happy to help.
Why does this happen? Most 3rd party developers will add ODB++/IPC-2581 importers to their existing tools (i.e simulation, assembly machine, etc.) - but during development will only use a small subset of ODB++ files for their testing and usually from a single vendor like: Cadence or Altium. Unfortunately every PCB CAD tool worldwide outputs their CAM files differently. For example an identical PCB design exported to ODB++, from both Cadence and Altium will be drastically different - if you perform a file comparison; plus certain property/attributes will be in different areas, sections or files.
Thanks again, and I look forward to hearing from you.
FAB3000 definitely outputs components in the ODB++ (provided there is component data), and this can be verified by importing your combined ODB++ file back into FAB3000 or any ODB++ Viewer (the component layers and information should definitely be visible).
However I believe the "vendor's issue" may be they're using a specific 3rd party tool to import the ODB++ files (for simulation, assembly machine, etc.), and that 3rd party tool expects the ODB++ component data to be arranged in a certain fashion (or containing specific attributes/properties).
All we need is any sample ODB++ file that does work for your vendor (it can even be a sample demo file), and we can quickly determine exactly what your vendor requires. Usually within a few days we can have an update of FAB3000 available, that does works perfectly for your vendor.
Note: This is very common and we're happy to help.
Why does this happen? Most 3rd party developers will add ODB++/IPC-2581 importers to their existing tools (i.e simulation, assembly machine, etc.) - but during development will only use a small subset of ODB++ files for their testing and usually from a single vendor like: Cadence or Altium. Unfortunately every PCB CAD tool worldwide outputs their CAM files differently. For example an identical PCB design exported to ODB++, from both Cadence and Altium will be drastically different - if you perform a file comparison; plus certain property/attributes will be in different areas, sections or files.
Thanks again, and I look forward to hearing from you.
Best regards,
Simon
0 Votes
0 Comments
Login or Sign up to post a comment