3d SHS Blend vs Unified Morph

[neurosis]

I'm starting to like using the Unified (limited to 3d) path over some of the SHS paths.  I stayed away from them due to the lack of tool path filtering.  The last couple of jobs I've played with, I did a side by side. Even without the filtering the toolpath wasn't out of control as far as code output and the path was a lot cleaner with more control. 

When I try to add offset to the walls of the pocket using the SHS path, I get the pogo effect.  I end up having to create wireframe and moving it in to contain the blend.  With the Unified, it just works and even trims the path to the surface edge.

This was a super easy pocket but a good test part.

SHS path: 

Unified Morph

[crazy^millman]

On the Highspeed toolpath use the top surface as a check with zero stock to leave and see if the POGO effect goes away. The lack of a filter is the biggest reason I force myself to use the HSS toolpaths. To many customers still have machines with only 2mb of machine memory.

[gcode]

The lack of a filter is the biggest reason I force myself to use the HSS toolpaths. To many customers still have machines with only 2mb of machine memory.

Agreed, this is a big problem and often forces me to use a HSS toolpath when a Unified toolpath would do a much better job

[CNCAppsJames]

To many customers still have machines with only 2mb of machine memory.

They need the Poor Man's Dataserver. 😁

CF Card, a couple parameters and send it.