topic Sheet metal drawing wrong bend table and numbering in Fusion Design, Validate & Document Forum

Sheet metal drawing wrong bend table and numbering

kru96 — Mon, 04 Jan 2021 11:44:11 GMT

Hello everyone,

I am having trouble when making the drawing of a sheet metal part with bends.

This is the finished part:

This part is made by drawing one half and then mirroring it. This is the half drawn in first place:

In any case, now that I am trying to do a drawing of this part, the bend table and its numbering is wrong.

There are two problems:

- Duplicate bend numbers

- Wrong bend directions

I though maybe it has something to do with the way of designing this component described above but I really can't find any coherency in this.

Any though? Any help?

Thank you

Re: Sheet metal drawing wrong bend table and numbering

TheCADWhisperer — Mon, 04 Jan 2021 12:06:01 GMT

@kru96
I though maybe it has something to do with the way of designing this component described above but I really can't find any coherency in this.

Any though? Any help?

Can you File>Export your *.f3d file to your local drive and then Attach it here to a Reply?

Re: Sheet metal drawing wrong bend table and numbering

kru96 — Mon, 04 Jan 2021 12:44:59 GMT

The component has many references to other component of the design, which I'd rather not share, But I have created a simplified design which follows the same approach and generates the same results. I'm attatching it.

The drawing produced is this one, with the same errors:

Thank you.

Re: Sheet metal drawing wrong bend table and numbering

TheCADWhisperer — Mon, 04 Jan 2021 13:43:35 GMT

Try the Attached file.

(You will need to change the Bend Radius on my example.)

Re: Sheet metal drawing wrong bend table and numbering

kru96 — Mon, 04 Jan 2021 17:45:25 GMT

Thank you @TheCADWhisperer for your assistance. Your design does produce indeed the drawing without the mentioned errors. However, the technique used to achieve it is not compatible with my design (it would require a completely new approach).

In any case, I don't think this is a problem about the methodology used to design the component, I think this is some sort of bug that @Anonymous should take a look at. Maybe this post should be moved to the support forum.