Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

A joint that won't delete

A joint that won't delete

Doubletop_
Advocate Advocate
439 Views
8 Replies
Message 1 of 9

A joint that won't delete

Doubletop_
Advocate
Advocate

I have a joint that won't delete. I suspect it is causing problems because once I step past it the component is moved to the jointed position but a copy of the component remains where it was originally. Moving further on in the timeline and Fusion crashes, and if it doesn't, it will crash if the design is saved.

 

I have moved the timeline to prior to the joint and it won't delete. Move it to beyond the joint and it deletes and the timeline moves before the joint but a greyed out  joint remains beyond the timeline marker. Step the timeline over the joint and it is back again.

 

I saw in a previous thread a possibility of command line solution but it was never provided

0 Likes
440 Views
8 Replies
Replies (8)
Message 2 of 9

g-andresen
Consultant
Consultant

Hi.


@Doubletop_  schrieb:

... I suspect it is causing problems because....


To verify this assumption, one must analyze the structure.

Please share the f3d File.

 

günther

0 Likes
Message 3 of 9

Doubletop_
Advocate
Advocate

I would share the file but as a last resort as there is a lot in it. I am looking for suggestions where to look e.g "I suspect it is causing problems because..."

 

In my investigations I have ventured into the dark world of python scripts and the deleteMe() function, although partially working in that the two joined components separate and the joint disappears from the browser tree. The function throws an exception and the joint hasn't actually been removed. So the deleteMe() function can find it again. My next step is to find the nature of the exception and see if I can find anything in the object attributes.

Pete

0 Likes
Message 4 of 9

g-andresen
Consultant
Consultant

Hi,


@Doubletop_  schrieb:

I would share the file but as a last resort as there is a lot in it. I am looking for suggestions where to look e.g "I suspect it is causing problems because..."

 

 


Whatever you say.

 

günther

0 Likes
Message 5 of 9

TheCADWhisperer
Consultant
Consultant

@Doubletop_ wrote:

I would share the file but as a last resort as there is a lot in it


@Doubletop_ 

Delete all components except for the issue and attach here. (Of course take care to not overwrite the original.)

0 Likes
Message 6 of 9

TheCADWhisperer
Consultant
Consultant

@Doubletop_ wrote:

I am looking for suggestions where to look e.g "I suspect it is causing problems because..."


Does Ctrl b (CMD b on Mac) return any issues?

Are there any unresolved issues highlighted in the timeline?

0 Likes
Message 7 of 9

Doubletop_
Advocate
Advocate

@Doubletop_ wrote:

Are there any unresolved issues highlighted in the timeline?


That is the clue I was looking for. I was focused on the first instance of the problem in the timeline thinking that moving the cursor there would negate any downstream problems. When I moved the time line downstream Fusion crashed. I have basically been following Rule #1 in a hybrid design so worked down the timeline, suppressing each component or assembly in turn. Moving the cursor as I went. As the joints between the components were are the high level they went red as the component was suppressed so I suppressed them as I went. Until Everything from the starting point to the end was suppressed. That stabilized the system so I was now able to start at the beginning, component by component checking them and then moving on until the culprit was found. 

The problem, I am sure many have, is not being strict enough with Rule #1 adherence and modifying components without activating them first and moving the timeline to where they were first invoked. Keeping everything i one place. Of course a Hybrid problem that probably doesn't exist with the separate components and assembly process as everything is kept in one place. 

Comments welcome please as my approach may be flawed in some way or missing some vital consideration.

Pete

0 Likes
Message 8 of 9

pkomatlapalli
Community Manager
Community Manager

Hi @Doubletop_ ,

 I wanted to follow up to see whether you still require assistance or if you were able to resolve your issue. Please let us know by providing an update. If you have already found a solution, we encourage you to share it with the community so that other members with similar questions may benefit from your experience.
 

Pavan Kumar | Community Manager
0 Likes
Message 9 of 9

Doubletop_
Advocate
Advocate

Pavan

 

No not entirely solved but under control. I had described what I had done in post #7. I believe the problem is caused by circular dependency or something similar. For example I have used two different bearing types, both are joined at the same place on an axle and both fixed into the same housing. I suppress one or the other as I need to check one version or another. In another case, I have 4 versions of a component and switch them in and out by suppressing them, as I wish. They are all joined to the same components but with their own joints. My theory is that if care is not taken on the switching in and out some sort of deadlock occurs. The other factor seems to be that although is joint is suppressed its dependencies still existent in the design so as this deadlock exists components and joints become impossible to delete.

 

Now this could be all wrong on my part but it does go some way towards me reconciling the situation in my head. I feel If I could remove one joint it would free up everything else. I would go so far to say if I could delete all the component to component joint at the top level (not sub-assembly level)  and I could systematically re-instated them and even get rid of the redundant component variants

 

Pete

0 Likes