Fusion to Vericut (cascading) post processor

[emlyn.stansbie]

I'm currently utilizing the cascading post for the Fusion to Vericut interface which works really well.

The major issue I have found is the interface doesn't translate the different types of tools that Vericut uses correctly. All the tools output to (TLS file) Vericut are all 'mill' tools which when you go to run the Vericut simulation an error appears when probing. As Vericut doesn't see this as a 'Probe' and so shows an alarm to say the spindle isn't rotating and the tool has collided with the stock!

With FUSION's on-going development and enhancements with probing functions this should be looked at ASAP.

Could the cascading post for Vericut be altered so that it defines the different tools correctly for Vericut i.e. hole making, Probe, Turning Tool, etc, etc ????????

[g-andresen]

Hi,

the  Manufacture Forum could be better for this purpose

günther

[bob.schultz · Accepted solution]

Hello @emlyn.stansbie,

The latest version of the Vericut post processor does support hole making tools.  Please download and use this version.  We will take a look at implementing probing tools into the library post.

[Anonymous]

I just downloaded the file but what are the setup instructions for the Vericut post processor to get it run smoothly? I don't get the legend "Using Cascade: 'VERICUT'"

[Anonymous]

Never mind I just already solve it.

For future people looking the same just click on Setup (Post processor page), choose to "Add Cascading Post" and browse for Vericut Post, done!.

P.D. I put those 2 files from zip on the same folder as posts are.

[bob.schultz]

Hello @emlyn.stansbie,

Thought you would like to know that Probing tools are now supported in the Vericut post processor.

https://cam.autodesk.com/hsmposts?p=vericut

[HughesTooling]

---

@Anonymous wrote:

P.D. I put those 2 files from zip on the same folder as posts are.

---

Are you saying you put them with all the other generic posts? If you have you'll have problems the next time Fusion updates, you should move them to the personal posts folder or to the cloud.

Do not put custom posts in the generic posts folder. Use the personal folder, or another location. Or enable cloud posts and upload to the cloud assets posts folder.

Fusion 360 CAM Personal Posts Folder Locations

_______________________________________________________________________________

Microsoft Windows:
%appdata%\Autodesk\Fusion 360 CAM\Posts

Mac / Apple / OSX:
/Users/<user id>/Autodesk/Fusion 360 CAM/Posts

Mark

[Anonymous]

I know!

They disappear every time when Fusion is updated. I Just download again the posts and put it again to the default folder.

I use this 'cause when I post the program I only have to choose the vendor, machine type then the post and we're ready to go. I'll check for using posts on the cloud tho, thanks.

[emlyn.stansbie · Accepted solution]

Many thanks for updating the posts and letting me know! @bob.schultz