Allegro 17.40.028 Canvas Export Issue

try updating the 3D model mappings using the batch file sym_3d_update.exe and then try exporting the pdf and step. You can find this in <install_directory>/tools/bin folder. For example, run this batch on windows command prompt for updating all the symbols in the psmpath variable,

sym_3d_update -d "C:\symbols_v174"

Try  sym_3d_update -help to see avaialble switches with this command.

Folks,

I should also mention that this routed PCB obviously had designed PCB footprints, but I did not assign any STP models to any of the components during the footprint creation.  I thought all you needed to do was to "map" or assign a given STP (STEP if you like) drawing to any component shown as a default or simple "boundary" model in the Canvas 3D viewer.  That seemed to work as the default monolithic "boundary" block became the STP model from the manufacturer.  The Canvas 3D model looks great, but when you export the 3D PDF or STP 3D file, I get a jumbled mess of graphics of one component's STP file for EVERY component placed on the PCB.

Is this issue caused by assigning STEP models to footprints on the finished PCB before assigning the STEP model at the component footprint creation?

Hi mahimag,

Thanks!!  I think the fact that I did not define nor set a PSM path in the Preferences is causing this issue.  As I did not do the PCB layout for this board, I did not do any of the path setups except for the STEPPATH entry.  In short, it appears that I have to export all of the components used to a PCB library directory (*.dra, *.psm, etc.) and then do the STEP library directory as first entry in my Allegro Preferences.

In the meantime, I will use the sym_3d_update command to see if that works.  If it does, then that tells me that unless you take a given Allegro board and do all of the work I just described with the libararies and paths, the 3D mapping will be corrupt.  Under that condition, then, one has to manually update the export process...even though it looks great within the 3D Canvas environment, using the sym_3d_update command line approach.

Does this make sense to you?

I do not think it has anything to do with paths as you mentioned. But in cases like this remapping helps. You can try the utility or you can also try opening 3D Canvas, there in 3D mapper tab you can export *.map file and then import the same file back. This will also help in remapping models.

I belive there is some update in the 3D Canvas utility in this release which needs the models to be remapped otherwise they should work fine the way you have mapped them.