Fusion - PCB in assemblies now have joint errors

[BristolBrailleTechnology]

so with the latest update my assembly files with linked 3d pcbs all have joint errors

this is in a few of my assemblies with linked pcbs (havent checked them all). That particular error code happened on a new file with the 3d pcb freshly dragged in and a component joint to it.

link to file
https://a360.co/4hPUnkF

any help to resolve this will be gratefully received.

This post has been edited due to: @lauri_barnhart added the product to the title to help more community members find this topic.

[BristolBrailleTechnology]

hmm, well this is a big problem for me now. any assembly with a pcb joint error seems to block any other joint being edited or made. so my workflow has halted now. I hope someone can help me out soon.

this is a new issue.  Before this I've working on this file without issue for the last few months.

[jorge_garcia]

Hello @BristolBrailleTechnology ,

I'm reaching out to the team that works on joints. I'll see what I can find out for you.

Best Regards,

[mayank.malukani]

Hi @BristolBrailleTechnology , for the original issue mentioned, on initial look,  in the PCB design 'side button pcb' , seems like the Ground to Parent on some components and the Rigid group are not going well together and causing a conflict. If I suppress the Rigid group or the Ground to Parent on the components then the joint seems to succeed. Let us know if this helps. We will continue the investigation at our end as well. 

Regards,

Mayank Malukani

Fusion - Assembly Development

[BristolBrailleTechnology]

thanks for this. So do i need to go through all my affected pcbs (looks like all of them) and adjust this grounding/ rigid group feature?

[BristolBrailleTechnology]

Can you elaborate further on this? I'm still getting the same error, even when i unground the linked pcb component.

The only rigid group in this design is the automatically made one when a 3d pcb is generated from the 2d pcb stage.

https://a360.co/4hPUnkF

This link is example of what I'm getting any any design i have with a linked pcb in it. I've tried deleting and remaking the link in the existing assembly, remaking the entire assembly, editing, updating and resaving the pcb design. none of this works.

My workflow is kind of stuck now and my latest prototype is now being held up. Any help fixing this newly appeared issue would be great.

[mayank.malukani · Accepted solution]

Hi @BristolBrailleTechnology , I was talking about the Ground to Parent on in the internal components inside the package. Like the one shown in below image

Can you try UnGrounding from Parent these components in your design. You will need to go there source design to do that. I do not have access. 

Please let me know if you need help ungrounding these or that did not help with your issue. 

[BristolBrailleTechnology]

oh wow! i totally missed that thanks. so yes this solves it. but i now have to go through all my affected pcbs and resolve this which is a bunch of extra work. is there any way around this?

Also to remove the grounding feature i had to go all the way to the offending parts library, break the 3d model link, save it and go through hierarchy of schematic, 2d pcb, assembly, sub assembly. I couldnt unground the part from the top most assembly file. Am i missing something or is what i did the correct process?

thanks

Nic

[mayank.malukani · Accepted solution]

@BristolBrailleTechnology Glad to hear it worked. This was a temporary solution to unblock your current design, we are still investigating why it is causing an issue.

Unfortunately, this is the only way to remove Grounding from the existing designs. You can try to use 'Edit in Place' from the top most assembly which will be slightly faster I guess. 

For future designs, you may chose to disable default Grounding of components from preferences : 

[BristolBrailleTechnology]

ok, thanks, as long as i know that's the correct workload then I'll grind through. good luck with the investigation 🙂

[jorge_garcia]

Hi @BristolBrailleTechnology ,

There was fixed released for this recently and the workaround should no longer be needed. Could you confirm this is indeed the case? Are you still running into this?

Best Regards,

[BristolBrailleTechnology]

Hi Jorge, I fixed them all with the previous advice so i cant say if the update fixed it or not sorry.