Workflow ruined due to the last update

[erik.hole]

Hi,

We use F360 to develop antennas that we draw and simulate in an external software. Previously we've had good success of the workflow:

1. Importing .dxf to a 3D design

2. scaling the .dxf sketch to the correct dimensions

3. Create 3D PCB and selecting the the sketch containing the lines from the .dxf

4. In the PCB tool, we took the lines from the board outline and converted it to polygon.

This was working perfectly, but now our files are getting corrupted when we try to use the cam processor, after converting splines to polygon. This is setting us days in using a different software to solve our PCB needs for our antenna designs.

The .dxf import ulp doesn't work, so that's no help. Is there a way that we can import custom polygons to PCB that also doesn't crash the software when we try to create gerber files?

Hoping there are some other workflow that is as easy as the one we have used so far.

Best Regards,

Erik Hole

[yqliu]

Hi @erik.hole ,

By reading your description sounds like the problem is the splines. If that's the reason, you can try to convert the splines into polylines using some tools, for example, https://apps.autodesk.com/FUSION/en/Detail/Index?id=4611814297957846949.

Please let me know if this doesn't work.

Best regards,

Richard

[erik.hole]

Well, the whole workflow is converting the splines to polygons and moving it to a copper layer. The issue is after doing this, Fusion crashes when we try to enter the cam processor and then the whole PCB file gets corrupten.

Best Regards,

Erik Hole

[yqliu]

@erik.hole , this issue will be fixed in the next update. Before the update, you can try one of the following workarounds:

1. You can convert the splines into line segments in sketch environment first, then create the 3D PCB and 2D PCB.
2. Or you can export your pcb as "EAGLE 9.x Compatible Files", then add it into a new project and do CAM there.

[erik.hole]

Ok, that's good to hear. Meanwhile we have been using the workaround #2 since posting this. I will accept solution when the update that actually fixes this is live 🙂