

The footprints are easy to rename but apparently the 3D packages cannot be renamed. But upon further investigation the names of the footprints and 3D packages did have "&" characters. I saw this before but didn't think it was the problem because in my case the name of the "Device" did not have any special characters in it. We have got a fix and before the updated is released, a workaround is you might change the component name, or use a different for the extra nudge in the right direction. The problem is the name of some components contains special characters like "/". It does switch to the 3D PCB screen and show the 3D PCB, but it's unresponsive and crashes after a few you for reporting the issue and sharing your designs to us. I didn't add any notes, but the way I caused this was to open the project, go to the board designer, and click "View 3D PCB". In the mean time, if you want to look at a specific CER, here's one I just sent. There is a fair bit of process abuse and general bungling going on here (Diptrace to Eagle to Fusion) which I think is confusing matters unnecessarily. Getting back to the crashing, I'll try and do some more investigation to narrow things down a bit before posting any files. Then I threw away the imported PCB and started a new one.Īt the end of the day, I would say the only value in importing a Diptrace schematic would be to use as a template for a new schematic, or if you just need it for documentation purposes (visual only). What I ended up doing was to basically use the imported schematic as a template, replacing every component with one from an existing Eagle library. To be honest, once I figured out that the schematic to board linkage had problems I mostly just gave up. Because the libraries don't really transfer over correctly, there is no linkage between schematic and PCB, or at least it isn't complete. But anyway, at the end of the day it's most likely not worth the effort if you plan to make a PCB with the imported schematic. I did manage to find a way to export a library of parts used in the schematic into Eagle, but the process was so weird and convoluted that I actually can't remember how I did it. The problem though is that you don't automatically get the part libraries to go along with them. The newer versions of Diptrace have an export to Eagle function for schematics and boards.

Would you be willing to share the files for review? There might be a unique object that Fusion is running into and causing the crash. I'm really curious as to what the procedure would be. workstation did you get a Diptrace file into Fusion? As far as I know that's not supported at all.Fusion electronics deleting associated files 1.Fusion 360 Electronics Polygon Unrouted Error 1.
