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.

How to force machine simulation to machine at A negative values

How to force machine simulation to machine at A negative values

officeKFSML
Explorer Explorer
335 Views
2 Replies
Message 1 of 3

How to force machine simulation to machine at A negative values

officeKFSML
Explorer
Explorer

I am trying to use adaptive 3d roughing on two surfaces which are on the sides of the part. For one it machines the part in front of the table (A-90) but for the other it machines at the back (A+90) which is not good as the operator cannot see what's going on. 
Can I force instead of A+90 to do A-90 C +180 ?

I tried setting up in the Kinematics to be preferred negative angles for A but no luck with that.

0 Likes
336 Views
2 Replies
Replies (2)
Message 2 of 3

seth.madore
Community Manager
Community Manager

For the public, there's only limited steps one can take to improve this. Yes, the machine config should be the route to go, curious that it's not.

 

However, we do have a feature available to members of our Insider Program that should give you the tools needed for this to work. Membership is free, but it does involve an application process. You can apply here: https://feedback.autodesk.com/key/Fusion360Insider


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 3 of 3

brekmiller
Autodesk
Autodesk

One other thing, after you change the preferences in the Kinematics, regenerate the toolpaths before simulating again.

 

When you simulate a toolpath for the first time, Fusion makes a note of which solutions were chosen.  All subsequent simulations (and post processing) will ignore your Kinematics settings and will try to reuse the original solutions.  Regenerating the toolpath will clear these saved solutions.

 

Fusion does this because it would be dangerous if it showed you one set of solutions when you simulate a toolpath (and saw that there were no collisions) and then chose different solutions when you post process and run the program on a machine.



Brek Miller

Software Engineer